From owner-freebsd-hackers Wed Oct 4 11:15:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id E237C37B503 for ; Wed, 4 Oct 2000 11:15:13 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e94IEwX92176; Wed, 4 Oct 2000 11:14:59 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Warner Losh Cc: nate@yogotech.com (Nate Williams), freebsd-hackers@FreeBSD.ORG Subject: Re: Automatic updates (was Re: How long for -stable...) In-Reply-To: Message from Warner Losh of "Wed, 04 Oct 2000 12:02:41 MDT." <200010041802.MAA38253@harmony.village.org> Date: Wed, 04 Oct 2000 11:14:58 -0700 Message-ID: <92172.970683298@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think that we can do a lot with cvsupd. I've used cvsupd to grab > binaries on an experimental basis and it seems to work great. I've Hmmm. Does cvsupd also move a target out of the way if it already exists and it's in the process of replacing it? What if the target is chflag'd but can be unprotected at the current security level? What I'm trying to say is that if you have "/sbin/init" and cvsupd is about to replace it, I would expect the steps to be something like this: Receive new init as /sbin/init.${pid} (or something) | |<--------------------------------------------+ | Yes |Yes \/ No | No Mv /sbin/init.${pid} /sbin/init --> chflags noschg /sbin/init --> Fail | | Yes \/ Done If cvsupd does that or can be gimmicked to do that (add --potentially-hose-me flag? ;) then I'd say it's a serious contender for being part of a binary update process. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message