Re: How to avoid meltdowns in the future
On Thu, Jun 27, 2002 at 03:04:20PM -0400, Andrew Perrin wrote:
>
> So, I tried booting to the rescue disk, then doing:
> linux single root=/dev/hda3
>
> which looked promising until it constantly recycled the error about not
> being able to create ksymoops because it's a read-only file system. I had
> to hard-reset to get out of that.
You were close there. I would have done a boot with
linux init=/bin/sh
You will then need to remount / and also mount proc:
mount -t proc proc /proc
mount -t whatever -o rw,remount /
You are then in a fairly safe position to start work. Note that when you
have finished, unmount every thing as much as you can, then:
sync
mount -t whatever -o ro,remount /
Then you can safely hard reboot, and although fsck will run, you shouldn't
have any problems.
> The only spare network card I had around was a 3Com, for which the driver
> wasn't in my kernel, so I couldn't toss it in.
Rule of thumb: keep 'sensible' device drivers compiled as modules. You
never know when you're going to need them, and let's face it, it really
won't add too much to the compile time.
Matthew
--
Matthew Sackman
Nottingham
England
BOFH Excuse Board:
not properly grounded, please bury computer
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: