It works on some devices; they do sign the builds as far as I can tell. But the bootloader itself needs to be convinceable to trust the LOS signatures, and needs to understand the secure boot implementation used in the Android that the current LOS is built from (since Android has re-done it all a few times). Nobody knows anything about bootloaders to figure out which of them can do this or how they would be induced to do it.
qsnc is a gentleperson and a scholar
You can print out QR codes to Rick Astley videos.
Thank you, I love to see these memes of production.
I wouldn’t recommend linking to it because IIRC it’s one of those web sites that can’t actually be relied on to serve the thing you linked to to the person who clicks the link. Instead it likes to serve complaints that they don’t have an account, kind of like Instagram.
So you would have to pair this with a switch that not only does VLANs but also somehow does your NAT for you.
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?
I don’t think that’s what accepting harmful interference means. It means more like, if there is noise in the channel, the device won’t just up its own power to clobber the noise, even if not doing that will somehow break it or otherwise make it not work right. It doesn’t mean you have to build the device so that some kinds of interference will cause it to break.
I think there are consumer-grade GPUs that can run this on a single card with enough quantization. Or if you want to run it on CPU you can buy and plug in enough DIMMs if you have an only somewhat large amount of money.
Looks like it has 32B in the name, so enough RAM to hold 32 billion weights plus activations (current values for the layer being run right now, which I think should be less than a gigabyte). It is probably made of 16 bit floats to start with, so something like 64 gigabytes, but if you start quantizing it to cram more weights into fewer bits, you can go down to like 4 bits per weight, or more like 16 gigabytes of memory to run (a slightly worse version of) the model.
If you’re good enough at writing to communicate all the information you need to something that is more different from you than any other human, why do you feel like you aren’t the best at writing?
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.
It’s still terrible though! Turn it 45 degrees why don’tcha!
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.
Does that work?
Is it right to tell random people “hey you, it’s your job to break local laws and topple your dictator, we could invade you with actual trained military people but that would be inconvenient for us”?