Jenkins build is still unstable: FreeBSD_stable_10 #431

2016-10-18 Thread jenkins-admin 
https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/431/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: make buildwotrld can not find zlib,h

2016-10-18 Thread Kevin Oberman 
On Tue, Oct 18, 2016 at 12:10 AM, Schaich Alonso 
wrote:

> On Fri, 14 Oct 2016 11:06:55 -0700
> Kevin Oberman  wrote:
>
> > On Fri, Oct 14, 2016 at 6:10 AM, Dmitry Luhtionov <
> dmitryluhtio...@gmail.com
> > > wrote:
> >
> > > c++  -O2 -pipe
> > > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include
> > > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/
> > > include
> > > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support
> -I.
> > > -I/usr/src/lib/clang/libllvmsupport/../../../
> contrib/llvm/../../lib/clang/
> > > include
> > > -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS
> > > -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing
> > > -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd11.0\"
> > > -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd11.0\"
> > > -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/tmp\" -MD
> -MF.depend.Compression.o
> > > -MTCompression.o -Qunused-arguments
> > > -I/usr/obj/usr/src/tmp/legacy/usr/include  -std=c++11 -fno-exceptions
> > > -fno-rtti -stdlib=libc++ -Wno-c++11-extensions  -c
> > > /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/
> > > Compression.cpp
> > > -o Compression.o
> > > /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/
> > > Compression.cpp:21:10:
> > > fatal error: 'zlib.h' file not found
> > > #include 
> > >  ^
> > > 1 error generated.
> > >
> >
> > Very odd. /usr/include/zlib.h is and long has been a standard component
> of
> > FreeBSD and should be present on your system. Can you confirm its
> absence?
> > Anything that could be in /etc/src.conf that might trigger this? (I can't
> > see anything obvious, but src.conf(5) is very long.)
> >
> > I'm also not sure whether, at this point in the build, you should be
> using
> > the system's include files or those in /usr/obj/usr/src/tmp/usr/include/
> or
> > /usr/src/lib/libz/zlib.h, which is what should be copied to
> > /usr/obj/usr/src/tmp/usr/include. Normally the system's files are not
> used
> > during the build.
> >
> > Have you tried completely removing /usr/obj (rm -r /usr/obj/*) before
> > starting the build with -DNO_CLEAN?
> > --
> > Kevin Oberman, Part time kid herder and retired Network Engineer
> > E-mail: rkober...@gmail.com
> > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
>
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
> Hi,
>
> I'm having an issue with libarchive that might or might not be related:
>
> > [...]
> > (cd /usr/src/lib/libarchive/tests &&  DEPENDFILE=.depend.libarchive_test
> NO_SUBDIR=1 make -f /usr/src/lib/libarchive/tests/Makefile
> _RECURSING_PROGS=t  PROG=libarchive_test )
> > cc -O2 -pipe -I/usr/src/lib/libarchive 
> > -I/usr/obj/usr/src/lib/libarchive/tests
> -I/usr/src/contrib/libarchive/libarchive 
> -I/usr/src/contrib/libarchive/test_utils
> -DHAVE_LIBLZMA=1 -DHAVE_LZMA_H=1   -g -MD  -MF.depend.libarchive_test.main.o
> -MTmain.o -std=gnu99 -fstack-protector-strong-Qunused-arguments  -c
> /usr/src/contrib/libarchive/libarchive/test/main.c -o main.o
> > /usr/src/contrib/libarchive/libarchive/test/main.c:2400:10: fatal
> error: 'list.h' file not found
> > #include "list.h"
> >  ^
> > 1 error generated.
> > *** Error code 1
> >
> > Stop.
> > make[1]: stopped in /usr/src/lib/libarchive/tests
> > *** Error code 1
> > [...]
>
> list.h is perfectly there, but it's in /usr/src/lib/libarchive/tests
> rather than /usr/obj/usr/src/lib/libarchive/tests (the second -I is
> wrong), so either some copy-to-builddir target was skipped or the build
> process should include the source path instead of the build path.
>
> I removed anything from /usr/obj/ and also commented-away anything I had
> in make.conf and src.conf prior to attempting to compile it (11-STABLE
> r307550).
>
> Alonso
>

You need to look at the output. One pass of the install should copy the new
.h files from /usr/src to /usr/obj/usr/src. Looks like one or more things
did not get copied.

Do you have an /etc/src.conf file? Are any parts of the system being
excluded there? What about /etc/make.conf? Since others have not reported
this, it seems likely that there is something you have configured at some
time.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Repeatable panic on ZFS filesystem (used for backups); 11.0-STABLE

2016-10-18 Thread Karl Denninger 
On 10/17/2016 18:32, Steven Hartland wrote:
>
>
> On 17/10/2016 22:50, Karl Denninger wrote:
>> I will make some effort on the sandbox machine to see if I can come up
>> with a way to replicate this.  I do have plenty of spare larger drives
>> laying around that used to be in service and were obsolesced due to
>> capacity -- but what I don't know if whether the system will misbehave
>> if the source is all spinning rust.
>>
>> In other words:
>>
>> 1. Root filesystem is mirrored spinning rust (production is mirrored
>> SSDs)
>>
>> 2. Backup is mirrored spinning rust (of approx the same size)
>>
>> 3. Set up auto-snapshot exactly as the production system has now (which
>> the sandbox is NOT since I don't care about incremental recovery on that
>> machine; it's a sandbox!)
>>
>> 4. Run a bunch of build-somethings (e.g. buildworlds, cross-build for
>> the Pi2s I have here, etc) to generate a LOT of filesystem entropy
>> across lots of snapshots.
>>
>> 5. Back that up.
>>
>> 6. Export the backup pool.
>>
>> 7. Re-import it and "zfs destroy -r" the backup filesystem.
>>
>> That is what got me in a reboot loop after the *first* panic; I was
>> simply going to destroy the backup filesystem and re-run the backup, but
>> as soon as I issued that zfs destroy the machine panic'd and as soon as
>> I re-attached it after a reboot it panic'd again.  Repeat until I set
>> trim=0.
>>
>> But... if I CAN replicate it that still shouldn't be happening, and the
>> system should *certainly* survive attempting to TRIM on a vdev that
>> doesn't support TRIMs, even if the removal is for a large amount of
>> space and/or files on the target, without blowing up.
>>
>> BTW I bet it isn't that rare -- if you're taking timed snapshots on an
>> active filesystem (with lots of entropy) and then make the mistake of
>> trying to remove those snapshots (as is the case with a zfs destroy -r
>> or a zfs recv of an incremental copy that attempts to sync against a
>> source) on a pool that has been imported before the system realizes that
>> TRIM is unavailable on those vdevs.
>>
>> Noting this:
>>
>>  Yes need to find some time to have a look at it, but given how rare
>>  this is and with TRIM being re-implemented upstream in a totally
>>  different manor I'm reticent to spend any real time on it.
>>
>> What's in-process in this regard, if you happen to have a reference?
> Looks like it may be still in review: https://reviews.csiden.org/r/263/
>
>
Initial attempts to provoke the panic has failed on the sandbox machine
-- it appears that I need a materially-fragmented backup volume (which
makes sense, as that would greatly increase the number of TRIM's queued.)

Running a bunch of builds with snapshots taken between generates a
metric ton of entropy in the filesystem, but it appears that the number
of TRIMs actually issued when you bulk-remove them (with zfs destroy -r)
is small enough to not cause it -- probably because the system issues
one per area of freed disk, and since there is no interleaving with
other (non-removed) data that number is "reasonable" since there's
little fragmentation of that free space.

The TRIMs *are* attempted, and they *do* fail, however.

I'm running with the 6 pages of kstack now on the production machine,
and we'll see if I get another panic...

-- 
Karl Denninger
k...@denninger.net 
/The Market Ticker/
/[S/MIME encrypted email preferred]/


smime.p7s
Description: S/MIME Cryptographic Signature

VT not showing cyrillic characters in text mode

2016-10-18 Thread lexa guskov via freebsd-stable 

Hello everyone. 

Cannot figure out if vt console driver supports non-ansi characters when 
started in textmode. The font in sys/dev/vt/vt_font_default.c seem to include 
cyrillic glyphs, but either it is not being used in textmode or something else 
is broken since only '?' are displayed instead of proper symbols. The 
LANG/LC_ALL doesnt affect anything. The problem occurs on 11.0-RELEASE and 
10.3-RELEASE.
Textmode is required since vt performance in graphical mode is very poor on 
HyperV and textmode seems to be the only option.

(sorry about the previous messy message in this mailing list, didnt expect 
problems with html emails ;)
-- 
Alexey Guskov
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

VT not showing cyrillic characters in text mode

2016-10-18 Thread lexa guskov via freebsd-stable 

Hello everyone. 

Cannot figure out if vt console driver supports non-ansi characters when 
started in textmode. The font in sys/dev/vt/vt_font_default.c seem to include 
cyrillic glyphs, but either it is not being used in textmode or something else 
is broken since only '?' are displayed instead of proper symbols. The 
LANG/LC_ALL doesnt affect anything. The problem occurs on 11.0-RELEASE and 
10.3-RELEASE.
Textmode is required since vt performance in graphical mode is very poor on 
HyperV and textmode seems to be the only option.

-- 
Alexey Guskov
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Jenkins build is still unstable: FreeBSD_stable_10 #430

2016-10-18 Thread jenkins-admin 
https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/430/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: I'm upset about FreeBSD

2016-10-18 Thread Ian Smith 
On Mon, 17 Oct 2016 18:52:15 +0200, Yamagi Burmeister wrote:
 > On Mon, 17 Oct 2016 03:44:14 +0300
 > Rostislav Krasny  wrote:
 > 
 > > First of all I faced an old problem that I reported here a year ago:
 > > http://comments.gmane.org/gmane.os.freebsd.stable/96598
 > > Completely new USB flash drive flashed by the
 > > FreeBSD-11.0-RELEASE-i386-mini-memstick.img file kills every Windows
 > > again. If I use the Rufus util to write the img file (using DD mode)
 > > the Windows dies immediately after the flashing. If I use the
 > > Win32DiskImager (suggested by the Handbook) it doesn't reinitialize
 > > the USB storage and Windows dies only if I remove and put that USB
 > > flash drive again or boot Windows when it is connected. Nothing was
 > > done to fix this nasty bug for a year.
 > 
 > As was already said in the other answers this is a bug in Windows.
 > Particulary in the partition parser. partmgr.sys (running in kernel
 > mode) crashes while parsing the FreeBSD installation images GPT
 > setup. This may be a variant of the bug known as "Kindle is crashing
 > Win 10":
 > 
 > http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/plugging-in-kindle-is-crashing-windows-10-after/5db0d867-0822-4512-919e-3d7786353f95?page=1

It's interesting that people primarily oriented to Windows tend to say 
'X crashes my Windows' rather than 'my Windows crashes when X happens', 
so your far more cluey approach is refreshing in this regard ..

 > That bug was patched on september 13 and I'm unable to reproduce the
 > crash on a fully patched Win 10 VM. But there's no patch for Win 7,
 > even with all patches applied my Win 7 VM is still crashing as soon
 > as the FreeBSD installation image is connected.

Amazing; what we'd call a kernel panic due to merely inserting a device.

 > I did some debugging and I'm pretty sure that the problem is not the
 > pmbr used for classic BIOS boot but the GPT itself. But my knowledge
 > of GPT and especially Windows internals is limit. So maybe someone 
 > with more insight can look into this. 

If FreeBSD GPT images (and Kindle readers) can trigger this, so could a 
theoretically unlimited combination of data on block 2 of USB media; 
modifying FreeBSD to fix a Windows bug should be out of the question.

 > Or even better: Complain to Microsoft. Even if the GPT is invalid it
 > should crash the kernel.

Well, exactly so, given s/should/should not/ .. and they'll have at 
least three images to test against: 10.3 (i386 only) and 11.0 (amd64 
and i386) apart from the Kindles; should be a clue or two in there ..

cheers, Ian
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Repeatable panic on ZFS filesystem (used for backups); 11.0-STABLE

2016-10-18 Thread Andriy Gapon 
On 18/10/2016 00:43, Steven Hartland wrote:
> On 17/10/2016 20:52, Andriy Gapon wrote:
>> On 17/10/2016 21:54, Steven Hartland wrote:
>>> You're hitting stack exhaustion, have you tried increasing the kernel stack 
>>> pages?
>>> It can be changed from /boot/loader.conf
>>> kern.kstack_pages="6"
>>>
>>> Default on amd64 is 4 IIRC
>> Steve,
>>
>> perhaps you can think of a more proper fix? :-)
>> https://lists.freebsd.org/pipermail/freebsd-stable/2016-July/085047.html
> Yes need to find some time to have a look at it, but given how rare this is 
> and
> with TRIM being re-implemented upstream in a totally different manor I'm
> reticent to spend any real time on it.

Fair enough.  Especially given that there is only a single affected system
reported so far.

-- 
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: I'm upset about FreeBSD

2016-10-18 Thread krad 
NOTE: you can only boot from gpt layout in uefi mode in windows

On 17 October 2016 at 17:52, Yamagi Burmeister  wrote:

> On Mon, 17 Oct 2016 03:44:14 +0300
> Rostislav Krasny  wrote:
>
> > First of all I faced an old problem that I reported here a year ago:
> > http://comments.gmane.org/gmane.os.freebsd.stable/96598
> > Completely new USB flash drive flashed by the
> > FreeBSD-11.0-RELEASE-i386-mini-memstick.img file kills every Windows
> > again. If I use the Rufus util to write the img file (using DD mode)
> > the Windows dies immediately after the flashing. If I use the
> > Win32DiskImager (suggested by the Handbook) it doesn't reinitialize
> > the USB storage and Windows dies only if I remove and put that USB
> > flash drive again or boot Windows when it is connected. Nothing was
> > done to fix this nasty bug for a year.
>
> As was already said in the other answers this is a bug in Windows.
> Particulary in the partition parser. partmgr.sys (running in kernel
> mode) crashes while parsing the FreeBSD installation images GPT
> setup. This may be a variant of the bug known as "Kindle is crashing
> Win 10":
>
> http://answers.microsoft.com/en-us/windows/forum/windows_
> 10-performance/plugging-in-kindle-is-crashing-windows-10-
> after/5db0d867-0822-4512-919e-3d7786353f95?page=1
>
> That bug was patched on september 13 and I'm unable to reproduce the
> crash on a fully patched Win 10 VM. But there's no patch for Win 7,
> even with all patches applied my Win 7 VM is still crashing as soon
> as the FreeBSD installation image is connected.
>
> I did some debugging and I'm pretty sure that the problem is not the
> pmbr used for classic BIOS boot but the GPT itself. But my knowledge
> of GPT and especially Windows internals is limit. So maybe someone
> with more insight can look into this.
>
> Or even better: Complain to Microsoft. Even if the GPT is invalid it
> should crash the kernel.
>
> Regards,
> Yamagi
>
> --
> Homepage:  www.yamagi.org
> XMPP:  yam...@yamagi.org
> GnuPG/GPG: 0xEFBCCBCB
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: make buildwotrld can not find zlib,h

2016-10-18 Thread Schaich Alonso 
On Fri, 14 Oct 2016 11:06:55 -0700
Kevin Oberman  wrote:

> On Fri, Oct 14, 2016 at 6:10 AM, Dmitry Luhtionov  > wrote:
> 
> > c++  -O2 -pipe
> > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include
> > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/
> > include
> > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I.
> > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/
> > include
> > -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS
> > -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing
> > -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd11.0\"
> > -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd11.0\"
> > -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/tmp\" -MD -MF.depend.Compression.o
> > -MTCompression.o -Qunused-arguments
> > -I/usr/obj/usr/src/tmp/legacy/usr/include  -std=c++11 -fno-exceptions
> > -fno-rtti -stdlib=libc++ -Wno-c++11-extensions  -c
> > /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/
> > Compression.cpp
> > -o Compression.o
> > /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/
> > Compression.cpp:21:10:
> > fatal error: 'zlib.h' file not found
> > #include 
> >  ^
> > 1 error generated.
> >
> 
> Very odd. /usr/include/zlib.h is and long has been a standard component of
> FreeBSD and should be present on your system. Can you confirm its absence?
> Anything that could be in /etc/src.conf that might trigger this? (I can't
> see anything obvious, but src.conf(5) is very long.)
> 
> I'm also not sure whether, at this point in the build, you should be using
> the system's include files or those in /usr/obj/usr/src/tmp/usr/include/ or
> /usr/src/lib/libz/zlib.h, which is what should be copied to
> /usr/obj/usr/src/tmp/usr/include. Normally the system's files are not used
> during the build.
> 
> Have you tried completely removing /usr/obj (rm -r /usr/obj/*) before
> starting the build with -DNO_CLEAN?
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Hi,

I'm having an issue with libarchive that might or might not be related:

> [...]
> (cd /usr/src/lib/libarchive/tests &&  DEPENDFILE=.depend.libarchive_test  
> NO_SUBDIR=1 make -f /usr/src/lib/libarchive/tests/Makefile _RECURSING_PROGS=t 
>  PROG=libarchive_test )
> cc -O2 -pipe -I/usr/src/lib/libarchive 
> -I/usr/obj/usr/src/lib/libarchive/tests 
> -I/usr/src/contrib/libarchive/libarchive 
> -I/usr/src/contrib/libarchive/test_utils -DHAVE_LIBLZMA=1 -DHAVE_LZMA_H=1   
> -g -MD  -MF.depend.libarchive_test.main.o -MTmain.o -std=gnu99 
> -fstack-protector-strong-Qunused-arguments  -c 
> /usr/src/contrib/libarchive/libarchive/test/main.c -o main.o
> /usr/src/contrib/libarchive/libarchive/test/main.c:2400:10: fatal error: 
> 'list.h' file not found
> #include "list.h"
>  ^
> 1 error generated.
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /usr/src/lib/libarchive/tests
> *** Error code 1
> [...]

list.h is perfectly there, but it's in /usr/src/lib/libarchive/tests rather 
than /usr/obj/usr/src/lib/libarchive/tests (the second -I is wrong), so either 
some copy-to-builddir target was skipped or the build process should include 
the source path instead of the build path.

I removed anything from /usr/obj/ and also commented-away anything I had in 
make.conf and src.conf prior to attempting to compile it (11-STABLE r307550).

Alonso


pgp6cLK2i33NF.pgp
Description: PGP signature

Re: moving ezjail-based jails from 10.3 host to 11.0 host

2016-10-18 Thread KIRIYAMA Kazuhiko 
At Mon, 17 Oct 2016 17:43:25 +0200,
Marko Cupać wrote:
> 
> On Mon, 17 Oct 2016 15:55:07 +0200
> Oliver Peter  wrote:
> 
> > On Mon, Oct 17, 2016 at 03:37:08PM +0200, Marko Cupać wrote:
> > > I have 10.3 host which runs a dozen or so ezjail-based jails. I have
> > > installed another 11.0 host, and I'd like to move jails to it.  
> > 
> > I would switch them to iocage+zfs, ezjail is sooo 90s. :)
> > Have a look at the documentation:
> > http://iocage.readthedocs.io/en/latest/basic-use.html
> > 
> > All jail settings are stored within ZFS properties so an upcoming
> > migration would only need a zfs send | zfs receive.
> > 
> > > Can I just archive jails on 10.3, scp them to 11.0, and re-create
> > > them there by restoring from archive (-a switch)?  
> > 
> > Further I would recommend to use rsync -av instead of scp.
> 
> Oliver,
> 
> I do appreciate you took the time to respond to my question. However,
> when I asked how to move my ezjail-based jails, I meant exactly that.
> I did not ask which is the best jail management system (for my use case
> I'm completely fine with ezjail), or about the good and bad things
> about ZFS (I have hardware RAID controller which can't do JBOD on this
> server), or advantages of rsync over scp (doesn't make much difference
> for one-time transfer of single .tar.gz file over LAN).
> 
> Now, to give answer to my own question: everything works fine, after -
> of course - reinstalling all the packages with `pkg-static upgrade -f'.

Also I've been same worry about this. But ezjail also worked
in 12.0-CURRENT and almost everything stuffs used in that
except below:

(1) `jail_JID_devfs_ruleset' must be specified by number but
  name like

export jail_desktop_devfs_ruleset=11

(2) Additional parameters shoule be specified by
  `jail_JID_parameters' with semicolon separated list like

export jail_desktop_parameters="allow.kmem; allow.sysvipc;"

(3) If you through ICMP packets, set

jail_JID_socket_unixiproute_only="NO"

But now basically FreeBSD does not supprt variable based
specification like ezjail but jail.conf configuration. So
jail spit warning whenever start/restart:

root@kx:~ # service ezjail restart mail
Stopping jails: mail.tfc.
Starting jails: mail.tfc.
/etc/rc.d/jail: WARNING: Per-jail configuration via jail_* variables  is 
obsolete.  Please consider migrating to /etc/jail.conf.
root@kx:~ # 

> 
> Regards,
> -- 
> Before enlightenment - chop wood, draw water.
> After  enlightenment - chop wood, draw water.
> 
> Marko Cupać
> https://www.mimar.rs/
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

---
KIRIYAMA Kazuhiko
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"