After beating down all the deamons, I was finally able to get 64-current loaded on my CD-Romless computer via, stealing a CD Drive from another machine, booting with disk 1.iso only, and then using NFS to complete the installation. I think I am throwing in the towel trying to get USB sticks to boot. I don't get what the problem is, but I have had no luck with Sandisk Cruzers or PNY sticks.

Now that I have installed it, I know that I can use Slackpkg to keep it "current" with "current".

But what about when 64-bit is "official"? Can you simply point Slackpkg to new mirror of 13-64_bit(or whatever the official mirror will be called) and do the upgrade/update?

Latest slackpkg mirrors list has listings for 13.0

However they result in 404 errors when you use them to update from.

It is my understanding that -current will become 13, and then sometime after that a new -current will develop.


In the meantime I am using -current mirrors until the 13 mirrors become in use

And that was going to be my next questions. How long will "current" stay as the "official" before development takes back over? Just trying to figure out if updating current is best, or to just do a brand new install when the official comes out??

First of all, -currrent is the testing branch, and should not be referred
to as "the official" in the sense that you seem to use it.

On the day that Slackware-13.0 is released, if you have updated everything
in Slackware -current, you will basically have the same thing. You can use
Alpha Geek's sligdo to change your -current to 13.0. This will essentially
change what you have into the Slackware-13.0 release.

When Slackware-13.0 is released, Pat and The Core Team will enjoy a time of
rest before working on new packages for the next testing, or -current, cycle.

If you want to run -current all the time, you should be doing so with either
an eye to help test new software, or play with a machine you can hose which
will not cause you to break out in sweats. So if you don't want to chance the
hosing of a system you rely upon for daily work, run the stable release and
not -current. If it does not matter that you might break something on your
system, or you want to help test the new software, run -current.

Bruce, I think you mis-understoond me. I meant that when "current" goes to "official", how long will "current" and "official" be the same until development begins on "current" again. I should have been more clear. My fault...

Yup, this is a computer I am playing with. Eventually, I will move it in to my server rack but only AFTER 64 goes official. Right now, I'm just doing some testing.

Bruce, as always, you are very helpful.