Slackware Release Candidate x86_64 Architecture Changelog
 

Wed Jul 1 16:04:35 CDT 2009
Hi folks -- the TODO isn't entirely empty here, but it's pretty much down
to minor nits, and so we're going to call this release candidate #1 and
(mostly) freeze further updates unless they happen to fix problems.
Regarding the kernel, 2.6.29.x has been well tested with this userspace
and seems like the best choice to ship for production use. Perhaps we
can put something else (at least source and configs) in /testing, though.


Rest of it here:

ftp://ftp.osuosl.org/pub/slackware/s.../ChangeLog.txt

Cool!!

Very cool!! Looks like PV is getting close to releasing the latest, greatest Slackware.:)

Welcome rc#1 !

Already used Eric's magic rsync script to create a fresh DVD ISO, burning it now and about to install it on another box.

Now you need to post a Slackware monitor superkaramba thing for Slackware for x86_64.
The old one doesn't work on it.

sweet!

I'll see what I can come up with Bruce!

Slackware-current ChangeLog - Next Release - RC1
 

It's getting closer!

Wed Jul 1 16:04:35 CDT 2009
Hi folks -- the TODO isn't entirely empty here, but it's pretty much down
to minor nits, and so we're going to call this release candidate #1 and
(mostly) freeze further updates unless they happen to fix problems.
Regarding the kernel, 2.6.29.x has been well tested with this userspace
and seems like the best choice to ship for production use. Perhaps we
can put something else (at least source and configs) in /testing, though.

Read more: ftp://ftp.osuosl.org/pub/slackware/s.../ChangeLog.txt

Check before posting a new thread:

http://www.linuxquestions.org/questi...0/#post3593644

Whoops! My apologies. Thanks for the link to the earlier post.

Peace.

So, no Firefox 3.5 in 13.0.

not necessarily, like the changelog said the TODO is not entirely empty. There is a still a good chance it will make it in. If not its a pretty simple self upgrade.

Slackware 13.0 Now At Release Candidate Stage
 

The upcoming slackware 13.0 is now at release candidate stage according to the change log,here is a snippet of the changelog:-

Hi folks -- the TODO isn't entirely empty here, but it's pretty much down
to minor nits, and so we're going to call this release candidate #1 and
(mostly) freeze further updates unless they happen to fix problems.
Regarding the kernel, 2.6.29.x has been well tested with this userspace
and seems like the best choice to ship for production use. Perhaps we
can put something else (at least source and configs) in /testing, though.

todds

Great news! I'm getting impatient :).

Excellent!!! It's getting closer and closer!!!

Really great news. Looking forward to it :)

Neat ! It might be out in a few weeks. I'm almost done with exams, so it might be just in time :D

Unofficial ISOs at ftp://ftp.slackware.no/pub/linux/ISO...ent-ISO-build/

I'm 100% convinced firefox 3.5 will be shipped into final release.

If not, it doesn't matter, I'll build it myself anyway because I update it often.

Hi,
Why? You could build your own with 'mirror-slackware-current.sh' from a mirror of choice.

This link and others are available from 'Slackware-Links'. More than just Slackware® links!

Hmmm,

yesterday KDE 4.3rc1 was released ... It means that 4.3 should be there recently soon. Just wondering will it be included in Slackware-13.

Anyway, the huge work is already done and a wonderful new Slackware is approaching. Wonderful. Thanks again to all the people from the other side of the monitor ( I mean Slackware developing team :).

Firefox is of course a very good browser but it is just one package, which is fairly easy to upgrade to as soon as the package is ready. And it will not require a lot of magic. Simply 'upgradepkg ...'.

We have a beautiful wicd wifi manager in /extra. Which makes very easy to set up wireless connections. The only thing I am missing is some kind of manager for bluez. And maybe soon we should switch to bluez-4? I spent two days, trying to use my Iphone 3G with OS 3.0 as a modem. But unfortunately I didn't find a solution to this. I believe, it should be very easy to do through some graphical application - bluetooth manager (like wicd for wifi management).

Anyhow, awaiting for 13. And meanwhile running current x64.

