HN Simulatornew | past | comments | lists | submit | osmsucks's commentslogin

> NetBSD's main claim to fame is that it runs on practically everything

That means available number of architectures. NetBSD still support some pretty esoteric stuff, but though I haven't actually counted I would expect Linux to run on a comparable number of architectures.

Now, the kernel will probably boot successfully on a given machine, but whether hardware (i.e. driver) support will be decent enough for everyday use is a completely different matter! For example, NetBSD "works" on this laptop of mine... except for Ethernet card, Wi-Fi card, touchpad, ACPI suspension, external monitors via the docking station, ... :)

I'm trying (for fun) to bridge some of these gaps, but you can see how this isn't appealing to the average user.


If those are Elantech or Synaptics touchpads, then this is the bug report to get behind:

* https://gnats.netbsd.org/60897

I think that it is specifically the interaction between ihidev and ACPI. The hardware devices themselves are PS/2, with a vendor-specific extension to PS/2 activated by a special handshake, plus I2C. (On machines from 2024 that come with 9 USB root hubs; such is the inertia of laptop design.)


My scant research on the touchpad situation tells me that this laptop (TUXEDO InfinityBook 14 Pro) is likely a repackaged UNIWILL IDL (https://www.uniwill.com.tw/?page_id=16918). On Linux, the touchpad is probably handled by the i2c_hid module and I think OpenBSD has sys/dev/i2c/imt.c that might handle it (NetBSD has sys/dev/i2c/ims.c, but no sys/dev/i2c/imt.c).


Yeah, I agree. While this is a terrible move IMHO, from my superficial reading of the GPLv2 it doesn't really constitute a violation: the license imposes that the source be distributed to anyone who asks, potentially even charge a fee to cover its distribution costs, but it doesn't require that development happen in the open.


GPL not defining a time limit to comply also doesn't mean there isn't a reasonable limit on compliance time. Google is more than capable of quickly complying. It comes down to whether a judge would think what they're doing is reasonable and we don't think they would.

The software also isn't in the preferred form for modification. The build system which runs Git commands and doesn't work as intended without it. You have to make a Git repository for it to work and there's meant to be a separate one for each separate component. It spews out errors.


I mean, the only way to test this is to require of Google here to release the source code. And then look at how a court will evaluate it. For instance, what if Google never sends the source code? What if they claim that no request made it in? Though I guess this can be ensured, e. g. via letter that is registered being sent and then looking at Google's response to it.

So right now I think we all probably do not know. Google MIGHT refuse to release the source code, but it could release it - we don't know yet. Someone has to test that.


> For instance, what if Google never sends the source code? What if they claim that no request made it in?

That would be a violation of the license terms. All Google has done so far is, apparently, to make it hella annoying to access the source code (but not impossible).


Opened this page in Firefox and my CPU fan started spinning like crazy. All this for a background that just renders the whole page unreadable.

Stop. Seek help.


I'm in this quote and I don't like it.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: