Garance A Drosihn wrote:
> At 7:18 PM + 7/29/02, [EMAIL PROTECTED] wrote:
> >I cvsup'd on Friday of last week, after I restored /usr. Did
> >the fix come later than that? I'm kind of afraid to try it
> >again :) Thanks, Rob.
>
> The fix in question was to -stable, not -current (I am not
At 7:18 PM + 7/29/02, [EMAIL PROTECTED] wrote:
>I cvsup'd on Friday of last week, after I restored /usr. Did
>the fix come later than that? I'm kind of afraid to try it
>again :) Thanks, Rob.
The fix in question was to -stable, not -current (I am not sure
if that was mentioned earlier).
I cvsup'd on Friday of last week, after I restored /usr. Did the fix come later than
that? I'm kind of afraid to try it again :) Thanks, Rob.
>- Original Message -
>From: Dag-Erling Smorgrav <[EMAIL PROTECTED]>
>To: rob <[EMAIL PROTECTED]>
>Sent: 29 Jul 2002 18:26:23
>
>rob <[EMAIL
rob <[EMAIL PROTECTED]> writes:
> I mounted my -stable /usr partition on -current /mnt to copy over a
> kernel config file, and when I finally fired up -stable, the /usr
> partition was borked. Fsck couldn't fix it manually. Luckily I had
> backups. It said that the master record didn't match t
rob wrote:
> I mounted my -stable /usr partition on -current /mnt to copy over a
> kernel config file, and when I finally fired up -stable, the /usr
> partition was borked. Fsck couldn't fix it manually...
I'm told that the fsck on -stable has been updated to fix this
problem. Have you updated
I mounted my -stable /usr partition on -current /mnt to copy over a
kernel config file, and when I finally fired up -stable, the /usr
partition was borked. Fsck couldn't fix it manually. Luckily I had
backups. It said that the master record didn't match the alternate. I
might have rebooted wit
