Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Ranting about systemd on Linux
I added a new file system /backup to my proxmox server ...
And at the next reboot - the system did not come up!
It was pingeable, but ssh did not work and strangely, it's local DNS name also did not resolve.
I finally attached a monitor to debug this ..
And the server was in "emergency mode", asking for the root password - on console!
And why?
Because systemd complained about some missing dependeny!
What in all the world has systemd to do with what I did configure in /etc/fstab?
That's not it's job!
And then, why in all the world enter some emergency mode, so that I cannot even login anymore??.
That is all sooo bad.
Comments
I had that happen. I screwed up the syntax in /etc/fstab when adding a volume.
But, I get it. The OS can't boot if it can't process the mount points. If you screw up fstab it doesn't know how to proceed, therefore it has no way of executing other processes such as ssh.
Are you saying that everything is fine in your fstab and it's puking just because you added /backup? That would be unusual.
btw, probably unrelated, but another similar situation happened when I didn't have enough power for all the drives attached to my Raspberry Pi. The fstab entry was fine, but when the added drive came online, the already mounted boot drive stopped because of not enough power. That caused the same kind of failure. I've since learned to hook up a monitor and usb keyboard at the first hint of problems at boot.
Yes, the file was totally fine for sure!
And it is Ok to complain about bad entries, but still it should boot if possible- and of course it could boot, even if the /backups entry was broken.
That is just a VERY bad idea and I start to understand why so many people hate systemd.
It tries and wants too much!
It seems, that this website may explain the problem:
https://billauer.co.il/blog/2023/12/systemd-dependencies-fstab/
It is so long that I did not yet read it.
Adding a line to /etc/fstab should not be such complicated.
RANT OFF
I've been on Debian Stable on all my systems (servers + desktops) for 6 years, but stuff like your post (and my preliminarily successful tests on a 2013 Mac Mini 😄) will make me switch to Devuan for future systems! 👌 (probably too lazy to reinstall any of the working systems while they're... working)