From owner-freebsd-small Tue Nov 7 16: 2:59 2000 Delivered-To: freebsd-small@freebsd.org Received: from ns1.qld.m2mtechnology.com (ns1.qld.m2mtechnology.com [203.24.40.1]) by hub.freebsd.org (Postfix) with ESMTP id 74AE737B479 for ; Tue, 7 Nov 2000 16:02:51 -0800 (PST) Received: from hannama (ip132.qld.m2mtechnology.com [203.24.40.132]) by ns1.qld.m2mtechnology.com (8.9.3/8.9.3) with SMTP id KAA90641; Wed, 8 Nov 2000 10:02:24 +1000 (EST) Message-ID: <003b01c04917$2c6d2600$842818cb@gc.deepsky.net> From: "Andrew Hannam" To: "Dave Swegen" , References: <20001107161532.F1927@software.plasmon> Subject: Re: Moving from 3.0 to 4.1 Date: Wed, 8 Nov 2000 10:02:22 +1000 Organization: FamZon Systems 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.4133.2400 Disposition-Notification-To: "Andrew Hannam" X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think that the 3.0 wd devices and the new 4.X ad devices use the same major and minor numbers - try creating both sets of devices and each version of the OS should use the ones it thinks it needs to use. I use this scheme to boot one hard-drive with both a 3.4 and a 4.1 kernel (although there were a few more tricky things further on in the boot process for this one). ----- Original Message ----- From: "Dave Swegen" To: Sent: Wednesday, November 08, 2000 2:15 AM Subject: Moving from 3.0 to 4.1 > Hi! We're currently in the process of moving one of our products from > 3.0 to 4.1, and it would seem that we also need to upgrade the install > kernel we use in order to cope with the switch from wd based device > names to ad based device names. The system we use currently is as > follows: > > We use a bootp server which sends a kernel containing an MFS to the > device, which is mounted via vn0. The system in the kernel then partions > the HD, and requests tarballs which contain the system to be installed > on the HD. > > The first problem we encountered was that the old 3.0 based system, > despite being given 4.1 bootblocks to use failed to mount / , as it > insisted on trying to mount a partiton on wd0, rather than ad0 (which > had been detected during boot), and of course stopped with a device not > configured failure. > > We therefore decided to try using a 4.1 kernel, with the same settings. > Which is where we encountered the first problem. The "config kernel root > on vn0" line we used is now obsolete, and the closest thing in LINT now > is the 'options ROOTDEVNAME=\"mfs:vn0\"' line we are using at > the moment. > > Add to this that MFS seems to have been replaced by MD (on which I can > find very little information), and life has suddenly > become...interesting :) > > At the moment the install fails either after reading the kernel from the > bootp server, or fails to detect the server altogether. > > Anyway, I would much appreciate any pointers on what I might be doing > wrong, and if any more information is required, let me know. > > Cheers > Dave > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message