Talk:Slackware

Slackware-based distributions section

What a mess this was in. I've fixed the list style, checked the links (they were all fine, one had moved, updated it), and removed a particularly spammy mention of LTSP from the Lorma linux part which claimed it was a Slack-based distro:
LTSP is an add-on package for Linux[1]

Also, not all the External Links are external links.

Fixed

200.195.30.165 has added a rather hefty list of Slackware-based distributions. For now I've moved it down the bottom of the page, near the See Also section, because the long list of links belong down there if anywhere. It was just after the History and Name section before, which I think was an inappropriate position.

The list is very long, I reckon something has to be done about it. I think it should either be placed in a List of Slackware-based distributions page, or into the List of Linux distributions page. I don't think that such a long list belongs on the Slackware page. --James Hales 14:13, 29 January 2007 (UTC)

I concur, someone who knows their distros needs to cut it down to the more noteworthy items. Also, "Linux Distribution" shouldn't be linked on every line. I haven't decided yet if I can be bothered to fix this personally, since it's clear at least one editor suffers from OCD and will revert it. Chris 17:03, 13 March 2007 (UTC)

Opening sentence

The current opening sentence:

Slackware was one of the earliest Linux distributions (and is still being maintained), created by Patrick Volkerding of Slackware Linux, Inc.

This is a little ambiguous, as well as being an awkward sentence structure. It could be taken to mean:

Slackware was one of the earliest Linux distributions to be created by Patrick Volkerding.

How about this?

Slackware was one of the earliest Linux distributions, and is the oldest distribution still being maintained. It was created by Patrick Volkerding of Slackware Linux Inc.

--Annoying anonymous guy #94804327

By the way, some interesting info from vivaolinux.com.br user stats(top distribuições): Slackware is the second most used distro in their community, at 5074 users, beaten only by Conectiva at 5109 users.

Should we use "lilo-slackware" boot screen picture, instead KDE desktop? It's the first slackware logo in 15 years that include in the distro. —Preceding unsigned comment added by 124.121.241.203 (talk) 17:02, 30 May 2008 (UTC)

The KDE desktop picture is somewhat misleading: it could be any distro with a generic KDE install. KDE is packaged with Slackware 12.2, but it is not Slackware-specific.152.2.67.61 (talk) 16:30, 19 February 2009 (UTC)

Dont know if it was a bug or a glitch, but the parser on the server wasn't parsing the links to other articles and dropping the text for the links out of the article completely rendering it unreadable. After changing the first link slightly, all of the subsequent ones were parsed correctly. If this was a temporary glitch, feel free to change the formatting back to the original. 205.217.251.33 (talk) 18:22, 16 April 2009 (UTC)

Media error

Er... Slackware uses packages. See http://www.slackware.com/packages/. --Stephen Gilbert

Beat me to it... pkgtool is their package tool. Not as fancy as RPMs, but it works, and works reliably, too. --Malcolm Farmer

Packages

I've taken this passage out, as it's varying levels of inaccurate, confusing, and seems poorly written to me:

There is a disdain for packages, where related files are grouped together and managed as one entity. For example, even a simple application such as cron would be packaged as a set of files containing the executable, documentation, and configuration files. While this can make installing a new application relatively simple, some Slackware users feel that packages limit their flexibility.

A rewrite and clarification is certainly in order here. The page is left a bit thin, but it's better than distributing inaccurate information. --nknight 03:15 Dec 4, 2002 (UTC)

As per my Summary any thoughts on my shot at describing the package management issue? --Moss Hart 01:23 24 Jul 2003 (UTC)

Looks reasonable to me. Thanks. --nknight 01:47 24 Jul 2003 (UTC)

I took the liberty of fleshing things out, including the package management section. I'm sure it could use a good editor at this point. I tried to keep things neutral despite my personal prefernce for Slackware. I also added a section on init scripts, but my understanding of the issue is limited, so it might be in need of some factual corrections. --Greyweather 03:46, 20 Feb 2004 (UTC)

