- This topic has 20 replies, 12 voices, and was last updated Apr 26-3:47 pm by Robin.
-
Posts
-
mate76
Hey, I’m doing 3D printing and building printers. I wanted to use a Dell Wyse3040 terminal with Klipper operating system as a ‘control center’. Klipper is installed by default on RP, but I can also use a Linux computer. I have installed AntiX, unfortunately the Klipper (Kiauh) install scripts refer to systemd (systemctl) and the whole script crashes. My terminal has only 8Gb of EMMC memory, so the possibility of installing other distributions is very limited. Is there any way to install systemd or some packages to complete the Klipper installation process?
Marcin
Edit: AntiX is a very lightweight system and works perfectly on the terminal. It occupies 4Gb and does not load the processor very much. If it is not possible to install sysyemd, or some packages, maybe some other system you recommend? I am pretty poor on linux. You have a lot of experience.- This reply was modified 1 week ago by mate76.
RJP
About Klipper installation, it should be able to install without systemd.
https://www.klipper3d.org/Installation.html
Read also:
https://vitux.com/how-to-start-stop-or-restart-services-in-ubuntu/
Using Init scripts to manage services on Ubuntu
- This reply was modified 1 week ago by RJP.
On RP yes, but I use KIUAH it automates the installation process.
https://github.com/th33xitus/kiauh
https://www.youtube.com/watch?v=Ib1Dd3rIE2I- This reply was modified 1 week ago by mate76.
anticapitalista
Have you asked KIUAH if they provide systemd-free scripts?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
I asked a question on Klipper’s Discord. I really screwed up a lot of distros, unfortunately hardware resources are small. On yours at least Kiuah has moved on to installation.
Robin
unfortunately hardware resources are small.
Then you should abstain from systemd. The absence of systemd is one of the reasons antiX performs that agile on limited hardware resources.
Try using a KIUAH build from before ver. 3.0 as of 2021-01-31. Their changelog states, that at this point of time support of all non-systemd environments were dropped:
»Important changes to how installations are set up now: All components get installed as systemd services. Installation via init.d was dropped completely! This shouldn’t affect you at all,… I just wanted to mention it here.«
The last two sentences attests them a good pint of naïveté.
I don’t get the idea of expecting or enforcing systemd running on limited resources hardware.
Windows is like a submarine. Open a window and serious problems will start.
- You must be logged in to reply to this topic.