best regards,
Vladimir

Because I can have my ISP mirror the ISO directly which will allow me to download it and not count toward my monthly quota.

Anyone try out kvpnc? I have tried this on another distro and it kept disconnecting. I connect to pptp VPN at work and would like to know if anyone has tried it or has had any problems.

Wow....my -current will soon morph into the big one-three!

Absolutely fantastic work and a sincere tip 'o the hat to Pat and the entire Development Team.

Well guys, I'd wait KDE4.3 release, the 4.2 still gives me little problems, sometimes it crashes and returns me some bug to report to the official team, I've some kwin effect enabled, wobbling windows and cube 3D(I rarely use it), I use an Intel Graphic Cards with the latest robby experimental drivers...It will be a great version of slackware :D Thank you Pat!

It will be my first time too :D

I hope KDE 4.3 can be polished on time =D

No KDE 4.3 either.

Eric

I agreed with Eric. KDE 4.3 will be too late to be tested and it *may* contains more bugs, since it contains huge changes in the core itself

I think you people wanting the bleeding edge should consider another distro. Slackware is about stability not bleeding edge, and yet I see many comments here that suggest many people want Pat V to stuff the latest bleeding edge software into the newest release then shove it out the door. I recommend Fedora Core for you people.

I'm glad Pat V resists such suggestions, otherwise Slackware would be very different.

I'll second that.

Well, I'll compile KDE4.3 by myself...

:D

Hi,
Good Luck! :)

And I'll third that sentiment. Pat V's approach to Slackware is the single biggest reason why I use it. And in looking around these forums, I think it has saved us all a lot of headaches.

Same same...................... :D

No problem. For my surprise, KDE 4.2.4 was amazing fast on my low end hardware (for the actual standards).

I'm looking forward to this. :) I will be out of position when 13.0 is released (I'm on holidays starting tomorrow); I'll be back home to my DVD burner in late July.
Many thanks to PV and the entire Slackware team for their dedication!

YES!!!!!!!!!!!!!

(13 exclamation marks)

gargamel

The next best thing to being there...
 

I guess if you want the closest thing to bleeding edge (Slackware) software packages, you'd have to run Slackware(64)-current.

Shingoshi

Hi,

Flame bait or just sarcasm?

Neither case...
 

Simply noting that if anyone wants KDE or any other package not present in the release, they'd have to use slackware(64)-current. Because that's where the packages are tested before being released. Although, probably for some packages, you'd have to use /testing. Because I think the /testing packages are only put in /*-current after having been somewhat established. However, KDE-4.2 is already in use, and therefore won't be in /testing for KDE-4.3. But I don't think anyone would want to use /testing without running /*-current as well. So in any case, you'll be using /*-current.

Shingoshi

slackware.com is down. Is the new version ready and they're just updating the site? :D

It doesn't mean anything...
 

I wouldn't read anything into the site being down. It's been down for about a day. It happens more than once.

This may not be related. But there's been a major cyber attack on the internet against many government and other sites. It happened over the weekend, when I first noticed the site was down.

Shingoshi

They had a hardware failure on the webserver. It is being worked
on now and will be back online asap. You can still get all the
Slackware goodness from ftp.slackware.com or another official
mirror.

Hi,
Actually problems were experienced on Friday 7-2-9 then down on the 4th.

Hello,

I have a little question.
I try to make a iso by using the mirror-current script.
But it fail again and again.

I do this : What did i wrong ?

Roelof

You messed up several things:

(1) you edited the script and probably changed the RSYNCURL variable instead of the RSYNCURLROOT variable

(2) you used a commandline option "-r slackware64-current" to try and mirror Slackware64. Instead you should use "-a x86_64" to change the architecture.

So, your commandline should become:
Eric

Which "magic rsync script" are you referring to?
Could you point me to it?

Thanx a lot.

Hi,
You can use Alien_Bob's-script 'mirror-slackware-current.sh'-UK from his toolbox.

The above link and others available from 'Slackware-Links'. More than just Slackware® links!

Here:

http://www.slackware.com/~alien/tools/

mirror-slackware-current.sh (Edit it to your needs)