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.
Well, I decided to take the plunge into linux by converting my main dev server box from win2k to slackware linux. Being new to linux and any distro install process, I have no idea how long to expect the unprompted install to last. My install is running now and seems to be taking a while and I want to make sure something isn't wrong. If someone could give me a ballpark time on a full install, I'd appreciate it.
8.1 iso cd
60G ata100 drive
complete unprompted install
Though I've never really timed it It's never taken me more than 15-20 minutes to install and configure any of my slackware boxes. Even on my P Pro 180 server box...the only thing that might take a bit is recompiling, obviously depending on what you recompile...
15-20mins, eh... well mine's been running for over an hour and is still on the A series package. It is progressing though.... just very slowly. I'm not aware of a command to monitor the progess of the install. The drive seemed to partition fine (seperate ones for /,/usr,/home,/var,/boot) and detection of the cddrive went fine. I'm at a loss.
I've installed Slack on my 200mhz 64 megs of ram with a 40x Cdrom in about 15 minutes flat. Though I didn't install X but I did manage to have the FTP, NFS and everything else I needed to run on it in another 15 minutes or so.. all nicely configured.
It shouldn't be taking an hour anD still on the A package series.
My other installs with about everything installed usually around 15 to 20 minutes tops.
Well, I did swap in a different cd drive (AOpen 52x) and the install time did speed up tremendously. Right around the 20mins mentioned for total install... which is sweet for an OS install.
The drive I had issues with was an NEC CDR-3001B 40X drive. A standard OEM drive. I actually had 2 of the same model from different OEMs (Micron and Gateway). One drive was manufactured 1999 and the other 2000...Certainly not 'old' drives. Both have the same problem, whatever that problem is.
I actually let the install finish using this model drive (at the time I knew no better). It took over 6hrs - maybe longer I fell asleep.
In addition to being incredibly slow, This NEC drive apparently corrupted the install data. You see I didn't wipe the partitions after the long install, thinking it just took a while but did finish in full.
After the files copied, The setup program barfed about not being able to find "passwd" to set the root password. And that's when the trouble started. Setup never made it to lilo, nic setup, gnome config, and anything beyond that point, but claimed to finish and said to reboot. Wrong. So of course I think I can just do some searches and fix the skipped parts. That was my big mistake. I did manage to get lilo working after some time, but had kernel panics and initial console errors that were really frustrating to debug beyond that. So I reformatted the drive and ran a full-install using the Aopen 52x drive in 20mins...
I found some references on the net about DMA issues with linux installs and the symptoms very closely resemble mine. So I'll take that explaination and go forward with some research as I need to use the NEC drive with linux.
Moral of the story, if a full install takes more than 30mins something is wrong and more than likely its DMA related.
Not to worry though, outside of all my previous troubles, I am enjoying the raw power and speed of my fresh slackware install...
I had a problem with a computer of mine, we thought it was the crappy CDROM which was screwing up the installs but it was really a bad stick of ram...in the middle of the install, a random package would crap out and say it couldn't be read. I couldn't install properly and kept getting that passwd error and certain config options didn't come up. I thought the CDROM was bad, but I swapped the ram out for some new ram and the problem was fixed.