From: n952162 <n952162@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] why do I need cargo to make an initramfs?
Date: Sat, 14 May 2022 14:51:52 +0200 [thread overview]
Message-ID: <16f102ed-2d7a-f56e-e16a-a0bdaa08a324@web.de> (raw)
In-Reply-To: <1592052651.20220514125230@xss.de>
On 5/14/22 12:52, Stefan Schmiedl wrote:
>
> Samstag, 14. Mai 2022 11:37:
>
>> I don't get it. Why should something built with rust require a boot
>> packaging tool that also requires rust? That's like saying, if a
>> facility has a python component, the whole facility needs to be
>> distributed with pip.
>> Can anyone tell me where the initramfs staging area or configuration
>> file is?
> How are you building your initramfs? dracut, genkernel, other?
>
> Are you sure that cargo is going to be included in the initramfs
> and not just required to build it?
>
> s.
>
Well, I'm not, that's what I'm trying to do. But I'd like to do it the
way I've done it for years rather using some new facility.
Can genkernel do it? I built my kernel just now according to
https://wiki.gentoo.org/wiki/Kernel/Upgrade, as I always have.
Maybe I should start over and use genkernel?
Okay, I see genkernel has a initramfs action. I'll try that. It
probably uses cargo under the hood. SMH. Building an initramfs isn't
all that difficult once you know what's got to go into it. Are we
gratuitously adding dependencies? We should strive to keep things simple.
next prev parent reply other threads:[~2022-05-14 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 8:00 [gentoo-user] why do I need cargo to make an initramfs? n952162
2022-05-14 8:44 ` Stefan Schmiedl
2022-05-14 9:37 ` n952162
2022-05-14 10:36 ` Dale
2022-05-14 11:07 ` n952162
2022-05-14 11:12 ` n952162
2022-05-14 10:52 ` Re[2]: " Stefan Schmiedl
2022-05-14 12:51 ` n952162 [this message]
2022-05-14 13:28 ` Neil Bothwick
2022-05-14 16:47 ` Dale
2022-05-17 6:35 ` hitachi303
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=16f102ed-2d7a-f56e-e16a-a0bdaa08a324@web.de \
--to=n952162@web.de \
--cc=gentoo-user@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