MLED - the Microlinux Enterprise Desktop - a complete Xfce-based desktop
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'm not talking about proprietary drivers Bertman; I'm talking about setting up an encrypted wireless or indeed PPPoE connection before running Slackware setup.
But you would also need to know how to set that up before installing slackware.
But you would also need to know how to set that up before installing slackware.
No you would not. Slackware provides a full offline installer you can bring around with you. Read the MLED installation instructions again: nowhere is it mentioned in these instructions how to set up the system using anything other than a wired network connection. A FAQ afterthought is not the same as official installation instructions.
Can you show me where he says a working internet connection is not required here?
In the Trim section he states "In case you didn't use the set of tagfiles during the initial installation, now's the time to eventually catch up on it." Meaning you can skip the initial part, start with the install slackware section, configure your wifi, and then continue.
In the Trim section he states "In case you didn't use the set of tagfiles during the initial installation, now's the time to eventually catch up on it." Meaning you can skip the initial part, start with the install slackware section, configure your wifi, and then continue.
Agreed, I have yet to use the tag files. I do a full slackware install (minus KDE), set up my proprietary drivers, install MLED, and then set up a user. It's a lot simpler and easier that way...
Niki Doesn't have to provide his scripts to the slackware community, he can save MLED for his clients if he wanted to, but he's providing a very good product (in my opinion) and I am happy and grateful for his time and hard work.
Niki and his little cohort of supporters here arrogantly assume we all have wired networking, or access to an internet cafe, or a workbench with CAT5 cables hanging off a switch, or indeed are allowed by the business we are working for to take their computer off the premises just so we can install MLED for them.
Businesses that operate in areas where Internet access is very expensive or difficult to obtain would, I imagine, exercise due diligence and choose an IT solution that meets their needs taking into consideration the availability of local support.
I apologise if anything I have contributed to this discussion struck you as aggressive or disrespectful, that was not my intent.
I do think that your posts provide useful critical feedback about documentation for the authors of MLED, but I also think that the language you are using to convey your feedback may make it harder for people to treat your posts as actionable content.
I also apologise more generally for misunderstanding the plans for Slackware Live Edition and I thank Didier Spaier for correcting that.
I do think that your posts provide useful critical feedback about documentation for the authors of MLED, but I also think that the language you are using to convey your feedback may make it harder for people to treat your posts as actionable content.
Well I can tell you here and now that repeatedly making snide comments about theology in this forum is pretty damn offensive to some as well. But you people never seem to spot the beam in your own eyes when you're criticising others for the splinters in theirs.
Well I can tell you here and now that repeatedly making snide comments about theology in this forum is pretty damn offensive to some as well. But you people never seem to spot the beam in your own eyes when you're criticising others for the splinters in theirs.
Perhaps my use of the word 'theology' was ill advised, and my intent was not to cause distress to members of any particular religious faith. I was rather trying to provide a corrective to quite a lot of negative comments about MLED which is actually a gift freely given.
If I can, in recompense, attempt a summary of the actionable content so far
1) The most prominently displayed installation instructions for MLED make the implicit assumption that a *wired* Internet connection is available
2) The Migration FAQ entry provides an outline of an installation method that does not require an Internet connection until a Slackware installation is complete, allowing the use of normal Slackware tools to set up the Internet connection
3) Kikinovak is thinking about writing a more detailed installation guide
Perhaps my use of the word 'theology' was ill advised, and my intent was not to cause distress to members of any particular religious faith.
You have not caused distress at all. You've just resorted to a completely inappropriate forum to make scoffing remarks. You're not the first to do that kind of thing here.
Niki wants to present MLED as an enterprise spin of Slackware. He should provide enterprise-grade documentation if he wants to convey this impression, otherwise I shall be forced to assume, yet again, that Linux is still not ready for the enterprise, despite the proclamations of its loudest users.
If this is to be rolled out on the enterprise on computers that won't have internet access, it will likely be with a customized ISO that has everything needed. Why is it so hard to do that yourself? Why does it need to be spelled out? Windows is used for Enterprises, but I had to resort to 3rd-party websites to figure out how to make the installer work how I want it. Did I complain to Microsoft? No. I did a little bit of extra research so I could tailor the installation for my usage.
Sounds like you just have something against Niki, and you're using this thread for attacks.
And you keep stating that he needs to have a working wireless option for it to be considered "enterprise". Why? This would require changing the Slackware installer, which is further than what his project is designed to do. You can do an offline installation without any specific instructions (which he provides in his FAQ anyway) fairly easily with even a small amount of resourcefulness. The fact that you're struggling to comprehend this amazes me.
And keep in mind, Niki is not aiming for his project to cover all enterprises, since it lacks PAM and the like, it is to cover his enterprise that he installs on networks he manages. In that case, it is very much enterprise software, but just not for every enterprise. The fact that he is sharing it with us doesn't mean he is attempting to take over all possible enterprise usage. It may not fit your definition of enterprise software, but it definitely fits for Niki and his customers.
Well I can tell you here and now that repeatedly making snide comments about theology in this forum is pretty damn offensive to some as well. But you people never seem to spot the beam in your own eyes when you're criticising others for the splinters in theirs.
The last three pages in this thread have more or less been filled with your whining. Frankly, I'm sick of your affective cretinism and your entitlement princess manners. Downloading a set of packages and tagfiles is too complicated for you? You can't be bothered with pretty much anything and rather spend your time whining around? Go do some basic RTFM about setting up your wireless card or using PPPoE, since you're manifestly anal about not using a network cable during setup. But don't complain about it in this thread. This is Slackware, not Ubuntu, so play the game and deal with this distributions' idiosyncrasies, or get lost. At this point, you might as well choose the latter, because as far as I'm concerned, you're just a toxic troll, and I'm not inclined to help you out in any way.
I often have to install laptops for clients, and I always have a spare network cable dangling from the switch over my workbench. Initial installation is done via cable, and once everything is installed and configured, the last step consists in wiping /etc/rc.d/rc.inet1.conf and activating rc.networkmanager. Sometimes, before doing that, I have to fiddle around a bit with third party drivers like broadcom-sta, but more often than not, wireless works out of the box. It's not the nightmare it was ten years ago.
I'm surprised by how many people either seem to need an offline installation or don't have a basic thing like a network cable at hand.
Taking note. I'll think this through and see what I can do.
Something completely different. I had a very pleasant surprise today. A company that wishes to remain anonymous bought me a nice big HP build server with a Core i7 processor. This significant hardware upgrade will allow me to churn out MLED even faster. I added a big "Thank you!" note on the MLED website's News page.
for example, my router stands in a different floor and 'just a cable' does therefore not help,it is stupid but for now it is as it is, when they made the new cable they came into the house where it is closest to the street, not best for me.
so it is not that simple as having 'just a cable', of course you have to encounter such a situation to understand it and not make just assumptions about situations that you can not imagine.
for example, my router stands in a different floor and 'just a cable' does therefore not help,it is stupid but for now it is as it is, when they made the new cable they came into the house where it is closest to the street, not best for me.
so it is not that simple as having 'just a cable', of course you have to encounter such a situation to understand it and not make just assumptions about situations that you can not imagine.
For the last ten years or so, I've been performing Linux installations on a daily basis in all kinds of setups: private clients, companies, schools, libraries, etc. I have yet to encounter a situation where folks can't access their router because they buried it in their garden or decided to lock it in a safe and threw away the key.
A user just mailed me and asked for creating a mailing list for MLED, after reading through this thread. I think this is a good idea.
For the last ten years or so, I've been performing Linux installations on a daily basis in all kinds of setups: private clients, companies, schools, libraries, etc. I have yet to encounter a situation where folks can't access their router because they buried it in their garden or decided to lock it in a safe and threw away the key.
and even if this is the case you can use an other router as a bridge and connect via cable to this, haven't you seen it all?
but that's not the point, rather that peoples are not idiots if they do not exactly as you expect them to do
Quote:
Originally Posted by kikinovak
A user just mailed me and asked for creating a mailing list for MLED, after reading through this thread. I think this is a good idea.
Each time someone makes a critique, Niki answers in full. The problem isn't Niki's responses, its the fact that the critics are not receiving the answer they expect. MLED isn't meant for a world wide audience. It's meant to serve Niki's customers.
100000000000000 % right ! That's the best answer I've read since the beginning of this thread.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.