Zypper. failed to start jobs. failed to enque some jobs

[sfalken]

So speaking as somebody that works with transactional-update quite regularly, I can say that while it is the default mechanism we use on MicroOS/Aeon/Kalpa, there’s nothing special about it, that requires use on a Read-only filesystem.

That being said, I agree, that recommending people just start using transactional-update on an already running installation of Tumbleweed can be problematic.

If somebody wanted to take advantage of the atomic updates transactional-update offers, and not work with a read only / there is the option, in the installer, to install Tumbleweed as a “transactional-server” at install time. (I think that’s the phrasing), which I think will give you the atomic updating via transactional-update with a traditional read-write filesystem, just like traditional Tumbleweed does.

I’ve not tried this, so don’t take it as gospel of any sort.

[arvidjaar]

@sfalken

with a traditional read-write filesystem

No, transactional server role will have read-only root. It can be viewed as grandfather of MicroOS.

                    <!-- root filesystem should be read-only -->
                    <btrfs_read_only config:type="boolean">true</btrfs_read_only>

[pavinjoseph]

@hendersj

I’ve been helping people in online forums for more than 30 years. I encourage people to experiment when it is safe to do so, but a production system is not the place to do that experimentation.

Respect for your experience and willingness to help people
I do agree with your position on experimenting on production systems.
In retrospect, @invalid_user_name does sound like he’s working on one.

I will create a post in a few months detailing how TU updates go, it’s just me and my two machines but at least I can be more certain when recommending it to others and it can serve as a reference for others to build on.

@sfalken I listened to your podcast! Didn’t know you were so involved with atomic desktops and even helping out the Ublue guys. I don’t know why it says next to your username “New or Quiet Penguin” when you’re neither

[sfalken]

I stand corrected.

[sfalken]

@pavinjoseph

@sfalken I listened to your podcast! Didn’t know you were so involved with atomic desktops and even helping out the Ublue guys. I don’t know why it says next to your username “New or Quiet Penguin” when you’re neither

¯_(ツ)_/¯

I assume that it’s whatever discourse has setup as the default “user badges” or some such. I have no clue what criteria goes into determining those.

[invalid_user_name]

@hcvv

Thus this is no case of fixing any error at all.

Thanks for the update. As I mentioned previously, I’ll explore hiring a Linux admin to look at the errors and advise and fix as needed.