Re: Considering stepping down from all of my FreeBSD responsibilities
On Friday, 1 April 2022 at 9:38:07 -0700, Cy Schubert wrote: > In message <20220401064816.gs60...@eureka.lemis.com>, Greg 'groggy' Lehey > write > s: >> >> --TSQPSNmi3T91JED+ >> Content-Type: text/plain; charset=us-ascii >> Content-Disposition: inline >> >> On Friday, 1 April 2022 at 5:58:39 +, Alexey Dokuchaev wrote: >>> I don't think 2.2.10 is warranted. >> >> Agreed. The upgrade isn't sufficiently important. >> >> How about 2.2.9.1? > > I had a different more sinister thought: Announcing that we've moved from > BSDL to GPLv3 to be more like Linux. Well, since we have accepted (or at least put up with) git, why not? Of course, things go both ways. For those of you who missed it, www.lemis.com/grog/slashdot/ And that wasn't even 1 April. Greg -- Sent from my desktop computer. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php signature.asc Description: PGP signature
Re: Considering stepping down from all of my FreeBSD responsibilities
On Fri, Apr 01, 2022 at 06:56:27PM +0200, Patrick M. Hausen wrote: > Hi all, > > > Am 01.04.2022 um 18:38 schrieb Cy Schubert : > > I had a different more sinister thought: Announcing that we've moved from > > BSDL to GPLv3 to be more like Linux. > > Don't we need explicit consent from every contributor for such a major > license change? > Shouldn't we start over from 1.1.5.1 in that case to keep the number of > people lower? > You're joking, right? If so, amusing. If not, check the date... Glen signature.asc Description: PGP signature
Re: Considering stepping down from all of my FreeBSD responsibilities
On Fri, Apr 01, 2022 at 11:42:48AM -0500, Justin Hibbits wrote: > On Fri, 01 Apr 2022 09:38:07 -0700 > Cy Schubert wrote: > > > In message <20220401064816.gs60...@eureka.lemis.com>, Greg 'groggy' > > Lehey write > > s: > > > > > > --TSQPSNmi3T91JED+ > > > Content-Type: text/plain; charset=us-ascii > > > Content-Disposition: inline > > > > > > On Friday, 1 April 2022 at 5:58:39 +, Alexey Dokuchaev wrote: > > > > > > > On Fri, Apr 01, 2022 at 02:20:31PM +0900, Yasuhiro Kimura wrote: > > > >> Hi Glen, > > > >> > > > >> From: Glen Barber > > > >> Subject: Considering stepping down from all of my FreeBSD > > > >> responsibilities Date: Fri, 1 Apr 2022 00:15:02 + > > > >> > > > >>> Dear community, > > > >>> > > > >>> Given the mental toll the past two years or so have taken on > > > >>> me, I have decided to step down from all of my "hats" within > > > >>> the Project, and take some time to sort out what my future > > > >>> looks like going forward. > > > >>> > > > >>> Happy April 1st. I'm not going anywhere. :-) > > > >> > > > >> We are waiting for the announce of FreeBSD 2.2.10-RELEASE. :-) > > > >> > > > >> Cf. > > > >> https://lists.freebsd.org/pipermail/freebsd-announce/2006-April/001055 > > > >> > > > .html > > > > > > > > I don't think 2.2.10 is warranted. > > > > > > Agreed. The upgrade isn't sufficiently important. > > > > > > How about 2.2.9.1? > > > > I had a different more sinister thought: Announcing that we've moved > > from BSDL to GPLv3 to be more like Linux. > > > > > > Take it to the next level. Since we're using git you can make the > license change, do the commit, then send the commit email out, and it > would have the valid hash and all. > I was so very close to doing something similar, but I was more worried about screwing up my local trees. Glen signature.asc Description: PGP signature
Re: Considering stepping down from all of my FreeBSD responsibilities
On Fri, 01 Apr 2022 09:38:07 -0700 Cy Schubert wrote: > In message <20220401064816.gs60...@eureka.lemis.com>, Greg 'groggy' > Lehey write > s: > > > > --TSQPSNmi3T91JED+ > > Content-Type: text/plain; charset=us-ascii > > Content-Disposition: inline > > > > On Friday, 1 April 2022 at 5:58:39 +, Alexey Dokuchaev wrote: > > > > > On Fri, Apr 01, 2022 at 02:20:31PM +0900, Yasuhiro Kimura wrote: > > >> Hi Glen, > > >> > > >> From: Glen Barber > > >> Subject: Considering stepping down from all of my FreeBSD > > >> responsibilities Date: Fri, 1 Apr 2022 00:15:02 + > > >> > > >>> Dear community, > > >>> > > >>> Given the mental toll the past two years or so have taken on > > >>> me, I have decided to step down from all of my "hats" within > > >>> the Project, and take some time to sort out what my future > > >>> looks like going forward. > > >>> > > >>> Happy April 1st. I'm not going anywhere. :-) > > >> > > >> We are waiting for the announce of FreeBSD 2.2.10-RELEASE. :-) > > >> > > >> Cf. > > >> https://lists.freebsd.org/pipermail/freebsd-announce/2006-April/001055 > > >> > > .html > > > > > > I don't think 2.2.10 is warranted. > > > > Agreed. The upgrade isn't sufficiently important. > > > > How about 2.2.9.1? > > I had a different more sinister thought: Announcing that we've moved > from BSDL to GPLv3 to be more like Linux. > > Take it to the next level. Since we're using git you can make the license change, do the commit, then send the commit email out, and it would have the valid hash and all. - Justin
Re: Considering stepping down from all of my FreeBSD responsibilities
In message <20220401064816.gs60...@eureka.lemis.com>, Greg 'groggy' Lehey write s: > > --TSQPSNmi3T91JED+ > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > On Friday, 1 April 2022 at 5:58:39 +, Alexey Dokuchaev wrote: > > On Fri, Apr 01, 2022 at 02:20:31PM +0900, Yasuhiro Kimura wrote: > >> Hi Glen, > >> > >> From: Glen Barber > >> Subject: Considering stepping down from all of my FreeBSD responsibilities > >> Date: Fri, 1 Apr 2022 00:15:02 + > >> > >>> Dear community, > >>> > >>> Given the mental toll the past two years or so have taken on me, I have > >>> decided to step down from all of my "hats" within the Project, and take > >>> some time to sort out what my future looks like going forward. > >>> > >>> Happy April 1st. I'm not going anywhere. :-) > >> > >> We are waiting for the announce of FreeBSD 2.2.10-RELEASE. :-) > >> > >> Cf. https://lists.freebsd.org/pipermail/freebsd-announce/2006-April/001055 > .html > > > > I don't think 2.2.10 is warranted. > > Agreed. The upgrade isn't sufficiently important. > > How about 2.2.9.1? I had a different more sinister thought: Announcing that we've moved from BSDL to GPLv3 to be more like Linux. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few.
Re: CURRENT: can't build 13-STABLE anymore: cp: [vdso]: No such file or directory *** Error
On Fri, 1 Apr 2022 at 12:04, FreeBSD User wrote: > > I tried the patch given at the URL above (Phabricator). Patch applied on > recent CURRENT and > trying to "make installworld" leaves me with this error, see bewlo. What I'm > doing weong here? You're not doing anything wrong, I had another bug in the version of the patch you tried. I've updated Phabricator again, please try again.
Re: CURRENT: can't build 13-STABLE anymore: cp: [vdso]: No such file or directory *** Error
Am Fri, 1 Apr 2022 10:08:11 -0400 Ed Maste schrieb: > On Fri, 1 Apr 2022 at 10:00, Jens Schweikhardt > wrote: > > > > Hello *, > > Looks like a semicolon is missing after the "fi". > > Indeed, and there was a close bracket missing as well. I've put a > (hopefully) fixed version in review at > https://reviews.freebsd.org/D34734. > I tried the patch given at the URL above (Phabricator). Patch applied on recent CURRENT and trying to "make installworld" leaves me with this error, see bewlo. What I'm doing weong here? Kind reagrds, O. Hartmann [...] >>> Install check world -- --- installworld --- mkdir -p /tmp/install.7P7AV5IW4F progs=$(for prog in [ awk cap_mkdb cat chflags chmod chown cmp cp date echo egrep find grep id install ln make mkdir mtree mv pwd_mkdb rm sed services_mkdb sh sort strip sysctl test time true uname wc zic tzsetup makewhatis; do if progpath=`env PATH=/usr/obj/usr/src/amd64.amd64/tmp/bin:/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/libexec::/sbin:/bin:/usr/sbin:/usr/bin which $prog`; then echo $progpath; else echo "Required tool $prog not found in PATH ($PATH)." >&2; exit 1; fi; done); if [ -z "" ] ; then libs=$(ldd -f "%o %p\n" -f "%o %p\n" $progs 2>/dev/null | sort -u | while read line; do $line; if [ "$1" = "[preloaded]" || "$1" = "[vdso]" ]; then continue; fi; if [ "$2 $3" != "not found" ]; then echo $2; else echo "Required library $1 not found." >&2; exit 1; fi; done); fi; cp $libs $progs /tmp/install.7P7AV5IW4F [: missing ] sh: [preloaded]: not found [: missing ] sh: [vdso]: not found [: missing ] sh: libc.so.7: not found [: missing ] sh: libcap_fileargs.so.1: not found [: missing ] sh: libcasper.so.1: not found [: missing ] sh: libedit.so.8: not found [: missing ] sh: libformw.so.6: not found [: missing ] sh: libm.so.5: not found [: missing ] sh: libmd.so.6: not found [: missing ] sh: libncursesw.so.9: not found [: missing ] sh: libnv.so.0: not found [: missing ] sh: libprivatebsddialog.so.0: not found [: missing ] sh: libregex.so.1: not found [: missing ] sh: libthr.so.3: not found [: missing ] sh: libtinfow.so.9: not found [: missing ] sh: libutil.so.9: not found [: missing ] sh: libxo.so.0: not found cp: [vdso]: No such file or directory *** [installworld] Error code 1 make[1]: stopped in /usr/src -- O. Hartmann
Re: CURRENT: can't build 13-STABLE anymore: cp: [vdso]: No such file or directory *** Error
On Fri, Apr 01, 2022 at 05:11:41PM +0200, FreeBSD User wrote: > > Hello, > > it is also impossible to installworld - same error. I'm on FreeBSD > 14.0-CURRENT #134 > main-n253938-4ef6e56ae80: Thu Mar 24 16:11:07 CET 2022 amd64, sources are up > to date as of > now. I think I got this error last time I tried to update a 13.0 jail on main. AFAIR it's caused by a shared version library bump on main. -- Herbert
Re: CURRENT: can't build 13-STABLE anymore: cp: [vdso]: No such file or directory *** Error
Am Fri, 1 Apr 2022 16:00:10 +0200 (CEST) Jens Schweikhardt schrieb: > Hello *, > Looks like a semicolon is missing after the "fi". > Jens > > - Ursprüngliche Mail - > Von: "Ed Maste" > An: "FreeBSD User" > CC: "freebsd-current" > Gesendet: Freitag, 1. April 2022 15:50:31 > Betreff: Re: CURRENT: can't build 13-STABLE anymore: cp: [vdso]: No such file > or directory > *** Error > > On Fri, 1 Apr 2022 at 08:54, FreeBSD User wrote: > > > > On 14.0-CURRENT #134 main-n253938-4ef6e56ae80: Thu Mar 24 16:11:07 CET 2022 > > amd64, it is without any problem possible to build most recent 13-STABLE > > sources as of today (stable/13-n250195-26e8bb3a4e1). > > > > On 14.0-CURRENT #18 main-n254160-4fc5a607fdf: Fri Apr 1 08:30:10 CEST 2022 > > amd64 this is not possible anymore > > Could you give this patch a try? > > diff --git a/Makefile.inc1 b/Makefile.inc1 > index c91034ed42fe..bd58f48a64d2 100644 > --- a/Makefile.inc1 > +++ b/Makefile.inc1 > @@ -1366,6 +1366,9 @@ distributeworld installworld stageworld: > _installcheck_world .PHONY > libs=$$(ldd -f "%o %p\n" -f "%o %p\n" $$progs > 2>/dev/null | sort -u | \ > while read line; do \ > set -- $$line; \ > + if [ "$$1" = "[preloaded]"; then \ > + break; \ > + fi \ > if [ "$$2 $$3" != "not found" ]; then \ > echo $$2; \ > else \ > Hello, it is also impossible to installworld - same error. I'm on FreeBSD 14.0-CURRENT #134 main-n253938-4ef6e56ae80: Thu Mar 24 16:11:07 CET 2022 amd64, sources are up to date as of now. It isn't only an issue with crossbuilding another FreeBSD branch. Kind regards, O. Hartmann -- O. Hartmann
Re: CURRENT: can't build 13-STABLE anymore: cp: [vdso]: No such file or directory *** Error
On Fri, 1 Apr 2022 at 10:00, Jens Schweikhardt wrote: > > Hello *, > Looks like a semicolon is missing after the "fi". Indeed, and there was a close bracket missing as well. I've put a (hopefully) fixed version in review at https://reviews.freebsd.org/D34734.
Re: CURRENT: can't build 13-STABLE anymore: cp: [vdso]: No such file or directory *** Error
Hello *, Looks like a semicolon is missing after the "fi". Jens - Ursprüngliche Mail - Von: "Ed Maste" An: "FreeBSD User" CC: "freebsd-current" Gesendet: Freitag, 1. April 2022 15:50:31 Betreff: Re: CURRENT: can't build 13-STABLE anymore: cp: [vdso]: No such file or directory *** Error On Fri, 1 Apr 2022 at 08:54, FreeBSD User wrote: > > On 14.0-CURRENT #134 main-n253938-4ef6e56ae80: Thu Mar 24 16:11:07 CET 2022 > amd64, it is without any problem possible to build most recent 13-STABLE > sources as of today (stable/13-n250195-26e8bb3a4e1). > > On 14.0-CURRENT #18 main-n254160-4fc5a607fdf: Fri Apr 1 08:30:10 CEST 2022 > amd64 this is not possible anymore Could you give this patch a try? diff --git a/Makefile.inc1 b/Makefile.inc1 index c91034ed42fe..bd58f48a64d2 100644 --- a/Makefile.inc1 +++ b/Makefile.inc1 @@ -1366,6 +1366,9 @@ distributeworld installworld stageworld: _installcheck_world .PHONY libs=$$(ldd -f "%o %p\n" -f "%o %p\n" $$progs 2>/dev/null | sort -u | \ while read line; do \ set -- $$line; \ + if [ "$$1" = "[preloaded]"; then \ + break; \ + fi \ if [ "$$2 $$3" != "not found" ]; then \ echo $$2; \ else \
Re: CURRENT: can't build 13-STABLE anymore: cp: [vdso]: No such file or directory *** Error
On Fri, 1 Apr 2022 at 08:54, FreeBSD User wrote: > > On 14.0-CURRENT #134 main-n253938-4ef6e56ae80: Thu Mar 24 16:11:07 CET 2022 > amd64, it is without any problem possible to build most recent 13-STABLE > sources as of today (stable/13-n250195-26e8bb3a4e1). > > On 14.0-CURRENT #18 main-n254160-4fc5a607fdf: Fri Apr 1 08:30:10 CEST 2022 > amd64 this is not possible anymore Could you give this patch a try? diff --git a/Makefile.inc1 b/Makefile.inc1 index c91034ed42fe..bd58f48a64d2 100644 --- a/Makefile.inc1 +++ b/Makefile.inc1 @@ -1366,6 +1366,9 @@ distributeworld installworld stageworld: _installcheck_world .PHONY libs=$$(ldd -f "%o %p\n" -f "%o %p\n" $$progs 2>/dev/null | sort -u | \ while read line; do \ set -- $$line; \ + if [ "$$1" = "[preloaded]"; then \ + break; \ + fi \ if [ "$$2 $$3" != "not found" ]; then \ echo $$2; \ else \
Re: injecting vars into rc-service-scripts at jail-start?
Quoting Jens Schweikhardt (from Fri, 1 Apr 2022 14:26:27 +0200 (CEST)): Identifier confusion? You use _rc_svcs and _rc_svcj in your description. Typo s/svcs/svcj/ in the explanation. The diff/code has the vars correct (svcj) and the conditional and the setting are close to each other and are "_rc_svcj". Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF pgpMgVvmC6DdY.pgp Description: Digitale PGP-Signatur
CURRENT: can't build 13-STABLE anymore: cp: [vdso]: No such file or directory *** Error
On 14.0-CURRENT #134 main-n253938-4ef6e56ae80: Thu Mar 24 16:11:07 CET 2022 amd64, it is without any problem possible to build most recent 13-STABLE sources as of today (stable/13-n250195-26e8bb3a4e1). On 14.0-CURRENT #18 main-n254160-4fc5a607fdf: Fri Apr 1 08:30:10 CEST 2022 amd64 this is not possible anymore, the build process dies with the error shown below: [...] >>> Install check world -- mkdir -p /tmp/install.l1zhrZWFwP progs=$(for prog in [ awk cap_mkdb cat chflags chmod chown cmp cp date echo egrep find grep id install ln make mkdir mtree mv pwd_mkdb rm sed services_mkdb sh sort strip sysctl test true uname wc zic tzsetup makewhatis; do if progpath=`env PATH=/pool/sources/13-STABLE/obj/pool/sources/13-STABLE/src/amd64.amd64/tmp/bin:/pool/sources/13-STABLE/obj/pool/sources/13-STABLE/src/amd64.amd64/tmp/usr/sbin:/pool/sources/13-STABLE/obj/pool/sources/13-STABLE/src/amd64.amd64/tmp/usr/bin:/pool/sources/13-STABLE/obj/pool/sources/13-STABLE/src/amd64.amd64/tmp/legacy/usr/sbin:/pool/sources/13-STABLE/obj/pool/sources/13-STABLE/src/amd64.amd64/tmp/legacy/usr/bin:/pool/sources/13-STABLE/obj/pool/sources/13-STABLE/src/amd64.amd64/tmp/legacy/bin:/pool/sources/13-STABLE/obj/pool/sources/13-STABLE/src/amd64.amd64/tmp/legacy/usr/libexec::/sbin:/bin:/usr/sbin:/usr/bin which $prog`; then echo $progpath; else echo "Required tool $prog not found in PATH ($PATH)." >&2; exit 1; fi; done); if [ -z "" ] ; then libs=$(ldd -f "%o %p\n" -f "%o %p\n" $progs 2>/dev/null | sort -u | while read line; do set -- $line; if [ "$2 $3" != "not found" ]; then echo $2; else echo "Required library $1 not found." >&2; exit 1; fi; done); fi; cp $libs $progs /tmp/install.l1zhrZWFwP cp: [vdso]: No such file or directory *** Error code 1 Stop. make[5]: stopped in /pool/sources/13-STABLE/src *** Error code 1
Re: injecting vars into rc-service-scripts at jail-start?
Identifier confusion? You use _rc_svcs and _rc_svcj in your description. Jens
injecting vars into rc-service-scripts at jail-start?
Hi,
I'm overlooking something fundamental it seems...
Context:
I'm working on my auto-jailing of services idea: if the auto-jail is
enabled, a service like syslog is started inside a jail (which
inherits the FS and depending on some settings also inherits network
and other stuff or not).
My previous implementation was using _rc_prefix (jailstart) to denote
the start of a service inside a jail so that "service XXX start" on a
host would "service XXX jailstart" inside a jail. This had off course
issues as there is no infrastructure for multiple prefix like
onejailstart or jailonestart...
Problem:
Now I try to find a way to do it without a prefix, and the first thing
which comes to my mind is to do "jail xxx 'exec.start=/usr/bin/env
_rc_svcs=jailing /usr/bin/service XXX CMD ARGS'".
My expectation is, that this would set _rc_svcs=jailing for the
command service XXX CMND args. Having a "set -x" in rc.subr shows
clearly in the jail-console log, that inside that jail, the variable
_rc_svcj is not set. Using "-v" for the env command shows in the log
that it is called and it sets the var and executes the service command
with syslog start as arguments.
I tried to find some env-cleanup part in rc.subr, which would discard
all _rc* variables, but if there is something like that I overlooked it.
For a stop, I call "jexec /usr/bin/env _rc_svcj=jailing
/usr/sbin/service XXX stop args", and it works, so I rather tend to
believe there is no env-cleanup.
What am I doing wrong so that _rc_svcj is not picked up inside the jail?
So here is my diff between "prefix driven" (= working) and "var
driven" (var not picked up inside the jail):
---snip---
case "$rc_arg" in
start)
- if [ "${_rc_prefix}" != jail ]; then
+ if [ "${_rc_svcj}" != jailing ]; then
_return=1
$JAIL_CMD -c
$_svcj_generic_params $_svcj_cmd_options \
-
exec.start="/usr/sbin/service ${name} jailstart $rc_extra_args" \
-
exec.stop="/usr/sbin/service ${name} jailstop $rc_extra_args" \
+
exec.start="/usr/bin/env _rc_svcj=jailing /usr/sbin/service ${name}
${rc_arg} $rc_extra_args" \
+
exec.stop="/usr/bin/env _rc_svcj=jailing /usr/sbin/service ${name}
${rc_arg} $rc_extra_args" \
exec.consolelog="/var/log/svcj_${name}_console.log" \
name=svcj-${name}
&& _return=0
else
# normal start of
_cmd via _run_rc_doit
---snip---
What set -x tells what it calls:
---snip---
+ /usr/sbin/jail -c 'path=/' mount.nodevfs 'host=inherit'
'ip4=inherit' 'ip6=inherit' allow.reserved_ports
'exec.start=/usr/bin/env -v _rc_svcj=jailing /usr/sbin/service -v
syslogd start ' 'exec.stop=/usr/bin/env _rc_svcj=jailing
/usr/sbin/service syslogd start '
'exec.consolelog=/var/log/svcj_syslogd_console.log' 'name=svcj-syslogd'
---snip---
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
pgpqKaeDPTVSH.pgp
Description: Digitale PGP-Signatur
Re: Considering stepping down from all of my FreeBSD responsibilities
On Friday, 1 April 2022 at 5:58:39 +, Alexey Dokuchaev wrote: > On Fri, Apr 01, 2022 at 02:20:31PM +0900, Yasuhiro Kimura wrote: >> Hi Glen, >> >> From: Glen Barber >> Subject: Considering stepping down from all of my FreeBSD responsibilities >> Date: Fri, 1 Apr 2022 00:15:02 + >> >>> Dear community, >>> >>> Given the mental toll the past two years or so have taken on me, I have >>> decided to step down from all of my "hats" within the Project, and take >>> some time to sort out what my future looks like going forward. >>> >>> Happy April 1st. I'm not going anywhere. :-) >> >> We are waiting for the announce of FreeBSD 2.2.10-RELEASE. :-) >> >> Cf. >> https://lists.freebsd.org/pipermail/freebsd-announce/2006-April/001055.html > > I don't think 2.2.10 is warranted. Agreed. The upgrade isn't sufficiently important. How about 2.2.9.1? Greg -- Sent from my desktop computer. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php signature.asc Description: PGP signature
Re: Considering stepping down from all of my FreeBSD responsibilities
On Fri, Apr 01, 2022 at 02:20:31PM +0900, Yasuhiro Kimura wrote: > Hi Glen, > > From: Glen Barber > Subject: Considering stepping down from all of my FreeBSD responsibilities > Date: Fri, 1 Apr 2022 00:15:02 + > > > Dear community, > > > > Given the mental toll the past two years or so have taken on me, I have > > decided to step down from all of my "hats" within the Project, and take > > some time to sort out what my future looks like going forward. > > > > Happy April 1st. I'm not going anywhere. :-) > > We are waiting for the announce of FreeBSD 2.2.10-RELEASE. :-) > > Cf. > https://lists.freebsd.org/pipermail/freebsd-announce/2006-April/001055.html I don't think 2.2.10 is warranted. 2.2.9 (or was it 2.2.8?) had improved Quake II support in Linuxolator, but since then we've got several native ports available in our collection which play just fine (modulo the problems caused by that shitty linuxish graphics stack we're confined to these days). ./danfe
