From owner-freebsd-current Sat Mar 25 16:39:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 4478F37B9F2 for ; Sat, 25 Mar 2000 16:39:11 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.19.160] (dialup160.brussels.skynet.be [195.238.19.160]) by trinity.skynet.be (Postfix) with ESMTP id A97F318423; Sun, 26 Mar 2000 01:39:05 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200003260018.KAA07524@shad.internal.en-bio> References: <200003260018.KAA07524@shad.internal.en-bio> Date: Sun, 26 Mar 2000 01:38:48 +0100 To: Tony Maher From: Brad Knowles Subject: Re: Accessing FreeBSD 3.4-STABLE filesystems from 4.0-STABLE... Cc: FreeBSD-CURRENT Mailing List Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:18 AM +1000 2000/3/26, Tony Maher wrote: > No, sd is deprecated. > AFAIK its da only in 4.0, and only character devices. > 3.4 has sd compatability and has block devices. Hmm. Okay, well I note that what's being used right now is da1s1a through da1s1h, and I had copied these entries as appropriate for da0. Only, they didn't work. Yes, I did check the device entries for da0s1a through da0s1h, and they do exist and appear to be correct. When I try to mount my 3.4-STABLE root filesystem on /old, here's what I get: $ mount /old mount: /dev/da0s1a on /old: incorrect super block Perhaps a listing of the devices would be useful: $ ls -la /dev/da[01]s1? crw-r----- 1 root operator 13, 0x00020000 Mar 20 09:38 /dev/da0s1a crw-r----- 1 root operator 13, 0x00020001 Mar 20 09:38 /dev/da0s1b crw-r----- 1 root operator 13, 0x00020002 Mar 20 09:38 /dev/da0s1c crw-r----- 1 root operator 13, 0x00020003 Mar 20 09:38 /dev/da0s1d crw-r----- 1 root operator 13, 0x00020004 Mar 20 09:38 /dev/da0s1e crw-r----- 1 root operator 13, 0x00020005 Mar 20 09:38 /dev/da0s1f crw-r----- 1 root operator 13, 0x00020006 Mar 20 09:38 /dev/da0s1g crw-r----- 1 root operator 13, 0x00020007 Mar 20 09:38 /dev/da0s1h crw-r----- 1 root operator 13, 0x00020008 Mar 18 21:45 /dev/da1s1a crw-r----- 1 root operator 13, 0x00020009 Mar 18 21:45 /dev/da1s1b crw-r----- 1 root operator 13, 0x0002000a Mar 18 21:45 /dev/da1s1c crw-r----- 1 root operator 13, 0x0002000b Mar 18 21:45 /dev/da1s1d crw-r----- 1 root operator 13, 0x0002000c Mar 18 21:45 /dev/da1s1e crw-r----- 1 root operator 13, 0x0002000d Mar 18 21:45 /dev/da1s1f crw-r----- 1 root operator 13, 0x0002000e Mar 23 12:34 /dev/da1s1g crw-r----- 1 root operator 13, 0x0002000f Mar 18 21:45 /dev/da1s1h Anyone got any other advice, or is there any other information I need to provide? Thanks! -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message