MLED installation script as a proof-of-concept

gegechris99 · 03-07-2016, 02:20 AM

The error has been here from the beginning for trim.sh.

Indeed I must first go into the directory where script is located before running it. As per the MLED installation guide:

Code:

# cd microlinux/desktop-14.1-$ARCH/tools/ 
# ./trim.sh

and

Code:

# cd microlinux/desktop-14.1-$ARCH/tools/ 
# ./cleanmenu.sh

I will fix it tonight.

PROBLEMCHYLD · 03-07-2016, 08:25 AM

Hey, at least we found it and can now fix it. I have a clean install waiting for the updated script. I actually watched the whole installation process and seen those errors. I normally just run the script and then go watch Netflix.

P.S

Do you think you can add the server option like you did with the extras?
Can you make the option screen appear for MLED packages, so one can deselect packages.

Quote:

# Install MLED packages
echo -e $BLUE"\n\nInstall the MLED packages:"$RESET
slackpkg -batch=on -default_answer=y install microlinux-desktop
echo -e $GREEN"\nMLED packages have been installed"$RESET

gegechris99 · 03-07-2016, 01:37 PM

Herewith the updated mledauto.sh script. It hopefully fixes the errors with the trim.sh and cleanmenu.sh scripts. It also shows the user dialog for selecting/deselecting MLED packages.

Detailed diff vs. previous version:

Code:

$ diff mledauto.txt.old mledauto.txt
< CWD=$(pwd)
220c219,220
< $CWD/microlinux/desktop-$VERSION-$ARCH/tools/trim.sh
---
> cd $HOME/microlinux/desktop-$VERSION-$ARCH/tools/
> ./trim.sh
245c245,247
< slackpkg -batch=on -default_answer=y install microlinux-desktop
---
> #slackpkg -batch=on -default_answer=y install microlinux-desktop
> # Show dialog to allow for user selection/deselection of MLED packages
> slackpkg install microlinux-desktop
256c258,259
< $CWD/microlinux/desktop-$VERSION-$ARCH/tools/cleanmenu.sh
---
> cd $HOME/microlinux/desktop-$VERSION-$ARCH/tools/
> ./cleanmenu.sh

The second "cd" command may not be needed but it doesn't hurt to repeat it.

Quote:

Do you think you can add the server option like you did with the extras?

I don't use MLES (server version of MLED), but AFAIK, MLES is not designed to be installed in parallel with MLED. There are for example different versions of the same software (ex: ffmpeg 2.6.4 in MLED 14.1 and ffmpeg 2.1 in MLES 14.1 at time of writing). I guess that a knowledgeable user could manage those cases but it doesn't look trivial to me.
Also, to make MLES packages "visible" to the MLED installation script, we would have to change the /etc/slackpkg/slackpkgplus.conf file to add the "server" repository. So if you're interested in MLES, I would rather create a separate installation script for MLES in which package slackpkg+ comes with the appropriate list of repositories.

Again thanks for taking time to test the MLED installation script.

PROBLEMCHYLD · 03-07-2016, 04:31 PM

The whole script ran with no errors. Thank you very, very much.

kikinovak · 03-10-2016, 08:26 AM

Mixing MLES and MLED packages is a very bad idea.

PROBLEMCHYLD · 03-10-2016, 08:33 AM

Maybe when you have time kikinovak, you can test the script yourself. It is a timesaver.

kikinovak · 03-10-2016, 09:04 AM

First of all, thanks everybody for putting so much effort into this. I'm currently busy rewriting the documentation. As soon as I have some time, I'll test this and report back.

Cheers,

Niki

gegechris99 · 03-11-2016, 03:42 PM

Herewith an update of the installation script.

Main change is that, on 64bit machine, the user is asked whether multilib packages should be installed (default answer=y).
Other changes are mainly cosmetic ones (ex: options in menu for selection of mirror are numbered instead of a, b, c, d) and code clean-up.

I hope I didn't break anything.

PROBLEMCHYLD · 03-12-2016, 12:06 AM

Thanks for the update, I don't have 64bit, but if I come across one I'm good to go.

What kernel version are you using?

gegechris99 · 03-12-2016, 06:23 AM

I'm using the 3.10.17 generic kernel that comes with Slackware64 14.1

You've mentioned that you were having issue with installing the generic kernel.

Here are some guides:

