Date: Mon, 20 Sep 2004 11:59:08 +0300 From: Ruslan Ermilov <ru@freebsd.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: arch@freebsd.org Subject: Re: [HEADSUP] naming of tty devices. Message-ID: <20040920085908.GA43176@ip.net.ua> In-Reply-To: <46041.1095665925@critter.freebsd.dk> References: <46041.1095665925@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
--Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 20, 2004 at 09:38:45AM +0200, Poul-Henning Kamp wrote: > My suggestion is the following: >=20 > 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]). >=20 > 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. >=20 > 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. >=20 > This results in the following major compatibility issues: >=20 > sio's cuaa* gets renamed to cuad* >=20 > sio's {tty,cua}[il]%d gets renamed to {tty,cua}%d.{init,lock} >=20 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. >=20 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, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBTpvcqRfpzJluFF4RAk8XAJ0ZOP1snrH5nkXkbokjbXf3cgxNfQCgizCo 1ZN5/30QcndPdPqPGuEBN/M= =1Hwi -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040920085908.GA43176>