From owner-freebsd-security Fri Sep 20 09:15:58 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19057 for security-outgoing; Fri, 20 Sep 1996 09:15:58 -0700 (PDT) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA19031 for ; Fri, 20 Sep 1996 09:15:55 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by passer.osg.gov.bc.ca (8.7.6/8.6.10) with SMTP id JAA08430; Fri, 20 Sep 1996 09:15:51 -0700 (PDT) From: Cy Schubert - ITSD Open Systems Group Message-Id: <199609201615.JAA08430@passer.osg.gov.bc.ca> X-Authentication-Warning: passer.osg.gov.bc.ca: Host localhost [127.0.0.1] didn't use HELO protocol Reply-to: cschuber@orca.gov.bc.ca X-Mailer: DXmail To: Andy Schenck cc: freebsd-security@freebsd.org Subject: Re: pwd_mkdb and NIS In-reply-to: Your message of "Thu, 19 Sep 96 18:57:15 PDT." Date: Fri, 20 Sep 96 09:15:50 -0700 X-Mts: smtp Sender: owner-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Thu, 19 Sep 1996, Cy Schubert wrote: > > > The only way I could have "botched" the upgrade was to periodically > > enter df -k in the "holographic shell". That probably loaded > > libc.so and a number of other libraries from the chrooted filesystem. > > > > I am curious as to how you could load the dynamically linked libraries > while executing a statically linked binary. It was me. I just finished writing a paragraph to explain to you how my .profile is set up and how it may have been loaded when I remembered that my .profile was replaced during the upgard. I'm rather emberrased to admit that I loaded bash in the holographic shell causing the problem. My apologies for wasting your time. > > Andy > Regards, Phone: (604)389-3827 Cy Schubert OV/VM: BCSC02(CSCHUBER) Open Systems Support BITNET: CSCHUBER@BCSC02.BITNET ITSD Internet: cschuber@uumail.gov.bc.ca cschuber@bcsc02.gov.bc.ca "Quit spooling around, JES do it."