Hi all,

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:

1. 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.
2. Run xorgconfig. I printed out my monitor's and video card's specs so I can fill in the information.
3. Create new users (when needed after a new installation).
4. 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).
5. Something new this time: download and install the proprietary Nvidia drivers and get them working.
   [*}Set up
6. Compile and install (via slackbuilds and src2pkg) OpenOffice, Kaffein, Mplayer, Frozen Bubble, Moria, QGIS, Scribus, with their dependencies.

How about everyone else?

-Drew

1) adduser
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

samac

I do most of the things mentioned in Lufbery and samac's excellent posts. I will also consume some cold beverages of the malt variety and enjoy my shiny, new Slackware OS.

I do many of the things that have already been identified above. Here's a few more that come to mind...

• Setting Permitroot NO in sshd.config for safety.
  
  
• chmod 700 /home/* (A user's home directory is nobody's business but their own in my book)
  
  
• Add --nolisten tcp to Xserver defaults.
  
  
• Add my rc.firewall script to configure iptables a little more securely.
  
  
• Apply my rc.S patch to allow multiple luks encrypted lvm PVs to be supported during boot.
  
  
• Set filter and preferred device options in lvm.conf and apply my cosmetic lvm patches to the initrd to make lvm a little cleaner than the default.
  
  
• Change inittab to start all 6 gettys even in runlevel 4 for consistency.
  
  
• Change zaxis "4 5 6 7" to "4 5" in xorg.conf to prevent silliness in firefox when you scroll a little too fast for its liking.
  
  

The rest is the usual tweaking and installing of additional software that we all do (though I dare say I've probably missed something or other).

Great stuff, folks! Keep 'em coming.

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.

Regards,

-Drew

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
4: xorgsetup
5: adduser brian
6: Edit /etc/inittab (set default level to 4)
7: alsaconf
8: alsactl store
9: logout as root
10: login as brian
11: startx
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.

xorgsetup
adduser
logout
(login as user)
startx
fix all config files to my liking
(I usually run alsaconf and alsactl store at some point later, sound is not much of a priority for me)

adduser
copy over or modify config files
build & install 52 packages

But using -current means i dont have to install that much. I am planning on moving to slackware64-current eventually though.

PS. alsa configs have always worked out of the box for me.
Regarding "Add --nolisten tcp to Xserver defaults" i have that as an alias to startx to my $SHELLrc

If it's a clean installation I'd also backup my custom scripts in /usr/bin/local and restore them on the new system. I call some of them from rc.local (you can backup rc.local too).

I also compile a new kernel, with a .config file borrowed from my latest kernel compile.

I generally use fluxbox, so I restore the .menu files etc, along with other things like the .xbindkeysrc file (to use xbindkeys when I'm on XFCE).

Of course, downloading Firefox add-ons is also a standard thing for me.

• ScummVM
• Freeciv
• video codecs (I didn't see them being mentioned before)

Oh, and another nice one I always build again is gtk-chtheme I don't want to learn how to fiddle with gnome config files just to make firefox look bearable...

To add a few things that are important to me:
* touch var/lib/slocate/slocatedb
* updatedb
* Set the cron jobs to a time that is more convenient

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
adduser michael
logout
login
startx
play

First, install/enable firewall.
Second, run slackpkg
Third, add myself as user
Fourth, have fun