1 |
Dale wrote: |
2 |
> Neil Bothwick wrote: |
3 |
>> On Sat, 1 Jan 2022 15:44:51 +0000, Wols Lists wrote: |
4 |
>> |
5 |
>>>> Compiling the kernel and modules? Replace 1 with |
6 |
>>>> |
7 |
>>>> make all modules_install install |
8 |
>>>> |
9 |
>>>> There's also the matter of the initramfs, one of the main reasons |
10 |
>>>> people use genkernel, although I prefer dracut for this. |
11 |
>>>> |
12 |
>>>> |
13 |
>>> until you trip over genkernel's "features" ... like AUTOMOUNT_BOOT, |
14 |
>>> which doesn't work, by design. Or NO_INSTALL, which does rather more |
15 |
>>> than just not installing ... |
16 |
>>> |
17 |
>>> I'm investigating source_mage, and ought to investigate dracut. |
18 |
>> Once you have a working kernel, there's very little to do on updates. A |
19 |
>> script that runs |
20 |
>> |
21 |
>> cd /usr/src/linux |
22 |
>> zcate /proc/config.gz >.config |
23 |
>> make oldconfig |
24 |
>> make all modules_install install |
25 |
>> dracut --kver=$(cat include/config/kernel.release) --xz |
26 |
>> update the bootloader |
27 |
>> |
28 |
>> mostly does it all, with a few frills thrown in to cover things like |
29 |
>> rebuilding modules. |
30 |
>> |
31 |
>> |
32 |
> |
33 |
> Can you explain this part a bit? How it knows what version for example |
34 |
> to build against? Does it follow the link in /usr/src/linux, eselect |
35 |
> info or something else? |
36 |
> |
37 |
> |
38 |
>> dracut --kver=$(cat include/config/kernel.release) --xz |
39 |
> |
40 |
> The one thing that stumps me is figuring out how to tell dracut what |
41 |
> version I want built. I keep 2, 3 and sometimes 4 kernels of different |
42 |
> versions lurking about in /boot. |
43 |
> |
44 |
> Thanks. |
45 |
> |
46 |
> Dale |
47 |
> |
48 |
> :-) :-) |
49 |
|
50 |
|
51 |
I got it figured out. That's a little like cheating. LOL |
52 |
|
53 |
Dale |
54 |
|
55 |
:-) :-) |