planish

That's what the BSOD is. It tries to bring the system back to a nice safe freshly-booted state where e.g. the fans are running and the GPU is not happily drawing several kilowatts and trying to catch fire.

Foreign to who?

Holy hell

I remember it as, Firefox was fast enough, but Chrome was shipping a weirdly quick JS engine and trying to convince people to put more stuff into JS because on Chrome that would be feasible. Nowdays if you go out without your turbo-JIT hand-optimized JS engine everyone laughs at you and it's Chrome's fault.

It sounds like nobody actually understood what you want.

You have a non-ZFS boot drive, and a big ZFS pool, and you want to save an image of the boot drive to the pool, as a backup for the boot drive.

I guess you don't want to image the drive while booted off it, because that could produce an image that isn't fully self-consistent. So then the problem is getting at the pool from something other than the system you have.

I think what you need to do is find something else you can boot that supports ZFS. I think the Ubuntu live images will do it. If not, you can try something like re-installing the setup you have, but onto a USB drive.

Then you have to boot to that and zfs import your pool. ZFS is pretty smart so it should just auto-detect the pool structure and where it wants to be mounted, and you can mount it. Don't do a ZFS feature upgrade on the pool though, or the other system might not understand it. It's also possible your live kernel might not have a new enough ZFS to understand the features your pool uses, and you might need to find a newer one.

Then once the pool is mounted you should be able to dd your boot drive block device to a file on the pool.

If you can't get this to work, you can try using a non-ZFS-speaking live Linux and dding your image to somewhere on the network big enough to hold it, which you may or may not have, and then booting the system and copying back from there to the pool.

That should just be the title bar now

I think we can trust that most phone camera apps do in fact obey the toggle they provide for whether or not to embed the GPS location data in the image.

shit how do you clean the dispenser tubes

Praise be to our lord and savior the UEFI Forum, that we might not all meet such a dismal fate.

This /c/ is catnip for lemmy users.

Welcome to /c/[email protected]

Sure

Like, each user is individually kicked off the PDS in reaction to some bad thing they did? Or labeling is reactive in that it labels bad stuff already posted, and each user has to pick labelers to listen to themselves?

I'm not sure if Bluesky's front-end defaults to using some particular labelers. I know there's some moderation going on for you as soon as you log in, done by someone.

But yes, each user has to choose whose moderation decisions they want to use, and they can't rely on everyone they can see also seeing exactly the same space they themselves are seeing. But I'm not sure it's possible or even desirable to get rid of the requirement/ability to choose your mods. I should be able to be in a community that has mods I trust, and the community chatting to itself and determining that so-and-so is a great mod who we should all listen to, and then all listening to them, sounds like a good idea to me.

Being able to see and talk to people who aren't in the same space I'm in might not be as good?