PC-BSD 1.3 RC1 has been released. From the changelog: "Fixed icon size issues in KMenu; installer now does not display extended partitions; installer now can use empty primary partition space to install; fixed issue with BSDStats not properly reporting usage; fixed problem with 'Start' icon text not being translated properly; fixed issues when using installer to upgrade system from 1.2 to 1.3; closed numerous other issues from BETA2." Get it here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-10-08
"Exactly! BSD doesn't have to have a partition for each mount point, instead, you have one primary partition and then all your mount points become slices within."
You're right, but be careful with the terminology. What you call "partition" in DOS is called "slice" in FreeBSD. A slice can hold many paritions (This is the FreeBSD term now!) which are mounted into the root partition (or into another mountpoint).
Exempli gratia:
% mount
/dev/ad0s1a on / (ufs, local)
/dev/ad0s1d on /var (ufs, local, soft-updates)
/dev/ad0s1e on /usr (ufs, local, soft-updates)
/dev/ad0s1f on /home (ufs, local, soft-updates)
Here, ad0 is the first hard disk, ad0s1 is its first partition (DOS) / first slice (FreeBSD). The slice holds the Partitions a (root partition), b (swap), d (system ressources), e (var), and f (home).
Every UFS1/UFS2 capable OS that is installed on the computer, let's say on another disk ad1 or on the same disk on a second slice ad0s2, can have access to these partitions.
Member since:2006-12-12
Member since:
2006-12-12
Exactly! BSD doesn't have to have a partition for each mount point, instead, you have one primary partition and then all your mount points become slices within.
I think the BSD way is a bit cleaner myself, but I have to admit it was confusing to me when I first encountered it.