JohnT
01-23-2005, 03:05 AM
Slackware Current ChangeLog Notice.
The following additions have been made to The Current ChangeLog.txt
------------------------------------------------------------------
New Entry: Sat Jan 22 18:12:37 PST 2005
New Entry: "Goes to show, you don't ever know"
New Entry:
New Entry: Hi folks!
New Entry: I'm going to call this Slackware 10.1 beta 1, because
we're at a state
New Entry: where things are relatively stable. There have been a
great deal of
New Entry: improvements over Slackware 10.0, and it would be best to
get this out
New Entry: before trying to tackle the major changes for Slackware 11.
New Entry:
New Entry: As far as I know, there are no serious security issues
remaining in the
New Entry: -current tree at this time. There may still be a few image
decoder bugs, but
New Entry: these seem to be crash bugs at worst, if even that. I've
yet to hear of any of
New Entry: them allowing remote access, or privilege escalation. I do
not think they are
New Entry: worth delaying a Slackware release over. I'd like to get
to them, but my
New Entry: condition is preventing this, and so I'm going to tell it
like I think it is:
New Entry: The sky is not really falling, regardless of what you read
on BugTraq. If I
New Entry: am missing anything major though, please mail to security
at slackware.com and
New Entry: let me know about it. As always, I want this to be a
high-quality release.
New Entry:
New Entry: And about my status... I didn't want to have to bring
this up again, but
New Entry: since a lot of people are under the impression that I've
recovered and I'm
New Entry: just fine (and are beginning to make the usual demands of
my time ;-), I'd
New Entry: better clarify what's going on. Especially since I'm not
exactly fine.
New Entry:
New Entry: Back on Thu Nov 25, I posted in the ChangeLog that I
thought I had infective
New Entry: endocarditis (and was promptly flamed for self-diagnosing
again). After so
New Entry: much beating around the bush without getting a referral to
a cardiologist, I
New Entry: finally called one myself and waited the two weeks it takes
to get in. He is
New Entry: a top-notch doctor and heart surgeon (I was very lucky to
be able get in to see
New Entry: him), and with no planting of any suggestion from me
whatsoever came to the
New Entry: conclusion that it seemed to be infective endocarditis.
I'm still waiting for
New Entry: more test results, but it looks like I finally have someone
working on my side.
New Entry: So, lets hope that they get some conclusive diagnostics (I
get another echo on
New Entry: Wednesday), that I make it until they do, and that it's not
too late for this
New Entry: to be treated without a need for valve (or heart)
replacement. I've had a
New Entry: rough couple of weeks (well, months really, but especially
the last two weeks),
New Entry: and I have to say that while it's good to have a near-death
experience every
New Entry: couple of years to keep your head clear and your focus on
the important things
New Entry: in life, having one every morning is too often. With that
frequency, they
New Entry: start to become a distraction. ;-)
New Entry:
New Entry: So, this verson is going to be wrapped up pretty quickly.
I hope people
New Entry: will support the release, because I'm sure I'll have a lot
more bills before
New Entry: all of this is through, and I'm blowing through what little
money I've managed
New Entry: to save. Again, I'm not asking for donations, but I hope
that when Slackware
New Entry: 10.1 comes out that people wanting to help out will order
it. Also, in case
New Entry: of emergency I've left instructions with some very trusted
people, so nobody
New Entry: should have to worry that if something happens to me that
their Slackware
New Entry: systems will be orphaned and unsupported. It may be a long
road back for me,
New Entry: but there will be people taking care of security issues as
they crop up
New Entry: (like the folks at GUS-BR and SlackSec), and if I should
make an unplanned
New Entry: departure there are is a basic plan of succession in place.
New Entry:
New Entry: Thanks again to all the kind folks I've known over the
years, and I hope
New Entry: to know you for many more. :-)
New Entry:
New Entry: Your Humble Slackware Maintainer,
New Entry:
New Entry: Pat
New Entry:
New Entry: Now, on to...
New Entry: Today's Slackware changes:
New Entry: n/gnupg-1.2.7-i486-1.tgz: Reverted to gnupg-1.2.7 since it
produces
New Entry: working signatures for Slackware packages. GnuPG 1.4.x
will not be
New Entry: considered for slackware/n/ again until after the 10.1
release.
New Entry: This version works fine.
New Entry: xap/fluxbox-0.9.12-i486-1.tgz: Upgraded to fluxbox-0.9.12.
New Entry: xap/gimp-2.2.3-i486-1.tgz: Upgraded to gimp-2.2.3.
New Entry: xap/xchat-2.4.1-i486-1.tgz: Upgraded to xchat-2.4.1.
New Entry: xap/xfce-4.2.0-i486-1.tgz: Upgraded to xfce-4.2.0. :-)
New Entry: extra/slackpkg/slackpkg-1.3.1-noarch-3.tgz:
New Entry: Upgraded to slackpkg-1.3.1-noarch-3.
New Entry: extra/slacktrack/slacktrack-1.23-i486-1.tgz:
New Entry: Upgraded to slacktrack-1.23_1.
New Entry: testing/packages/gnupg-1.4.0-i486-1.tgz: Moved this back
to /testing
New Entry: because it's creating broken signatures for Slackware
packages.
New Entry:
testing/packages/linux-2.6.10/alsa-driver-1.0.8_2.6.10-i486-1.tgz:
New Entry: Compiled for Linux 2.6.10.
New Entry:
testing/packages/linux-2.6.10/kernel-generic-2.6.10-i486-1.tgz:
New Entry: Upgraded to Linux 2.6.10.
New Entry:
testing/packages/linux-2.6.10/kernel-headers-2.6.10-i386-1.tgz:
New Entry: Upgraded to Linux 2.6.10.
New Entry: (see the warning on this -- glibc should really be
recompiled to make
New Entry: use of these headers).
New Entry:
testing/packages/linux-2.6.10/kernel-modules-2.6.10-i486-1.tgz:
New Entry: Upgraded to Linux 2.6.10.
New Entry:
testing/packages/linux-2.6.10/kernel-source-2.6.10-noarch-1.tgz:
New Entry: Upgraded to Linux 2.6.10.
The following additions have been made to The Current ChangeLog.txt
------------------------------------------------------------------
New Entry: Sat Jan 22 18:12:37 PST 2005
New Entry: "Goes to show, you don't ever know"
New Entry:
New Entry: Hi folks!
New Entry: I'm going to call this Slackware 10.1 beta 1, because
we're at a state
New Entry: where things are relatively stable. There have been a
great deal of
New Entry: improvements over Slackware 10.0, and it would be best to
get this out
New Entry: before trying to tackle the major changes for Slackware 11.
New Entry:
New Entry: As far as I know, there are no serious security issues
remaining in the
New Entry: -current tree at this time. There may still be a few image
decoder bugs, but
New Entry: these seem to be crash bugs at worst, if even that. I've
yet to hear of any of
New Entry: them allowing remote access, or privilege escalation. I do
not think they are
New Entry: worth delaying a Slackware release over. I'd like to get
to them, but my
New Entry: condition is preventing this, and so I'm going to tell it
like I think it is:
New Entry: The sky is not really falling, regardless of what you read
on BugTraq. If I
New Entry: am missing anything major though, please mail to security
at slackware.com and
New Entry: let me know about it. As always, I want this to be a
high-quality release.
New Entry:
New Entry: And about my status... I didn't want to have to bring
this up again, but
New Entry: since a lot of people are under the impression that I've
recovered and I'm
New Entry: just fine (and are beginning to make the usual demands of
my time ;-), I'd
New Entry: better clarify what's going on. Especially since I'm not
exactly fine.
New Entry:
New Entry: Back on Thu Nov 25, I posted in the ChangeLog that I
thought I had infective
New Entry: endocarditis (and was promptly flamed for self-diagnosing
again). After so
New Entry: much beating around the bush without getting a referral to
a cardiologist, I
New Entry: finally called one myself and waited the two weeks it takes
to get in. He is
New Entry: a top-notch doctor and heart surgeon (I was very lucky to
be able get in to see
New Entry: him), and with no planting of any suggestion from me
whatsoever came to the
New Entry: conclusion that it seemed to be infective endocarditis.
I'm still waiting for
New Entry: more test results, but it looks like I finally have someone
working on my side.
New Entry: So, lets hope that they get some conclusive diagnostics (I
get another echo on
New Entry: Wednesday), that I make it until they do, and that it's not
too late for this
New Entry: to be treated without a need for valve (or heart)
replacement. I've had a
New Entry: rough couple of weeks (well, months really, but especially
the last two weeks),
New Entry: and I have to say that while it's good to have a near-death
experience every
New Entry: couple of years to keep your head clear and your focus on
the important things
New Entry: in life, having one every morning is too often. With that
frequency, they
New Entry: start to become a distraction. ;-)
New Entry:
New Entry: So, this verson is going to be wrapped up pretty quickly.
I hope people
New Entry: will support the release, because I'm sure I'll have a lot
more bills before
New Entry: all of this is through, and I'm blowing through what little
money I've managed
New Entry: to save. Again, I'm not asking for donations, but I hope
that when Slackware
New Entry: 10.1 comes out that people wanting to help out will order
it. Also, in case
New Entry: of emergency I've left instructions with some very trusted
people, so nobody
New Entry: should have to worry that if something happens to me that
their Slackware
New Entry: systems will be orphaned and unsupported. It may be a long
road back for me,
New Entry: but there will be people taking care of security issues as
they crop up
New Entry: (like the folks at GUS-BR and SlackSec), and if I should
make an unplanned
New Entry: departure there are is a basic plan of succession in place.
New Entry:
New Entry: Thanks again to all the kind folks I've known over the
years, and I hope
New Entry: to know you for many more. :-)
New Entry:
New Entry: Your Humble Slackware Maintainer,
New Entry:
New Entry: Pat
New Entry:
New Entry: Now, on to...
New Entry: Today's Slackware changes:
New Entry: n/gnupg-1.2.7-i486-1.tgz: Reverted to gnupg-1.2.7 since it
produces
New Entry: working signatures for Slackware packages. GnuPG 1.4.x
will not be
New Entry: considered for slackware/n/ again until after the 10.1
release.
New Entry: This version works fine.
New Entry: xap/fluxbox-0.9.12-i486-1.tgz: Upgraded to fluxbox-0.9.12.
New Entry: xap/gimp-2.2.3-i486-1.tgz: Upgraded to gimp-2.2.3.
New Entry: xap/xchat-2.4.1-i486-1.tgz: Upgraded to xchat-2.4.1.
New Entry: xap/xfce-4.2.0-i486-1.tgz: Upgraded to xfce-4.2.0. :-)
New Entry: extra/slackpkg/slackpkg-1.3.1-noarch-3.tgz:
New Entry: Upgraded to slackpkg-1.3.1-noarch-3.
New Entry: extra/slacktrack/slacktrack-1.23-i486-1.tgz:
New Entry: Upgraded to slacktrack-1.23_1.
New Entry: testing/packages/gnupg-1.4.0-i486-1.tgz: Moved this back
to /testing
New Entry: because it's creating broken signatures for Slackware
packages.
New Entry:
testing/packages/linux-2.6.10/alsa-driver-1.0.8_2.6.10-i486-1.tgz:
New Entry: Compiled for Linux 2.6.10.
New Entry:
testing/packages/linux-2.6.10/kernel-generic-2.6.10-i486-1.tgz:
New Entry: Upgraded to Linux 2.6.10.
New Entry:
testing/packages/linux-2.6.10/kernel-headers-2.6.10-i386-1.tgz:
New Entry: Upgraded to Linux 2.6.10.
New Entry: (see the warning on this -- glibc should really be
recompiled to make
New Entry: use of these headers).
New Entry:
testing/packages/linux-2.6.10/kernel-modules-2.6.10-i486-1.tgz:
New Entry: Upgraded to Linux 2.6.10.
New Entry:
testing/packages/linux-2.6.10/kernel-source-2.6.10-noarch-1.tgz:
New Entry: Upgraded to Linux 2.6.10.