Remembered a couple more things to do:
edit /etc/profile.d/lang.sh, change en_US to en_GB.
edit /usr/info/dir, replace fileutils, sh-utils, and textutils, with coreutils.

Thanks for that reminder. I ran afoul of that problem and posted a thread about it a few weeks ago. It's darned strange, but an upstream problem.

I thought of at least one more thing that hasn't been mentioned yet (I don't think): set up CUPS.

I just installed 12.2 on a new computer last month, and already Slackware 13 is due out soon. I suspect I'm going to do what I usually do and wait a few weeks after the release to install the newest version -- more of a pre-installation routine. That way I can see the initial problems that folks are having and their solutions.

Regards,

-Drew

What does that do?

Well, /usr/info/dir is an index to all the info files. Some time ago, all the GNU tools were sorted into fileutils, sh-utils, and textutils - then, I don't know when, they became collectively known as coreutils. But Slackware's info/dir file hasn't caught up.

enabling unicode
compiling generic kernel, including ext2/3 reiserf and xfs, deactivate some unused things, so no initrd
enabling ondemand cpu scaling
get xorg running
copy existing data to new homedir
install a lot of software

rest is done step by step if things get necessary

With me, usually a whisky of the malt variety.

I don't think I've actually got through a cosy post-install routine without getting distracted from it into a fight with some bit of hardware and compiling something or other for it. Last time it was alsa (slackware 12.1 on my eee pc 1000h) and on my previous laptop it was the wireless under slackware 11.

I anticipate for slackware 13 it will be:
0. Flawless install on my eee pc
1. adduser
2. switch to generic kernel
3. edit xorg.conf
4. get wireless working (was rc.inet scripts before, prob wicd in 13)
5. use SBOs for openoffice, skype, flash, netbeans (jdk from extra) etc
6. upgrade to FF3.5 (if not in 13)
7. get to know kde 4.2
8. have dram of glen turret

addusr

Alsa settings

inittab settings

xorgsetup then NVIDIA upgrade

Slim down the kernel and recompile

Update Firefox and addons

For the laptop, install Aircrack-ng and patch my drivers

Set desktop to how I like

Get Slacking

I just installed slackware-current64 I'm still in shock and awe EVERYTHING WORKED OUT OF THE BOX ALL I HAD TO ADD WAS WICD AND I'M ON THE NET WITH MY WIFI

That thread is about three and a half years old, when you get to my age it's difficult to remember last week. No wonder we all forgot about it.

samac

There's not really much that I do after I've installed Slack. The main things are:

1. Add a user account for myself
2. Disable HAL (i.e. just a simple chmod -x /etc/rc.d/rc.hald, or whatever the file is called)
3. Restore my configs (e.g. X.org, .bashrc, etc) and other files from backups
4. Change default runlevel to 4

Hi,
Even simpler would be to de-select during the services setup while doing the install.

D'oh.. what a retard. I'll make sure to do that when 13 comes out. Ta .

Hi,

This will be a new system generation for me so no more VM. Since Slackware Rc1 is here the first thing for me is to create a new SystemLog for this release. I've always relied on a SystenLog to maintain with my systems. Be for a Client/Employer or whomever a written SystemLog is very important. Those brain cells seem to fade to quick. Plus the habit is hard to break. A SystemLog has saved my A$$ more than once.

I would add that I also prepare my system before any installation. Especially if the hardware is new then I will perform hard diagnostics and burning to shake out any potential problems. Again another forced habit.

Once the system is assured I will then prepare my storage for my filesystem. I know that you can do this from setup but paranoia for me plus a habit. I rarely have problems with my system due to filesystem failures. I even shake my 'swap' creation to make certain there's not a potential problem. Most of this is from my early days with 'SMD' and even 'Winchester' systems. Back then the platters were as expensive as the drives. Even with 'Gold' rate platters we would find problems. So a shakedown would be performed for hours on a new one. Then the verify.

Once this is done I will burn my media from the downloaded image. I've just got to verify that too.

I start the installation and go an have that well deserved 'MGD'.

Now for the POST installation. Most of that entails moving config files from machines and/or media.

Any toolbox files are from media, usually cd/dvd/USB.

I do like to configure my FF with available addons. But other than that I really don't install much. Except that wonderful 'VirtualBox'. I would have saved a lot of time in the day if that tool had been around. I love it.

I can setup just about any environment I want to work with. I no longer have to work with embed/controllers but I do on my dime now and when I want. 'VirtualBox' would have saved so much time in development back then.

I do generally have to tweak my configs for newer packages. But those are not always major. Sure if I need to 'xorg' change then I'll do a configure. But that to is still documented and adaptable from my configs.

I expect to have to tweak more on this release. I'm going to try that KDE. To see what everyone is crying or should I say complaining about. Just curious but I know that a simple desktop will win out. I'm not a 'GUI' man. Sure I'll use an environment with certain tools but for hardcore work on the system I'll use the 'cli'. I do like the feel of 'FF' and I can setup things to suit my needs.

After all this work I think I need that 'MGD'.

Great list. I need to add about half of these steps to my list. You may be able to eliminate the xorgsetup step. With the massive Xorg update, hardware is now detected automatically using HAL. It's worked fine on my test box over several recent -current installs. YMMV.
Here's Robbie's post on the subject