From owner-freebsd-hackers Tue Jul 2 7:32:32 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 218C537B400; Tue, 2 Jul 2002 07:32:29 -0700 (PDT) Received: from topperwein.dyndns.org (acs-24-154-28-203.zoominternet.net [24.154.28.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F6C143E0A; Tue, 2 Jul 2002 07:32:28 -0700 (PDT) (envelope-from behanna@zbzoom.net) Received: from topperwein (topperwein [192.168.168.10]) by topperwein.dyndns.org (8.12.5/8.12.5) with ESMTP id g62EWStl012841; Tue, 2 Jul 2002 10:32:28 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Tue, 2 Jul 2002 10:32:23 -0400 (EDT) From: Chris BeHanna Reply-To: FreeBSD-Hackers To: Brett Glass Cc: "Jacques A. Vidrine" , FreeBSD-Hackers Subject: FreeBSD Auto-update (Was: Re: resolv and dynamic linking to compatlibc) In-Reply-To: <4.3.2.7.2.20020701210053.0229c970@localhost> Message-ID: <20020702002229.V47784-100000@topperwein.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 1 Jul 2002, Brett Glass wrote: > At 12:22 PM 7/1/2002, Jacques A. Vidrine wrote: > > >Gee, I guess we better get cracking to take offline every previous > >version of libc, too --- which would mean every version of FreeBSD and > >who knows what else. > > Alas, ethics demand that they be either taken offline or accompanied > with a clear, visible, and strong warning. Who is going to expend the time and effort to do this, and what task should they let drop on the floor to get it done? > [...snip...] > > A snapshot of 4.6-STABLE should also be made and released as 4.6.1. I repeat my above question. Yes, "Windows-update"-like machinery in sysinstall would be nice, but I don't see you falling all over yourself to either contribute it or fund it. All I see you doing is complaining that your priorities aren't adopted by the committers. What you want is more likely to occur if/when sysinstall is cleaned up. By all accounts, it's a maze of twisted little code paths, all alike. You could contribute to that, for a start, to make sure that the modularity needed to plug in an update facility is designed in. I'd suggest piggybacking the update facility on top of portupgrade to minimize duplication of effort. That, of course, depends upon the availability of known good binary packages with valid MD5 checksums and/or PGP signatures, and that's a whole 'nother resource problem. Followups to -hackers. -- Chris BeHanna http://www.pennasoft.com Principal Consultant PennaSoft Corporation chris@pennasoft.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message