bboozzoo
Joined 9 years ago
Karma
230
Submissions
113
Member since
Jun 11
Recent submissions
Comment · 3 months ago
Why, LLMs of course. Isn't that obvious by now?
Comment · 3 months ago
It'd be interesting to add Nemotron, which is quite popular on Spark alongside Qwen 3.6.
Comment · 4 months ago
24.04 is a stable release. Package updates in stable releases need to follow the Stable Release Update process https://ubuntu.com/project/docs/SRU/stable-release-updates/
In essence someone needs to do contribute time and effort to make it happen. Canonical is free to choose the packages they want to maintain themselves and which ones go to universe and are community maintained. The upstream, if they care enough, can choose to get involved and try to do the updates. The process isn't exactly easy or fun. There's a bunch of requirements regarding backward compatibility and testing that need to be met. Snapd upstream goes though it for almost every release and it takes anything from a couple of weeks to a month. I don't think anything is stopping either party from updating the packages, although I don't why upstream wouldn't be interested in getting involved making this happen.
Comment · 4 months ago
> "There's a bike behind you travelling approximately X speed"
Funny how garmin varia gives the exact same information but on cars. "There's a car behind you travelling approximately X speed" (which is most often over the speed limit anyway)
Comment · 4 months ago
This looks like a choice is a serious eye injury if you roll is something you're looking for. Why not buy a handlebar mirror like this one https://cateye.com/intl/products/accessories/BM-45/ I have one on each of my bikes, road/gavel/fitness. Dirt cheap, gives very good rear visibility and very compact size.
Comment · 4 months ago
You forgot to mention it's also $200+. Some folks buy bicycles for less than that.
Comment · 5 months ago
Seven tokens long input isn't very realistic, is it? For coding tasks it's normal for the input to be thousands or 10s of thousands. If it wasn't for prefix caching it'd be one miserable experience, but even then at the very best the input is often in hundreds each time. And don't even try to dump some logs into the prompt.
Comment · 5 months ago
> An alternative service manager could
I guess we would care if one showed up, no?
Comment · 5 months ago
Why would they care about any other views but their own and those who contribute either financially or through code? Seems like all people can do these days is complain on github, X, mastodon, reddit, HN. It's only talk, talk and more talk, but no do.
Comment · 5 months ago
Can you share what was that thing that didn't work with systemd? I've seen pretty crazy setups and can't quite imagine how horrid of a mess those would have been if a large rc.init shell script ridden with sleeps was used instead.
Comment · 5 months ago
I believe this is called competition, encouraged since the EU markets are open and freedom of migration is guaranteed. If it wasn't for those guys, you'll have migrant workers from Ukraine, or India or some other place. However, I suspect that before the Poles and Romanians came to DE, you already had quite a bit of migration from Spain, Italy and Turkey, isn't that right?
Comment · 6 months ago
> patch series from a competent team that changes 3000 lines should probably be
split into a bunch of much smaller changes?
Comment · 6 months ago
Isn't that essentially a release of Ubuntu with a different kernel, DE and maybe some userspace utilities?
Comment · 6 months ago
The constructed policy is quite strict and expects certain UEFI things to be set up correctly. For example both this https://github.com/canonical/secboot/blob/7434bac27844362ff8... and https://github.com/canonical/secboot/blob/7434bac27844362ff8... are enabled in the policy. The policy choices and various early checks, even as trivial as confirming that the TCG log content is correct after booting into installation system, are enough to rule out a lot of potentially problematic EFI deployments. Effectively making it more strict helps avoid a lot of funny issues where the firmware is clearly buggy and things would fall apart sooner or later.