Re: Boot issue. INIT cannot execute etc/rc.d/sysinit

2001-01-21 Thread RaghuNath L
corrcetion please boot through the rh6.1 cd and then try rescue RaghuNath L wrote: > Here is the simple solution bot through the linux as rescue and launch vi > editor delete the line what you added this wored for me in RedHat 6.1 > > Patrick Lacchia wrote: > > > > > > Yes I tried and it doesn'

Re: Boot issue. INIT cannot execute etc/rc.d/sysinit

2001-01-21 Thread RaghuNath L
Here is the simple solution bot through the linux as rescue and launch vi editor delete the line what you added this wored for me in RedHat 6.1 Patrick Lacchia wrote: > > Yes I tried and it doesn't work. Here is what happen > > 1) I type "vi rc.sysinit" > 2) The file open and the bottom line

Re: Boot issue. INIT cannot execute etc/rc.d/sysinit

2001-01-21 Thread Duane Clark
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

Re: Boot issue. INIT cannot execute etc/rc.d/sysinit

2001-01-21 Thread Ray Curtis
> "pl" == Patrick Lacchia <[EMAIL PROTECTED]> writes: pl> Guess what? I stupidly added 3 lines to etc/rc.d/rc.sysinit. It looked safe, pl> you just open the file with gnupad, add the lines, save. Safe until the next pl> time you reboot and find out that you can't use RedHat 6.2 anymore. Dur

Re: Boot issue. INIT cannot execute etc/rc.d/sysinit

2001-01-21 Thread Uncle Meat
On 21-Jan-01 Patrick Lacchia opined: > > Yes I tried and it doesn't work. Here is what happen > > 1) I type "vi rc.sysinit" > 2) The file open and the bottom line says "rc.sysinit [readonly] > 3) I jump to the lines I want to delete and do a "dd" on the first one > 4) The bottom line becomes re

RE: Boot issue. INIT cannot execute etc/rc.d/sysinit

2001-01-21 Thread Uncle Meat
On 21-Jan-01 Patrick Lacchia opined: > 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 n

Re: Boot issue. INIT cannot execute etc/rc.d/sysinit

2001-01-21 Thread jcunning
The problem is probably that / is mounted read-only. Before running vi to edit the file you want to change, enter mount / -o remount,rw I've recently had to do this, and I was able to save a new file, even one without writeable permissions, by using the ":w!" command. Jim Cunning On S

Re: Boot issue. INIT cannot execute etc/rc.d/sysinit

2001-01-21 Thread Matthew Melvin
On Sun, 21 Jan 2001 at 4:09pm (-), 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

Re: Boot issue. INIT cannot execute etc/rc.d/sysinit

2001-01-21 Thread Matthew Melvin
On Sun, 21 Jan 2001 at 4:09pm (-), 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

Re: Boot issue. INIT cannot execute etc/rc.d/sysinit

2001-01-21 Thread Patrick Lacchia
rst place with a text pad and now it's impossible to modify it again. Looks like all the files are read-only. I am wondering if it's due to the linux emergency mode. Patrick >From: rpjday <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: <[EMAIL PROTECTED]> &

Re: Boot issue. INIT cannot execute etc/rc.d/sysinit

2001-01-21 Thread rpjday
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