Extended "system" attributes within jailed environment dont work
Can someone advise how I can enable extended attributes in a "system" namespace within a jailed (or bhyve) environment? There was no guidance in "man jail" nor "man jail.conf". Simple test >From the host or base system: # touch /a ; setextattr user t1 first /a ; getextattr user t1 /a /a first # touch /a ; setextattr system t2 second /a ; getextattr system t2 /a /a second Within a jail: # touch /a ; setextattr user t1 first /a ; getextattr user t1 /a /a first # touch /a ; setextattr system t2 second /a ; getextattr system t2 /a setextattr: /a: failed: Operation not permitted getextattr: /a: failed: Operation not permitted The impact of this is that SAMBA after 4.3 uses "system" namespace extended attributes; hence can not provision an Active Directory within a jailed environment. (For the inclined, this affects sysvol, and interestingly "rsync -x" is unable to copy extended attributes, so having consistent sysvols across a SAMBA domain may be a challenge) Regards, Dewayne. ___ 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: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice
On Thu, Jul 13, 2017 at 05:06:12PM -0700, Mark Johnston wrote: > On Thu, Jul 13, 2017 at 01:06:30PM +, Glen Barber wrote: > > On Wed, Jul 12, 2017 at 11:29:05PM -0700, jungle boogie wrote: > > > On 07/10/2017 10:48 PM, Konstantin Belousov wrote: > > > > On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote: > > > > > I suspect that this is a result of r320763. That change removed a > > > > > field > > > > > from struct vm_map_entry, which is embedded in struct vm_map. > > > > > Virtualbox > > > > > does not reference the fields of struct vm_map directly, but it does > > > > > call vm_map_pmap(), which is an inline accessor. > > > > > > > > Thank you for noting. I do not consider vm_map part of the guaranteed > > > > stable KBI, but in this case it is simpler to add padding than to follow > > > > principles. > > > > > > > > Fixed in 320889, will ask re for MFS permissions in a day. > > > > > > I think this is the commit: > > > https://svnweb.freebsd.org/base/stable/11/sys/vm/vm_map.h?view=log&pathrev=320889 > > > > > > Do you think this will get picked up by/for RC3, which will begin on > > > Friday? > > > https://www.freebsd.org/releases/11.1R/schedule.html > > > > > > > Yes, it will be in RC3. It was committed to releng/11.1 as r320909. > > It should be noted that anyone that recompiled virtualbox for RC2 will > need to do so again after updating to RC3. Anyone going straight from > RC1 or earlier to RC3 ought to be unaffected. > Thank you for mentioning this. I would have forgotten to include this in the RC3 and RELEASE announcement text. I'll make a note of it right now... Glen signature.asc Description: PGP signature
Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice
On Thu, Jul 13, 2017 at 01:06:30PM +, Glen Barber wrote: > On Wed, Jul 12, 2017 at 11:29:05PM -0700, jungle boogie wrote: > > On 07/10/2017 10:48 PM, Konstantin Belousov wrote: > > > On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote: > > > > I suspect that this is a result of r320763. That change removed a field > > > > from struct vm_map_entry, which is embedded in struct vm_map. Virtualbox > > > > does not reference the fields of struct vm_map directly, but it does > > > > call vm_map_pmap(), which is an inline accessor. > > > > > > Thank you for noting. I do not consider vm_map part of the guaranteed > > > stable KBI, but in this case it is simpler to add padding than to follow > > > principles. > > > > > > Fixed in 320889, will ask re for MFS permissions in a day. > > > > I think this is the commit: > > https://svnweb.freebsd.org/base/stable/11/sys/vm/vm_map.h?view=log&pathrev=320889 > > > > Do you think this will get picked up by/for RC3, which will begin on Friday? > > https://www.freebsd.org/releases/11.1R/schedule.html > > > > Yes, it will be in RC3. It was committed to releng/11.1 as r320909. It should be noted that anyone that recompiled virtualbox for RC2 will need to do so again after updating to RC3. Anyone going straight from RC1 or earlier to RC3 ought to be unaffected. ___ 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: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice
On Wed, Jul 12, 2017 at 11:29:05PM -0700, jungle boogie wrote: > On 07/10/2017 10:48 PM, Konstantin Belousov wrote: > > On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote: > > > I suspect that this is a result of r320763. That change removed a field > > > from struct vm_map_entry, which is embedded in struct vm_map. Virtualbox > > > does not reference the fields of struct vm_map directly, but it does > > > call vm_map_pmap(), which is an inline accessor. > > > > Thank you for noting. I do not consider vm_map part of the guaranteed > > stable KBI, but in this case it is simpler to add padding than to follow > > principles. > > > > Fixed in 320889, will ask re for MFS permissions in a day. > > I think this is the commit: > https://svnweb.freebsd.org/base/stable/11/sys/vm/vm_map.h?view=log&pathrev=320889 > > Do you think this will get picked up by/for RC3, which will begin on Friday? > https://www.freebsd.org/releases/11.1R/schedule.html > Yes, it will be in RC3. It was committed to releng/11.1 as r320909. Glen signature.asc Description: PGP signature
Re: Any support creating a Windows Server 2012 unattended install
Bezüglich Paul Webster's Nachricht vom 13.07.2017 10:22 (localtime): > Ah ha we can now see installs, perfect thank you harry! just what I > needed I thought we still had no way of seeing the install process You can run anything that provides a UEFIx64 loader with VNC-graphics, due to the ongoing effort of many bhyve developers. Thank goes to them! -Harry ___ 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"
