[HEADSUP] naming of tty devices.

[Poul-Henning Kamp]

In message <20040920085908.GA43176 at ip.net.ua>, Ruslan Ermilov writes:

>> This results in the following major compatibility issues:
>>
>> 	sio's cuaa* gets renamed to cuad*
>>
>> 	sio's {tty,cua}[il]%d gets renamed to {tty,cua}%d.{init,lock}
>>
>But we now have cuaa0, cuaia0, cuala0, ttyd0, ttyid0, and ttyld0.
>So, shouldn't the above line be instead:
>
>	sio's tty[il]d%d gets renamed to ttyd%d.{init,lock}
>	sio's cua[il]a%d gets renamed to cuad%d.{init,lock}
>
>You didn't make it clear what ${base_device} should look like, but I'm
>sure you meant that will it include the driver's "letter".  This way
>we'll have: ttyd0, ttyd0.init, ttyd0.lock, cuad0, cuad0.init, cuad0.lock.

>If this will be done in both RELENG_5 and HEAD, I suggest to have
>backward compatibility symlinks under /dev (in RELENG_5 only).  I
>don't know how hard it would be to implement this, just an idea.

It will not be done in RELENG_5.

We can consider making a "future compatibility" rc script which creates
some strategic symlinks, but that is for discussion down the road.


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.