Date: Sun, 8 Jul 2018 04:21:52 +0530 From: Manish Jain <jude.obscure@yandex.com> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Fwd: A request for unnested UFS implementation in MBR Message-ID: <2449a381-01db-a0b7-a306-cbadf35fb504@yandex.com> In-Reply-To: <20180708004645.5a39c930.freebsd@edvax.de> References: <98201d37-2d65-34c6-969e-c9649f1a3ab1@yandex.com> <f57a5540-9736-53bf-5312-166a1b2e23b0@yandex.com> <20180707231908.65a2e973.freebsd@edvax.de> <a09d56e5-38c7-bc52-dc92-49d5956e152d@yandex.com> <20180708001336.4097d20e.freebsd@edvax.de> <6bbfdaad-6872-1a6b-f176-471e57ac8d0a@yandex.com> <20180708004645.5a39c930.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/08/18 04:16, Polytropon wrote:
> On Sun, 8 Jul 2018 03:50:09 +0530, Manish Jain wrote:
>> MBR permits 3 primary partitions + 1 EBR slice.
>>
>> What I meant was one of the three partitions serving as FreeBSD / (UFS,
>> unnested), and any extra filesystems the user needs reside within the EBR.
>>
>> In other words, an option for UFS to be just like Ext2 in this respect.
>
> Yes, that is possible if you simply format that slice. It
> does not matter if it's a DOS primary partition or a logical
> volume inside a DOS extended partition. What you basically
> do is that you get a 'c'-labeled BSD partition (where 'c'
> means "the whole thing", in this case, a partition.
>
> Let's say you have the following construct:
>
> da0 = { [da0s1] [da0s2] [da0s3] [da0s5 da0s6] }
>
> We assume da0s1 - da0s3 are used for DOS, "Windows", maybe
> one Linux Ext2 data partition - 3 DOS primary partitions.
> And then we assume one DOS extended partition with two
> logical volumes in it. You can now use newfs to format
> them:
>
> # newfs /dev/da0s5
> # newfs /dev/da0s6
>
> This gives you /dev/da0s5c and /dev/da0s6c (where the 'c'
> can be omitted, and you can use /dev/da0s5 and /dev/da0s6
> instead), and you could for example do:
>
> # mount -t ufs /dev/da0s5 /usr
> # mount -t ufs /dev/da0s6 /var
>
> Entries in /etc/fstab will attach them at boot time.
>
> However, there is a problem with booting, as I already said.
> FreeBSD requires an 'a'-labeled BSD partition to boot from,
> MBR or not (or its equivalent in GPT, freebsd-boot, to
> construct a "boot chain" from the freebsd-boot to a
> freebsd-ufs partition which holds /), and this partition
> will then be the / partition.
>
> As you can see, this is not possible. You cannot have a
> 'a' partition when you can only create a 'c' partition
> on a bare slice (coverin the whole slice).
>
>
>
> Resources:
>
> https://www.freebsd.org/doc/handbook/disk-organization.html
>
> http://www.wonkity.com/~wblock/docs/html/disksetup.html
>
> https://wiki.pacbsd.org/index.php/Partitioning
Then how do the 'a' and 'c' partitions get accommodated in GPT ?
Poly, your thinking is wrong. The BSD schema served its purpose. Now, we
should think about retiring it. Or at least, provide it as only an
option to conform with past behaviour. But definitely not as a matter of
forced usage.
Tx
MJ
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2449a381-01db-a0b7-a306-cbadf35fb504>