So you want to be a Slacker! What do I do next?

Bruce Hill · 08-01-2009, 10:11 AM

onebuck,

In your Slackware links wiki post, the link to ESR's
How To Ask Questions The Smart Way has an incorrect
link and points to a Wikipedia Netiquette article.

onebuck · 08-02-2009, 07:02 PM

Hi,

Quote:

Originally Posted by Bruce Hill

onebuck,

In your Slackware links wiki post, the link to ESR's
How To Ask Questions The Smart Way has an incorrect
link and points to a Wikipedia Netiquette article.

Thanks Bruce! That's was an edit screw up by me. The links have been corrected.

The GNUinator · 08-02-2009, 09:55 PM

Quote:

Originally Posted by joeBuffer

onebuck, I've been thinking about using Slackware more ... I've tried it before, but didn't stick with it for very long ... what do you think is better about Slackware than other distributions?

Because Slackware acts like a real operating system should act. For me it is that simple. The first time I installed Slackware I was too stupid to realize that it is "as user friendly as a coiled rattlesnake" ... from the Vector Linux website. I just read and followed the instructions. Got used to using the command line and editing config files with a text editor. Would never attempt to run Linux without MC the Midnight Commander. Now I'm running 12.2 and one thing I really like is that it recognizes Atheros based wireless cards automagically without having to install alien packages. I use Alien Bob's makeinitrd shell script and Slackupdate shell script from Darklinux.

Slack does everything I need it to do. Looking forward to version 13.0 soon.

My blog: The Gypsy Chief Blog: http://kakoluri.com

hth,

The GNUinator

onebuck · 08-03-2009, 07:30 PM

Hi,

This is just a reminder!

We have the best forum around. Generally the information available to you is possibly a
simple search >>> LQ Search <<<

So if you don't find your answer with a search of the knowledge source(s) here on LQ then post the query. Please be sure to include all information possible i.e.; System Info, distro, kernel, error messages, log messages and even your personal observations.

You need to remember the helpers here are not sitting behind you. Jeremy had us all send back the cracked crystal balls. The balls were giving us smoky looks or views that would not allow us to look clearly over your shoulder.

The next two links will aid;

onebuck · 08-06-2009, 08:44 AM

Hi,

'Slackware 13 RC2';

Quote:

excerpt from changelog (x86);

> Thu Aug 6 00:48:30 CDT 2009
Hi folks! We're going to call this set of updates RC2. There are still
README files to be handled (that's the nature of documentation, I guess), as
well as some other things remaining on the TODO list, but X seems pretty
stable now, and it seems like a release soon would be in order so that we
can march right back into development territory with -current again soon. :-)
Enjoy, and let us know about any problems you run into!

'mirror-slackware-current.sh' is still the best way to get your '-current' ISO. Be sure to check your md5sum for the burnt ISO image since the download md5sum is already done for you.

Bruce Hill · 08-06-2009, 09:29 AM

Quote:

Originally Posted by onebuck

Hi,

'Slackware 13 RC2';

'mirror-slackware-current.sh' is still the best way to get your '-current' ISO. Be sure to check your md5sum for the burnt ISO image since the download md5sum is already done for you.

Recently I found out that using md5sum against CD/DVD is not always reliable.

So far, when md5sum has failed, cmp has not.

onebuck · 08-06-2009, 10:14 AM

Hi,

Quote:

Originally Posted by Bruce Hill

Recently I found out that using md5sum against CD/DVD is not always reliable.

So far, when md5sum has failed, cmp has not.

I haven't experienced a problem with 'md5sum' when done properly. Check out 'CdromMd5sumsAfterBurning'. What were you checking when the failure occurred? Padding error?

onebuck · 08-13-2009, 06:25 PM

Hi,

Some confusion about Slackware 13.0 release from a lot of users that are not aware of what really is going on;

Quote:

Originally Posted by Alien Bob

There won't be an official statement about switching to x86_64 because that switch is not being made. If you had followed Slackware's progress over the past months, you would have seen that there are now two supported architectures for Slackware that are jointly developed and maintained - one for 32bit and one for 64bit architecture.
You get to choose what to install. The 32bit Slackware will not be dropped.

Eric

The above was a response to 'Hmm... Slack 13 is out?'.

onebuck · 08-28-2009, 09:29 AM

Hi,

Great balls of fire!

'Slackware® 13.0' is official and you can read the release at Distrowatch.

I recommend that you use torrent downloads so we don't load Slackware® Home.

The torrents Page at Slackware® Home is a good place.

Torrents: Slackware® 13.0 is another source.

Slackware® 13.0 Mirror for ISO.

I've update the 'Slackware-Links'. More than just Slackware® links!

The long wait for Slackware® 13.0 was well worth it! Happy Slacking.

onebuck · 09-11-2009, 10:58 AM

