jay@hqda-ai.ARPA (Jay Hiser) (09/09/88)
I grew up on BSD 4.2. Now I'm the administrator for 1/2 dozen CCI 6/32s that are using SYSVR2. I really miss having the job control available under BSD and I'd like to get whatever I can on my present system. My system does have shl, but no one has ever used it and I doubt if it is properly set up. Typing shl results in: "no control channels available (errno 2)" My documentation consists of the man pages for shl and sxt -- that's it. In addition, I'm not authorized to call CCI's software helpline anymore because I haven't had their sys admin class (neither my employer nor our client is thrilled about spending $750 so I can spend a week reviewing ls and cat). CCI didn't offer any more support for uucp or the Berkely net extensions either, but I figured them out with the help of good books & good advice. All I need are a couple of clues (its got to do with /dev/stx, right?) and I think I can get this to work. If you are using the shell layer manager on your SysV Tahoe, please let me know what the trick is. Thank you, Jay Heiser The Phantom System Administrator
dao@cs.nott.ac.uk (David Osborne) (09/12/88)
In article <11234@hqda-ai.ARPA> jay@hqda-ai.ARPA (Jay Hiser) writes: >My documentation consists of the man pages for shl and sxt -- that's >it. ... >All I need are a couple of >clues (its got to do with /dev/stx, right?) and I think I can get this ^^^ wrong, i think, that should read `sxt' >to work. > >If you are using the shell layer manager on your SysV Tahoe, please >let me know what the trick is. Thank you, i'm not using shell layers on our SysV tahoe, but i think you need to configure the sxt pseudo-device into the kernel. on our system, the file to edit is /usr/src/uts/machine/cf/CF (the configuration file). if you're running a newer SysV than ours, you may well have the sysadm utility which will have a "reconfigure kernel" option in a menu. my System Admin Manual says "several drivers and software subsystems are treated like device drivers without any associated hardware. To include any of these pieces, a pseudo-device specification is used, as shown below: pseudo device-name [ howmany ] Examples of pseudo-devices are sxt, the job-control driver; pty, the pseudo-terminal driver (where the optional howmany indicates the number of pseudo-terminals to configure--32 is the default); and inet... Other pseudo-devices for the network include loop, ...; imp ...; and ether ..." here's the tail-end of our CF file as an example device ace0 at vba? csr 0xff0000 vector acecint acerint device ace1 at vba? csr 0xff0100 vector acecint acerint pseudo-device pty 32 pseudo-device sxt 8 pseudo-device loop 1 \dave David Osborne, system administrator, ICL Clan 7/200 (== Power 6/32 tahoe) Cripps Computing Centre, University of Nottingham, Nottingham NG7 2RD, UK Phone: +44 602 484848 x2064 JANET: dao@uk.ac.nott.clan BITNET: dao%uk.ac.nott.clan@ukacrl.bitnet ARPA: dao%uk.ac.nott.clan@nss.cs.ucl.ac.uk or %ukacrl.bitnet@cunyvm.cuny.edu UUCP: {...!mcvax}!ukc!nott-cs!clan!dao -- David Osborne Cripps Computing Centre, University of Nottingham, Nottingham NG7 2RD, UK Phone: +44 602 484848 x2064 JANET: dao@uk.ac.nott.cs BITNET: dao%uk.ac.nott.cs@ukacrl.bitnet ARPA: dao%uk.ac.nott.cs@nss.cs.ucl.ac.uk or %ukacrl.bitnet@cunyvm.cuny.edu UUCP: {...!mcvax}!ukc!nott-cs!dao