Microlinux / MLEDThis forum is for the discussion of MLED (Microlinux Enterprise Desktop).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think if he add the transparency option, it wouldn't hurt to have both. Giving users options is what I'm all about. After creating your new user and configuring everything,
Example: Would you like (F)ull or (P)artial Transparency? If you don't choose one after 3 seconds then nothing is change and everyone is happy. It would be ideal for the script to do it because it create the user for it.
Last edited by PROBLEMCHYLD; 10-03-2016 at 11:21 PM.
Do you think it's possible to create an offline mledauto script? I plan to put everything on a DVD and let it take course.
Thanks, I have a couple machines ready with clean installs for testing if you decide to do it.
At the same time I developped the meldauto script, I looked into how to create a script for offline installation.
I took notes that you'll find at the end of this post (my notes are taken in the form of a post as I intended to publish them when I was done).
As it stands today, a script for an offline installation needs to:
- make assumption of the structure of the offline media (DVD/USK Key): Slackware packages, MLED ones + extras ones, multilib, MLED GIT repository - Refer to Assumptions c) in my notes
- the trim.sh script uses slackpkg to add missing Slackware packages. If the initial Slackware installation was full, it should not be a problem otherwise one needs to ensure that Slackware packages are available offline (the installation media would be the best place).
Basically, if the DVD has the Slackware packages, MLED packages (including the extra ones), multilib packages (if one doesn't want to restrict it to 32-bit installation) and the MLED git repository, an offline script should not be too difficult to create starting from the existing mledauto script.
What do you have in your DVD?
My draft notes for an offline installation:
Quote:
checklist for a MLED offline installation.
I built a checklist for an offline installation of MLED. It's not an installation guide but I believe a checklist is a good starting point to identify points of attention and desgin decisions to be taken (ex: how to install Slackware extra packages).
I focused on the installation steps and not the creation of the MLED installation medium (CD/DVD or USB key) because I think that how we do the installation would determine what we want to have in the MLED CD/DVD/USB.
Here's how I would see an offline installation of MLED. In the checklist below, the command lines start with "$", my comments start with "#".
1) Assumptions:
a) User has a Slackware installation medium (DVD or USB) that includes the extra packages
b) Slackware has been installed on the machine (Full installation except maybe E, KDE, KDEI categories).
User is logged as root in the console.
c) User has a MLED installation medium (CD/DVD or USB) with following directory layout:
desktop-{14.1|14.2}-{32|64}bit:
list of MLED packages and tools copied from http://www.microlinux.fr/microlinux/desktop-{14.1|14.2}-{32|64}bit/slackware{64}/
extras-{14.1|14.2}-{32|64}bit:
list of MLED extra packages copied from http://www.microlinux.fr/microlinux/extras-{14.1|14.2}-{32|64}bit/slackware{64}/
# TO-DO: describe how to create the MLED installation medium
# TO-DO: check any licensing/distribution issue with getting multilib from AlienBob repository
2) MLED offline installation procedure:
2.1) Install Slackware extra packages: mplayerplug-in and recordmydesktop
If Slackware CD/DVD
$mount /dev/cdrom /mnt/tmp
Else Slackware USB
$mount /dev/sdb1 /mnt/tmp
# /mnt/tmp seems to be the most appropriate mount point as the name is independant from the installation medium type
# TO-DO: add a step to check on which device is detected the USB key
# TO-DO: an alternative solution would be to include mplayerplug and recordmydesktop packages into the MLED installation medium. In this case, installation of extra packages would take place after trimming the base installation (step 2.3 here).
2.2) Mount MLED installation medium
If MLED CD/DVD
$mount /dev/cdrom /mnt/tmp
Else MLED USB
$mount /dev/sdb1 /mnt/tmp
2.3) Trim the Slackware base installation
$cd /mnt/tmp/desktop-{14.1|14.2}-{32|64}bit/tools/
$./trim.sh
# WARNING: there is a problem if trim.sh needs to add packages as it uses slackpkg install
2.4) Installation of multilib packages (only for 64bit edition)
$cd /mnt/tmp/multilib/{14.1|14.2}/
$upgradepkg --reinstall --install-new *.t?z
2.5) Installation of MLED packages
$cd /mnt/tmp/desktop-{14.1|14.2}-{32|64}bit/slackware{64}/
$for dir in ap d f l locale multimedia n profile x xap xfce ; do \
( cd $dir ; upgradepkg --reinstall --install-new *.t?z ) \
done
2.6) Installation of MLED extra packages
$cd /mnt/tmp/extras-{14.1|14.2}-{32|64}bit/slackware{64}/
$for dir in ap d x xap y ; do \
( cd $dir ; upgradepkg --reinstall --install-new *.t?z ) \
done
# TO-DO: explain that user should substitute <extra package> in the command with the name of the package to be installed
2.7) Clean menus (should be done here and not in configuration section as we want to remove installation medium before proceeding to the configuration section
$cd /mnt/tmp/desktop-{14.1|14.2}-{32|64}bit/tools/
$./cleanmenu.sh
2.8) Umount MLED installation medium
$ umount /mnt/tmp
# Remove MLED installation medium
2.9) Configure slackpkg+
# TO-DO Even if we did an offline installation, I believe the guide should include the steps to configure slackpkg+: select mirror, and optionally slackpkg update gpg && slackpkg update
A final word: it looks like most of the installation steps could easily be automated using a simple script (at least to cover steps 2.3 to 2.7). This would greatly reduce the size of the offline installation guide.
I don't have anything on my DVD atm. I was waiting to download all of MLED and your script then burn it to a DVD. Then run the script from the within the DVD.
This is a list of updated packages after a clean install using mledauto script.
These should be on the media as well. These are installed before the trim.sh
From my current knowledge/investigation, the main difficulty in writing a script for offline installation lies with the trim.sh script that uses slackpkg to add or remove packages. There might be no need to add packages if one has already done a full installation of Slackware but one would still need to have some packages removed.
So the ideal DVD structure should be based on a Slackware DVD including the CHECKSUM, FILELIST, etc.. files needed by slackpkg (but without the source directory to save space) to which the following directories should be added:
# Slackware packages updated since the release of the Slackware DVD
slackware{64}-{14.1|14.2}/patches/packages/
Herewith the first draft version of script mledoffline.sh that automates an offline installation of MLED.
I based the script on the assumption that the user would have an installation medium (DVD or USK Key) containing local copies of the Slackware and MLED package repositories (and multilib one for 64-bit edition).
The expected structure of the installation medium is:
For Slackware 32-bit edition:
slackware-14.{1|2}/ and its sub-directories
microlinux/desktop-14.{1|2}-32bit/ and its sub-directories
microlinux/extras-14.{1|2}-32bit/ and its sub-directories
For Slackware 64-bit edition:
slackware64-14.{1|2}/ and its sub-directories
microlinux/desktop-14.{1|2}-64bit/ and its sub-directories
microlinux/extras-14.{1|2}-64bit/ and its sub-directories
multilib/14.{1|2}/ and its sub-directories
For the Slackware repository, the following sub-directories are not needed (to help save space on DVD):
isolinux/
kernels/
slackware{64}/kde/
slackware{64}/kdei/
source/
testing/
usb-and-pxe-installers/
How to build the installation medium is not the object of this post. I can suggest that you use lftp to retrieve the repositories from their online locations. Syntax should be:
Of course, there are lftp options to exclude files/directories from the mirror command. Finding the adequate syntax is left as an exercise to the reader
I made only basic unitary tests of the script.
Feedback would be appreciated.
[EDIT]
One last thing: the mledoffline.sh script can be copied into the installation medium but it's not mandatory. You can just put it somewhere in the Slackware machine on which you want to install MLED.
[/EDIT]
Last edited by gegechris99; 12-11-2016 at 03:38 PM.
Reason: location of mledoffline.sh script
I'm about to test away.............. Thanks
When you said next weekend, I thought you meant the following, which is next week.
Anyway, I got some down time, so I'm about to test. Be back in a couple hours.
WARNING! One or more errors occurred while slackpkg was running
------------------------------------------------------------------------------
Repository 'microlinux-desktop' not configured.
Add:
MIRRORPLUS['microlinux-desktop']=http://repoaddres/...
See documentation in /usr/doc/slackpkg+-* for details
It seems that, when prompted to enter the mount point of your installation medium, you entered it with the trailing /
So when the script update the location of the local mirror for MLED, the path has double /
This should be avoided with the current version of the script. I put a warning about this in the lines before the prompt.
Please try entering the mount point without the trailing / (i.e. /run/media/root/1320-3B16). My unitary tests on this section of the script were successful.
If that's the origin of the error, I'll make a correction later (either remove the trailing / if inadvertently entered by the user or request the trailing / and adapt the script accordingly).
Also, I don't know if you made an error during upload of the slackpkgplus.conf files but the slackpkgplus.conf.offbkp file should have been the original one and it's not. It may be an error in the script but we'll find out because after offline installation of MLED, the slackpkgplus.conf.offbkp file is moved back to slackpkgplus.conf.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.