From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B460B13877A for ; Fri, 1 Aug 2014 15:29:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7FF06E0999; Fri, 1 Aug 2014 15:29:39 +0000 (UTC) Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5608AE0963 for ; Fri, 1 Aug 2014 15:29:38 +0000 (UTC) Received: by mail-ie0-f181.google.com with SMTP id rp18so6087726iec.40 for ; Fri, 01 Aug 2014 08:29:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=cd6Y+rn5/9BYjKxS31JT1iIBlDQjM9o236j2NMydP5E=; b=pwi62oa1nlPRkEtemvawb9vcw6aUGAZ39iVa5YQCA1KZC7U1Mn0oomMQwuMIzuWOIO tQBqWhClFMOxPwFHa+BxjYd91pXsc0kX9kLMEkmR+KtbTs7dz1z4vq2nyl7tCp1e1UY1 mRDmqXTP1x2whGrmJJuW4Yf1o0nQ30po7Ds2xOLkj/wba/4VrDwD81dG9R+yDCOf34DM CnAVyx82kTOU16JGLlI7DeneiAqlKu2heq67fR79hhfH8+8SpFis6ob7KwSMS79xlbow +iAIU5QhTjejUZPJ4mQDHjtJQj3osBViqL3mHVGDo6oG/Px65gfLSNGim6y1T4pH2Kw6 2Dkg== X-Received: by 10.43.150.193 with SMTP id kp1mr8089513icc.33.1406906977646; Fri, 01 Aug 2014 08:29:37 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.107.12.5 with HTTP; Fri, 1 Aug 2014 08:29:17 -0700 (PDT) In-Reply-To: <2759907.J6mR1A4EQB@wstn> References: <3566559.YT61t9IyHV@wstn> <6536155.f0GWtIUbSO@wstn> <2759907.J6mR1A4EQB@wstn> From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= Date: Fri, 1 Aug 2014 10:29:17 -0500 Message-ID: Subject: Re: [gentoo-user] What to put in chroot mtab To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 27841871-6095-4d19-91ae-b1790aefe38b X-Archives-Hash: e039e0e00c970271ea12da8edddf7c11 On Fri, Aug 1, 2014 at 10:21 AM, Peter Humphrey wro= te: > On Friday 01 August 2014 10:00:40 Canek Pel=C3=A1ez Vald=C3=A9s wrote: > >> ... just for completeness, systemd actually requires /etc/mtab as a >> link to /proc/self/mounts, so don't be surprised if software in the >> future in Linux just assumes that. > > Well, that seems to imply that you can't run a systemd chroot on a system= d or > openrc host, no? If you want to "boot" a container with systemd-nspawn, then no, you can't; you need mtab to be a symlink to /proc/self/mounts. If you simply want to chroot to it, it doesn't matter; you will not be running systemd anyway. > Because from inside the chroot, what /proc/self/mounts lists > is inaccurate. In what sense is inaccurate? Inside my systemd-nspawn container: root@gentoo ~ # sort /etc/mtab | uniq /run /var/run none rw,bind 0 0 debugfs /sys/kernel/debug debugfs rw 0 0 fusectl /sys/fs/fuse/connections fusectl rw 0 0 hugetlbfs /dev/hugepages hugetlbfs rw 0 0 mqueue /dev/mqueue mqueue rw 0 0 tmpfs /tmp tmpfs rw,strictatime,mode=3D1777 0 0 That seems accurate to me. Sure, as Rich mentioned, there are repetitions and other stuff, but nothing that a quick grep or sort will not fix. > I wouldn't like to be the one who has to write a new installation handboo= k for > systemd-only systems! :) We'll need to rewrote the whole thing when we switch to systemd anyway. Regards. --=20 Canek Pel=C3=A1ez Vald=C3=A9s Profesor de asignatura, Facultad de Ciencias Universidad Nacional Aut=C3=B3noma de M=C3=A9xico