On Friday 20 October 2006 04:11, Philip Webb wrote:
When using 'rm -f' (with or without '-r') the iron rule is
(1) goto the dir which contains the items to be removed
(2) 'pwd'
(3) 'ls whatever'
(4) if whatever is not '*', recall that line with Up-arrow,
backspace over 'ls'
On Wednesday 18 October 2006 22:07, Stuart Howard wrote:
Hey folks,
In advance I admit I have done a dumb! thing [by accident] I have
managed to delete most of /usr/lib/ and my backup does not seem to be
wholesome .
Could someone suggest a method for rebuilding the libraries?
I was thinking
On 18/10/06, Stuart Howard [EMAIL PROTECTED] wrote:
Could someone suggest a method for rebuilding the libraries?
If you have a working toolchain and python, then you can utilise
emerge to rebuild the system.
If not then you will need to acquire a binary gcc/etc to work around
it. Then
2006/10/19, Mark [EMAIL PROTECTED]:
If not then you will need to acquire a binary gcc/etc to work around
it. Then rebuild.
emerge -e world
I think, after having set up the tool chain, you'd do a
emerge -e system and then
emerge -e world,
because the system packages aren't considered by the
Thanks for the advice folks.
As it turned out I had enough of the lib left to keep some of the
system running and I managed to copy over sufficient to get a working
connection going then after much more thrashing of the head on desk it
turned out that my backup was sufficient to get portage
061019 Stuart Howard wrote:
I am now working on the --emptytree to restore everything properly.
ps. tip of the day when spring cleaning your system watch out for
those little typos that can ruin your summer :)
pps. Just for fun it went something like this,
rm -rf /usr/lib/libcrco.so /usr/lib/
Hey folks,
In advance I admit I have done a dumb! thing [by accident] I have
managed to delete most of /usr/lib/ and my backup does not seem to be
wholesome .
Could someone suggest a method for rebuilding the libraries?
I was thinking about a liveCD plus chroot but I would like some advice
7 matches
Mail list logo
