| 1 |
On Monday 30 April 2012 01:28:58 William Hubbs wrote: |
| 2 |
> On Mon, Apr 30, 2012 at 12:48:55AM -0400, Mike Frysinger wrote: |
| 3 |
> > it leaves your system in a hard to recover state because you happened to |
| 4 |
> > forget to check a filesystem option (which ironically isn't under |
| 5 |
> > Filesystems in the kernel). it's piss-poor user facing behavior. |
| 6 |
> |
| 7 |
> Here's the situation. |
| 8 |
|
| 9 |
the fact that the script leaves your system in a hard to recover state is what |
| 10 |
i'm whining about, not that udev requires devtmpfs. |
| 11 |
|
| 12 |
/dev/pts isn't created, thus devpts doesn't get mounted, thus you cannot log |
| 13 |
in to your system to fix it. would also be trivial to run the all of three |
| 14 |
commands so people could recover: |
| 15 |
mount -t tmpfs dev /dev |
| 16 |
busybox mdev -s |
| 17 |
mkdir /dev/pts |
| 18 |
we already have examples of the init scripts modifying /etc/issue to notify |
| 19 |
login entry points that their system needs manual attention to recover. |
| 20 |
-mike |
Archives