@dvl i do this via local directories so far (keep meaning to setup a webserver for this). It is very annoying that (apparently) pkg has different behavior for local vs http repos. Let me experiment 🤔
@dvl so I do my local pkg repo setup via poudriere, one thing I note is that pkg is 'special', it is in "Latest" directory AND in the "All" directory, in the Latest directory it has its own individual signature, whereas the "All" directory is signed all at once with a signature that encompasses the ENTIRE repo together via their hashes; if you look in the Latest directory of your repo, do you have pkg there? is there a signature file next to it?
FreeBSD 13.0-RELEASE Now Available on Microsoft Azure Marketplace
I'd like to thank #FreeBSD for helping resolve an issue with the touchpad's physical buttons on my laptop.
Today I've been using 'mkjail update -a' to update all my jails with respect to recent published known vulns on #FreeBSD.
Why update the jail and the host? Because I can.
Patch everything when a patch is available. One vuln might have unknown leverage. I can't tell. So I patch.
@Gargron is this meaningfully transferring to net new users, or is this just conversion of existing users of the fediverse to a new client?
zero out drive for good measure. reboot.... garbage on the serial console.... power cycle. garbage. power cycle.. garbage... vague memories that this is why I pulled one of these machines out and gave up on the series for anything real...
Now I begin my trek through my spares....
No point trying to recover, and it is old.. there's no way this data is valuable, I look at it again.. yeah.. toast it. download fresh 12.2-RELEASE-SPARC.disc1.iso, check chesksums and signatures (ALWAYS DO THIS).. now to find CDR media... ZOMG found some... ZOMG, cdrecord works.. boots.. errors on sector way at the end. whatever burn again.. slower speed. new disk fails the EXACT SAME sector. whatever.. just boot and go
Morning. power outage.. crap.. go to check, the tar finished, great.. system reset, sitting at fsck.. unexpected fileystem error.. crap. run fsck ... EVERYTHING is corrupt.. double crap.. vague memory that I knew this.. that for some reason fsck on 11 on sparc would flag everything as bad even though filesystem was consistent, but fsck on 10 would show it all as good... crap...
ah, yes.. where did we leave off... oh yes.. it boots, it works.. wow even attempting the emulation was a waste of time. running FreeBSD 11.. so even pretty recent (for SPARC)... check it out.. 1G RAM.. but no swap. and there's some data on the drive I should preserve before I nuke it. Start the tar.. go to bed.
Relent. give up. Hardware time.
Go downstairs, find most convenient box pick it up, clean it off, bring it up, plug in, turn on.
WTF.. It boots. Its is sitting at a login prompt?! EVEN THE NVRAM IS VALID?!?!?!
FreeBSD enthusiast and frequent contributor, CommerceHub Staff Software Engineer.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!