From: erif <linux-newbie@omnib.org>
To: Steven Smith <sos22@cam.ac.uk>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Mounting BSD-labeled slices in Linux
Date: Tue, 20 Apr 2004 14:13:11 +0200 [thread overview]
Message-ID: <20040420141311.D22871@bigtower.net> (raw)
In-Reply-To: <20040420114321.GA44860@archibold.chu.cam.ac.uk>; from sos22@cam.ac.uk on Tue, Apr 20, 2004 at 12:43:21PM +0100
On Tue, Apr 20, 2004 at 12:43:21PM +0100, Steven Smith wrote:
> > /dev/hda1 corresponds to FreeBSDs /dev/ad0s1.
> > What does Linux call, for example, /dev/ad0s1a?
>
> Usually, Linux just shoves stuff in BSD-style slice tables on the end
> of the partition table. In my case, ad0s4a is hda11, ad0s4b hda12,
> and so on.
>
> For recent 2.4 kernels, dmesg should have a line of the form:
>
> p4: <bsd: p11 p12 p13 p14 p15 p16 >
Thanks!
Yes, this is the FreeBSD-slice
hda1: <bsd: hda10 hda11 hda12 hda13 >
and this is the DragonFly-slice
hda2: <bsd: hda14 hda15 hda16 hda17 >
..strange numbering, shouldn't it look like this?
hda2: <bsd: hda20 hda21 hda22 hda23 >
One thing I found particularly interesting is that _both_ /dev/hda2 and
/dev/hda14 seem to represent /dev/ad0s2a, and I can even mount them both at
the same time!
=/
--
Fredrik Eriksson
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-04-20 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 10:37 Mounting BSD-labeled slices in Linux erif
2004-04-20 11:43 ` Steven Smith
2004-04-20 12:13 ` erif [this message]
2004-04-20 12:40 ` Steven Smith
2004-04-20 13:05 ` erif
2004-04-20 18:10 ` John T. Williams
2004-04-20 19:11 ` erif
2004-04-20 19:18 ` Steven Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040420141311.D22871@bigtower.net \
--to=linux-newbie@omnib.org \
--cc=linux-newbie@vger.kernel.org \
--cc=sos22@cam.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.