MLED 14.2 has been released!

kikinovak · 08-01-2016, 04:00 AM

Hello everybody,

MLED 14.2 has just been released.

http://www.microlinux.eu/news.php

Get it while it's hot.

Niki

Bertman123 · 08-02-2016, 12:33 PM

Awesome, thanks!

BCarey · 08-05-2016, 10:07 AM

Great news, I've been waiting for this.

I think there is an error in your documentation for 14.2 64 bit.

Code:

Edit 
/etc/slackpkg/mirrors
 and choose a Slackware mirror according to your geographical 
location, for example
:
# /etc/slackpkg/mirrors
...
# GERMANY (DE)
ftp://ftp.fu-berlin.de/unix/linux/slackware/slackware-14.2/
...
On a 64-bit system
:
# /etc/slackpkg/mirrors
...
# GERMANY (DE)
ftp://ftp.fu-berlin.de/unix/linux/slackware/slackware64-14.1/
...

As you can see, the 64 bit version says to point to a 14.1 rather than 14.2 repository.

Thanks again,
Brian

kikinovak · 08-10-2016, 01:38 AM

Quote:

Originally Posted by BCarey

Great news, I've been waiting for this.

I think there is an error in your documentation for 14.2 64 bit.

Code:

Edit 
/etc/slackpkg/mirrors
 and choose a Slackware mirror according to your geographical 
location, for example
:
# /etc/slackpkg/mirrors
...
# GERMANY (DE)
ftp://ftp.fu-berlin.de/unix/linux/slackware/slackware-14.2/
...
On a 64-bit system
:
# /etc/slackpkg/mirrors
...
# GERMANY (DE)
ftp://ftp.fu-berlin.de/unix/linux/slackware/slackware64-14.1/
...

As you can see, the 64 bit version says to point to a 14.1 rather than 14.2 repository.

Thanks again,
Brian

Fixed. Thanks for reporting.

Cheers,

Niki

PROBLEMCHYLD · 08-10-2016, 05:59 PM

I'm not sure what part of your scripts does it, but how do I stop MLED from downgrading my Kernel 4.4.16 to 4.4.14? I have manually upgraded my Kernel and some command downgrades when I'm using MLED. It happens around the mark in the screenshot

gegechris99 · 08-11-2016, 10:57 AM

@PROBLEMCHYLD

I currently have no access to my computer (holidays)

A quick answer to your query: script mledauto.sh will automatically upgrade Slackware packages. Somehow slackpkg+ will replace your own kernel packages (4.4.16) with the official packages (4.4.14). To avoid this behaviour, you can blacklist kernel packages in /etc/slackpkg/blacklist. There should be comments in this file to help you configure it to your needs.

PROBLEMCHYLD · 09-07-2016, 04:13 PM

@ kikinovak

Can you add the necessary lines to your Virtual Machine Manager 1.4.0 package

Code:

Automatic startup

If you want to have the libvirt daemon started automatically, add the following section to /etc/rc.d/rc.local:

# start libvirt
if [ -x /etc/rc.d/rc.libvirt ]; then
    /etc/rc.d/rc.libvirt start
fi 

Make sure /etc/rc.d/rc.libvirt is executable.

kikinovak · 09-09-2016, 04:49 PM

Quote:

Originally Posted by PROBLEMCHYLD

@ kikinovak

Can you add the necessary lines to your Virtual Machine Manager 1.4.0 package

Code:

Automatic startup

If you want to have the libvirt daemon started automatically, add the following section to /etc/rc.d/rc.local:

# start libvirt
if [ -x /etc/rc.d/rc.libvirt ]; then
    /etc/rc.d/rc.libvirt start
fi 

Make sure /etc/rc.d/rc.libvirt is executable.

This file is meant to be edited by hand, with various third-party services added by the user. For example, here's the rc.local on my LAN server:

Code:

# Squid
if [ -x /etc/rc.d/rc.squid ]; then
  /etc/rc.d/rc.squid start
fi

# Start libvirt:
if [ -x /etc/rc.d/rc.libvirt ]; then
  /etc/rc.d/rc.libvirt start
fi

And here's the same file on a public server I manage:

Code:

# Start Icecast server
if [ -x /etc/rc.d/rc.icecast ]; then
  /etc/rc.d/rc.icecast start
fi

# Start MPD server
if [ -x /etc/rc.d/rc.mpd ]; then
  /etc/rc.d/rc.mpd start
fi

# Start Postgrey mail filter 
if [ -x /etc/rc.d/rc.postgrey ]; then
  /etc/rc.d/rc.postgrey start
fi

# Start Postfix mail server 
if [ -x /etc/rc.d/rc.postfix ]; then
  /etc/rc.d/rc.postfix start
fi

# Start Dovecot mail server 
if [ -x /etc/rc.d/rc.dovecot ]; then
  /etc/rc.d/rc.dovecot start
fi

# Chip drivers
/sbin/modprobe coretemp
/usr/bin/sensors -s

You see why it can't be packaged?

PS: your initial message should have figured in a separate thread, IMHO.