Hi,

Alien Bob has done it again! Alien Bob's Blog entry.

'KDE 4.4.0 packages' for Slackware 13. Plus take a look at 'KDE 4.4.0 on Alien Bob's site' for additional information.

Everyone is having a tissy with Slackware.com being down. In case you need Alien Bob's Slackbuilds.

:hattip:

How do you get to be an certified slacktech is there any official affiliate or training program.
i live in sweden and am going to the computer fair in kista this week are any of you guys gonna be there.

Hi,

I'm not aware of a certification program for 'Slackware'. Loads of documentation that could be used to help oneself in learning GNU/Linux therefore Slackware.

Look at 'Slackware-Links' for additional links.

Just a few general links to aid you on the road to understanding;

Slackware® Essentials
Slackware® Basics
Linux Documentation Project
Rute Tutorial & Exposition
Linux Command Guide
Utimate Linux Newbie Guide
LinuxSelfHelp
Getting Started with Linux
Advanced Bash-Scripting Guide
Linux Home Networking
Virtualiation- Top 10

:hattip:
The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!

Thanks!

Hi,

After a month of no activity with the '-current changelog' some major rebuilding has occurred.

If you want to utilize x86_32 or x86_64 '-current' prepare yourself by looking at;

'CURRENT.WARNING'
'CHANGES_AND_HINTS.TXT'
'UPGRADE.TXT'
'README.initrd'
'Slackware-HOWTO'

:hattip:
The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!

Hi,

Just a reminder that the '/usr/share/pci.ids' file is probably dated for your system. You can get '/usr/share/pci.ids' that should be current. No harm but to update this will aid you in understanding newer devices that are not identified but output as 'unknown device'. Not everyone memorizes their 'pci:id' so update that '/usr/share/pci.ids'.

I posted 'Slackware '-current' '/usr/share/pci.ids' file is dated' to prepare anyone for the new release and thinking the system was at fault. You will need to update '/usr/share/pci.ids' to rid the 'unknown device' errors. No harm, just a aid.

:hattip:

Hi,

There is a security bug for FireFox 3.6.

Look at Gazl's post for a remedy.

:hattip:

I'd expect a fixed package to be included in Slackware very shortly, so this warning will not have a very long shelf life. By the time most people read this it will most likely be patched.

However, I would strongly encourage any Slackers who are interested in system security to subscribe to the following two threads over in the LQSEC forum:

Mozilla Firefox Vulnerabilities

and

Kernel Vulnerabilities


We've discussed this latest firefox vulnerability quite a lot over the last few weeks.

Hi,

Very interesting and appreciate the links.

Some people are just blind or put FUD out there to confuse everyone. :hattip:

Hi,

Security is on everyone's mind now a days or at least it should be.

'LQ Security' wiki is a good place to start. If you use Slackware or even plan to use Slackware then be sure to check out 'Slackware Security Advisories' and if you are not on the mailing list. Be sure to follow the instructions which usually is simply a matter of downloading the necessary packages and doing 'upgradepkg packagename'.

:hattip:

Hi,

Some security fixes for mozilla apps. Please be sure to use a mirror, plus let things get updated as it does take some time to settle;

'Official List of Mirrors'

'AlphaGeek's Unofficial Mirror List'

'Oregon State' <<< one that I like to use.

:hattip:

The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!

Hi,

Just a heads up!

If you need some casual reading then look at the 'Linux Books & Online Magazines' section of 'Slackware-Links'. Loads of FREE online books and magazines to enhance your relationship with other LQ members.

;)

Hi,

Changelog cycle is at about a two week period. Some major points of interest;

This security fix is very interesting;
Yet another security fix for 'KDM CVE-2010-0436';

So guys, you should be signing up for 'Slackware Security Advisories' if you don't follow '-current'.

'LQ Security' wiki is a good place to start. If you use Slackware or even plan to use Slackware then be sure to check out 'Slackware Security Advisories' and if you are not on the mailing list. Be sure to follow the instructions which usually is simply a matter of downloading the necessary packages and doing 'upgradepkg packagename'.
:hattip:

Hi,

Please remember that when the stable becomes available to use a 'mirror'. Check out the Get Slackware section of 'Slackware-Links under 'Slackware® Mirrors:' or for you point & clickers;

Official List of Mirrors
AlphaGeek's Unofficial Mirror List
LinuxQuestions.org > ISOs > Slackware®
Oregon State << My choice
The Linux Mirror Project

