LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 12-31-2009, 04:58 AM   #916
gauchao
Member
 
Registered: Dec 2009
Distribution: SLACKWARE 14.1 64bit
Posts: 167

Rep: Reputation: 30

http://www.ylmf.org/

Just take a look... I don't speak chinese (anyone here can help?), but the page which sent me to this told the chinese are distributing a ubuntu-based-distro that looks like windows xp. This is being sold in my country and those who don't want to buy original m$ products can use it. Instead of selling pcs with windows OEM, which makes them more expensive, some stores here sell this os and fool their clients saying it is a "generic windows". That's what I said before: people want windows, they don't want to learn or don't have the time. So, we keep our beloved Slackware untouched and let them use this kind of cr-p. We don't have to change in order to satisfy the majority of PC users in the world. And it's not a mafioso statement.

As said by shadowsnipes:

Quote:
People can just turn their monitor off or look at a wall for a minute if they hate the text boot up.
Simple... again, DON'T MESS WITH SLACK!
 
Old 12-31-2009, 07:07 AM   #917
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,139
Blog Entries: 52

Rep: Reputation: Disabled
I'd like to see dancing paperclips and cute little Search dogs, please.
 
1 members found this post helpful.
Old 12-31-2009, 09:28 AM   #918
Lufbery
Senior Member
 
Registered: Aug 2006
Location: Harrisburg, PA
Distribution: Slackware 64 14.0
Posts: 1,142
Blog Entries: 29

Rep: Reputation: 119Reputation: 119
Quote:
Originally Posted by shadowsnipes View Post
Thank you, Woodsman, for all of your suggestions!
Your responses are nicely articulated too! You two, and others in this thread, have done a lot to keep it productive. Thank you.

Quote:
AGREED! Having no color in the boot scripts might bore people so much they consider putting a bootsplash in instead! As long as it is off by default it should not negatively affect function or stability. Done correctly, it should not complicate the scripts either.

I do this for my own scripts and would offer to provide patches, but many of my scripts are already thoroughly customized for other reasons. It is a pain to integrate the new changes with each Slackware version, but I like the coloring. Sometimes I think I turn on my computer just to look at it...
This made me laugh!
 
Old 01-04-2010, 08:07 AM   #919
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,272

Rep: Reputation: 186Reputation: 186
Go-OO.

Adding the G0-OO version of OpenOffice to /extra would be greatly appreciated. Seeing it as the default office suite would be even better.
 
Old 01-05-2010, 12:13 AM   #920
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,498

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
tnx to all the slackware team for the new glibc, gcc and kernel in current!
Santa Pat brought us shiny new toys to play with!

note: alien bob has already made available also his multilib versions

just be sure to read the update warning
Quote:
New kernels... and this deserves a mention/warning: the last bits of the "old" IDE/ATA system have been removed now. Everything should be using the libata based drivers now, so if you have any drives that are currently running as /dev/hda, /dev/hdb, etc., when you reboot with these kernels all drives will be renamed as /dev/sda, /dev/sdb, etc. If you had any /dev/sd* already, they might get renamed. Adjustments may be required in /etc/lilo.conf, /etc/fstab, the initrd, and elsewhere. Good luck!

Last edited by ponce; 01-05-2010 at 02:06 AM.
 
Old 01-05-2010, 07:19 AM   #921
AGer
Member
 
Registered: Oct 2007
Distribution: Slackware current
Posts: 136
Blog Entries: 22

Rep: Reputation: 19
Still under impression of the latest wave of very constructive ideas in this thread, just having read this http://beej.us/blog/?p=36 nice Arch and Slackware review, and still remembering how I unexpectedly ran over the explanation of the reasons why GNOME is not in the official Slackware, I hope I can formulate my desired change.

I would like Slackware to be officially explained. Linux is so mature now that it makes sense to do so in a formal, corporate style if you prefer, way.

Goals come first. Based on goals, the Design Principles, including priorities, are listed. Whenever the application of design principles is not evident, it is explained.

Thus, a reviewer will not have to reverse engineer the fact that Slackware follows the KISS principle. It looks like a correct guess, but even the best guess leaves some space for an error.

This will allow any proposed change can be explicitly positioned as a change to goals, design principles, or their application. This will result in better structured proposals compared to "users are afraid of the boot time messages". This one, for example, assumes that one of Slackware goals is to be as easy as possible for Slackware newbies.

