| 1 |
On Tue, Mar 27, 2012 at 9:57 AM, Dale <rdalek1967@×××××.com> wrote: |
| 2 |
> Michael Hampicke wrote: |
| 3 |
<SNIP> |
| 4 |
>> |
| 5 |
>> I don't understand why people always say that they hate genkernel |
| 6 |
>> because they like to build the kernel on their own. You still can do |
| 7 |
>> this with genkernel. I've been doing it for years. |
| 8 |
<SNIP> |
| 9 |
> |
| 10 |
> |
| 11 |
> I tried genkernel and it was a miserable failure for me. So, for me, I |
| 12 |
> have no desire to use it. I have also read where others have the same |
| 13 |
> experience so it is not just me. It may work fine for some but for |
| 14 |
> others it does not. |
| 15 |
> |
| 16 |
> I plan to keep making mine the manual way. You can keep using genkernel |
| 17 |
> if you want. |
| 18 |
> |
| 19 |
> BTW, mine is like this: |
| 20 |
> |
| 21 |
> copy old config |
| 22 |
> make oldconfig |
| 23 |
> make all && make modules_install |
| 24 |
> copy kernel to /boot |
| 25 |
> |
| 26 |
> That to me seems a LOT easier and it also works very well for me. |
| 27 |
> |
| 28 |
> Dale |
| 29 |
> |
| 30 |
> :-) :-) |
| 31 |
|
| 32 |
Until you add in the work of doing the initrd for each new kernel. I |
| 33 |
think that's Michael's point. |
| 34 |
|
| 35 |
I agree with you Dale. I do it the same way as you, except if I build |
| 36 |
an initrd I've done it completely by hand, building the whole |
| 37 |
directory structure, etc, then building it into the binary. That's a |
| 38 |
lot of work. Today we have two tools I know of, genkernel & dracut, |
| 39 |
that are represented as doing this work for us. I'm interested in what |
| 40 |
genkernel did wrong for you, as well as how to use both tools |
| 41 |
successfully. |
| 42 |
|
| 43 |
- Mark |
Archives