Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
11-05-2013, 01:00 AM
|
#1
|
Member
Registered: Jun 2004
Location: Minnesota, USA
Distribution: Slackware64-stable, Manjaro, Debian64 stable
Posts: 531
Rep: 
|
mkinitrd suggestion / ext4 support in generic kernel question
I sent this to Patrick, but figured I could ask the ext4 question here: Why isn't ext4 fs support included in the generic kernel? How much overhead would it add?
Quote:
Minor suggestion...
I switched from the huge to generic kernel, forgetting generic doesn't have ext4 support.
So after I got back in , I ran mkinitrd to create a RD image. mkinitrd ran fine and exited with a message to re-run lilo if I use the newly created image...
but didn't remind me to edit lilo.conf to use the new RD image.
In my mind, if it's worth it to mention to users to re-run lilo, it's also worth mentioning to add the appropro "initrd =" to lilo.conf,
or add ext4 support to the generic kernel .
|
|
|
|
11-05-2013, 03:21 AM
|
#2
|
Senior Member
Registered: Feb 2006
Location: Outer Shpongolia
Distribution: CRUX
Posts: 1,503
|
well, the README.initrd is right there in /boot and says:
Quote:
4. Now that I've built an initrd, how do I use it?
Now that you've got an initrd (/boot/initrd.gz), you'll want to load
it along with the kernel at boot time. If you use LILO for your boot
loader you'll need to edit /etc/lilo.conf and add a line to load the
initrd. Here's an example section of lilo.conf showing how this is
done:
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-3.2.28
initrd = /boot/initrd.gz
root = /dev/sda6
label = 3228
read-only
# Linux bootable partition config ends
|
|
|
|
11-05-2013, 04:11 AM
|
#3
|
Member
Registered: Sep 2011
Posts: 925
|
Quote:
Originally Posted by Andy Alkaline
Why isn't ext4 fs support included in the generic kernel? How much overhead would it add?
|
Short answer:
Code:
-rw-r--r-- 1 root root 115960 Jun 21 06:32 /lib/modules/3.8.13/kernel/fs/ext2/ext2.ko
-rw-r--r-- 1 root root 344399 Jun 21 06:32 /lib/modules/3.8.13/kernel/fs/ext3/ext3.ko
-rw-r--r-- 1 root root 806287 Jun 21 06:32 /lib/modules/3.8.13/kernel/fs/ext4/ext4.ko
(Yes, that's an -older current kernel.)
One could also remove ext2 and ext3, because ext4 should be able to mount ext2 and ext3 filesystems, too.
|
|
|
All times are GMT -5. The time now is 12:47 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|