[ANN] MLED is back

Bertman123 · 04-19-2015, 07:58 PM

Quote:

Originally Posted by gezley

Is it possible to do a migration of vanilla Slackware with already-downloaded MLED packages Niki? I downloaded the whole lot assuming it would be possible, and also assuming I might want to re-install at some point in the future. While I'm at it, is it possible to do a standard install with already-downloaded packages?

And here's another question for you, not strictly MLED-related but I think your README should add the information anyway: the standard installation method assumes the user has an ethernet connection. Is it possible at this early stage of installation to bring up an encrypted wireless connection instead? It's something I've never tried since I always install from DVD.

I would think that you could use the trim.sh script, install/upgrade the packages that you downloaded, and then cleanup the menu.

bormant · 04-20-2015, 12:32 AM

Quote:

Originally Posted by gezley

Is it possible at this early stage of installation to bring up an encrypted wireless connection instead?

If you know how to configure and connect with wpa_supplicant, you can:
1) unpack kernel drivers to the wifi card from kernel-modules package, run depmod -a;
2) unpack firmware from kernel-firmware package, if the card needs it
3) installpkg /mnt/cdrom/slackware*/n/wpa-supplicant-*t?z
4) load modules
5) create /etc/wpa_supplicant.conf and start wpa_supplicant for wireless interface
6) configure ip/mask and routes manually or use dhcpcd to get them from DHCP server

kikinovak · 04-20-2015, 03:03 AM

Quote:

Originally Posted by gezley

Is it possible to do a migration of vanilla Slackware with already-downloaded MLED packages Niki? I downloaded the whole lot assuming it would be possible, and also assuming I might want to re-install at some point in the future. While I'm at it, is it possible to do a standard install with already-downloaded packages?

Of course. Once you trimmed your system successfully, you can install your downloaded packages:

Code:

# upgradepkg --reinstall --install-new *.txz

Then setup everything as usual, configure slackpkg, double-check slackpkgplus.conf, and you're good.

kikinovak · 04-20-2015, 03:05 AM

On a side note, a little extra information. I've setup a technical blog some time ago, with regular technical articles about Slackware (for now) and CentOS (later).

https://kikinovak.wordpress.com/

solarfields · 04-20-2015, 03:24 AM

Any plans for making it in English?

kikinovak · 04-20-2015, 03:35 AM

Quote:

Originally Posted by solarfields

Any plans for making it in English?

No, I'm sorry. I already have a hard time keeping things up to date in one language. I chose French, because I also work as a Linux trainer in France, so I'm using parts of this documentation - along with my written books - for my courses.

On the other hand, I understand Google Translate does quite a good job. And the *nix commands are universal.

Gerard Lally · 04-20-2015, 11:18 AM

Quote:

Originally Posted by Bertman123

I would think that you could use the trim.sh script, install/upgrade the packages that you downloaded, and then cleanup the menu.

I'm not so hot on shell scripting; I was under the impression the trim.sh script installed the packages at the end:

Code:

if [ ! -z "$PACKAGES" ]; then
  /usr/sbin/slackpkg install $PACKAGES
fi

I'll have to study it more closely. Thanks.

Gerard Lally · 04-20-2015, 11:21 AM

Quote:

Originally Posted by kikinovak

Of course. Once you trimmed your system successfully, you can install your downloaded packages:

Code:

# upgradepkg --reinstall --install-new *.txz

Then setup everything as usual, configure slackpkg, double-check slackpkgplus.conf, and you're good.

Great. Thanks. Another question for you, since I don't understand shell scripts very well. If not the MLED packages themselves, what is it that trim.sh installs at the end of the script:

Code:

if [ ! -z "$PACKAGES" ]; then
  /usr/sbin/slackpkg install $PACKAGES
fi

kikinovak · 04-20-2015, 01:03 PM

Quote:

Originally Posted by gezley

Great. Thanks. Another question for you, since I don't understand shell scripts very well. If not the MLED packages themselves, what is it that trim.sh installs at the end of the script:

From the MLED-HOWTO:

Code:

Trim the base installation
--------------------------

In case you didn't use the set of tagfiles during the initial installation,
now's the time to eventually catch up on it. 

The 'desktop-14.1-32bit/tools/' subdirectory provides a basic 'trim.sh' script
that takes care of two things:

  1. install needed packages

  2. get rid of unneeded packages

The script makes use of 'slackpkg', so make sure it's configured correctly.

Trim your Slackware installation: 

  # cd microlinux/desktop-14.1-32bit/tools/ 
  # ./trim.sh 

