NetBSD Problem Report #4195

Received: (qmail 5994 invoked from network); 30 Sep 1997 20:30:34 -0000
Message-Id: <199709302030.WAA01790@zork.north.de>
Date: Tue, 30 Sep 1997 22:30:25 +0200 (MET DST)
From: gizmo@zork.north.de (Klaus Weber)
Reply-To: gizmo@zork.north.de (Klaus Weber)
To: gnats-bugs@gnats.netbsd.org
Subject: install/upgrade disks do not include ccd support
X-Send-Pr-Version: 3.95

>Number:         4195
>Category:       install
>Synopsis:       install/upgrade disks do not include ccd support
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people
>State:          closed
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue Sep 30 23:20:02 +0000 1997
>Closed-Date:    Sun Jun 22 13:59:22 +0000 2014
>Last-Modified:  Sun Jun 22 13:59:22 +0000 2014
>Originator:     Klaus Weber
>Release:        1.2
>Organization:
-
>Environment:
System: NetBSD zork.north.de 1.2.1 NetBSD 1.2.1 (ZORK) #5: Sun Sep 21 23:56:38 MET DST 1997 gizmo@zork.north.de:/usr/src/sys/arch/i386/compile/ZORK i386


>Description:
	Currently, the install/upgrade floppies do not support
	installing/upgrading on ccd'ed partitions. This will make
	upgrading unnecessarily hard for people who have one or more
	of /, /usr, or /var on a ccd.
>How-To-Repeat:
	Read INSTALL kernel config file, note that ccd-support is not
	enabled.
>Fix:
	- uncomment "pseudo-device  ccd     4" line in INSTALL kernel
	  config file
	- put /sbin/ccdconfig on the install/upgrade floppies.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: fair 
State-Changed-When: Thu Jul 9 20:55:29 PDT 1998 
State-Changed-Why:  
Theoretically, this is easy. In practice, it costs 9K in the kernel, and 
up to 100K on the install media. For CD-ROM, this is a slam-dunk; for 
floppy, it might put us over the top. Is there space for this? If it's not 
there, is it impossible to install/upgrade a system with ccd, or merely 
very inconvenient? 

From: Klaus Weber <gizmo@zork.north.de>
To: fair@NetBSD.ORG
Cc:  Subject: Re: misc/4195
Date: Fri, 10 Jul 1998 12:30:10 +0200 (CEST)

 fair@NetBSD.ORG writes:
  > Synopsis: install/upgrade disks do not include ccd support
  > 
  > State-Changed-From-To: open->analyzed
  > State-Changed-By: fair
  > State-Changed-When: Thu Jul 9 20:55:29 PDT 1998
  > State-Changed-Why: 
  > Theoretically, this is easy. In practice, it costs 9K in the kernel, and
  > up to 100K on the install media. For CD-ROM, this is a slam-dunk; for
  > floppy, it might put us over the top. Is there space for this? If it's not
  > there, is it impossible to install/upgrade a system with ccd, or merely
  > very inconvenient?

 Depends on how you define "impossible". It is certainly possible in
 these situations:

 - you have another machine where none of /usr, /var is on a ccd. You
   can upgrade this machine first, then use it to compile a custom
   kernel for installing a machine which has one or more of /usr, /var
   on a ccd (this is how I upgraded my machine in the past).

 - the toolchain on the machine to be upgraded is able to compile a new
   kernel (with ccd support) with the new kernel sources. You are then
   able to make a custom upgrade floppy and use that.

 - if you need a new toolchain to compile a new kernel, but the new
   userland works with the old kernel, you could get away with:
   * boot system single-user, configure ccd.
   * untar new release on top of the currently installed binaries
   * without rebooting, compile a new kernel using the just-installed
     binaries.
   * reboot with the new kernel, and pray that you got it right on the
     first try. :-/

 If you need a new userland to compile a new kernel which in turn needs
 a new kernel to work, and you do not have another machine handy, then
 you're hosed, afaict. :-<


 I'm not really sure how to resolve this. On one hand, having one or
 more of /usr, /var on a ccd is probably not a very common
 configuration (yet). We could simply declare it "not supported", and
 people who have this are on their own.

 On the other hand, if we want this to be a supported configuration, I
 think it's necessary to include ccdconfig on the upgrade disk/ccd
 support in the kernel. I don't think the additional 9k in the kernel
 are much of a problem, however, the extra 100k for ccdconfig are a bit
 annoying. Maybe ccdconfig can be stripped down a bit? I only looked at
 it briefly, but it looks like it only needs the kvm stuff to print out
 the currently configured ccds. This would not be strictly necessary
 in a install/upgrade situation, and thus eliminate the need to link
 with libkvm (of course, this is only a win if no other binary on the
 install disk needs libkvm). 

 I can't do some testing right now as I will leave soon (will be back
 sunday evening), but if ccdconfig could be stripped down, "/usr and
 /var on a ccd" could be made a supported configuration, which would be
 a win, imho.

 Regards,
 	Klaus

Date: Sun, 27 Jun 1999 23:42:04 -0700 (PDT)
From: David Brownlee <abs@anim.dreamworks.com>

We already have a two disk install set for i386 (with an option of
a single disk stripped kernel version). We should probably bite 
the bullet and come up with a 'fat' and 'thin' sysinst and kernel
config. Is anyone interested in contributing patches for this? :)

	David/absolute

	  -=-  "Maybe god will cover up his eyes"  -=-


State-Changed-From-To: analyzed->closed
State-Changed-By: bsiegert@NetBSD.org
State-Changed-When: Sun, 22 Jun 2014 13:59:22 +0000
State-Changed-Why:
i386 now uses a GENERIC kernel for installation, so there is ccd(4) support.


>Unformatted:

Home	PR Database Search