From owner-freebsd-questions Wed Aug 16 20:30:17 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id UAA14780 for questions-outgoing; Wed, 16 Aug 1995 20:30:17 -0700 Received: from diamond.sierra.net (diamond.sierra.net [204.94.39.235]) by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id UAA14759 for ; Wed, 16 Aug 1995 20:30:10 -0700 Received: from martis-d228.sierra.net by diamond.sierra.net with SMTP id AA01418 (5.67b8/IDA-1.5 for ); Wed, 16 Aug 1995 15:05:07 -0700 Message-Id: <199508162205.AA01418@diamond.sierra.net> From: "Jim Howard" To: Chuck Robey , freebsd-questions@freefall.FreeBSD.org Date: Wed, 16 Aug 1995 13:35:49 -0800 Subject: Re: gnumalloc Reply-To: jiho@sierra.net Priority: normal X-Mailer: Pegasus Mail/Windows (v1.22) Sender: questions-owner@FreeBSD.org Precedence: bulk > I don't think you have the whole story, and I believe you might possibly > be wrong about this administrator versus user mindset. One of the big > reasons why you want stuff in the root partition to be statically linked > is so that, in the situation where you've blown away something drastic in > /usr, and can't mount it (and all of your shared libs), the tools that > exist to allow you to (possibly) fix this still work. If everything is > made dynamically linked, and you lose your libs, you're dead. If fact, I > don't think you can even update your libs easily, because when you move > them, every tool you have will die. But your rebuttal just provides another example of the point. In the single-user desktop PC world, if things get THAT fouled up you just re-install the whole system from scratch, with important files presumably backed up securely. Your argument would be considered somewhere pretty far out on the fringe, frankly. But even accepting it, why would anyone consider putting /usr on a separately-mounted partition on any machine except a server? What purpose is served [ ;) ] for a single-user desktop machine? And how did this degenerate into an argument, anyway? Your perspective is clearly different from mine. It still amazes me that, although most UNI* machines are single-user workstations, it doesn't occur to people to reconsider the notion that workstations should carry all the baggage that only multi-user servers actually require. This one-size-fits-all approach has limited the appeal of UNI*. (The hardware margins of workstation vendors, however, have attracted a fair amount of envy in the PC clone market, where everyone is counting on Windows 95 to prop things up.) And since this all started with the memory usage of X and its clients: How many sites do you know of, where the network transparency of X is actually utilized as originally designed? What happened to the X terminal market? I thought the newsgroups had been abandoned to arguments like this....