Share your knowledge at the LQ Wiki.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 02-20-2010, 11:44 AM   #46
Registered: Jan 2009
Distribution: Slackware 14.1
Posts: 333

Rep: Reputation: 56

Originally Posted by raju.mopidevi View Post
installation of softwares ....
I don't like installing from "tar" files.
download -> extract -> ./configure -> make -> make install

I like GUI based installation.

open package manager, select s/w, click to install.
...and miss the opportunity to understand exactly what's on your system, and how it works. On Slackware, installing from source is usually a breeze. I find it much easier than using any of the automated tools I've used. Using those tools, it was easier in the short term, but much more difficult in the long term since so many of the details of what was being done to my system were hidden from me.
Old 02-20-2010, 11:47 AM   #47
Registered: Jan 2009
Distribution: Slackware 14.1
Posts: 333

Rep: Reputation: 56
Originally Posted by lumak View Post
I don't like that quality, useful programs don't respect Slackware and insist on using gnome libraries to compile. e.g. gnucash and inkscape.
I agree with you - I HATE HATE HATE HATE having to use anything that depends on Gnome libraries. Hate it.

But this isn't a problem with Slackware, it's a problem with the programs that depend on Gnome libraries...
Old 02-20-2010, 12:16 PM   #48
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 12,440
Blog Entries: 23

Rep: Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868Reputation: 1868
Originally Posted by pixellany View Post
Of course it is a Slackware approach--SW is os one of the majority of distros that does a complete install, but the SW community also is big on customizing and optimizing. My only point is that I prefer to optimize by adding things, not by removing them. Maybe that means I should really be using LFS.

"moderator troll"----I like it--please ask Jeremy to add that to the list of available titles. But does one attain this before or after--eg--"guru" or "moderator"?
I like it!

I'll bet you have to even use 'USENET' to get to that status.

Old 02-20-2010, 12:18 PM   #49
Registered: Oct 2009
Posts: 73

Rep: Reputation: 25
Unless I run `chmod -x /etc/profile.d/xfce.*`, I get the Xfce run box in KDE when I hit Alt-F2
Old 02-20-2010, 12:20 PM   #50
Senior Member
Registered: May 2008
Posts: 3,974
Blog Entries: 1

Rep: Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380
Quote from
GTK+ is built on top of GLib
I think that's one of the biggest problems. If gtk+ was a self-contained standalone widget library then a lot of these problems would go away.

Then of course, there's stuff like gconf. Ideally, Application developers would leave this to be a compile time '--enable-feature' on ./configure. and code it so that it would fallback to the traditional .programrc files and Xresources when not enabled. Unfortunately, developers can't be arsed to put the effort into coding this and therefore the need for gconf is forced upon everyone just so that one silly little program can get something trivial like its font settings or colours from gconf.

Part of it is down to the application writers, but part of it is also bad library design and separation of function.
Old 02-20-2010, 01:29 PM   #51
Registered: Mar 2006
Location: home
Distribution: OpenBSD, FreeBSD, Slackware, Debian
Posts: 231

Rep: Reputation: 39
There is probably a way people know to do this, but I don't like after doing a full install, I use pkgtool to remove programs/etc, without knowing if the file/program is required.
For just a desktop user, it's hard for me knowing what I can delete and can't. All those proto files for example.
OTT, Slackware is great!
Old 02-20-2010, 01:52 PM   #52
Registered: Sep 2006
Posts: 345

Rep: Reputation: 34
I don't like Sendmail as the default MTA. I would much prefer Postfix.

Also I would much rather have PostgreSQL instead of MySQL.

Other than that I'm a happy camper.
Old 02-20-2010, 02:33 PM   #53
Registered: Mar 2008
Location: Kaunas, Lithuania
Distribution: Slackware forever
Posts: 30

Rep: Reputation: 17
There is nothing i would dislike about Slackware, common, it's stable, it's clean (as far as i know software included with Slack is as most pure vanilla as you can get), it's free (as in beer and as in freedom) it's fun (for the little geek in me), it's cool (as i can proudly say "I use Slackware!" )

The only thing i would like to see is the Slackware Wiki, where users could write how-to docs that would cover lots of things to make other users to understand Slackware better (package creation, installation, removal, dependency solving, configuring, optimizing, customizing, etc... ), and those docs should not only have a list of commands that you can copy paste to get something done, but also explain exactly what they do, how they do and why they do something. That would be truly awesome in my opinion.

Maybe such wiki already exists and i just do not know about it?

Last edited by Affromen; 02-20-2010 at 02:36 PM.
Old 02-20-2010, 03:19 PM   #54
Alien Bob
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 6,247

Rep: Reputation: Disabled
Go to and start adding documentation then!

Old 02-20-2010, 03:57 PM   #55
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware 14.1, Slackware64 14.1
Posts: 945

Rep: Reputation: 98
Originally Posted by GazL View Post
Quote from

