1 |
On Wed, 21 Jun 2006 10:47:11 +0100, Paul Stear wrote: |
2 |
|
3 |
> I am running an ~x86 system and yesterday I did an emerge world, all |
4 |
> went well until the next time I booted. kdm ran but the screen just had |
5 |
> a flashing loggin box. I could not even get another terminal using alt |
6 |
> F1-F7. So I am faced with not being able to loggin at all. This raises |
7 |
> a few questions about my own inadequacies :- |
8 |
> 1. What is the correct procedure to recover a system in this state? |
9 |
> What tools do I need? |
10 |
|
11 |
In this case, all you need to do is boot without X, or SSH in from |
12 |
another box. As a last resort you could boot a live CD chroot and fix |
13 |
things. |
14 |
|
15 |
> 2. I have an rsynced backup on an external usb harddrive, but unless I |
16 |
> can loggin how can I restore the files from the backup? |
17 |
|
18 |
By booting from a live CD. |
19 |
|
20 |
> 3. It appears that a freetype update was the cause of this failure, but |
21 |
> this information was hard to find on the forum's (I was lucky). I had |
22 |
> an old installation cd and chroot'ed and emerged the previous version |
23 |
> of freetype, rebooted and all is well (I hope). |
24 |
|
25 |
Yes, it was a patch to freetype that caused this. I got bitten too. |
26 |
|
27 |
> 4. How can an update like this get into ~x86 tree when it plainly |
28 |
> causes a major problem? |
29 |
|
30 |
Because ~arch is for testing. A ~ keyword only guarantees that it works |
31 |
for the ebuild's author, that's why it is called testing, you are the |
32 |
tester. Had this bug made it through to the stable tree, you would have |
33 |
cause for complaint. |
34 |
|
35 |
> I wonder if I should revert to just x86. |
36 |
|
37 |
If you are not willing to accept the risks and responsibilities of |
38 |
running a testing system, then the answer is probably "yes". |
39 |
|
40 |
|
41 |
-- |
42 |
Neil Bothwick |
43 |
|
44 |
Bumper Sticker: If you can read this, you are in phaser range. |