Goals and Design Principles may go to www.slackware.com, the Slackbook may be radically changed (or another one added) to be a book about Slackware distribution, not a Linux survival guide with Slackware based examples, and some wiki/blog may be created where package maintainers may add comments.

For example, I checked Distrowatch and both Slackware and Arch are on Python 2.6.4. There must be some reason for that, especially when a very nice and absolutely current Python 3 is in Slackbuilds, but how can I find it? The kernel jumped from 29 to 32. Thus, 30 and 31 must be no good with some hints in the Net, but the latest stable Mandriva boldly uses 31.5. Would it be nice to get an official Slackware comment? Would it be nice for a newbie to read why there are that empty rcX.d directories in etc, there is no selinux, there are no less than 9 directories for the same lonely optical device in media, some being links and other not - all in one place - Slackbook?
 
Old 01-05-2010, 08:14 AM   #922
GooseYArd
Member
 
Registered: Jul 2009
Location: Reston, VA
Distribution: Slackware, Ubuntu, RHEL
Posts: 183

Rep: Reputation: 46
Quote:
Originally Posted by AGer View Post

I would like Slackware to be officially explained. Linux is so mature now that it makes sense to do so in a formal, corporate style if you prefer, way.
you want a corporate blurb for a project with bob dobbs as the mascot?
 
Old 01-05-2010, 09:09 AM   #923
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Rep: Reputation: 137Reputation: 137
Quote:
tnx to all the slackware team for the new glibc, gcc and kernel in current!
Santa Pat brought us shiny new toys to play with!

note: alien bob has already made available also his multilib versions
Freshly installed to a new partition, I didn't want to wreck my working version of current. Anyway the boot process feels much faster, 15 seconds of BIOS to bootloader, 45 seconds to KDE (including my slow password typing) and another 15 seconds to load all the stuff I load at the beginning of KDE. I estimate that it is about 15-20 seconds faster.

Now we have the new toolchain it can't be too long until 13.1!

samac
 
Old 01-05-2010, 10:53 AM   #924
a4z
Member
 
Registered: Feb 2009
Posts: 526

Rep: Reputation: 188Reputation: 188
Quote:
Originally Posted by samac View Post
Now we have the new toolchain it can't be too long until 13.1!
better wait for KDE 4.4.0
because if slackware stays as it is now in current everything is so stable that it could become boring
 
Old 01-05-2010, 01:29 PM   #925
AGer
Member
 
Registered: Oct 2007
Distribution: Slackware current
Posts: 136
Blog Entries: 22

Rep: Reputation: 19
Quote:
Originally Posted by GooseYArd View Post
you want a corporate blurb for a project with bob dobbs as the mascot?
No, I would not go that far. Thanks for the offer, though.
 
Old 01-05-2010, 05:13 PM   #926
stoggy
Member
 
Registered: Jun 2008
Location: Dallas, TX
Distribution: Slackware and FC
Posts: 107

Rep: Reputation: 20
Quote:
Originally Posted by brianL View Post
I'd like to see dancing paperclips and cute little Search dogs, please.
A gui installer, more spam from the slackware newsgroup and every package that slackware doesn't include as a package as a package. Possibly even a slackware installation key manager so I can keep up with all the installation keys that are required when I install slackware.

Because reading and compiling from source is so over rated these days.


How about LSB home dirs?
 
Old 01-05-2010, 05:58 PM   #927
GooseYArd
Member
 
Registered: Jul 2009
Location: Reston, VA
Distribution: Slackware, Ubuntu, RHEL
Posts: 183

Rep: Reputation: 46
3-D manpages
 
Old 01-09-2010, 03:52 PM   #928
leeeoooooo
Member
 
Registered: Jan 2009
Distribution: Slackware 14.0
Posts: 104

Rep: Reputation: 18
Quote:
Originally Posted by AGER View Post
I would like Slackware to be officially explained.
Oh, nothing so "formal, corporate style", nothing so "PINK", but I have from time-to-time found myself wishing for a "rationale" file...

So much of what I know about the philosophy of Slackware comes from bits and pieces I've picked up from articles and interviews from here and there. It would be nice to have a README with answers to frequently asked questions like:

