Date: Mon, 27 Mar 2000 19:30:08 +0200 From: Brad Knowles <blk@skynet.be> To: Julian Elischer <julian@elischer.org> Cc: Doug Barton <Doug@gorean.org>, Tony Maher <Tony.Maher@eBioinformatics.com>, FreeBSD-CURRENT Mailing List <freebsd-current@freebsd.org> Subject: Re: Accessing FreeBSD 3.4-STABLE filesystems from4.0-STABLE... Message-ID: <v04220815b5054a410216@[195.238.1.121]> In-Reply-To: <Pine.BSF.4.10.10003270911480.40800-100000@InterJet.elischer.org> References: <Pine.BSF.4.10.10003270911480.40800-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 9:13 AM -0800 2000/3/27, Julian Elischer wrote: > in a 4.0 kernel, teh block device doesn't exist, you always use the > character device, > so it was renamed so that /dev/da0s1a is teh name for the char device > but if you are using a device on a 3.4 disk it refers toi the block device > (which isn't in a 4.0 kernel) This is a 4.0-STABLE system: $ cd /dev && ls -la da[01]s1? crw-r----- 1 root operator 13, 0x00020000 Mar 20 09:38 da0s1a crw-r----- 1 root operator 13, 0x00020001 Mar 20 09:38 da0s1b crw-r----- 1 root operator 13, 0x00020002 Mar 20 09:38 da0s1c crw-r----- 1 root operator 13, 0x00020003 Mar 20 09:38 da0s1d crw-r----- 1 root operator 13, 0x00020004 Mar 20 09:38 da0s1e crw-r----- 1 root operator 13, 0x00020005 Mar 20 09:38 da0s1f crw-r----- 1 root operator 13, 0x00020006 Mar 20 09:38 da0s1g crw-r----- 1 root operator 13, 0x00020007 Mar 20 09:38 da0s1h crw-r----- 1 root operator 13, 0x00020008 Mar 18 21:45 da1s1a crw-r----- 1 root operator 13, 0x00020009 Mar 18 21:45 da1s1b crw-r----- 1 root operator 13, 0x0002000a Mar 18 21:45 da1s1c crw-r----- 1 root operator 13, 0x0002000b Mar 18 21:45 da1s1d crw-r----- 1 root operator 13, 0x0002000c Mar 18 21:45 da1s1e crw-r----- 1 root operator 13, 0x0002000d Mar 18 21:45 da1s1f crw-r----- 1 root operator 13, 0x0002000e Mar 23 12:34 da1s1g crw-r----- 1 root operator 13, 0x0002000f Mar 18 21:45 da1s1h This is a different 3.2-RELEASE system: $ cd /dev && ls -la da[01]s1? brw-r----- 1 root operator 4, 0x00020009 Jul 7 1999 da1s1b brw-r----- 1 root operator 4, 0x0002000c Jul 28 1999 da1s1e brw-r----- 1 root operator 4, 0x0002000d Jul 29 1999 da1s1f It seems to me like I've got the correct character devices created under 4.0-STABLE, and yet there still isn't a valid filesystem that fsck can find on /dev/da0s1a, which I know to be false because I can reboot the machine and bring it up in 3.4-STABLE on that disk. So, I'll repeat the question -- what do I have to do in order to get 3.4-STABLE disks readable under 4.0-STABLE, and/or 4.0-STABLE disks readable under 3.4-STABLE? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, <blk@skynet.be> || 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v04220815b5054a410216>