I agree that a more flexible approach is generally better, but since
it's not necessary I don't want to create an extra entry in my
/etc/usbd.conf (one more file to worry about during mergemaster).
Thus I think the best solution would be to dump devfs.conf and
/etc/rc.d/devfs entirely (or leave it optional for backwards
compatibility) and give devfs the ability to create links.
I have a dislike for inconsistent solutions and I think most people here
share this dislike. It's just what happens when software grows. Sooner
or later you get to the point where you should throw away 80% of what's
there and turn the rest into something that does what needs to be done.
Johny Mattsson wrote:
> Note that while for you it might be sufficient to have a hard coded link
> from /dev/pilot to /dev/ttyU0, that is not necessarily the case if you
> have multiple USB serial gadgets.
> The way I handled it is by using an entry in /etc/usbd.conf:
>
> #
> # Fixup permissions for Palm Handheld ucom devices
> # (set here and not in devfs.rules since we only want to apply
> # the change to Palm com ports, not all USB com ports)
> device "PalmHandheld"
> devname "ucom[0-9]+"
> vendor 0x0830
> attach "/bin/chmod 0666 /dev/${DEVNAME} ; /bin/ln -s
> /dev/${DEVNAME} /dev/pilot"
> detach "rm -f /dev/pilot
>
>
> Having said that, it would be great to be able to create links from
> devfs.rules - I'd certainly use it for my /dev/cdrom entry!
>
> Cheers,
> /Johny
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
