NetBSD Problem Report #13746

Received: (qmail 10402 invoked by uid 1218); 18 Aug 2001 16:48:52 -0000
Message-Id: <20010818164852.10401.qmail@mail.netbsd.org>
Date: 18 Aug 2001 16:48:52 -0000
From: jhawk@MIT.EDU
Reply-To: jhawk@netbsd.org
To: gnats-bugs@gnats.netbsd.org
Cc: "Myrddin Emrys" <netbsd@spiritusa.net>
Subject: sysinst does not allow remote upgrades
X-Send-Pr-Version: 3.95
X-GNATS-Notify: "Myrddin Emrys" <netbsd@spiritusa.net>

>Number:         13746
>Category:       install
>Synopsis:       sysinst does not allow remote upgrades
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    install-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sat Aug 18 16:49:00 +0000 2001
>Closed-Date:    
>Last-Modified:  Thu Apr 10 04:22:20 +0000 2008
>Originator:     John Hawkinson
>Release:        1.5.1
>Organization:
	MIT
>Environment:

System: NetBSD mail 1.5 NetBSD 1.5 (HOMEWORLD) #0: Sat Feb 10 08:13:16 EET 2001 mycroft@netbsd.hut.fi:/usr/src/sys/arch/i386/compile/HOMEWORLD i386


>Description:

   Myrddin Emrys describes his problem (below). There is no way to remotely
perform a NetBSD upgrade from 1.5 to 1.5.1 (or suchlike) via sysinst.
Sure, you can extract the sets by hand, but in addition to being
potentially error-prone, there's no good way to perform functions like
the removal of obsolete files, etc.

>How-To-Repeat:

From netbsd@spiritusa.net Thu Jul 12 15:49:56 2001
Return-Path: <netbsd@spiritusa.net>
Delivered-To: netbsd-users@netbsd.org
Received: (qmail 22010 invoked from network); 12 Jul 2001 15:49:56 -0000
Received: from softdnserror (HELO ws1.spiritusa.net) (209.83.81.11)
  by mail.netbsd.org with SMTP; 12 Jul 2001 15:49:56 -0000
Received: from firewall.spiritusa.net (firewall.spiritusa.net [209.83.81.3]) by ws1.spiritusa.net (NTMail 3.03.0017/1d.aa5n) with ESMTP id sa394360 for <netbsd-users@netbsd.org>; Thu, 12 Jul 2001 10:55:31 -0500
Message-ID: <00ee01c10aea$de43e0e0$0a00000a@spiritusa.net>
From: "Myrddin Emrys" <netbsd@spiritusa.net>
To: <netbsd-users@netbsd.org>
Subject: Remote Upgrade of 1.5 to 1.5.1
Date: Thu, 12 Jul 2001 10:54:00 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Length: 745
Lines: 16

I have remote access only to a colocated DNS server. I would like to upgrade
the server remotely if possible... the drive is considerable, especially
since my car is not functioning at the moment. :-)

What steps should I take to make the upgrade as smoothly as possible? From
what I understand, I should download the new sets, backup my /etc, stop all
services (except for sshd of course), extract the relevant sets except for
/etc, extract the new /etc to something like /etc.new, and reboot. Then
resolve any issues with new /etc formats after the computer is back up.

Is this likely to work? Did I miss any steps I'll need to perform? I really
don't want to have to physically go to the box if I mess up and can no
longer ssh in.

Myrddin


From netbsd@spiritusa.net Fri Jul 13 14:27:20 2001
Return-Path: <netbsd@spiritusa.net>
Delivered-To: netbsd-users@netbsd.org
Received: (qmail 13278 invoked from network); 13 Jul 2001 14:27:20 -0000
Received: from softdnserror (HELO ws1.spiritusa.net) (209.83.81.11)
  by mail.netbsd.org with SMTP; 13 Jul 2001 14:27:20 -0000
Received: from firewall.spiritusa.net (firewall.spiritusa.net [209.83.81.3]) by ws1.spiritusa.net (NTMail 3.03.0017/1d.aa5n) with ESMTP id va396131 for <netbsd-users@netbsd.org>; Fri, 13 Jul 2001 09:32:57 -0500
Message-ID: <019b01c10ba8$7b9295e0$0a00000a@spiritusa.net>
From: "Myrddin Emrys" <netbsd@spiritusa.net>
To: <netbsd-users@netbsd.org>
Subject: Leftover Files after 1.5 -> 1.51 Upgrade
Date: Fri, 13 Jul 2001 09:31:19 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Length: 371
Lines: 6

After updating the kernel, extracting the sets, and running 1.51... how can
I clean up any leftover files that are no longer used in 1.51? Extracting
sets will add new files, but it won't remove old apps that are no longer
used. Other than extracting the file lists from the old tars and doing a
diff on the new sets, is there a way to easily clean up unused 1.5 files?
>Fix:


I think a reasonable first cut would be to install sysinst as part of
the OS and allow the execution of various functions independantly from
the base install. Or perhaps build it and make it avaialble in
installation/misc/...
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback
State-Changed-By: reinoud@netbsd.org
State-Changed-When: Sat, 30 Sep 2006 22:20:04 +0000
State-Changed-Why:
Part of the problem has been fixed with postinstall. The other
question about remote instal support in sysinst is not clear to
me yet.



State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Thu, 10 Apr 2008 04:22:20 +0000
State-Changed-Why:
this should not be in feedback state; it is not soliciting feedback, just
waiting for someone to do massive rewrites to sysinst.


>Unformatted:

 Removing obsolete files can be done with `postinstall fix obsolete' so that
 part is taken care for in 3.x and 4.x. The remote upgrading part might still
 be a bit tricky. If there is a serial console available remotely, one could
 boot an installation kernel and use sysinst. Since there is a /resque in 3.x
 and 4.x with statically linked binaries for emergency recovery i think its 
 safe to just unpack the new tar's on top of the old installation esp. in such
 small upgrade cases.

 DO remember always to run a new kernel first before unpacking.

Home	PR Database Search