Two packages are provided by the official 'extra/' repository. Install them
manually:

  # slackpkg install mplayerplug-in recordmydesktop

From the same documentation:

Code:

About this Installation Guide
-----------------------------

The following instructions assume you already know how to install and
configure Slackware Linux. Read them carefully. The bits you skip will come
back and bite you.

Cheers,

Niki

Gerard Lally · 04-20-2015, 02:36 PM

Quote:

Originally Posted by bormant

If you know how to configure and connect with wpa_supplicant, you can:
1) unpack kernel drivers to the wifi card from kernel-modules package, run depmod -a;
2) unpack firmware from kernel-firmware package, if the card needs it
3) installpkg /mnt/cdrom/slackware*/n/wpa-supplicant-*t?z
4) load modules
5) create /etc/wpa_supplicant.conf and start wpa_supplicant for wireless interface
6) configure ip/mask and routes manually or use dhcpcd to get them from DHCP server

hmmm, thanks Bormant. Steps 1 and 2 look a little complicated. I'll have to try this next time I set up Slackware.

kikinovak · 04-20-2015, 03:54 PM

Quote:

Originally Posted by gezley

hmmm, thanks Bormant. Steps 1 and 2 look a little complicated. I'll have to try this next time I set up Slackware.

I install Slackware on lots (!) of different laptops (for clients). My KISS approach:

1. Connect the network with a cable.

2. Configure the network using DHCP.

3. Install and configure a complete desktop.

4. Clear out rc.inet1.conf and switch to rc.networkmanager.

5. Connect to wireless network using NetworkManager's GUI.

Everything else is way too much trouble for nothing.

bormant · 04-21-2015, 12:49 AM

Quote:

Originally Posted by gezley

Steps 1 and 2 look a little complicated. I'll have to try this next time I set up Slackware.

You can add these files into /isolinux/initrd.img on install media, add the wpa-supplicant, so long to prepare will be short to use. Another option is to prepare separate package with only wifi drivers and firmware and installpkg it in installation environment. (kernel-modules package itself is too big to installpkg it in installation environment initial RAM disk).

Gerard Lally · 04-21-2015, 10:48 AM

Quote:

Originally Posted by kikinovak

I install Slackware on lots (!) of different laptops (for clients). My KISS approach:

1. Connect the network with a cable.

2. Configure the network using DHCP.

3. Install and configure a complete desktop.

4. Clear out rc.inet1.conf and switch to rc.networkmanager.

5. Connect to wireless network using NetworkManager's GUI.

Everything else is way too much trouble for nothing.

I would do it the very same way if my mobile broadband hotspot had an ethernet port.

notKlaatu · 04-21-2015, 10:06 PM

Quote:

Originally Posted by kikinovak

Because MLED is essentially Slackware under the hood, and the user is supposed to do things manually: add a user, configure the network, switch to the generic kernel, configure X11, switch to init 4, etc. It is not MLED's scope to be another drop-in replacement for Ubuntu or one of its numerous spinoffs. On the other hand, once MLED is installed, it's equally easy to use. To administrate it, on the other hand, you have to do your homework.

I don't provide a separate ISO for a few reasons. The main raison being that there are already way too many Linux distributions out there, in my not so humble opinion. MLED is explicitly an add-on to an existing distribution (Slackware), so providing a separate installation support would be an unnecessary redundancy. It's also a manner of paying respect where respect is due.

Cheers,
Niki

A brilliant way of doing things, if I may humbly say so. It's to the detriment of the Linux ecosystem that everyone has a distro that they want people to download when the same results could be achieved with some config files, theme packs, and a wallpaper image. We all praise Linux for its modularity, and then point users to 1GB downloads to discs requiring a full re-install just to experience a nifty new desktop.

Also, great to have you back Niki.

kikinovak · 04-22-2015, 02:57 AM

Quote:

Originally Posted by notKlaatu

A brilliant way of doing things, if I may humbly say so. It's to the detriment of the Linux ecosystem that everyone has a distro that they want people to download when the same results could be achieved with some config files, theme packs, and a wallpaper image. We all praise Linux for its modularity, and then point users to 1GB downloads to discs requiring a full re-install just to experience a nifty new desktop.

Also, great to have you back Niki.

Thanks for your kind words. And I agree, I'm a bit wary of all these distributions which are essentially Ubuntu with a different wallpaper. Although I admit I really like this one.

I just renewed my Slackware subscription, and I encourage MLED users to subscribe to Slackware.