Re: rc.conf ...need help
On 2/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On 06/02/07, Jerry McAllister [EMAIL PROTECTED] wrote: On Tue, Feb 06, 2007 at 03:58:06PM -0500, Don Munyak wrote: How can I edit rc.conf while in single user mode. I've tried vi ee, but system doesn't recognize either. Thanks to everyone. I actually had fixed the file 2 minutes after receiving first reply but was unable to respond until now. However, having 2-3 different approaches and/or alternatives is also quite helpful. Thanks Again, Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
rc.conf ...need help
Hello,
I was tweaking the /etc/rc.conf file and apparently had a typo. Now
the system boots into single user mode. I know what my error is
syslogd_enable=YES {left off the first }
How can I edit rc.conf while in single user mode. I've tried vi ee,
but system doesn't recognize either.
Thanks
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rc.conf ...need help
On Tuesday 06 February 2007 15:58, Don Munyak wrote:
I was tweaking the /etc/rc.conf file and apparently had a typo. Now
the system boots into single user mode. I know what my error is
syslogd_enable=YES {left off the first }
How can I edit rc.conf while in single user mode. I've tried vi ee,
but system doesn't recognize either.
You can mount /usr (assuming that's not related to whatever you're trying to
fix) by typing mount /usr. You'll also need to mount / read/write before
you can modify rc.conf so I usually just do mount -a. mount / will
re-mount / with the default r/w settings.
If you do have a problem with /usr, there are statically linked versions of
both system default editors in /rescue. So you could also
do /rescue/ee /etc/rc.conf, for example.
JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rc.conf ...need help
Don Munyak [EMAIL PROTECTED] writes:
I was tweaking the /etc/rc.conf file and apparently had a typo. Now
the system boots into single user mode. I know what my error is
syslogd_enable=YES {left off the first }
How can I edit rc.conf while in single user mode. I've tried vi ee,
but system doesn't recognize either.
I made a mistake in rc.conf, or another startup file, and now I
cannot edit it because the filesystem is read-only. What should I do?
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#RCCONF-READONLY
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rc.conf ...need help
On Tue, Feb 06, 2007 at 03:58:06PM -0500, Don Munyak wrote:
Hello,
I was tweaking the /etc/rc.conf file and apparently had a typo. Now
the system boots into single user mode. I know what my error is
syslogd_enable=YES {left off the first }
How can I edit rc.conf while in single user mode. I've tried vi ee,
but system doesn't recognize either.
It is probably not in your limited path in single user or not
in a mounted partition.
You may have to mount the partition containing 'vi', probably /usr.
While in single user, do:
fsck -p
mount -u /
mount -a
swapon -a
Then you should be able to use vi as:
/usr/bin/vi /etc/rc.conf
using the full path for vi skips over putting it in your path.
Make your fix and reboot.
jerry
Thanks
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rc.conf ...need help
On 06/02/07, Jerry McAllister [EMAIL PROTECTED] wrote: On Tue, Feb 06, 2007 at 03:58:06PM -0500, Don Munyak wrote: How can I edit rc.conf while in single user mode. I've tried vi ee, but system doesn't recognize either. It is probably not in your limited path in single user or not in a mounted partition. You may have to mount the partition containing 'vi', probably /usr. While in single user, do: fsck -p mount -u / mount -a swapon -a Then you should be able to use vi as: /usr/bin/vi /etc/rc.conf using the full path for vi skips over putting it in your path. Make your fix and reboot. knowing ed (red or sed) can be a useful skill, as it resides in /bin, thus being useful in other situations (/usr buggered (which I know never hap'ns in real life)) although dealing with / and in sed can be a bit of a chore, practise will not hurt and if it is nothing terrifically important that was mauled (syslogd can be started from the command line, for instance) ^D in single user mode will go ahead and finish the boot to multi- user -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
