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.
I've been having some massive problems installing Slack 11.0. I've downloaded the ISO CDs and verified md5, and also verified md5 on the burned CD; everything is fine there.
I've tried installing from scratch at least 6 times and I keep getting errors about libs being 0-sized or not found, then when everything is done I see 100s of symlinks in / pointing to nowhere (mostly HTML and images that aren't mine.) It starts up, but nothing works.
What are you using the computer for? If it's a desktop or a laptop you'll run into trouble with the small (1GB) partitions.
I did the same as you with a 1GB /tmp and found that some programs like KDE's archiver used /tmp for tmp files and it limited the size of the tarball I could create because archiver would throw up an error saying /tmp was out of disk space.
If the computer isn't a server I don't see an advantage to "over partitioning" the drive.
I use it mostly for software development. I generally keep /boot separate so it can be R/O all the time, / and /usr for the same reason, and /usr/local to keep it separate. I keep /var separate, also, because otherwise certain kernel configs would cause it to fill whatever it's placed on. Lastly, I keep /tmp separate so I can encrypt it (as with /home and a few other things which are external.)
I had the same basic partition setup when I installed Slackware 10.0 before and it worked. Maybe it can't handle so many on the same extended partition? I've never had 8 logical partitions on a single extended before.
In any case, my DVD drive went out on that laptop since my last post and I went out and bought a nicer one. Hopefully it will work with the new one...
PS I think the problem was that /usr was too small. In fact, I'm almost positive of that now. Thanks.
I recommend that you increase /usr dramatically. My /usr contains about 2GB of data.
I personally would recommend, at most, unless you are running a high traffic server or such:
You should not need more than that. Your /usr/local is also waay to large, as is your /tmp and /var. They should be in the hundreds of megabytes at best if you want to split them, but there is no reason what so ever to do it, as it will actually increase latency unless the partitions are on separate controllers and disks.
I got Slack 11.0 and Slamd64 loaded on my new laptop. They both work great (and were the only ones I tried that would load.) As far as partitions, I guess my /usr/local is too large, but I really want /var and /tmp separate so they don't overrun /, and I like to keep as much of / R/O-mounted as possible. In my experience, /tmp and /var are the sizes I need. Remember /tmp is where ark expands archives (sometimes mine are > 1GB) and k3b stores working CD/DVD images. I also have a lot of kernel output, which takes up a lot in /var. I upped /usr to 4GB (I think.)