Re: [HEADSUP] naming of tty devices.

From: Poul-Henning Kamp (phk_at_phk.freebsd.dk)
Date: 09/21/04

  • Next message: Alexey Dokuchaev: "Re: [HEADSUP] naming of tty devices." 
    To: Alexey Dokuchaev <danfe@nsu.ru>
Date: Tue, 21 Sep 2004 12:51:04 +0200

    In message <20040921104246.GA75823@regency.nsu.ru>, Alexey Dokuchaev writes:
    >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.

    The problem with just a 'i' or 'l' is that it creates confusion as to
    what is the device name and what is the extension. I like the concept
    of a big fat '.' in there to tell the extension apart. Shortening the
    extension from "init" to "i" and "lock" to "l" would be confusing at
    best, and of little real saving in practice.

    My plan is for the ".init" and ".lock" devices to be "on-demand", in
    other words, they won't show up until first time you try to access them. 

    -- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@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.
_______________________________________________
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"
  • Next message: Alexey Dokuchaev: "Re: [HEADSUP] naming of tty devices."

    Relevant Pages

    • Re: ASSERT problem in CWnd::DestroyWindow within a DLL
      ... I've tried with extension DLL's and I've got the following error: ... "DllMain already defined in DLL1.obj" ... How can i avoid this problem? ... Prev by Date: ...
      (microsoft.public.vc.mfc)
    • Re: File backup script in c shell.
      ... It works fine now but the only problem is that, when grepping files, ... included - not just in the extension. ... Anyway to avoid this? ... -- The Blues Brothers ...
      (comp.unix.shell)
    • Re: Name a File via Code Q
      ... If the extension is always 4 characters long, then you could just avoid ... eg. what I want to appear is "Part of name of original file 07-feb-09 ...
      (microsoft.public.excel.programming)
    • Re: [HEADSUP] naming of tty devices.
      ... >>device names is a thing to avoid, ... > what is the device name and what is the extension. ... they won't show up until first time you try to access them. ... To unsubscribe, ...
      (freebsd-arch)
    • New extension date on Form 4868?
      ... The Form 4868 for 2005 does not state clearly the extension date, ... does not have any explicit options to have 6-month extension or not, ... confusion. ... Does it simply mean that August 15 deadline of last year is ...
      (misc.taxes)