1 |
Neil Bothwick wrote: |
2 |
> On Sat, 6 Jun 2020 11:34:28 -0500, Dale wrote: |
3 |
> |
4 |
>>>> From what I've read, I like my way better. I did have to change the |
5 |
>>>> names from bzimage* to kernel* but other than that, I can use the |
6 |
>>>> naming method I've used for years and keep the good kernels I want. |
7 |
>>> make install names the kernels vmlinuz-$VERSION, and updates a |
8 |
>>> symlink to vmlinuz if one exists. |
9 |
>> But sometimes I have more than one of the same version. I add a -1, -2, |
10 |
>> -3 etc to them as I go. From my understanding, make install doesn't do |
11 |
>> that. I do and with good reason. It seems make install won't accomplish |
12 |
>> what I do by hand. |
13 |
> There's a kernel option that does that automatically, LOCALVERSION I |
14 |
> think, but it's years since I've needed to touch it. |
15 |
|
16 |
But if it changes how it works and I don't know it, that could cause |
17 |
problems. It could even remove something I don't want removed. If I do |
18 |
it myself, I know what is done and don't remove anything I don't want to |
19 |
lose. Even the make commands change between kernels at times. I suspect |
20 |
make install has changes too. I don't want to have to track kernel |
21 |
changes just to know if I can use make install and still get what I have |
22 |
now. |
23 |
|
24 |
|
25 |
> |
26 |
>>>> My biggest problem, getting the dracut command options right. If I |
27 |
>>>> didn't need dracut, I'd be in heaven. |
28 |
>>> If you have a plain setup, dracut shouldn't need any options. |
29 |
>> I don't have a plain setup tho nor do I really want that setup. |
30 |
> You don't boot from an encrypted drive (yet) or use unusual hardware, |
31 |
> that's what I meant by a plain system. Dracut handles booting from a a |
32 |
> btrfs root on a LUKS encrypted block device here with no fancy |
33 |
> configuration. It really is impressive the way it figures so much out for |
34 |
> itself. |
35 |
> |
36 |
|
37 |
What I meant was, I don't use make install because I do things |
38 |
differently than make install does. It's not "plain" in that regard. |
39 |
|
40 |
|
41 |
>> I like |
42 |
>> having backup kernels and my own numbering system. It has worked for me |
43 |
>> for decades, ever since I started using Gentoo and building my own |
44 |
>> kernels. I don't see any point in changing what works unless I can |
45 |
>> streamline what I'm already getting with the results I expect. If I |
46 |
>> could get rid of the init thingy, I would have zero issues with my |
47 |
>> method. It's dracut that causes the issues. We all know how much I |
48 |
>> dislike init thingys tho. ;-) That said, dracut hasn't failed me in a |
49 |
>> while. If it can't build correctly, it does spit out it failed. It's |
50 |
>> been a while since the init thingy it creates has failed as well. So, |
51 |
>> at least there is that. |
52 |
> I use a shell script to compile and install the kernel, build the |
53 |
> initramfs and then update the bootloader. It means the process is always |
54 |
> executed consistently and I only have to remember one command :) |
55 |
> |
56 |
> |
57 |
|
58 |
|
59 |
Well, we know my scripting ability isn't anywhere near that advanced. |
60 |
Claiming I can do a basic script is a stretch. ROFL When I do it |
61 |
manually, I get consistent results to and I know what steps were taken |
62 |
to get there. My only problem is recalling the options for dracut. |
63 |
|
64 |
Dale |
65 |
|
66 |
:-) :-) |