We use jenkins to build, test and release 11.0-CURRENT using jenkin's uid:gid.
Everything works well up to "install -o root -g wheel" in "make release".
Anyone know what the use case is for requiring release to be built as root?
Roger
___
To clarify this proposal a bit better, there are only two flags I think
should be added to pkg to accommodate the usability issues introduced by
base packages and to do so without breaking existing scripts and
aliases:
-b) only display base packages
-B) display both base and third party
Julian Elischer wrote:
I mentioned this before but I think hte answer is to make a change on
the way that "meta packages" are displayed by default in pkg.
I like this suggestion both as it applies to base and third party
packages and agree that the 'leaf' keyword, once documented, will
Nathan Whitehorn wrote:
Thanks, Roger. That seems perfectly reasonable. I'm not sure that goal is
really met by having 800 packages, though, or at least I see no particular
gain relative to a handful (where things like OpenSSL or sendmail would be
discrete things). (Almost) every single
, but they're already
more useful and bugfree than pkgng when it was mandated.
In any case, if I'm not mistaken base packages are entirely optional.
Roger Marquis
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd
. Other operating systems don't do that for
their base packages. Honestly, some of us are wondering what exactly is
behind some of these concerns regarding base packages.
Roger Marquis
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org
Don't know how to debug this and cannot post the Makefile in question but it
last worked in 8.4. In 11-CURRENT Var_Value appears to return NULL at
/usr/src/contrib/bmake/compat.c:621
Var_Set(IMPSRC, Var_Value(TARGET, gn, ), pgn, 0);
which passes the NULL to Var_Set as the second argument
> You don't mkdir it, you create it as a ZFS dataset, and mark it with the
> 'canmount=no' property, so it only exists to be a parent, not as an
> actual dataset. This is the default in zfboot currently.
Thanks to everyone for pointing this out. I'll forget about mkdir then,
ignore the output of
> I no nothing about this script but if you want /usr/local as ZFS
> filesystem, then you need to create parent (/usr in this case) and you
> can use property canmount=off plus different 'mountpoint' (for example
> /mnt/usr) to not mount /usr over existing directory on root filesystem.
Exactly,
Wondering if anyone has example patches for zfsboot (from
usr.sbin/bsdinstall/scripts)?
We're looking to change some of the default zfs subvolumes, removing /usr in
favor of /usr/local in particular, and have run into a "parent does not exist"
issue. It's not clear where in the script the /usr
In FreeBSD, we *do* have a compelling case for installing a small subset of
the base system: service jails (or ?containerised applications? as the kids
are calling them). We want to be able to install, for example, owncloud and
nginx or ejabberd in a jail with only the bare minimum required for
hould assign an IP to the bridge it is
probably
not a good idea, code aside, since bridges are layer 2 devices and IPs are
layer 3.
Haven't seen this issue while testing if_bridge/epair under 11-CURRENT but also
have not been assigning IPs to bridges, only to bridge membe
tps://svn.freebsd.org/base/head ./
Checked out revision 292870.
make cleanworld
make buildworld -DNO_GAMES
Had been seeing the same results on multiple systems, with a couple of
yesterday's and several previous revisions, but as of 292873 it does build
again.
Thanks,
Roger
> To: Roger Marquis
> I don't use cleanworld. That might be a part of the problem. Is /usr/obj on
> tmpfs?
Haven't tried /usr/obj on tmpfs (yet), just ufs and zfs.
Roger
___
freebsd-current@freebsd.org mailing list
Anyone else seeing these buildworld errors?
===> lib/clang/include (install)
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444
/usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/__stddef_max_align_t.h
Forwarding this from freebsd-security in case anyone here can update us
regarding the status of base packaging or has URLs for projects/release-pkg.
Roger
Date: Fri, 18 Dec 2015 14:21:04 -0800 (PST)
To: freebsd-secur...@freebsd.org
Subject: Re: [OpenSSL] /etc/ssl/cert.pem not honoured by
is not more widely
used today is that many sysadmins aren't familiar with it.
Roger Marquis
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-uns
17 matches
Mail list logo
