SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Bravo Gene! I love your site. You explain the whole Slackware install process nice and simply. I already helped several of my friends switch from windows to Ubuntu, and I'll probably use your guide to help lure them into Slackware (I agree with you, ubuntu is quite buggy! but it's nice for newbies)
How long does it take someone who is experienced with slack to actually install and configure a basic slack system?
A system comparable to a winsxp install.
For me the best time frame would be around 20-30 minutes. Dictated if it is a new install and configuration of partitions for a particular install. Polishing of the install around a 5-10 minutes and that too will be dictated by the install type. Desktop or server, each will have different needs for particular configurations. But each for a default install would be around the same time frame dictated by the hardware in use. As time passes a user will add more to the toolbox to enable scripted operations that will enhance one's abilities.
Just remember that wall clock and system console time are not always comparable. You're always waiting a period for systems to resolve/complete the operations that you have requested.
“What we wish, we readily believe, and what we ourselves think, we imagine others think also.” - Julius Caesar
Last edited by onebuck; 03-10-2011 at 08:12 PM.
Reason: grammar correction :) edit2: font errors
Less time than it takes to merely complete the stock installation process for Windows 7.
You're actually trying to compare apples w/oranges. You asked how long it takes to install and configure a Slackware system to one's liking, as opposed to how long it takes to just install.
Two different things.
So I'll pose this question back to you:
How long does it take YOU, to configure a Windows box to your liking (i.e., AFTER the install)?
Just remember that wall clock and system console time are not always comparable. Your always waiting a period for systems to resolve/complete the operations that you have requested.
I'm not really worried about time to install, as I have plenty of time and since you guys got me hooked on VB, I can take my time and learn the system. I have a lot of reading up to do it and not have to do a lot of install and reinstalling like I did with my debian system. I do have it installed I just have to configure it.
Quote:
How long does it take YOU, to configure a Windows box to your liking (i.e., AFTER the install)?
Until I started dealing with debian, I really didn't have a clue of what had to be done to configure wins. In fact I didn't know that you could choose how much of the drive wins takes. Stick disk in take free space install, no matter how big the drive was. If it gets virus reinstall again.
How long does it take someone who is experienced with slack to actually install and configure a basic slack system?
A system comparable to a winsxp install.
I hope I should never have to perform a microsoft installation on my PC to measure this comparison...
I've been trying to catch up on some reading lately. Big fan of Linux Magazine. Some articles stand out more than others;
Quote:
Linux 2.6.37: Scalability Improvements Abound
While 2.6.37 might be considered a quiet release, there are some very nice scalability improvements for file systems and one cool new feature that warrant a review. Read This
Personally, I will be doing some work on new system builds in the next few weeks. Hardware is all here and setting by the bench awaiting the magic touch.
Looking forward to experimenting on new hardware and setting things up for the new sys-gens.
How long does it take someone who is experienced with slack to actually install and configure a basic slack system?
A system comparable to a winsxp install.
:chuckle:
Typically 20 - 30 mins and I am on the Internet. I create my user account, add a downloads directory and download fwbuilder and its libraries ulogd, webmin, streamtuner (gotta have tunes), wireshark; sometimes I will install gnome slackbuild. Usually I can take my monitor off the slackware machine in about a couple of hours.
I use slackware 13.1 on an old P-III 800Mhz as a firewall and DNS and Samba server. It took about 20 mins to get it on the Internet,another couple of hours to compile and install fwbuilder and ulog. And part of the time involved cooking and eating dinner.
My last XP install took 3 days. The install took about 30 mins, the updates took a couple of days. Sorry I'm too easily bored to watch a computer update. I've also installed Vista with the same results. Windows 7 seems to go a little faster. I installed Red Hat net install, it took a couple of hours. Again I don't sit there and watch it.
Longest install I've done has been FreeBSD on the P-III installing from ports, not pretty.
The time it take is going to depend on your hardware and more so, what you install.
excerpt from Current (pre-release) ChangeLog for x86_64
Wed Mar 9 05:52:06 UTC 2011
Hey folks, I think it's time for Slackware 13.37 (hopefully this helps
make up for our lack of code names) release candidate 1!
After a lot of testing and consideration, we've decided to go with the
recently released 2.6.37.3 Linux kernel which seems to work best for X,
contains support for Speakup, and looks like a better kernel branch to
be using as we move forward.
Please test so we can have a stable release soon. :-)
Yes folks… we have a release candidate for the next stable version of Slackware. Its version mumber is going to be “13.37” as could be expected… it was too tempting not to be used, after we had “12.34567890″ for a little while during an earlier development cycle…
And to accompany this event, I have also made available a new set of KDE packages. It’s KDE 4.6.1 and the packages have been built on Slackware 13.37-RC1.
Alien_Bob's new Multi-Libs upgrade;
Quote:
Slackware -current’s kernel has been updated to 2.6.37.3 (something many of you probably did not expect) as part of the large update leading to the first release candidate for Slackware 13.37.
excerpt from Alien_Bob's Blog;
I also updated the content of the slackware64-compat32 directory which holds a copy of all the packages which are created by running the massconvert32.sh script (to make it easier for you if you have your doubts about how to use that script).
Thanks Eric!
Last edited by onebuck; 03-09-2011 at 03:30 PM.
Reason: add link reference
I've put up an article related to the release HERE on my site as well, with pointers back to your post above too, in order to make it convenient for others to find everything they need all in one place.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I've reported on this at my site too...