"Slackware's approach to package management is unique." - The reason given is that it lacks a somewhat controversial feature. While it may actually be unique in that no other distribution has this approach (which I am not sure is true), I think labelling it "unique" shows a bias towards it. Or it may just be me; English is not my first language. I was pointed to this wording in this article on a different Linux distribution. --Haakon 20:34, 9 Feb 2005 (UTC)

As old as this comment is, I rather agree with it. Slackware almost does not have a packaging system at all, each package is just a tgz file with some rather basic info for the database. (package name, version & discription) Having a lack of packaging system not really unique, LFS also does not use a packaging system, and many livedisks don't either. How about changing the sentance to read something like this? "Slackware employs a minimal approach to package management."

Live CDs don't generally have package management because they are put onto static, fixed media, which makes packages kinda pointless. And the ones which aren't intended to be static (eg Puppy linux and Knoppix with the UnionFS, both on a RW disc of some sort) do have package management. And LFS doesn't include it because LFS... is a book. --Maru 12:55, 24 August 2005 (UTC)

Say what you want, but if other (rather specialised, I'll admit) distros have it, it's not unique. --Jamesgecko 16:49, 24 August 2005 (UTC)

I think you are misunderstanding me. I was replying to the unsigned comment which claimed that lacking a packaging system is not unique (I think it is very rare), and gave examples of lacking. I was pointing out the examples were flawed for various reasons. --Maru 16:53, 24 August 2005 (UTC)

Slackware's packaging system is .txz now for x zip, someone might want to fix that. 66.30.79.125 (talk) 14:07, 9 July 2009 (UTC)

Well the .txz format is tarred and compressed with the XZ Utils, so the x does not stand for x zip. —Preceding unsigned comment added by 20.142.112.37 (talk) 18:21, 28 October 2010 (UTC)

And, most importantly, what is installed by a Slackware package is almost exactly what you would get by running "tar xvzf source-pkg.tar.gz ; ./configure ; make ; make install".

Changes

I added a few changes, including an unofficial version history, more external links, and move the subentry for CollegeLinux, to the subheading for Slackware based distros in the external links. --moorcito 11:58 02 Sept 2004

I've moved the dependency resolution to a separate section rather than a subsection under Package Management. I've also clarified the slackbuilds.org statement so it does not appear that the source tarball is available at slackbuilds.org (since they're not). --Ken Roberts 15:14, 21 October 2009 (UTC) —Preceding unsigned comment added by Alisonken1 (talk • contribs)

BSD vs. SysV init procedures

Here's an excerpt from the slackware-current ChangeLog:

+--------------------------+
Fri Feb  9 22:59:51 CST 2007
a/sysvinit-2.86-i486-1.tgz:  Upgraded to sysvinit-2.86.  Split the actual
  init scripts into a new package to avoid needlessly compiling sysvinit
  over and over again.
a/sysvinit-scripts-1.0-noarch-1.tgz:  Added a new package containing the
  system startup scripts.  Thanks to Piter Punk for 2.4 kernel cruft
  removal and other bugfixes and enhancements.

... and the slack-desc for sysvinit:

sysvinit: sysvinit (init, the parent of all processes)
sysvinit:
sysvinit: System V style init programs by Miquel van Smoorenburg that control
sysvinit: the booting and shutdown of your system.  These support a number of
sysvinit: system runlevels, each with a specific set of utilities spawned.
sysvinit: For example, the normal system runlevel is 3, which starts agetty
sysvinit: on virtual consoles tty1 - tty6.  Runlevel 4 starts xdm.
sysvinit: Runlevel 0 shuts the system down.

I feel that this proves beyond a reasonable doubt that Slackware uses System V-style init scripts rather than BSD-style scripts. -- H3xx 05:27, 22 May 2007 (UTC)

Sorry, but you are wrong. Slack uses BSD scripts, the sysV scripts that you mention are there for compatibility reasons only since Slackware 7. If you are a technical enthusiast, you may want to check by yourself in /etc/rc. There is an additional script called /etc/rc.sysvinit that provides the compatibility and is linked to the sysv package, thus its presence on the system. Hope that answers the questions.

Umm you do know there is no /etc/rc right in slackware

You're right that there is no /etc/rc in Slackware, there is however an /etc/rc.d/ and /etc/rc.conf - 86.160.43.187 (talk) 23:22, 18 October 2009 (UTC)

Package Managers

In the bit about third party package managers, should it be mentioned that those are external outside links, or should they be wikified to stubs which contain the outside links, or what? As it is, it is a bit surprising to click on an apparent wikilink and be somewhere completely else. --maru 15:48, 18 Apr 2005 (UTC)

IMHO, the different color and the little arrow icon should be enough to indicate that they are external links. --Yath 22:05, 18 Apr 2005 (UTC)

It is true that to an experienced Wikipedian, those indicators are more than sufficient; I noticed it right away. But is Wikipedia designed only for experienced Wikipedians, or is it designed on a basis of 'don't suprise a basic user'? --maru 16:10, 19 Apr 2005 (UTC)

VectorLinux?

I believe VectorLinux is a Slackware derivative. Could we add that to other derivatives? http://www.vectorlinux.com/ for more info.

Live CD section

Why do we need a section devoted to Slackware-based live CDs? This is an article about Slackware after all. I think this section should resemble the section on Slackware-based distributions - One link and one line devoted to each live CD, linking to wikipedia stubs as appropriate. Any thoughts? --Grazer 2005-06-09

OK, I've made the change. Hopefully you won't want my head on a plate. --Grazer 2005-06-10

Live CDs introduce users to Slackware and its file organization http://freshmeat.net/projects/linuxlivescripts/ exerpt "There are many excellent projects build by using these scripts, like Slax, GoblinX, Mutagenix and gNOX"

Not as widely used as it was in the 90's?

I've been in university for many years now and I've yet to meet a classmate who also uses Slackware. Everyone is "Debian this, RedHat that, Ubuntu this, Gentoo that" -- I feel like I'm the only one on the entire campus who uses Slackware! It used to be in the 1990's that I didn't have such a hard time meeting Slackware users (in the real, physical world I mean, not the Internet), but these days I think I have a better chance of seeing a leprechaun riding a unicorn. --I am not good at running 18:18, 30 August 2005 (UTC)

I hope you've not been there too long... But you are right- I personally think the reason is obvious: one of the major advantages of Linux distros over all the other OSs (I'm excluding *BSD here) is the various packaging systems, which are a unique selling point. MS can't do that, nor can Apple. Slackware does not really have one. --Maru 21:11, 30 August 2005 (UTC)

I'd say that the main reason is that Slackware is still percieved as "old-fashioned". Things like the text-based installation routine put "average" people off of using it. However, for me, design decisions like that are WHY I use Slackware - it's fast, clean, simple, small and runs on ANYTHING (even going back to monochrome monitors and text-only displays)... plus playing with the menus is a cinch. All of the distros you mention are mainly graphical from boot to desktop. Slackware can run a modern Linux desktop no problem but people see that they have to work a little at it ("What? I have to TYPE?") and that will put them off, even if it is just for the first boot. People who grew up on DOS or UNIX won't even question it.

Your average person doesn't want to know as soon as they realise they have to do something in a CLI. Your experienced computer technicians will choose it over the graphical systems because of the flexibility - I have PC's that can't even run X, can't display to screen, don't even have a graphics adaptor installed, run over serial console etc. That's where you need something like Slackware. And then the fact that it can be a graphical desktop too if you want makes it the primary choice of people who use Linux for a wide range of tasks every day.

Fads come and go. But you tend to find that the people who stick to a particular OS, rather than hop to whatever is fashionable, are the ones who are actually using their computers to get stuff done. The others spend most of their lives installing and complaining about every OS that comes out... :-) --ledow 10:55, 1 June 2007 (UTC)

