*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm planing to install FreeBSD 6.0 on my system as a third OS. Up 'til now my main OS is Linux and as a second WinXP. I read about installing FeeBSD on there website, but I'm having trouble understanding the way, BSD calls/manages its partitions. So maybe some of you can help me out?
On my system I'd like to create some free space on my second hd. It would look like this (linux naming)
sdb1 - linux swap
sdb2 - ext3
sdb3 - FreeBSD? (would it be da1s3?)
sdb5 - ntfs
sdb6 - ntfs
sdb7 - fat32
So, da1s3 would contain the BSD partitions with /, /var, etc. like da1s3a, b...?
Do I have to understand a slice as some kind of extended partition where the mounted BSD partitions are logical drives? If this would be the case, would I run into problems if there already is an extended partition on this HD?
Any help apreciated!
Thanks!
So, da1s3 would contain the BSD partitions with /, /var, etc. like da1s3a, b...?
Yup! Although, depending on what kind of disk it is (or more correctly, where on the system it's located), FreeBSD may assign a different name to it. For example, I have a serial ATA drive: it shows up as da4 even though it's the only hard disk in there. Also, certain letters have special meanings. "a" indicates the root partition, "b" is for a swap partition, and "c" indicates the whole slice (in raw terms, don't screw with this one!). "d" used to represent the entire disk (also in raw terms) but doesn't anymore. So / will be da1s3a, SWAP will be da1s3b, and anything you add after that will be da1s3d, da1s3e, etc.
Quote:
Originally Posted by dabang
Do I have to understand a slice as some kind of extended partition where the mounted BSD partitions are logical drives?
Kinda. FreeBSD will handle this information by itself, so the BIOS doesn't get involved in determining the partitions on a BSD slice. This is why many more traditional partition editors (especially Microsoft ones) don't fully recognize BSD slices for what they really are, at least not in terms of the partitions they contain. To the outside world, a BSD slice looks just like any other ordinary partition.
Quote:
Originally Posted by dabang
If this would be the case, would I run into problems if there already is an extended partition on this HD?
No, you should not, because the BIOS does not consider it as an extended partition. But of course, always backup your important data before messing with partition tables.
Write down on paper the information given by fdisk on Linux regarding the C/H/S numbers to enforce them at the BSD sysinstall if necessary, and at least backup the MBR (contains the partition table) in case something goes wrong: "dd if=/dev/hda of=/mnt/floppy/mbr bs=512 count=1"
FreeBSD may change your partition layout if it uses another setup of C/H/S numbers, so try to see whether sysinstall agrees with what fdisk gave you. If not, then introduce them yourself. Then if you like you may reboot to linux again to see how the partition table was setup and go back to the installer knowing that it won't write data past the partition you want for it
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.