1 |
The Embedded Howto suggests mounting /proc and /usr/portage into the |
2 |
development root filesystem. Is mounting portage such a wise idea? |
3 |
|
4 |
Today, after having had a shell chrooted into the development |
5 |
environment for over a week, I decided to exit the shell, move the |
6 |
development environment out of the way, and create a new one. in the |
7 |
same location. I did: |
8 |
|
9 |
exit |
10 |
mv /opt/i586... /opt/i586....bak |
11 |
tar zxvf stage1-embedded -C /opt/i586.... |
12 |
|
13 |
And then for whatever reason: |
14 |
|
15 |
rm -rf /opt/i586.... |
16 |
|
17 |
Now, the problem is, I still had /usr/portage mounted on /opt/ |
18 |
i586..../usr/portage, and I guess mount points don't move when you |
19 |
move directories that contain them. |
20 |
|
21 |
The bottom line is, I blew away my host computer's /usr/portage, and |
22 |
now have to recover it. |
23 |
|
24 |
Since the development root filesystem is stored on a desktop machines |
25 |
harddrive, why not just have it get its own, separate portage tree? |
26 |
|
27 |
-Josh |
28 |
|
29 |
-- |
30 |
Joshua ChaitinPollak |
31 |
Software Engineer |
32 |
Kiva Systems |
33 |
|
34 |
|
35 |
-- |
36 |
gentoo-embedded@g.o mailing list |