and of course, because nothing is ever easy, I now have to forward-port code across 7 years of unrelated changes, and I may have to rethink bits a bit. Ah well, we'll get there.
Maybe it's finally time to update the negotiate() function to be cleaner.
Maybe it's finally time to update the negotiate() function to be cleaner.
all this to say that the NBD userland utilities will soon have:
- nbd-get-status: find out whether a device (or all known devices) is/are connected
- working -persist again (yay!)
- optional destroy-on-disconnect for the nbd device
#TFW you think you'll just update the kernel driver to support some feature because the kernel maintainer doesn't write it and it turns out he did write it and pushed patches for your code to a repository that you pulled from but he did it about a month *after* you pulled, and all that was SEVEN YEARS AGO and you just find out today.
@cks
Oh.
I see now that you mention 'the GUI', which I assume is virt-manager.
Sorry, missed that ๐คฆโโ๏ธ
@purpleidea
Oh.
I see now that you mention 'the GUI', which I assume is virt-manager.
Sorry, missed that ๐คฆโโ๏ธ
@purpleidea
@purpleidea
You can use it client side to manage systems over ssh, too. My laptop's configuration has four connections: one to the local system libvirt, one to my home server, one to my hosted server, and one to a VM on my hosted server that does nested virtualization.
Has the functionality of virt-install built in, and so much more...
@cks
You can use it client side to manage systems over ssh, too. My laptop's configuration has four connections: one to the local system libvirt, one to my home server, one to my hosted server, and one to a VM on my hosted server that does nested virtualization.
Has the functionality of virt-install built in, and so much more...
@cks
@purpleidea
And virt-manager.
The only time I ever edited XML was when I wanted to convert a Windows 10 VM to a Windows 11 one, which required that I changed the bios firmware to UEFI, and *that* required that I changed the system from PCI-based to PCIe.
No way could I have done that without virt-manager helping me making sure the XML is correct:
https://grep.be/blog/en/computer/Upgrading_a_Windows_10_VM_to_Windows_11/
@cks
And virt-manager.
The only time I ever edited XML was when I wanted to convert a Windows 10 VM to a Windows 11 one, which required that I changed the bios firmware to UEFI, and *that* required that I changed the system from PCI-based to PCIe.
No way could I have done that without virt-manager helping me making sure the XML is correct:
https://grep.be/blog/en/computer/Upgrading_a_Windows_10_VM_to_Windows_11/
@cks
@hyc
To be exact, it would run flat in an hour if it were to produce 500W sustained.
Not all batteries can sustain 500W without overheating ;-)
@RustyBertrand
To be exact, it would run flat in an hour if it were to produce 500W sustained.
Not all batteries can sustain 500W without overheating ;-)
@RustyBertrand
@Bright5park
Yes, there is that
Yes, there is that
@foone
Pretty sure they already can with the info you've just written down if they want.
Pretty sure they also don't want, because it would be embarrassing to the extreme for them to come forward after what you just wrote down ๐
Pretty sure they already can with the info you've just written down if they want.
Pretty sure they also don't want, because it would be embarrassing to the extreme for them to come forward after what you just wrote down ๐
@mcc
On the plus side, the gpl is reasonably easy to agree to.
On the plus side, the gpl is reasonably easy to agree to.
Lint
@foone
Not to mention the drum
Not to mention the drum
@campuscodi
It's actually not the EU mandating that. The law only says you can't track people without their consent. There are two obvious ways out of there: either you ask consent, or... you just don't track!
Shocking, I know.
It's actually not the EU mandating that. The law only says you can't track people without their consent. There are two obvious ways out of there: either you ask consent, or... you just don't track!
Shocking, I know.
@mjg59
I wish I could say you moet obviously be mistaken, but then I realize I've seen too much incompetence in this world to honestly believe that...
I wish I could say you moet obviously be mistaken, but then I realize I've seen too much incompetence in this world to honestly believe that...
@CyrilBrulebois
A year? Try six ๐
https://security-tracker.debian.org/tracker/CVE-2011-0530
We fixed CVE-2005-3534 on the released branch and found out six years later that we forgot to also fix it on the development branch ๐คฆโโ๏ธ
A year? Try six ๐
https://security-tracker.debian.org/tracker/CVE-2011-0530
We fixed CVE-2005-3534 on the released branch and found out six years later that we forgot to also fix it on the development branch ๐คฆโโ๏ธ
@icedquinn
I think nobody *prefers* public transport, except in areas where there's large traffic jams and the public transport bypasses those. Otherwise personal transport is faster and more convenient.
@sleepytako @rsf92 @pluralistic
I think nobody *prefers* public transport, except in areas where there's large traffic jams and the public transport bypasses those. Otherwise personal transport is faster and more convenient.
@sleepytako @rsf92 @pluralistic
@mirabilos
RFC3986, ยง3.1, second paragraph:
'An implementation should accept uppercase letters as equivalent to lowercase in scheme names (e.g., allow "HTTP" as well as "http") for the sake of robustness'
So if you are using something that doesn't work with uppercase letters in the scheme, file a bug. Otherwise, the uppercase letter causes no harm and is perfectly fine.
@sanguish
RFC3986, ยง3.1, second paragraph:
'An implementation should accept uppercase letters as equivalent to lowercase in scheme names (e.g., allow "HTTP" as well as "http") for the sake of robustness'
So if you are using something that doesn't work with uppercase letters in the scheme, file a bug. Otherwise, the uppercase letter causes no harm and is perfectly fine.
@sanguish