Search
123 results for “av6”
-
Bienvenue à la v7 !
Il était temps pour IT Live Maps de passer à la vitesse supérieure.
De la même façon que la v6.0 était une refonte du socle qui a permis les nombreuses évolutions de la v6.1 jusqu’à v6.6 (voir le bilan de la v6) ; la v7.0 ouvre la voie vers de très nombreuses nouvelles fonctionnalités !
Les implications sont nombreuses :
Facilité et efficacité du […]
-
Well here's a Toyota Blade, with hideous taillights. A fat Corolla with a V6.
-
Day 10 of #ITAdvent There is now a v6 of the #Microsoft365 Foundations CIS benchmark available since November 2025! The Center for Internet Security (#CIS) is a non-profit org that publishes resources to harden your IT environments.
In almost all of my projects their best-practice recommendations are required and they are a very solid basis for your #security design. I haven't checked it for significant changes yet. Did you find anything that stood out? Let me know! -
#Statamic community: Are there rumors about a v6 release date yet? (support docs mention Q4 2025)
Currently stuck in a project where I want to use Filament v4 and the tiptap dependency blocks the install.
Should I just yolo it and install the v6 alpha?
-
Hey PostgreSQL users, is there a way to get the *expanded* IPv6 text representation of a v6 inet or cidr data type? Pg does a lovely job of compressing it correctly, but I need it uncompressed.
(Why: ".ip6.arpa", sadly. I'm doing DNS work.)Exporting to a file and running a standalone utility is _not_ a viable solution in this scenario.
Feel free to boost for visibility.
-
https://www.evshift.com/455506/the-1991-audi-quattro-spyder-was-a-groundbreaking-mid-engined-sports-car-concept-unveiled-at-the-frankfurt-motor-show-featuring-an-aluminum-body-permanent-all-wheel-drive-and-a-v6-engine/ The 1991 Audi Quattro Spyder was a groundbreaking mid-engined sports car concept unveiled at the Frankfurt Motor Show, featuring an aluminum body, permanent all-wheel drive, and a V6 engine. #AutoArt #AutoTech #AutomotiveArt #TransportTechnology #UnusualVehicles #WeirdWheels
-
Looks like Spinrite v6.1 has now been officially released by Steve at GRC.
I have a v6.0 license, purchased over 10yrs ago, and I received my free v6.1 upgrade offer yesterday!
Bigger drives, better performance, faster access, more hardware support.
Apparently it is even possible to improve SSD performance as it degrades over time.
Support for floppy drives has been dropped, but that is mitigated by the free access to v5.0 that you get.
Getting my copy now...
-
Looks like Spinrite v6.1 has now been officially released by Steve at GRC.
I have a v6.0 license, purchased over 10yrs ago, and I received my free v6.1 upgrade offer yesterday!
Bigger drives, better performance, faster access, more hardware support.
Apparently it is even possible to improve SSD performance as it degrades over time.
Support for floppy drives has been dropped, but that is mitigated by the free access to v5.0 that you get.
Getting my copy now...
-
Looks like Spinrite v6.1 has now been officially released by Steve at GRC.
I have a v6.0 license, purchased over 10yrs ago, and I received my free v6.1 upgrade offer yesterday!
Bigger drives, better performance, faster access, more hardware support.
Apparently it is even possible to improve SSD performance as it degrades over time.
Support for floppy drives has been dropped, but that is mitigated by the free access to v5.0 that you get.
Getting my copy now...
-
Looks like Spinrite v6.1 has now been officially released by Steve at GRC.
I have a v6.0 license, purchased over 10yrs ago, and I received my free v6.1 upgrade offer yesterday!
Bigger drives, better performance, faster access, more hardware support.
Apparently it is even possible to improve SSD performance as it degrades over time.
Support for floppy drives has been dropped, but that is mitigated by the free access to v5.0 that you get.
Getting my copy now...
-
Looks like Spinrite v6.1 has now been officially released by Steve at GRC.
I have a v6.0 license, purchased over 10yrs ago, and I received my free v6.1 upgrade offer yesterday!
Bigger drives, better performance, faster access, more hardware support.
Apparently it is even possible to improve SSD performance as it degrades over time.
Support for floppy drives has been dropped, but that is mitigated by the free access to v5.0 that you get.
Getting my copy now...
-
#Voron Tap question - since it’s the entire tool head that moves, I shouldn’t have an issue swapping out the actual hotend, right?
Printer comes with a V6 hotend and I don’t want that at all.
-
#Voron Tap question - since it’s the entire tool head that moves, I shouldn’t have an issue swapping out the actual hotend, right?
Printer comes with a V6 hotend and I don’t want that at all.
-
#Voron Tap question - since it’s the entire tool head that moves, I shouldn’t have an issue swapping out the actual hotend, right?
Printer comes with a V6 hotend and I don’t want that at all.
-
#Voron Tap question - since it’s the entire tool head that moves, I shouldn’t have an issue swapping out the actual hotend, right?
Printer comes with a V6 hotend and I don’t want that at all.
-
Okay, so please correct me if I'm wrong about the state of #OpenPGP right now.
So first there's the former #RFC4880bis which is now pursued as "#LibrePGP", used by #GnuPG (and #rnp?), with a "v5" key format, that everyone else seem to looks "politely" at.
Then there's #RFC9580 with a "v6" key format, used by #OpenPGPjs, #SequoiaPGP (and more) but explicitly rejected by GnuPG. However, it seems to be pushed forward under the assumption that GnuPG will yield to pressure.
So we effectively have two incompatible standards, with a "common denominator" of ancient #RFC4880, some tools pursuing one of them with disregard for the other, and a few supporting both for the sake of the users. And #Gentoo is effectively stuck with whatever GnuPG supports, because we need working crypto on all supported platforms, not just the "Rust subset".
-
Okay, so please correct me if I'm wrong about the state of #OpenPGP right now.
So first there's the former #RFC4880bis which is now pursued as "#LibrePGP", used by #GnuPG (and #rnp?), with a "v5" key format, that everyone else seem to looks "politely" at.
Then there's #RFC9580 with a "v6" key format, used by #OpenPGPjs, #SequoiaPGP (and more) but explicitly rejected by GnuPG. However, it seems to be pushed forward under the assumption that GnuPG will yield to pressure.
So we effectively have two incompatible standards, with a "common denominator" of ancient #RFC4880, some tools pursuing one of them with disregard for the other, and a few supporting both for the sake of the users. And #Gentoo is effectively stuck with whatever GnuPG supports, because we need working crypto on all supported platforms, not just the "Rust subset".
-
Okay, so please correct me if I'm wrong about the state of #OpenPGP right now.
So first there's the former #RFC4880bis which is now pursued as "#LibrePGP", used by #GnuPG (and #rnp?), with a "v5" key format, that everyone else seem to looks "politely" at.
Then there's #RFC9580 with a "v6" key format, used by #OpenPGPjs, #SequoiaPGP (and more) but explicitly rejected by GnuPG. However, it seems to be pushed forward under the assumption that GnuPG will yield to pressure.
So we effectively have two incompatible standards, with a "common denominator" of ancient #RFC4880, some tools pursuing one of them with disregard for the other, and a few supporting both for the sake of the users. And #Gentoo is effectively stuck with whatever GnuPG supports, because we need working crypto on all supported platforms, not just the "Rust subset".
-
Okay, so please correct me if I'm wrong about the state of #OpenPGP right now.
So first there's the former #RFC4880bis which is now pursued as "#LibrePGP", used by #GnuPG (and #rnp?), with a "v5" key format, that everyone else seem to looks "politely" at.
Then there's #RFC9580 with a "v6" key format, used by #OpenPGPjs, #SequoiaPGP (and more) but explicitly rejected by GnuPG. However, it seems to be pushed forward under the assumption that GnuPG will yield to pressure.
So we effectively have two incompatible standards, with a "common denominator" of ancient #RFC4880, some tools pursuing one of them with disregard for the other, and a few supporting both for the sake of the users. And #Gentoo is effectively stuck with whatever GnuPG supports, because we need working crypto on all supported platforms, not just the "Rust subset".
-
Okay, so please correct me if I'm wrong about the state of #OpenPGP right now.
So first there's the former #RFC4880bis which is now pursued as "#LibrePGP", used by #GnuPG (and #rnp?), with a "v5" key format, that everyone else seem to looks "politely" at.
Then there's #RFC9580 with a "v6" key format, used by #OpenPGPjs, #SequoiaPGP (and more) but explicitly rejected by GnuPG. However, it seems to be pushed forward under the assumption that GnuPG will yield to pressure.
So we effectively have two incompatible standards, with a "common denominator" of ancient #RFC4880, some tools pursuing one of them with disregard for the other, and a few supporting both for the sake of the users. And #Gentoo is effectively stuck with whatever GnuPG supports, because we need working crypto on all supported platforms, not just the "Rust subset".
-
Kernel 6.1 on my #OrangePi5 works okay but there's one major issue where my SD card would hang randomly and the driver had to manually reset the SD card controller.
That could be my card or it's a v6.1 issue.. maybe I should try to run the card on DDR50 mode.
-
Kernel 6.1 on my #OrangePi5 works okay but there's one major issue where my SD card would hang randomly and the driver had to manually reset the SD card controller.
That could be my card or it's a v6.1 issue.. maybe I should try to run the card on DDR50 mode.
