Re: [HEADSUP] naming of tty devices.
From: Valentin Nechayev (netch_at_lucky.net)
Date: 09/20/04
- Previous message: Poul-Henning Kamp: "Re: [HEADSUP] naming of tty devices."
- In reply to: Poul-Henning Kamp: "Re: [HEADSUP] naming of tty devices."
- Next in thread: Ruslan Ermilov: "Re: [HEADSUP] naming of tty devices."
- Reply: Ruslan Ermilov: "Re: [HEADSUP] naming of tty devices."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 20 Sep 2004 15:19:13 +0300 To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Mon, Sep 20, 2004 at 14:09:02, phk wrote about "Re: [HEADSUP] naming of tty devices.":
>>When restoring terminal device from this name, now it is possible yet
>>to determine terminal testing /dev/tty$x or /dev/cua$x; with your new
>>scheme this will be impossible totally.
> No, that is exactly the way it will work, and which today it doesn't.
> ttyd0 and cuad0 is the same device. The difference between "tty"
> and "cua" is how we react to DCD when opening.
> You can never be
> logged in vial both ttyd0 and cuad0 at the same time, so there is
> no logging issue.
I say not for logging, but for restoring full terminal name from short name.
E.g. listing processes controlled by this terminal. Whether /bin/ps will
list processes for both callin and callout port, when got "-t d1"?
-netch-
_______________________________________________
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: "Re: [HEADSUP] naming of tty devices."
- Next in thread: Ruslan Ermilov: "Re: [HEADSUP] naming of tty devices."
- Reply: Ruslan Ermilov: "Re: [HEADSUP] naming of tty devices."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: Mutex in ostream operator - doesnt work
... There is a way to get fairly scalable logging scheme. ... POSIX works
well with this scheme. ... performance single-producer/consumer lock-free queues in this
scheme to ... (comp.programming.threads) - Re: need wireless router where wan can be on 192.168.1.x net
... All routers allow you to change the LAN IP scheme. ... Linksys ship with
a 192.168.1.x scheme, but by logging into the router, ... (alt.internet.wireless)