From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] why do I need cargo to make an initramfs?
Date: Sat, 14 May 2022 05:36:27 -0500 [thread overview]
Message-ID: <5e53ab95-5eb7-8781-1484-df6acd1fdc72@gmail.com> (raw)
In-Reply-To: <45877713-7919-dbf8-be3e-cd3c2f61dc98@web.de>
n952162 wrote:
> On 5/14/22 10:44, Stefan Schmiedl wrote:
>> Samstag, 14. Mai 2022 10:00:
>>
>>> I never needed to use cargo before, to update my kernel. In what
>>> way is
>>> cargo better than earlier mechanisms to build initramfs?
>>
>> With cargo being rust's package manager, I'd hazard the guess that
>> you got yourself a shiny new rust component in either your kernel
>> or your initramfs content.
>>
>> s.
>>
>>
>
> 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?
>
>
>
The file(s) are in /etc/dracut.conf.d/. I only have one file but
depending on setup, you could have more than one.
Hope that helps.
Dale
:-) :-)
next prev parent reply other threads:[~2022-05-14 10:37 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 [this message]
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
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=5e53ab95-5eb7-8781-1484-df6acd1fdc72@gmail.com \
--to=rdalek1967@gmail.com \
--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