Johannes Erdfelt writes:
> On Wed, Apr 19, 2000, Richard Gooch <rgooch@xxxxxxxxxxxxxxx> wrote:
> > Johannes Erdfelt writes:
> > > I'd like to make it flexible enough to track based on vendor/product
> > > and possibly bus topology for those people who wish to use it.
> >
> > Is this perhaps USB-specific? If so, we could leave this to the USB
> > extension for devfsd. This level of flexibility sounds quite complex,
> > and I don't know if there is a generic scheme that could be applied.
> >
> > Also, I don't see the advantage of using a database, rather than just
> > a directory tree. It seems to me that the hard part is in deciding
> > what to store and "where", and in deciding what to extract. That's all
> > policy, and is probably USB specific.
> >
> > The actual mechanisms for storing and extracting permissions would
> > seem to be trivial.
>
> It's all dynamic. I'd rather not rewrite the config file with
> dynamically generated information.
I'm not suggesting that. I'm just saying that I don't know if a
database is better than using a directory tree. In any case, like I
said, it seems the hard part is deciding what to store and where, not
how to actually store something.
> It could be specific to the module, but I suppose other systems will
> have similar issues. Firewire, hot plug PCI, etc.
True. I don't know how similar they will be, though.
> How do we want to handle USB specific options?
Depends on how complex the USB needs are. If the config file isn't
flexible enough, then we can consider new (core) actions for it,
provided they are reasonably generic. Otherwise, they belong in usb.so
instead.
> For instance, the driver database (this is relatively static). The
> location of the device permissions tracking database.
What exactly are these things?
I don't have a clear picture of what you want to do, or what your
vision of USB permissions persistence is, so I'm just groping in the
dark here. It may be easier to talk on the telephone.
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|