• 3 Posts
  • 103 Comments
Joined 2 years ago
cake
Cake day: June 8th, 2023

help-circle

  • Usually the routers you install OpenWRT on are really a CPU with one port to a VLAN-capable switch, and the port labeled WAN on the device is just VLAN’d separately by default. One cool thing OpenWRT lets you do on “normal” hardware is change the VLAN settings on the switch ports which are not accessible under stock firmware.

    But if they are shipping “just” the router piece and making people go get their own VLAN-capable switch, I’m not sure what hardware exactly they expect people to use? And I’m not sure what being connected to the switch over one real 2.5G cable is going to do to LAN/WAN throughput, vs. how a “normal” router ties the CPU into the switch through means not known to mortal minds. Maybe it is just as good, maybe it is a huge bottleneck. It is definitely going to add cost over the $89 sticker price.

    But if most people are just going to run fiber modem straight to WiFi, maybe this is the right config actually?













  • 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.






  • 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?