Re: [HEADSUP] naming of tty devices.

From: Alexey Dokuchaev (danfe_at_nsu.ru)
Date: 09/21/04

  • Next message: Eivind Eklund: "Re: [HEADSUP] naming of tty devices." 
    Date: Tue, 21 Sep 2004 17:58:39 +0700
To: Poul-Henning Kamp <phk@phk.freebsd.dk>

    On Tue, Sep 21, 2004 at 12:51:04PM +0200, Poul-Henning Kamp wrote:
    > 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.

    Sounds fair enough.

    Thanks!

    ./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"

  • Next message: Eivind Eklund: "Re: [HEADSUP] naming of tty devices."

    Relevant Pages

    • Re: [HEADSUP] naming of tty devices.
      ... In message, Alexey Dokuchaev writes: ... >device names is a thing to avoid, ... 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. ...
      (freebsd-arch)
    • 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: THoughts on I-355, I-80 and US 45 / 52
      ... I decided to run it for the first time ... avoid route 45 / 52 between Frankfort and Manteno at all costs. ... one way passenger car toll on I-355 south ... extension is $1, which at about 8c per mile is around the average as ...
      (misc.transport.road)