From slackware: README.initrd

From MLED: Switch to the GENERIC kernel

kikinovak · 03-12-2016, 12:40 PM

Quote:

Originally Posted by gegechris99

I'm using the 3.10.17 generic kernel that comes with Slackware64 14.1

You've mentioned that you were having issue with installing the generic kernel.

Here are some guides:

From slackware: README.initrd

From MLED: Switch to the GENERIC kernel

A word on that. Editing /etc/mkinitrd.conf and mkinitrd -F is much easier and less error-prone than going through the hassle of calling all options manually.

Niki

PROBLEMCHYLD · 03-12-2016, 02:22 PM

Quote:

Originally Posted by gegechris99

I'm using the 3.10.17 generic kernel that comes with Slackware64 14.1

You've mentioned that you were having issue with installing the generic kernel.

Here are some guides:

From slackware: README.initrd

From MLED: Switch to the GENERIC kernel

I followed those same instructions and get 99 99 etc...... I skip that section altogether because I don't know how to recover from it. I'm playing with Slackware more and Windows less. I do understand some of the commands in your script. Once I have enough hours under my belt, I'll become as fluent as you guys. gegechris99, I have done about 10+ installs with your script. It does help me until I become more familiar with linux overall.

gegechris99 · 03-12-2016, 04:08 PM

Quote:

Originally Posted by PROBLEMCHYLD

I followed those same instructions and get 99 99 etc......

To check if something isn't correctly set, can you post the results of the following commands?

Code:

cat /etc/fstab

Code:

ls -l /boot

Code:

cat /etc/lilo.conf

gegechris99 · 03-19-2016, 08:55 AM

Just an update of the mledauto.sh script.

Changes vs. previous version are:

- code cleaning for welcome message (don't make it too complex)
- use lftp to retrieve slackpkg+ package instead of wget. Unitary tests are OK here.

Regarding the use of lftp vs. wget, I just find the log trace of lftp nicer looking on the screen than the one from wget. Also code is easier to read in the script (at least for me). Anyway, both lftp and wget do the job.

Code:

$ diff mledauto.sh.txt.old mledauto.sh.txt     
30,42d29
< # Welcome message
< WELCOME=("\nWelcome to the MLED installation script\n"
<   "\nMLED (Microlinux Enterprise Desktop) is a full-blown production desktop"
<   "\nbased on Slackware Linux and the Xfce desktop environment."
<   "\nThis script will automate many of the steps of the MLED installation."
<   "\nThe MLED installation guide is available at:"
<   "\nhttp://www.microlinux.eu/installation_guide.php"
<   "\nor"
<   "\nhttp://www.microlinux.eu/downloads/mled-14.1-documentation-english.pdf")
< # Important note
< NOTE=("\nIMPORTANT NOTE: the script should be executed on a machine"
<   "\nrunning Slackware Linux version 14.1\n")
< 
115,117c102,115
< echo -e ${WELCOME[@]}
< echo -e $BLUE${NOTE[@]}$RESET
<   
---
> echo ""
> echo "Welcome to the MLED installation script"
> echo ""
> echo "MLED (Microlinux Enterprise Desktop) is a full-blown production desktop"
> echo "based on Slackware Linux and the Xfce desktop environment."
> echo "This script will automate many of the steps of the MLED installation."
> echo "The MLED installation guide is available at:"
> echo "http://www.microlinux.eu/installation_guide.php"
> echo "or"
> echo "http://www.microlinux.eu/downloads/mled-14.1-documentation-english.pdf"
> 
> echo -e $BLUE$"\nIMPORTANT NOTE: the script should be executed on a machine" \
>   "\nrunning Slackware Linux version 14.1\n"$RESET
> 
227,229c225,227
< wget -r -l1 -np -nH --cut-dirs=3 -A "slackpkg+*_microlinux.txz" \
<   http://www.microlinux.fr/microlinux/desktop-$VERSION-$ARCH/$SLACKDIR/
< installpkg slackpkg+*_microlinux.txz  
---
> lftp -c 'open -e "mget slackpkg+*.txz" \
>   http://www.microlinux.fr/microlinux/desktop-'$VERSION'-'$ARCH'/'$SLACKDIR
> installpkg slackpkg+*.txz

PROBLEMCHYLD · 03-19-2016, 08:21 PM

I will be testing the script tomorrow and will report back.