On 2020-03-23 01:44 +0000, Ken Moffat via blfs-dev wrote: > On Mon, Mar 23, 2020 at 09:12:18AM +0800, Xi Ruoyao via blfs-dev wrote: > > On 2020-03-22 21:34 +0000, Ken Moffat via blfs-dev wrote: > > > > > # mount --bind /run /mnt/lfs/run > > > > I think it's dangerous: potentially harmful to the host. Some service > > running > > in the LFS chroot may overwrite the runtime directory of the service running > > on > > the host. > > So, you are saying that packages from mozilla should not now be > built in chroot ?
No. I think we need a better way. > But, what do you mean by a service running in chroot ? I assume we > are specifically talking of systemd here ? Do services not get > started during the boot process ? The systemd instance in chroot > has never started, so I assume it will be ineffective and systemd on > the host will only care about services described in /etc/systemd ? Maybe that's not a issue. But still, /run contains lots of sockets of running services. That means now we can connect host services from the chroot environment. Even if it's not dangerous to host, it's polluting the new LFS system. Consider /run/initctl. We don't want something in chroot to switch the *host* to runlevel 1 :). -- Xi Ruoyao <[email protected]> School of Aerospace Science and Technology, Xidian University -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
