LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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 05-04-2010, 02:47 PM   #46
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,564
Blog Entries: 1

Rep: Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024

Quote:
Originally Posted by GazL View Post
You know, when I see the confusion in this thread, I can't help but think Ubuntu has the right idea with their silly animal names. Therefore I propose that the next current be called "Slacking Snake".
or 'swift salamander'
 
Old 05-04-2010, 02:52 PM   #47
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware 14.1 64-bit with multilib
Posts: 2,074

Rep: Reputation: 199Reputation: 199
Eww.. Lets just leave the 'wannabe pithy' naming schemes to Ubuntu.
 
Old 05-04-2010, 03:02 PM   #48
GazL
Senior Member
 
Registered: May 2008
Posts: 3,392

Rep: Reputation: 917Reputation: 917Reputation: 917Reputation: 917Reputation: 917Reputation: 917Reputation: 917Reputation: 917
Quote:
Originally Posted by Jeebizz View Post
Eww.. Lets just leave the 'wannabe pithy' naming schemes to Ubuntu.
Indeed. But what I was alluding to is that Slackware's development cycle is more or less the same as Ubuntu's except all our animals are called 'current', but each current is still a different animal.
 
Old 05-04-2010, 03:04 PM   #49
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,564
Blog Entries: 1

Rep: Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024
Quote:
Agree. So it will be nice if people who decide to stay with slack-current will be provided with some help or advice.
You can complain on many things in Slackware (well, not really) but you can't complain on the level of support out there. There are lots of knowledgeable guys here on LQ. Furthermore, slackware devs are regulars here and in some other places like irc and alt.os.linux.slackware. Last but not least, you've got excellent documentation online (slackbook, slackwiki, etc.)


Quote:
Perhaps there are readers of this thread who are now curious what is it all about, why some have slack-current other don't have, and how they can get slack-current. Is it some kind of a mystery? I suppose they also should be given a simple explanation. What is it, how it works
Isn't that what a number of LQ members (including AlienBOB - slackware developer) did in this thread? Furthermore, AlienBOB has an excellent script to create -current isos on his website.

What else does one need to be happy?
 
Old 05-04-2010, 03:30 PM   #50
GazL
Senior Member
 
Registered: May 2008
Posts: 3,392

Rep: Reputation: 917Reputation: 917Reputation: 917Reputation: 917Reputation: 917Reputation: 917Reputation: 917Reputation: 917
Ok, one last try. Perhaps this example will clear things up....

OpenBSD also works with 'current' and 'stable'. Their system works like this.
Code:
Current ------------------------------------------------------------------------------>
                |Release 1             |                        |
                                       |Release 2               |
                                                                |Release3
In OpenBSD, current is a continuous entity and each Release is a point in time snapshot/fork of current.

Now, compare to the Slackware way of doing it:
Code:
Current ---------| Stable 1------------------------------------------------------------>
                                |Current -----------------> | Stable 2------------------------->
                                                                             | Current -------------->
Unlike OpenBSD, at certain points in time there is no such thing as 'Current'. Current starts, runs for a while and then turns into the next Stable. Then after a short while a new 'current' forks from stable.


If that doesn't show why current doesn't really exist in it's own right, then I'm at a loss to explain it any better. But if you can accept that it doesn't exist, you'll see why it doesn't need a logo too.
 
Old 05-04-2010, 03:40 PM   #51
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,170

Rep: Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534
You can find Eric's -current build script at his site (in my signature). There is a lot of support on this forum and on the Internet for Slackware stable and -current. However, if you're choosing to run -current you are expected to be able to trouble-shoot some issues on your own.
The Slackware Team (Pat, Robby, Eric, et al) is very busy at the moment working on 13.1.
 
Old 05-04-2010, 03:46 PM   #52
igadoter
Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: slack 12.2, debian-Trinity , openbsd
Posts: 729

Original Poster
Rep: Reputation: 56
Let take closer look at your pictures GazL. IMO they prove in the contrary:
there are no really big differences between how are developed openbsd and slackware.
 
Old 05-04-2010, 04:31 PM   #53
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
Quote:
Originally Posted by igadoter View Post
Let take closer look at your pictures GazL. IMO they prove in the contrary:
there are no really big differences between how are developed openbsd and slackware.
There aren't a lot of differences between a living person and one that just died.
 
Old 05-04-2010, 06:21 PM   #54
igadoter
Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: slack 12.2, debian-Trinity , openbsd
Posts: 729

Original Poster
Rep: Reputation: 56
Quote:
Originally Posted by Richard Cranium View Post
There aren't a lot of differences between a living person and one that just died.
No idea what are you talking about. Can only guess. Can you explain?
 
Old 05-05-2010, 11:28 AM   #55
ROXR
Member
 
Registered: Jan 2009
Location: Spain
Posts: 110
Blog Entries: 1

Rep: Reputation: 20
Quote:
Originally Posted by igadoter View Post
No idea what are you talking about. Can only guess. Can you explain?
I imagine that he say, because Open BSD is some dead and slackware is full life

Last edited by ROXR; 05-05-2010 at 11:30 AM.
 
Old 05-05-2010, 11:58 AM   #56
broken
Member
 
Registered: Apr 2010
Location: Your mom's trailer
Distribution: NetBSD
Posts: 31

Rep: Reputation: 15
Quote:
Originally Posted by ROXR View Post
I imagine that he say, because Open BSD is some dead and slackware is full life
Or the other way around
 
Old 05-05-2010, 11:13 PM   #57
afreitascs
Member
 
Registered: Aug 2004
Location: Brasil
Distribution: Slackware_Cur-64_mult
Posts: 433

Rep: Reputation: 30
living person: A person who possesses life.
dead person: A person who does not have life.

Well at this point should be to define what life would be .... Tricky, no?

Last edited by afreitascs; 05-05-2010 at 11:15 PM.
 
Old 05-06-2010, 06:58 AM   #58
igadoter
Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: slack 12.2, debian-Trinity , openbsd
Posts: 729

Original Poster
Rep: Reputation: 56
Quote:
Originally Posted by afreitascs View Post
living person: A person who possesses life.
dead person: A person who does not have life.

Well at this point should be to define what life would be .... Tricky, no?
Nice but what about zombie?
zombie: a dead person who possesses life (and looks ugly).
 
Old 05-06-2010, 09:27 AM   #59
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
Quote:
Originally Posted by igadoter View Post
No idea what are you talking about. Can only guess. Can you explain?
"Not many differences" != "Not many important differences"
 
Old 05-07-2010, 02:46 PM   #60
vigi
Member
 
Registered: May 2009
Location: australia
Distribution: slackware
Posts: 177

Rep: Reputation: 27
The reason other logos are more memorable than Slackware; You have to keep booting up.
You see the slackware logo once - and get on with you work.

Slackware stable can get boring at times; because it does not break.
 
  


Reply


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
updating Slack 10.2 with slack-current isos nacha Slackware 2 06-02-2006 08:52 PM
Slack v. 10.2 or current nacha Slackware 2 05-20-2006 02:21 PM
Change Suse Logo to KDE Logo little_penguin Suse/Novell 2 04-05-2005 05:35 PM
using slack 9 CD to install slack current mr_mandrill Slackware - Installation 1 06-20-2004 01:23 AM
current Slack-Current giving troubles? r_jensen11 Slackware 5 02-02-2004 05:08 PM


All times are GMT -5. The time now is 11:25 PM.

Main Menu
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