public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] separate /usr without initramfs
Date: Sun, 27 Oct 2019 17:01:53 +0000	[thread overview]
Message-ID: <20191027170153.594bad9e@symphony.aura-online.co.uk> (raw)
In-Reply-To: <6636e037-a7c7-080b-c3bc-1ce04c3baf92@veremit.xyz>

[-- Attachment #1: Type: text/plain, Size: 1557 bytes --]

On Sun, 27 Oct 2019 16:17:04 +0000
Michael Everitt <gentoo@veremit.xyz> wrote:

> On 27/10/19 16:12, Matt Turner wrote:
> > On Sun, Oct 27, 2019 at 3:06 AM James Le Cuirot <chewi@gentoo.org> wrote:  
> >> On Sun, 27 Oct 2019 05:38:48 -0400
> >> Joshua Kinard <kumba@gentoo.org> wrote:
> >>  
> >>> Why do I not like an initramfs, though?  Well, for one, it complicates the
> >>> kernel compiles (and it makes them bigger, something which is an issue on
> >>> the old SGI systems at times).  Two, it's another layer that I have to
> >>> maintain.  Three, it violates, in my mind, the simplicity of keeping the
> >>> kernel and userland separated (e.g., kernel does kernel-y things, userland
> >>> does userland-y things).  
> >> You make it sound like the initramfs has to be built into the kernel
> >> image. It can be but it usually isn't. I suspect you know that though?
> >> Admittedly that does depend on support from your bootloader. While GRUB
> >> and U-Boot have supported this for years, I forget what oddball
> >> bootloaders your hardware may be using.  
> > Though he's likely not using it, GRUB2 supports all the platforms he
> > mentioned (x86, amd64, sparc64, [sgi] mips).
> >  
> FWIW, I do believe I saw LILO mentioned ..

https://wiki.gentoo.org/wiki/Early_Userspace_Mounting#Configuring_LILO

Phew. ;-)

Actually I was getting confused between initramfs support and device
tree support. I think every bootloader has supported initramfs since
forever.

-- 
James Le Cuirot (chewi)
Gentoo Linux Developer

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-10-27 17:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 18:14 [gentoo-dev] separate /usr without initramfs William Hubbs
2019-10-25 18:40 ` Dale
2019-10-25 20:08   ` William Hubbs
2019-10-25 20:16     ` Dale
2019-10-25 20:56       ` William Hubbs
2019-10-25 19:52 ` Jaco Kroon
2019-10-27  9:38 ` Joshua Kinard
2019-10-27 10:06   ` James Le Cuirot
2019-10-27 16:12     ` Matt Turner
2019-10-27 16:17       ` Michael Everitt
2019-10-27 17:01         ` James Le Cuirot [this message]
2019-10-27 19:55       ` Joshua Kinard
2019-10-27 19:52     ` Joshua Kinard
2019-10-27 11:22   ` Benda Xu

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=20191027170153.594bad9e@symphony.aura-online.co.uk \
    --to=chewi@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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