| 1 |
On Fri, Apr 12, 2013 at 1:20 PM, Maxim Kammerer <mk@×××.su> wrote: |
| 2 |
> On Fri, Apr 12, 2013 at 7:22 PM, Mike Frysinger <vapier@g.o> wrote: |
| 3 |
>> i don't know what you mean. if the ebuild detects devpts being mounted and |
| 4 |
>> the mount is incorrect, it will die. if you don't have devpts mounted at all, |
| 5 |
>> then it assumes you know what you're doing. |
| 6 |
> |
| 7 |
> What I am saying is that you make no distinction between build |
| 8 |
> environment and deployment environment. Quite a few users build their |
| 9 |
> Gentoo systems in a chroot. In that case, whole /dev, or its portions |
| 10 |
> (including /dev/pts) can be bind-mounts from the host filesystem, and |
| 11 |
> /dev/pts does not need to have the correct permissions. However, you |
| 12 |
> *would* see such a bind-mount as a devpts mount in /proc/mounts. So |
| 13 |
> why not print a warning — what's the point of dying in pkg_preinst? |
| 14 |
> |
| 15 |
|
| 16 |
Do you have a reason for not having /dev/pts mounted with gid=5 on the |
| 17 |
system hosting the chroot environment? |
| 18 |
|
| 19 |
Calling die is much more likely to save users systems than an ewarn. |
Archives