Hi,

Hopefully now that 'Slackware.com' is back then we can get back to the serious side of slacking.

I recently moved to a hardware install of Slackware64. That is one slick Slack!

Looking forward to that new Slackware Release.

Hi,

It's been about three weeks(Wed Jul 1 16:04:35 CDT 2009) since the Slackware RC1. I've since installed to a AMD64 machine. I'm really delighted and look forward to moving to other machines with the new release. It's about time to move the machines to the newer OS. I'll do a stable install to these just to see how things work out.

I feel that it won't be long before stable is here.

I'm confused, what do you mean "if you anticipate"?

Hi,

I don't think that the word was mis-used;

For clarity sake when you quote something in the future please provide the full quote with reference/link.

No, I'd apologize if this seems like an insult, I'm just saying ...
Anticipating a storm and doing something, that I'd understand, but anticipating acpi in general wouldn't make much sense, since it should be there in most cases ... meaning if you expect that acpi will be doing things, and you turn it off, that doesn't make any sense, if you anticipate that it's going to cause problems, that's different.
It just seems like it might be confusing to someone, if they didn't understand what you mean.

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?

LOL

cause Slack ain't gonna hold your hand like Ubuntu

You gotta learn configuring and adding pkg's without a gui pkg manager

But, slack is better in Many ways

it's very stable

you'll see...

