Remix.run Logo
adastra22 5 hours ago

I so wish that FreeBSD was GPL. I know this won't be a popular opinion, but I believe that success Linux has had is because of copyleft, and *BSD are riding on the coat tails of that.

But I don't like Linux. I use it daily, but I don't like it. I wish FreeBSD held the position Linux does in the market today. That would be heaven.

cesarb 4 hours ago | parent | next [-]

> but I believe that success Linux has had is because of copyleft

No, the success Linux has had is because it ran on the machines people had at home, and was very easy to try out.

An instructive example would be my own path into Linux: I started with DJGPP, but got annoyed because it couldn't multi-task (if you started a compilation within an IDE like Emacs, you had to wait until it finished before you could interact with the IDE again). So I wanted a real Unix, or something close enough to it.

The best option I found was Slackware. Back then, it could install directly into the MS-DOS partition (within the C:\LINUX directory, through the magic of the UMSDOS filesystem), and boot directly from MS-DOS (through the LOADLIN bootloader). That is: like DJGPP, it could be treated like a normal MS-DOS program (with the only caveat being that you had to reboot to get back to MS-DOS). No need to dedicate a partition to it. No need to take over the MBR or bootloader. It even worked when the disk used Ontrack Disk Manager (for those too young to have heard of it, older BIOS didn't understand large disks, so newer HDDs came bundled with software like that to workaround the BIOS limitations; Linux transparently understood the special partition scheme used by Ontrack).

It worked with all the hardware I had, and worked better than MS-DOS; after a while, I noticed I was spending all my time booted into Linux, and only then I dedicated a whole partition to it (and later, the whole disk). Of course, since by then I had already gotten used to Linux, I stayed in the Linux world.

What I've read later (somewhere in a couple of HN comments) was that, beyond not having all these cool tricks (UMSDOS, LOADLIN, support for Ontrack partitions), FreeBSD was also picky with its hardware choices. I'm not sure that the hardware I had would have been fully supported, and even if it were, I'd have to dedicate a whole disk (or, at least, a whole partition) to it, and it would also take over the boot process (in a way which probably would be incompatible with Ontrack).

sellmesoap 4 hours ago | parent [-]

I'd say with modern hardware, like the xe Intel iGPUs on 11th gen Intel and up got driver attention quickly. Some things like realtek 2.5gb NICs took a little while to integrate but I think realtek offered kernel modules. I remember NIC compatibility was sparse when I started playing with it around 1999-2000. What trips me up is command flags on gnu vs freebsd utils, ask me about the time I DOSed the Colo from the jump machine using the wrong packet argument interval.

assimpleaspossi 4 hours ago | parent | prev | next [-]

>>I believe that success Linux has had is because of copyleft, and *BSD are riding on the coat tails of that.

Apparently many here are unaware of the history and story as to what stalled FreeBSD in a long lawsuit involving ATT. You need to read up on that. Copyleft had nothing to do with it.

toast0 4 hours ago | parent | prev | next [-]

What would FreeBSD as GPL give you? You could fork it and release FreeGPL with that license tomorrow. (Minus ZFS, but that's in contrib)

Some users of FreeBSD prefer more freedoms than GPL offers. The contributors must not be put off by providing more freedoms.

Places I've worked have contributed changes to FreeBSD and Linux, mostly for the same reason ... regardless of any necessity from distributing code under license, it's nicer to keep your fork close to upstream and sending your changes upstream helps keep things close.

unexpectedtrap an hour ago | parent [-]

IANAL, but you can’t actually just relicense code, even if it’s under BSD‐like license. What you can do is to release this code in the binary form without providing the source code.

bluGill 29 minutes ago | parent [-]

Right you can add gpl code on top, but the base is still BSD

zie an hour ago | parent | prev | next [-]

I don't understand this thinking. The GPL is more restrictive than the FreeBSD license. You have more freedoms with the FreeBSD license than you do with the GPL(of any version).

> I wish FreeBSD held the position Linux does in the market today. That would be heaven.

Well The BSD's were embattled with a lawsuit from AT&T at the time Linux came around, so it got a late start as it were, even if it's a lot older.

unexpectedtrap an hour ago | parent | prev | next [-]

I feel the same, because it seems that the only desktop-ready OS under GPL today is GNU/Linux, and it feels too bloated nowadays (not to mention that Linux is effectively stuck under GPLv2). Something like FreeBSD feels much lighter and better still being desktop‐ready. Looks like that guys from Hyperbola think the same and that’s why they are doing HyperbolaBSD. Btw there’s some progress in GNU Hurd, but they are still far from being desktop-ready.

pyvpx 5 hours ago | parent | prev | next [-]

It’s a nice belief for some but wholly divorced from historical facts and circumstances

CalChris 5 hours ago | parent | prev | next [-]

GCC vs LLVM. It isn’t the license.

bigfishrunning 5 hours ago | parent | next [-]

I don't know about that... Llvm didn't exist until 2003. The BSDs and Linux both existed for a long time before that, and Linux already had much more momentum at that point.

coaksford 2 hours ago | parent [-]

BSD was mired in the uncertainty of a lawsuit over some of their code at the time that Linux was getting started, and the FUD around that gave Linux a head start that BSD had up until that point, so you can't infer much about the reasons Linux's early success over BSD through that fog. If Linux had been dealing with the same problem that BSD had instead, BSD almost certainly would be in Linux's place right now.

jm4 37 minutes ago | parent [-]

Linux was dealing with SCO just a few years later. There was also a period where Microsoft was out to destroy Linux.

blueflow 5 hours ago | parent | prev [-]

I think that's less because of the license and more because people found patching gcc to be a big pain.

tom_alexander 4 hours ago | parent | next [-]

To be fair, GCC's design was motivated by the same thing as the license. They intentionally didn't modularize GCC so that it couldn't be used by non-free code.

> Anything that makes it easier to use GCC back ends without GCC front ends--or simply brings GCC a big step closer to a form that would make such usage easy--would endanger our leverage for causing new front ends to be free.

https://gcc.gnu.org/legacy-ml/gcc/2000-01/msg00572.html

CalChris 5 hours ago | parent | prev [-]

Correct, it’s not the license.

cerved 4 hours ago | parent | prev | next [-]

It'll never happen. You can't distribute ZFS under GPL

sbseitz 3 hours ago | parent | next [-]

Comes in binary form from Debian and Ubuntu. I can add it to any other distribution via DKMS. Same core ZFS code as BSD uses.

pabs3 an hour ago | parent | next [-]

Debian only distributes it in DKMS form, not binary form.

matthewmc3 2 hours ago | parent | prev [-]

Honest question - if it comes in binary form, how can you know it's the same core ZFS code BSD uses?

E39M5S62 2 hours ago | parent [-]

Same as anything else installed as a binary package - you trust the people packaging/providing the binary. If you don't, build it yourself. The source is publicly available.

pabs3 an hour ago | parent [-]

Or you build it yourself and verify you got the same checksum.

https://reproducible-builds.org/

dardeaup 4 hours ago | parent | prev [-]

Agreed. I'd say it goes much deeper than that in the case of FreeBSD though. It's just an ideological thing that can't be changed.

a-dub 5 hours ago | parent | prev | next [-]

freebsd didn't have the hardware support base that linux did and suffered a huge delay in rearchitecture when x86 smp hardware became widely available. (only one cpu could be in the kernel at a time, the "bkl", was a major impediment in the early 00s). freebsd had better resource scheduling at the time and a beloved networking stack, but linux caught up with cgroups etc. i think linux was also just a trendy vanguard of sorts as the world learned of open source software by and of the internet.

movedx 4 hours ago | parent | prev | next [-]

Linux is OK. It’s a mess compared to BSD, but it’s OK. It’s the lazy man’s solution. It’s mainly for people who only want to “docker compose up” and walk away. The art of the OS has been lost. People think the OS is something to be abstracted away as much as possible and it’s evil and hard to secure. Shame.

stackghost 3 hours ago | parent [-]

I'd offer in counterargument that Linux is for getting things done, whereas BSD seems to be largely for people who view the OS itself as the hobby.

I have zero interest in tinkering with my operating system. I mostly want it to just get out of my way, which Linux does well 95% of the time.

quesera 3 hours ago | parent [-]

That used to be the argument for Windows over Linux.

FreeBSD has always required far less tweaking or maintenance than Linux, though.

hnthrowaway0328 5 hours ago | parent | prev | next [-]

Can you please elaborate the str of Freebsd vs Linux?

3 hours ago | parent | prev | next [-]
[deleted]
long__cat 2 hours ago | parent | prev | next [-]

[dead]

4 hours ago | parent | prev [-]
[deleted]