Re: Remote upgrade of 4.X-5.3-Stable

[Andriy Tkachuk]

Gentlemen, is this theme for this list?
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Remote upgrade of 4.X-5.3-Stable

[Clifton Royston]

On Thu, Feb 24, 2005 at 12:01:08PM +, [EMAIL PROTECTED] wrote:
> Date: Wed, 23 Feb 2005 17:06:02 +
> From: Wouter van Rooij <[EMAIL PROTECTED]>
> Subject: Remote upgrade of 4.X-5.3-Stable
> To: freebsd-hackers@freebsd.org
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=US-ASCII
> 
> You did a make buildworld?
> You just have to boot in single user mode and run mergemaster -p and
> mergemaster.

  This doesn't work for the remote update case without physical console
access, which he's asking about.  Once the machine comes up in single
user mode, sshd is not running and there's no way to get into it.

  Sorry to belabor the obvious.

  I believe that what's really needed here is to replicate some magic
that is done on the first boot after installing FreeBSD on a system. 
IIRC, there's a special one-time invocation of an rc file - I think
after a quick check of /etc/rc that it's rc.early that I'm thinking of.

  You can put commands in here which are run very early on following
the first automatic boot into multi-user of the system, after all
virtual drives are "assembled" but before filesystems are checked and
mounted.  If all steps of your upgrade script succeed, you can then at
the end have the rc.early file rename itself (so it won't run on the
next boot) sync the root file system, and reboot again.

  Obviously you want to test this very carefully, because in a remote
environment you will probably get just one shot at having it work
correctly; but hopefully this puts you on a workable path.
  -- Clifton

-- 
  Clifton Royston  --  [EMAIL PROTECTED] 
 Tiki Technologies Lead Programmer/Software Architect
"I'm gonna tell my son to grow up pretty as the grass is green
And whip-smart as the English Channel's wide..."
   -- 'Whip-Smart', Liz Phair
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Remote upgrade of 4.X-5.3-Stable

[Wouter van Rooij]

You did a make buildworld?
You just have to boot in single user mode and run mergemaster -p and
mergemaster.
I hope this helped you
Wouter van Rooij
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Remote upgrade of 4.X-5.3-Stable

[Dwayne MacKinnon]

Hi all,
I've been experimenting with upgrading 4.X to 5.3-STABLE. The challenge 
I've been given is that the box to be upgraded is physically 
inaccessible and so there's no console access. All I have to work with 
is ssh and scp.

In our lab I built a box to 5.3-STABLE. I then used the /usr/obj 
directories from that build to start a "remote" upgrade on another lab box.

Things have gone reasonably well. I was able to successfully make 
installworld using a rc.d script even though it reboots into multi-user 
mode after installing the kernel.

The problem is that rc.conf isn't getting sourced properly after the 
installworld. I figure that something more is needed with mergemaster. I 
run mergemaster -ia through my rc.d script, but that's apparently 
insufficient.

So what I'm wondering is this: What do I need in place to make sure that 
networking will come up and sshd will start after upgrading 4.X to 5.3?

Thanks,
DMK
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"