| To: | Juan Quintela <quintela@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [kernel] char/raw.c devfs support |
| From: | Borsenkow Andrej <Andrej.Borsenkow@xxxxxxxxxxxxxx> |
| Date: | 14 Feb 2002 21:55:34 +0300 |
| Cc: | Richard Gooch <rgooch@xxxxxxxxxxxxxxx>, "'Thierry Vignaud'" <tvignaud@xxxxxxxxxxxxxxxx>, Mandrake kernel list <kernel@xxxxxxxxxxxxxxxx>, "'devfs mailing list'" <devfs@xxxxxxxxxxx>, "'Frederic Lepied'" <flepied@xxxxxxxxxxxxxxxx> |
| In-reply-to: | <m2d6z8q6lt.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <000601c1b56b$241be2e0$21c9ca95@xxxxxxxxxxxxxx> <m2lmdwq7q2.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx> <200202141750.g1EHo2G12220@xxxxxxxxxxxxxxxxxxxxxxxx> <m2d6z8q6lt.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-devfs@xxxxxxxxxxx |
On Чтв, 2002-02-14 at 21:08, Juan Quintela wrote: > > Other thing that is perhaps a bug in our setup is that we are storing > /dev/log in /lib/dev-state, and probably we shouldn't(this was Andrej > discovery), but that is a different story, i.e. I think that: > No it won't help if I understand how initlog/minilogd are working. If they use /dev/log (and string shows /dev/log as available) then when devfsd is started /dev/log has already been created. It is trivial to prevent restoring it - just do ^log$ IGNORE - but I am not sure if it really helps. The main problem being I still do not know how to reliably reproduce it. -andrej |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: modprobe /dev/*, Richard Gooch |
|---|---|
| Next by Date: | Re: modprobe /dev/*, Russell Coker |
| Previous by Thread: | Re: [kernel] char/raw.c devfs support, Juan Quintela |
| Next by Thread: | Re: [kernel] char/raw.c devfs support, Richard Gooch |
| Indexes: | [Date] [Thread] [Top] [All Lists] |