SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I just downloaded it and I'm going to upgrade from 2.4.26 today. Just wondering if anyone had anything to say about this kernel. Yes, it is 3 days old. I liked my current one, until yesterday that is, when I found out that my ioctl won't load crypto modules (very easily anyway) with that kernel. Sad reason to upgrade, but I just wrote my own module and want to test it out (and of course start using it). Any opinions on 2.6.12 in general for that matter?
ta0kira
Im using 2.6.12.1 I dont update to 2.6.12.3 because everyweek they release a new modification and there is no need to upgrade every release, but I think the 2.6.12 is all the same with a feel details, and I think your upgrade is more then on time, I have no bad things to say about this kernel... much better them 2.4.x
Well, it seems fine with the exception of udev taking around 5 minutes to initialize each time I start up. Do you know how to fix that? Thanks.
ta0kira
I do like how you can link kernel modules now. I haven't messed with it, but I noticed that when you compile a module feeding off of the kernel Makefile it will place 3 .files in your folder giving the command lines used. For the .ko file it used ld. Hopefully that means we can now link external libs into our modules.
ta0kira
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.