From owner-freebsd-questions Tue Nov 26 01:51:17 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA06136 for questions-outgoing; Tue, 26 Nov 1996 01:51:17 -0800 (PST) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA06130 for ; Tue, 26 Nov 1996 01:51:13 -0800 (PST) From: Greg Lehey Received: from freebie.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0vSKAZ-000QrdC; Tue, 26 Nov 96 10:51 MET Received: (grog@localhost) by freebie.lemis.de (8.8.3/8.6.12) id KAA00461 for questions@FreeBSD.org; Tue, 26 Nov 1996 10:50:53 +0100 (MET) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Message-Id: <199611260950.KAA00461@freebie.lemis.de> Subject: Re: ld.so and emacs problems (fwd) To: questions@FreeBSD.org (FreeBSD Questions) Date: Tue, 26 Nov 1996 10:50:53 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Doug White writes: > On Wed, 20 Nov 1996, MDM wrote: > >> 1. EMACS 19.31 will not "start". I get an error message: >> ld.so failed: Can't find shared library "libgcc.so.261.0" >> I have searched for this file and have found: >> /usr/lib/libgcc.a, libgcc_pic.a, libgcc_p.a >> /usr/local/lib/libgcc.a >> /usr/src/gnu/usr.bin/cc/libgcc/libgcc1.c, libgcc2.c > > Hm, I see a /usr/lib/libgcc.so.261.0. If you're missing it for some > reason you can grab mine: > > ftp://gdi.uoregon.edu/pub/libgcc.so.261.0.gz Unfortunately, it wasn't on the 2.1.5 CD-ROM. >> 2. What command generates the locate database >> /var/db/locate.database ? >> The locate man page doesn't tell. > > Just leave the machine on Friday night, or grab the command line from > /etc/weekly. Specifically, it's: echo "" echo "Rebuilding locate database:" locdb=/var/db/locate.database touch ${locdb}; chown nobody ${locdb}; chmod 644 ${locdb} echo /usr/libexec/locate.updatedb | nice -5 su -m nobody 2>&1 |\ fgrep -v 'Permission denied' chmod 444 ${locdb} >> 3. I "chsh"ed the root shell to Bash (and also of my normal account), but >> paths and aliases written in the either the /root/.bashrc ( or the >> /usr/home/myhome/.bashrc) do not get "accessed" or read or "used". What's >> up? > > I'm not familiar with Bash, but since it's based on sh I would say it's > picking up the .profile in /root and ignoring your .bashrc. The bash man > page should show which file(s) it wants. You need to have a .bash_profile for login shells. It can contain just a single line: . .bashrc > I would HIGHLY recommend changing root back to sh; you won't be able to > log in if your /usr partition disappears, while a static version of sh is > in /bin. You should use su instead of logging in as root. In fact, when you come up in single user mode, you get a choice of shell. Choose sh. Greg