Search results

No. We're all much better than that. Arguing is a petty-bourgeois vice.

GPL code in training doesn't make any generated code GPL. Good luck to the FSF arguing that in court, though IANAL. GPL infection is done via linking and libraries may contain the linking exception or use the LGPL.

This is not true. I'm not a fan of Wikipedia but here are some pointers: https://en.wikipedia.org/wiki/Artificial_intelligence_and_copyright They won't go after NetBSD. Lawsuits are all about money.

The chance of this happening is close to nil. Why isn't NetBSD afraid of Oracle lawsuits over ZFS then?

In the worst case scenario, the code belongs to the Public Domain. That's why we shouldn't just accept whatever is copy/pasted but heavily modify it after review. LLM's are just another tool like compilers.

I kinda agree. I see some problematic developments: 1. Heavy-metal tends to be guitar-solo centric and over time the tendency has been to play them to perfection. So on one end of the spectrum you have Led Zeppelin, where each live album is different from each other, and in the other you have...

I bought a G11 at the store just yesterday and it's sad that they now produce 2 invoices. One for $159 so they pay less taxes and refund less to you and another with the real price that they tell you they won't refund. The whole thing is shady now. Sigh. At least I got a €30 discount code...

I used to like what he does on OS News. Then I made the mistake of following him on the Fediverse where he mostly shitposts and lots of times he clearly doesn't know what he's talking about. He says that FreeBSD is fascist because there's a package for xlibre. I find the abuse of this word...

The anti-AI bias from Thom Holwerda from OS News is well known.

I'm seeing commits tagged with `Assisted-By: Claude Opus 4.6`.

I reported it 2 years ago: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276240 Tried to fix it here but wasn't successful: https://github.com/freebsd/freebsd-src/pull/1020

You have to remove it from the blacklist: rm /usr/lib/modprobe.d/60-blacklist_fs-ufs.conf It's not that great. YMMV. ZFS is the way.

I dunno why these LinuxKPI commits were committed to the main & stable/15 branches the same day. Should have been tested in -CURRENT fist.

If you use ZFS you can also do a rollback to the latest snapshot (assuming you take snapshots before upgrading): mount -u / zfs rollback -r $(zfs list -t snapshot | tail -1 | awk '{ print $1 }')

And that's why it makes sense that newgrp has setuid turned off in FreeBSD. OpenBSD lacks the command. Only in NetBSD is setuid but any user could read the hashed group password in /etc/group

You can also use podman.

Group passwords are really neat. Before rootless Docker became possible on Linux, you had 2 options: either run docker through sudo or assign yourself to the docker group, which is dangerous. I chose a 3rd option that they adopted in their documentation...

Having a subforum makes a lot of sense as it would help to depoliticize the subject or keep it contained.

On *BSD there's no equivalent to Linux's /etc/gshadow to store the group password.

Turns out it's doable in FreeBSD with procctl(2) and PROC_NO_NEW_PRIVS_CTL https://man.freebsd.org/cgi/man.cgi?procctl(2) The command to do this would be: proccontrol -m nonewprivs /bin/sh I wonder if HardenedBSD would dare to do this in the future.