| 1 |
On 5/14/22 12:36, Dale wrote: |
| 2 |
> n952162 wrote: |
| 3 |
>> On 5/14/22 10:44, Stefan Schmiedl wrote: |
| 4 |
>>> Samstag, 14. Mai 2022 10:00: |
| 5 |
>>> |
| 6 |
>>>> I never needed to use cargo before, to update my kernel. In what |
| 7 |
>>>> way is |
| 8 |
>>>> cargo better than earlier mechanisms to build initramfs? |
| 9 |
>>> With cargo being rust's package manager, I'd hazard the guess that |
| 10 |
>>> you got yourself a shiny new rust component in either your kernel |
| 11 |
>>> or your initramfs content. |
| 12 |
>>> |
| 13 |
>>> s. |
| 14 |
>>> |
| 15 |
>>> |
| 16 |
>> I don't get it. Why should something built with rust require a boot |
| 17 |
>> packaging tool that also requires rust? That's like saying, if a |
| 18 |
>> facility has a python component, the whole facility needs to be |
| 19 |
>> distributed with pip. |
| 20 |
>> |
| 21 |
>> Can anyone tell me where the initramfs staging area or configuration |
| 22 |
>> file is? |
| 23 |
>> |
| 24 |
>> |
| 25 |
>> |
| 26 |
> |
| 27 |
> The file(s) are in /etc/dracut.conf.d/. I only have one file but |
| 28 |
> depending on setup, you could have more than one. |
| 29 |
> |
| 30 |
> Hope that helps. |
| 31 |
> |
| 32 |
> Dale |
| 33 |
> |
| 34 |
> :-) :-) |
| 35 |
> |
| 36 |
|
| 37 |
Unfortunately, I don't have that directory. I'm at 4.14.97. |
| 38 |
|
| 39 |
Upgrading to 5.15.32. But I get a kernel panic and have no initramfs |
| 40 |
for 5.15.32... |
| 41 |
|
| 42 |
I suppose I could unpack the one I have for 4.14.97 and create a new one |
| 43 |
based on that ... |
Archives