> . If they don't do that, they're more likely to be broken by Linux changes, and it makes distributing their drivers more annoying So the idea is that having no drivers is better than having proprietary drivers? Seems like a perfectly reasonable and sensible approach..
having no drivers and having drivers that no longer work because the source isn't available and the maintainers can't update them is functionality identical.
Maybe they should stop breaking them then?
That’s a design decision, Linux maintainers decided to not have a stable ABI because they’d rather have no drivers at all than proprietary ones.
For the last 5 years, I have replaced FreeBSD on servers with Linux. The main reason is that Linux, is a lot less work. The time spent on upgrading for example Debian is significantly less than FreeBSD which has a cumbersome process which requires some manual human interaction a few times during the process. Another thing is that behaviour of some applications I write are different on FreeBSD compared to Linux. One p…
Did you create an issue about this data corruption?
For the last 5 years, I have replaced FreeBSD on servers with Linux. The main reason is that Linux, is a lot less work. The time spent on upgrading for example Debian is significantly less than FreeBSD which has a cumbersome process which requires some manual human interaction a few times during the process. Another thing is that behaviour of some applications I write are different on FreeBSD compared to Linux. One p…
So true! My family have a secret holiday destination. It has unspoiled beaches, friendly locals, cheap beer, amazing restaurants. When people ask where we went for summer we lie. "Oh we went to Ibiza again". Some things are best kept for yourself, not to be popular. We don't want "those sorts" dragging the whole show down to the lowest common denominator. So listen to the parent poster, and trust me, BSD is a piece o…
Yeah, that’s just, like, your opinion, man. For me, FreeBSD is rock-solid server and workstation OS. Documentation is very good, the Handbook is great, and most of the time the manual pages is all that you need. The ports collection is large and it’s not very hard to package your own software as a port. The OS is predictable and this is something I value highly.
For the last 5 years, I have replaced FreeBSD on servers with Linux. The main reason is that Linux, is a lot less work. The time spent on upgrading for example Debian is significantly less than FreeBSD which has a cumbersome process which requires some manual human interaction a few times during the process. Another thing is that behaviour of some applications I write are different on FreeBSD compared to Linux. One p…
FreeBSD upgrade and packaging will change a lot in 15.0.
Currently - up to 14.x - the freebsd-update(8) command is used for upgrades - and yes - it can require manual intervention - but one can also use it in unattended mode like that:
But the FreeBSD 15.x will use PKGBASE concept [1] and [2] and parts of the system will be 'just' pkg(8) packages and also maintained by pkg(8) - so FreeBSD Base System upgrades will be just pkg(8) commands - just like now with non system packages.
Can / does asterisk-BSD share many hardware drivers with Linux? IMHO that's the only way asterisk-BSD is to have any hope of catching up in the laptop space.
FreeBSD already uses GPU drivers from Linux and also starts to use Linux WiFi drivers.
having no drivers and having drivers that no longer work because the source isn't available and the maintainers can't update them is functionality identical.
Maybe they should stop breaking them then? That’s a design decision, Linux maintainers decided to not have a stable ABI because they’d rather have no drivers at all than proprietary ones.
The only decision to be made there is when to break them, not if. Linux went with "sooner than later".
having no drivers and having drivers that no longer work because the source isn't available and the maintainers can't update them is functionality identical.
Maybe they should stop breaking them then? That’s a design decision, Linux maintainers decided to not have a stable ABI because they’d rather have no drivers at all than proprietary ones.
if you prefer to have security vulnerabilities, you can always pin your kernel version?
the kernel needs to keep evolving, and the maintainers will keep your code updated for free - you just have to open source it.
So true! My family have a secret holiday destination. It has unspoiled beaches, friendly locals, cheap beer, amazing restaurants. When people ask where we went for summer we lie. "Oh we went to Ibiza again". Some things are best kept for yourself, not to be popular. We don't want "those sorts" dragging the whole show down to the lowest common denominator. So listen to the parent poster, and trust me, BSD is a piece o…
Yeah, that’s just, like, your opinion, man. For me, FreeBSD is rock-solid server and workstation OS. Documentation is very good, the Handbook is great, and most of the time the manual pages is all that you need. The ports collection is large and it’s not very hard to package your own software as a port. The OS is predictable and this is something I value highly.
You might want to read the comment you're replying to again.
As a long term FreeBSD user (since 2.0) and advocate, my view is that FreeBSD should focus on its niche as a rock-solid server operating system. For most developers buying a MacBook and SSH-ing into a server is probably the right answer (or running a VM if you really need something local). The level of effort to match the MacBook user experience feels like a lost cause (Linux has been trying to do this for decades wi…
On my bubble it is more like buying Windows laptops.