| 1 |
Stroller <stroller@××××××××××××××××××.uk> writes: |
| 2 |
|
| 3 |
> On 19/11/2010, at 12:57am, Allan Gottlieb wrote: |
| 4 |
>> Mick <michaelkintzios@×××××.com> writes: |
| 5 |
>>>> |
| 6 |
>>>> Should I now run emerge -e world? If so, I suppose I should stop cron |
| 7 |
>>>> from running an emerge --sync during the night. |
| 8 |
>>> |
| 9 |
>>> I used to do the same with reiserfs, but since I borked badly a reiser4 fs I |
| 10 |
>>> decided it is safer to use a LiveCD for this job. So I have to say YMMV. ;-) |
| 11 |
>> |
| 12 |
>> I am not sure I understand. If I use a liveCD, won't I have to chroot |
| 13 |
>> to the disk with my real system? In that case can't I get the same |
| 14 |
>> fs breakage? |
| 15 |
> |
| 16 |
> You don't have to chroot to run fsck. You can just boot from the LiveCD and run `fsck -o -p -t -i -o -n -s /dev/sda1`. |
| 17 |
> |
| 18 |
> I feel a bit more confident fscking my root filesystem from a LiveCD, because you know that you're not repairing the floor you're standing on, and fsck can have full leeway to do what it needs to do to clear up the problem properly. |
| 19 |
|
| 20 |
The question was about emerge -e world not fsck (see quoted material |
| 21 |
above). |
| 22 |
|
| 23 |
The fsck succeeded prior to this (I did touch /forcefsck; reboot). |
| 24 |
|
| 25 |
thanks, |
| 26 |
allan |
Archives