From owner-freebsd-current@FreeBSD.ORG  Thu Nov 20 18:29:29 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8BA0A16A4CE
	for <current@freebsd.org>; Thu, 20 Nov 2003 18:29:29 -0800 (PST)
Received: from firecrest.mail.pas.earthlink.net
	(firecrest.mail.pas.earthlink.net [207.217.121.247])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2536E43FDF
	for <current@freebsd.org>; Thu, 20 Nov 2003 18:29:28 -0800 (PST)
	(envelope-from richardcoleman@mindspring.com)
Received: from titan.criticalmagic.com ([68.213.16.23] helo=mindspring.com)
	by firecrest.mail.pas.earthlink.net with asmtp (Exim 3.33 #1)
	id 1AN12z-0003OB-00; Thu, 20 Nov 2003 18:29:26 -0800
Message-ID: <3FBD788A.4070809@mindspring.com>
Date: Thu, 20 Nov 2003 21:29:30 -0500
From: Richard Coleman <richardcoleman@mindspring.com>
Organization: Critical Magic, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "boyd, rounin" <boyd@insultant.net>
References:
	<Pine.NEB.3.96L.1031118233432.99345H-100000@fledge.watson.org><p06002033bbe0acb7b8c0@[128.113.24.47]>
	<2147483647.1069240727@[192.168.42.6]>
	<20031120095214.GA68334@server.vk2pj.dyndns.org>
	<050d01c3afa8$1dfb97a0$b9844051@insultant.net>
	<156539179.20031121001033@andric.com>
	<061f01c3afbd$4692a040$b9844051@insultant.net>
In-Reply-To: <061f01c3afbd$4692a040$b9844051@insultant.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 1ee258965991efcb0865379cdb43356e5e89bb4777695beb702e37df12b9c9ef8ed06db074b3c47b90faec8f622ad720350badd9bab72f9c350badd9bab72f9c
cc: Dimitry Andric <dimitry@andric.com>
cc: current@freebsd.org
Subject: Re: Unfortunate dynamic linking for everything
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: richardcoleman@mindspring.com
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2003 02:29:29 -0000

boyd, rounin wrote:

> From: "Dimitry Andric" <dimitry@andric.com>
> 
>     % sudo ldd /sbin/init
>     /sbin/init:
>         libutil.so.3 => /lib/libutil.so.3 (0x28074000)
>         libcrypt.so.2 => /lib/libcrypt.so.2 (0x2807f000)
>         libc.so.5 => /lib/libc.so.5 (0x28097000)
> 
>     Yes, working fine here. What should the problem be?
> 
> the day /lib gets smashed.
> 
> you're building a house of cards.  once, if /etc/init and
> /bin/sh and some other pieces where in place a smashed
> file-system could be easily fixed.  now you have to have
> 3 shared libs and a viable /lib.
> 
> do you want systems that work?  or houses of cards?

I would prefer to solve this problem using a fixit floppy or cdrom 
anyways.  I don't think that creates a house of cards.  My systems work 
just fine.

But I've often wondered how frequently a production system has such 
problems.  I've been a sysadmin for many years and can't remember this 
ever happening.  It's much more common to blow a hard drive, or have 
flaky memory, etc.

Richard Coleman
richardcoleman@mindspring.com