peter@ficc.uu.net (Peter da Silva) (04/08/89)
The really really big thing that clutters up /dev is all those tty devices. There are dozens more of those than there are disks, tapes, memory, and so on. So why did AT&T move all the disks into /dev/dsk/* and leave all those ttys out there? I know that you can't REALLY call it /dev/tty/whatever, because /dev/tty is a historical relic, but what's wrong with having SOME sort of /dev/t/whatever arrangement? -- Peter da Silva, Xenix Support, Ferranti International Controls Corporation. Business: uunet.uu.net!ficc!peter, peter@ficc.uu.net, +1 713 274 5180. Personal: ...!texbell!sugar!peter, peter@sugar.hackercorp.com.
gwyn@smoke.BRL.MIL (Doug Gwyn ) (04/08/89)
In article <3757@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes: >... what's wrong with having SOME sort of /dev/t/whatever arrangement? Nothing at all, so long as you fix up the handful of utilities that "know" about /dev/tty* names.
peter@ficc.uu.net (Peter da Silva) (04/09/89)
In article <10010@smoke.BRL.MIL>, gwyn@smoke.BRL.MIL (Doug Gwyn ) writes: > In article <3757@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes: > >... what's wrong with having SOME sort of /dev/t/whatever arrangement? > Nothing at all, so long as you fix up the handful of utilities that > "know" about /dev/tty* names. They can do it while fixing all the utilities that don't use perror() or optargs() or assume that "" == "." or assume that "//xds13" == "/xds13", and so on and so on... Yeh, I know 'ps' doesn't like terminals called "/dev/cul32". But really it's long past time this sort of no-brainer fix was finally done. -- Peter da Silva, Xenix Support, Ferranti International Controls Corporation. Business: uunet.uu.net!ficc!peter, peter@ficc.uu.net, +1 713 274 5180. Personal: ...!texbell!sugar!peter, peter@sugar.hackercorp.com.