From: Warner Losh <imp@bsdimp.com>
To: Vincenzo Nicosia <katolaz@freaknet.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Unix install & "standalone" package
Date: Mon, 4 Sep 2023 11:20:31 -0600 [thread overview]
Message-ID: <CANCZdfptcmo9KAt7iLE5w0KtJciLHHRNqKzTyJURbSnb75YT9g@mail.gmail.com> (raw)
In-Reply-To: <ZPXv+YBVUJS/c6hl@wontolla.jungle>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
On Mon, Sep 4, 2023 at 8:56 AM Vincenzo Nicosia <katolaz@freaknet.org>
wrote:
> rather, back then you didn't need the same kernel to run on a wide
> variety of hardware, with all the possible different combinations of
> peripherals, requiring all sorts of different drivers.
>
> I think that's the only real reason why initramfs came to existence:
> allowing a selection of kernel modules to be loaded at init time,
> depending on the hardware at disposal on that machine. Then things went
> south, and more recent initramfs have everything and the kitchen sink.
> But that's another story.
Yea, it was an effort to move mounting of root out of the kernel. The
earliest
scripts just mounted the right disk and moved on, and didn't load any new
drivers: they just had the logic to pick the desired root. But at the same
time,
there were a lot of people that were running on 4MB and 8MB systems that
noticed they could put all the router software in the initramfs and never
pivot
to something else and they could have quite the product with that. And those
were the first few bricks that paved the road to hell :)
Warner
[-- Attachment #2: Type: text/html, Size: 1584 bytes --]
next prev parent reply other threads:[~2023-09-04 17:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 14:44 [TUHS] " Norman Wilson
2023-09-04 14:55 ` [TUHS] " Vincenzo Nicosia
2023-09-04 17:20 ` Warner Losh [this message]
2023-09-04 19:05 ` Clem Cole
2023-09-05 17:03 ` Paul Winalski
2023-09-05 18:02 ` Clem Cole
2023-09-04 19:59 ` Theodore Ts'o
2023-09-04 23:51 ` Warner Losh
2023-09-04 17:18 ` Warner Losh
2023-09-04 22:10 ` Steffen Nurpmeso
2023-09-05 15:53 ` Steffen Nurpmeso
2023-09-06 17:50 ` Warner Losh
2023-09-07 0:11 ` Steffen Nurpmeso
2023-09-07 16:05 ` Warner Losh
2023-09-08 14:58 ` Theodore Ts'o
2023-09-08 13:56 ` Michael Kjörling
2023-09-08 23:38 ` Steffen Nurpmeso
2023-09-09 22:43 ` Steffen Nurpmeso
2023-09-11 4:10 ` Theodore Ts'o
2023-09-11 22:05 ` Steffen Nurpmeso
2023-09-05 1:07 ` Jonathan Gray
-- strict thread matches above, loose matches on Subject: below --
2023-09-04 9:57 [TUHS] " Paul Ruizendaal via TUHS
2023-09-04 14:53 ` [TUHS] " emanuel stiebler
2023-09-04 17:07 ` Warner Losh
2023-09-04 18:21 ` Dan Cross
2023-09-05 11:15 ` Paul Ruizendaal via TUHS
2023-09-05 14:15 ` Clem Cole
2023-09-05 17:03 ` Warner Losh
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=CANCZdfptcmo9KAt7iLE5w0KtJciLHHRNqKzTyJURbSnb75YT9g@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=katolaz@freaknet.org \
--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).