GTK+ is built on top of GLib
I think that's one of the biggest problems. If gtk+ was a self-contained standalone widget library then a lot of these problems would go away.
Why do you think that this is a problem? You can think of gtk/glib/pango etc. as parts of a single big package, like the Qt toolkit. They can only exist together. At the very beginning perhaps "Gnome library" and "glib" were almost the same thing, but at least after gtk+2 they were clearly separated. Of course, glib development follows that of Gnome, but the changes are (mostly) in the form of backward compatible incremental updates. I also hate Gnome-dependent software but I'm very happy with the Gtk dependent ones, no problem there at all.

In recent releases they have begun incorporating some Gnome libraries into Glib (or more precisely, the Gtk framework), e.g. the Gio stuff or the printing interface. This is good news, as applications will have fewer or no reasons to depend on Gnome libraries. Qt seems to be more complete in that respect, but hopefully Gtk will catch up.
Old 02-20-2010, 04:18 PM   #56
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Rep: Reputation: 62
Sendmail. Why can't postfix be the default MTA?
Old 02-20-2010, 04:57 PM   #57
Senior Member
Registered: May 2008
Posts: 3,974
Blog Entries: 1

Rep: Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380Reputation: 1380
I agree with you about display related things like pango, cairo and gtk being considered as a single entity and in fact there's probably a good argument for merging them into a single library. They're all related to a single area of function (i.e. graphics/display/gui) it's when routines to provide other types of function are included in what is essentially a gui toolkit that I think is a mistake.

What brought this home to me recently was when I wanted to build an application on OpenBSD that needed the gtk+ library, and to build the library I also had to build CUPS, which required me to build Bonjour and so on. If the gtk+ application doesn't do any printing and only needs the gui widgets then why should I have to add these libraries? Proper separation of library functions based on functional area would have avoided the need for this.

Keeping clear separation of function/purpose between libraries is just good practice for efficient code reuse. At least, that's the way I view it.
Old 02-20-2010, 05:33 PM   #58
Registered: Jul 2007
Distribution: Fedora
Posts: 527

Rep: Reputation: Disabled
Originally Posted by gargamel View Post
But in recent years there seem to have been a few more security problems in Postfix than in Sendmail. No one would have expected this five years ago, when Sendmail was the Swiss Cheese of MTAs.
I won't discuss the rest of the post, as the configuration mechanisms are a matter of taste and I know for a fact that sendmail can dispatch messages faster than Postfix (but both are quite fast anyway).

However, I'd like to read some information backing up the claim on Postfix having more security problems than Sendmail in recent years. Honest question. I've looked back at some security advisories since 2006 for both projects and Postfix has only had two local minor security problems since then (both for 2.x and none for 1.x), while Sendmail has had a remotely exploitable SSL certification vulnerability, for example. Sendmail has certainly improved over the years, but I don't think Postfix is worse in any way regarding security.
Old 02-20-2010, 05:38 PM   #59
LQ Newbie
Registered: Jan 2010
Distribution: Slackware 12.2
Posts: 9

Rep: Reputation: 0
Originally Posted by pixellany View Post
I don't like:
The basic philosophy of have no dependency-checking package manager by default.
the first point is a feature! there's nothing more painful than watching an inapt packet manager cluttering your hd with shit you don't need.

The approach of starting with a full install and then removing what's not needed.

(opposite extreme is Arch, which starts with nothing.)
so what do you do after your kernel loaded itself into your RAM? count the blinks of your cursor?

there's only Slackware, everything else is bloat.

regards, slacky02
Old 02-20-2010, 06:02 PM   #60
Registered: Jun 2004
Location: USA
Distribution: Slackware
Posts: 137

Rep: Reputation: 21
Originally Posted by sahko View Post
One thing i dont like about Slackware is that it doesnt have its own forum and it relies on LQ so we have to put up with moderator trolls.
I have to disagree. Remember, at the heart of it, Slackware is one guy (no offense to Eric, Robbie, etc.). If Pat were to run his own forum, the time he would undoubtedly have to spend dealing with it would only take away from work on the distro itself. Instead, he outsourced the forum to the very capable hands of Jeremy and the LQ crew.

As for something I dislike about Slack, I really despise it's reputation as "a good server distro" or a distro that's "not for linux newbies". The first (and only) distro I ever took seriously was Slack and I can't even enumerate all I've learned about linux. Yes, I've taken my lumps, but it's not impossible for someone new to linux to start with Slack. All it takes is patience, google, the LQ search function and a willingness to learn.


awesome, feedback missing, fud, slackware, slackware64, slackwarecurrent

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Post Slackware distros Tylerious Linux - Distributions 15 02-16-2006 06:12 PM
slackware post install nicole_jeff Slackware 2 05-23-2004 06:06 AM

All times are GMT -5. The time now is 09:15 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration