LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-11-2005, 11:57 AM   #16
xaos5
Member
 
Registered: Dec 2004
Distribution: debian and slackware
Posts: 217

Original Poster
Rep: Reputation: 31

can you actually compile the filesystem into it so you don't need it? I noticed the 2.4 kernel in lilo.conf didn't have an initrd line so I'm guessing you can. So much stuff to learn so little time. thanks for all the help but when I get the time i'm going to just recompile the kernel because the computer is so old I think I might need some special stuff built into it.

I noticed in the kde control center there is a list of kernel options and you can save them and load them. Has anybody built a kernel this way?
 
Old 03-14-2005, 03:18 AM   #17
bigearsbilly
Senior Member
 
Registered: Mar 2004
Location: england
Distribution: Mint, Armbian, NetBSD, Puppy, Raspbian
Posts: 3,515

Rep: Reputation: 239Reputation: 239Reputation: 239
yeah.

I don'y have initrd on mine.
Just compiled reiserfs in.

I use grub though.
 
Old 03-14-2005, 04:01 AM   #18
gbonvehi
Senior Member
 
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145

Rep: Reputation: 53
xaos5 if I'm not wrong KDE only supported 2.4.X kernels and I wouldn't recommend configuring one in that "way".

You can compile stuff in your kernel directly built-in, that means, it will be a big "file" containing all you need, or built them as modules (kind of "drivers", separate files) that will be loaded later on boot process.
The reason you must have your filesystem support built-in is that the kernel when is loading doesn't know how to read your partition's filesystem (reiserfs), because the module it needs to read it is inside that filesystem that's still unknown!
I hope i didn't mix all your head, but I guess you'll get the point.

By the way, precompiled means it's already compiled, so you're actually compiling your kernel, not usinga precompiled one

Last edited by gbonvehi; 03-14-2005 at 04:04 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel 2.4 in Zipslack (Waring: unable to open an initial console | Kernel Panic...) kurtamos Linux - General 2 05-10-2006 12:58 PM
Kernel-Patch Debian Logo 2.6.2 not correctly working for custom kernel 2.6.11 smp deepclutch Debian 3 06-27-2005 03:59 AM
kernel-source-2.6.5-7.src.rpm requires kernel-dummy to build!? fizzdandantilus SUSE / openSUSE 5 12-02-2004 12:48 PM
kernel panic: try passing init= option to kernel...installation with Red Hat 9 kergen Linux - Hardware 1 09-30-2004 03:28 AM
kernel memory + slabinfo.. + possible reasons for kernel space allocation failures!! premenjit Linux - Software 1 09-28-2004 04:13 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:27 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration