1 |
Bill Longman wrote: |
2 |
> On 06/21/2010 01:23 PM, Dale wrote: |
3 |
> |
4 |
>>> The only thing that genkernel would add is your initrd. The kernel is |
5 |
>>> exactly the same, whether you compile it with "make" or through |
6 |
>>> "genkernel". Do a test and you'll see. (I'm assuming we're both talking |
7 |
>>> about gentoo-sources, not vanilla-sources. Either way, they'd be the |
8 |
>>> same.) Some might be confused about what happens in the steps if they |
9 |
>>> haven't been down the "kernel compilation trail" more than once or |
10 |
>>> twice, but for folks who just want to compile their kernel and plop it |
11 |
>>> into place, along with a hands-off initrd, it's rather handy. |
12 |
>>> |
13 |
>>> |
14 |
>>> |
15 |
>> But only if it works. When I compile my kernel, I KNOW for sure what is |
16 |
>> in there. When genkernel does one, especially on a new install, I have |
17 |
>> no idea what is in it or what is not. If something goes wrong, I don't |
18 |
>> know where to start. Is it a kernel problem or is it something else? |
19 |
>> Who knows. Then you have to go back and start from the bottom, usually |
20 |
>> the kernel, and work your way back up to find out what is broken. |
21 |
>> |
22 |
> By "But only if it works," I assume the antecedent "it" refers to is a |
23 |
> kernel that we're attempting to boot correctly. (In other words, you're |
24 |
> not talking about genkernel failing to create a kernel for you. Is that |
25 |
> correct?) |
26 |
> |
27 |
> If someone has trouble on an initial install, then that just means they |
28 |
> didn't configure the kernel correctly, is what I interpret that to mean. |
29 |
> The result of "make" and the result of "genkernel kernel" are exactly |
30 |
> the same. If your "make menuconfig" creates an invalid .config file for |
31 |
> you, no sort of magic is going to make its resultant kernel valid. Do |
32 |
> you mean to say that you just grab a kernel, jump into the directory and |
33 |
> say "make" without an mrproper and some sort of config? You do realize |
34 |
> that genkernel has --menuconfig, --xconfig and --gconfig exactly for |
35 |
> this purpose, don't you? |
36 |
> |
37 |
> What sort of things do you believe genkernel is adding to your kernel? |
38 |
> If you use "genkernel --menuconfig --no-install kernel", you can look |
39 |
> and see what it did. It's no different than running "make menuconfig" |
40 |
> followed by a "make; make modules". Just look in /usr/share/genkernel at |
41 |
> the gen_compile.sh and you'll see that it does a make. |
42 |
> |
43 |
> |
44 |
>> Genkernel may work for you but that doesn't mean it does for everyone |
45 |
>> else. Should I mention hal here? When someone comes for help, your |
46 |
>> looking for the failure not the successes. If it was sucessful, they |
47 |
>> wouldn't need help. |
48 |
>> |
49 |
> Which is why I mentioned genkernel in the first place. Most times a hang |
50 |
> after boot is due to components that were missed in the kernel build -- |
51 |
> from where? -- from a missing or incorrectly created initrd if the |
52 |
> required modules weren't compiled into the kernel. The easiest way that |
53 |
> I've seen is to use genkernel and get back to work. Then later on you |
54 |
> can find out what an initrd is and why it's needed with modules but at |
55 |
> least you'd have a running system. |
56 |
> |
57 |
> No, I don't think you should mention hal because it's probably OT for a |
58 |
> thread about a hung boot. But you should apply to yourself a similar |
59 |
> logic you ask of me: if others can use genkernel successfully, why can't I? |
60 |
> |
61 |
> Bill |
62 |
> |
63 |
> |
64 |
|
65 |
I'm not saying you can't use it just that it doesn't always work. Thing |
66 |
is, when someone uses genkernel to make the kernel, when someone asks |
67 |
'did you include some driver', the usual answer is 'I don't know, I used |
68 |
genkernel' and then nobody knows whether it is there or not. If a |
69 |
person builds their own kernel, they usually know if it is there and |
70 |
better yet how to check and make sure it is there. Also, I don't use |
71 |
initrd and not sure why most people need one. I don't use modules |
72 |
either, hence the reason I don't need initrd. Just build in the drivers |
73 |
and such that are needed to boot until the modules are loaded and that's |
74 |
it. It's not rocket science. Driver controller, file system that root |
75 |
uses and that's about it. |
76 |
|
77 |
I haven't used genkernel in a while. I have just seen where people have |
78 |
used it and it not work. Same as hal. It works for most but when it |
79 |
doesn't, no one can figure out why because few people know how the thing |
80 |
works and even fewer can figure out the config file. That's not quite |
81 |
as off topic as it appears. |
82 |
|
83 |
If you want to use genkernel, go for it. I just know this, when someone |
84 |
asks for help that may be kernel related and they use genkernel, there |
85 |
is very very little help I can provide. Some people here use genkernel |
86 |
but there are a lot that don't. There is another thread posted a day or |
87 |
so ago where they used genkernel, no one has been able to help them |
88 |
yet. Not one reply that I have seen. I want to help but with |
89 |
genkernel, I have no idea where to start. I'm sure it is a kernel issue |
90 |
but that's about it. It appears that on one else can help either. It's |
91 |
not like this is a small mailing list with few people on it. |
92 |
|
93 |
It's your choice. Use whatever makes you happy and gets you where you |
94 |
want to go. |
95 |
|
96 |
Dale |
97 |
|
98 |
:-) :-) |