Hi,

I have Slackware 10.2 running, but I've been looking at the changelog at
slackware.com and it would be nice to get all those changes onto the system.

I noticed in a post elsewhere on this group someone mentioned that 10.4
would be out soon. Does that mean that Slackware is adopting a
kernel-like version numbering scheme, where 10.3 would be a development
release? Does anyone have an idea when the next official release of
Slackware will be?

Someone else also mentioned Slackware 10.2+

Does this mean that somewhere, people are building ISO images of the
latest release (10.2) with all or some of Pat's upgraded packages on? If
so where can I download the ISO's from? BTW, I appreciate there are
instructions on slackware.com about building your own ISO's after
downloading all the packages - I'm just lazy :-)

What I think would be nice is a system of patch clusters, like Solaris
has. You just download the patch cluster, unzip and run it. It gets on
with patching all the relevant files. Its great :-)

Thanks!

Paul
~~~~~

Paul Duncan wrote:

> I noticed in a post elsewhere on this group someone mentioned that 10.4
> would be out soon.

i'd question that. that's nothing but a rumor, with no facts to back it up.
pat has mentioned a new release, but most likely that would be 11.0 and not
some 10.4

Hi Dominik,

Thanks for getting back to me.

Dominik L. Borkowski wrote:
[10.4 would be out soon.]
>
> i'd question that. that's nothing but a rumor, with no facts to back it up.
> pat has mentioned a new release, but most likely that would be 11.0 and not
> some 10.4

Okay, thanks very much. Just hope it comes out by March 5th.
TTFN!

Paul
~~~~~

Paul Duncan wrote:

> Okay, thanks very much. Just hope it comes out by March 5th.

If you're really anxious, some people [including me], create isos of
slackware-current. you can find mine at:

ftp://inferno.bioinformatics.vt.edu/...re-current-iso

On Fri, 17 Feb 2006 14:32:15 +0000, Paul Duncan wrote:

> Hi,
>
> I have Slackware 10.2 running, but I've been looking at the changelog at
> slackware.com and it would be nice to get all those changes onto the system.
>
> I noticed in a post elsewhere on this group someone mentioned that 10.4
> would be out soon. Does that mean that Slackware is adopting a
> kernel-like version numbering scheme, where 10.3 would be a development
> release? Does anyone have an idea when the next official release of
> Slackware will be?
>
> Someone else also mentioned Slackware 10.2+
>
> Does this mean that somewhere, people are building ISO images of the
> latest release (10.2) with all or some of Pat's upgraded packages on? If
> so where can I download the ISO's from? BTW, I appreciate there are
> instructions on slackware.com about building your own ISO's after
> downloading all the packages - I'm just lazy :-)
>
> What I think would be nice is a system of patch clusters, like Solaris
> has. You just download the patch cluster, unzip and run it. It gets on
> with patching all the relevant files. Its great :-)
>
> Thanks!
>
> Paul
> ~~~~~
>
You know, you can upgrade any packages which need to patched using files
from this directory:

MIRROR=http://some.mirror.somewhere/slackware
${MIRROR}/slackware-10.2/patches/packages/

You can upgrade to -current by upgrading your packages from this directory:
${MIRROR}/slackware-current/slackware

I refer to Slackware 10.2+ (informally) as some state beyond the default.

The easiest way to stay current (with either patches or -current) is to
use a local copy, built with rsync.

R=mirrors.xmission.com
S=slackware
V=slackware-current

DEST=/home/slackware
(cd $DEST && rsync -lptrv --progress --delete ${R}::${S}/${V} .)

(Choose a mirror appropriate for your location. You can minimize
the files to be downloaded if you fill out the "current" directory
with files from an "almost current" Slackware CD, say 10.2.)

From here you would verify each package has a good signature and upgrade
as appropriate.

cd /home/slackware/slackware-current/slackware
P=a
for i in $(find ${P}/. -type f | grep tgz$);do
upgradepkg --dry-run $i
done

It is a good idea to read this first:
http://mirrors.xmission.com/slackwar....2/UPGRADE.TXT

--
Douglas Mayne

Hi Douglas,

Thanks for the response!

Douglas Mayne wrote:

> You know, you can upgrade any packages which need to patched using files
> from this directory:
>
> MIRROR=http://some.mirror.somewhere/slackware
> ${MIRROR}/slackware-10.2/patches/packages/
>
> You can upgrade to -current by upgrading your packages from this directory:
> ${MIRROR}/slackware-current/slackware
>
> I refer to Slackware 10.2+ (informally) as some state beyond the default.
>
> The easiest way to stay current (with either patches or -current) is to
> use a local copy, built with rsync.
>
> R=mirrors.xmission.com
> S=slackware
> V=slackware-current
>
> DEST=/home/slackware
> (cd $DEST && rsync -lptrv --progress --delete ${R}::${S}/${V} .)
>
> (Choose a mirror appropriate for your location. You can minimize
> the files to be downloaded if you fill out the "current" directory
> with files from an "almost current" Slackware CD, say 10.2.)
>
> From here you would verify each package has a good signature and upgrade
> as appropriate.
>
> cd /home/slackware/slackware-current/slackware
> P=a
> for i in $(find ${P}/. -type f | grep tgz$);do
> upgradepkg --dry-run $i
> done
>
> It is a good idea to read this first:
> http://mirrors.xmission.com/slackwar....2/UPGRADE.TXT

Okay, I will give that a try over the weekend. Have a big Seagate
external drive, so backing up is not a problem. And I'll use
mirror.ac.uk since its usually quite fast. Looks a bit daunting, but
I've read the UPGRADE.TXT file, and it seems to make sense. I'll let you
know how I get on. Just had a quick try of rsync on my work box, but I
didn't install rsync on it (never needed it before!).

Thanks again!

Paul
~~~~~

On Fri, 17 Feb 2006 16:48:08 +0000, Paul Duncan wrote:

> Hi Douglas,
>
> Thanks for the response!
>
> Douglas Mayne wrote:
>
<snip>
>
> Okay, I will give that a try over the weekend. Have a big Seagate
> external drive, so backing up is not a problem. And I'll use
> mirror.ac.uk since its usually quite fast. Looks a bit daunting, but
> I've read the UPGRADE.TXT file, and it seems to make sense. I'll let you
> know how I get on. Just had a quick try of rsync on my work box, but I
> didn't install rsync on it (never needed it before!).
>
> Thanks again!
>
> Paul
> ~~~~~
>
I neglected to mention to be careful with rsync. rsync can do great
damage to your system, especially with the --delete option. It is picky
about dots and trailing slashes. Practice with it until you have it down
pat.

OT: A little more thought about safety could have helped here:
http://extras.sltrib.com/bagley/content/02142006.jpg

--
Douglas Mayne