News for hackers. Stuff that matters.
Re:Using /proc to get a process' current stack trace by someguydave on Monday October 15, 2018 @11:44AM (#18220632)
Also, how many of the aforementioned bsds use drivers that were ported from the Linux kernel tree?
Re:Using /proc to get a process' current stack trace by oneanddone on Monday October 15, 2018 @01:52PM (#18221924)
BSD user here. Of course there is porting occurring, but this is the nature of open source, is it not? Oftentimes, the BSD devs will take whatever hardware specs they can get and code something from that. OpenBSD frequently writes drivers that are orders of magnitude smaller than comparable Linux drivers, while getting the same functionality. NVIDIA drivers are but one example. Some hardware vendors are generous with hardware specs for OSS, most are not. OpenBSD, as an example, will not have any GPL'd code in the base OS, as it's not truly free. Ports are another issue.
Re:Using /proc to get a process' current stack trace by TheDong on Monday October 15, 2018 @05:07PM (#18223744)
> will not have any GPL'd code in the base OS, as it's not truly free

That's a disingenuous way to put it. The GPL is a free software license. It is "free" as in libre by all common definitions of "free" in regards to software.

The GPL is not compatible with the BSD dev's preferred license, which is much more likely the reason they avoid using such code.

By all conventional definitions, the BSD and GPL licenses are "truly free [software licenses]."

You're welcome to argue that the BSD license is better (because, for example, it lets sony create derivative playstation OSs without providing that source code to their users, ensuring their users have less freedom than if it were linux) or that the GPL is better (because it would prevent the previous), but they're both free licenses.

Re:Using /proc to get a process' current stack trace by monocasa on Monday October 15, 2018 @04:19PM (#18223306)
> will not have any GPL'd code in the base OS, as it's not truly free.

"My freedom to lock down someone else's code is more important than my user's freedom to have access to the code."

Re:Using /proc to get a process' current stack trace by trasz on Monday October 15, 2018 @05:19PM (#18223859)
No idea about other BSDs, but in case of FreeBSD that’s generally just Intel and AMD graphics drivers. All the rest is native.

And this goes both ways - at one point Linux folks famously managed to violate the BSD license when porting some WiFi driver, iirc, which is notable, since it’s not that easy given the licenses nature :-)

Re:Using /proc to get a process' current stack trace by dman on Monday October 15, 2018 @02:22PM (#18222219)
I dont understand how ports help / hinder usability of drivers. Could you please elaborate?
Re:Using /proc to get a process' current stack trace by someguydave on Monday October 15, 2018 @03:08PM (#18222709)
They don't. However, they do reduce the ability of the target O/S of the port to claim that it isn't a clone of Linux. The top-level post was complaining that people don't consider non-Linux O/S, and then failed to offer compelling alternatives.
Re:Using /proc to get a process' current stack trace by Annatar on Monday October 15, 2018 @04:55PM (#18223663)
I did not, I stated that nothing has changed: before people only knew PC buckets and Windows, now PC buckets and Linux is the only truth and religion. Nothing else exists. So the more things changed, the more they stayed the same. That's progress!

I also listed several alternatives just a few comments below, but apparently you didn't read that. You know of the old saying "you can bring a horse to the water, but you can't make him drink"?