On Sun, 21 Jan 2001, Patrick Lacchia wrote:
> Guess what? I stupidly added 3 lines to etc/rc.d/rc.sysinit. It looked safe,
> you just open the file with gnupad, add the lines, save. Safe until the next
> time you reboot and find out that you can't use RedHat 6.2 anymore. During
> the launch I now have a message saying, "INIT cannot execute
> etc/rc.d/sysinit". I tried several rescue solutions and so far the only one
> that gives me some result is to boot by typing linux emergency. That gives
> me the chance to log as root before INIT (and therefore rc.sysinit) is
> launched. From there I can access the file, edit it with VI but
> unfortunately not save it. The file is read only. I can copy the file on a
When your init stuff is screwed up your options are rather limited, as
far as I know. The reason that you cannot write the file is that in
"emergency" mode, the root filesystem is mounted read only, and there is
no way to write anything to it.
I believe that mode is really intended as a desperation measure. It
allows you to mount another partition, in read/write mode, copy over any
important files, and then wipe the root filesystem and start from
scratch. Propably not what you want.
With init mangled, you need to get another boot disk and use that. Since
it appears you still have network access, I can give two suggestions.
One is Toms Boot disk, which is a bootable Linux system on a floppy!:
http://www.toms.net/rb/home.html
But I much prefer a bootable CDROM. It can fit many more tools on it. If
you have a CDRW, then get:
http://open-projects.linuxcare.com/BBC/readme.epl
An excellent tool, with lots of READMEs on the CD to help you along. And
a tool that everyone should have laying around, for situations just like
yours. This will initially mount the filesystem read only, but in this
case you can unmount and remount it read/write, and make the changes you
need.
Duane
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
