1 |
Neil Bothwick wrote: |
2 |
> On Fri, 3 Jan 2020 01:27:22 -0600, Dale wrote: |
3 |
> |
4 |
>>>> I name my kernels and such this way: |
5 |
>>>> |
6 |
>>>> root@fireball /usr/src/linux # ls -al /boot/kernel* |
7 |
>>>> -rw-r--r-- 1 root root 7061552 Oct 14 2018 /boot/kernel-4.18.12-1 |
8 |
>>>> -rw-r--r-- 1 root root 7082032 May 15 2019 /boot/kernel-4.19.40-1 |
9 |
>>>> -rw-r--r-- 1 root root 7102512 Jan 2 19:46 /boot/kernel-4.19.40-2 |
10 |
>>>> -rw-r--r-- 1 root root 5858496 Jun 17 2016 /boot/kernel-4.5.2-1 |
11 |
>> I decided to go back to a older version, just to see if it works. The |
12 |
>> first example I had saved didn't work but the second did. First was |
13 |
>> likely from a much older version of dracut. Do you know what changed |
14 |
>> between dracut-046-r1 and dracut-048-r1? I ran into this once before |
15 |
>> when a major version number changed. |
16 |
> There was an elog message when the latest dracut emerged here, that was |
17 |
> to do with naming. I didn't read all of it as it clearly didn't apply |
18 |
> when using the default naming scheme of installkernel. |
19 |
> |
20 |
|
21 |
|
22 |
I'll go dig for that after I re-emerge the new version. I cleaned out |
23 |
that HUGE directory a while back. I do that about once a year to free |
24 |
up a little space. |
25 |
|
26 |
|
27 |
>> One reason I'd like to be able to specify everything is to avoid changes |
28 |
>> in future versions. That way I can use the same command each time |
29 |
>> unless they completely change everything which I'm sure I'd read about |
30 |
>> long before I needed to use it. Just has a example: |
31 |
>> |
32 |
>> dracut /boot/<kernel name> <initramfs name> -k <path to kernel modules> |
33 |
> If you stick with the standard kernel naming schemes, dracut will follow |
34 |
> them and you shouldn't have such issues. Using make install to install |
35 |
> the kernel instead of copying it manually will ensure you have names that |
36 |
> dracut will find. |
37 |
> |
38 |
> Unless you have a good reason to use non-standard naming, I would |
39 |
> recommend sticking with the defaults, there is less likelihood of this |
40 |
> type of breakage. |
41 |
> |
42 |
> If you really want to plough your own furrow, try running dracut with the |
43 |
> --debug option. When had issues with dracut recently, -v didn't add |
44 |
> anything but --debug highlighted the problem immediately. |
45 |
> |
46 |
> |
47 |
|
48 |
|
49 |
Can you post a ls -al /boot for both kernels and images? That way I can |
50 |
see how it names them when doing it your way. If I can make sense of |
51 |
it, I may try doing it that way. Thing is, it'll change eventually |
52 |
too. lol |
53 |
|
54 |
I need to build a 2nd rig for my TV. Between downloading stuff, |
55 |
watching TV and the other stuff I do on this thing, rebooting is hard to |
56 |
schedule. I got a mobo, memory, CPU already. Video card and a few |
57 |
others things like ethernet cards and I'd be ready to build one. |
58 |
|
59 |
Thanks. |
60 |
|
61 |
Dale |
62 |
|
63 |
:-) :-) |