Re: config(5) break down

[Masao Uebayashi <uebayasi%gmail.com@localhost>]

On Sun, Mar 21, 2010 at 1:43 AM, Matt Thomas <matt%3am-software.com@localhost> 
wrote:
>
> On Mar 20, 2010, at 9:06 AM, Masao Uebayashi wrote:
>
>> On Sun, Mar 21, 2010 at 1:01 AM, Matt Thomas 
>> <matt%3am-software.com@localhost> wrote:
>>> I'm talking about <maj, min> to device.  How, as a user, do I know what 
>>> actual tty does /dev/ttyXX open?
>>
>> If we make tty(4) a device, we can lookup its parent by drvctl(8)
>> (extend it to return dv_parent).
>
> That is user unfriendly.  The name in /dev should tell me enough to know what 
> it is.
> I should not have to invoke another command to figure that out.

You can use scripts and symlinks.

>> My question is - is this the only reason why each serial driver has
>> its own device entry?
>
> It is the primary reason.  And it's a good reason.

I disagree, but this is a matter of taste.

I'm fine if you can outline tty/serial drivers structure and strategy
of MP-safe locking.

Masao