Re: binary updating 6.0-6.2

2007-02-22 Thread Robin Becker

Jerry McAllister wrote:

Hello Robin,

I see from the latest announcement that freebsd-update is now in the base 
system for 6.2. Following the links I see there's a procedure for 6.0-61. 
and another for 6.1-6.2 binary updating.




By the way, I see that your post says binary update, but I really
don't have confidence in that and prefer updating the source
and doing the build as I described in my response.

jerry

no problem, I just replied to that and I almost guessed you might have missed 
the binaryness. My experience of the binary update process is fairly positive, 
but there have been glitches eg my lsof didn't get updated along with a kernel 
and I now see stuff like


lsof: WARNING: compiled for FreeBSD release 6.0-RELEASE; this is 6.0-SECURITY.

when using it. I suppose things like lsof needing to be recompiled are an 
implied dependency and may be hard to find.

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


Re: binary updating 6.0-6.2

2007-02-22 Thread Robin Becker

Jerry McAllister wrote:

On Thu, Feb 22, 2007 at 03:38:18PM +, Robin Becker wrote:


.


What you want to do is a cvsup (Mathew Seaman recently pointed out csup
that is supposed to be part of the system, but I don't seem to have it
on the machine I am presently on running 6.1) so you would have to install
cvsup from ports (/usr/ports/net/cvsup  or  /usr/ports/net/cvsup-without-gui)
if you need it.


You seem to be suggesting just what I wish to avoid ie all the trouble of a 
complete system compile and install with a full ports rebuild. Rather than the 
src build I would prefer a complete dump and iso reinstall.


I looked further into the binary update script and it seems pretty 
comprehensive. I still expect to go through my ports rebuild, but perhaps I 
wouldn't need to copy my files back. Even so I see comments in the 6.0-6.1 
upgrade.sh like


"# XXX For some reason, /usr/lib/liblwres.so had its version bumped.
# XXX Leave behind the old version just in case."

so we end up with some minor cruft left lying about. If the ports need to be 
rebuilt anyhow, I think I prefer to start from scratch.





I just posted a basic rundown on doing this (but with slightly different
numbers) just a couple days ago.   You might want to check the questions
archive.Briefly, you install cvsup (if not already installed); run
the cvsup (or csup if you have it) using a supfile set for
  *default tag=RELENG_6_2
(I will append my working supfile at the end.  It is a simple one)
Then build and install everything.
Do this stuff in a script(1) session to preserve messages and warnings.

  cvsup -g -L 2 /etc/supfile62


...good stuff elided
--
Robin Becker
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: binary updating 6.0-6.2

2007-02-22 Thread Jerry McAllister
On Thu, Feb 22, 2007 at 03:38:18PM +, Robin Becker wrote:

> I see from the latest announcement that freebsd-update is now in the base 
> system for 6.2. Following the links I see there's a procedure for 6.0-61. 
> and another for 6.1-6.2 binary updating.
> 
> In the past I have always dumped all my files and /etc /usr/local/etc done 
> a completely fresh install, reinstalled files and manually hacked any of 
> the modified system files. Then follows a long process of updating the 
> ports tree and rebuilding the ports I need.
> 
> Clearly I will still dump all my files in case anything horrific goes 
> wrong. But can I update 6.0-6.1 6.1-6.2 with a reasonable hope of success.
> 
> The very first step seems the hardest since I have been using 
> freebsd-update already in my 6.0 system and the kernel is no longer a 
> 6.0-RELEASE, but 6.0-SECURITY FreeBSD and a warning in the notes on the 
> 6.1-6.2 update process says I need a GENERIC or SMP kernel. Does the 
> updater know about updates?

What you want to do is a cvsup (Mathew Seaman recently pointed out csup
that is supposed to be part of the system, but I don't seem to have it
on the machine I am presently on running 6.1) so you would have to install
cvsup from ports (/usr/ports/net/cvsup  or  /usr/ports/net/cvsup-without-gui)
if you need it.

I just posted a basic rundown on doing this (but with slightly different
numbers) just a couple days ago.   You might want to check the questions
archive.Briefly, you install cvsup (if not already installed); run
the cvsup (or csup if you have it) using a supfile set for
  *default tag=RELENG_6_2
(I will append my working supfile at the end.  It is a simple one)
Then build and install everything.
Do this stuff in a script(1) session to preserve messages and warnings.

  cvsup -g -L 2 /etc/supfile62
Check out /etc/group  and  /etc/passwd  files to make sure there are
no conflicts or important changes.  Then build stuff.
  cd /usr/src
  make buildworld
Edit/create your kernel config if needed,  Then:
  make buildkernel KERNCONF=GENERIC   (or your own kernel config)
  make installkernel  KERNCONF=GENERIC  (or your own kernel config)
Then reboot to single user.
  fsck -p For good measure
  mount -u /
  mount -a
  swapon -a
  cd /usr/src
  make installworld
Take a look at things to see if everything is OK, especially make sure
you have enough disk space.   Then run mergemaster
  mergemaster -cv

After this, reboot to a running system and check your config files
and other things.   Then install the ports and other stuff you want.  

> 
> Does the updater squirrel away copies of the updated files so a last ditch 
> attempt at status quo restoration can be made?

It preserves some things, but I am not sure all the details.

> 
> Also do my existing ports continue to work with the new kernel?

Probably they need to be reinstalled or updated, or at least rebuilt
with the latest libraries, etc.  It is best to assume so, even though
some might still work fine.

Note that the supfile I show updates both the system and the ports
tree in one swell foop..

Note also, that this should be no problem going from one 'minor' version
level to a couple down the line, within the same 'major' version level
such as  your 6.0 -> 6.2  but I am much less convident crossing 'major' 
version levels such as 5.x -> 6.x and do a complete reinstall for those.

> -- 
> Robin Becker

 --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  
A supfile for going from 6.0 to 6.2.
Note, I keep my supfile in /etc and name it with the OS version which
accounts for the  cvsup -g -L 2 /etc/supfile62  command & arguments as above.
Ports don't have branches in the way the system source does, thus
the line for ports is:ports-all tag=.Same for doc.
 --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  

# $FreeBSD: src/share/examples/cvsup/standard-supfile,v 1.23.4.2.2.1 2006/05/06 
07:41:03 scottl Exp $
#
#   cvsup standard-supfile
#
# If not running X, or invoking cvsup from a non-interactive script, then
# run it as follows:
#
#   cvsup -g -L 2 standard-supfile
#
*default host=cvsup.FreeBSD.org
*default base=/var/db
*default prefix=/usr
*default tag=RELENG_6_2
*default release=cvs 
*default delete use-rel-suffix

*default compress

## Main Source Tree.
# The easiest way to get the main source tree is to use the "src-all"
# mega-collection.  It includes all of the individual "src-*" collections.
src-all

ports-all tag=.

doc-all tag=.


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