From owner-freebsd-questions Fri Oct 29 13:59:18 1999 Delivered-To: freebsd-questions@freebsd.org Received: from s8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by hub.freebsd.org (Postfix) with ESMTP id 566C1150E6 for ; Fri, 29 Oct 1999 13:59:12 -0700 (PDT) (envelope-from jcwells@u.washington.edu) Received: from localhost (jcw@localhost) by s8-37-26.student.washington.edu (8.9.3/8.9.3) with ESMTP id BAA33967; Sat, 30 Oct 1999 01:56:40 GMT (envelope-from jcwells@u.washington.edu) X-Authentication-Warning: s8-37-26.student.washington.edu: jcw owned process doing -bs Date: Sat, 30 Oct 1999 01:56:40 +0000 (GMT) From: "Jason C. Wells" X-Sender: jcw@s8-37-26.student.washington.edu Reply-To: "Jason C. Wells" To: J McKitrick Cc: freebsd-questions@FreeBSD.ORG Subject: Re: stupid root/toor question... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Oct 1999, J McKitrick wrote: >Looks like root IS toor. >But why was everyone saying to use a different shell in toor and save sh >for root in the event of problems? Now for the gory details. Bash is built with the use of shared libraries. The libraries are in /usr/lib. Suppose /usr has a problem. You cannot mount /usr. You cannot use bash. If root tries to use bash but bash will not work, then root cannot login. Poof, you are locked out. sh does not shared libs. FWIW, bash can be built with static linking, but don't worry about that just yet. Thank You, | http://students.washington.edu/jcwells/ Jason Wells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message