r/devuan

Hey everyone! Just distrohopped from artix due to updates requiring a lot of maintenance and then one update left my system in an unbootable state. I felt it was too frequent and then it broke 😅 I have a feeling I made the right decision. However wanted to get any tips to avoid breakage if possible. I setup btrfs snapshots with snap-pac on artix. Snap-pac broke. Then I would manually create snapshots and snapshots didn't work. Ttys were also broken 😅. So hoping the debian base is more stable lol l. I'm rambling but thank you!

I've heard a lot of good things about devuan, especially since it doesn't use systemd. I'm curious if anyone has used or is using it for gaming. I wanna set it up so that I can use steam as well as create content using obs and kdenlive. Is it good for these kinds of activities?

Thanks to our community for sending us feedback. This helps us a lot to make MOS better and better ❤️

• Zusätzliche Benachrichtigungen für die Installation per API zu mos-install hinzufügen
• Logikfehler in smbd init.d beheben
• localmaster-Optionen zu smb.conf hinzufügen
• localmaster zur Samba-Initialisierungsdatei hinzufügen
• Sicherstellen, dass Smart auch bei Fehlern weiterläuft
• smartmontools-Standarddatei erstellen
• Korrekturen für die Docker-Bereitstellung
• Multiarch-Kompatibilität zu netbird init.d hinzufügen
• Multiarch-Kompatibilität zu tailscale init.d hinzufügen
• localmaster-Schlüssel zu mos/settings/network/services hinzufügen
• Smart-Konfigurationsfehler beheben
• Proxy-Ziele in der Vite-Konfiguration aktualisieren Testumgebung und Verbesserung der Listenelementdichte im Dateibrowser
• Proxy-Ziele in der Vite-Konfiguration aktualisieren
• Rollup-Optionen in der Vite-Konfiguration korrigieren
• Vue und zugehörige Bibliotheken in package.json auf die neuesten Versionen aktualisieren
• router/index.js für dynamische Importe zur besseren Codeaufteilung und Performance überarbeiten
• Vite-Konfiguration verbessern, um die Chunking-Strategie für externe Bibliotheken zu optimieren
• Unterstützung für Netbird- und Tailscale-Login/Logout in den Netzwerkeinstellungen hinzufügen
• Suchfunktion für Docker-, LXC- und VM-Container hinzufügen
• Unterstützung für die Anzeige und Verwaltung von Docker-Ports hinzufügen
• Benachrichtigungseinstellungen aktualisieren und E-Mail-Anbieter hinzufügen
• Remote-Tracking-Branch 'refs/remotes/origin/master' zusammenführen
• Unterstützung für GRUB und Localmaster in den Einstellungen hinzufügen
• Subreddit-Link aktualisiert

https://mos-official.net
https://docs.mos-official.net

https://preview.redd.it/ue9gke2eum1h1.jpg?width=1920&format=pjpg&auto=webp&s=f1f014b9fb1eb92fcd9b5ecd0eeb0cd9467cd4c0

i think we are very close to our first stable version 😉

Full Log:

• Recommend Kernel 6.18.29
• Update MergerFS v2.42.0
• Update mos-notify v0.1.5
• Added multi arch compatibility to netbird init.d
• Added multi arch compatibility to tailscale init.d
• Added notification persistence
• Added stop for notification init.d service
• Added verbose arg to notify service
• Applied logic fixes for DOCKER_CONFIG
• Made sure to update remote Docker sha correctly on update
• Hide output from prune
• Cleanup untagged docker images after running mos-update_containers
• Made sure to display no messages depending if no_autoupdate is true and where the update was triggered for docker updates
• Added no_autoupdate to docker container updates
• Fixed issue possibly getting wrong Docker index
• Made sure to save sha256_remote if it is an existing container not overwrite it
• Added no_autoupdate key to Docker deploy
• Added a few more diagnostic files to diagnostics
• Made sure to restart mos-notify only if config from providers change
• Fixed issue with shares being written incorrectly
• Added key persist_notifications to mos/settings/system endpoints
• Added mos/settings/notification endpoints
• Fixed issue with messages in docker websocket
• Fixed issue with no_autoupdate not working correctly in websocket
• Fixed issue with not updating local sha on force update from Compose Stacks
• Added no_autoupdate to Docker
• Added no_autoupdate to Compose
• Fixed issue with handling docker compose yaml files not correctly in MOS Hub if extension is yml instead of yaml
• Improved layout of IPv4 settings in network interfaces
• Added support for MTU settings in network interfaces
• Fixed IP addresses in ports and removed warning
• Added support for persistent notifications
• Added notification settings and updated UI for provider management
• Added new options for creating docker containers and compose stacks and updated UI
• Added support for "force update stack" option and improved error handling in multiple components
• Added support for "no auto update" option in docker forms

mos-official.net
docs.mos-official.net

Hi,

I'm a basic Linux user since years but I moved to Devuan last week on an old laptop for my daughters.
Basically everything is working fine I just have one question/issue.

Firstly I updated the repository in order to be at leatest version (just as I was used to do even under Debian in the past), what is new for me is that if a new Kernel version is released must be installed manually and it's not underline as update.

For example: I installed 6.19.something and then in Synaptic I found availability for 7.0.4, why the system didn't notify this new version?

To be clear: this is not an issue, if I want/need to updgrade version I can do manually but this is the first time happening