*BSD News Article 24369


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!paladin.american.edu!gatech!usenet.ins.cwru.edu!lerc.nasa.gov!purdue!mentor.cc.purdue.edu!staff.cc.purdue.edu!spm
From: spm@staff.cc.purdue.edu (Sean McDermott)
Subject: Re: [Q] How to edit file /etc/rc.local
Message-ID: <CH01In.M37@mentor.cc.purdue.edu>
Sender: news@mentor.cc.purdue.edu (USENET News)
Organization: Purdue University
References: <CGwJJ9.BDq@oakhill.sps.mot.com> <CGxEpM.Bpw@mentor.cc.purdue.edu> <rwa.754075243@aupair.cs.athabascau.ca>
Date: Wed, 24 Nov 1993 13:59:10 GMT
Lines: 51

In article <rwa.754075243@aupair.cs.athabascau.ca> rwa@aupair.cs.athabascau.ca (Ross Alexander) writes:
>spm@staff.cc.purdue.edu (Sean McDermott) writes:
>
>>To edit the file....do the following.........
>>boot single user...(type -s at the boot prompt)
>>mount -u -o rw  /
>
>You might want to run "fsck /dev/rXX0a" for some suitable value of XX first.
>

True......thanks for pointing that out.

>>mount /var
>>mount /usr
>
>Ditto here.  Or else just "fsck -p".
>
>>mount (anything else in /etc/fstab)
>
>mount -t ufs -a.  He hasn't initialized the network yet.

good point.......if you need something off a nfs mount,  you will need to
start the networking code by hand.

>
>>cd etc
>>vi rc.local
>
>oldtimers tend to use ed rather than vi ;).
>
>>sync;sync;sync

I forgot the sleep 10; sync at the end....opps.

>
>This should be on three seperate lines.  Why?  Because it
>takes longer to type that way.
>
>>shutdown -r now


My main reason for posting in the first place was let you know,you should
avoid the "type control c in the middle of the fsck" theory......that can 
cause file damage.........
In general,  look for a way to do what you want,  in this case single user.
It is normally best to try and avoid "making something work"

-- 
spm@staff.cc.purdue.edu
Sean McDermott