From: Warner Losh <imp@bsdimp.com>
To: Phil Budne <phil@ultimate.com>
Cc: tuhs@tuhs.org, gtaylor@tnetconsulting.net
Subject: [TUHS] Re: Question about BSD disklabel history
Date: Sun, 31 Dec 2023 14:02:00 -0700 [thread overview]
Message-ID: <CANCZdfqvSpcToetRxWTfucn0g3u89Ey5EqWJBpoK2oR2yYCDMQ@mail.gmail.com> (raw)
In-Reply-To: <202312312027.3BVKRK5d049733@ultimate.com>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
On Sun, Dec 31, 2023 at 1:27 PM Phil Budne <phil@ultimate.com> wrote:
> arnold@skeeve.com wrote:
> > I am guessing that the original conventions date back to
> > V7 or 32V, but one would have to go looking at code to be sure.
>
> Looking at the hp (RP-04/5/6) man page in V7, 32/v, and 3bsd the
> convention was rpN, where 0 <= N <= 7 were partitions on the first
> drive, and rp8 was the first partition on the second drive. rp0 was
> root, rp1 was swap, rp2 and rp3 (in the v7 man page) are unassigned.
>
> The rpNx convention, where N is the drive number, with "c" as the
> whole disk is present in the 4.1BSD hp(4) man page.
>
This was just a change to MAKEDEV. The kernel used the same minor
number encoding. 4BSD still used the V7 make script in /dev, but at some
point before 4.1cBSD (I don't have the 4.1BSD exploded locally) it changed,
both in name from MAKE to MAKEDEV and to start the [a-h] suffix for
partitions.
Warner
[-- Attachment #2: Type: text/html, Size: 1444 bytes --]
next prev parent reply other threads:[~2023-12-31 21:02 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 [this message]
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
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=CANCZdfqvSpcToetRxWTfucn0g3u89Ey5EqWJBpoK2oR2yYCDMQ@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=gtaylor@tnetconsulting.net \
--cc=phil@ultimate.com \
--cc=tuhs@tuhs.org \
/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).