RE: trouble mounting NetBSD file system
= Original Message From Malcolm Kay [EMAIL PROTECTED] = On Sun, 20 Jul 2003 12:41, nmanisca wrote: I can't seem to mount one of my two NetBSD file systems. One mounts fine, the other is not 'seen' by FreeBSD. I have two disks. The first disk has two NetBSD file systems (/ and /disk) and one swap area.All three live in BIOS partition #4. The second disk has one FreeBSD file system (/) and one swap area. These live in BIOS partition #1. I boot to FreeBSD-5.1 and the kernel sees my disks as ad0 (my first disk) and ad1(my second disk). In /dev I see only two ad0* devices, ad0 and ad0s4. I suppose ad0s4 corresponds to the #4 BIOS parition of my first disk. I can mount this just fine; it looks like NetBSD's / (NetBSD calls it wd0a). Under FreeBSD 4.x the BSD partitions on the first disk would be ad0s4a and ads04e; and if you want the swap partition ad0s4b. ad0s4 is actually the address of the entire BIOS partition(slice). If this is the only slice with a BSD disklabel then ad0a, ad0e and ad0b should be legitimate alternative names. (All I suspect very similar to NetBSD, using ad in place of wd -- historically it was also wd in FreeBSD) I would expect to see these devices in /dev, but they're just not there. If the devices with a,b and e suffixes don't exist you may need to make them using /dev/MAKEDEV. FreeBSD 5.x may be a little different (and outside my ken) but the clues should be in the above. I think devfs is supposed to make the device nodes itself. The man page for MAKEDEV says it's been deprecated. Time for me to learn more about devfs. I'm reverting to 4.8 now to see if the device shows up. --Nick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble mounting NetBSD file system
On Sun, Jul 20, 2003 at 11:39:43PM +0200, nmanisca wrote: = Original Message From Malcolm Kay [EMAIL PROTECTED] = On Sun, 20 Jul 2003 12:41, nmanisca wrote: I can't seem to mount one of my two NetBSD file systems. One mounts fine, the other is not 'seen' by FreeBSD. I have two disks. The first disk has two NetBSD file systems (/ and /disk) and one swap area.All three live in BIOS partition #4. The second disk has one FreeBSD file system (/) and one swap area. These live in BIOS partition #1. I boot to FreeBSD-5.1 and the kernel sees my disks as ad0 (my first disk) and ad1(my second disk). In /dev I see only two ad0* devices, ad0 and ad0s4. I suppose ad0s4 corresponds to the #4 BIOS parition of my first disk. I can mount this just fine; it looks like NetBSD's / (NetBSD calls it wd0a). Under FreeBSD 4.x the BSD partitions on the first disk would be ad0s4a and ads04e; and if you want the swap partition ad0s4b. ad0s4 is actually the address of the entire BIOS partition(slice). If this is the only slice with a BSD disklabel then ad0a, ad0e and ad0b should be legitimate alternative names. (All I suspect very similar to NetBSD, using ad in place of wd -- historically it was also wd in FreeBSD) I would expect to see these devices in /dev, but they're just not there. If the devices with a,b and e suffixes don't exist you may need to make them using /dev/MAKEDEV. FreeBSD 5.x may be a little different (and outside my ken) but the clues should be in the above. I think devfs is supposed to make the device nodes itself. The man page for MAKEDEV says it's been deprecated. Time for me to learn more about devfs. I had the same problem recently with -current and an OpenBSD disk. devfs would not make the necessary device node so I'm stuck. Works fine in -stable however after making the node. I'm reverting to 4.8 now to see if the device shows up. I expect that it works in 4.8. Karel. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble mounting NetBSD file system
On Sun, 20 Jul 2003 12:41, nmanisca wrote: I can't seem to mount one of my two NetBSD file systems. One mounts fine, the other is not 'seen' by FreeBSD. I have two disks. The first disk has two NetBSD file systems (/ and /disk) and one swap area.All three live in BIOS partition #4. The second disk has one FreeBSD file system (/) and one swap area. These live in BIOS partition #1. I boot to FreeBSD-5.1 and the kernel sees my disks as ad0 (my first disk) and ad1(my second disk). In /dev I see only two ad0* devices, ad0 and ad0s4. I suppose ad0s4 corresponds to the #4 BIOS parition of my first disk. I can mount this just fine; it looks like NetBSD's / (NetBSD calls it wd0a). Under FreeBSD 4.x the BSD partitions on the first disk would be ad0s4a and ads04e; and if you want the swap partition ad0s4b. ad0s4 is actually the address of the entire BIOS partition(slice). If this is the only slice with a BSD disklabel then ad0a, ad0e and ad0b should be legitimate alternative names. (All I suspect very similar to NetBSD, using ad in place of wd -- historically it was also wd in FreeBSD) If the devices with a,b and e suffixes don't exist you may need to make them using /dev/MAKEDEV. FreeBSD 5.x may be a little different (and outside my ken) but the clues should be in the above. How can I see/mount the other NetBSD file system (/disk)? NetBSD calls this one wd0e. Just in case it would be useful, I've pasted below the disklabel of my first disk (as reported by NetBSD). Thanks, Nick # /dev/wd0d: type: unknown disk: mydisk label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 234441648 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] a: 1677809763 4.2BSD 1024 819286 # (Cyl.0*- 16644) b: 2096640 16778160 swap # (Cyl. 16645 - 18724) c: 23444158563 unused 0 0 # (Cyl. 0*- 232580) d: 234441648 0 unused 0 0 # (Cyl. 0 - 232580) e: 215566848 18874800 4.2BSD 2048 16384 328 # (Cyl. 18725 - 232580) ___ Malcolm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
