From owner-freebsd-arch@FreeBSD.ORG Thu Jun 5 04:48:36 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D91E37B401 for ; Thu, 5 Jun 2003 04:48:36 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71A9143F3F for ; Thu, 5 Jun 2003 04:48:35 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfmr7.dialup.mindspring.com ([165.247.219.103] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19NtEP-0006zO-00; Thu, 05 Jun 2003 04:48:34 -0700 Message-ID: <3EDF2DCE.2B2DBAAA@mindspring.com> Date: Thu, 05 Jun 2003 04:47:26 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel C. Sobral" References: <20030603113927.I71313@cvs.imp.ch> <16092.35144.948752.554975@grasshopper.cs.duke.edu> <20030603115432.EGLB13328.out002.verizon.net@kokeb.ambesa.net> <20030603122226.BGPM11703.pop018.verizon.net@kokeb.ambesa.net> <3EDD81A4.B6F83135@mindspring.com> <3EDDF732.1060606@tcoip.com.br> <20030604152156.GB25240@Odin.AC.HMC.Edu> <3EDE1D7F.1090501@tcoip.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4394c788ad2786350eac809866615a819a2d4e88014a4647c350badd9bab72f9c350badd9bab72f9c cc: arch@freebsd.org Subject: Re: Making a dynamically-linked root X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2003 11:48:36 -0000 "Daniel C. Sobral" wrote: > Sorry, Terry didn't answer /rescue/sh. He disclaimed the need for one > because, see, the risk we are incurring by having root dynamically > linked isn't greater. > > Yes, /rescue/sh answer this question. But I'm not questioning the > proposal, I'm questioning Terry's answer to a valid question (which > *should* have been /rescue/sh). If init or mount gets toasted, you are just as toasted by a single file failure as if everything were linked dynamic and you lost ld.so or libc.so. You can type incantations at the boot loader prompt (if you are local, or if you are remote, and the single points of failure of the boot loader configuration files for enabling the serial console don't get hosed) until you are blue in the face, but unless you have everything installed on / so you can rebuild init or mount from sources, you are screwed by these single points of failure. -- Terry