--- Ahmad Arafat Abdullah <[EMAIL PROTECTED]> wrote:
> > > ----- Original Message ----- > > From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > > To: "Daniel Gerzo" <[EMAIL PROTECTED]> > > Subject: Re: rebooting into single user mode on a > remote server > > Date: Sun, 17 Sep 2006 23:49:34 +0200 > > > > > > Daniel Gerzo wrote: > > > Hello pobox, > > > > > > Saturday, September 16, 2006, 8:47:04 PM, you > wrote: > > > > > >> Hello, > > > > > >> could somebody help me to understand the best > way to enter into a single > > >> user mode on a remote server. > > > > > >> I need it for the moment, during rebuilding > world, when I have to reboot > > >> into single user mode before 'mergemaster -p'. > > > > > > I don't want to persuade you to something that > is not officially > > > supported, but I have never booted into single > user mode while > > > upgrading my FreeBSD boxes and I have never > experienced any problems > > > because of this. Just try to skip the reboot > step and go ahead. It > > > works(tm) for me this way. > > > > > > If you are paranoid, try to stop all running > services except the ssh > > > deamon. > > > > Phew... I hear this again and again. > > > > Only I am not sure I have the level of boldness to > do this on a > > production machine. > > > > Isn't the following sequence of steps similar - > 'shutdown -r now' > > (reboots in multi-user mode), and then immediately > 'shutdown now' > > (drops to single user mode)? > > > > Iv. > > > > _______________________________________________ > > email@example.com mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > > > > > > dudes, > > I never tried it, and not dare to try it.. because > it's a remote server and > single mode maybe ( I'm not sure dude ) cut off all > network connections from > inside and outside.. > > anyway for remote servers, i'm prefer make > installwold in normal mode.. it's safer > > > TQ > the best possible only way is to use a serial console via a modem, which could drop out during the update, or a network accessable serial multiplexer. Those are expensive, modems are relatively cheap. Both require a serial console enabled kernel on the server. the only other way would be to have a cheap old box that can be connected to over the network with a null modem between it and the server. you would want this box to be UBER secured because it is a console to the system. There are ways of doing this so that a remote trigger is required to boot this system, but such methods require relays, a soldering iron, and some paranoia to complete. The gist of it is you will need a serial console on the server. Then you need a way to connect this serial line to your remote location. the easiest. cheapest, and least likely to fail is an old 486 or p1. p2 whatever you have lieing around that can be remoted connected to via ssh. if security is a concern you should use a key connection with no passwords. the user on that box doesn't have to be root, but he will need to be able to access the serial ports. then via a communications program available in ports take your pick you connect via a null modem to the server. you can then login and shutdown to single user mode on the server and upgrade to your hearts desires. -brian _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"