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.
Ouch, my guess is you'd have to use a liverun like Knoppix to redo it. If I were you I wouldn't worry about it till I decieded to upgrade or reinstall. Your not really hurting yourself by having /boot as reiser. Just wasting alittle extra space, which you wouldn't be using anyway because like egag said, you only write to your /boot when you install a new kernel.
So let me see if I get this right then. If I were to reload slackware, I should run the cfdisk, let it wipe out my hda2 (which is my current " / " root partition my home's are there too) and use the CFDISK to make it reiser then, and just go thru my slack setup.
Or should i be making a partition as ext2 for /boot stuff only and a whole different partition for my / root directory and my homes?
The documentation is really confusing on this, sorry to steal the thread
A few general questions: 1. How often is Slackware released? Is it updated roughly every 6 months or when the team feels like it? 2. How many people is actually on the Slackware team? Does Patrick Volkerding do all the work himself? I was told that Slackware was a one-man show, I was wondering if the statement was literal?
1. Both: Roughly every 6 months, when the team leader feels like it. 2. Pat V. is making all the decisions, based on technical reasons, as opposed to marketing reasons, but he listens to users and is always willing to accept proper patches and good ideas from helpful contributors. In short: There's only a very small team dedicated to maintain Slackware, but there's always the Bazaar model, with contributors passing by and dropping their stuff for use in the distribution. The number of 'visitors' is unknown. But then: Slackware is the 'purest' Linux around in the sense that it avoids vendor patches; from that perspective almost everyone contributing to Linux is contributing to Slackware, making a total estimated number of roughly 25,000 developers. Calming, isn't it? gargamel
Whats the advantage of having diiferent file systems and/or seperate partions for different directories ???
Well we've already discused why you use ext2 for /boot. The biggest reason i'm aware of for putting different directories on sepearte paritions is for security reasons. For example, since /boot is alone, and shouldn't be automounted at boot, it helps protect your boot sector from being compromised by viruses. Something Windows suffers some. Also another thing, if you keep your /home seperate, that makes it really easy to upgrade without losing all your precious data. /root is kept sepearte for many of the same reasons that /boot is. Though /root has to be mounted for your system to run. Which is why we have file permissions.
But then: Slackware is the 'purest' Linux around in the sense that it avoids vendor patches; from that perspective almost everyone contributing to Linux is contributing to Slackware, making a total estimated number of roughly 25,000 developers. Calming, isn't it? gargamel
If you want more paritions than that, thats fine too. I know most slackware users set thiers up with seperate /var, /tmp, etc.
One last recomendation, your /boot should be no more than 50M max.
I have a 60 gig drive that I want to play and reload slackware 10.2 with, especially seeing how fast reiser is on an old pc I have here for data drives, I can only imagine how much better it would be on my faster pc.
Would these sizes be okay? Based on what you have above for my 60 gig drive?
/dev/hda1 /boot ext2 <----I should be 50 meg here max
/dev/hda2 /swap swap <----I have 1 Gig of ram in the pc so I do 800 meg here
/dev/hda3 /root reiserfs <-----Not sure really what size this should be in gig.
/dev/hda4 /home reiserfs <---I guess the rest of the hard drive.
With /var and /tmp <--I've heard of people crashing if not enough room so I think I just put them in with /home as it defaults for now.