onebuck, I feel like maybe I started off poorly with you, since I made a post saying that you were advertising 24 hours a day it seems like ... but I guess you aren't, going by the other posts I've read of yours.
linus72: I've read about it being very stable, and I've tried 12.2 with KDE 3.5 (which is the first time I've tried 3.5), but I didn't use it or read about it for long and was under the impression it had something like a package manager, and then afterwards read that it's a very big distribution for people who like configuring things through text files, also. It made me much more curious. I have used Gentoo before, but it does have a package manager. I did some of the Linux From Scratch, but didn't finish it - I had no problems, however, when installing it, it was just taking so long and I had other things I wanted to do.
Ubuntu is the easiest distribution I've used, for 100% of what I've done with it. It's very simple. Everything from installing it to packages, it's the simplest thing I've used. I'm using 9.10, but I installed it to an extended partition, and was going to have at least one other distribution on here, and was thinking about Gentoo or Slackware now, and was thinking maybe Slackware would be the way to go, from what I've read of it.
By the way, I'm the person who was using the chigurh8 nickname on here, but I changed my name.

Dig this dude, Joebuffer

98% of Linux is like editing config files/text files

no snit dude

Onebuck and the others know their stuff too

kde slack has kpackage

but, I never use kde, I like xfce, and the lighter stuff

KDE confuses me, it's like having 8 12 packs of different kinds of beer
and I gotta decide which one I'm gonna drink first...LOL?

Hi,

I'm not insulted by your query. Please read the definition. To 'anticipate' something is to attempt to do something to correct/prevent or the need to shield one from something expected so as not to do harm or error.

I really like the 'answers.com' usage;

In effect you are saying the same in your definition of the reasoning to turn acpi off. You just spun a little with the wording. Maybe some non-native speakers would have a problem. But I would look up a definition or translation whenever something isn't clear.

I could have used 'To look forward to; to expect' but to me 'anticipate' came out and fits. We all think and hopefully communicate so as to convey understanding to others. Look at the USAGE above. If you use that then things are really spinning. I hope this has helped to clarify.

Hi,
I like the configure ability, stability and the historic functions with Slackware. Plus I'm an old, and I mean a real old UNIX man. I only use a few LiveCDs that are based on other distributions. You can take a look at 'Tools, Recovery, Diagnostic, Emergency' section of 'Slackware-Links' to see the LiveCDs that I use.

Distro-hopping is not my cup of tea. You could do a search here on LQ as this very subject has been queried so many times. If you learn Slackware then you will be able to work with other distributions. You will need to learn the semantics of the other distributions but moving around them will be a lot easier once you learn the 'cli'. Sure you can still use a 'GUI' with Slackware but to configure properly you had better learn the command line.

Hi,
I like that analogy. What brands?

'Sam adams'
'MGD 64' for old men like me but I do like a good lager.
'Blue Moon'
'Leinenkugel's Original'
'Leinenkugel's Honey Weiss'
'Leinenkugel's Sunset Wheat'
'Leinenkugel's Creamy Dark'
'LaCrosse Lager'

Just a few that I really enjoy as in 'Free' to enjoy. So when they make a 'Lager 64' then send me to heaven. I know that would be impossible but we can dream.

I'm going to a birthday party today and that is 'Free' to 'Enjoy' plus it is 'Free' so the enjoyment is really going to be great to enjoy... Glug!

Hi,
It's just a communication layer thing! I do participate on LQ a lot. Partly because my physicians have restricted my physical activity. Which hopefully will be lifted fully. The limitations don't affect my mind, except maybe when I've had a few beers. I do mean a few now. Since those too are limited by the doctors.

I appreciate you being up front about your name change. But I really didn't have a problem except that it did seem you did not understand my reason(s) for what I've been doing here on LQ. I do come from academia and can get a little wordy. I've been trying to tone down a bit but that is difficult because of the conditioning over the years.

BTW, challenges are healthy. So don't stop if you find that something isn't clear. I've learned a lot here on LQ from the members. So ask or debate. I love this part of the LQ rules;

What sort of UNIX did you use?
linus72 - I feel very awkward when using KDE. I haven't gotten used to it yet. GNOME, Xfce, Fluxbox, I like all of them, and I don't feel awkward. For some reason KDE feels awkward to me. I think I just haven't used it for long enough and gotten used to it.
As far as configuration files, I've only gotten used to the ones I need when I'm installing something, basically ... like Gentoo. I've been planning on reading much more about configuration, also, but I've been reading a lot about sed/awk/find/bash scripting, and all the command-line first. I'm still getting used to some things, really ... I've been using Linux since early this year.

joeBuffer,

I like Slackware because Pat Volkerding has the last say about
everything. So you don't wind up with some wishy-washy democratic
committee collisions like in Debian.

Slackware has a sizable community of men who know their stuff. You
may never hear of/from most of them, but when something in Slack
needs fixing, they'll write Pat. And when it's been tested and it
is proven, Pat will add the fix.

Slackware has "pkgtool" and now "slackpkg" is part of the standard set
of packages. They don't resolve dependencies for you, they just help
you install Slackware packages. Slackware is built on the philosophy
that any software you want to add that is not an official Slackware
package is your responsibility. This might seem like it could be hard
on the users, but it has never been a problem for me. It is the best
way in the long run of keeping your system as you want it.

On the other hand, while waiting for Slackware to release x86_64, it
behooved me to try some other 64-bit distros. Probably the only one
that got more than a day was openSUSE-11.2. And what I found was that
these package managers would downgrade software, would replace some
software I'd already added, and generally do things I did not want.
Manually editing some config files was impossible; i.e., whenever I
would put my nameservers in /etc/resolv.conf, SUSE would not accept
that file and write/use some new file. There were so many things that
SUSE expected YaST2 to do. While in the #suse channel on FreeNode,
it surprised me how many guys had problems that were strictly because
of the package manager doing more, or changing things, other than the
person wanted. And I could not find out how to keep my bluetooth mouse
working across reboots. I had to run "hidd --search" every time I either
rebooted, or DPMS turned the monitor off. What a goofy situation, and
I found no one who knew how to change it.

For Slackware packages: if official Slackware has the software, I will
use that. If not, my next option is to check Alien Bob's repository. If
he doesn't have it, then I build it myself. There are other repos of
Slackware packages, but I do not trust them because from experience they
have SlackBuild scripts that are of inferior quality. I have never had
any bad scripts from Alien Bob; and when one did not do what I anticipated,
he has either told me why or added that function. Also, Alien Bob has now
created a web page where you can make a SlackBuild from his toolkit. You
would need to edit it slightly, sometimes, and then other times you can
use it just as it outputs the first time. Even using his template I always
run "./configure -help" on the source and edit the SlackBuild.

1 members found this post helpful.