Hi,

Please explain a little better? You used Alien_Bob's; Or The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!

Hi onebuck,

http://taper.alienbase.nl/mirrors/sl...nstall-dvd.iso

That's the link I used. Sorry for not being clear. The install was pristine, as in I have never had slackware on the r51 Thinkpad.

I have since found a bug with the xfce terminal. I mounted the DVD to install KDE to see how it would go on a slowish machine. While in xfce, I opened "terminal", changed directory to " /media/Slackware-current DVD/slackware/kde" and invoked a small loop to install all *.txz packages in the directory. As a matter of course I did "su root".
This returned "syntax error near unexpected token `do'"
I switched to xterm and the command worked as expected.

I did try "pkgtool" but ran into a snag where I think the space in the directory path has baulked things. (Erm, yes I burnt the DVD in Windows, if it makes a difference).

The dialog showed up as expected but when I tried to select "Install packages from current directory" pkgtool exited with:
/sbin/pkgtool: line 404: [: /media/Slackware-current: binary operator expected
/sbin/pkgtool: line 490: [: /media/Slackware-current: binary operator expected
... You can see the path is cut short. This was in "Terminal" (xfce) and "xterm".

Can you point me to the appropriate place to report this? I took a look but I have limited time ATM.

TIA

BTW, KDE did work ok but was sluggish to start and a sometimes lagged. XFCE is much better suited to this machine, which I did suspect before hand.

Cheers, Mick

How to apply security patches and updates on a Slackware system.

Slackware now ships with the slackpkg utility which allows you to easily download and install security patches and updates with a few simple keyboard commands.

1. Use an editor to uncomment one and only one mirror of your choice on your system. Save and exit. I am running Slackware 13.37 in my example.

nano /etc/slackpkg/mirrors

Open up a terminal prompt and get root access. Then run the following commands in this order to update, download, and install security patches and any new programs that are available.

2. Check for updates:

3. Install any new programs that are available:

4. Upgrade your system:

5. Run this command if you're upgrading to a new version of Slackware or if you have obsolete packages that you wish to remove:

2 members found this post helpful.

For the first time you do all that, or if you change your mirror, before running slackpkg update, run:

2 members found this post helpful.

Hi,

For 13.37 users that update or upgrade to FireFox 11.0, from #5;
HTH!

Yeah, mine is working OK, using Eric's OpenJDK and iced tea packages.

I've been away from Slackware for too long, lured by the easy-install-and-forget-it distros.

But I'm coming back to my favorite first distro, so I'll be looking/reading through this awesome thread and the rest of the forum.

Also, the latest version is aptly named with it's numbering: 13.37!

Slackware IS 1337!!!

Looking forward to start tinkering...

It's easy enough if they run /usr/share/mkinitrd/mkinitrd_command_generator.sh.
That will, as the script name suggests, give them the command to run to make an initrd.

I still prefer to manually edit the /etc/mkinitrd.conf and run
for finer control?
Ecpecially as I usually make few initrd-s for few kernels (aech to it's own) so I usually end up even tweaking the /etc/mkinitrd.conf:

I swap the lines with the kernel version and initrd-filename, so the file name includes the version:

Hi,

I look away for a while and 'www.slackware.com Website Down?' causing panic, misinformation along with some well intentioned blog entries set a flame ablaze. 'Caitlyn Martin' does another sensationalist journalistic one sided hatchet job from misinformation about Slackware from Eric's blog (not Alien_Bob but V. T. Eric Layton or vtel57 at LQ) on DW. Even with trusted members and maintainer(Alien_Bob) stating that the information presented was not clear or correct, Ms. 'Caitlyn Martin' did not make retractions or corrections fully.

Sadly 'Caitlyn Martin' did no retraction nor correction for the damage she has done. She has attempted some damage control here but none at DW, even when she has referenced the LQ Thread: 'www.slackware.com Website Down?' with comments on DW. She is very defensive at this point in time and still do her wiggling routine. Personally when I see here name on any written document, I will automatically become a little skeptic therefore guarded. One other point; Slackware is still the oldest current stable Gnu/Linux. I really think that some people tend to resent that fact.

I have not posted to 'www.slackware.com Website Down?' thread, probably won't either. Trying to keep the blood pressure under control.

For those that are worried about the status of Slackware then be sure to check the ChangeLog.txt. You can find the ChageLog.txt on your favorite mirror. Over the years slackware.com has been down only to recover. You can still access store.slackware.com for donations or Slackware Gear purchases.

I use http://slackware.osuosl.org/ or one of the following;Overall, I am really proud of the way LQ members have handled this situation. Even when replying to 'Caitlyn Martin' here ('www.slackware.com Website Down?') and at DW (starts at comment 29).

Please remember that the problems are in the way facts or information have been presented/interpreted by members and 'Caitlyn Martin'. Caitlyn did not follow good journalistic practices therefore stepped into a big pile and her feet are still dirty. No proper cleanup!

3 members found this post helpful.

I've been away for awhile, playing around with Arch, but I decided that it's time to install Slackware on my laptop. I've set up Slackware enough to know what I need to do but I had a question about it anyway. One of the first things I do is switch to a generic kernel as when I was learning about Slackware I read about doing that. However, I almost never see anyone mention that, even when talking to new people. Do you all just huge the huge kernel? I figured the generic kernel would be a bit snappier as it has less modules to load but I've never really tested it.

I think most people do that (Except those who build there own kernels. ). The 13.37 release announcement even tells you about the generic kernel and what is needed to use it:

People probably don't talk too much about it because README.initrd is pretty thorough.

Well I know I use generic :^), but then I do build custom kernels when needed, although I align my configs as close to Slackware's vanilla builds as practical...

Hi,

For members who are subscribed to the this thread! Now is the time to post your questions for a Interview with Patrick Volkerding thread. Time to clear up some open questions about Slackware since there have been loads of FUD and speculation lately.

Hi,

Good online tool for package & file searches: SlackFinder
Still in development phase but useful.

Note the above search limitations at this point in time.

You can hover the mouse pointer over the package name for a bubbled description.

If you find a problem or issue then please provide feedback in the thread: New site to search packages containing a file