| 1 |
On Mon, Apr 30, 2012 at 11:59:02AM -0400, Mike Frysinger wrote: |
| 2 |
> the fact that the script leaves your system in a hard to recover state is what |
| 3 |
> i'm whining about, not that udev requires devtmpfs. |
| 4 |
|
| 5 |
So why did you decide to whine instead of opening a bug? :p |
| 6 |
|
| 7 |
> /dev/pts isn't created, thus devpts doesn't get mounted, thus you cannot log |
| 8 |
> in to your system to fix it. would also be trivial to run the all of three |
| 9 |
> commands so people could recover: |
| 10 |
> mount -t tmpfs dev /dev |
| 11 |
> busybox mdev -s |
| 12 |
> mkdir /dev/pts |
| 13 |
|
| 14 |
Yes, I could do this. |
| 15 |
|
| 16 |
> we already have examples of the init scripts modifying /etc/issue to notify |
| 17 |
> login entry points that their system needs manual attention to recover. |
| 18 |
|
| 19 |
This part can't happen in the udev init script since / is ro when it is |
| 20 |
run. Doing something in udev-postmount is also eroneous because that |
| 21 |
assumes that the user is booting to the default runlevel which they may |
| 22 |
not be. |
| 23 |
|
| 24 |
The best thing I can think of to do is to just log a message about it in |
| 25 |
udev-mount and fail which will cause udev to fail. |
| 26 |
|
| 27 |
William |
Archives