bonzini

51 ms·

931.
by bonzini 3y ago
Nope it's because it's the only 4K of memory that BASIC did not use and that wasn't mapped under the system ROM; so it was a common place where to put assembly language code to be loaded with a BASIC program, or to be used wh
932.
by bonzini 3y ago
He's talking about 8F/0 (pop) and FF/6 (push).
933.
by bonzini 3y ago
CVE fixes should not be available in RHEL only. If they are it's a bug. Of course RHEL might fix it with a backport whereas CentOS Stream might fix it with a new upstream version, but the fix should be there.
934.
by bonzini 3y ago
I have not yet fully made up my mind, but notice that there is a lot of nuance in the actual text. For example "Accepting donations without the intention of making a profit should not count as a commercial activity, unless such donatio
935.
by bonzini 3y ago
Do you know if the requirement is: * that a project is developed AND supplied commercially? * or rather that a project is developed OR supplied commercially? For example if I write an experimental project at work which might have vulnerabil
936.
by bonzini 3y ago
I absolutely haven't said I consider builders bad and I also was careful not to say rebuilders ! I am being very careful with my words. Please don't put things I didn't say in my mouth. However: unfortunately part of what yo
937.
by bonzini 3y ago
By builders I mean specifically those users that work with the full set of RPMs of the distro. It's not a badge of honor, it's a specific and very specialized way to consume what a distro offers. In the case of EL, Fedora and Cent
938.
by bonzini 3y ago
The builders community is where the next EL is built. It's Fedora ELN and CentOS Stream. You made your choice to keep focusing on "bug-for-bug" downstream instead, that's fine but I like it less than working together wit
939.
by bonzini 3y ago
You're talking about the users' community (and I have nothing to complain about that) and generic upstream; however I am talking about the builders' community instead.
940.
by bonzini 3y ago
That there is a community around enterprise Linux that you chose not to participate in, and that is the Fedora ELN/CentOS Stream community. And that I think I am finally understanding the differences between Alma and Rocky.
941.
by bonzini 3y ago
Software looks for them. Fedora code names are like "Thirty Eight".
942.
by bonzini 3y ago
> stopped sharing their toys As far as I can see Fedora and Stream still exist. You're basically talking about ~6 months of stable branch work that Red Hat would like to keep confined to their paid product.
943.
by bonzini 3y ago
> screw over our community For some definition of community.
944.
by bonzini 3y ago
The main benefit is periodic releases.
945.
by bonzini 3y ago
That's not a coincidence...
946.
by bonzini 3y ago
The thread-safety guarantees can only be obeyed if the arguments are thread-safe as well. For example, take a java.util.concurrent.ConcurrentHashMap, which is thread-safe. If your value object is mutated concurrently, and is not thread-saf
947.
by bonzini 3y ago
> I heard that a lot of RHEL packages are actually built from Fedora repos, which are maintained by voluntary contributors Most RHEL packages are at least co-maintained by paid Red Hat employees. Bring numbers please. > is now giving
948.
by bonzini 3y ago
And it used to be open, until Oracle started closing their tickets for paid support with essentially cut-and-paste of access.redhat.com. That's why you can't have nice things.
949.
by bonzini 3y ago
No, that's not being hostile towards open source. It's being indifferent towards people who want all your beer to be free. Red Hat is contributing upstream of RHEL in three different ways (actual upstream, Fedora, CentOS Stream).
950.
by bonzini 3y ago
There is a difference between package documentation and system documentation. Red Hat contributes package documentation upstream, but system documentation is by its nature distro-dependent. Red Hat has contributed work that made distros m
951.
by bonzini 3y ago
They're admitting that the Linux that enterprise people want is RHEL (or RHEL-based) and not SLES. Also, if CIQ follows them and SUSE bases this on CentOS Stream (at least for RHEL9; CentOS Stream 8 is admittedly a bit messy), this is
952.
by bonzini 3y ago
Even if that was the intended meaning, it's quite an extrapolation that Red Hat is "growing hostile towards open source as a whole", especially since people say that of Red Hat roughly every two years.
953.
by bonzini 3y ago
Note that the last paragraph is a supposition that is not rooted in reality. Red Hat is still doing upstream first development and is still mostly independent from IBM (who didn't participate in this decision).
954.
by bonzini 3y ago
To be honest it's a pretty good track record if you can only remember one instance of botching a backport, it's many years old, and it didn't have any security impact unlike Debian's ssh key generation.
955.
by bonzini 3y ago
Exactly, it's QEMU that abstracts over the processor virtualization APIs of KVM, Microsoft WHPX, Apple Hypervisor.framework etc. Not Libvirt.
956.
by bonzini 3y ago
KVM is not enough to create a virtual machine. KVM only virtualizes the processor, not a whole machine.
957.
by bonzini 3y ago
Nitro is the custom hardware that runs in AWS data centers (or in outposts). You can use it bare metal, or if you use VM instances it will run Linux (plus KVM) and a custom user space component that replaces QEMU.
958.
by bonzini 3y ago
According to the actual paper that introduced the distinction, and adjusting for change of terminology in the last 50 years, a type-1 hypervisor runs in kernel space and a type-2 hypervisor runs in user space. x86 is not virtualizable by a
959.
by bonzini 3y ago
Libvirt does not use KVM. Libvirt uses either QEMU (which in turn might or might not use KVM) or Xen or other hypervisors. So it's incorrect to say that Libvirt abstracts over KVM. And virt-manager indeed manages Libvirt machines so it
960.
by bonzini 3y ago
The main important point is that Libvirt takes care of privilege separation. It makes sure that if your VM and/or QEMU are broken out of, there are extra layers to prevent getting access to the whole physical machine. For example it ru

More ›