Re: What should do in chrooted environment?

> On 24 Apr 2018, at 23:39, Marc Branchaud wrote: > On 2018-04-24 09:24 AM, Glen Barber wrote: >> There are additional nits regarding jail(8) that chroot(8) does not have >> the same limitations. Setting/unsetting the immutable flag on something >> like /sbin/init, for

Re: What should do in chrooted environment?

On Tue, Apr 24, 2018 at 10:09:40AM -0400, Marc Branchaud wrote: > On 2018-04-24 09:24 AM, Glen Barber wrote: > > There are additional nits regarding jail(8) that chroot(8) does not have > > the same limitations. Setting/unsetting the immutable flag on something > > like /sbin/init, for example,

Re: What should do in chrooted environment?

On 2018-04-24 09:24 AM, Glen Barber wrote: There are additional nits regarding jail(8) that chroot(8) does not have the same limitations. Setting/unsetting the immutable flag on something like /sbin/init, for example, comes to mind. Try allow.chflags in your jail.conf.

Re: What should do in chrooted environment?

There are additional nits regarding jail(8) that chroot(8) does not have the same limitations. Setting/unsetting the immutable flag on something like /sbin/init, for example, comes to mind. Glen On Tue, Apr 24, 2018 at 11:49:46AM +0100, krad wrote: > wouldn't it just be easier to do this in a

Re: What should do in chrooted environment?

wouldn't it just be easier to do this in a jail, and then all of these little bits would be taken care of? On 24 April 2018 at 01:48, O'Connor, Daniel wrote: > > > > On 24 Apr 2018, at 08:14, Glen Barber wrote: > > I think you might not have the devfs

Re: What should do in chrooted environment?

> On 24 Apr 2018, at 08:14, Glen Barber wrote: > I think you might not have the devfs mount in the image. With the paths > provided above, I think this should fix it: > > # mount -t devfs devfs /mnt/dev I wonder if it's worth doing a basic sanity check that /dev/null and

Re: What should do in chrooted environment?

14560423728 83720204 13311869628 1% > /.dake > vms.pis:/ds/src/stable/11.1/r332874 14560423728 83720204 13311869628 1% > /usr/src > vms.pis:/ds/obj/stable/11.1/r332874 14560423728 83720204 13311869628 1% > /usr/obj > admin@tbedfs:~ % su > Password: > root@tbedfs:/usr/home/admin # cd /usr/src/ > root@tbedfs:/usr/src # make buildworld > > > To make buildworld in chrooted environment, what should I do ? > I think you might not have the devfs mount in the image. With the paths provided above, I think this should fix it: # mount -t devfs devfs /mnt/dev Glen signature.asc Description: PGP signature

What should do in chrooted environment?

min # cd /usr/src/ root@tbedfs:/usr/src # make buildworld To make buildworld in chrooted environment, what should I do ? Best regards (*1) Acctually used vm-bhyve port(sysutils/vm-bhyve). [1] http://ds.truefc.org/~kiri/freebsd/stable/dake.log [2] http://ds.truefc.org/~kiri/