For the new user to get '-current' or this 'Slackware 13.1 BETA1' I suggest that you use Alien_Bob's-script-mirror-slackware-current.sh. To download -current, create cdrom/dvd Or Alien_Bob's-script -mirror-slackware-current.sh : UK backup of script script to download the '-current' of choice ( 'x86' meaning 32bit or 'x86_64' meaning 64bit). You can either pass parameters or edit the script to create the 'ISO' medium of choice. Plus be sure to select a mirror of choice to use. The script is well documented to allow you choices. Alien_Bob is a Slackware® contributor and has graciously provided the scripts/tools.

So an ata-boy and a big Thank You to PV, Alien_Bob, Robby and Team. Plus I want to extend my personal thanks to the LQ Slackware forum members.

The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!

Patience!

Happy Slacking :D

Hi,

I've noticed a problem for some new users that are attempting to use 'Slackware 13.1 BETA1'.

'libata_switchover' has been around since 13.0 but some new users are not aware.
A new user should look at rworkman's 'libata_switchover HOWTO';

I also suggest that everyone looks at CHANGES_AND_HINTS.TXT and the other text files. Hopefully this will keep the gotcha clown away.:doh:

:hattip:

Hi,

One thing that I believe everyone should read is the 'CURRENT.WARNING' as it pertains to '-current' & 'Slackware 13.1 BETA1' is '-current'.

Plus other text files should be read as there are hidden treasures of information that may keep you from :banghead:.

Slackware 13.1 RC2
 

Hi,


Tue May 18 22:17:13 UTC 2010 Slackware 13.1 RC2. Expect a stable release when it's ready.

We're getting close to a release date! So when we do have a release be sure to seed the torrents and be patient for mirror updates.

:hattip:

Hi,

Please note that you only need CD1,2 & 3 for a full install of Slackware x86.

Torrents for Slackware 13.1, 32-bit x86

Slackware 13.1 x86 Install ISO disc 1 (A/AP/D/E/L/N, bootable installer, kernels, testing/, Slackbook)
Slackware 13.1 x86 Install ISO disc 2 (F/K/T/TCL/X/XAP/Y, L source)
Slackware 13.1 x86 Install ISO disc 3 (KDE/KDEI)
Slackware 13.1 x86 ISO disc 4 (A/AP/D/E/F/installer source, extra/, pasture/, old Berkeley DB packages)
Slackware 13.1 x86 ISO disc 5 (KDE/KDEI source)
Slackware 13.1 x86 ISO disc 6 (K/N/T/TCL/X/XAP/Y source, USB and PXE installers)

Slackware 13.1 x86 DVD ISO (everything)

Slackware 13.1 x86_64 DVD ISO (everything)

Seeders are necessary!

Enjoy!

Hi,

The dust is settling for this wonderful release. Forum activity is minimal for this release other than praise.

BUT: Once You get the ISO downloaded then you should do a md5sum check on the downloaded ISO(s) image(s) to keep from having a stack of coasters. This can be done using a M$ Windows application such as 'md5sum.exe' to check the md5sum. Or for Linux from the cli you would do;

Once you are sure that everything is OK then you can burn the 'ISO IMAGE' to your selected media. Please note that some users must burn the ISO image at a slower speed to insure a good burn. By slowing the burn speed you may insure that a good copy will be created if the image is indeed valid.

Once the image has been burned to the media then a 'CdromMd5sumsAfterBurning' check would be advised. Your burn application can fail so a check of the final media would prevent you from some possible headaches.

After you have the new release ready to install then you should read for understanding and revelation to help in having no stumbling blocks or gotcha(s);


Slackware® 13.1 Release Announcement
Slackware® 13.1 CHANGES_AND_HINTS.TXT
Slackware® 13.1 UPGRADE.TXT
Slackware® 13.1 README.TXT
Slackware® 13.1-HOWTO
Slackware® 13.1 usb-and-pxe-installers
Slackware® 13.1 README.initrd

I'm sure there are people who will have some stumbles. They should first do some searches here on LQ Or Google/Linux.


I also suggest that you look at 'How to Ask Questions the Smart Way' so that in the future your thread queries provide information which will aid us in diagnosis of the problem from a good formed question(s).

Patience!
:hattip:

Hi,

For those that wish to create ISO from a Slackware 13.1 tree then visit http://alphageek.dyndns.org/linux/sligdo/ ;