Hi,

Well the dust is settling and the new release of Slackware® 13.0 x86_32/x86_64 seems to be getting smoother for all.

One problem that a lot of new users have is partly due too the creation of an account for a new user in that they fail to include user(s) in proper groups;

Code:

users floppy audio video cdrom plugdev power netdev <<<<  suggested groups

When adding a new user you can get the suggested groups by pressing the up-arrow at the prompt after 'users' group prompt at the additional groups prompt;

Code:

Or press the UP arrow to add/select/edit additional groups
:users floppy audio video cdrom plugdev power netdev <<< up-arrow response, you can move across line to modify

I've also noticed a lot of the new users fail to revert their '/etc/rc.d/rc.inet1.conf' and '/etc/wpa_supplicant.conf' files to the original state when they attempt to use 'wicd'. It should also be noted that 'wicd' KDE tool is very clumsy and not a reliable means too initially setup your access. I suggest that users should rely on the 'wicd-curses' to setup initially from a console. Sure a little more work but reliable.

Another potential error is that a lot of people fail to verify their copies of the ISO along with the media for the burnt image. Then claim to have errors at the fault of Slackware®. Guys the computer does as it's instructed to perform. If it's garbage in then garbage out.

Test the ISO and Burnt Image to insure a valid copy. Don't A$$ume (A$$ u and me)!

Don't just rely on the burner application to verify as these too can provide a potential problem.

Whenever posting to the forum please provide enough detail as to your problem along with supporting information to aid everyone in hopefully getting things resolved for you. A lot of our responses to new forum members is requesting information such as to the Distro/version, kernel used, hardware specification(s) along with any error or messages you may have received with your attempt.

Some helpers do request information that may seem critical, if so just xxx out anything that may seem a security risk. Keys are not necessary as long as they are valid for you. The response to a request like 'ifconfig -a' instead of just 'ifconfig' may seem redundant but it's not. The '-a' option shows you all devices that are recognized;

Quote:

excerpt 'man ifconfig';
-a display all interfaces which are currently available, even if
down

Meaning your device is there but not available when shown with 'ifconfig' alone. 'man' those commands!

PV and team have provided a lot of valuable information that everyone should read in the form of text files on the media;

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

Be sure to use the LQ search function as a lot of the problems most new users experience have solutions. The queries you get from your search may aid you in solving your problem. If not then the same results may aid you in defining a new thread/post.

Happily Slacking along instead of distro hopping!

...

onebuck · 09-14-2009, 07:03 PM

Hi,

A heads up for 'Slackware® 13.0 x86_64' users that multilib;

Quote:

Originally Posted by Alien Bob

Did you by any chance install the 32bit multilib packages that I created, and then ran the slackpkg command after that?

There is a bug in my multilib setup (which I am fixing right now) so that if you run slackpkg after installing my set of multilib packages and then tell slackpkg to install the *.new files that it finds, you will end up with empty /etc/rc.d/rc.hald , /etc/rc.d/rc.messagebus and /etc/rc.d/rc.mysqld scripts.

The result of not starting hal and dbus when the computer boots will perhaps not be immediately obvious, but if you start X, you will have no mouse and no keyboard.

The fix is to reinstall the hal, dbus and mysqld packages:

Code:

upgradepkg --reinstall a/dbus-1.2.14-x86_64-1.txz
upgradepkg --reinstall l/hal-0.5.11-x86_64-6.txz
upgradepkg --reinstall ap/mysql-5.0.84-x86_64-1.txz

and make sure you use the *.new files that will be installed in /etc/rc.d/ ...

Eric

Knowing Alien_Bob it won't be long for a fix. But use his work around for now.

Alien Bob · 09-15-2009, 01:56 AM

Quote:

Originally Posted by onebuck

Hi,

A heads up for 'Slackware® 13.0 x86_64' users that multilib;

Knowing Alien_Bob it won't be long for a fix. But use his work around for now.

I have fixed the bug and uploaded new packages: http://alien.slackbook.org/blog/no-m...ling-multilib/

Eric

brianL · 09-15-2009, 06:43 AM

Eric
Is there any need to re-run massconvert32.sh on the packages from 12.2 after this update of compat32-tools?

Alien Bob · 09-15-2009, 07:13 AM

Quote:

Originally Posted by brianL

Eric
Is there any need to re-run massconvert32.sh on the packages from 12.2 after this update of compat32-tools?

The packages found under multilib/slackware64-compat32 form the complete set of packages created by the massconvert32.sh script.

So, if you have downloaded and installed those, then there is no need to run the massconvert32.sh script.

Eric

brianL · 09-15-2009, 07:25 AM

Thanks, Eric, for the quick reply.
When I went multilib I used the -9alien compat32-tools to convert packages from my 12.2 DVD. I just wondered whether these would still be OK.