Monthly snapshot announcement
Re: Monthly snapshot announcement
Yes, but you can also upgrade the installer before you install even if you use an older ISO (but that's obviously available only if you have network connectivilty)
Re: Monthly snapshot announcement
... Thanks for the precision Adrian.
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32
- dolphin_oracle
- Developer
- Posts: 20032
- Joined: Sun Dec 16, 2007 1:17 pm
Re: Monthly snapshot announcement
pro tip, everyone on mx17 get's the installer, just update mx-installer before installing.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Re: Monthly snapshot announcement
Hi Dolphin_oracledolphin_oracle wrote: ↑Sun Jun 10, 2018 1:12 pm ... everyone on mx17 get's the installer, just update mx-installer before installing.
... Maybe this can be done automatically (or tried ) with an other new installer (to try to update the installer before the install)
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32
Re: Monthly snapshot announcement
Uploaded new MX Linux monthly snapshots bit.ly/mx-monthly
about 30 updates, more relevant: Firefox, Thunderbird got updated, new MX Cleanup app, updated MX Live USB Maker to clarify the interface. The installer got some fixes
about 30 updates, more relevant: Firefox, Thunderbird got updated, new MX Cleanup app, updated MX Live USB Maker to clarify the interface. The installer got some fixes
Re: Monthly snapshot announcement
Get Your MX17.1 Linux June Snapshot with ZSYNC
Attchached find my zsync download scrypt ZSYNC_MX-17.1_June_x64.sh
which will load latest june snapshot from nearest sourceforge server.
Place the script in the same directory as one of those previous iso‘s you might
already have like:
MX-17_x64.iso, MX-17.1_x64.iso , MX-17.1_April_x64.iso or MX-17.1_April_x64.iso.
Make the script executable.
I've just download only remaing 13% as I had already the may-snapshot:
In addition: The script will fetch the signature keys to perform the file signature-verification.
Attchached find my zsync download scrypt ZSYNC_MX-17.1_June_x64.sh
which will load latest june snapshot from nearest sourceforge server.
Place the script in the same directory as one of those previous iso‘s you might
already have like:
MX-17_x64.iso, MX-17.1_x64.iso , MX-17.1_April_x64.iso or MX-17.1_April_x64.iso.
Make the script executable.
I've just download only remaing 13% as I had already the may-snapshot:
Code: Select all
#!/bin/bash
#---------------------------------------------------
# get Monthly MX Linux ISO with zsync
#---------------------------------------------------
# filename ZSYNC_MX-17.1_June_x64.sh
# fehlix 15-06-2018
# add available local ISO-sources here - newest last
SOURCE=MX-17_x64.iso
SOURCE=MX-17.1_x64.iso
SOURCE=MX-17.1_April_x64.iso
SOURCE=MX-17.1_May_x64.iso
# new ISO-target we want get with zsync
#
TARGET=MX-17.1_June_x64.iso
#----------------------------------------------------
# some fun @ fehlix
#----------------------------------------------------
function echodo () { echo "#>> : ${@}"; "${@}"; }
function doit () {
local R;
echo "#>> BEGIN: ${@}";
"${@}"; R=$?;
echo "#>> END : ${@}"; return $R;
}
##---------------------------------------------------
# do we have zsync
command -v zsync >&- || {
# opps we need to and install zsync
sudo apt-get update
sudo apt-get install zsync
}
##---------------------------------------------------
# prepare keys for signaure verificytion
# keyserver use either of those below - change if timed out
HKP="--keyserver hkp://pool.sks-keyservers.net" # Global pool
HKP="--keyserver hkp://eu.pool.sks-keyservers.net" # European pool
HKP="--keyserver hkp://na.pool.sks-keyservers.net" # North american pool
HKP="--keyserver hkp://keys.gnupg.net" # Gnupg
##---------------------------------------------------
# MX17 signing keys:
# gpg: key 9B68A1E8B9B6375C: "Dolphin Oracle (mx linux) <dolphinoracle@gmail.com>"
# gpg: key 70938C780679EE98: "Adrian <adrian@mxlinux.org>"
# gpg: key 13C74A22892C32F1: "Steven Pusser <stevep@mxlinux.org>"
KEYS="9B68A1E8B9B6375C 70938C780679EE98 13C74A22892C32F1"
# we only use these trusted keys for signature verifications
RING="--no-default-keyring --keyring $HOME/.gnupg/trustedkeys.kbx"
# receive or update signaure keys
doit gpg -v $RING $HKP --recv-keys $KEYS
##---------------------------------------------------
#
ZSYNC=${TARGET}.zsync
MD5=$TARGET.md5
SIG=$TARGET.sig
# get closes sourceforge server for zsync
DOWNLD=https://sourceforge.net/projects/mx-linux/files/Snapshots/${ZSYNC}/download
SPIDER=$(wget -nv --spider ${DOWNLD} 2>&1 | grep -Eo https.*iso.zsync | sed 's/https/http/')
# let's do zsync
[ -f ${TARGET} ] || doit zsync -i $SOURCE ${SPIDER}
# get checksum and signature
URL="${SPIDER%/*}"
[ -f $MD5 ] || doit curl -RLJO $URL/$MD5
[ -f $SIG ] || doit curl -RLJO $URL/$SIG
# check sum
[ -f $MD5 ] && doit md5sum -c $MD5
# verfy signature with gpgv
[ -f $SIG ] && doit gpgv -v $SIG $TARGET
#-----#
exit #
#-----#
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
Re: Monthly snapshot announcement
Great little script, I wonder if we generalize it a bit and make it accept some arguments... maybe "-32" option to get the 32bit ISO or an option to give it the name of the file (but assume the same SourceForge path)
Re: Monthly snapshot announcement
Thanks, for the idea.
For now, so the user can place it into the same folder
as the ISO's in case he has two folders for both arch's
just symlink or copy the script either
to ZSYNC-MX-17.1_June_386.iso.sh
or ZSYNC-MX-17.1_June_x64.iso.sh
If the filename contains "386" it will fetch MX-17.1_June_386.iso
other wise MX-17.1_June_x64.iso if local latest ISO for zsync was found.
Code: Select all
#!/bin/bash
#---------------------------------------------------
# get Monthly MX Linux ISO with zsync
#---------------------------------------------------
# filename ZSYNC_MX-17.1_June_x64.sh
# will fetch MX-17.1_June_x64.iso
# (default)
#
# copy/symlink to ZSYNC_MX-17.1_June386.sh
# will fetch MX-17.1_June_386.iso
# from nearest sourceforge server
#
# fehlix 15-06-2018
ARCH='x64'
# set ARCH to '386' if in script name
F=${0##*/} # get name of script
[ -z "${F##*386*}" ] && ARCH='386'
# add available local ISO-sources here - newest first
# check latest ISO-sources are available
SOURCE=""
for I in $(echo "
MX-17.1_May.2_${ARCH}.iso
MX-17.1_May.1_${ARCH}.iso
MX-17.1_May_${ARCH}.iso
MX-17.1_April_${ARCH}.iso
MX-17.1_March_${ARCH}.iso
MX-17.1_${ARCH}.iso
MX-17_${ARCH}.iso")
do
[ -f $I ] && SOURCE="$I" && break
done
[ -z $SOURCE ] && echo "No latest ISO for ZSYNC available! exit" && exit 1
echo "ISO found for ZSYNC: $SOURCE"
# new ISO-target we want get with zsync
#
TARGET=MX-17.1_June_${ARCH}.iso
#----------------------------------------------------
# some fun @ fehlix
#----------------------------------------------------
function echodo () { echo "#>> : ${@}"; "${@}"; }
function doit () {
local R;
echo "#>> BEGIN: ${@}";
"${@}"; R=$?;
echo "#>> END : ${@}"; return $R;
}
##---------------------------------------------------
# do we have zsync
command -v zsync >&- || {
# opps we need to and install zsync
sudo apt-get update
sudo apt-get install zsync
}
##---------------------------------------------------
# prepare keys for signaure verificytion
# keyserver use either of those below - change if timed out
HKP="--keyserver hkp://pool.sks-keyservers.net" # Global pool
HKP="--keyserver hkp://eu.pool.sks-keyservers.net" # European pool
HKP="--keyserver hkp://na.pool.sks-keyservers.net" # North american pool
HKP="--keyserver hkp://keys.gnupg.net" # Gnupg
##---------------------------------------------------
# MX17 signing keys:
# gpg: key 9B68A1E8B9B6375C: "Dolphin Oracle (mx linux) <dolphinoracle@gmail.com>"
# gpg: key 70938C780679EE98: "Adrian <adrian@mxlinux.org>"
# gpg: key 13C74A22892C32F1: "Steven Pusser <stevep@mxlinux.org>"
KEYS="9B68A1E8B9B6375C 70938C780679EE98 13C74A22892C32F1"
# we only use these trusted keys for signature verifications
RING="--no-default-keyring --keyring $HOME/.gnupg/trustedkeys.kbx"
# receive or update signaure keys
doit gpg -v $RING $HKP --recv-keys $KEYS
##---------------------------------------------------
#
ZSYNC=${TARGET}.zsync
MD5=$TARGET.md5
SIG=$TARGET.sig
# get closes sourceforge server for zsync
DOWNLD=https://sourceforge.net/projects/mx-linux/files/Snapshots/${ZSYNC}/download
SPIDER=$(wget -nv --spider ${DOWNLD} 2>&1 | grep -Eo https.*iso.zsync | sed 's/https/http/')
# let's do zsync
[ -f ${TARGET} ] || doit zsync -i $SOURCE ${SPIDER}
# get checksum and signature
URL="${SPIDER%/*}"
[ -f $MD5 ] || doit curl -RLJO $URL/$MD5
[ -f $SIG ] || doit curl -RLJO $URL/$SIG
# check sum
[ -f $MD5 ] && doit md5sum -c $MD5
# verfy signature with gpgv
[ -f $SIG ] && doit gpgv -v $SIG $TARGET
#-----#
exit #
#-----#
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
Re: Monthly snapshot announcement
... Very good, and good to the planet too (less energy and time to spend)
I simply replaced into the script "ARCH='x64'" by "ARCH='386'" and few time after I have the "MX-17.1_June_386.iso" iso file available, from the "MX-17.1_May2_386.iso" ( just download the only remaining ~13% as I had already the may-snapshot: ) .
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32
Re: Monthly snapshot announcement
Totally agree with @Adrian here @fehlix; great little script. Likewise only had to get 13%. Works like a charm.
Can do a lot more new installs for people with this. So many of these "younguns" to Linux just don't get the power of the OS; its CLI and subsequent scripting?! :)
cheers,
greywolf.
Can do a lot more new installs for people with this. So many of these "younguns" to Linux just don't get the power of the OS; its CLI and subsequent scripting?! :)
cheers,
greywolf.
It is about the Dragons - it was always about the Dragons!