From: Patrick Wiseman on 5 Dec 2009 14:50 On Sat, Dec 5, 2009 at 2:21 PM, Henrique de Moraes Holschuh <hmh(a)debian.org> wrote: > On Thu, 03 Dec 2009, Jochen Schulz wrote: >> > Now when I try to boot, I get the message "... update kernel or >> > disable CONFIG_SYSFS_DEPECATED...". >> >> This should be negligible. > > It is not. It will likely hang the box during boot as stuff wait for udev > to create nodes that never show up. > > I don't know if it will eventually timeout, but if it will, it will take a > _long_ time. [Apologies to Henrique for first replying to him; darn Gmail default!!] Not in my experience. I've been booting with this message for several weeks now, with no observable degradation in boot time. And if it did behave as you predict, "deprecated" is hardly sufficient warning! Patrick -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Henrique de Moraes Holschuh on 5 Dec 2009 15:30 On Sat, 05 Dec 2009, Patrick Wiseman wrote: > On Sat, Dec 5, 2009 at 2:21 PM, Henrique de Moraes Holschuh > <hmh(a)debian.org> wrote: > > On Thu, 03 Dec 2009, Jochen Schulz wrote: > >> > Now when I try to boot, I get the message "... update kernel or > >> > disable CONFIG_SYSFS_DEPECATED...". > >> > >> This should be negligible. > > > > It is not. �It will likely hang the box during boot as stuff wait for udev > > to create nodes that never show up. > > > > I don't know if it will eventually timeout, but if it will, it will take a > > _long_ time. > > [Apologies to Henrique for first replying to him; darn Gmail default!!] > > Not in my experience. I've been booting with this message for several > weeks now, with no observable degradation in boot time. And if it did > behave as you predict, "deprecated" is hardly sufficient warning! Well, I should have been far more precise about it. It can hang in "certain configs". It did here, and I needed a live-cd to fix the issue. It could well depend on your arch, kernel config, and set of packages installed, as well as whether you're using an initrd or not. Too bad I didn't have the time to fix or track it, so I used a live-cd, downgraded udev to 146-something, got it to boot, fixed things up in the kernel, and it is now working properly. It was not reported to the BTS, since it would justly deserve an "unreproducible needsinfo" set of tags most likely, and I'd have no further info to contribute. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
First
|
Prev
|
Pages: 1 2 3 Prev: Migrating to Grub2 deletes kernel automagic updates and other settings Next: Xorg epilepsy? |