1 |
Bill Longman wrote: |
2 |
> On 06/21/2010 03:37 PM, Dale wrote: |
3 |
> |
4 |
>> I'm not saying you can't use it just that it doesn't always work. Thing |
5 |
>> is, when someone uses genkernel to make the kernel, when someone asks |
6 |
>> 'did you include some driver', the usual answer is 'I don't know, I used |
7 |
>> genkernel' and then nobody knows whether it is there or not. If a |
8 |
>> person builds their own kernel, they usually know if it is there and |
9 |
>> better yet how to check and make sure it is there. Also, I don't use |
10 |
>> initrd and not sure why most people need one. I don't use modules |
11 |
>> either, hence the reason I don't need initrd. Just build in the drivers |
12 |
>> and such that are needed to boot until the modules are loaded and that's |
13 |
>> it. It's not rocket science. Driver controller, file system that root |
14 |
>> uses and that's about it. |
15 |
>> |
16 |
> And all I'm trying to point out is that you're making a leap of |
17 |
> incorrect logic by ascribing to genkernel characteristics that it |
18 |
> doesn't have. The root cause is that they've misconfigured something, so |
19 |
> the red herring of "I blah blah blah genkernel blah blah blah" shouldn't |
20 |
> set off alarms. |
21 |
> |
22 |
> I've been using it for years and it's always worked for me. Very few |
23 |
> times I have seen it crash while trying to build, but never have I seen |
24 |
> it do anything untoward or unexpected. Maybe part of the issue is that |
25 |
> users might rely on it without supplying enough arguments to it. I had |
26 |
> to write my script because I was getting carpal tunnel from typing out |
27 |
> the stupid command so many times. That said, I *always* use the |
28 |
> --kerneldir argument, so that might explain some things. By default, it |
29 |
> just uses /usr/src/linux, even if you're in some other directory, and if |
30 |
> you're not aware of that, yeah, I can see how you could bite off your |
31 |
> own toes pretty easily and not even notice. |
32 |
> |
33 |
> |
34 |
|
35 |
Things is, I have seen genkernel fail for lots of people. I have never |
36 |
had my way to fail. I may forget a option or have to add a option when |
37 |
adding hardware but I have never had make && make modules_install fail. |
38 |
The copy process always works too. It's not a leap from my point of |
39 |
view. Maybe you are just lucky so far. Some people use genkernel and |
40 |
it works but a lot have problems with it too. |
41 |
|
42 |
Funny thing is, when a person comes for help and genkernel is being |
43 |
used, not much help is offered. The other thread I mentioned earlier is |
44 |
getting help but not with genkernel. We are helping him with building |
45 |
his own tho and figuring out the options. This sort of reminds me of |
46 |
cdrkit and cdrtools. You can use cdrkit of you want. Thing is, you |
47 |
won't get much help with it because it is buggy and just doesn't work |
48 |
with some hardware. You can use it tho. It's still your choice. |
49 |
|
50 |
By all means, use genkernel. |
51 |
|
52 |
Dale |
53 |
|
54 |
:-) :-) |