The technique is straight and easy to follow. Three SlackStars for http://alphageek.dyndns.org/linux/sligdo/ methodology.
:hattip:

Hi,

Well the dust is on the ground now! Or is that pants on the ground? General Larry Lee has to be a newbie wanna be Slacker!

I've noticed a lot of problems with users defaulting to the 'huge' installer kernel. A big problem is that most users do default to the 'huge' kernel when PV & Team suggestion is to use the 'generic' kernel for daily use with a initrd. Which if the user reads the suggested file '/boot/README.initrd' to know how to implement thus having a bootable system. I could continue with examples but it would be better for everyone that is interested to peruse the Slackware Forum.

Lot of these issues can be prevented if the new user or users would just read the docs 'CHANGES_AND_HINTS.TXT' and other associative text files available with content that will provide necessary information or leads to solution(s).

:hattip:

[edit]: If you have already done the install and wish to switch to the 'generic' kernel then the script '/usr/share/mkinitrd/mkinitrd_command_generator.sh' would be a way of generating the initrd information. I still recommend that you should read the file '/boot/README.initrd' to get some useful information. Of course if your curious then look at the '/usr/share/mkinitrd/mkinitrd_command_generator.sh' script. Alien_Bob comments his work very well.
Or use '/usr/share/mkinitrd/mkinitrd_command_generator.sh --longhelp' to get some useful information. [/edit]

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.

Hi,

I agree!

But if you are doing a new install and a newbie then the solutions are not always that apparent.
:hattip:

Hi,

Well '-current' is on the go again;

I did notice a contribution to '-current' by Alan Hicks. Wonder what the status of the new Slackbook is? Still checking on that.

It's Friday, hot outside and the beer is getting cold for tonight. No major issues with Stable. The Slackware forum is slow so things must be good to go for the Slack community.
Onward Slackware Soldiers...
:hattip:

Hi,

So you want to be a Slacker! What do I do next? Title should include 'Linux'. For those that mistake the use of the word 'Linux' as to mean distribution. General use of the term does relate to the 'kernel' when properly used.

If you really want to understand Slackware then I suggest that you investigate by looking at 'Anatomy of the Linux kernel'. Excellent 'History and architectural decomposition' from IBM that will provide some insight and understanding for the Linux kernel. This site and composition has some excellent resources along with useful links to enhance your Slackware experience;

A short tour of Linux history
Introduction to the Linux kernel
Properties of the Linux kernel
Major subsystems of the Linux kernel
Interesting features of the Linux kernel

'Downloads and products'

I do suggest that IBM site is an excellent GNU/Linux resource but not the only one.

Read on! Become a knowledgeable Slacker!

:hattip:

Hi,

Well things are still happening in the Slackware world.

You should subscribe to 'slackware-security' Mailing Lists as a new user or a oldie so you can be aware of potential problems;
Looking at the Slackware-current ChangeLog for x86 (32-bit) Architecture or x86_64 Architecture along with other arch is one way but signing up for the 'slackware-security' Mailing Lists is the better.

I have stated this many times but think it's to the users advantage to be on the mailing list(s) for Slackware. That way you can make the decision whether or not to make changes to the system to insure things are secure.

:hattip:

Hi,

For those of us who like to have the best and greatest:

Dugan has done it again with the new update. Very Nice!

If you like a beautiful looking Slackware install for the Desktop then look at Dugan's Site.
:hattip:

Bradley's 1.) Off Topic, and 2.) A day late
 

Yesterday was my birthday.

I got a congrats from LQ and a bazillion other sites too.

But this year was especially significant ;) I spent most of the day informing people that on this particular birthday of mine, The Roman Empire fell exactly one thousand, six hundred years ago.

Wow. Let's hear it for Alaric and his merry band of Goths!

Late Happy Birthday and three cheers for the Goths!!! What did the Romans ever do for us?

Imperialism.

Hi,

Thanks!

Caesar salad? Some good red to go along.
:hattip:

Hi,

Happy belated birthday!

I know what my parents were doing so many years ago one winter night.

On my birthday, pretty normal day here on the farm. Cool day to move hay yesterday. Then share cake & ice cream with the family later in the evening. Of course, my beer while mowing the front pasture parameter. Waved to the locals as they passed :D. Nice cold beer goes down so easily. I've got to get that cooler mounted on the tractor so I don't have to get off to get one.
:hattip:

