public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] To mount or not to Mount proc, that is the question
Date: Fri, 16 Mar 2012 15:40:03 -0600	[thread overview]
Message-ID: <CADPrc80jAGM5_6-+gYuOna8Oj-PGzUFOeBVUEPW5uvp-JOvhXg@mail.gmail.com> (raw)
In-Reply-To: <CAK2H+ecPndY=4q0VwbwyQZOMdSFArkb-+qk542Qamcawginf2g@mail.gmail.com>

On Fri, Mar 16, 2012 at 3:18 PM, Mark Knecht <markknecht@gmail.com> wrote:
> On Fri, Mar 16, 2012 at 12:47 PM, Canek Peláez Valdés <caneko@gmail.com> wrote:
>> On Fri, Mar 16, 2012 at 1:40 PM, Mark Knecht <markknecht@gmail.com> wrote:
> <SNIP>
>>> Looking at the Gentoo amd64 install guide here:
>>>
>>> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8
>>>
>>> it appears that the recommendation is to mount proc.
>>>
>>> [QUOTE]
>>>
>>> /dev/sda1   /boot        ext2    defaults,noatime     1 2
>>> /dev/sda2   none         swap    sw                   0 0
>>> /dev/sda3   /            ext3    noatime              0 1
>>>
>>> /dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0
>>>
>>> proc        /proc        proc    defaults             0 0
>>> shm         /dev/shm     tmpfs   nodev,nosuid,noexec  0 0
>>>
>>> [QUOTE]
> <SNIP>
>>
>> I haven't put /proc explicitly on my /etc/fstab since a long time ago,
>> and everything seems to be working. However, I use systemd, which
>> always mounts /proc with the default options, and only uses the entry
>> in /etc/fstab (if present) to override the default options. In other
>> words, systemd always mounts /proc, no matter if it's listed in
>> /etc/fstab or not.
>>
>> I don't know what OpenRC does, but it would not surprise me that it's
>> something similar.
>>
>> Regards.
>> --
>> Canek Peláez Valdés
>> Posgrado en Ciencia e Ingeniería de la Computación
>> Universidad Nacional Autónoma de México
>>
>
> Thanks Canek. I appreciate your response.
>
> It seems when rereading the link above the authors do put the work
> 'example' in italics, implying that possibly I should know what I'm
> doing and not depend on the text on that page. I'm fine with the not
> depending part. I'm not so sure about the 'know what I'm doing' part.
> ;-)
>
> I'm going to take a wild guess that it's somehow mounted in an init
> script these days but I have no reason to know that's actually how it
> gets done. I did read the kernel docs and it doesn't seem to be done
> automatically by the kernel AFAICT.

No, it's the init system; look at /lib/rc/sh/init.sh:66:

# By default VServer already has /proc mounted, but OpenVZ does not!
# However, some of our users have an old proc image in /proc
# NFC how they managed that, but the end result means we have to test if
# /proc actually works or not. We do this by comparing two reads of
# /proc/self/environ for which we have set the variable VAR to two
# different values. If the comparison comes back equal, we know that
# /proc is not working.
mountproc=true
f=/proc/self/environ
if [ -e $f ]; then
        if [ "$(VAR=a cat $f)" = "$(VAR=b cat $f)" ]; then
                eerror "You have cruft in /proc that should be deleted"
        else
                einfo "/proc is already mounted, skipping"
                mountproc=false
        fi
fi
unset f

if $mountproc; then
        procfs="proc"
        [ "$RC_UNAME" = "GNU/kFreeBSD" ] && proc="linprocfs"
        ebegin "Mounting /proc"
        if ! fstabinfo --mount /proc; then
                mount -n -t "$procfs" -o noexec,nosuid,nodev proc /proc
        fi
        eend $?
fi

Mistery solved :D

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México



  reply	other threads:[~2012-03-16 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 19:40 [gentoo-user] To mount or not to Mount proc, that is the question Mark Knecht
2012-03-16 19:47 ` Canek Peláez Valdés
2012-03-16 21:18   ` Mark Knecht
2012-03-16 21:40     ` Canek Peláez Valdés [this message]
2012-03-16 21:50       ` Mark Knecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADPrc80jAGM5_6-+gYuOna8Oj-PGzUFOeBVUEPW5uvp-JOvhXg@mail.gmail.com \
    --to=caneko@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox