On Sun, 2004-01-04 at 02:24, walt wrote: > > > rm -rf /dev/* > > rm -f /dev/.udev.tdb > > /etc/init.d/udev start > > However, after doing the above and recreating a few missing devices > the behavior of the machine seems back to normal, so clearly I did > something that mattered. I don't pretend to understand how or why, > but thanks. Forgot to say in other mail to you - I had weird issues with nodes that was not yet sysfs'ified in the past due to strange permissions (this is now aside those on ptmx). Try rc1-mm1 for misc/vc sysfs support (might be a fluke, but I have not yet had strange going on's since Greg posted them, so maybe it might be /dev/null, etc that caused issues for me, that did it for you as well), or if you roll your own kernels, I will be glad to post you the patches off list if you cannot find them here. -- Martin Schlemmer
Attachment:
signature.asc
Description: This is a digitally signed message part
References:
- Technical udev question for Gregwalt
- Re: Technical udev question for GregGreg KH
- Re: Technical udev question for Gregwalt
- Prev by Date: Re: 2.6.0: atyfb broken
- Next by Date: Re: Badness in local_bh_enable at kernel/softirq.c:121
- Previous by thread: Re: Technical udev question for Greg
- Next by thread: 2.6.1-rc1-mm1 - KGDB fails to breakpoint in Serial Mode
- Indexes:[Main][Thread]