As a proto-hacker aspiring to become truly "L337" with every OS, I wholeheartedly agree with you. It's one of the best comments that I've read in a long time. I'm so annoyed of all those Apple and Ubuntu fanboys, but really looking forward to get my hands on Slackware. :) —Preceding unsigned comment added by 217.85.199.228 (talk) 13:48, 11 May 2010 (UTC)

Zipslack

Anyone familiar enough with zipslack willing to include a paragraph or two about it? --Unconcerned 10:13, 4 January 2006 (UTC)

I think the Zipslack paragraph is in the wrong place; it is right after design philosophy and package management, which IMO are definitely not similar topics. --maru (talk) contribs 02:54, 8 February 2006 (UTC)

I agree completely. I have just moved the Zipslack section to underneath the Releases section, which I believe is more appropriate. James Hales 05:54, 21 April 2006 (UTC)

Release History Table

I do not like the release history table that is aligned to the right hand side of the screen. It leaves a large area of blank space between headings. The only alternative that I could come up with was to use a table like on the Fedora Core page, and place it underneath the text of the section, without aligning , which makes a slight improvement. I had previously tried a few experimentations involving removing the <br clear="all" /> so that proceeding headings would appear to the left of the page, but the release history section was too short and the release history table too long and narrow to make it look attractive.

