Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: blmblm@myrealbox.com Newsgroups: comp.os.linux.misc Subject: Re: Good Linux to start with Date: 11 Jul 2011 22:31:00 GMT Organization: None Lines: 32 Message-ID: <981bt4FlgtU2@mid.individual.net> References: X-Trace: individual.net UkHMWHkMpIHZIa22r7cnvgQKl0YNkvmMdJ/zpHYEbRl9Eoyaza X-Orig-Path: not-for-mail Cancel-Lock: sha1:dhsP9BIhw6MrD8CUfbRvXuTjd8s= X-Newsreader: trn 4.0-test76 (Apr 2, 2001) Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.misc:1747 In article , Peter J. Holzer wrote: > On 2011-07-10 03:49, Robert Riches wrote: > > On 2011-07-09, Peter J. Holzer wrote: > >> On 2011-07-09 00:05, Aragorn wrote: [ snip ] > > Yellow Pages, later renamed to NIS, and some more recent > > directory services, extend the Unix multiuser paradigm for > > networked environments. > > YP/NIS (which I first encountered in 1987 or 1988, I think) does little > more than synchronize password files[1] (and other config files) between > a master and several slaves. [ snip ] > [1] It keeps them in a different place and uses a different format for > performance reasons, but that doesn't change the principle. Where is this other place? My CPOE uses NIS on a network on Linux systems (Red Hat and derivatives), and it sure *seems* like login on an NIS client machine requires communication with the NIS server, except for those few users listed in the local /etc/passwd file. I'm not saying you're wrong, just puzzled/curious now .... [ snip ] -- B. L. Massingill ObDisclaimer: I don't speak for my employers; they return the favor.