From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-59613-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id ADE701381F3
for <garchives@archives.gentoo.org>; Fri, 12 Apr 2013 18:54:15 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id DA4A2E09E6;
Fri, 12 Apr 2013 18:54:12 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
(using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id DC297E09DF
for <gentoo-dev@lists.gentoo.org>; Fri, 12 Apr 2013 18:54:11 +0000 (UTC)
Received: from mail-ia0-x22e.google.com (mail-ia0-x22e.google.com [IPv6:2607:f8b0:4001:c02::22e])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
(Authenticated sender: floppym)
by smtp.gentoo.org (Postfix) with ESMTPSA id E3AFB33E52C
for <gentoo-dev@lists.gentoo.org>; Fri, 12 Apr 2013 18:54:10 +0000 (UTC)
Received: by mail-ia0-f174.google.com with SMTP id r13so2632637iar.19
for <gentoo-dev@lists.gentoo.org>; Fri, 12 Apr 2013 11:54:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-received:in-reply-to:references:date:message-id
:subject:from:to:content-type:content-transfer-encoding;
bh=xkU4OnO5p/XiHUFHBJtDvVcUL7ZyfggWbRfrZILxYyc=;
b=ZJOpdk8lKu82rEES5LKu40oorFK879DaRYTHP635yd7G2rhCUaZA6QclY97FDnjT0a
h113/bbyr30DfY0d5gM/tFxCbyawJfm3cLB/CKizzOmvpBAD9ketp4i+h0ogll8yWvYM
7EStCwt0fRFjGEAg6p88ViFb4zQhL9HxgCPC+Y3tkH2M4OddtuOsMfl1tnofaWnvQqwJ
F1cIoVh/vPGCeUVTEwGt7m2nM9L6hCNBcn5Y1kzonFrR0P3Ro437c47Po3DDghfIcjtk
MDtHMYyBgjGUgwhLUjymNuFoAQj79nAXcKrAuIlpKfncsJPhFyVqvF3hUjT5sientahQ
O4VQ==
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
X-Received: by 10.50.107.106 with SMTP id hb10mr2613269igb.25.1365792849418;
Fri, 12 Apr 2013 11:54:09 -0700 (PDT)
Received: by 10.64.102.66 with HTTP; Fri, 12 Apr 2013 11:54:09 -0700 (PDT)
In-Reply-To: <CAHsXYDAUg4X86nA9Ht28O0wsK=V8TVTsk7BjNXLq9DxzFuoLxQ@mail.gmail.com>
References: <201304100115.53431.vapier@gentoo.org>
<CAHsXYDBxFFPemBKVFsn5_zYd=+prKh0u2hger_FZQnoiZ6L7rQ@mail.gmail.com>
<201304121222.36527.vapier@gentoo.org>
<CAHsXYDAUg4X86nA9Ht28O0wsK=V8TVTsk7BjNXLq9DxzFuoLxQ@mail.gmail.com>
Date: Fri, 12 Apr 2013 14:54:09 -0400
Message-ID: <CAJ0EP43eNgDAy-zGgapEGxorZavMTwnSzx7n+oWm4h4XK_yHtQ@mail.gmail.com>
Subject: Re: [gentoo-dev] glibc: pt_chown setuid going away by default
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: c17c3303-6f3f-4247-a03e-4cacc7a63d08
X-Archives-Hash: 304e778506529a223f175706d6f8cb05
On Fri, Apr 12, 2013 at 1:20 PM, Maxim Kammerer <mk@dee.su> wrote:
> On Fri, Apr 12, 2013 at 7:22 PM, Mike Frysinger <vapier@gentoo.org> wrote=
:
>> i don't know what you mean. if the ebuild detects devpts being mounted =
and
>> the mount is incorrect, it will die. if you don't have devpts mounted a=
t all,
>> then it assumes you know what you're doing.
>
> What I am saying is that you make no distinction between build
> environment and deployment environment. Quite a few users build their
> Gentoo systems in a chroot. In that case, whole /dev, or its portions
> (including /dev/pts) can be bind-mounts from the host filesystem, and
> /dev/pts does not need to have the correct permissions. However, you
> *would* see such a bind-mount as a devpts mount in /proc/mounts. So
> why not print a warning =E2=80=94 what's the point of dying in pkg_preins=
t?
>
Do you have a reason for not having /dev/pts mounted with gid=3D5 on the
system hosting the chroot environment?
Calling die is much more likely to save users systems than an ewarn.