From: "D. Stussy" <spam+newsgroups@bde-arc.ampr.org>
To: linux-kernel@vger.kernel.org
Subject: Mounting /proc w/ kernel 3.4.0 - "uid" parameter no longer valid?
Date: Wed, 23 May 2012 20:08:42 -0700 [thread overview]
Message-ID: <jpk8nr$2f8$1@snarked.org> (raw)
proc: unrecognized mount option "uid=1" or missing value
This works under 3.3.6 and earlier (I never tried 3.3.7). It appears that the
"uid" mount option was removed. WHY? More importantly, where is this change
listed? I didn't see it in the git log.
This is really bad as I rebooted a remotely colocated server and since the
procfs is not mounted, I cannot log in via SSH to correct the problem.
OK, so there's not that much point in changing the UID of the procfs files,
but I preferred to set their default ownership to a non-privileged user.
next reply other threads:[~2012-05-24 3:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 3:08 D. Stussy [this message]
2012-05-24 14:17 ` Mounting /proc w/ kernel 3.4.0 - "uid" parameter no longer valid? Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2012-05-24 19:52 kd6lvw
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='jpk8nr$2f8$1@snarked.org' \
--to=spam+newsgroups@bde-arc.ampr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=replies+newsgroups@kd6lvw.ampr.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