Date: Thu, 05 Jun 2003 04:47:26 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: "Daniel C. Sobral" <dcs@tcoip.com.br> Cc: arch@freebsd.org Subject: Re: Making a dynamically-linked root Message-ID: <3EDF2DCE.2B2DBAAA@mindspring.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
"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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EDF2DCE.2B2DBAAA>