Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Data Storage Microsoft Open Source Patents Linux Technology

Microsoft Readies exFAT Patents For Linux and Open Source (zdnet.com) 119

An anonymous reader writes: For years, Microsoft used its patents as a way to profit from open-source products. The poster-child for Microsoft's intellectual property aggression were the File Allocation Table (FAT) patents. But the Microsoft of then is not the Microsoft of now. First, Microsoft open-sourced its entire patent portfolio and now Microsoft is explicitly making its last remaining FAT intellectual property, the exFAT patents, available to Linux and open source via the Open Invention Network (OIN). Microsoft announced that it now loves Linux and "we say that a lot, and we mean it! Today we're pleased to announce that Microsoft is supporting the addition of Microsoft's exFAT (Extended File Allocation Table) technology to the Linux kernel." ExFAT is based on FAT, one of the first floppy disk file systems. Over time, FAT became Microsoft's files ystem of choice for MS-DOS and Windows. It would become the default file system for many applications. Microsoft extended FAT to flash memory storage devices such as USB drives and SD cards in 2006 with exFAT. While FAT isn't commonly used today, exFAT is used in hundreds of millions of storage device. Indeed, exFAT is the official file system for SD Card Association's standard large capacity SD cards.

Now, Microsoft states: "It's important to us that the Linux community can make use of exFAT included in the Linux kernel with confidence. To this end, we will be making Microsoft's technical specification for exFAT publicly available to facilitate the development of conformant, interoperable implementations. We also support the eventual inclusion of a Linux kernel with exFAT support in a future revision of the Open Invention Network's Linux System Definition, where, once accepted, the code will benefit from the defensive patent commitments of OIN's 3040+ members and licensees." Specifically, according to a Microsoft representative, "Microsoft is supporting the addition of the exFAT file system to the Linux kernel and the eventual inclusion of a Linux kernel with exFAT support in a future revision of the Open Invention Network's Linux System Definition."

This discussion has been archived. No new comments can be posted.

Microsoft Readies exFAT Patents For Linux and Open Source