Has anyone any alternative suggestions? Here is the table I've written up. Hopefully someone can come up with something better. James Hales 05:54, 21 April 2006 (UTC)

I just came up with something and tried it. Moved the <br clear="all" /> to underneath the Zipslack section, so that they would sit closer to one another, which I think is proper anyway, but it does not allow the release history table to sink into the design philosophy section, which is a larger and unrelated part of the article. James Hales 11:18, 22 April 2006 (UTC)

Slackware x86 Release History

Version	Date
1.0	July 16 1993
2.0	July 2 1994
3.0	November 30 1995
3.1	June 3 1996
3.2	February 17 1997
3.3	June 11 1997
3.4	October 14 1997
3.5	June 9 1998
3.6	October 28 1998
3.9 / 4.0	May 17 1999
7.0	October 25 1999
7.1	June 22 2000
8.0	July 1 2001
8.1	June 18 2002
9.0	March 19 2003
9.1	September 26 2003
10.0	June 23 2004
10.1	February 2 2005
10.2	September 14 2005
11.0	October 1 2006

Citing sources

Someone's tagged this article for not citing its sources, and I've taken a crack at adding some. I mostly made links to various pages of the Slackware web site. Places where it's lacking at the moment are the KISS section and the packages section. I couldn't find a reference for those on the main pages of the web site, so I'll keep looking. Once those two sections are done I'm taking away that tag.

For most of the other sections I've added references, except where there is a link to another article or web site which would serve as the relevant reference.

--James Hales 15:00, 22 January 2007 (UTC)

There are references all over the article now, so I've removed the notice box, as the article is mostly referenced now. There are still a few comments around the article which require citations, and I think that they're mostly the subjective comments, or are about technical details not mentioned on the official website, but I'm looking around the net for reviews or guides related to Slackware which might back these points up. --James Hales 07:31, 31 January 2007 (UTC)

SlackWare Screenshot

Could somebody get a SlackWare screenshot up? —The preceding unsigned comment was added by 81.76.56.155 (talk) 15:52, 8 March 2007 (UTC).

Not much point... Slackware is text-based installation with well-known window managers under XWindows. So a screenshot would consist of a text screen (of which there are only a handful "unique" to Slackware, i.e. the installation dialogs) or a screenshot of XWindows with a particular window manager. --ledow 10:44, 1 June 2007 (UTC)

File Formats

Does Slackware use RPM files, DEB files or what? ^Talk User:Fissionfox 12:29, 16 April 2007 (UTC)

Slackware#Package management. Chris Cunningham 12:44, 16 April 2007 (UTC)

