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 just installed Slackware 12.2 on my new machine last night, but I went to bed before I started my post-installation routine. I've been using Slackware since version 11 -- meaning I'm still a relative newbie. I've both upgraded and done a new installation when moving from one version to the next, but generally speaking, the post-installation routine doesn't change much.
Basically, here's what I do after the successful completion of the slackware installation:
Create an initrd so I can boot from my JFS-formatted drives with the generic-smp kernel and then reconfigure lilo. I usually have the huge-smp kernel as a "safe" boot option.
Run xorgconfig. I printed out my monitor's and video card's specs so I can fill in the information.
Create new users (when needed after a new installation).
Copy essential files from my backed-up copies of /etc /root/ and /home directories (e.g. .emacs, .bashrc, Thunderbird profiles, startup stuff from /etc, and a custom keymap I use).
Something new this time: download and install the proprietary Nvidia drivers and get them working.
Compile and install (via slackbuilds and src2pkg) OpenOffice, Kaffein, Mplayer, Frozen Bubble, Moria, QGIS, Scribus, with their dependencies.
2) alsaconf, alsamixer, alsactl store
3) nvidia driver
4) modify xorg.conf for a scroll mouse
5) link generic kernel, config, and System.map
6) mkinitrd -c -k 2.6.xx.x -m jfs
7) startx, modify inittab to 4
8) change kde language and keyboard to en_GB
9) install flashplayer plugin, flashblock, adblock and mplayer-plugins all for firefox
10) make the desktop like I like it
11) configure slackpkg and sbopkg
12) build and install wine, openoffice, pysolfc, foobillard
A few of you have captured some things that I don't do, but should (IP tables), and some stuff that I have done, but forgot (SSHD and ALSA stuff). Part of the problem is that I only deal with Slackware setup every six to eight months, so I tend to forget what I'm doing from one update to the next.
My next goal is to write this stuff down and save it for future use. There are some excellent Slackware guides out there, and they're my primary sources on setting up and configuring my favorite OS, but naturally I have my own personal settings.
Here's a follow-up question: how many use their Slackware machines as single-user desktops and how many have multiple users? My wife and I both use the computer, so I need to manage two regular user accounts. I'll probably add one for my son when he's older. He's only 3 now.
Mine is setup as a multi-user environment. Though there's really only me that ever uses it, I use different accounts for a number of different purposes and they're all more or less isolated from each other. It's probably overkill, but if I ever need to let someone else use my box, I don't need to worry about doing anything special. There's no way they're going to accidentally delete the family photos or my music collection. My own personal user account can't even do that for that matter as all such files are owned by my 'librarian' user account.
Once you get into the habit of thinking multi-user it's really not that hard to come up with a simple scheme that works without causing too much inconvenience.
1: Edit /etc/slackpkg/mirrors
2: slackpkg update
3: slackpkg upgrade-all
5: adduser brian
6: Edit /etc/inittab (set default level to 4)
8: alsactl store
9: logout as root
10: login as brian
Then it's configuring the desktop, getting sbopkg, etc, etc.
Oh yeah, I forgot getting Eric's mkinitrd_command_generator script so I can run the generic kernel - that's in the list of essentials too.
Most things have been said, but what I also do:
- put "setleds" in rc.local
- put ntpdate in rc.local
- configure my foreign keyboard (.Xmodmap)
- Xfce plugins
- configure cbq
- configure samba / rsyncd / nfs shares
- install my standard "household" scripts in cron
- compile my own kernel
edit /etc/profile.d/coreutils-dircolors.sh and add -a
edit /usr/share/jed/lib/jed.rc and remove backups and uncomment edt + emacs
install nvidia binary
edit xorg.conf to enable nvidia driver, add max resolution and change mouse type to IMPS/2
test X as root and if not self destruct