Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!math.fu-berlin.de!irz401!sax!not-for-mail
From: joerg@sax.sax.de (Joerg Wunsch)
Newsgroups: comp.os.386bsd.development
Subject: Re: Naming convention for tty-like devices
Date: 20 May 1993 15:44:28 +0200
Organization: SaxNet, Dresden, Germany
Lines: 20
Message-ID: <1tg1vs$2v5@sax.sax.de>
References: <C77J1C.LCI@rex.uokhsc.edu> <1993May18.103444.26378@gmd.de> <C79w03.Guy@sugar.NeoSoft.COM>
NNTP-Posting-Host: sax.sax.de
In article <C79w03.Guy@sugar.NeoSoft.COM> peter@NeoSoft.com (Peter da Silva) writes:
>
>So fix PS. The Berkeley-style PS is pretty limited anyway (doesn't have
>the ability to select by user or by port, for example, which means you have
>to grep the output... and when you're trying to kill runaway procs you
>don't want to start up any more than you have to), and could do with a
>wider TT field.
You're right with ps' limits. But, the tty naming problem is more
complex, it's not only ps, but also finger, w... Maybe, still more.
I can really live with /dev/tty[0-9][0-9] for the com ports,
/dev/ttyv[0-9a-f] for the virtual consoles and the usual names for
pty's. I can't see why this is a real limitation (but it should be
documented).
--
J"org Wunsch, ham: dl8dtl : joerg_wunsch@uriah.sax.de
If anything can go wrong... : ...or:
.o .o : joerg@sax.de,wutcd@hadrian.hrz.tu-chemnitz.de,
<_ ... IT WILL! : joerg_wunsch@tcd-dresden.de