You don't. You use Debian, Ubuntu, or redhat.
this post was submitted on 07 May 2025
17 points (81.5% liked)
Linux
54078 readers
731 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
The same way you set it up on every Linux. What's your specific problem?
There are a couple of downvotes, but this is a valid comment. It's considered good etiquette to demonstrate that some effort has been made to solve an issue when asking for guidance online.
Mx linux is a bad chioce if you cant answer this yourself because its going to differ from most other debian distros. You probably want to use normal debian or linux mint if you are still learning.
To answer anyway; youll want to install lighttpd or similar server using apt, then firgure out the differences between sysvinit and systemd so you can properly configure the server to start.
If you just use debian instead, "sudo apt install lighttpd" would be enough to get everything started.
because its going to differ from most other debian distros
How? It's just Debian with extra tools and sysvinit besides systemd.
then firgure out the differences between sysvinit and systemd
Or just set systemd as a default
You just answered your own question
So, clicking a setting in a gui once is such a big deal that MX is a bad choice? Next level...
I think you know its not just a matter of "clicking a setting in a gui once"
Why would you choose a non systemd based distro only to just switch it over to systemd? Why over complicate thinga for a new user who is clearly just starting out? Just use normal debian!
I think you know its not just a matter of "clicking a setting in a gui once"
I know it is that simple because I've done it while running MX on my devices... You can even switch between the two at boot freely.
Why would you choose a non systemd based distro only to just switch it over to systemd? Why over complicate thinga for a new user who is clearly just starting out? Just use normal debian!
It comes with tools that make system management a lot easier for beginners. I think that's more than a fair trade for having to click a single setting in a gui.
You obviously haven't used MX, and I have no clue where you're pulling your opinions out of from. Give it a try instead of continuing to spew nonsense.
I tried it about a week ago but since i have zero interest in alternatives to systemd or gui tools I find its easy to just install something that uses the things i want by default.
If you enjoy having that extea option and managing it with gui tools then im glad mx works for you, but it seems overcomplicated with no practical benefit to me.
What can sysv do that systemd cant anyway?
MX is just Debian under the hood.
https://itslinuxfoss.com/install-apache-web-server-debian-12-linux/
This one is a very useful link. Thanks 😊😊
What are you trying to host?
Just pick the webserver you want (nginx, caddy, etc..) and check the docs for Debian instructions since that's what MX Linux is.
Isn't it Debian without systemd? So it's going to be a pain to use regular documentation.
Ah, yeah MX might not be the best choice of a distro for ease of use.
I got this from someone :
When installing MX-Linux, you can also install the Apache web server. You will be asked during the installation. You can also install the web server later with the package manager.
When setting up, you just have then select the directories that you want to share for web access.
Are we still doing LAMP stacks? Is that still the thing to recommend?
Start small. Do one thing at a time. Set up apache, learn how to secure it, expose it, filter out probes and bots, etc. This is a long and fulfilling journey. Maybe.
I feel like nowadays it's more specific web servers instead of a general purpose one. Also containerization often is a thing.
How do you begin right from the scratch ?