Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!ncoast!allbery From: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR) Newsgroups: comp.unix.sysv386 Subject: Re: Which UNIX? Message-ID: <1990Sep22.162149.23519@NCoast.ORG> Date: 22 Sep 90 16:21:49 GMT References: <1990Sep19.011303.13481@NCoast.ORG> Reply-To: allbery@ncoast.ORG (Brandon S. Allbery KB8JRR/KT) Followup-To: comp.unix.sysv386 Organization: North Coast Public Access *NIX, Cleveland, OH Lines: 23 As quoted from by mju@mudos.ann-arbor.mi.us (Marc Unangst): +--------------- | allbery@NCoast.ORG (Brandon S. Allbery KB8JRR/KT) writes: | > You missed a thread from about a month ago. I *have* relaxed security; I | > installed it that way. Unfortunately, this didn't stop it from screaming | > about security violations when I attempted to add a new shell to the sysadmsh | > list of configurable login shells. Among other things. | | Oh, you use sysadmsh. That explains a lot. +--------------- Understand, please, that I do *not* use sysadmsh when I can find the documentation to do it otherwise. I *do*, however, work for a VAR... and value-added, for us, includes adding things to the system. And we don't expect our (generally small) clients to understand UNIX well enough to hack around with the raw system. And ESPECIALLY not with C2 security! ++Brandon -- Me: Brandon S. Allbery VHF/UHF: KB8JRR on 220, 2m, 440 Internet: allbery@NCoast.ORG Packet: KB8JRR @ WA8BXN America OnLine: KB8JRR AMPR: KB8JRR.AmPR.ORG [44.70.4.88] uunet!usenet.ins.cwru.edu!ncoast!allbery Delphi: ALLBERY