On 2009-07-23 18:24, s. keeling wrote:
<ron.l.john...@cox.net> <ron.l.john...@cox.net>:
---- "s. keeling" <keel...@nucleus.com> wrote:
<ron.l.john...@cox.net> <ron.l.john...@cox.net>:
boot procedure still mounts / as RO, and so "it" can't write to
/var (which is part of /) and thus the boot process freezes just
after S55something.
(No, it doesn't drop me into single-user mode. I think it wants
to, but things fly by so fast that I can't see.)
Look on the bright side. You get to test your recovery procedures.
>>
Monty Python references not appreciated at this moment...
Is this better:
Pull out the CD-R to which you backed up your project directory.
CD-R??? Hahahahahaha. That's soooo 1998. Besides, they seem not
to age very well.
No, I'm not trying to be flippant. For the past 50 years, people/
organizations that don't make backups don't have any right to whine
about lost data.
You're right. That's why I've got external drives!
$ pydf -g /mnt/backups
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/b~vg-backup_lv 1834 854 886 46.6 [#..] /mnt/backups
-- Ron Johnson <ron.l.john...@cox.net>
:-) Tell me to STFU anytime.
Fortunately, science kicked me in the head: if the fs is clean, then
something else must be forcing it to RO!!
So, I changed the grub "set root" lines to point to the real root
device, and also told the boot line to mount root as rw instead of
ro. System up, and now I cooking with gas!
After, of course, I had to fiddle with the frickin net udev rules to
force the new mobo's NIC to eth0 and then reboot...
--
Scooty Puff, Sr
The Doom-Bringer
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
