Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
04-10-2004, 02:18 PM
|
#1
|
Member
Registered: Mar 2004
Posts: 53
Rep:
|
things to do before and after installing slackware
Hi everyone. I have been using fedora for a while and now have decided to try slack as i have heard lots of good comments about it. Have just order the CDs, meanwhile wanted to know what are some of the steps that i need to know before installing slack and aslo any important configuration that i need to do after i have install it. Any suggestion from you personal experince or any good websites that you know. Thanks, sorry if my english doesn't make sense but it is not my native language.
|
|
|
04-10-2004, 02:31 PM
|
#2
|
LQ Guru
Registered: Sep 2003
Location: Danville, VA
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep: 
|
the slack book should have some answers for you, it is a little dated, however it contains a lot of good info. you can find it here
http://www.slackware.com/book/
you should look into checkinstall as well, it makes package management in slack much easier. you can find it here
http://www.linuxpackages.net/search_...nstall&ver=9.1
some other things to look into would be swaret, and slaptget, i personally have no experience w/either, but, a number of users here seem to like them both. hope that gets you going in the right direction.
good luck.
|
|
|
04-10-2004, 02:43 PM
|
#3
|
Member
Registered: Mar 2004
Posts: 53
Original Poster
Rep:
|
thanks very much, am very impressed how quickly got an answer, i will have a look at your suggestions.
Tho, i am very intersting at some personal experience such as things that have gone wrong and how you solve them, or tips in configuration for best perfomance.
thanks
|
|
|
04-10-2004, 03:08 PM
|
#4
|
Member
Registered: Oct 2003
Location: teddy bears Land
Distribution: Slackware 10
Posts: 176
Rep:
|
well for your last questions about when things goes wrong how to solved it, the same way you could solve it under debian, suse, redhat, mandrake, etc. they all linux box, and maybe they act in different ways but they always have the same way of solutions. for example i already had have troubles in slack, which i have solve the first one was upgrading my kernel of 9.1 to current. and i forgot to do /sbin/lilo and didn't have another choice of kernel image to boot, so when i reboot i couldn't login to slack. How i solve it? well the stuff of linux single in the prompt didn't work (in redhat or mandy do) so i have to put CD1 and boot up whit it, and login then mount the root partition whit mount /dev/hda1 /mnt then the process is the same as all the others linux box,
chroot /mnt /sbin/lilo
others problem i have whit slack, are being when upgrading packages and those packages need some libraries files that 9.1 have not update, so cause slack doesn't have dependencies stuff is hard to find out what happen, but thanks god it exist ldd command  so i just give and ldd executable and voila i found out the dependencies stuff. i have solved all my slack problems if that help you. and i did have before old problems whit mandrake and redhat that i never could solve. like configure my sound, ethernet, etc. slack is not so friendly like redhat, but slack have more hardware support, it's upgrade are less than redhat for the fact that slack is less vulnerable, slack runs faster than most of the distros out there, slack let you install what you really need and not all that what the distro want (like friendly distro).
And of course, have to thanks linuxquestions forum cause if you have some problem whit slack, these people try all the possible ways to solved your problem.
|
|
|
04-10-2004, 03:21 PM
|
#5
|
Member
Registered: Mar 2004
Posts: 53
Original Poster
Rep:
|
Thanks for all your input. Sorry if i come up with all kind of questions, i just what to know what to do. So my other qustion is whether slack can use GRUB as a boot loader or it can only use lilo. I have heard that grub is better and since fedora has allready installed it, i thout to keep it, but i guess its impossible. Any suggestions out there?
|
|
|
04-10-2004, 03:32 PM
|
#6
|
Member
Registered: Apr 2003
Location: Sweden
Distribution: Slackware
Posts: 242
Rep:
|
Now I don't know how new you are to Linux, but a look at the tips and guides offered at Simply Linux is a good start.  Of course, read anything with a critical eye, and check many different sources. Forums are always a good thing.
One of the most important things (if not THE most important thing) to do after an installation is to harden the OS. Create appropriate user accounts. Read up on netfilter configuration and set up a good firewall. Read about the daemons, run only the ones you (or the OS) will use.
Then plug your network cable in.
And so on. After that, you're ready for the really tough part; choosing a desktop background for your WM.
As for the bootloader...of course you may use whatever you prefer. Personally I use LILO; it works just as it should and never caused any problems whatsoever, so I can't see any reason to change (GRUB is possibly "more configurable", but hey...I just want the bootloader to boot my OS, it doesn't have to display error messages in 24-bit color or clean the toilet for me  ). I don't know if there's a situation which LILO can't cope with but GRUB can, but such a situation seems quite extraordinary.
|
|
|
04-11-2004, 06:38 AM
|
#7
|
Member
Registered: May 2003
Posts: 56
Rep:
|
some things you'll want to take care of right away if it's a desktop machine are sound--add your users to the "sys" group usually takes care of it, and running alsamixer and alsactl store as root to bring it up.
The other thing I've seen a lot of questions on is getting scsi emulation to work--for things like burners, etc. In your lilo just add a line that says...
append="hdx=ide-scsi"
under the boot section.
Those are two of the repeat questions I've seen--
Good luck.
|
|
|
04-11-2004, 08:22 AM
|
#8
|
Senior Member
Registered: Sep 2003
Location: Indiana
Distribution: Slackware 15.0
Posts: 1,273
Rep:
|
A couple suggestions. Read the book listed above. Search this forum. THe search button is at the top. It is unlikely that you have a problem that has not been addressed already. If you don't find it here, google is your friend.
A FAQ http://wombat.san-francisco.ca.us/fa...c/cache/1.html
http://www.slackfiles.net/index.php
An attempt to update the book http://slackbook.yoshiwara.org.uk/
There area also many linux help sites. Since Slackware is fairly vanilla many of the fixes will work. Good luck and hope you enjoy your foray into Slackness.
|
|
|
All times are GMT -5. The time now is 01:09 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|