For interesting topics. But remember this is a Linux Forum. Do not post offensive topics that are meant to cause trouble with other members or are derogatory towards people of different genders, race, color, minors (this includes nudity and sex), politics or religion. Let's try to keep peace among the community and for visitors.
No spam on this or any other forums please! If you post advertisements on these forums, your account may be deleted.
Do not copy and paste entire or even up to half of someone else's words or articles into posts. Post only a few sentences or a paragraph and make sure to include a link back to original words or article. Otherwise it's copyright infringement.
You can talk about other distros here, but no MX bashing. You can email the developers of MX if you just want to say you dislike or hate MX.
dreamer wrote: Sat Apr 06, 2019 6:00 pm
RAM usage was high (700+)
That looks way too high.
I just checked the 3 Xubuntu live USB sticks I have. I booted them and without touching anyting else I immediately opened a terminal and did uname -a to figure out which was which and free -h.
18.04.2 LTS = 391 M
18.10 = 424 M
19.04 beta = 432 M
Thanks, those are better numbers. I must have had something running in the background (daily build April 5). This is great because then Xfce 4.13 isn't a memory hog.
Note to self and others: SysVinit is a good option. However if you run into problems try with systemd first. This applies to AppImages, Flatpaks, GitHub packages and even some Debian packages.
For comparison my Xubuntu 18.10 USB was 424 M.
My Xubuntu 18.10 installed to SSD with all the unnecessary services disabled is 319 M.
My MX 18.1 persistent USB with all the unnecessary services disabled is 293 M.
BV206 wrote: Sat Apr 06, 2019 8:56 pm
For comparison my Xubuntu 18.10 USB was 424 M.
My Xubuntu 18.10 installed to SSD with all the unnecessary services disabled is 319 M.
My MX 18.1 persistent USB with all the unnecessary services disabled is 293 M.
Good numbers!
Note to self and others: SysVinit is a good option. However if you run into problems try with systemd first. This applies to AppImages, Flatpaks, GitHub packages and even some Debian packages.
One thing I might add is that systemd can be slower to release memory so it's possible it held onto memory. That's one thing that differs from SysV. Systemd feels more like an engine like svchost.exe in Windows. It's constantly "active" in a way that reminds me more of Windows than Linux. Maybe systemd doesn't release memory if it doesn't have to? Maybe it speeds up the system by holding more stuff in memory?
I want systemd to work well, but I don't think I'll ever like it. I like certain things in Windows, but svchost.exe isn't one of them. What I like about a SysV system is how calm it feels. Calm, but responsive. That's all I need.
Note to self and others: SysVinit is a good option. However if you run into problems try with systemd first. This applies to AppImages, Flatpaks, GitHub packages and even some Debian packages.
dreamer wrote: Sat Apr 06, 2019 6:00 pm
RAM usage was high (700+)
That looks way too high.
I just checked the 3 Xubuntu live USB sticks I have. I booted them and without touching anyting else I immediately opened a terminal and did uname -a to figure out which was which and free -h.
18.04.2 LTS = 391 M
18.10 = 424 M
19.04 beta = 432 M
I have Xubuntu 18.04 installed on my second machine and it uses 370 M on the boot, I'm using Plank dock and it uses around 30-40 M.
Wouldn't that be in violation of systemd's GPL(2) licence?
The additional management tools could be designed such that they avoided "sharing code" with systemd components, and just provided a frontend for interacting with the configuration files of systemd components (along with sysfs files). Arguably, the "aggregate" need not be fully opensource.
