> So far sysctl is only used to configure kernel parameters, so there exists
> one parameter in the system (per kernel).
Not true.. see net.ipv* stuff - for each device, same parameters are to be set.
I see no problem in this.
> An example for devices would be mass storage devices. You may want to switch
> DMA on and off per device. Using one-value-files you would have directories
> called /somepath/0/dma, /somepath/1/dma and so on, and could turn on DMA on
> device 1 by executing "echo 1 > /somepath/1/dma".
Set 1 for dev.ide.host0.bus0.target0.lun0.dma (we should stay consistent at
least with devfs, or we can give it up completely ;)
> Beside that there is the good old problem "who manages the sysctl namespace"
> problem that is even more important if you want to use sysctl for device
> drivers that may not even be in the kernel.
Well, why not maintainers of appropriate kernel sections, or even special
maintainer, like the one for device numbers. For each section of sysctl
namespace, subset of required ctls should be defined, obviously not restricting
optional bloat ;).
--Petr "Pasky" Baudis
UN*X programmer, UN*X administrator, hobbies = IPv6, IRC Real Users hate Real Programmers. Public PGP key, geekcode and stuff: http://pasky.ji.cz/~pasky/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Nov 07 2001 - 21:00:27 EST