[arch-general] mkarchiso operates poorly with new glibc-2.18 built without pt_chown
Hi. I've encountered the following trouble: 1. Boot the system. devpts has correct mount options and vte terminals work fine: vadim@aquila:~$ mount -t devpts devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) 2. Run mkarchiso init. In my case, it is run from a script: vadim@aquila:/media/stuff/Проекты/Личные/AL/al-iso$ su -c 'bash /media/stuff/Проекты/Личные/AL/al-iso/build.sh -v' mkarchiso init executes command mount -t devpts devpts ${work_dir}/root-image/dev/pts Executing that command seems to drop mount options of /dev/pts, now we have both devpts mount points have the same options: vadim@aquila:~$ mount -t devpts devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000) devpts on /media/stuff/Проекты/Личные/AL/al-iso/work/i686/root-image/dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000) And vte terminals stop to work after that, of course. -- Regards, Vadim Ushakov
Am 15.08.2013 18:00, schrieb Vadim Ushakov:
mkarchiso init executes command mount -t devpts devpts ${work_dir}/root-image/dev/pts Executing that command seems to drop mount options of /dev/pts, now we have both devpts mount points have the same options: vadim@aquila:~$ mount -t devpts
First, this seems like a kernel bug. The old mount point should not be changed in this case - if they necessarily must have the same option, the new mount point should get the options of the existing one. One should either use a --bind mount call or use the 'newinstance' option. The latter brings a few small issues, but those can be worked around.
participants (2)
-
Thomas Bächler
-
Vadim Ushakov