Gnome

desktop environment was removed from the pending future release,[5] and turned over to community support and distribution. The removal of GNOME was seen by some in the Linux community as significant because the desktop environment is found in many Linux distributions. In lieu of this, several community-based projects have filled the GNOME void in Slackware, by offering complete GNOME distributions for Slackware.

Is this really worth mentioning? -- Pauric (talk-contributions) 10:45, 19 April 2007 (UTC)

Considering the popularity and pervasiveness of GNOME, I would think it is. Dismas|^(talk) 11:10, 19 April 2007 (UTC)

Slackware dropped Gnome, so I dropped my subscription to Slackware.

It was a significant design decision by Pat, I think it does bear mentioning. At least two dedicated users switched away from Slackware for a more integrated Gnome distribution;) 66.57.100.48 (talk) 13:01, 25 September 2010 (UTC)

Slackware's relation to the Church of the SubGenius

I noticed that here on the Slackware page the claim is made:

There is persistent speculation that it is a reference to the term "Slack" as defined by the Church of the SubGenius[3], but Volkerding is not known to have confirmed this.

Yet on the Patrick Volkerding page there is a link to a Slashdot article where Pat clearly says that it was based on the SubGenius, and even mentions the Dobb's head on the CDs (which I have also read elsewhere).

Anyone want to shed some light on why this page contradicts Pat's (and as it would seem, the evidence)? MS3FGX 12:23, 26 July 2007 (UTC)

You don't even have to look at a slashdot post. The install.end file in early versions (which signals the install scripts that you are on the last floppy) has the name and mailing address of the Church of the Subgenius. Later versions rot-13 obfusated it, but it is still there so theoretically you can still install Slackware off of 950 floppies. 2^127-1 is prime (talk) 05:20, 2 January 2008 (UTC)

Another Church of the SubGenius question: I just tried Slackware for the first time, and I'm astonished how little Bulldada is present in the distribution. Bulldada is central to the Church, and other distros generate a culture based on their design philosophy. Why doesn't Slackware? --Moly 18:56, 13 January 2008 (UTC) —Preceding unsigned comment added by Moly (talk • contribs)

Unclear sentence

"The removal of GNOME was seen by some in the Linux community as significant because the desktop environment is found in many Linux distributions." - significant in what way? It might be obvious to Linux geeks, but it isn't to a general reader (me!); please explain this better. 86.132.138.205 03:29, 1 October 2007 (UTC)

Unwarranted advertising

The Third Party heading was clearly intended to include a list of third party sources of packages for Slackware. However, at the end a superfluous mention of Puppy Linux has been slipped in, with the statement that: "Puppy Linux, as of version 3.00, is now compatible with Slackware 12, as it includes almost all the dependencies needed for the installation of Slackware packages."

Aside from the illogicality of the term "compatible" to mean "contains a subset of the required libraries", this is merely unwarranted advertising. If there are no rational objections within a few days, it should be removed. There is no justification for listing all the distributions that can have Slackware packages installed, which, logically, should be nearly all of them. —Preceding unsigned comment added by Marksouth (talk • contribs) 20:12, 6 February 2008 (UTC)

Release information

Can we compile the release history and related information into a table such as this:

Colour	Meaning
Red	Old release; not supported
Yellow	Old release; still supported
Green	Current release
Blue	Future release

