tlamponi

6 ms·

31.
by tlamponi 1y ago
There was a time when people said that about AMD. Don't get me wrong, Intel's outlook is IMO currently indeed rather bleak, but I would not completely write it off just yet.
32.
by tlamponi 1y ago
> Is it like writing frontend code in Rust and compiled to WASM ? Exactly, it's actually quite lightweight and stable plus mostly finished, so don't let the slower upstream releases discourage you from ever trying it more exten
33.
by tlamponi 1y ago
The linked forum post has an FAQ entry, this was a carefully weighted decision with many factors playing a role, including having more staff available to manage any potential release fall-out on our side. And we're in general pretty mu
34.
by tlamponi 1y ago
We manage anything, including package builds, ourselves if the need should arise; we also monitor Debian and release critical bugs closely, we see no realistic potential for any Proxmox relevant package to disappear, at least nothing higer
35.
by tlamponi 1y ago
> now how do I log in to rewrite the ifcfg file when the interface wasn't brought up with the correct config because it has a different name? Unlike most desktops, basically all servers got out-of-band management (e.g. IPMI) and a N
36.
by tlamponi 1y ago
Note that I'm neither a "sales people", nor is the one that made the original post, as that is Olaf from the Perl foundation, who reached out to me after I made a contribution to one of his Perl projects, if you must know. Tb
37.
by tlamponi 1y ago
As long as you only got NICs with different permanent MAC addresses installed that does not matter for getting actually long-term stable names. And for the other case you can still fallback to the other policies, it still will be much more
38.
by tlamponi 1y ago
Yeah, the permanent MAC address (i.e., the one the card actually reports to the system not the one dynamic one it can use) would be the safest bet, as that is the most stable thing there is, and more importantly, it is very relevant for swi
39.
by tlamponi 1y ago
Scam is probably the wrong word, and it's choice might be a bit feeling fueled, but it's really not true that this only depends on the HW. systemd also changes behavior in what naming policies are the default and what it considere
40.
by tlamponi 1y ago
Kill? no, definitively not. But 1) not adding a lot of extra and 2) applying the Pareto principle here are a huge difference. I.e. making the essential parts approachable enough to get one started while not being blocked too much by upfront
41.
by tlamponi 1y ago
The original one is still there. Systemd knows even about that, it's differentiated as MAC vs PermanentMAC.
42.
by tlamponi 1y ago
> This would be appealing in a world where Kubernetes doesn't exist as a mature option. The feature set of Kubernetes and Proxmox VE do not really overlap completely IMO, or would need much more hands-on approach and specialized in-
43.
by tlamponi 1y ago
Note that Proxmox did not put out any news, the Perl foundation did, and that is based in the USA, so not sure if it really shows what you try to suggest.
44.
by tlamponi 1y ago
Yeah, I know, I spent more than a week into looking for options to reduce impact for all of our users. And note that cgroupv1 also still works in the kernel just fine, only the part that systemd controlled was removed from systemd. You can
45.
by tlamponi 1y ago
If you want to package something from upstream git then you might want to check out https://optimizedbyotto.com/post/debian-packaging-from-git/ it is relatively new and uses a modernish tooling. The policy manual
46.
by tlamponi 1y ago
14 different schemes multiplied by some acting slightly different in every version. Sure you can pin it, but that fixes only their internal back and forth, is only possible via the kernel cmdline and there is no guarantee for how long the o
47.
by tlamponi 1y ago
While UI/UX is–as probably everywhere–a huge topic, we actually have spent most engineering power in the whole management stack. And of that managing QEMU/KVM–while surely significant–is by far not the biggest part of our also 100
48.
by tlamponi 1y ago
With some currently still a bit of hands-on approach you can set up measured boot that can measure everything from the BIOS (settings) through the kernel, the initrd, and also kernel command line parameters. I currently do not have time for
49.
by tlamponi 2y ago
You're right, but that's why SPICE has a so-called Agent that runs inside the guest and provides a neater integration (like seamless switching from client to host, ad-hoc USB passthrough, sharing the clipboard, detecting video str
50.
by tlamponi 2y ago
Thanks not only for your reply and chat invitation but also all of you for the work on this nice project! I'll relay your invitation to the persons mainly doing the evaluation. And good to hear that QOI image coded is getting further a
51.
by tlamponi 2y ago
Note that this is a bit of a POV thing. For one, CPU cycles handling display also go (indirectly) to your user. And if your users gets a crisper and better picture with less bandwidth due to a modern codec then it can be also seen as win in
52.
by tlamponi 2y ago
Here I'm talking about our integration, which means full audit of what's possible in a simple POC, then a more involved look to see how we can integrate it nicely in the Proxmox VE stack, from low level QEMU to the REST API and it
53.
by tlamponi 2y ago
> I wonder if tools like Proxmox could use this as a more efficient alternative to VNC (which is slow and weird) or SPICE (for which there are very few non-Linux tools). Yeah, we at Proxmox are actually evaluating such things, and we hop
54.
by tlamponi 2y ago
> https://magiskmanager.com/ WARNING: this is not the official site for Magisk [0], keep to the actual GitHub hosted repo and builds [1]. [0]: https://www.xda-developers.com/psa-magiskmanager-com-no
55.
by tlamponi 2y ago
I'm not sure what to get from this comment, are you sure you checked out the actual new interface? There's a screenshot here: https://pve.proxmox.com/mediawiki/images/7/76/Pdm-alpha-0.1.... &gt
56.
by tlamponi 2y ago
> is there a place to follow up on these developments, a roadmap of sorts? For PDM there is a roadmap [0] for the new widget toolkit there isn't such a single documents, but an initial whitepaper (well simple markdown-format
57.
by tlamponi 2y ago
Argh, I had a borked test, sorry! Now fixed the second module too and did a fresh clone in a fresh, isolated directory to confirm it really works now.
58.
by tlamponi 2y ago
It's an early alpha; the bigger news hidden within is our new Rust/Yew based web framework called proxmox-yew-widget-toolkit [0], it will allow us to move away from ExtJS (where the backing company seemingly forgot that they used
59.
by tlamponi 2y ago
> since they have a bogus url in their .gitmodules Fixed just now.
60.
by tlamponi 2y ago
Well, if that pro-NATO, pro-EU guy declared having spent no money on their campaign while their Face being plastered all over the place and other proof that someone spent money on a campaign for that person, and there's a law that spen

More ›