Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!noc.near.net!uunet!opl.com!psinntp!psinntp!uuneo!sugar!peter From: peter@NeoSoft.com (Peter da Silva) Newsgroups: comp.os.386bsd.development Subject: Re: Naming convention for tty-like devices Message-ID: <C7EzpE.Etq@sugar.NeoSoft.COM> Date: 22 May 93 06:08:01 GMT References: <1993May18.103444.26378@gmd.de> <C79w03.Guy@sugar.NeoSoft.COM> <1786@lucifer.UUCP> Organization: NeoSoft Communications Services -- (713) 684-5900 Lines: 31 In article <1786@lucifer.UUCP> rst@liciren.li.co.uk (Richard Thombs) writes: > How about /dev/tty[a-o][0-9a-f] for serial lines > and /dev/tty[p-z][0-9a-f] for pseudo ttys? > Plenty of serial lines, plenty of pseudo ttys and a 'normal' naming scheme. Because you can have more than 16 ports on a serial card. More than 36. Because there are things that aren't ptys or serial ports. Virtual consoles, for example. Certain streams devices, if we want to integrate streams into the system. Multiplexed files. On one system at work, where we have virtual consoles, OSI-based ptys, network ptys, regular serial ports, and hardcoded serial cards, we get: /dev/tty0[01] /dev/ttyi1[a-h] /dev/ttyp[00-99] /dev/ttyv[00-99] /dev/vt[000-004] Another system has three sets of ids for serial ports: /dev/tty[01] /dev/ttyi1[a-p] /dev/ttya[00-16] -- Peter da Silva. <peter@sugar.neosoft.com>. `-_-' Har du kramat din varg idag? 'U` "Det er min ledsager, det er ikke drikkepenge."