From owner-freebsd-questions Sat Feb 8 17:21:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA12868 for questions-outgoing; Sat, 8 Feb 1997 17:21:31 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA12861 for ; Sat, 8 Feb 1997 17:21:27 -0800 (PST) Received: from admin.cyberenet.net (mail@admin.cyberenet.net [204.213.252.6]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id RAA25557 for ; Sat, 8 Feb 1997 17:21:26 -0800 (PST) Received: from twwells.com [199.79.159.1] (root) by admin.cyberenet.net with smtp (Exim 1.59 #1) id 0vtNw7-0006gE-00; Sat, 8 Feb 1997 20:20:07 -0500 Received: by twwells.com (Smail3.1.29.1 #8) id m0vtNsp-0000ruC; Sat, 8 Feb 97 20:16 EST Message-Id: From: bill@twwells.com (T. William Wells) Subject: 2.1.7 binaries and 2.1.5 system (fwd) To: freebsd-questions@freebsd.org Date: Sat, 8 Feb 1997 20:16:42 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I want to do a quick substitution of the 2.1.7 setuid programs > (when 2.1.7 comes out) into my 2.1.5 system, as I don't have the > time to do a full upgrade. Any caveats? Oh, and before anyone else tells me -- yes, I know what I'm doing, e.g., libc has to be replaced or I have to statically link those setuid programs. And I have to trace down program calls to ensure that the bugs don't get invoked in unreplaced programs. I'm concerned about kernel call changes, file format changes, and the like -- stuff that I'd have to spend hours reading the source to find. If I were going to do that, I'd just go ahead and do a full upgrade!