1 |
Howdy, |
2 |
|
3 |
I'm trying to rebuild a kernel to include new options, see other |
4 |
thread. I got the kernel built but dracut is giving me grief. I hate |
5 |
that thing and when a previous way that worked no longer works, it |
6 |
doesn't help me like it any more. Still, it is what it is even if I |
7 |
don't like it. I read the man page, the Gentoo wiki and tried different |
8 |
methods but it just refuses to build a init thingy that I need. It |
9 |
either fails right away or gets to the end and errors out without |
10 |
completing. |
11 |
|
12 |
I name my kernels and such this way: |
13 |
|
14 |
root@fireball /usr/src/linux # ls -al /boot/kernel* |
15 |
-rw-r--r-- 1 root root 7061552 Oct 14 2018 /boot/kernel-4.18.12-1 |
16 |
-rw-r--r-- 1 root root 7082032 May 15 2019 /boot/kernel-4.19.40-1 |
17 |
-rw-r--r-- 1 root root 7102512 Jan 2 19:46 /boot/kernel-4.19.40-2 |
18 |
-rw-r--r-- 1 root root 5858496 Jun 17 2016 /boot/kernel-4.5.2-1 |
19 |
root@fireball /usr/src/linux # |
20 |
|
21 |
I copy the kernels from the /usr/src/linux directory by hand as I've |
22 |
always done. I name them starting with kernel and then add the kernel |
23 |
version with a sequence number on the end. In the past, I've made it to |
24 |
-4 before getting what I need. Right now, I'm working on 4.19.40-2 and |
25 |
building a init thingy for it. This is how the init thingys end up, in |
26 |
the past anyway: |
27 |
|
28 |
|
29 |
root@fireball /usr/src/linux # ls -al /boot/initramfs* |
30 |
-rw------- 1 root root 7752134 Oct 15 2018 /boot/initramfs-4.18.12-1.img |
31 |
-rw------- 1 root root 8560993 May 15 2019 /boot/initramfs-4.19.40-1.img |
32 |
-rw------- 1 root root 5377395 May 20 2016 /boot/initramfs-4.5.2-1.img |
33 |
root@fireball /usr/src/linux # |
34 |
|
35 |
|
36 |
What I need, the proper command with options to tell dracut I want to |
37 |
build a init thingy for 4.19.40-2. I've tried many different ways but |
38 |
none of them work. This includes commands I've used in the past that |
39 |
did work. If I have to specify the init thingy name and the location of |
40 |
the kernel modules directory, that's fine. I keep commands like this in |
41 |
a file to refer back to because I do tend to forget specifics but in |
42 |
this case, it seems dracut changed something. Previous commands are not |
43 |
working. |
44 |
|
45 |
Does anyone know how to accomplish this task? Hopefully something that |
46 |
will work even if dracut changes something with its defaults. I figure |
47 |
if I tell it all it needs to know, then it should work even if dracut |
48 |
changes the default method. I just can't seem to figure out what method |
49 |
to use here. Maybe I'm missing a option or something. |
50 |
|
51 |
Thanks much. |
52 |
|
53 |
Dale |
54 |
|
55 |
:-) :-) |