[SOLVED] MLED - Microlinux Enterprise Desktop - a full-blown production desktop (KDE or Xfce)
SlackwareThis Forum is for the discussion of Slackware Linux.
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 must say I was extremely pleased with the SolydK Business edition. What strikes me - and this is why I'm mentioning this here - is that this is more or less the KDE edition of MLED, only with Debian stable as a base...
I've been with Solyd since around September '13. I've always thought the sober configuration you mentioned is its best feature, and that the Business Edition is indeed hard to beat. However when Jessie becomes the new Debian Stable I'll probably head over your way, on the run from systemd. I've been testing Slackware pretty heavily as an alternative and I really like it a lot. As a huge fan of Solyd's BE, your MLED spin naturally caught my eye. Wanted to say thanks for the really great job you're doing here.
I've been with Solyd since around September '13. I've always thought the sober configuration you mentioned is its best feature, and that the Business Edition is indeed hard to beat. However when Jessie becomes the new Debian Stable I'll probably head over your way, on the run from systemd. I've been testing Slackware pretty heavily as an alternative and I really like it a lot. As a huge fan of Solyd's BE, your MLED spin naturally caught my eye. Wanted to say thanks for the really great job you're doing here.
Thank you very much for your kind words of encouragement.
Not sure if this is where I ought to be asking this question, but here goes...
I've got a fresh install of MLED. Thing are going well so far. I just installed skype via the slackbuild, but when I try to run it, I get a problem with liblzma.so.5. Running ldd /usr/bin/skype shows everything is found except for this library.
Is it normal, that I should be missing this with an MLED install? (or maybe with Slackware in general?)
when I try to run it, I get a problem with liblzma.so.5. Running ldd /usr/bin/skype shows everything is found except for this library
Since liblzma.so is located in both aaa_elflibs and xz packages, I assume you're running 64bit version. Did you install multilib? Skype requires it. liblzma.so.5 is in aaa_elflibs multilib package. I believe MLED has multilib repo enabled in slackpkgplus.conf, so after updating your repos you just need to run
Not sure if this is where I ought to be asking this question, but here goes...
I've got a fresh install of MLED. Thing are going well so far. I just installed skype via the slackbuild, but when I try to run it, I get a problem with liblzma.so.5. Running ldd /usr/bin/skype shows everything is found except for this library.
Is it normal, that I should be missing this with an MLED install? (or maybe with Slackware in general?)
MLED doesn't provide Skype (yet). I'm still busy working on quality assurance of the existing packages & documentation. But it's on my TODO list. One dragon at a time. And yes, you need a full Multilib set for Skype to work.
Thanks for all your work on this kiki. I certainly understand the necessity of, "One dragon at a time."
I am indeed on a 64 bit system. Sorry for my ignorance, but during the installation, I ran slackpkg install compat32 as per the MLED Installation Guide. As far as I can tell, this is pretty much the same as slackpkg install multilib. (Please correct me if I'm wrong).
So, given that, does it still make sense that I'm missing the 32bit version of liblzma ? (running locate liblzma does show me the 64bit libraries)
Either way, if skype is on your TODO list, I won't worry about this too much. I know you'll get to it sooner or later. Personally, skype is something I rarely need to use anyhow. (Although it's certainly annoying that a closed, proprietary system has become the de facto standard for video communication, but that's a whole other topic... )
I am indeed on a 64 bit system. Sorry for my ignorance, but during the installation, I ran slackpkg install compat32 as per the MLED Installation Guide. As far as I can tell, this is pretty much the same as slackpkg install multilib. (Please correct me if I'm wrong).
I investigated your problem a little bit, and I made an interesting discovery. The two commands slackpkg install compat32 and slackpkg install multilib are not exactly the same. I expected their result to be the same, but it seems I was wrong. While the first provides a wildcard on package tags as an argument, the latter takes the repository name as an argument. And there's indeed a difference between the two, because running the latter installs two missing packages, aaa_elflibs_compat32 and glibc-debug from the multilib repo.
I'm currently busy rewriting the MLED installation guide. Instead of a one-size-fits-all, I intend to publish separate installation guides for all the different flavours and architectures. I will include this new information.
I found that happen to me also. compat32 alsa was broke till I just pulled the multi-lib and reinstalled it. The group and user for virtualbox you may want to add them part of your install script.
I investigated your problem a little bit, and I made an interesting discovery. The two commands slackpkg install compat32 and slackpkg install multilib are not exactly the same. I expected their result to be the same, but it seems I was wrong. While the first provides a wildcard on package tags as an argument, the latter takes the repository name as an argument. And there's indeed a difference between the two, because running the latter installs two missing packages, aaa_elflibs_compat32 and glibc-debug from the multilib repo.
to prevent installation of glibc-debug, add it to /etc/slackpkg/blacklist, or you can apply this patch to slackpkg+ (also in attachment) :
Code:
--- slackpkgplus.sh.org 2014-10-26 11:20:12.448186282 +0100
+++ slackpkgplus.sh.new 2014-10-26 11:20:44.568188316 +0100
@@ -918,9 +918,13 @@
echo "$pref" | grep -qi "multilib" && MLREPO_SELELECTED=true
- if $MLREPO_SELELECTED && [ "$CMD" == "remove" ] ; then
- internal_blacklist "glibc"
- internal_blacklist "gcc"
+ if $MLREPO_SELELECTED ; then
+ if [ "$CMD" == "install" ] ; then
+ internal_blacklist "glibc-debug"
+ elif [ "$CMD" == "remove" ] ; then
+ internal_blacklist "glibc"
+ internal_blacklist "gcc"
+ fi
fi
package="SLACKPKGPLUS_${pref}"
I found that happen to me also. compat32 alsa was broke till I just pulled the multi-lib and reinstalled it. The group and user for virtualbox you may want to add them part of your install script.
I thought about that, and decided against it. There's only a 'virtualbox' group to add to the machine, and then you have to add yourself to that group. There's no special virtualbox user.
I just wrote a series of four distinct HOWTOs for MLED. I think the text-only format is better than the HTML version on the website, since it's easier reading it in console mode during the installation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.