Re: [HEADSUP] naming of tty devices.
From: Alexey Dokuchaev (danfe_at_nsu.ru)
Date: 09/21/04
- Previous message: Poul-Henning Kamp: "Re: [HEADSUP] naming of tty devices."
- In reply to: Poul-Henning Kamp: "[HEADSUP] naming of tty devices."
- Next in thread: Poul-Henning Kamp: "Re: [HEADSUP] naming of tty devices."
- Reply: Poul-Henning Kamp: "Re: [HEADSUP] naming of tty devices."
- Reply: Eivind Eklund: "Re: [HEADSUP] naming of tty devices."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 21 Sep 2004 17:42:46 +0700 To: Poul-Henning Kamp <phk@phk.freebsd.dk>
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.
What about contracting `.init|lock' to just `i|l', like we have with all
(most) other device names out there (i.e., acd0t0, not acd0track0) -- long
device names is a thing to avoid, IMHO.
./danfe
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Poul-Henning Kamp: "Re: [HEADSUP] naming of tty devices."
- In reply to: Poul-Henning Kamp: "[HEADSUP] naming of tty devices."
- Next in thread: Poul-Henning Kamp: "Re: [HEADSUP] naming of tty devices."
- Reply: Poul-Henning Kamp: "Re: [HEADSUP] naming of tty devices."
- Reply: Eivind Eklund: "Re: [HEADSUP] naming of tty devices."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: compilation problem with module function interface definition
... >> decimal floats start appearing, it would be wise for users to avoid
... > for numeric literals was a decimal KIND (as previously suggested ... I
guess I sort of passed over that suggestion because I don't ... (comp.lang.fortran) - Re: (OT) Singing my same old sad song.
... they avoid the full text of what has been written, and claim the NEED to drive to work,
ignoring such things as car pooling, making fewer trips to the store, shopping closer to
home, and otherwise cutting back on miles driven. ... Nobody has suggested that anyone STOP driving,
yet most of the responses have been dished out as though that WERE the suggestion. ...
(rec.outdoors.rv-travel) - Re: How do I speed Up dataset.ReadXML????????
... Try my suggestion, using a text file where the separator is a control char,
... that avoid having to process the fields looking for ... embedded comma
inside the values. ... (microsoft.public.dotnet.framework.compactframework) - Re[4]: [PHP] nested, referenced foreach & implicit current array pointer issues
... instead to avoid the reference, ... assignment. ... Yep,
already did, 10x for the suggestion. ... (php.general) - Re: multilinepattern match
... it throws one into the debugger, ... Again - just a suggestion :-) ...
Another suggestion is avoid setting '$_'. ... (comp.lang.perl.misc)