Comments Filter:
  • It is simple (Score:4, Informative)

    by chispito ( 1870390 ) on Wednesday August 28, 2019 @12:10PM (#59133368)
    Microsoft loves Linux.

    Running on Azure.
    • Re:It is simple (Score:4, Interesting)

      by stikves ( 127823 ) on Wednesday August 28, 2019 @02:53PM (#59134032) Homepage

      Which happened to be very good for everyone involved.

      Until the CEO change, Microsoft was Windows first, and Windows only. They had reluctant support on Mac OS, and barely existing one on Linux (via Skype and a few other things).

      Now it is software first, and the platform does not matter. They still want to sell Windows licenses, and Azure subscriptions, however if that does not hinder Linux, or even supplements it that is very welcome.

      (That does not mean that it would stay the same in the next decade or another).

      • by Anonymous Coward

        Correction: Now it is *spyware* first. For all of Ballmer's faults, he never spied on anyone or put ads in the OS or pulled shady shit like the forced Windows 10 "upgrade".

        It's only a matter of time before Windows 10 users are given the choice of paying a subscription or receiving increased amounts of ads baked into the OS. Users paying the subscription will still be subjected to some amount of ads and still won't be able to disable the spyware or control updates.

  • by Dallas May ( 4891515 ) on Wednesday August 28, 2019 @12:13PM (#59133388)

    Here is my Prediction:

    Next year:
    1) Windows and Windows Server (as brands) will still exist for years to come but will be fully migrated to Linux
    2) Win32 will be open sourced and migrated to full compatibility with Linux, Virtually all legacy windows application will run natively in Linux
    3) The full Office 365 suite will be available as a Linux native application

    • The full Office 365 suite will be available as a Linux native application

      But Ubuntu will offer it only as an overbloated "snap".

    • by fph il quozientatore ( 971015 ) on Wednesday August 28, 2019 @12:26PM (#59133430)
      2020 Year of the Linux desktop confirmed!
    • 1) Windows and Windows Server (as brands) will still exist for years to come but will be fully migrated to Linux

      That would be an interesting alliance again . . . Microsoft and IBM, as IBM now owns RedHat!

      Now make a reality TV show out of their "partnership"!

      • What does RedHat have to do with Linux? You seem to be confused. RedHat distributions "contain" Linux, but Linux distributions do not "contain" RedHat.

        Sort of like "Hot Dogs" contain pork, but pork (as in a nice shoulder roast) does not contain "Hot Dogs".

        • You seem to be confused. RedHat distributions "contain" Linux, but Linux distributions do not "contain" RedHat.

          Not to be pedantic, but I respectfully disagree. RedHat is a major Kernel and GNU utilities contributor. Linux distributions very much do contain RedHat. That's a good thing.

      • by rlwinm ( 6158720 )
        So it's 2019 and who could have predicted IBM messing up Linux (we know the're going to "IBMify" RedHat) and Microsoft helping it. Seriously. If you're as old as me (and ran the pre 1.0 kernels and 386BSD [no, not FreeBSD, 386BSD!]) then... wow has crap changed!
    • by AvitarX ( 172628 )

      Why 2?

      Why would open source windows have any need to migrate over?

      • 2 is the most important part. Many many many companies and governments that MS needs to stay in good graces with run legacy mission critical software. This software is an unsustainable pain for MS, because if Windows stops supporting the legacy software it looks bad on MS. However, the legacy software is becoming exponentially missed more expensive for MS to support. That was always the unkeepable promise MS Windows made, your software today will run on Windows forever.

        By open sourcing Win32, MS gets to wal

        • Win32 is not the problem. The Win32 API has not changed in decades. I have software that was written before the turn of the century that still runs perfectly fine on current versions of Windows. The problem is all the other fly-by-night shit that Microsoft promulgates so they can have planned obsolescence, and the reams of fanbois that insist on using the latest crappola from Microsoft because they cherish instability and the planned obsolescence means they get to sell the same old shit over and over and

          • " I have software that was written before the turn of the century that still runs perfectly fine on current versions of Windows."

            That's literally exactly what I'm talking about. Keeping Windows secure while still fully supporting decades of legacy software (much of it written at a time when security wasn't a thing people did) is exponentially more are more expensive for MS.

            So, MS needs to walk away but can't without upsetting many big important clients. Open sourcing that stuff and kicking the legacy suppo

    • by gtall ( 79522 )

      And we still won't use it due to its security holes and guis that look and work like a little demented leprechaun wanker on the Lucky Charms commercials.

    • Next year:

      Microsoft has been on the Linux bandwagon for the best part of this decade and only just got around to opening up patents to exFAT. If your prediction holds any weight at all it will be for something due to happen in 10+ years.

      • 10+ years is easy. My prediction is next year.

        MS already said Windows 10 is the last Windows version. That's a odd thing to say if you think about it. Sure, it's received major service pack updates, but based on MS's historic time line, it should be due for a replacement soon. Enter Linux Windows.

        • by Guspaz ( 556486 )

          Mac OS X has been the latest Mac OS version for nearly twenty years. Microsoft has adopted the same development pattern. Windows 10 doesn't get service packs, it gets annual or seasonal updates. Changes that used to wait for new OS releases, like memory compression or replacing the windows terminal, are now done in those updates.

    • by AmiMoJo ( 196126 )

      Seems more like they are going the other way, i.e. making Linux stuff work on the Windows kernel, e.g. WSL.

    • My friend, you define optimism.

      • I don't think it's simple optimism.

        The problem with Windows for MS is that MS made an unsustainable Windows promise that they couldn't keep. Every single version of Windows has to perfectly run every single third party legacy software written for Windows. The cost of that support grows exponentially with every Windows version. It's unsustainable. MS has to cut off its legacy promise, but doing so will look very bad on MS and will likely make them lose major clients.

        So, MS is slowly open sourcing all of the

        • This all seems to be predicated on your assumption that Microsoft wants to cut off their PC/Windows business, which contrary to popular belief here on Slashdot, is still making them quite a bit of money. Their Personal Computing division, which includes Windows sales, grew 4% last quarter and earned over $11 billion, which is about a third of their earnings.

          Microsoft is still investing in Windows, notably making it a more jack-of-all-trades desktop by incorporating Linux compatibility, which I suspect is l

    • Windows Server (as brands) will still exist for years to come but will be fully migrated to Linux

      I'm highly doubtful that Windows, at least in the server sense, would ever switch to a kernel it doesn't control. Google and it's history with Android is a great indicator of why that is. Hell IBM is a husk of what it used to be and they still develop actively their AS400 OS to this day. Now when it comes to desktop, maybe, maybe not.

      Win32 will be open sourced and migrated

      Well I'm not so sure about that. Some of the older API isn't Microsoft's. DDE, OLE, Some of the NT4 API, DCOM's de/serializing APIs, and so on. If we're sticking to moder

    • by gweihir ( 88907 )

      Timeline is negotiable, but it looks very much like MS is planning make Windows a Window Manager (+associated tools) on top of the Linux kernel. It would make a lot of sense technologically and from business-side.

      • I'm calling it.

        2020 is the year to do it. MS will release GNU/LINUX Windows.

        • by gweihir ( 88907 )

          Well, it would be really cool if you turn out to be correct!

        • It makes sense. After 2 decades, all the good backdoors are now buried in silicon. Hell, at some point, Microsoft could open source the NT kernel and userland code! Imagine all of the free bug fixes and better performance! EEE.
        • by rlwinm ( 6158720 )
          I already run a bunch of Win32 binaries on my Linux workstation. Personally I think the NT kernel has better thread synchronization primitives. I think Linux has better memory management. But the underlying kernel is really unimportant to most users. Granted, I am doing embedded (sometimes Linux) work but really - the kernel on my workstation could be NT, could be Linux, could be FreeBSD. As long as my editor, compilers, and special HW tools and PCB layout stuff work -- why would I care?
    • Not out of the question, but I predict that "next year" is too quick.
    • Here is my Prediction:

      Next year:
      1) Windows and Windows Server (as brands) will still exist for years to come but will be fully migrated to Linux
      2) Win32 will be open sourced and migrated to full compatibility with Linux, Virtually all legacy windows application will run natively in Linux
      3) The full Office 365 suite will be available as a Linux native application

      I doubt the Office 365 suite, they want to sell that online subscription !! They will migrate more of the office features to the O365 of the office suite.

  • Did something go wrong and there is no source link?

  • by Errol backfiring ( 1280012 ) on Wednesday August 28, 2019 @12:23PM (#59133418) Journal

    Microsoft announced that it now loves Linux

    And Father Christmas will give me a pony. Because he said so.

  • How about NTFS (Score:5, Insightful)

    by jfdavis668 ( 1414919 ) on Wednesday August 28, 2019 @12:23PM (#59133420)
    Now explain how NTFS works so Linux can ensure they handle it properly.
    • by aitikin ( 909209 )
      Came here to say that...
    • by Shark ( 78448 )

      I don't think Microsoft really knows how it works either. They just winged it and got lucky ;)

    • Comment removed based on user account deletion
      • There's the ext2 file system driver you can download. It supports ext2 read write and I believe ext3 read only. It's third party software but if you need to work with ext on Windows it helps.

        As for why Microsoft hasn't implemented it, it's probably because they haven't really had a need to until now. I suspect you might see something like ext support coming in the next year or two just because they're starting to push Linux integration.
    • It works like Microsoft Word format works... they aren't sure. It is patch on top of patch on top of patch and while there is some specifications, there are a lot of one offs all over the place that aren't explicitly documented, even internally.
  • by Danathar ( 267989 ) on Wednesday August 28, 2019 @12:27PM (#59133434) Journal
    AWESOME. I've been waiting for years to run / as exFAT. This should improve performance considerably....
    • by wierd_w ( 1375923 ) on Wednesday August 28, 2019 @01:05PM (#59133616)

      Why yes-- performance should increase if you are using flash media for your storage.

      Just, don't expect any of your linux-specific permissions sets to have any meaning, and hope you never have a power failure, because exFAT only keeps a single copy of the FAT, instead of keeping a failsafe copy, like older versions of FAT.

      (Better idea is to properly format your flash storage device with EXT4, using stride and stripe-width parameters, so that whole erase blocks are used on each committed write operation.)

      • Better idea is to properly format your flash storage device with EXT4

        I don't know about that - within the past couple of years I've lost EXT4 file systems on two separate occasions due to an unexpected loss of power. I've never had that issue with EXT3 or XFS and I've since banned EXT4 from all of the systems I administer at home and at work.

        • by Wolfrider ( 856 )

          > within the past couple of years I've lost EXT4 file systems on two separate occasions due to an unexpected loss of power

          --I suspect you might be doing something wrong, or there is some issue with the firmware on your drive... I've had unrecoverable btrfs (stopped using it entirely in favor of ZFS) and data loss on exfat, but no problems recovering ext4 with noatime.

          --Of course, backups are important tho...

  • ...the FAT patents finally expired (patents are only valid for 20 years) so they had nothing to lose.
    • exFAT's only been around since 2006.

    • The patents were bogus anyway, and no one would use this system anyway except that it's become the defacto standard for flash based filesystems that need to be compatible across systems - thus choose the worst system because it's popular rather than the best system. A file system is mostly a set of structures and protocols, and really nothing should even be possible to be patented in this. For example, a hashing scheme for quick filename lookup is a mathematical operation, and mathematical operations cann

  • FUSE is great for (relatively) low speed media like network shares and SD cards. It really starts showing its limitations if you start pushing large files around on external SSDs that are meant to be shared between systems. FAT32 hasn't really been viable for this in years.

  • What if Microsoft transitioned to the Linux Kernel since Apple went BSD any the *nix Wars began anew?

    • Re: (Score:3, Interesting)

      by Medievalist ( 16032 )

      Unix derived systems like Linux use a lightweight process creation model (the fork() system call is blazing fast) but the (post-NT) windows kernel is derived from DEC's VMS, and as such has such heavyweight process creation that threaded code is actually a good idea.

      So Microsoft will simply brand and develop their own Linux distribution (they are already well down that path) and sell it in parallel with Windows. It's extremely unlikely that they'll try to replace the NT kernel, it's not worth the level of

      • by lgw ( 121541 )

        Unix derived systems like Linux use a lightweight process creation model (the fork() system call is blazing fast) but the (post-NT) windows kernel is derived from DEC's VMS, and as such has such heavyweight process creation that threaded code is actually a good idea.

        The only difference between a process and a thread in the NT kernel is the protection boundaries. Threads are just faster in general because you can share objects between threads without serializing them. This is why threads are easy to work with in any modern programming language, and processes ... aren't.

        So Microsoft will simply brand and develop their own Linux distribution (they are already well down that path) and sell it in parallel with Windows. It's extremely unlikely that they'll try to replace the NT kernel, it's not worth the level of effort required when they can just sell linux at the same time.

        Replacing the NT kernel with the Linux kernel would be trivial for MS to do. It's more or less what WINE did, but much easier to do from the inside, as it were. Windows userland software talks to the

        • The only difference between a process and a thread in the NT kernel is the protection boundaries

          That isn't true... at all. Hell, there isn't even just one type of thread. I mean, why would you just make shit up like that?

          Replacing the NT kernel with the Linux kernel would be trivial for MS to do.

          WTF? No it wouldn't be trivial. Every single thing about the two are different, from the driver interface, to even the protection ring levels, to processes and threads, to every other bloody thing.

          FFS. Get o
          • by lgw ( 121541 )

            That isn't true... at all. Hell, there isn't even just one type of thread. I mean, why would you just make shit up like that?

            I've worked with several people who have worked on the NT kernel. Process boundaries aren't part of the thread dispatch and anti-starvation logic in NT, it's just a bucket of threads.

            Launching a new process obviously requires the overhead of setting up protection boundaries, which could be expensive depending on what you're ding.

            WTF? No it wouldn't be trivial. Every single thing about the two are different, from the driver interface, to even the protection ring levels, to processes and threads, to every other bloody thing.

            You do understand we're talking about implementing win32 over the Linux kernel APIs, right? What WINE already did?

            You don't want compatibility for stuff that uses the kernel APIs,

        • by Wolfrider ( 856 )

          > Replacing the NT kernel with the Linux kernel would be trivial for MS to do

          That's literally the stupidest thing I've heard all week. You obviously know NOTHING about backwards compatibility requirements on the Windows platform, much less Licensing.

          • by lgw ( 121541 )

            Not "Windows platform", but "Windows userland".

            MS would have a big win if the vast bulk of legacy Windows userland software would work with the Linux kernel. That just requires getting win32 to work with the Linux kernel (which WINE has mostly done) and getting the most commonly used "cheats" to work with the Linux kernel (which WINE has mostly done).

            MS could make WINE bulletproof, as they of course have the relevant source code to get to the bottom of the crufty corner cases.

        • The only difference between a process and a thread in the NT kernel is the protection boundaries. Threads are just faster in general because you can share objects between threads without serializing them. This is why threads are easy to work with in any modern programming language, and processes ... aren't.

          None of that is really accurate. It's almost jaw-droppingly wrong. [wikipedia.org]

          I have worked with kernel interactive code on linux, DEC RSX-11 and RT-11, VAX-VMS and post-NT Windows. That experience is what informed

  • Finally! (Score:3, Insightful)

    by poopie ( 35416 ) on Wednesday August 28, 2019 @12:46PM (#59133532) Journal

    Thank you, Microsoft. Better late than never.

  • by wierd_w ( 1375923 ) on Wednesday August 28, 2019 @12:49PM (#59133548)

    It is even more terrible than the older FAT32 it has supplanted, because it only has one copy of the table, instead of two.

    Additionally, it was adopted by the SDCard association because of two basic features:

    1) I allows OBSCENELY sized clusters, which just so happens to correspond with the native erase block sizes of larger SDcard media, because of how flash storage works under the hood, allowing exFAT to not have write amplification.

    2) Its simplicity means it can blast that data into the card very quickly, if unreliably. (again, a single FAT.)

    This is because Microsoft and Pals just cant bother themselves to make a proper journaling file system that works natively with obscenely huge physical sectors, and instead just threw some old shit at the wall, and it stuck.

    Linux CAN use SDCards "correctly" (ahem) by abusing the RAID functionality baked into EXT3/4. Just nobody seems that keen on doing this except the really geeky, because the media manufacturers seem completely unwilling to disclose what the physical allocation sizes are of their consumer grade media devices. (Forcing people to have to resort to esoteric interrogation of the media to suss out what that geometry actually is.) This means there is no quick and easy way to automatically determine what stripe and stride-width values to use to properly use the card, and so no linux tools helpfully jump in to go "Hey, dumbass-- that's an SDCard, let me format it PROPERLY for you."

    Accepting exFAT is accepting the lowest common denominator here.

    • > media manufacturers seem completely unwilling to disclose what the physical allocation sizes are of their consumer grade media devices. (Forcing people to have to resort to esoteric interrogation of the media to suss out what that geometry actually is.) This means there is no quick and easy way to automatically determine what stripe and stride-width values to use to properly use the card

      It occurs to me that if you align on 8MB, you will also be aligned on 4MB, 2MB, 1MB, 512K, 128K, etc. Just use a powe

      • by sjames ( 1099 )

        The alignment is the easy part. The thing is, you need to know the actual block size. If you choose wrong, you will wear the flash out much faster and get much worse performance as well as wasting a lot of capacity in the form of unneeded slack space.

  • Microsoft, like every other corporation on the planet loves the free work, as provided by the Linux ecosystem. Imagine a world where software from IBM, RedHat, Google, Apple and Microsoft was seamlessly made available to everyone. I see layoffs in the near future.
  • Because right now if you want to use a card >64Gb either inside of external (via an OTG adapter), you have to reformat it to FAT32 with Linux. Because Windows refuses to format FAT32 more than 64Gb. It then works well, but exFAT would be better, in particular to allow files above 4Gb.
  • This overall is a good thing. it shows Microsofts commitment to Linux.

    Microsoft is planning to transition Windows over to Wayland and a Linux kernel, and systemd. It will happen. This will include an system call emulation facility for running Windows apps on the Linux kernel (WINE is being considered) , and a compatibility facility for running Windows drivers on the Linux kernel. This is good for everyone since Microsoft can reduce development costs and as well the community gets more collaborative effort.

    • by riley ( 36484 )
      Citation required
    • That's one huge speculation.

      It's also not good for Microsoft. Yes, lower development costs - but also a lower cost for users who might seek to transition away from Windows entirely. Plenty of businesses would really love to save on those license fees, but right now the fees are cheaper than the cost of porting applications and training staff. The more linux-like Windows is, the better the prospect looks.

  • This is great for Linux but does it offer any protection or benefit to the FLOSS non-Linux operating systems out there? Random examples include FreeBSD, NetBSD, Haiku, ReactOS, RTEMS, HelenOS, etc.

    • No, it doesn't. This is almost certainly going to be the same kind of patent agreement Microsoft always use to divide & conquer. License the patents to some 'approved' free software/open source projects, and when other projects try to fork / use the same code exclude them.

      This is yet another way for them to control the open source world, and choose (pro-microsoft hegemony) winners.
  • Comment removed (Score:4, Interesting)

    by account_deleted ( 4530225 ) on Wednesday August 28, 2019 @01:35PM (#59133764)
    Comment removed based on user account deletion
    • Microsoft bet on software, IBM bet on hardware - and now Microsoft is looking enviously at Apple, who established the 'ecosystem' model in the consumer space, where every product promotes every other. It's a nice apple pie, and Microsoft wants a slice. You can't use Windows 10 stock without it making frequent, gentle but insistent nudges in the direction of the Microsoft store and OneDrive. You can't even install Windows 10 without it asking you to create a Microsoft account - though you can skip that if yo

  • This is just a piece of marketing for them. Trying to get some converts.
    I will believe their commitment to Open Source when they open source all of their products.

    That will never happen.
    • I will believe their commitment to Open Source when they open source all of their products.

      Could this be part of why Microsoft recently rebranded Microsoft Studios to Xbox Game Studios? If Microsoft became a free software company, a rebrand would at least make it easier to spin out the Xbox business without having to come up with a business model for developing original, high-production-value video games for release as free software from day one.

  • After a read of the summary, one could easily mistake it for being an April Fool's joke. But I guess Microsoft is now embracing open source. As the subject reads, hell hath completely frozen over.
  • The FUSE implementation does work well for me, but having exFAT in kernel will make it easier to use, and it will probably expand the support for this file system among non-PC devices.
  • For years, Microsoft used its patents as a way to profit from open-source products. The poster-child for Microsoft's intellectual property aggression were the File Allocation Table (FAT) patents. But the Microsoft of then is not the Microsoft of now

    The fuck it isn't, this is the same company that is currently extorting revenue from Android phone makers. It's understandable why your reader would want to remain anonymous. Here's a Microsoft front trying to patent SMS messages [unifiedpatents.com].

    Dominion Harb [intellectualventures.com]
  • Now lets see the SD Card association open source their IP so they not bilking small businesses $3k/yr to use an SD card in their product.

  • As of this moment, my fortune at the bottom of /. reads We are Microsoft. Unix is irrelevant. Openness is futile. Prepare to be assimilated.

  • Genuine question. I remember Microsoft releasing exFat in 2006. After looking at the description and reading that Microsoft planned to charge people who used it, I was left scratching my head. Why would someone use it in preference to fat which was free, or one of the numerous open source file systems out there which were not only free, but fast and robust as well?

    It's now 13 years down the track and I've never seen an exFat formatted anything - which meant everything has panned out pretty much as expect

  • It's a trap!

UNIX is hot. It's more than hot. It's steaming. It's quicksilver lightning with a laserbeam kicker. -- Michael Jay Tucker

Working...