Date: Mon, 2 Dec 2002 02:34:41 -0800 (PST) From: Doug Barton <DougB@FreeBSD.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: current@FreeBSD.org Subject: Re: [REPORT] Upgrade from 4.0-RELEASE to 5.0-CURRENT Message-ID: <20021202022719.I7297-100000@master.gorean.org> In-Reply-To: <3DEB2ED8.5764A174@mindspring.com> References: <20021201150303.GA6369@sunbay.com> <20021202011542.H7297-100000@master.gorean.org> <3DEB2ED8.5764A174@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2 Dec 2002, Terry Lambert wrote:
> Doug Barton wrote:
> > On Sun, 1 Dec 2002, Ruslan Ermilov wrote:
> > > I've attempted to overcome 1) as suggested by UPDATING, by running
> > > the ``mergemaster -p'' (from src/usr.sbin/mergemaster/). This did
> > > not work well because mergemaster(8) attempted to use stat(1) which
> > > is not present in 4.0.
> >
> > I'm not sure how to solve this problem non-invasively. One way to deal
> > with it would be to include the instructions to install stat(1) if needed
> > in UPDATING, but then if the upgrade fails for whatever reason, the user
> > would be left with a bogus 5.x stat(1) binary on their system. However,
> > if someone wants to include that step in UPDATING, I have no objection.
>
> What arguments and information did it use? Most of the stuff
> stat(1) outputs can be gotten at another way... e.g. by awk'ing
> 'ls' output, or tar'ing to a tempfile and "tvf"'ing the archive
> to get the information, etc..
I need to find the mode of a file, convert it to octal, and munge the
user's umask value. While there were a lot of complicated solutions
possible, stat(1) makes this quite easy, and since all I had to do was
a minimal port from netbsd, it was the easy way to go; with (arguably)
some nice side effects.
> Makes me want to ask the question: how did you end up with a
> mergemaster(8) that needed stat(1), when the 4.x version of
> mergemaster that you were supposed to have been running uses
> a back-ticked perl command?
The 4.0-vintage mm doesn't have the -p mode to do just the master.passwd
and group files that is needed for 5.0. Thus, UPDATING recommends using mm
to bootstrap that, but RELENG_4 prior to the smmsp user's introduction
upgrading to 5.0 is always going to be a problem for this situation.
Doug
--
"We have known freedom's price. We have shown freedom's power.
And in this great conflict, ... we will see freedom's victory."
- George W. Bush, President of the United States
State of the Union, January 28, 2002
Do YOU Yahoo!?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021202022719.I7297-100000>