#Where does the webui pull this from?
1 messages · Page 1 of 1 (latest)
/etc/mainsailos-release
But it is not the UI it is moonraker. The UI has no direct access to any file or folder
Does the version of mainsail and the mainsailOS go hand in hand?
I guess that would be a negatory with 1.2.1 of the OS being the current release of it and 2.6.0 being mainsails release.
Is there a way to update the mainsailOS release without flashing the SDCard over again?
There is, but it's not supported
No MinsailOS version and Mainsail version do not go hand in hand. MainsailOS is an image that should help you to install your printer faster. Mainsail is the UI.
MainsailOS will get a new version if we change something at the surrounding e.g the switch from buster to bullseye or next to bookworm
Debian itself has no real way to switch versions so no there is no real way to update the base system without reflashing, all other parts of MainsailOS (klipper/moonraker/Mainsail/crowsnest …) are updatable without the need to flash new.
There is a way by changing the package sources of Debian but that until now always gets these system in a very unpredictable state and is therefore not recommended
As buster is out of long term support I highly recommend to consider to flash it new, you might wait a little an skip bullseye and use direct bookworm. But I can not guarantee that it will come soon as the changes the camera stack again and our preferred streamer does currently not even compile on it.
Debian itself has no real way to switch versions
I'm sorry, but this is factually incorrect. Speaking as a previous Debian Developer.
There is a way by changing the package sources of Debian but that until now always gets these system in a very unpredictable state and is therefore not recommended
This is the real issue, that the upgrade isn't supported by SBC OS vendors. There is no issue with the upgrade process itself, and it does exist.
@tired jungle then delight me how would a update of an SBC looks like? We talking here about rPI and others. The only real way I know for that is a reflash.
sudo sed --in-place --expression 's/buster/bullseye/g' /etc/apt/sources.list
sudo apt update
sudo apt dist-upgrade -y
and if you want to be extra safe, you do:
sudo apt update
sudo apt dist-upgrade -y
sudo sed --in-place --expression 's/buster/bullseye/g' /etc/apt/sources.list
sudo apt update
sudo apt dist-upgrade -y
tested the above myself while looking into the crowsnest upgrade issue, before it was made clear to me that the issue only impacted actual RPi camera modules
I was on 0.7.1 and upgraded like this then manually pulled all (klipper/moonraker/crowsnest) to fix the webcam being upgraded from 3 to 4. I looked through all the issue notes and none of them seemed to work for me but after doing that the camera worked again fine with v4. Then I had to rebuild the python klippy-env and add the comms connection for klippy.sock and flash the mcu then everything seemed ok so far.
Would be nice if there were scripts released when mainsailOS releases get made that could modify what issues or improvements were made on the fly to the same distribution version until you change sources.list to the next version.
MainsailOS is a service that should help you install your printer faster. From there on a update of Klipper/Moonraker/Mainsail is enough to get a up to date and running printer. We also provide a instruction on how to install all tools we develop by hand.
But the OS (and all improvements we do) will never be a rolling release.
Setup up a new SD card is a 15 min task
- backup your config folder
- backup the moonraker database
- flash a new sd card
- restore both
The changes we normally do to the OS either a new base version (buster,bullseye, bookworm) or convenience features