[HEADSUP] naming of tty devices.

[Ruslan Ermilov]

On Mon, Sep 20, 2004 at 09:38:45AM +0200, Poul-Henning Kamp wrote:
> My suggestion is the following:
> 
> 	All drivers will offer "tty${something}" devices, and
> 	generally ${something} will consist of a letter followed
> 	by a number, possibly in base 36 ([0-9a-z]).
> 
> 	All drivers which attach to external equipment via a serial
> 	connector should also offer "cua${thesamething}".  "Embedded"
> 	serial ports, pseudo drivers etc, do not have to offer the
> 	"cua" if DCD state on open is not an issue.
> 
> 	The init and lock devices will be called ${base_device}.[init,lock]
> 	and they will possibly be provided by on-demand devices so that
> 	they do not clutter up /dev.
> 
> 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.

> Well-argued protests or researched alternatives before friday please.
> 
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.


Cheers,
-- 
Ruslan Ermilov
ru at FreeBSD.org
FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20040920/e474e686/attachment.bin