The Windows Driver Frameworks are on GitHub • Hacker News Board

Re: The Windows Driver Frameworks are on GitHub

#11

Post by viraptor » Thu, Mar 19, 2015, 6:37 AM UTC

sliverstorm wrote: post #6

[deleted] wrote: post #4

[deleted]

Let me see if I have this straight: - Keeps source closed. Is therefore evil. - Opens source. Must be up to no good, because is evil. This might qualify for the original meaning of, begging the question...

Considering the company pretty much defined EEE as we know it and is known for lying about competition, I don't think being cautious is a bad thing. I'm happy they're releasing things and trying to be more open, but... let's see where it goes before we start celebrating.

Re: The Windows Driver Frameworks are on GitHub

#12

Post by shmerl » Thu, Mar 19, 2015, 6:44 AM UTC

Will it help making drivers for filesystems which MS doesn't care to support?

Re: The Windows Driver Frameworks are on GitHub

#13

Post by whoopdedo » Thu, Mar 19, 2015, 6:58 AM UTC

shmerl wrote: post #12

Will it help making drivers for filesystems which MS doesn't care to support?

Drivers aren't much of a threat to the Windows hegemony because since Vista they've needed to be signed. If you don't mind taking the risk of running with driver signature verification turned off you can get FSDs for XFS and Ext4.

Re: The Windows Driver Frameworks are on GitHub

#14

Post by ximeng » Thu, Mar 19, 2015, 6:58 AM UTC

One barrier to developing drivers for Windows is the driver signing policy https://msdn.microsoft.com/en-us/library/windows/hardware/ff... which requires you to pay for a software publisher certificate.

Re: The Windows Driver Frameworks are on GitHub

#15

Post by ghuntley » Thu, Mar 19, 2015, 6:59 AM UTC

vortico wrote: post #2

I hope Microsoft knows this, but Open Source doesn't imply putting your source on GitHub (and vise-versa). If Microsoft dev teams served source tarballs along with their releases, we'd be just as happy. But perhaps they will actually use the GitHub issue trackers and other neat features, as they are pretty useful.

Uh, they have moved their entire development workflow to GitHub pull requests. Fully transparent and out in the open.

Work has commenced on getting CoreCLR (the official.NET run-time) ported and running on BSD and the following PR's were merged yesterday which add initial support for NetBSD and OpenBSD:

https://github.com/dotnet/coreclr/pull/453 https://github.com/dotnet/coreclr/pull/470

The "port team" is organzing work via the following issue:

https://github.com/dotnet/coreclr/issues/455#issuecomment-82...

We are looking for more people to help out, if this is of interest then please goto above and say Hello ;-)

Re: The Windows Driver Frameworks are on GitHub

#16

Post by Sanddancer » Thu, Mar 19, 2015, 7:06 AM UTC

shmerl wrote: post #12

Will it help making drivers for filesystems which MS doesn't care to support?

Probably not. The filesystem API Microsoft uses, Installable File System, has been in place and used by a bunch of people since the OS/2 days. Support for filesystems like zfs is lacking more due to apathy than anything else.

Re: The Windows Driver Frameworks are on GitHub

#17

Post by geon » Thu, Mar 19, 2015, 7:07 AM UTC

ximeng wrote: post #14

One barrier to developing drivers for Windows is the driver signing policy https://msdn.microsoft.com/en-us/library/windows/hardware/ff... which requires you to pay for a software publisher certificate.

Is it any different than the Apple iOS developer license?

Re: The Windows Driver Frameworks are on GitHub

#18

Post by aceperry » Thu, Mar 19, 2015, 7:12 AM UTC

I must say, I'm very impressed with all of the open source moves that MS has done lately. I wonder if that will drive more adoption of C# and cause Oracle to open up Java. I'm not a fan of C# because it's basically only used on windows systems, despite xamarin and et al.

Re: The Windows Driver Frameworks are on GitHub

#19

Post by Sanddancer » Thu, Mar 19, 2015, 7:16 AM UTC

geon wrote: post #17

ximeng wrote: post #14

One barrier to developing drivers for Windows is the driver signing policy https://msdn.microsoft.com/en-us/library/windows/hardware/ff... which requires you to pay for a software publisher certificate.

Is it any different than the Apple iOS developer license?

Yes. The certificates Microsoft requires use the standard CA system, and are pretty much bog-standard code signing certificates, so the key you need can also be used to sign other windows apps you make, java apps, mozilla add-ons, etc.

Re: The Windows Driver Frameworks are on GitHub

#20

Post by frozenport » Thu, Mar 19, 2015, 7:22 AM UTC

ximeng wrote: post #14

One barrier to developing drivers for Windows is the driver signing policy https://msdn.microsoft.com/en-us/library/windows/hardware/ff... which requires you to pay for a software publisher certificate.

I can live with this. Buggy software drivers wreak havoc and security vulnerabilities. I routinely use expensive industrial equipment without signed drivers, and the problem seems to be a warning from the installer.