The official slackware linux mirror (RU.Tomsk)
About
The mirror to daily syncing with slackware.mirrors.tds.net
Supported versions is 11.0 and higher. The "current" branch included.
In additional we have "slackbuilds" mirror here, see links below.

Mirror links
Both ftp & http proto supported
http://slackware.tsu.ru/slackware/slackware-current
http://slackware.tsu.ru/slackware/slackware64-current
http://slackware.tsu.ru/slackware/slackware-VERSION
http://slackware.tsu.ru/slackware/slackware64-VERSION
http://slackware.tsu.ru/slackbuilds

Latest updates
  • slackware-12.2: Fri Oct 18 02:41:09 UTC 2013
  • slackware-13.37: Tue Jun 19 22:35:25 UTC 2018
  • slackware-14.1: Tue Jun 19 22:35:25 UTC 2018
  • slackware-14.2: Tue Jun 19 22:35:25 UTC 2018
  • slackware-current: Tue Jun 19 22:35:25 UTC 2018
  • slackware64-current: Tue Jun 19 22:35:25 UTC 2018

  • Helpful resources
    Official Slackware web http://slackware.com
    Official SlackBuilds repo http://slackbuilds.org

    Full ChangeLog links of latest
    Slackware current
    Slackware64 current
    Slackware 14.2
    Slackware64 14.2
    Docs
    The SlackBook site (Eng)
    SlackBook 2 (Rus,PDF) 1.2Mb

    ISOs
    http://slackware.tsu.ru/slackware/slackware-iso
    http://slackware.tsu.ru/slackware/slackware-current-iso
    The current ISOs builds as requested. Feel free to mail me.

    Contacts
    email: snelius[at]tsu.ru
    Tail of the ChangeLogs
    14.2 (x86)

    Tue Jun 19 22:35:25 UTC 2018
    patches/packages/gnupg-1.4.23-i586-1_slack14.2.txz: Upgraded.
    Sanitize the diagnostic output of the original file name in verbose mode.
    By using a made up file name in the message it was possible to fake status
    messages. Using this technique it was for example possible to fake the
    verification status of a signed mail.
    For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12020
    (* Security fix *)
    Current (x86)

    Tue Jun 19 22:35:25 UTC 2018
    a/acl-2.2.53-i586-1.txz: Upgraded.
    a/attr-2.4.48-i586-1.txz: Upgraded.
    n/gnupg-1.4.23-i586-1.txz: Upgraded.
    Sanitize the diagnostic output of the original file name in verbose mode.
    By using a made up file name in the message it was possible to fake status
    messages. Using this technique it was for example possible to fake the
    verification status of a signed mail.
    For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12020
    (* Security fix *)
    x/libXaw3d-1.6.3-i586-1.txz: Upgraded.
    x/libinput-1.11.1-i586-1.txz: Upgraded.
    x/xf86-input-mouse-1.9.3-i586-1.txz: Upgraded.
    testing/packages/pkgtools-15.0-noarch-20.txz: Rebuilt.
    This update is a bit scarier than usual, so we're going to test it here
    first and then move it into the main tree in a couple of days if there
    are no serious bug reports. It's well-tested here, and works with the
    slackpkg that's in -current now, but I don't know about slackpkg+ so that's
    another reason to let it cool down here first. The purpose of this update
    is to migrate the package database and directories from /var/log to
    /var/lib/pkgtools. /var/log was never a good place for this data, as it is
    considered by many to be a directory that could be wiped to free up some
    space. Originally the package database was in /var/adm, but the FSSTND
    (later FHS) group decided that directory should be a symlink to /var/log,
    and I went along with that since it was years ago and I was a n00b and didn't
    know any better. /var/lib/pkgtools will be a better and safer location.
    The removed_packages and removed_scripts directories are really just logs
    that aren't actually used for anything - those will remain under /var/log,
    but moved into /var/log/pkgtools. Everything under /var/log will be
    considered potentially non-permanent by the pkgtools - if any directories or
    symlinks disappear from there, the pkgtools will automatically recreate them
    as needed. In fact, the migration process will create symlinks from all the
    old directory locations to the new ones, so anything that expects the old
    locations (including slackpkg, for now) should continue to work. Once this
    moves into the main tree, the plan is to fix other packages to use the new
    installer script directory (/var/lib/pkgtools/setup) and change the installer
    and slackpkg to use the new native locations for everything. When slackpkg
    is changed over to use the new native locations, I'll also make sure to float
    that in testing/ for a few days before moving it to the main tree to avoid
    more unintentional disruption to slackpkg+ users.
    Be aware that the package database migration is a one-way operation, but even
    so if you later downgrade to an older version of the pkgtools it will still
    work through the compatibility symlinks.
    Current (x86_64)

    Tue Jun 19 22:35:25 UTC 2018
    a/acl-2.2.53-x86_64-1.txz: Upgraded.
    a/attr-2.4.48-x86_64-1.txz: Upgraded.
    n/gnupg-1.4.23-x86_64-1.txz: Upgraded.
    Sanitize the diagnostic output of the original file name in verbose mode.
    By using a made up file name in the message it was possible to fake status
    messages. Using this technique it was for example possible to fake the
    verification status of a signed mail.
    For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12020
    (* Security fix *)
    x/libXaw3d-1.6.3-x86_64-1.txz: Upgraded.
    x/libinput-1.11.1-x86_64-1.txz: Upgraded.
    x/xf86-input-mouse-1.9.3-x86_64-1.txz: Upgraded.
    testing/packages/pkgtools-15.0-noarch-20.txz: Rebuilt.
    This update is a bit scarier than usual, so we're going to test it here
    first and then move it into the main tree in a couple of days if there
    are no serious bug reports. It's well-tested here, and works with the
    slackpkg that's in -current now, but I don't know about slackpkg+ so that's
    another reason to let it cool down here first. The purpose of this update
    is to migrate the package database and directories from /var/log to
    /var/lib/pkgtools. /var/log was never a good place for this data, as it is
    considered by many to be a directory that could be wiped to free up some
    space. Originally the package database was in /var/adm, but the FSSTND
    (later FHS) group decided that directory should be a symlink to /var/log,
    and I went along with that since it was years ago and I was a n00b and didn't
    know any better. /var/lib/pkgtools will be a better and safer location.
    The removed_packages and removed_scripts directories are really just logs
    that aren't actually used for anything - those will remain under /var/log,
    but moved into /var/log/pkgtools. Everything under /var/log will be
    considered potentially non-permanent by the pkgtools - if any directories or
    symlinks disappear from there, the pkgtools will automatically recreate them
    as needed. In fact, the migration process will create symlinks from all the
    old directory locations to the new ones, so anything that expects the old
    locations (including slackpkg, for now) should continue to work. Once this
    moves into the main tree, the plan is to fix other packages to use the new
    installer script directory (/var/lib/pkgtools/setup) and change the installer
    and slackpkg to use the new native locations for everything. When slackpkg
    is changed over to use the new native locations, I'll also make sure to float
    that in testing/ for a few days before moving it to the main tree to avoid
    more unintentional disruption to slackpkg+ users.
    Be aware that the package database migration is a one-way operation, but even
    so if you later downgrade to an older version of the pkgtools it will still
    work through the compatibility symlinks.
    © Snelius (2006-2018). Hosted@TSUNet