On 10/16/07, Matthias Urlichs <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Paul Alfille:
> > /bus.n/interface/overdrive ?
> > /bus.n/master/overdrive ?
> >
> Either of these would be fine; I'm more partial to "interface" since
> that word doesn't require us to care about whether it's a master/slave
> bus. (Not every user is a hard-core techie. ;-)
>
>
> And no, I don't want to see those files mirrored anywhere else.
> Much too confusing.
>
> This way, it's immediately obvious which bus and therefore which devices
> are affected when we change this "overdrive" value. What would be the
> use case of having that setting available anywhere else?
>
>
This is certainly the easiest scheme to implement.
I suppose the use case against is that for methods that don't allow
wildcards, it's a little tedious to
find all the buses and then query or set them individually.
For owfs (filesystem)
cat /1wire/bus.*/name
(Also works in owftpd)
For owshell:
b=`owdir -s 4304 / | grep bus` ; for n in $b ; do cat $b/name ; done
owhttpd is even worse (although wget may allow wildcards).
Still, the typical use of OWFS should be to ignore the bus.x architecture
and see the full 1-wire
system as a unified whole. Any individual settings should be exceptional. So
individual settings
need to be possible, not convenient.
Paul Alfille
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
