LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
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 07-17-2009, 06:44 AM   #76
metrofox
Member
 
Registered: Jan 2009
Location: Palermo, Italy
Distribution: Slackware
Posts: 236

Rep: Reputation: 37
Talking


Quote:
Originally Posted by onebuck View Post
Hi,



I think you mean '2.6.29.6'.

Yeah sorry... Well guys, slackware 13 stable is near...In the /etc/slackpkg/mirrors there are now a lot of new mirrors, for ARMedslack, slackware64 etc...Today I upgraded the new X packages, and the new intel experimental drivers too... Really satisfied guys
 
Old 07-17-2009, 07:05 AM   #77
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,022
Blog Entries: 1

Rep: Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364
Hi,

I really like Slackware64 -current.
 
Old 07-19-2009, 06:30 PM   #78
gankoji
Member
 
Registered: Nov 2007
Location: Southern California
Distribution: Slackware-13.0 x86_64, Slackware 12.2, slackware64-current
Posts: 225

Rep: Reputation: 35
Just installed slackware64-current last night, and so far it's been a dream. Really like the move to a pretty stable version of KDE4, it looks slick! Whether or not it will hold up to my brutality tests is another story, but more on that later. It might be too soon to ask since this hasn't been around long, but does anyone have/is anyone currently working on a repository for 64 bit only packages? I'd love to see that, and am definitely down to pitch in if necessary.
 
Old 07-19-2009, 06:39 PM   #79
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
You want other 64-bit packages check Alien Bob's repo.

If you mirror it you can run "find . -name "*-x86_64-*.tgz"
from ./slackbuilds and find all Slackware for x86_64 pkgs.
 
Old 07-20-2009, 04:54 AM   #80
metrofox
Member
 
Registered: Jan 2009
Location: Palermo, Italy
Distribution: Slackware
Posts: 236

Rep: Reputation: 37
When slackware64 will be stable slacky.eu will adopt a repository right for slackware64
 
Old 07-20-2009, 08:53 AM   #81
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,380

Rep: Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840
latest beta sbopkg can be also a useful alternative to easily build what's needed.
 
Old 07-21-2009, 06:43 AM   #82
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,861
Blog Entries: 51

Rep: Reputation: Disabled
Should we be calling it Slackware-current or Slackware-13.0-RC1, or what, or doesn't it matter?
 
Old 07-21-2009, 07:37 AM   #83
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,180

Rep: Reputation: Disabled
Quote:
Originally Posted by brianL View Post
Should we be calling it Slackware-current or Slackware-13.0-RC1, or what, or doesn't it matter?
Slackware-current is already past 13.0-RC1. I would always call it slackware-current.

Eric
 
Old 07-21-2009, 07:39 AM   #84
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,861
Blog Entries: 51

Rep: Reputation: Disabled
Thanks, Eric. A Slackware by any name would run as sweet (apologies to Mr W.Shakespeare).
 
Old 07-24-2009, 01:30 AM   #85
foodown
Member
 
Registered: Jun 2009
Location: Texas
Distribution: Slackware
Posts: 609

Rep: Reputation: 218Reputation: 218Reputation: 218
Five days of eerie silence in the change log . . . could it almost be time? The anticipation is killing me.

This has been my first time ever to bother running the -current Slackware on my desktop . . . It's pretty neat. You wouldn't want to do it on a production server, but it sure is fun. The issues caused by pixman-0.15.10-x86_64-1.txz, for example, were driving me bonkers trying to figure out what I had done wrong with my custom 2.6.30.1 kernel until I saw 7/18's change log entry and breathed a huge sigh of relief.

I'll probably keep on running -current even after the stable release comes out. The view from the bleeding edge is cool and educational.

I have to wonder how many other slackers are running -current and doing daily updates for the first time due to the introduction of the x86_64 architecture, and how many of us will keep on doing it.

Has there been a poll on that?

Last edited by foodown; 07-24-2009 at 01:34 AM.
 
Old 07-24-2009, 02:01 AM   #86
Shingoshi
Member
 
Registered: Oct 2006
Location: Cochise County, Arizona
Distribution: Gentoo-AMD64 / Slackware64-Current
Posts: 474
Blog Entries: 28

Rep: Reputation: 34
Catching up with the rest of us!

Quote:
Originally Posted by foodown View Post
Five days of eerie silence in the change log . . . could it almost be time? The anticipation is killing me.

This has been my first time ever to bother running the -current Slackware on my desktop . . . It's pretty neat. You wouldn't want to do it on a production server, but it sure is fun. The issues caused by pixman-0.15.10-x86_64-1.txz, for example, were driving me bonkers trying to figure out what I had done wrong with my custom 2.6.30.1 kernel until I saw 7/18's change log entry and breathed a huge sigh of relief.

I'll probably keep on running -current even after the stable release comes out. The view from the bleeding edge is cool and educational.

I have to wonder how many other slackers are running -current and doing daily updates for the first time due to the introduction of the x86_64 architecture, and how many of us will keep on doing it.

Has there been a poll on that?
I've been running -current for years. All that time I've heard mostly disparaging remarks from others for doing so. Now that so many Slackware users who have earnestly wanted 64-bit have had little choice but to run -current, it's personally pleasing/rewarding to see so many now have the fears of running -current finally dispelled. I suspect the experience will have affected them to such degree, that many won't stop running -current. The primary benefit of this will be the greater feedback in the continued development of software for Slackware. Hence, we may see more progress occur more often.

