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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm still hoping for a way to configure the kernel where I can edit a file that lists EVERY option (and suboption, etc ... leaving nothing out for the selected architecture). Just dropping in my own config file isn't the same, since the saved config files don't have all options in them.
I am running 2.6.35 right now without issue - works just as well as the last release, but if you follow ChangeLogs, you'll notice a lot of new stuff (improvements) in both .35 and .34 over previous versions.
I did try the nconfig menu, and found it to be ugly as heck - needs some colorizing at the least, and maybe some borders around the popup boxes (one or both, to aid in distinguishing popup boxes from background text). Functionally, it's better than menuconfig IMO, though it seems it would take a few builds to get used to the nconfig keys/buttons.
@Skaperen: 'make oldconfig' is probably what you want.
It asks you about all the new (added) options that don't exist in your config file from the previous (old) kernel, and carries forward all the other old options without asking you.
It was too long ago to remember exactly, but 1.1.46 rings a bell with me for some reason. I can certainly remember building 1.1.89 and then being really excited when 1.2 was released.
Anyway, nostalgia aside... As well as the new .35 branch, there's also been releases of 34.2 33.7 and a 32.17.
Slackware 13.1 shipped with the .33 branch and 33.7 will be the last of that branch so folks running that need to plan what they're going to do in future when new security vulnerabilities are found. Downgrade to .32 for the long-term or upgrade to .35 and chase the leading edge seems to be the choice at hand.
I'm not sure which I'm going to run at the moment but either way I don't run .0's if I can help it.
I had some problems with the TG3 driver, but found a patch that has seemed to fix it. there was a huge number of updates to this driver in the changelog.
Anyone else run into any problems with Broadcom?
I would bet that there will be a quick .1 release because there were about 10 Russian posts within the first 14 hours of release. The only thing I could read in them was TG3
john
WRONG AGAIN!
It seems the patch was not required
dhcpcd was timing out during boot
result no network
after logging in if I run dhcpcd from command line
the network hooks up fine buisness
My guess is dhcpcd is running too early during boot-up
thanks
john
Last edited by AlleyTrotter; 08-04-2010 at 08:39 AM.
Reason: patch not needed
Not sure aufs will ever make its way in a mainline kernel...
Anyhow, would I ever want to try it, I'd follow this page and pull it from git, either as a standalone kernel module or with full kernel source files, instead of patching a mainline kernel.
I did try the nconfig menu, and found it to be ugly as heck - needs some colorizing at the least, and maybe some borders around the popup boxes (one or both, to aid in distinguishing popup boxes from background text).
similar to that, minus the borders around stuff. Thinking about it now, the reason may have been due to my terminal settings (I start xterms with a launch script). Lemme go and try it with a 'stock' terminal... Back in a few moments.
Yep, that was it, Bruce.
Just ran nconfig in a black-backgrounded `konsole` and it looked like your pic. Thanks - though I still prefer xconfig for within X; I think the nconfig will be good in a VT though (where I usually don't rebuild kernels unless something went awry on the last build).
Last edited by GrapefruiTgirl; 08-04-2010 at 01:41 PM.
I still remember back when I compiled my first kernel, the 2.6.35 (way back then). But seriously, this is the first time I have attempted to compile a kernel myself. It is compiling right now. :-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.