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.
How can I obtain kernel configuration for newer or non-stock kernels?
That is, how Pat is making one?
Naturally, I could go through the configuration process (I know the whole thing pretty well) on my own, but this time I'd just like to get .config for generic kernel and don't bother. I need it for 4.2 line.
It's in the source directory on the Slackware mirrors.
Yep, I know that.
What I want to know is what is the way that Pat uses to make .config's.
I need to create one for 4.2.x, which is not available in slackware/ neither in testing/ for the current current.
I need the generic .config and I don't want to go myself through the configuration stages.
I would "make olddefconfig" as suggested by Tonus then run /usr/src/linux/scripts/diffconfig to quickly spot possibly interesting new options that could have been overlooked.
I would "make olddefconfig" as suggested by Tonus then run /usr/src/linux/scripts/diffconfig to quickly spot possibly interesting new options that could have been overlooked.
Then maybe it would be better to run make oldconfig? diffconfig will give you the difference, but only with cryptic symbols, whereas oldconfig would also display the description.
BTW, my last configuration was done with oldconfig and the enter key pressed down till all the new options were answered with theirs defaults
I do make oldconfig with the generic config, holding down the enter key until it's done. Then I do make menuconfig and change ext4 from a module to a compiled-in.
I do make oldconfig with the generic config, holding down the enter key until it's done.
make olddefconfig might prevent your finger from getting stuck to the enter key
Quote:
Then I do make menuconfig and change ext4 from a module to a compiled-in.
You can also specify ext4 module to the mkinitrd (since you're using generic anyway).
Quote:
zcat /proc/config.gz
That's of no help. This gives you the .config for the currently running kernel. What we're trying to find out here is, how do you create .config for a kernel that is not present in stock Slackware.
I think the main point of building-in ext4 is that it means you don't need a initrd, which makes kernel updates much easier. At least, that's why I do it.
IMO, now that ext2/3 have been removed upstream and the ext4 module services all 3 filesystems, it makes even more sense to have this one built in to 'generic'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