Shingoshi
 
Old 07-25-2009, 06:27 AM   #87
daniel-slack
LQ Newbie
 
Registered: Jul 2009
Location: Bucharest
Distribution: Slackware
Posts: 8

Rep: Reputation: 0
Quote:
Originally Posted by Shingoshi View Post
The primary benefit of this will be the greater feedback in the continued development of software for Slackware. Hence, we may see more progress occur more often.
This sounds like a contradiction in terms. Users run Slackware particularly because it is well tested and the official release does not include unstable stuff, just as others prefer to run the stable version of Debian, not testing or Sid.

The entire purpose of the development process is focused on bringing about a stable and fast final release that can actually be used in production.

You on the other hand suggest that we should be using current not stable, in order to make better the stable release, that we won't be able to use anyway, since we're running current, in order to make stable better etc.

Thus you create a vicious circle, like an infinite loop in a badly written script.
 
Old 07-25-2009, 09:35 PM   #88
foodown
Member
 
Registered: Jun 2009
Location: Texas
Distribution: Slackware
Posts: 609

Rep: Reputation: 218Reputation: 218Reputation: 218
Quote:
Originally Posted by daniel-slack View Post
This sounds like a contradiction in terms. Users run Slackware particularly because it is well tested and the official release does not include unstable stuff . . .

You on the other hand suggest that we should be using current not stable, in order to make better the stable release, that we won't be able to use anyway, since we're running current, in order to make stable better etc.

Thus you create a vicious circle, like an infinite loop in a badly written script.
I don't think that is the suggestion . . . only that more users choosing to run -current on one of their machines expands the bed of testers and thus provides more feedback and perhaps quickens the improvement of the next stable release. Certainly the suggestion is not that John Q. Slacker should run -current. Of course the vast majority will continue to run the stable release. I see no contradiction.
 
Old 07-26-2009, 07:49 AM   #89
daniel-slack
LQ Newbie
 
Registered: Jul 2009
Location: Bucharest
Distribution: Slackware
Posts: 8

Rep: Reputation: 0
Be that as it may, I think there's enough trouble getting the system up and running anyway. (I don't mean the initial installation process per se, but the tweaking and tinkering afterwards.)

I am willing to do that, because the end result will be a fast and reliable system, but if I wanted to go for the bleeding edge (the latest and greatest, aka the buggiest and the suckiest), I would run Fedora, Ubuntu or something like that.

Slackware gives me the nice balance between very stable and very new software (as new as it can be, provided it's well tested - again, comparable with Debian Stable).

(In this regard, Red Hat/CentOS is doing a much lousier job - their stable release still uses kernel 2.6.18 - hello!?)

The Slackware criteria are fairly close to those from FreeBSD, which I would probably be running, if their device drivers and filesystems wouldn't suck big time, as they do - the Linux kernel does a much better job in terms of hardware recognition and the filesystems supported in Linux are great (JFS from AIX, XFS from IRIX, ext2/3/4, ReiserFS etc.)
 
Old 07-29-2009, 09:12 AM   #90
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware 14.1, Slackware64-current, OpenBSD 5.5
Posts: 4,126

Rep: Reputation: 519Reputation: 519Reputation: 519Reputation: 519Reputation: 519Reputation: 519
Smile

Quote:
Originally Posted by daniel-slack View Post

Slackware gives me the nice balance between very stable and very new software (as new as it can be, provided it's well tested - again, comparable with Debian Stable).

(In this regard, Red Hat/CentOS is doing a much lousier job - their stable release still uses kernel 2.6.18 - hello!?)

The Slackware criteria are fairly close to those from FreeBSD, which I would probably be running, if their device drivers and filesystems wouldn't suck big time, as they do - the Linux kernel does a much better job in terms of hardware recognition and the filesystems supported in Linux are great (JFS from AIX, XFS from IRIX, ext2/3/4, ReiserFS etc.)
I will agree with you on your first point. I love the fact that Slackware's software is thoroughly tested, highly stable, and very reliable. I enjoy setting up a new Slackware box after the release of a new version of Slackware. The damn thing will run forever.

I've had very good luck with hardware identification with FreeBSD. I've run FreeBSD 5.x-7.x on Plll machines, and am currently dual booting Slackware 12.2 with FreeBSD 7.2-amd64 on my Intel Core Duo unit. FreeBSD runs well and is stable as hell, like Slackware.
Slackware is and always will be my first love.
 
  


Reply

Tags
linux, poll, reiserfs, request, slackware64, xfs


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
LXer: Slackware 12.0 release candidate 1 is out. LXer Syndicated Linux News 0 06-16-2007 11:31 AM
LXer: Slackware 11.0 release candidate 4 LXer Syndicated Linux News 0 09-03-2006 08:54 AM
LXer: Debian release candidate architecture requalification results; amd64 is RC LXer Syndicated Linux News 0 12-27-2005 04:01 AM
LXer: Release candidate architecture requalification results; amd64 is RC LXer Syndicated Linux News 0 12-26-2005 10:46 AM


All times are GMT -5. The time now is 06:14 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