:tisk:
Don't drink and drive, Gary.
:)

Especially don't drink and operate heavy farm machinery. One handed typing doesn't sound like fun. So there.

A belated happy birthday, old son.

The Romans gave us socks and sandals...socks I use but I hav,nt got the sandals... !

Hi,

I enjoy my MGD 64 on and off the tractor. When I'm in the field there's only 3 in the small cooler. But others in the beer fridge. MGD64 light is a low alcohol. Doesn't taste to bad on a hot afternoon. One beer, one bottle of water. I stand by that on a hot day.

BTW, the tractor steers itself in a straight line. I just turn corners. Looked at the pasture this afternoon before spaying and the lines were pretty good. Now, the sprayer is another story. Pain in the butt, literally.

I notice some changes since I've not been attending to the forum. What happened to the 'Thanks'? What's that little green tag below the posters information?
Few days away, loose attentive points or am I just losing it? :)
:hattip:

EDIT: Just noticed more tags below. Boy, jeremy is a changin things. :)

Those little green squares are part of a new Reputation thing that Jeremy's trying out. Wade through this thread:
http://www.linuxquestions.org/questi...system-828421/

Hi,

Thanks!

Hi,

Gone for a few days and things really change here on LQ. LQ Reputation System is a very long yet informational thread relative to the new rep system that 'jeremy' is rolling out. Looking for member feedback there but http://www.linuxquestions.org/questi...n-beta-829543/ is the announcement thread. You might want to look at 'Reputation' to get a clear overview FAQ in the Board FAQ.

Right now I have no opinion in regard to the rep system. I've been reading the referenced threads and still forming a position. 'jeremy' has LQ & the members in thought when rolling out this system. The 'Thanks' system just wasn't worth the efforts. Just a merit and no way for feedback other than within the posts content. This big brother method may be to everyone's benefit. In terms it's an expansion of a merit ranking system that will aid in policing the forum(s).

The reason for posting in the 'So you want to be a Slacker! What do I do next?' is to provide exposure to subscribers to this thread. 'jeremy' is looking for feedback on this subject!

:hattip:

Hi,

Looking at the Slackware-current ChangeLog: x86 (32-bit) Architecture: Those of you that are adventurous then look at the packages mozilla-firefox-4.0b4-i486-1.txz from -current. Sure it's beta but why not have some fun.

:hattip:

Hi,

I've had a little time on my hands today. So some maintenance & changes to 'Slackware®-Links' have been done. Hope you like whats been done. I've got more to do but will do in stages.

It looks like things have settled somewhat for the LQ Reputation System thread. I'm curious what fellow Slackware users have to say?
Please respond within LQ Reputation System thread.

You might want to look at 'Reputation' to get a clear overview FAQ in the Board FAQ.

Onward fellow Slackware users! :)
:hattip:

Gary
According to his blog, Eric has a new mirror (or site, or whatever).

Hi,

Thanks for the heads up & link!

:hattip:


EDIT: Added AlienBase mirror link to Slackware®-Links

Hi,

Just when I think 3.6.8 has been polished the way I want then;

I know this has been said many times before but Security Advisories
sign-up is a must for any Slackware user!
:hattip:

Hi,

New Adobe flash player for Linux, look at http://labs.adobe.com/technologies/flashplayer10/ for the announcement and downloads.

Alien_Bob has created Slackware packages for the new Adobe flashplayer (32-bit or 64-bit), so you can grab those from http://slackware.com/~alien/slackbuilds/flashplayer-plugin/ .

Happy slacking!
:hattip:

Firefox Beta6 is in /testing on -current. I am presently using it with no problems. Its a bit faster, but speed is not my first priority - functionality is. Good so far!

Hi,

Yes, I linked it earlier. I do need to get back to some testing but got other things that are taking priority. :( :)

I noticed in the changelog this mourning:
To many things to do and daylight is burning.
:hattip:

Oops - I need to go back a ways in this thread before a post.

Hi,

SlackUp!

'David Woodfall (aka dive)' has provided 'manpages' for mkslack 3.5.mkslack 3.5 as described;

The 'mkslack - a SlackBuild generator script' is another tool to aid the user when working with those packages;
"Where there is no vision, the people perish."-Proverbs

HTH!
:hattip:

Now this is a dawning of a new age of building @Slackware :)
Stevan C.