I have just finished reading all the posts in the HAL with slack 12 sticky and found it extremely helpful. I am running a custom version of the generic SMP kernel using an initrd.gz to load my ext2 filesystem module and HAL works great.

My question is this:

Is it possible to compile the necessary filesystem support into this kernel directly to avoid using the initrd.gz? When I was creating the config file I didn't see an option for ext2 (don't ask me why I chose this partition type) and I don't want to go back to the huge kernel and lose HAL functionality.

On the other hand, is it possible to change the partition type to ext3 without losing data?

Thanks in advance and HI PAPPY_MCFAE if you're out there. I really enjoyed reading your posts.

I haven't had the experience with Slack, but I have compiled many kernels.

And I never use a initrd. I compile filesystem support directly into the kernel and install any modules separately.

Have you tried any git sources from kernel.org?

My kernel compiles are quick and completely custom to my hardware. I might be totally wrong with what your asking, but it seems in your case, its a matter of creating and compiling a new kernel.

Thanks for the response but the problem I had was that I didn't see an option to compile the ext2 filesystem into the kernel. Again, I am using a customized version of the generic SMP kernel from the slack CD.

It almost seems that I have to choose between the generic kernel to have HAL but having to use an initrd, or the huge kernel as a base with no initrd and no HAL support.

It's the first option in the File systems menu entry in 'make menuconfig'. It's called "Second extended fs support".

The configure option for ext2 is the first in the "File systems" sub-menu if you "make menuconfig", it's called "Second extended fs support". Of course you can choose to have it built-in the kernel.

If you prefer "make xconfig", the same apply: highlight "File systems", it's the first option again. Don't go in one of the sub-directories of the sub-tree, it's at the root of it.

EDIT Screenshots added to make it more clear.

Yes you can select ext2 for buildt-in; try this to see you current selectionsAnd yes you can convert back and forward (on the fly) between ext2 and 3.

I'm saying is customize your own.... download the source and create your own... and leave the old kernel in place and troubleshoot if there are any problems by using grub.

In make menuconfig you'll see under

put an asterisks in there ... and re-compile

Better yet and get your own sources and compile a new kernel and symlink the source when fully tested

Thanks everyone for the great responses. I probably just missed it when running make xconfig. I haven't compiled too many kernels so I appreciate the responses.

I will give it a shot when I get home tonight.

quick posters on this one... before I could repost your answers where there. Though compiling your own kernel and avoiding unnecessary modules, will help with a faster boot and not having to worry about a initrd.gz file.