Pretty sure I did. I have Wayland running on a Debian 12 box but didn't bother with on Alpine - might give that a shot soon on a non-server machine.

My condolences. 

Mon Jul 08 2024 10:50:04 EDT from fandarel

I'm running alpine on a spare laptop here, but it's a pretty spartan install.
wayland 

Booted. Ran install. It did some stuff ( past the point of making the file system and copying files. I think it was on the tail end of the setup ).. then *Poof*. I didn't even get to the point of doing anything to break it.

I might look at it again later. Might not. I donno. Long ago i did have it running but too much stuff was missing for me personally to use it. ( forget what now, but enough )

Mon Jul 15 2024 06:31:49 EDT from darknetuser

I wonder what you did there. I perform lots of Devuan installs for testing random crap and I rarely find any issue.

This was REALLY early on, perhaps pre-release days. Not sure now. And i cant tell you what i was missing, but there were a couple of things i use on a daily basis that were gone so the experiment didn't last long. It wasn't until now that i thought id peek again.  Could i have compiled them myself? Most likely. But really didn't feel like messing with it. If i have to go to that extent, might as well just go all-in and go Linux from scratch..  Or back to BSD.

( and speaking of BSD, not heard from our resident kitty for a while. Hope kitty is ok out there.   And Cat..   i cant imagine what her life is like in a war zone )

Mon Jul 15 2024 08:29:47 EDT from darknetuser

Really? I think it has worked as a Debian drop-in replacement pretty much since the first day of release. I had not noticed any missing component.

lol

"and for my next act.. "

From over on LXer's blog

"In light of the CrowdStrike-Microsoft outage/disaster that has been wreaking havoc on corporate Windows systems around the world since Friday, systemd lead developer Lennart Poettering pointed out how such a situation on Linux systems could be averted by leveraging systemd's Automatic Boot Assessment functionality."

Only have 2 words: F- pottering.

SystemD + wayland, might as well use windows. 

As much as i love proxmox, and like their backup solution, as far as features.. having it do backup/restores has got to be the slowest thing on the planet. In production, it would be a BAD scene.. "sorry, you are offline for a few days while we restore.. " is not a good thing to tell a customer.

Barely touching my network, no CPU use, and yet its taking days ( literally ) to restore my 3tb NAS VM after that drive died yesterday.

No i don't expect it to be instant with this much, but days???? I could understand if my CPU or network were the bottleneck, but no....  And while the bus on these boxes are not super fast due to their nature, i can still copy simple files around a hell of a lot faster.. so it CAN go faster.

I guess after all this is over im going to go back to using an external drive and let it backup directly from the host.  ( or i guess an NFS server, just reload this backup server or something. i donno i got all weekend to decide at this rate.  Grumble. )

According to logs im only getting about 181.93MB/s restore speed. 

Its a PVE VM server, + a PVE Backup server over a 1G network.

And of course after some 26+ hours.. the freaking server rebooted. ( i think my battery freaked out..  as the servers are set to power back up after a power cycle, and it did )

m.2 boot on the PVE.   SSD for teh data drive.   SSD on the BVE.     Also shut down all the VMs, this round to avoid any bus contention ( besides, most needed the NAS anyway )

its about 51% now, seems slightly faster ( still slow  )..  might be done by 10pm..   crossing my fingers.

Once the smoke clears ill try external again, do some measurements to see if the speed increase is worth the loss of features.    The other VMs, are all under 30g so they do fly, just this one is the big boy that had to die.  and this isn't my only backup, its mainly a storage for media.  I have a master copy on an external, but its a pita to copy all that over and put it back like it was.    ( other than files i had staged on the NAS to be backed up external... they are gone :( )

Seems wayland isn't well thought of over in the 9Front camp either.  Same sorts of reasons i dont like it.  Its anti-unix.  Someone brought it up and blew up the mailing list.

Now is X11 perfect? No of course not, but much like init/systemd, you dont toss it all out and head the wrong direction due to a burr, or agenda.  ( making it overly complex for code and support, monolithic not modular, not network centric, etc ). The right way is to work to fix what is there and keep going the correct direction.

I am a proud user of Unixlike systems and immense fan of the Unix Hater's Handbook.

Remember too, that Plan 9 was to fix all the mistakes..