So I got slack 13.37 installed and X working? How do I update my box (security updates, application enhancements, etc.)? Is there a GUI tool to do auto-updates or manual updates? Firefox is out of date. How should I go about getting FF v6.02 on my box?

Thanks in advance.

Ok so I...

# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all

Small problem... I dropped cordless phone and it hit the enter key with "upgrade-all" window open before I could read through the list. Ten trillion lines of text whizzed by my terminal window, while I was distracted by a phone call. Is there a log with all the output I can review before moving on to the slack builds and sbopkg steps?

Not that I am aware of. But upgrade-all does only this: Download the new packages, delete the files from the old versions, extract the new files from the packages. Normally nothing to worry about.

Hahahahaha sorry man, but I read that just after reading your signature (son, me,me...) and I couldn't help to roll and laugh ! You made my day... So you think Tony Stark, Einstein and Tesla would use a cordless phone just up to the enter key after typing for fun ?? Hahahahahaha... Sorry to be out of topic but I couldn't help myself .

It doesn't really matter, just run it again and if it has already done the upgrades it will just upgrade them again with the same package. First thing you should do though is open a text editor and open the file /etc/slackpkg/mirrors and uncomment a slackware mirror of your choice, there are many mirrors to choose from, just take your pick. I use the following below, to enable it just delete the comment like so

#ftp://slackware.oregonstate.edu/pub/...ackware-13.37/

to

ftp://slackware.oregonstate.edu/pub/...ackware-13.37/

then you can run
# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all

After you've successfully done this you can then begin installing third party packages from www.slackbuilds.org using slackware build scripts. Sbopkg is a just a gui "front end" to use with www.slackbuilds.org. I would at first download some builds by hand over at SBo.org and compile them manually, its still very easy but more time consuming, once you get the idea of what is going on then move to using sbopkg.

@NoStressHQ That command will fail spectacularly. 'man rm' and look at --no-preserve-root

Hey guys, my question relates. I am a new slackware user and I still haven't been able to install a package, I read everything but im stuck,

Give a bit of detail as to what stumps you.

Check out SlackBuilds.org for extra packages that aren't on the DVD.

To install any pre-built package do this:

installpkg /"path-to-directory"/"package-name".txz (or .tgz, .tlz, etc.)

For Tarball source packages you may need to find a SlackBuild script package (at slackbuilds.org or various other places) or use the src2pkg program that can be Googled.

Remember, you will need to build an install ANY dependencies before installing the main package and even then some dependencies have dependencies themselves.

src2pkg runs like this:

src2pkg /"path-to"/"tarball-source".tar.gz

while SlackBuilds run as:

ARCH=(i486 or x86_64) "other_options_listed"=(yes/no/etc.) ./"package".SlackBuild

examples:

To install gnome-mplayer 1.0.0 on a 32-bit system download the source and slackbuild and then run this command inside the SlackBuild folder with the source gzipped-tarball inside:

ARCH=i486 GCONF=yes ./gnome-mplayer.SlackBuild

then you'd execute:

installpkg /tmp/gnome-mplayer-1.0.0_i486-1_SBo.tgz

You'll get the idea. BTW... don't be afraid to hose the system a few times before you get it right and have to reinstall it.

I hope you didn't think I was serious ? I was just having a big laugh picturing myself the sitcom "You know my son, because the bests are using linux..." and "paf!" the phone falls on the wrong key at the wrong time and the previous self assured man becomes a victim of the fate... The signature strikes back...

:: completely off-topic but...::

@NoStressHQ: We got a full round of lols at my place. My son and my neighbor's son was laughing at your comment. It took the two of them 4 tries to explain the jokes to my wife without laughing mid-way. All the laughing they did while explaining the story and adding in their own follow-up jokes, got my wife laughing.

One big happy family...

I'm assuming you're using SlackBuilds.org for most of them. For slackbuilds packages you download the SlackBuild file, and the source file (some of them are split into 64-bit and 32-bit, so download the one respective to your Slackware).

Here's an example:

I want to download, chemtool. So I look up chemtool on SlackBuilds.org, it finds me this link here:
http://slackbuilds.org/repository/13...emic/chemtool/

I download chemtool.tar.gz.

Then I download the source, chemtool-1.6.9.tar.gz (as of today at the time of this post). You'll notice that the source's always have the version number on them.

Then extract chemtool.tar.gz, I prefer:
but you don't really need some of the other options like -z (they just help me personally).

Then a folder titled "chemtool" will appear. Move the source file (chemtool-1.6.9.tar.gz) into this folder, and type:

The [TAB] is the tab key itself, don't actually type out [TAB]. This will automagically set it to ./chemtool.SlackBuild. For some programs this won't always happen, so for those programs you will have to type out

Afterwards, you should get a new file in your /tmp directory (set their by default). Then:

Usually it's something like chemtool-1.6.9_SBo.extension, the extensions vary on several different programs.

Three things to note are, by doing this you're installing by source. Which means, that unless the SlackBuild package is in the slackpkg repositories, you will have to update the program yourself. Luckily there's sbopkg to do this for us.

If you update to the newer one before sbopkg is synced with it, sbopkg will say yours is older (aka 'different') but just give it a few days and it should be okay.

Some programs which are no longer supported may have really old versions, and you'll have to install these by source yourself from their official website. When you extract their file, you should get a "README.txt" or "INSTALL.txt" file that tells you how to install it (and make any desirable changes).

You may want to place your folder (that you got from extraction) into /usr/src for organizational purposes.

You can also do many of these commands at once by separating each command with a semicolon. So something like:

===========================================================
I wouldn't say there's anything to worry about unless you didn't blacklist Alien Bob's compat32 files or something. Which, I'm assuming you don't have.

Basically everything should be updated now, so Firefox should be 6.0.2 (check to make sure).