Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-27 Thread Bruce Dubbs via blfs-dev
On 3/27/20 12:19 PM, Pierre Labastie via blfs-dev wrote: On Fri, 2020-03-27 at 15:47 +, Ken Moffat via blfs-dev wrote: If you wish to change what is in LFS I'll leave that discussion/decision to those with a better understanding than I have. Agreed, we should have another thread for

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-27 Thread Pierre Labastie via blfs-dev
On Fri, 2020-03-27 at 15:47 +, Ken Moffat via blfs-dev wrote: > On Fri, Mar 27, 2020 at 10:11:20PM +0800, Xi Ruoyao via blfs-dev > wrote: > > [...] > > For me, I do not use my normal script for entering chroot when I'm > building a desktop in chroot. Whenever I do that I've normally done > a

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-27 Thread Ken Moffat via blfs-dev
On Fri, Mar 27, 2020 at 10:11:20PM +0800, Xi Ruoyao via blfs-dev wrote: > On 2020-03-27 11:46 +, Ken Moffat via blfs-dev wrote: > > On Fri, Mar 27, 2020 at 07:03:29AM +0100, Pierre Labastie via blfs-dev > > wrote: > > > Le 27/03/2020 à 00:22, Ken Moffat via blfs-dev a écrit : > > > > On Thu,

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-27 Thread Xi Ruoyao via blfs-dev
On 2020-03-27 11:46 +, Ken Moffat via blfs-dev wrote: > On Fri, Mar 27, 2020 at 07:03:29AM +0100, Pierre Labastie via blfs-dev wrote: > > Le 27/03/2020 à 00:22, Ken Moffat via blfs-dev a écrit : > > > On Thu, Mar 26, 2020 at 10:57:03PM +0100, Pierre Labastie via blfs-dev > > > wrote: > > > >

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-27 Thread Ken Moffat via blfs-dev
On Fri, Mar 27, 2020 at 07:03:29AM +0100, Pierre Labastie via blfs-dev wrote: > Le 27/03/2020 à 00:22, Ken Moffat via blfs-dev a écrit : > > On Thu, Mar 26, 2020 at 10:57:03PM +0100, Pierre Labastie via blfs-dev > > wrote: > > > > (asking about only one item) > >> > >>> > >>> If you do not do

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-27 Thread Pierre Labastie via blfs-dev
Le 27/03/2020 à 00:22, Ken Moffat via blfs-dev a écrit : > On Thu, Mar 26, 2020 at 10:57:03PM +0100, Pierre Labastie via blfs-dev wrote: > > (asking about only one item) >> >>> >>> If you do not do this, configuring will fail with a python traceback >>> report referencing a

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Bruce Dubbs via blfs-dev
On 3/26/20 8:38 PM, Xi Ruoyao via blfs-dev wrote: On 2020-03-26 23:22 +, Ken Moffat via blfs-dev wrote: On Thu, Mar 26, 2020 at 10:57:03PM +0100, Pierre Labastie via blfs-dev wrote: (asking about only one item) If you do not do this, configuring will fail with a python traceback report

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Xi Ruoyao via blfs-dev
On 2020-03-26 23:22 +, Ken Moffat via blfs-dev wrote: > On Thu, Mar 26, 2020 at 10:57:03PM +0100, Pierre Labastie via blfs-dev wrote: > > (asking about only one item) > > > If you do not do this, configuring will fail with a python traceback > > > report referencing a

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Ken Moffat via blfs-dev
On Thu, Mar 26, 2020 at 10:57:03PM +0100, Pierre Labastie via blfs-dev wrote: (asking about only one item) > > > > > If you do not do this, configuring will fail with a python traceback > > report referencing a /usr/lib/pythonN.N/multiprocessing/synchronize.py > > file and ending 'OSError:

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Pierre Labastie via blfs-dev
Le 26/03/2020 à 18:15, Ken Moffat via blfs-dev a écrit : > On Thu, Mar 26, 2020 at 04:51:59PM +, Ken Moffat via blfs-dev wrote: >> On Thu, Mar 26, 2020 at 01:41:40PM +, Ken Moffat via blfs-dev wrote: >> >> [snip how, and what, I tested] >> > > And now the proposal: > > Replace the Note

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Bruce Dubbs via blfs-dev
On 3/26/20 3:29 PM, Pierre Labastie via blfs-dev wrote: Le 26/03/2020 à 21:19, Pierre Labastie via blfs-dev a écrit : Le 26/03/2020 à 18:32, Bruce Dubbs via blfs-dev a écrit : On 3/26/20 10:22 AM, Xi Ruoyao via blfs-dev wrote: Now the book is handling the case "/dev/shm is a link to

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Pierre Labastie via blfs-dev
Le 26/03/2020 à 21:19, Pierre Labastie via blfs-dev a écrit : > Le 26/03/2020 à 18:32, Bruce Dubbs via blfs-dev a écrit : >> On 3/26/20 10:22 AM, Xi Ruoyao via blfs-dev wrote: >> >>> Now the book is handling the case "/dev/shm is a link to /run/shm" correctly >>> and >>> explicitly.  Unfortunately

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Pierre Labastie via blfs-dev
Le 26/03/2020 à 18:32, Bruce Dubbs via blfs-dev a écrit : > On 3/26/20 10:22 AM, Xi Ruoyao via blfs-dev wrote: > >> Now the book is handling the case "/dev/shm is a link to /run/shm" correctly >> and >> explicitly.  Unfortunately it seems for the case "/dev/shm is *not* a link to >> /run/shm" the

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Bruce Dubbs via blfs-dev
On 3/26/20 10:22 AM, Xi Ruoyao via blfs-dev wrote: Now the book is handling the case "/dev/shm is a link to /run/shm" correctly and explicitly. Unfortunately it seems for the case "/dev/shm is *not* a link to /run/shm" the book is defective. I'm surprised that it didn't cause any problem

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Ken Moffat via blfs-dev
On Thu, Mar 26, 2020 at 04:51:59PM +, Ken Moffat via blfs-dev wrote: > On Thu, Mar 26, 2020 at 01:41:40PM +, Ken Moffat via blfs-dev wrote: > > [snip how, and what, I tested] > And now the proposal: Replace the Note about $SHELL and /dev/shm in firefox with a standard copy member. The

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Ken Moffat via blfs-dev
On Thu, Mar 26, 2020 at 01:41:40PM +, Ken Moffat via blfs-dev wrote: [snip who replied to whom] Here is what I did for testing. > I'll reply in a while with what I have now tested (after I've > assembled my notes). I've gone with Bruce's suggestion to (only) > mount a tmpfs on /run when

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Ken Moffat via blfs-dev
On Thu, Mar 26, 2020 at 04:06:46PM +0100, Pierre Labastie via blfs-dev wrote: > Le 26/03/2020 à 14:41, Ken Moffat via blfs-dev a écrit : > > On Thu, Mar 26, 2020 at 11:40:59AM +0100, Pierre Labastie via > > blfs-dev wrote: > >> Le 23/03/2020 à 03:49, Bruce Dubbs via blfs-dev a écrit : > >>> On

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Xi Ruoyao via blfs-dev
On 2020-03-26 16:06 +0100, Pierre Labastie via blfs-dev wrote: > Le 26/03/2020 à 14:41, Ken Moffat via blfs-dev a écrit : > > On Thu, Mar 26, 2020 at 11:40:59AM +0100, Pierre Labastie via > > blfs-dev wrote: > > > Le 23/03/2020 à 03:49, Bruce Dubbs via blfs-dev a écrit : > > > > On 3/22/20 9:25

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Pierre Labastie via blfs-dev
Le 26/03/2020 à 14:41, Ken Moffat via blfs-dev a écrit : > On Thu, Mar 26, 2020 at 11:40:59AM +0100, Pierre Labastie via > blfs-dev wrote: >> Le 23/03/2020 à 03:49, Bruce Dubbs via blfs-dev a écrit : >>> On 3/22/20 9:25 PM, Xi Ruoyao via blfs-dev wrote: On 2020-03-23 01:44 +, Ken Moffat

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Ken Moffat via blfs-dev
On Thu, Mar 26, 2020 at 11:40:59AM +0100, Pierre Labastie via blfs-dev wrote: > Le 23/03/2020 à 03:49, Bruce Dubbs via blfs-dev a écrit : > > On 3/22/20 9:25 PM, Xi Ruoyao via blfs-dev wrote: > >> On 2020-03-23 01:44 +, Ken Moffat via blfs-dev wrote: > >>> On Mon, Mar 23, 2020 at 09:12:18AM

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Xi Ruoyao via blfs-dev
On 2020-03-26 09:41 +0100, Pierre Labastie via blfs-dev wrote: > So my suspicion is that when we mount --bind /dev, we lose some permissions, > and those permissions are needed for FF. I'll have to try again without > /run/shm The problem is /dev/shm is a seperated tmpfs, instead of a normal

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Pierre Labastie via blfs-dev
Le 23/03/2020 à 03:49, Bruce Dubbs via blfs-dev a écrit : > On 3/22/20 9:25 PM, Xi Ruoyao via blfs-dev wrote: >> On 2020-03-23 01:44 +, 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 +, Ken Moffat via

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-26 Thread Pierre Labastie via blfs-dev
Le 23/03/2020 à 15:29, Ken Moffat via blfs-dev a écrit : > On Sun, Mar 22, 2020 at 09:49:02PM -0500, Bruce Dubbs via blfs-dev wrote: >> On 3/22/20 9:25 PM, Xi Ruoyao via blfs-dev wrote: >>> On 2020-03-23 01:44 +, Ken Moffat via blfs-dev wrote: On Mon, Mar 23, 2020 at 09:12:18AM +0800, Xi

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-23 Thread Ken Moffat via blfs-dev
On Sun, Mar 22, 2020 at 09:49:02PM -0500, Bruce Dubbs via blfs-dev wrote: > On 3/22/20 9:25 PM, Xi Ruoyao via blfs-dev wrote: > > On 2020-03-23 01:44 +, 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

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-22 Thread Bruce Dubbs via blfs-dev
On 3/22/20 9:25 PM, Xi Ruoyao via blfs-dev wrote: On 2020-03-23 01:44 +, 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 +, Ken Moffat via blfs-dev wrote: # mount --bind /run /mnt/lfs/run I think it's

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-22 Thread Xi Ruoyao via blfs-dev
On 2020-03-23 01:44 +, 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 +, Ken Moffat via blfs-dev wrote: > > > > > # mount --bind /run /mnt/lfs/run > > > > I think it's dangerous: potentially harmful to the

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-22 Thread Ken Moffat via blfs-dev
On Mon, Mar 23, 2020 at 09:12:18AM +0800, Xi Ruoyao via blfs-dev wrote: > On 2020-03-22 21:34 +, 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

Re: [blfs-dev] Python multiprocessing checks in chroot

2020-03-22 Thread Xi Ruoyao via blfs-dev
On 2020-03-22 21:34 +, 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. -- Xi Ruoyao School of

[blfs-dev] Python multiprocessing checks in chroot

2020-03-22 Thread Ken Moffat via blfs-dev
This weekend we had a problem where someone was trying to build mozjs60 in chroot and failed. I've seen this myself on some of the rare occasions I've built desktops in chroot. Key facts: 1. The solution is (as root, on the *host* system) bind /mnt/lfs/run to /run, i.e. # mount --bind /run