4,395 karma · joined November 23, 2015
On WSL you would be using the “hyperv 9p server”.
Same Linux 9p client in both cases but that’s not where the fix was.
Reasonable question but the answer is still no.
Worth a watch: https://youtu.be/1KeYzjILqDo
Plus any apple machine and the thinkpad x13s
And the raspberry pi
Yep just me ok
There are exceptions though in the very small "burstable" etc instances, like the micro etc.
EDIT: Seems I am wrong.
"Each vCPU is a thread of a CPU core, except for T2 instances and instances powered by AWS Graviton2 processors."
From: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance...
Turns out I’m also half deaf in one ear.
Anyway I’d recommend both a centre channel with adjustable volume and a hearing test.
can definitely drive and listen to a podcast when you’re good at it.
Rclone is also multi threaded so goes much faster compared to rsync
Seems like it may be borderline enough for the video part not being active but maybe similar to USB it might be "not quite enough".
Not so likely whatever remote target you are looking at has the same blocks and checksum algorithm.
On the upside you can often ask such file systems to take two snapshots and what changed between them. Or to export some kind of differential to transform the original snapshot to the newer snapshot. Both ZFS and Btrfs can do those.
Details: https://www.maketecheasier.com/enable-live-captions-ios-maco...
https://www.maketecheasier.com/enable-live-captions-ios-maco...
Google meet also has it built in on the client.
Edit: previously incorrectly linked to https://support.apple.com/en-au/guide/mac-help/mchlc1cb8d54/...
I guess 4GB seemed like a reasonable limit when FAT32 was designed.
Most likely FAT32 has a 32bit number for file size and ExFAT presumably has either a 64bit one or stores file size in some format other than bytes.
I expect to see a rapid push to enterprise with individual users left behind and a lot of broken stuff along the way :/
Details here: https://bugs.launchpad.net/bugs/1710341
It was since fixed though I never updated the bug.
src/util/virrandom.c:virRandomOnceInit seeds the random number generator using this formula: unsigned int seed = time(NULL) ^ getpid();
This seems to be a popular method after a quick google but it's easy to see how this can be problematic. The time is only in seconds, and during boot of a relatively identical system these numbers are both likely to be relatively similar across multiple systems which is quite likely in cloud-like environments. Secondly, by using bitwise OR only a small difference is created and if the 1st or 2nd MSB of the pid or time are 0 then it would be easy to have colliding values.
Though problematic from basic logic, I also tested this with a small test program trying 67,921 unique combinations of time() and pid() which produced only 5,693 random seeds using PID range 6799-6810 and time() range 1502484340 to 1502489999.
Some of the best I've had:
- Crumpler Backpacks (Dry Red No 5 & an older model I don't remember the name of)
- Bellroy Slim Wallet
- Bellroy Passport Wallet
- AirPods Pro
- UniFi AC Pro Access Points
- 2018 Subaru Outback PremiumAlso with pricing, pricing transparency is a real PITA.
You can do this either by launchign with "capsh" and should also be able to configure a systemd service to do it.
There seems some gotchas though so I haven't tested it with systemd but some references: https://serverfault.com/questions/916807/net-bind-capability...
https://stackoverflow.com/questions/413807/is-there-a-way-fo...
If you were to disable/lower privileged ports entirely you need to also realise there are, as always, a bunch of implicit security boundaries related to this that you need to account for. As a most simple example, if you can trigger a local DoS to force a process to exit then you can race to bind it's port and potentially do something nefarious - depending on the protocol you raced it may give you some privileges to deceive a remote host etc. Which is not to say you shouldn't do it in general but one must be aware of these implications when you want to change a literally decades old design decision that like all good bugs, many people depend on.
@antongribok sounds like you have it in hand having seen your subsequent comments just didn’t want to leave someone assuming that error rate was normal in the smaller clusters that are more commonly but not universally the case. Evidently not the case for you :)