1 |
On Tuesday 01 May 2012 12:51:55 William Hubbs wrote: |
2 |
> On Tue, May 01, 2012 at 11:45:01AM -0400, Mike Frysinger wrote: |
3 |
> > On Tuesday 01 May 2012 11:06:42 William Hubbs wrote: |
4 |
> > > On Mon, Apr 30, 2012 at 11:59:02AM -0400, Mike Frysinger wrote: |
5 |
> > > > we already have examples of the init scripts modifying /etc/issue to |
6 |
> > > > notify login entry points that their system needs manual attention to |
7 |
> > > > recover. |
8 |
> > > |
9 |
> > > This part can't happen in the udev init script since / is ro when it is |
10 |
> > > run. Doing something in udev-postmount is also eroneous because that |
11 |
> > > assumes that the user is booting to the default runlevel which they may |
12 |
> > > not be. |
13 |
> > |
14 |
> > in the past, we would `mount -o remount,rw /`, but that was because we |
15 |
> > needed to add missing dirs in /. |
16 |
> |
17 |
> Hmm, if I do that I would also have to put it back ro after I modify |
18 |
> issue because fsck hasn't run yet... |
19 |
> |
20 |
> Do we want to mess around with the fs before fsck is run? |
21 |
|
22 |
the previous cases made sense in context (they had to modify / anyways), so if |
23 |
you wanted to skip that step, it's probably fine. i'm not too worried about |
24 |
fsck as many nowadays recover their journal gracefully at mount time ... |
25 |
-mike |