On Oct 24, 2005, at 11:45 PM, Dimitar Vasilev wrote:
I don't reccommend doing installworld or kernel in multiuser, but
I have never
had any problems doing it on a lightly loaded machine. With that
said what
could bite you is your new kernel not booting or something broken in
userland. You
On 10/24/05, Beecher Rintoul [EMAIL PROTECTED] wrote:
On Monday 24 October 2005 02:24 pm, John DeStefano wrote:
When updating world, section 20.4.5 of the handbook calls for dropping
to single user mode. The reasons given for this make sense. But this
is a problem for me: my BSD server
--- Eric F Crist [EMAIL PROTECTED] wrote:
On Oct 24, 2005, at 11:45 PM, Dimitar Vasilev wrote:
I don't reccommend doing installworld or kernel in multiuser,
but
I have never
had any problems doing it on a lightly loaded machine. With
that
said what
could bite you is your new
If this isn't a production machine, try it. I have been doing
system
updates since 3.4 and not once have I booted into single user mode
to
compile my kernel or userland. I've even done it as recently as
two
weeks ago. I don't have a huge userbase, so my system is pretty
quiet.
When updating world, section 20.4.5 of the handbook calls for dropping
to single user mode. The reasons given for this make sense. But this
is a problem for me: my BSD server does not have a local K/V/M setup
connected directly to it; it sits on my network and I connect to it
via PuTTy for
Is there a way to achieve single-user mode while still being able to
connect remotely (via LAN)? (I know that's something of an oximoron,
but I needed to ask) And if not, am I losing any serious
features/functionality of the update process by _not_ dropping into
single user?
Serial cable
On Monday 24 October 2005 02:24 pm, John DeStefano wrote:
When updating world, section 20.4.5 of the handbook calls for dropping
to single user mode. The reasons given for this make sense. But this
is a problem for me: my BSD server does not have a local K/V/M setup
connected directly to it;
I don't reccommend doing installworld or kernel in multiuser, but I have never
had any problems doing it on a lightly loaded machine. With that said what
could bite you is your new kernel not booting or something broken in
userland. You will then need console access (serial or local) to fix
