Date: Sun, 13 May 2001 10:03:11 -0700 From: "Bryce" <bryce@burnip.net> To: "Hugh Blandford" <hugh@island.net.au>, <stable@freebsd.org> Subject: Re: Running Stable on remote production server Message-ID: <003201c0dbce$b2f069e0$8000000a@ultimate> References: <006c01c0dba7$f21a38c0$0bdea8c0@island.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
To save yourself some time, you can also buildworld, and build the kernel on another machine before hand. Then nfs mount /usr/src, and /usr/obj of that machine from the remote machine, and make install. It's also rather nice to have one central server, with a version of the software you know works. Then as you "upgrade" all your servers, you know they're all running the same code. Regards, Bryce --- bryce@burnip.net ----- Original Message ----- From: "Hugh Blandford" <hugh@island.net.au> To: <stable@freebsd.org> Sent: Sunday, May 13, 2001 5:26 AM Subject: Running Stable on remote production server > Hi All, > > I have been reading the instructions for tracking stable and what is > recommended in the way of procedures. It seems from this that it would be > extremely hard to follow these recommendations for a remote POP. IE moving > to single user mode and on the whole messing with the machine for several > hours at a time. > > I would be very interested in hearing from anyone who is running a 24x7 > server who is tracking stable and how they cope. In my case I haven't seen > one of my servers for over a year. It is in a phone exchange and costs a > fortune to 'visit'. > > Thanks, > > Hugh > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003201c0dbce$b2f069e0$8000000a>