| 1 |
On Wed, 23 Jan 2013 13:10:44 +0200 |
| 2 |
Thanasis <thanasis@××××××××××.org> wrote: |
| 3 |
|
| 4 |
> on 01/23/2013 04:41 AM »Q« wrote the following: |
| 5 |
> > On Sun, 20 Jan 2013 16:57:59 +0000 |
| 6 |
> > Peter Humphrey <peter@××××××××××××××.org> wrote: |
| 7 |
> > |
| 8 |
> >> On Sunday 20 January 2013 08:51:43 Philip Webb wrote: |
| 9 |
> >>> I just tried upgrading to udev-197 , which is supposed to be |
| 10 |
> >>> stable. There were multiple problems & I'm now back with |
| 11 |
> >>> udev-171 . |
| 12 |
> >> |
| 13 |
> >> My daily update pulled in udev-197-r3. The installation went |
| 14 |
> >> smoothly but I decided I ought to reboot to check that I could. I |
| 15 |
> >> couldn't. Udev couldn't start because my kernel config didn't have |
| 16 |
> >> CONFIG_DEVTMPFS=y. So I booted my rescue system on the same disk, |
| 17 |
> >> chrooted in and built a new kernel with that option. On rebooting |
| 18 |
> >> everything was fine. |
| 19 |
> >> |
| 20 |
> >> Just a note for anyone else who may not have that kernel option. |
| 21 |
> > |
| 22 |
> > This got me too. Now there's a discussion in -dev about making |
| 23 |
> > config warnings fatal. |
| 24 |
> > |
| 25 |
> |
| 26 |
> It hit me too, as I hadn't noticed any warning messages..., maybe the |
| 27 |
> messages were added afterwards..., or I was not careful enough... |
| 28 |
|
| 29 |
|
| 30 |
A news item about this is coming down the wire very soon now (aka |
| 31 |
within hours judging by the thread on -dev). |
| 32 |
|
| 33 |
Unfortunately, it's too late for you now but at least many other users |
| 34 |
will see the message before they emerge world and save them some pain |
| 35 |
|
| 36 |
|
| 37 |
-- |
| 38 |
Alan McKinnon |
| 39 |
alan.mckinnon@×××××.com |
Archives