NFS upgrading from 5.2.1->5.4

[Mars G. Miro]

On 6/15/05, Scot Hetzel <swhetzel at gmail.com> wrote:
> On 6/14/05, Mars G. Miro <marsgmiro at gmail.com> wrote:
> > [ resent, as I forgot to add the subject, sorry ]
> > 
> > I've found out that there are some hurdles in doing this upgrade, as
> > also pointed out by another user [0]. The problem is in make and I
> > think it happened during this change [1]. It can be solved by
> > installing the new make first, before the installkernel and
> > installworld process, e.g.:
> >  [ this assumes you've already built world from another box and
> > NFS-exported the /usr/src and /usr/obj directories, and mounting them
> > from the client ]
> >  # cd  /usr/src/usr.bin/make && make install
> >  [ 'rehash' if using csh. then create the pf user/groups, as pf became
> > officially imported in 5.3, refer to src/etc/master.passwd and group
> > files ]
> >  # cd /usr/src && make installkernel && make installworld
> >  [ mergemaster  ]
> > 
> This is commonly found when you do an NFS upgrade when not using
> machines that don't have the same -RELEASE number.
> 
> NFS server/build machine - 5.4-RELEASE
> NFS client/install machine - 5.2.1-RELEASE
> 


I have not tried not doing the upgrade via NFS or building the world
directly on a 5.2.1 installation but it's likely the same case. What
gets built on /usr/obj and NFS exported will be what's installed on
the client, but since it's the 5.2.1 'make' that doesn't understand
some of the new entries on the 5.4R Makefiles that result in this
problem, you'll need to install the new 5.4R make first.


> If the build machine and install machine were at the same -RELEASE
> number, I don't believe you would have come across this problem.
> 


I'm not sure I get you but the purpose of making the world in FreeBSD
is ought to be able to upgrade across releases (some people even
report upgrading from major releases, e.g 4.X to 5.X), albeit minor
hurdles (like the one I've experienced).


> As for the pf user/group, it is suggested in "UPDATING" and the
> handbook, that you do a mergemaster -p before the installworld to
> ensure that the password and group files are upto date with the
> required users/groups.
> 

Yes. mergemaster -p or adding the user/groups directly accomplish the
same thing ;-)


> Scot
> 


cheers
mars