| 1 |
Bill Longman wrote: |
| 2 |
> <snip> |
| 3 |
> |
| 4 |
>> This is funny. I have NEVER got a genkernel to work on my system. |
| 5 |
>> Actually, on any system. I'm not sure the OP would know that kernel is |
| 6 |
>> any better then the one he makes. |
| 7 |
>> |
| 8 |
> Dale, |
| 9 |
> |
| 10 |
> If you've never gotten genkernel to work, you should try this little |
| 11 |
> script that I've used for the past few years. I put it in /usr/src/gk |
| 12 |
> and I change into whatever /usr/src/kernel directory I'm going to |
| 13 |
> compile. Then, I just call "../gk all" and off it goes. Of course, if |
| 14 |
> you use lilo, it's a different story because I jumped out of the lilo |
| 15 |
> life raft years ago and managed to swim to shore. |
| 16 |
> |
| 17 |
> Here's gk. Tweak to your environment: |
| 18 |
> |
| 19 |
> CFLAGS="-O2 -march=barcelona -pipe" \ |
| 20 |
> genkernel --lvm --menuconfig --save-config --oldconfig \ |
| 21 |
> --bootloader=grub --install --symlink --kerneldir=$PWD \ |
| 22 |
> --makeopts="-s -j4" "$@" |
| 23 |
> |
| 24 |
> -- |
| 25 |
> Bill |
| 26 |
> |
| 27 |
|
| 28 |
I don't use genkernel anymore. I just roll my own. That way, I know |
| 29 |
what is in there and what is not. Then if something doesn't work, I |
| 30 |
know if it is the kernel or something else. With genkernel, you won't |
| 31 |
have a clue what it is since you don't know much if anything about the |
| 32 |
kernel and how it is configured. |
| 33 |
|
| 34 |
I'll pass. As I have seen with others, genkernel doesn't work |
| 35 |
consistently enough. |
| 36 |
|
| 37 |
Dale |
| 38 |
|
| 39 |
:-) :-) |
Archives