From: Grant Taylor via TUHS <tuhs@tuhs.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Question about BSD disklabel history
Date: Sun, 31 Dec 2023 21:24:22 -0600 [thread overview]
Message-ID: <f5fac166-ef86-42eb-b2cb-babf97d222b3@tnetconsulting.net> (raw)
In-Reply-To: <CANCZdfqckGiHw0J3Qp-sOTqQ0m4YT6r9RyDG=tZTdo-mhr-MLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On 12/31/23 20:22, Warner Losh wrote:
> It means you either use one set of non overlapping partitions or
> another set. They were setup in clever ways
>
> It's more like you can use two or three partitions with non overlapping
> sets that cover the whole disk.
...
> Think more of a limited number of ways to mix and match for greater
> flexibility w/o editing the tables.
>
> A silly example: a is first 2/3 of the disk. B is 2nd 2/3, c d and
> e are 1/3 each.
Okay.
This makes more sense. Pre-define overlapping partitions but only use
non-overlapping. Sort of like tool boxes that come with a bunch of
supports for dividers, but you can only put so many dividers in the
pre-defined spots, but contents between the dividers doesn't overlap.
Sort of like how many squares are in this bigger grid of dots that is
itself a big square.
> But ancient Unix didn’t have nested partitioning schemes like
> FreeBSD supports...
Understood and appreciated.
--
Grant. . . .
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4033 bytes --]
next prev parent reply other threads:[~2024-01-01 3:24 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 17:30 [TUHS] " Grant Taylor via TUHS
2023-12-31 17:38 ` [TUHS] " arnold
2023-12-31 20:07 ` Warner Losh
2024-01-01 0:13 ` Bakul Shah
2023-12-31 20:27 ` Phil Budne
2023-12-31 21:02 ` Warner Losh
2024-01-01 0:26 ` Grant Taylor via TUHS
2024-01-01 2:22 ` Warner Losh
2024-01-01 3:24 ` Grant Taylor via TUHS [this message]
2023-12-31 21:31 ` Clem Cole
2023-12-31 22:07 ` Warner Losh
2024-01-01 16:00 ` Clem Cole
2024-01-02 18:49 ` Warner Losh
2024-01-02 19:30 ` Chet Ramey
2024-01-02 20:07 ` Clem Cole
2024-01-02 19:50 ` Dan Cross
2024-01-02 19:55 ` Jim Capp
2024-01-02 20:11 ` Dan Cross
2024-01-02 20:30 ` Dan Cross
2024-01-02 20:50 ` Clem Cole
2024-01-02 21:04 ` Dan Cross
2023-12-31 22:46 ` G. Branden Robinson
2023-12-31 23:06 ` Larry McVoy
2023-12-31 23:37 ` Al Kossow
2023-12-31 23:41 ` Alec Muffett
2024-01-02 20:48 ` Dan Cross
2024-01-02 21:17 ` John Cowan
2024-01-03 3:33 ` Theodore Ts'o
2024-01-03 3:57 ` Warner Losh
2024-01-03 4:03 ` Warner Losh
2024-01-03 4:30 ` Theodore Ts'o
2024-01-03 5:10 ` Warner Losh
2024-01-03 15:56 ` Dan Cross
2024-01-03 16:37 ` Theodore Ts'o
2024-01-03 16:41 ` Dan Cross
2024-01-04 8:42 ` arnold
2024-01-04 18:26 ` Kevin Bowling
2024-01-03 14:39 ` Dan Cross
2023-12-31 23:08 ` Phil Budne
2023-12-31 23:37 ` G. Branden Robinson
2023-12-31 23:59 ` Warner Losh
2023-12-31 23:50 ` G. Branden Robinson
2024-01-01 0:09 ` Al Kossow
2023-12-31 21:55 Norman Wilson
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=f5fac166-ef86-42eb-b2cb-babf97d222b3@tnetconsulting.net \
--to=tuhs@tuhs.org \
--cc=gtaylor@tnetconsulting.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).