Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!tut.cis.ohio-state.edu!rutgers!bellcore!texbell!killer!vector!chip
From: chip@vector.UUCP (Chip Rosenthal)
Newsgroups: comp.unix.xenix
Subject: Re: uucico problem (XCLUDE); also, 2.2 vs 2.3.
Message-ID: <764@vector.UUCP>
Date: 20 Mar 89 00:06:13 GMT
References: <715@vector.UUCP> <1989Mar18.233136.14960@ateng.ateng.com>
Reply-To: chip@vector.UUCP (Chip Rosenthal)
Organization: Dallas Semiconductor
Lines: 27

chip@ateng.ateng.com (Chip Salzenberg) writes:
>According to chip@vector.UUCP (Chip Rosenthal):
>>Analysis -- uucico apparently sets the XCLUDE flag on the line.
>Yup.  The SVID exlicitly states that the XCLUDE flag remains in effect even
>when a devices is closed. [...] My reading of the SVID didn't give me any
>indication that a fixup was possible, even as root.

Luckily, on SCO 2.2 you can open("/dev/tty2A",O_RDONLY|O_NDELAY) as root
and patch it up.  I've been told that Tandy XENIX won't allow this; once
XCLUDE is set that line is really locked.

One has to wonder if this area of SVID was rationally developed or if
it covers a kludge in the initial tty driver.

>Except, of course, for the modes of /usr/spool/uucp being 777.  Sigh.

Does this have to be??  Are you saying:

    drwxrwx-wx   6 uucp     uucp        4336 Mar 19 17:56 /usr/spool/uucp

won't work?  That's what I do now.

P.S.  Thanks for the info on Devices.

-- 
Chip Rosenthal     chip@vector.UUCP    | -------- watch this space --------
Dallas Semiconductor   214-450-5337    | - real domain address coming soon -