[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.
$DESKTOP, $VERSION and $ARCH are variables. You're not supposed to type them in as such. $DESKTOP can be "kde" or "xfce", $VERSION can be "14.0", "14.1" or something similar, and $ARCH is either "32bit" or "64bit".
Note that MLED targets users with a bit of Slackware experience for the installation procedure. If you're totally new to Linux, you might want to study the official Slackware documentation first.
Thank you again and sorry for the silly questions. I perfectely understand your concern and warning about studying the slackware documentation. In fact, I use Linux since 1999 and I am totally in favour of its use by everyone (either at home or at work). Unfortunately I do not work with it and what (not much) I know about it I have learnt by myself and, of course, with the help of expertises like this fórum. I use Slack since the 8.1 version but sometimes I still have some doubts (some of them really silly for those who have a high level knowledgement. I also have Arch Linux installed in another partition. For me, these are the best distros ever.
As I told you, I had no problem at all with the installation. I thank you for you attention and I have apologize for this question (really silly) . As soon as I finish and enter the graphic mode I will let you know. I congratulate you on your great job and I am glad to have gotten in touch with MLED. Have a nice week.
Thank you again and sorry for the silly questions. I perfectely understand your concern and warning about studying the slackware documentation. In fact, I use Linux since 1999 and I am totally in favour of its use by everyone (either at home or at work). Unfortunately I do not work with it and what (not much) I know about it I have learnt by myself and, of course, with the help of expertises like this fórum. I use Slack since the 8.1 version but sometimes I still have some doubts (some of them really silly for those who have a high level knowledgement. I also have Arch Linux installed in another partition. For me, these are the best distros ever.
As I told you, I had no problem at all with the installation. I thank you for you attention and I have apologize for this question (really silly) . As soon as I finish and enter the graphic mode I will let you know. I congratulate you on your great job and I am glad to have gotten in touch with MLED. Have a nice week.
No problem, buddy. Feel free to ask any question you want, really. There's no such thing as a silly question.
I forgot to bring this up. 32bit alsa was a problem so I actually cloned alienbobs compat32 and did a uprade --reinstall of the compat32-* and it fixed the issue so that is some where to look ?
I use vivox and it is a 32bit voice program.
I forgot to bring this up. 32bit alsa was a problem so I actually cloned alienbobs compat32 and did a uprade --reinstall of the compat32-* and it fixed the issue so that is some where to look ?
I use vivox and it is a 32bit voice program.
Is this related to MLED specifically? I think you're posting in the wrong thread.
Is this related to MLED specifically? I think you're posting in the wrong thread.
yes I am looking for a version of slackware with that gcc. and those builds. I know it was part of current for a while.
then they settled on 4.7.1 for 14.0. I was going to use it for some work of mine.
If it is not around I will upgrade a 13.37 because it is the builds that went with it that is a big part of what I need it for.
I couldn't find any info about how to "upgrade" an *old* install of MLED-XFCE (prior to the introduction of the MATE variant). Back then I disabled the MLED repos in slackpkg+ and continued to install the official Slackware patches. Now, given that the XFCE variant is live again, how could I start tracking the XFCE-branch again?
I couldn't find any info about how to "upgrade" an *old* install of MLED-XFCE (prior to the introduction of the MATE variant). Back then I disabled the MLED repos in slackpkg+ and continued to install the official Slackware patches. Now, given that the XFCE variant is live again, how could I start tracking the XFCE-branch again?
Hmmm, let me think.
1. Disable any third-party repo.
2. Call slackpkg clean-system.
3. Import the Microlinux scripts from Github.
4. Download and install slackpkg+ from desktop-base-*/ap/
5. Run the trim_desktop_xfce.sh script.
6. slackpkg install desktop-base
7. slackpkg install desktop-xfce
My suggestion: print out the new installation guide as well as my post, and with these two you should succeed.
Cheers,
Niki
Edit: I think I'll add some little documentation about how to turn any existing Slackware installation into an MLED desktop. And maybe also how to switch desktops, e. g. turn MLED KDE into MLED Xfce and the other way around. I'll try to do this next weekend.
Would there be a problem if I do everything on a remote system? I've no physical access to a machine that I would like to properly re-MLED, so would the procedure be safe?
After some experimenting, I've decided to add Digikam to the KDE-based standard edition of MLED.
1. Missing libraries have been added to the desktop-base repo, so here's how you fetch them easily:
Code:
# slackpkg update
# slackpkg install desktop-base
2. Digikam relies on the 'marble' package, so you have to install this additional dependency, which hasn't been part of the base choice of packages until now:
Code:
# slackpkg install marble
3. Now install Digikam:
Code:
# slackpkg install desktop-kde
Digikam is a nice photo management application, but it has the nasty tendency to clutter the KDE menus in Applications > Graphics. You can run the desktop-kde-14.1-$ARCH/tools/cleanmenu.sh utility to unclutter it. I've updated the collection of *.desktop files accordingly.
Likewise, I've updated the collection of tagfiles and package lists for the trim scripts to include marble from now on. On a side note, I've done some editing with the tagfiles, they were a bit messed up.
Some external modules seem to be missing for the panorama module. I'll see what I can do about that.
Last but not least, there were updates to Firefox and Thunderbird this morning, so I've updated the localization packages accordingly.
Would there be a problem if I do everything on a remote system? I've no physical access to a machine that I would like to properly re-MLED, so would the procedure be safe?
Of course, as long as you don't shoot yourself in the foot.
Yeah, sure. I forgot: since your user is already created, the default MLED profile won't apply. Make sure to copy over all the stuff from /etc/skel into your home directory.
... since your user is already created, the default MLED profile won't apply. Make sure to copy over all the stuff from /etc/skel into your home directory.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.