Talk:Understanding Sugar code: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (moved Talk:Understanding sugar code to Talk:Understanding Sugar code: correct capitalization) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
==Alternate ways to peel the onion== |
==Alternate ways to peel the onion== |
||
I used a non-development image to do this exploration. As a result, I didn't have access to yum, rpm, or a bunch of other value added linux utilities. OLPC does have development images with these utilities added in to make development bearable. A fast way to see the full scope of a sugar installation is this one line command: |
I used a standard (non-development) image to do this exploration. As a result, I didn't have access to yum, rpm, or a bunch of other value added linux utilities. OLPC does have development images with these utilities added in to make development bearable. A fast way to see the full scope of a sugar installation is this one line command: |
||
rpm -ql sugar |
rpm -ql sugar |
||
Latest revision as of 21:12, 13 August 2010
Alternate ways to peel the onion
I used a standard (non-development) image to do this exploration. As a result, I didn't have access to yum, rpm, or a bunch of other value added linux utilities. OLPC does have development images with these utilities added in to make development bearable. A fast way to see the full scope of a sugar installation is this one line command:
rpm -ql sugar
It returns all sugar installation files with full paths.