How did this get started?
What are the priorities?
Why Lilo and not Grub?
Why so many command shells?
Why KDE but not Gnome?
Why Python 2.6 but not Py3K?
Why KOffice but not OOo?
Will we see Mono or GNUstep?
How is this decided, what gets included and what doesn't?
Why isn't this pretty like Unbutu?
Do I really have to compile any additional packages from source?

I now know and appreciate the answers to most of these, but I still hear them (and others) from newbies, and as AGer says, reviewers seem to flounder trying to guess the answers.

Last edited by leeeoooooo; 01-09-2010 at 03:55 PM.
 
Old 01-09-2010, 04:09 PM   #929
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Rep: Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534
Quote:
So much of what I know about the philosophy of Slackware comes from bits and pieces I've picked up from articles and interviews from here and there. It would be nice to have a README with answers to frequently asked questions like:
Most of what you seek is readily explained by the fact that Pat is a Deadhead.

Seems as though you have already performed most of the work to provide what you seek. Return to the various web links where you found the information from which you rhetorically asked your questions. Massage the information into a nice text file. Post the file somewhere, notify folks on this forum, and ask for reviews and commentary.
 
Old 01-09-2010, 07:19 PM   #930
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,383

Rep: Reputation: Disabled
Well since you wrote the questions but did not add the answers, I will give my view on them:

Quote:
Originally Posted by leeeoooooo View Post
How did this get started?
Read the interview with Pat Volkerding
Quote:
What are the priorities?
To keep everything working as stable as possible
Quote:
Why Lilo and not Grub?
lilo always works
Quote:
Why so many command shells?
It's not that many... different people prefer different shells
Quote:
Why KDE but not Gnome?
When gnome became too hard to maintain for Slackware, Pat Volkerding removed it from the distribution. From the changelog:
Quote:
gnome/*: Removed from -current, and turned over to community support and
distribution. I'm not going to rehash all the reasons behind this, but it's
been under consideration for more than four years. There are already good
projects in place to provide Slackware GNOME for those who want it, and
these are more complete than what Slackware has shipped in the past. So, if
you're looking for GNOME for Slackware -current, I would recommend looking at
these two projects for well-built packages that follow a policy of minimal
interference with the base Slackware system:

http://gsb.sf.net
http://gware.sf.net

There is also Dropline, of course, which is quite popular. However, due to
their policy of adding PAM and replacing large system packages (like the
entire X11 system) with their own versions, I can't give quite the same sort
of nod to Dropline. Nevertheless, it remains another choice, and it's _your_
system, so I will also mention their project:

http://www.dropline.net/gnome/

Please do not incorrectly interpret any of this as a slight against GNOME
itself, which (although it does usually need to be fixed and polished beyond
the way it ships from upstream more so than, say, KDE or XFce) is a decent
desktop choice. So are a lot of others, but Slackware does not need to ship
every choice. GNOME is and always has been a moving target (even the
"stable" releases usually aren't quite ready yet) that really does demand a
team to keep up on all the changes (many of which are not always well
documented). I fully expect that this move will improve the quality of both
Slackware itself, and the quality (and quantity) of the GNOME options
available for it.

Folks, this is how open source is supposed to work. Enjoy. :-)
Quote:
Why Python 2.6 but not Py3K?
Not enough requests perhaps? You have to realize that usually Slackware follows a conservative path. Py3K is not fully compatible with the old versions.
Quote:
Why KOffice but not OOo?
Koffice integrates with KDE, OOo integrates with nothing, and it is a bitch to build.
Quote:
Will we see Mono or GNUstep?
I'll fight mono wherever I encounter it.
Quote:
How is this decided, what gets included and what doesn't?
Pat Volkerding decides, but the rest of the team always tries to sneak things in.
Quote:
Why isn't this pretty like Unbutu?
You're joking, right?
Quote:
Do I really have to compile any additional packages from source?
Of course not. There are many 3rd party package repositories out there. It's just that they are not formally associated with Slackware, like with other distributions.

Eric
 
2 members found this post helpful.
  


Reply

Tags
cd, live


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
Slackware future? coyctecm Slackware 12 02-01-2006 11:03 PM
Future of Slackware kratunko Slackware 30 08-12-2005 01:31 PM
Slackware features? rusty_slacker Slackware 49 12-02-2004 05:45 AM
what are the features of the new slackware 9? ethanchic Slackware 2 09-27-2002 07:15 PM


All times are GMT -5. The time now is 01:15 PM.

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