Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Monthly snapshot announcement

Post Reply
Message
Author
Alt
Forum Novice
Forum  Novice
Posts: 78
Joined: Wed Jan 27, 2016 1:28 am

Re: Monthly snapshot announcement

#61 Post by Alt » Sun Jun 17, 2018 2:28 pm

Alt wrote:
Sun Jun 03, 2018 7:18 am
I wonder what is wrong with UEFI on Monthly Snapshots. I just unable to boot it (no error, just returns to BIOS boot selector. Tried it on HP 450 G3 & MacBook Pro 2014.
Original release works with both, Snapshot only works with HP on legacy mode.
Current solution here (2nd post in < [Tutorial] Make your Linux USB write-able >)

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2009
Joined: Wed Apr 11, 2018 5:09 pm

Re: Monthly snapshot announcement

#62 Post by fehlix » Mon Jun 18, 2018 6:33 am

Alt wrote:
Sun Jun 17, 2018 2:28 pm
...
I wonder what is wrong with UEFI on Monthly Snapshots.
I just unable to boot it (no error, just returns to BIOS boot selector.
...
You might consider to completely disable BIOS-mode including disable
Compatibility Support Module CSM within UEFI-firmware.
Otherwise, you never know when and why your UEFI firmware
decides to fallback to BIOS boot selector.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Timmbits
Forum Novice
Forum  Novice
Posts: 3
Joined: Wed Jun 20, 2018 4:52 pm

Re: Monthly snapshot announcement

#63 Post by Timmbits » Wed Jun 20, 2018 5:14 pm

Hi I just landed here and please forgive me if this was covered somewhere else. And sorry in advance if these seem like stupid questions.
FYI, I'm considering coming over to MX, from Mint. I'm by far not an expert user.

Concerning Meltdown and Spectre, since these are exploits for 64bit processors,
would the 32bit version of the MX operating system running on said processors be less vulnerable to these exploits?
If not, is there anything that makes it more difficult to harden the 32bit version of the OS against these?

I certainly don't need the extra memory and storage addressing capabilities of 64bit on my personal system.
All I care about is efficiency (efficient use of system resources and speed), programs compatibility, stability, less fuss and less bloat where possible, and I'm leaning towards the 32bit version.

(both my laptops are AMDx64, so I think it's only Spectre they're vulnerable to. and my eee PC 1000he has a processor that does not have the vulnerability)

User avatar
asqwerth
Forum Veteran
Forum Veteran
Posts: 3441
Joined: Sun May 27, 2007 5:37 am

Re: Monthly snapshot announcement

#64 Post by asqwerth » Thu Jun 21, 2018 12:23 am

Look at this link:

https://mxlinux.org/meltdown-spectre-news

which is at the top of the forum page under "Important Information".

You can also install the meltdown spectre checker from the repos. Just open Synaptic and type "meltdown" in the search box.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
Adrian
Forum Veteran
Forum Veteran
Posts: 8985
Joined: Wed Jul 12, 2006 1:42 am

Re: Monthly snapshot announcement

#65 Post by Adrian » Mon Jul 16, 2018 12:42 pm

MX-17.1 July snapshot available http://bit.ly/mx-monthly
Includes Debian 9.5 updates, new versions of Firefox and Thunderbird. MX Installer got some refinements, MX Packageinstaller has been updated to support translations (some available now, the rest are upcoming)

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 22646
Joined: Wed Jul 19, 2006 6:13 am

Re: Monthly snapshot announcement

#66 Post by Jerry3904 » Mon Jul 16, 2018 12:57 pm

Very nice!
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, Kingston SSD 120 GB and WesternDigital 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB

User avatar
chrispop99
Forum Guide
Forum Guide
Posts: 2426
Joined: Tue Jan 27, 2009 3:07 pm

Re: Monthly snapshot announcement

#67 Post by chrispop99 » Mon Jul 16, 2018 1:20 pm

Thanks Adrian.

Chris
Test machines:
32-bit non-PAE - Thinkpad T41, 1.6GHz Pentium M, 1GB RAM.
32-bit PAE - DELL Latitude D610, 1.73GHz Pentium M, 2GB RAM.
64-bit - Lenovo T61, 2GHz Core 2 Duo, 2GB RAM
64-bit - Gigabyte Z77P-D3, Intel i3-3220, GeForce 8400 GS, 4GB PC3-12800.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2009
Joined: Wed Apr 11, 2018 5:09 pm

Re: Monthly snapshot announcement

#68 Post by fehlix » Mon Jul 16, 2018 1:37 pm

Adrian wrote:
Mon Jul 16, 2018 12:42 pm
MX-17.1 July snapshot available http://bit.ly/mx-monthly
Get Your MX17.1 Linux July Snapshot with ZSYNC NOW

Attchached find the scripts ZSYNC_MX-17.1_July_x64.sh / ZSYNC_MX-17.1_July_386.sh
which will download latest July 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, MX-17.1 , MX-17.1_April or MX-17.1_June.

Make the script executable.
If the automatic select mirror is to slow, just interrupt with CTRL+C und rerun again.
Already downloaded data will recognised.

I've just download just remaing diff to MX-17-1_June
of 15.6% for x64 and 12.5% for x386 ISO's.

Save below as: ZSYNC_MX-17.1_July_x64.sh or ZSYNC_MX-17.1_July_386.sh

Code: Select all

#!/bin/bash

#---------------------------------------------------   
# get Monthly MX Linux ISO with zsync
#---------------------------------------------------   
# filename        ZSYNC_MX-17.1_July_x64.sh
#      will fetch MX-17.1_July_x64.iso 
#      (default)
#  
# copy/symlink to ZSYNC_MX-17.1_July_386.sh
#      will  fetch MX-17.1_July_386.iso
# from nearest sourceforge server 
#
# fehlix 16-07-2018

ARCH='x64'
# set ARCH to '386' if in script name
F=${0##*/}           # get name of script
[ -z "${F##*386*}" ] && ARCH='386'
  
# new ISO-target we want get with zsync
#
TARGET=MX-17.1_July_${ARCH}.iso

# add available local ISO-sources here - newest first
# check latest ISO-sources are available
SOURCE=""
for I in $(echo "
	MX-17.1_June_${ARCH}.iso
	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"


#----------------------------------------------------
# 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://eu.pool.sks-keyservers.net" # European pool
HKP="--keyserver hkp://pool.sks-keyservers.net"    # Global 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  #
#-----#  

If the gpg-keys server time-out for receiving/update the signature keys
choose another one from within the script,
default is
HKP="--keyserver hkp://keys.gnupg.net"
which sometimes is too busy.
:snail:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Richard
Posts: 2138
Joined: Fri Dec 12, 2008 10:31 am

Re: Monthly snapshot announcement

#69 Post by Richard » Tue Jul 17, 2018 9:20 am

Thanks, Fehlix.
This is a neat idea, and trick to parse the filename. :)
And thanks to whoever builds the Zsync files! Adrian?
A real time & bandwidth saver.

For some reason, I had a root Thunar open and used that to create the *.sh files.
That didn't work for me, until I erased those and created again as user,
then made sure they were on an executable partition.

Could have been either one of the two, but just a reminder to create and execute as user.
MX171: Lenovo T430: Intel Ivy Bridge i5-3320M, 8GB RAM, 4.18.0-2-amd64, 119GB SSD
MX171: AA1/EeePC: DualCore N270, 1GB RAM, 4.9.126-antix.1-686-smp-pae, 150GB HDD
Thunar/Doublecmd, LibO613, Dropbox, Firefox, CherryTree, Vbox. LinuxCounter #208633

User avatar
Adrian
Forum Veteran
Forum Veteran
Posts: 8985
Joined: Wed Jul 12, 2006 1:42 am

Re: Monthly snapshot announcement

#70 Post by Adrian » Tue Jul 17, 2018 10:46 am

I built the zsync, it's really easy, you just run "zsyncmake -e filename" and it takes seconds... you just need the server to support fragment downloading (I think mxrepo.com doesn't)

I would really like to take Fehlix script and modify it a bit make it more general and put in the download folder of Snapshots on Sourceforge.

My desired features:
- remove "doit" because it's not something that everybody has, it's not installed by default on MX I think. What does it actually do, I'm not familiar with it?
- use a generic name for the script "downloadMXsnapshot.sh" and pull the name of the last snapshot from Sourceforge
- maybe use a switch/option for 32bit instead of relying on the file name, so by default it would download 64bit and then if you run "donwloadMXsnapshot.sh -32" it would get the 32bit...
- get the signature keys only if they are not already installed
- generalize a bit the input file try to use all the older .isos of the same arch, then try the most recent of a different arch, even if you download 32 bit and use 64 bit ISO as input you still get a considerable saving in terms of bandwidth.

Can a script wizard take a look at this?

Post Reply

Return to “General”