Masinick and I have something in common! I started Slacking on a Micron P100 in 1995, too! I SCSI'd mine, tho, at somebody's suggestion. I bumped the memory up to 48 MB, for another $200. The box smoked! It was great! I knew almost nothing about Unix or Linux for that matter except what I could pick up at work on our SunOS 4.1.5 machines.

Slack 11.0rc3. I'm going to go ahead and make an ISO. I'll buy the disk when it comes out. My box needs a stable Slack system on it. It's brand spanking new and I've been holding off sealing the OS on it until 11 came out. I haven't loaded any of my apps back on it yet. It's killing me!!!

--vonSt

Some (neat) comments about Slackware 11.0 RC3
Anyway, it doesn't say something that we all don't know.

hello all,
I'm not to sure where to ask this.

I decided to have a look at the 2.6.17.11 kernel and it doesn't have reiserfs or ext3 in the kernel, only as a module. What is the chances of getting this changed.

You could recompile the kernel?

CONFIG_EXT3_FS=y
&
CONFIG_REISERFS_FS=y

That's what I found in the /kernels/huge26.s/config. I don't know why 2.6.17.11 exists in both /kernels/huge26.s & /extra/linux-2.6.17.11 though. Hopefully Pat'll remove it from /extra, as he's put it in the /kernels directory already. Is there any reason not to, the /extra version doesn't include a config file either.

Plus, I don't think the auto-SMP detection thing is enabled either (the HOTPLUG_CPU option is only available after enabling the SMP option, which Pat hasn't done).

I thought huge26.s was 2.6.16.x :/.

As of the last changelog entry he made it 2.6.17.11 as he felt it was very stable. I think it'll all be cleaned up by the time it's officially released.

A thought occurred to me. Most hardcore Slackware users compile their own kernels anyway especially if there is some specific use for the computer. It would be interesting if there were an option to do a custom compile as part of the installation process. It's been a little while since I've done an installation, and I'm not so much a guru to know whether the environment could be used or possibly emulated during the installation so I might just be talking out my rear... but just throwing it out there.

I missed that line in the changelog, thanks zetabill .

I remember trying a distro a while back, and there was an option to compile a kernel at install time

Cant remember what it was tho, but it is possible

Gentoo lets you do that, I'm not sure if there are others though.

I doubt Gentoo 'lets' you compile the kernel
I think it pretty much forces you to compile your own kernel

Well it has genkernel too, they give you a choice you know .

I wish there was some automagic way to configure the hardware aspects of a kernel rather than DIY as I invariably get something wrong. At least the mobo/cpu aspects, similar to what I think hotplug_cpu is meant to do.

Well I have justed had a closer look at the changelog.
And it turns out that huge26.s is a 2.6.17.11 kernel. I should pay attention to what i'm reading really.

It would be nice to have the modules for it in /a instead of /extra

None of the 2.6 kernels for slackware have these filesystems compiled into the kernel. This is one reason why you need to create an initrd after installing the kernel, source, and modules from /extra. There's a readme in that directory that explains the procedure. It's pretty much a cut and paste if all you need is reiserfs as he gives this as an example. You will then need to edit lilo.conf accordingly.

And, as someone pointed out, you could just add it on your own by reconfiguring your own kernel.