| To: | Russell Coker <russell@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: ownership of target of /dev/cdroms/cdroms0 in devfs |
| From: | Richard Gooch <rgooch@xxxxxxxxxxxxxxx> |
| Date: | Sun, 16 Sep 2001 19:53:56 -0400 |
| Cc: | Alex Bowley <alex.bowley@xxxxxxxxxxxxxx>, devfs@xxxxxxxxxxx, debian-user@xxxxxxxxxxxxxxxx |
| In-reply-to: | <20010905203303.A428A34F1F@xxxxxxxxxxxxxxxxx> |
| References: | <20010904171036.B571@xxxxxxxxxxxxxxxxx> <200109041537.f84Fbbu05192@xxxxxxxxxxxxxxxxxxxxxxxx> <20010905203303.A428A34F1F@xxxxxxxxxxxxxxxxx> |
| Sender: | owner-devfs@xxxxxxxxxxx |
Russell Coker writes:
[...]
> Also any permissions related configuration directives in
> /etc/devfs/conf.d/* will over-ride /etc/devfs/perms (so there's no
> real need to comment anything out of /etc/devfs/perms unless you are
> making permissions more restrictive and want to avoid race
> conditions).
What race conditions are you referring to? Filesystem access to
entries is blocked until devfsd has finished processing all pending
events. So no process can ever see an intermediate state. Only devfsd
and it's children can bypass this block.
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: DAC960 and ram disk devfs conflict, Leonard N. Zubkoff |
|---|---|
| Next by Date: | Re: [IDEA] Enhanced trace level system, Richard Gooch |
| Previous by Thread: | Re: ownership of target of /dev/cdroms/cdroms0 in devfs, Russell Coker |
| Next by Thread: | Re: ownership of target of /dev/cdroms/cdroms0 in devfs, Russell Coker |
| Indexes: | [Date] [Thread] [Top] [All Lists] |