Date: Tue, 6 Nov 2012 10:26:35 +0000 (UTC) From: jb <jb.1234abcd@gmail.com> To: freebsd-stable@freebsd.org Subject: Re: freebsd-update and sources of 9.1-RC3 Message-ID: <loom.20121106T104832-355@post.gmane.org> References: <50952210.7060000@grosbein.net> <loom.20121103T162713-254@post.gmane.org> <50953CD5.7010902@grosbein.net> <loom.20121103T165235-720@post.gmane.org> <50961FF1.9010605@ose.nl> <loom.20121104T111825-994@post.gmane.org> <509649B3.70700@ose.nl> <loom.20121104T120134-513@post.gmane.org> <50965035.8030508@ose.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Bas Smeelen <b.smeelen <at> ose.nl> writes:
> ...
> >> Since freebsd-update is meant to update the system I don't really see a
> >> point to make it install sources (or others things) if they are not
> >> present on the system being updated.
> ...
> > But, you brought up that "StrictComponents yes" option and we have to figure
> > out what it means ...
>
> From looking at the freebsd-update script (it's in /usr/sbin) I
> understand when StrictComponents is set to yes it skips the step,
> inspecting system.... and uses the list provided in freebsd-update.conf,
> so this option might save some time and disk activity.
But then, after I removed /usr/src dir, it re-created it for itself just to
create in there that ../release sub-dir with some documents, which looked
useless to me, not to mention the fact that it attempted to install there some
20 or so other docs, but could not and failed with errors (see my test run
output in earlier post).
So, to me that is already a reason to ask the maintainer to look at it as it
is an important utility.
> I don't fully understand what the impact might be when running a custom
> kernel.
When I had src present (by my download) prior to freebsd-update upgrade,
without custom kernel, without that "override" option ("StrictComponents no"),
I got src updated in various places, in particular the file
/usr/src/sys/conf/newvers.sh, which is OK.
If you had a custom kernel and src present, then src would get updated as
above, and your custom kernel would be gone, but you would be asked to rebuild
your kernel manually. So, it would be convinient for you to have src ready,
by manual download or "override" option ("StrictComponents yes").
> ...
> > # When upgrading between releases, should the list of Components be
> > # read strictly (StrictComponents yes) or merely as a list of components
> > # which *might* be installed of which FreeBSD Update should figure out
> > # which actually are installed and upgrade those (StrictComponents no)?
> > # StrictComponents no
> >
> > The components are:
> > Components src world kernel
> >
> > Then what gives ? Does it not apply to src component ?
When I looked at this "override" option, which is per default disabled, which
is perfectly OK for most users, I understood it as not only saving some time
on verification of current system state, but a real option to request full
update of my system for components specified. This would make e.g. src download
needed first time, but if that is what I wanted, it would be configurable and
make sense for me and other people like the OP who actually expected it.
It would make this utility fully functional, not half-baked like it is right
now.
jb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?loom.20121106T104832-355>