SCO telinit bug (Was: Re: Trouble with uucp/cu/dialing sharing a phone line)

Larry Dighera root at conexch.UUCP
Mon Dec 26 03:45:13 AEST 1988


In article <10 at estinc.UUCP> fnf at estinc.UUCP (Fred Fish) writes:
>
>BEWARE!  The documentation for 2.3 claims that you can change inittab
>and then execute "telinit 2", just like under "real unix", and it will
>automatically regenerate the ttys file for you.  I naively changed a
>couple of entries in the supplied inittab, without first looking at
>or saving the ttys file, and ran "telinit 2".  Well, it regenerated
>a ttys file for me alright, but apparently the original inittab was
>out of sync with the original ttys file, because it no longer spawned
>a getty to the console, causing me to think the system was hung.

SCO's /etc/inittab and telinit are a completely useless kludge.  Not only
do they fail to provide the functionality of the real thing, they break 
your system if you try to use them.  There is no reason for SCO to 
continue to embarrass themselves by distributing this hack in an otherwise
superior implementation of UNIX(tm).  Why don't they just compile the
AT&T SysV init source code and become fully compatible (and functional)
instead of clinging to their old Sys III /etc/ttys junk?
 
The AT&T SysV init code is known to work with Xenix286/386.  In fact, 
binaries are available in the public domain to convert your SCO Xenix
to be fully compatible with SysV in this regard.  Once converted, you
can do things like run different gettys on individual ports, have 
several different run-levels, and not have to worry about breaking your
system by running telinit 2.

Larry Dighera

-- 
USPS: The Consultants' Exchange, PO Box 12100, Santa Ana, CA  92712
TELE: (714) 842-6348: BBS (N81); (714) 842-5851: Xenix guest account (E71)
UUCP: conexch Any ACU 2400 17148425851 ogin:-""-ogin:-""-ogin: nuucp
UUCP: ...!uunet!turnkey!conexch!root || ...!trwrb!ucla-an!conexch!root



More information about the Comp.unix.xenix mailing list