From owner-freebsd-current Mon Jul 21 08:18:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA18122 for current-outgoing; Mon, 21 Jul 1997 08:18:40 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA18116; Mon, 21 Jul 1997 08:18:29 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id RAA09737; Mon, 21 Jul 1997 17:21:12 +0200 (CEST) From: Mikael Karpberg Message-Id: <199707211521.RAA09737@ocean.campus.luth.se> Subject: Re: /boot.foo madness In-Reply-To: <199707211449.QAA09651@ocean.campus.luth.se> from Mikael Karpberg at "Jul 21, 97 04:49:40 pm" To: karpen@ocean.campus.luth.se (Mikael Karpberg) Date: Mon, 21 Jul 1997 17:21:12 +0200 (CEST) Cc: jkh@time.cdrom.com, bde@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Mikael Karpberg: [... snip ...] > I think the second alternative sounds ok, with a small change. > > There should be no problem with the files being in the bindist, should it? > In case of an upgrade you simply save those files, if they exist, > just like you save /etc, and then in the "post install fixup" you check > the "save directory" for those files, and if they exist you move the new > files (which might contain something the user may want to see) to > /boot.foo.new, and put his old files back into position. Or am I missing > something? :-) I have to comment on my own suggestion here, actually. The above scheme would seem appropriate for the /boot.foo files, except that maybe the /boot.help file should be the newest, and therefor the old file should be called /boot.help.old instead of the new one being called /boot.help.new. But that's all easilly solvable in the post install fixup thingie. :-) /Mikael