Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Jun 2005 11:09:38 -0500
From:      Scot Hetzel <swhetzel@gmail.com>
To:        "Mars G. Miro" <marsgmiro@gmail.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: NFS upgrading from 5.2.1->5.4
Message-ID:  <790a9fff05061409093da406f6@mail.gmail.com>
In-Reply-To: <28edec3c0506140449509acb4c@mail.gmail.com>
References:  <28edec3c0506140449509acb4c@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 6/14/05, Mars G. Miro <marsgmiro@gmail.com> wrote:
> [ resent, as I forgot to add the subject, sorry ]
>=20
> 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  ]
>=20
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

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

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.

Scot



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff05061409093da406f6>