From: William Hubbs <williamh@gentoo.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] busybox[sep-usr] support for mounting /usr w/out hassle
Date: Tue, 1 May 2012 11:51:55 -0500 [thread overview]
Message-ID: <20120501165155.GA24115@linux1> (raw)
In-Reply-To: <201205011145.02332.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
On Tue, May 01, 2012 at 11:45:01AM -0400, Mike Frysinger wrote:
> On Tuesday 01 May 2012 11:06:42 William Hubbs wrote:
> > On Mon, Apr 30, 2012 at 11:59:02AM -0400, Mike Frysinger wrote:
> > > the fact that the script leaves your system in a hard to recover state is
> > > what i'm whining about, not that udev requires devtmpfs.
> >
> > So why did you decide to whine instead of opening a bug? :p
>
> based on past behavior, i assumed it was operating as indented
>
> > > we already have examples of the init scripts modifying /etc/issue to
> > > notify login entry points that their system needs manual attention to
> > > recover.
> >
> > This part can't happen in the udev init script since / is ro when it is
> > run. Doing something in udev-postmount is also eroneous because that
> > assumes that the user is booting to the default runlevel which they may
> > not be.
>
> in the past, we would `mount -o remount,rw /`, but that was because we needed
> to add missing dirs in /.
Hmm, if I do that I would also have to put it back ro after I modify
issue because fsck hasn't run yet...
Do we want to mess around with the fs before fsck is run?
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-05-01 16:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 2:00 [gentoo-dev] busybox[sep-usr] support for mounting /usr w/out hassle Mike Frysinger
2012-04-30 4:31 ` William Hubbs
2012-04-30 4:48 ` Mike Frysinger
2012-04-30 5:20 ` Luca Barbato
2012-04-30 5:28 ` William Hubbs
2012-04-30 15:59 ` Mike Frysinger
2012-05-01 15:06 ` William Hubbs
2012-05-01 15:45 ` Mike Frysinger
2012-05-01 16:13 ` Mike Frysinger
2012-05-01 17:34 ` [gentoo-dev] " Duncan
2012-05-01 16:51 ` William Hubbs [this message]
2012-05-01 18:52 ` [gentoo-dev] " Mike Frysinger
2012-05-02 4:52 ` Luca Barbato
2012-04-30 6:34 ` Ulrich Mueller
2012-04-30 16:00 ` Mike Frysinger
2012-04-30 16:14 ` Ulrich Mueller
2012-04-30 16:40 ` Mike Frysinger
2012-04-30 16:54 ` Ulrich Mueller
2012-04-30 10:35 ` Maxim Kammerer
2012-04-30 16:03 ` Mike Frysinger
2012-04-30 17:16 ` Maxim Kammerer
2012-04-30 17:32 ` Mike Frysinger
2012-04-30 17:56 ` Maxim Kammerer
2012-05-01 4:18 ` Mike Frysinger
2012-05-01 2:57 ` Walter Dnes
2012-05-01 4:10 ` Mike Frysinger
[not found] <4F9E44D0.70002@linx.net>
2012-04-30 8:05 ` Tony "Chainsaw" Vroon
2012-04-30 16:00 ` Rich Freeman
2012-04-30 20:27 ` William Hubbs
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=20120501165155.GA24115@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=vapier@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