Version	Code name	Testing name	Release date	Supported until	Features and Changes
4.10	Warty Warthog	Sounder	2004-10-20	2006-04-30	Initial release; ShipIt
5.04	Hoary Hedgehog	Array	2005-04-08	2006-10-31	Update Manager; Upgrade Notifier; readahead; grepmap; laptop suspend, hibernate and standby; dynamic frequency scaling; Ubuntu hardware database; Kickstart; installation from USB devices; UTF-8 by default; APT authentication
5.10	Breezy Badger	Colony	2005-10-13	2007-04-13	Usplash (graphical boot sequence); "Add/Remove..." application tool; easy language selector; logical volume management support; full Hewlett-Packard printer support; OEM installer support; Launchpad integration
6.06 LTS	Dapper Drake	Flight	2006-06-01	2009-06 (desktops)	Long Term Support (LTS) release; Live CD and Install CD merged onto one disc; Ubiquity graphical installer on Live CD; Usplash on shutdowns; Network Manager for easy switching of multiple wired and wireless connections; 'Humanlooks' theme implemented using Tango guidelines, based on Clearlooks and featuring orange colours instead of brown; LAMP installation option; installation to USB devices; GDebi graphical installer for package files
				2011-06 (servers)
6.10	Edgy Eft	Knot	2006-10-26	2008-04	Ubuntu 'Human' theme heavily modified; Upstart init daemon; automated crash reports (Apport); Tomboy notetaking application; F-spot photo manager; EasyUbuntu merges into Ubuntu via meta-package installs and features
7.04	Feisty Fawn	Herd	2007-04-19	2008-10	Migration assistant; Kernel-based Virtual Machine support; easy codec and restricted drivers installation; Compiz desktop effects; Wi-Fi Protected Access support; PowerPC support dropped; Sudoku and chess games added; disk usage analyser (baobab) added; GNOME Control Center; Zeroconf for many devices
7.10	Gutsy Gibbon	Tribe	2007-10-18	2009-04	Compiz Fusion by default; AppArmor security framework; fast desktop search; fast user switching; some plug-ins for Mozilla Firefox now handled by APT (Ubufox); graphical configuration tool for X.org; a revamped printing system with PDF printing by default; full NTFS support (read/write) via NTFS-3G
8.04 LTS	Hardy Heron	Alpha	2008-04-24	2011-04 (desktops)	Long Term Support (LTS) release;; Better Tango compliance; compiz usability improvements; tracker integration;; Brasero disk burner, Transmission BitTorrent client and Vinagre VNC client by default; PulseAudio by default
				2013-04 (servers)
8.10	Intrepid Ibex	Alpha	2008-10-30	2010-04	Complete interface redesign; improvements to mobile computing and desktop scalability; increased flexibility for Internet connectivity

Altonbr (talk) 03:25, 25 February 2008 (UTC) no because Slackware doesn't work the same way as ubuntu does. —Preceding unsigned comment added by 71.58.107.102 (talk) 04:30, 25 March 2008 (UTC)

Support term

A bit of info that should be part of every article about a Linux distro: how long is a major release typically supported?--Exidor (talk) 17:26, 23 June 2008 (UTC)

They are supported as long as Pat supports it. Slackware 8.1 from 2001 is still getting updates. Just check the changelogs. —Preceding unsigned comment added by 157.201.199.14 (talk) 19:09, 18 February 2009 (UTC)

Pre-1.0 timeline

Donbranson (talk) 20:20, 19 April 2010 (UTC) Does anyone have info on when versions 0.8 and 0.9 were available? I used them, but can't for the life of me come up with release dates for those.

Name

the name es based in Church_of_the_SubGenius my english is bad, so i won't write this.--Vincegeratorix (talk) 14:09, 14 November 2010 (UTC) —Preceding unsigned comment added by Vincegeratorix (talk • contribs) 13:55, 14 November 2010 (UTC)

Slackware ports

The article says:

"Slackware for the IBM S/390 architecture is also still actively developed and maintained in both -current and -stable forms."

I'm not sure it is still true. The latest Slack390 release is 11.0 [1] and according to the Changelog there has been no activity in the project since June 2009 [2]. The project doesn't look actively developed to me, it appears to be dead. What do you think?

[1] See http://distro.ibiblio.org/pub/linux/distributions/slack390/

[2] See http://distro.ibiblio.org/pub/Linux/distributions/slack390/slack390-current/ChangeLog.txt —Preceding unsigned comment added by 88.149.251.171 (talk) 19:51, 23 November 2010 (UTC)