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 13:47:09 -0600	[thread overview]
Message-ID: <CADPrc82-xYTsSfpcWXw2wUtNKNo9ioLD8beCZhMrpsEZVOsXdQ@mail.gmail.com> (raw)
In-Reply-To: <CAK2H+edgjz548NXDEqdKYoyVk_pBKjaP4qY_3Zr50H6U5YxFcQ@mail.gmail.com>

On Fri, Mar 16, 2012 at 1:40 PM, Mark Knecht <markknecht@gmail.com> wrote:
> I've been trying to debug a problem where one laptop's networking, as
> controlled by wicd, seems to randomly go offline once in awhile. In
> the process of reviewing 5 machines I ran across an inconsistency
> across a bunch of my machines, new and old. It seems some of them
> mount proc in fstab while others do not. Some of these machines have
> been around for a few years not mounting proc and except for the
> laptop's networking issues there really haven't been any problems.
>
> 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]
>
>
> What would the issues be with proc not mounted? For instance, this
> machine doesn't mount proc in fstab but still has proc:
>
> laptop1 ~ # cat /etc/fstab
> <SNIP>
> /dev/sdb1               /boot           ext2            noauto,noatime  1 2
> /dev/sdb4               /               ext3            noatime         0 1
> /dev/sdb2               none            swap            sw              0 0
> /dev/cdrom              /mnt/cdrom      auto            noauto,ro       0 0
>
> shm                     /dev/shm        tmpfs
> nodev,nosuid,noexec     0 0
>
>
> laptop1 ~ # cat /proc/mdstat
> Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
> md127 : active (auto-read-only) raid1 sdb3[1] sda3[0]
>      343758245 blocks super 1.2 [2/2] [UU]
>
> unused devices: <none>
> laptop1 ~ #

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



  reply	other threads:[~2012-03-16 19:48 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 [this message]
2012-03-16 21:18   ` Mark Knecht
2012-03-16 21:40     ` Canek Peláez Valdés
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=CADPrc82-xYTsSfpcWXw2wUtNKNo9ioLD8beCZhMrpsEZVOsXdQ@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