[-] fruitcantfly@programming.dev 1 points 4 hours ago

Development stopped not because LILO didn’t need any changes, but because of its limitations (source):

NOTE: I have finished development of LILO at December 2015 because of some limitations (e.g. with BTFS, GPT, RAID). If someone want to develop this nice software further, please let me know ...

Also, I dunno what your position is on this, but it is amusing to see calls for Canonical to replace GPL licensed software, with something with a more lenient license (BSD-3-clause). Normally that would cause outrage around here

[-] fruitcantfly@programming.dev 1 points 10 hours ago* (last edited 10 hours ago)

I guess they have their own fork of it?

Upstream hasn’t seen a new release, nor any commits, since 2015: https://lilo.joonet.de/

ETA: It is also my understanding that LILO fundamentally does not support reading filesystems, while Canonical want to keep SquashFS, among others. Adding support for that to LILO, along with whatever other features are missing, would likely be a major undertaking

[-] fruitcantfly@programming.dev 2 points 11 hours ago

and another thing: im not mad. please dont put in the newspaper that i got mad.

[-] fruitcantfly@programming.dev 27 points 1 day ago

It’s probably easier to strip down GRUB, than it is to resurrect and add missing features to a project that has been dead for 10+ years

It hasn’t been rolled back. You can go to the systemd repo and look at the main branch for yourself.

Here’s the commit. Just click through and see if the code was subsequently removed from any of the files. You’ll find that it wasn’t.

https://github.com/systemd/systemd/commit/7a858878a03966d2a65ef9e8f79b5caff352ac53

[-] fruitcantfly@programming.dev 1 points 2 days ago

Did you reply to the wrong comment? I have no idea how you managed to get all that from my comment. All I’m saying is, "when you hear hoofbeats, think of horses, not zebras”

[-] fruitcantfly@programming.dev 8 points 3 days ago

There is no verification and there is no surveillance: You can enter whatever value you want, or no value at all.

It’s exactly like the other personal information (full name, location, phone numbers) you can enter, when you create an account using standard tools on Linux

[-] fruitcantfly@programming.dev 1 points 3 days ago

That’s a lot less likely to be the case; I am aware of just one example of what you describe, and that’s the example you give, whereas I’ve “sped up” my own code many times, by accidentally breaking stuff.

Rather than assume the presence of backdoors, the rational thing is simply to work out why you are seeing a difference in performance, and to determine if you fixed something by accident, or (the more likely scenario) if you broke something by accident

[-] fruitcantfly@programming.dev 9 points 3 days ago

Ignoring /boot, what is the benefit of putting everything else in different subvolumes? As opposed to just one subvolume for / and one for /home, which is what I currently have. It just looks to me like it’d be extra work, but I’m probably missing something

[-] fruitcantfly@programming.dev 24 points 3 days ago

I also saw a 4.5 second boot time speedup from installing mine. I have NO IDEA how, but it’s happened.

If I saw a speedup that I didn’t understand, then I’d worry that I had accidentally broken something. It’s easy to get speedups by not doing things correctly

[-] fruitcantfly@programming.dev 2 points 5 days ago

They’ve already been using Claude for at least the last few months; you’ll find a CLAUDE.md file and related settings in the uv repo if you look

[-] fruitcantfly@programming.dev 58 points 3 months ago

At this point the people complaining about Rust at every opportunity have become more annoying than the "rewrite it in Rust" people ever were

view more: next ›

fruitcantfly

joined 2 years ago