The Ultimate "When Will The Next Slackware Release Arrive" MegaThread
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Slackware was the VERY FIRST GNU/Linux distro I ever tried, WAY back in 1995. ... On the other hand, that old software absolutely SMOKED on an old Micron P100 - a 100 Mhz Pentium with a 2.1 GB hard drive, a 2X CDrom reader and 16 MB of memory.
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!!!
That's what I found in the /kernels/huge26.s/config. I don't know why 188.8.131.52 exists in both /kernels/huge26.s & /extra/linux-184.108.40.206 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).
Last edited by Mr Marmmalade; 08-26-2006 at 04:53 PM.
As of the last changelog entry he made it 220.127.116.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 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.
Last edited by Mr Marmmalade; 08-26-2006 at 05:20 PM.
I decided to have a look at the 18.104.22.168 kernel and it doesn't have reiserfs or ext3 in the kernel, only as a module. What is the chances of getting this changed.
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.