Hi,
as I soon want to start with the userland tool for devfs, I would like
to hear some thoughts on what userland functionality is needed for
devfs.
While my original intentions were to also replace the current devd, I
don't see the need for it, neither do I think it's appropriate as it
for
:2) let the userland tool load a whole set of rules (for each devfs
:mount point) into the kernel. In turn the kernel applies the set of
:rules every time a device is attached. This has several advantages:
:- userland wouldn't have to be asked for every device attach
:- rules would continue to be
Matthew Dillon wrote:
:2) let the userland tool load a whole set of rules (for each devfs
:mount point) into the kernel. In turn the kernel applies the set of
:rules every time a device is attached. This has several advantages:
:- userland wouldn't have to be asked for every device attach
:-
As a matter of fact I only intended to do partial string matching, at
best a few special formatters or so to specify a beginning or end of a
string.
Do we need anything besides that? In my opinion you normally would
want to match them by prefix or device group (ad*, da*, ...) or so, no
need for
:But do you really want to perform regexp/glob matching in the kernel? Or
:do you want to restrict the users to prefix matching?
Yes, it is not a problem. It is not a critical path. But not Regex.
Just simple ?/* wildcarding. Regex is overrated and unnecessarily
complex for what we
:As a matter of fact I only intended to do partial string matching, at
:best a few special formatters or so to specify a beginning or end of a
:string.
:
:Do we need anything besides that? In my opinion you normally would
:want to match them by prefix or device group (ad*, da*, ...) or so, no
