Tuxera Inc.| Private |
| Industry | Software and embedded systems |
|---|
| Founded | Finland (2008) |
|---|
| Headquarters | , |
|---|
Key people | Tuukka Ahoniemi, CEO
Szabolcs Szakacsits, President and CTO |
|---|
| Website | www.tuxera.com |
|---|
Tuxera Inc. develops and sells file systems software. Its most popular products are Tuxera NTFS and Tuxera exFAT, both available on a number of platforms including Linux, Android, QNX and macOS. Tuxera's customers include a number of consumer electronics manufacturers in mobile phones, tablets, TVs, set-top boxes, automotive infotainment and storage markets.[1] Tuxera NTFS for Mac provides read-write connectivity to Windows formatted hard drives for macOS.[2]
The company was founded in 2008 and is currently headquartered in Espoo, Finland. Tuxera's other offices are located in US, South Korea,[3], Japan, Germany, Taiwan and China.
History[edit]
Mar 16, 2020 NTFS-3G POSIX namespace incompatible with some embedded hw. I have a USB multimedia hard disk enclosure, they're the kind that look more or less like any enclosure, but have a small embedded computer inside allowing them to act as a standalone player. Tuxera NTFS is a performance optimized, fail-safe, fully compatible NTFS file system driver. It ships for example in smart TVs, set-top boxes, smartphones, tablets, routers, NAS and other devices. It is available for Android and other Linux platforms, QNX, WinCE Series 40, Nucleus RTOS and VxWorks.
The origin of the company dates back to the open-source NTFS development in the late 1990s. NTFS had been introduced in 1993 by Microsoft as the file system for Windows NT. At that time Anton Altaparmakov emerged as the lead developer and maintainer of the Linux NTFS kernel driver. Meanwhile, Szabolcs Szakacsits continued to lead a platform-independent project under the name NTFS-3G. In 2006, NTFS-3G became the first driver to gain full read and write support. Commercial activity started in 2007 and the company was founded next year. In 2009 the company signed agreements with Microsoft,[4] which was followed by global expansion and establishing the collaboration with chipset vendors and software platform companies.[5]
In February 2011 Tuxera joined the Linux Foundation,[6] which was an expected step as for many years Tuxera has contributed to the Linux kernel.
In July 2019 Tuxera acquired Datalight, [7] to strengthen its internal storage offering and expertise in flash memory and flash management software.
Embedded products[edit]
Microsoft NTFS by Tuxera (formerly Tuxera NTFS)[edit]
Tuxera NTFS is a performance optimized, fail-safe, fully compatible NTFS file system driver. It ships for example in smart TVs, set-top boxes, smartphones, tablets, routers, NAS and other devices. It is available for Android and other Linux platforms, QNX, WinCESeries 40, Nucleus RTOS and VxWorks. Supported architectures are ARM architecture, MIPS architecture, PowerPC, SuperH and x86.
Microsoft exFAT by Tuxera (formerly Tuxera exFAT)[edit]
Tuxera exFAT technology is used for SDXC memory card support. Tuxera was the first independent vendor to receive legal access to exFAT and TexFAT specifications, source code and verification tools from Microsoft.[8] Tuxera exFAT can be found in automotive infotainment systems, Android phones and tablets from ASUS, Fujitsu, Panasonic, Pantech and others.[9]
Microsoft FAT by Tuxera (formerly Tuxera FAT)[edit]
Tuxera FAT software provides interoperability and support for storage types such as SD memory card, CF card, Memory Stick, SSD, HDD via USB, SATA, eSATA, MMC and others.[10] It is used by chipset and hardware manufacturers, and software and system integrators for full compliance with Microsoft patent licenses and GPL.
Tuxera Ntfs Mac
NTFS-3G[edit]
NTFS-3G is the original free-software 'community edition' driver used widely in Linux distributions, including Fedora, Ubuntu, and others. In April 12, 2011 it was announced that Ntfsprogs project was merged with NTFS-3G.[11]
VelocityFS by Tuxera (formerly Tuxera Flash File System)[edit]
Tuxera also develops and commercializes its own proprietary Flash file system. Due to its fail-safe technology it can be found for instance in vehicles and cars, integrated with the event data recorder to make sure the data recorded from sensors is consistent even in case of a crash.[12]
Tuxera FAT+[edit]
In 2017, Tuxera introduced FAT+[13], a file system implementation for Universal Flash Storage cards and removable storage that is compatible with FAT32 but without the file size limitation of 4 GiB. It is royalty free for UFS card host devices[14] and a standard recommended by the Universal Flash Storage Association[15].
Consumer products[edit]
AllConnect[edit]
AllConnect is a mobile app that allows to stream music, photos and videos from Android devices to DLNA receivers (smart TVs, set-top-boxes, wireless speakers, etc.). It was launched in November 12, 2013 under the name of Streambels.[16]
Tuxera NTFS for Mac[edit]
Tuxera NTFS for Mac allows macOS computers to read and write NTFS partitions. By default, macOS provides only read access to NTFS partitions. The latest stable version of the driver is 2016, released in September 2016.[17] With the introduction of System Integrity Protection (SIP) by Apple in OS X El Capitan, usage of third-party software in Disk Utility is no longer possible. As a workaround, Tuxera NTFS for Mac ships together with Tuxera Disk Manager[18] to facilitate the format and maintenance of NTFS volumes in macOS. Currently the software supports 13 languages: Arabic, Simplified and Traditional Chinese, English, French, German, Italian, Japanese, Korean, Portuguese, Russian, Spanish and Turkish.[19] The software supports 64-bit kernels, including OS X El Capitan.[20] It supports NTFS extended attributes and works with virtualization and encryption solutions including Parallels Desktop and VMware Fusion.
SD Memory Card Formatter[edit]
Tuxera developed the official formatting application for SecureDigital memory cards, which is available as a free download for Windows and macOS.[21]
Tuxera Ntfs Embedded Windows 10
See also[edit]
Tuxera Ntfs Embedded File
References[edit]
Tuxera Ntfs
- ^Tuxera Shows Example In Finding Your Niche
- ^https://appducate.com/2013/01/read-write-to-windows-ntfs-partition-on-mac/
- ^Tuxera Opens Office in Korea - Market Leader in File Systems Expands Service and Support Across Asia
- ^https://blogs.technet.com/b/port25/archive/2009/08/26/tuxera-signs-file-system-ip-agreement-with-microsoft.aspx
- ^Suomalaisfirman ohjelmisto löytyy uusista Bemareista ja Mersuista
- ^https://www.reuters.com/article/2011/02/08/idUS118124+08-Feb-2011+MW20110208 Tuxera Joins Linux Foundation (Reuters)
- ^https://nordic9.com/news/tuxera-acquired-datalight-from-us-news2062421531/ Tuxera acquired Datalight from US
- ^James Kendrick, Android, Linux get Large File Handling With Tuxera exFAT
- ^Jani Timonen, 'Kotimainen ohjelmistoyritys Tuxera on teknologiaraketti – kasvua yli 6000 prosenttia', Helsingin Sanomat, 14.07.2015. Retrieved 05.10.2015.
- ^Tuxera FAT by Tuxera Inc.
- ^NTFS-3G Merges With NTFSprogs, Plus New Version
- ^Kristen Hall-Geisler, The importance of black boxes in an autonomous automotive future, 'TechCrunch', 13.05.2016. Retrieved 15.05.2016.
- ^Tuxera FAT+ File System for Embedded Systems is Compatible with FAT32, Faster, and Supports Files up to 16TB
- ^Mikko Välimäki, Introducing FAT+: A royalty-free file system technology for removable UFS cards, Flash Memory Summit, 10.08.2017. Retrieved 11.01.2018.
- ^Universal Flash Storage Association, Tuxera introduces FAT+, a futureproof and interoperable file system technology for Removable Flash Storage
- ^Streambels App Brings AirPlay and DLNA to Android Phones and Tablets Supports Media Streaming to the Most Popular Smart Devices on the Market
- ^Tuxera NTFS for Mac Release History
- ^Tuxera Disk Manager works around El Capitan to format drives that work with Windows
- ^Tuxera NTFS for Mac 2012
- ^RoaringApps - application compatibility for Mac OS X El Capitan
- ^https://www.sdcard.org/downloads/formatter/
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Tuxera&oldid=936861512'
| View unanswered posts | View active topics | It is currently Sat Apr 11, 2020 11:37
|
NTFS-3G POSIX namespace incompatible with some embedded hw.Moderators: d242, szaka
| Previous topic | Next topic |
NTFS-3G POSIX namespace incompatible with some embedded hw. | Author | Message |
|---|
NTFS-3G POSIX namespace incompatible with some embedded hw. I have a USB multimedia hard disk enclosure, they're the kind that look more or less like any enclosure, but have a small embedded computer inside allowing them to act as a standalone player.
The enclosure's media firmware therefore supports reading off the hard drive's filesystem directly, and can read NTFS. When plugged into a PC it shows up like any other generic external disk.
Anyways, getting to the point. At first I tried writing to it with NTFS-3G, and it seemed to work for awhile, then suddenly after copying a massive amount of data (over 200G), some files started to appear 'invisible' to the enclosure's firmware, however, when you plugged it into a PC (windows or linux with ntfs-3g), all the files were present.
After much troubleshooting and reading, I read about how NTFS was designed with three namespaces, and that NTFS-3G supports all three, but writes files in POSIX by default, I figured this was a likely cause because it's conceivable that a product like this might not conform 100% to the official NTFS specifications.
I decided to test this by doing several experiments, I wrote data from windows to the enclosure, and all of it was readable, then I tried to write a lot of data from linux (ntfs-3g) and again this specific data showed up as invisible, in some cases the top level folder was visible, but anything inside was invisible. Again, on a PC everything is visible. Then I deleted that same data and rewrote it from windows, and it shows up. I did this several times, and also used ntfsinfo from ntfsprogs to check what the namespaces were on certain files.
There's more information I might be able to provide on the testing methodology I used, but for now, as a first post, I just want to get the basics on the table.
Now, I know this is not an NTFS-3G bug, however, we all know what hardware vendors are like. The fact is that NTFS-3G's behavior in regards to it's default namespace is different than Windows, and this means some devices out there could be incompatible, not just mine.
However, before I get flamed, let me say this, I do agree that POSIX should be the default namespace, since it makes sense for UNIX/LINUX users.
But what I think is that there should be a mount option to override this default behavior, to make NTFS-3G behave like Windows XP's driver, assigning both Win32 and DOS entries to each file created.
There could be mount options to specify them separately, such as:
-o ntspace=win32,dos
-o ntspace=win32
I've looked in the manpage and something like that doesn't seem to be present. This would potentially increase compatibility with all devices that test only against Windows and nothing else. It is unlikely that any hardware vendors actually take the POSIX namespace (or even the DOS one for that matter) into account when designing their products, so I would not be surprised if there were other hardware out there that has this problem.
Oh, and by the way, I did contact the vendor earlier this week and told them there is a problem with their NTFS implementation, however I did not have as much information about the specifics then as I do now. I also have suspicions that they likely licensed their implementation from some other vendor, meaning they probably can't do anything and would have to pass on my problem to *their* OEM for their firmware, and so on.
Anyways, that is my situation. All suggestions and discussion is welcome. Thank you in advance for taking the time to read this [quite lenghty] post.
| | Sun Oct 05, 2008 04:15 |
Joined: Tue Nov 21, 2006 23:15
Posts: 1648
| Thank you for the interesting description.
The vendor should fix their firmware. Windows SFU also creates files in the POSIX namespace, so they have the same problem with Windows too in that case. All namespaces are STANDARD, one can't support only one, or two. NTFS-3G supports all but writes only in the POSIX namespace to maximize interoperability. This 100% conforms to the NTFS specification what the flawless Window interoperability also proves.
The POSIX namespace was not only designed and used for UNIX/Linux by Microsoft, but for all operating systems, including Windows and the one your embedded hardware uses. This is a government regulation Microsoft had to comply to be able to run for $$$$$ governmental and other businesses.
May I ask what are these 'some embedded hw'? We would like to document and warn people they have a non-conformant NTFS driver. Thank you.
Regards, Szaka
| | Sun Oct 05, 2008 12:01 | Hello, thank you for your response. I appreciate it.
The particular embedded hardware I am referring to in this case is my MediaSonic Media Player HM2-SU2TV.
I understand that the proper fix would be for the vendor to change their firmware, but it is quite unlikely that they will. I also know that even Windows sometimes creates files in the POSIX namespace, I recall seeing some files that're longer than the Win32 character limit. However, even Windows itself has problems and incompatibilities with these files, I have noticed that sometimes if you try to delete such a file it will say things like 'file doesn't exist' or something: http://www.google.com/search?q=filename+too-long
In other words, just because the namespace is 100% valid, that doesn't mean that they treat it equally. And most if not all files that the user would be copying to this media enclosure (mostly your movies, music and images) are going to be created using the Win32 & DOS namespaces. They have no reason to comply with my request to fix their firmware.
The bottom line here, is that I have hardware that works in both Windows and Linux, but ONLY when I write data from Windows, can the media enclosure's firmware READ the data. Regardless of who's 'fault' it is, or who is to blame, the fact is that the driver on Linux behaves differently than the Windows NTFS driver, and therefore the results with some implementations out there will be different.
Like I said, the *default* can remain POSIX, but why would it be such a bad thing to have a mount *option* to change it? Free Software and Open Source are about choice, and taking control of your computer, I should be able to tell the driver to write in whatever namespace *I* chose.
Right now I am in a position of being forced to use Windows because I cannot tell the Linux driver to write files in the namespace that I want it to.
I want to make it clear, this is not a bug report, it is more of a feature request, I'm not accusing NTFS-3G of having the problem, I already noted that the problem is with the firmware. But adding this simple feature to the driver could easily solve the issue.
I'm sorry for the post being long again, but I like to be thorough and I got the feeling that I did not explain myself very well the first time. Thank you.
| | Sun Oct 05, 2008 20:14 |
Joined: Tue Nov 21, 2006 23:15
Posts: 1648
| Re: : Free Software and Open Source are about choice, and taking control of your computer, I should be able to tell the driver to write in whatever namespace *I* chose.
Yes. Unlike your vendor to who you paid, this is why we gave you the source code and the right to be able to implement yourself what you want. But I sincerely hope you understand that you can't expect us to implement something brain-damaged (too long to explain) in our own free time so you can use your broken hardware because its vendor ignores you. If you don't want to code yourself then I suggest return your hardware or sell it then use some other one which knows how to implement NTFS properly. There are plenty ones.
| | Sun Oct 05, 2008 21:54 | I understand your view, however I don't see how this is 'brain-damaged'.
The vfat driver in linux has to do the same sorts of things.
How is it brain-damaged to support a write mode that the Windows NTFS driver supports? The fact is, the Windows driver can do something that yours cannot. And Microsoft, as much as many people despise them, *are* the reference implementation for all their technologies.
Just like the Wine project has a tradition of doing everything 'the windows way' to maximize compatibility, any other project seeking to implement Microsoft's technology would do well to follow that principle at least to some extent if they wish to reach a proper level of compatibility with the various products available out there that are *only* tested against Windows.
However, I will not press the issue any longer, although I'd be interested in the 'long explanation' of why implementing something that exists in windows, as well as in the vfat linux driver, could be considered brain-damaged.
Again, I appreciate that you have taken the time to answer me, and I hope you haven't interpreted me as being hostile in any way, I am trying to be as polite as possible in voicing my concerns and opinions, with the greatest amount of respect.
| | Sun Oct 05, 2008 22:23 | Hi,
I own the same product which you've discussed here. I'm having a bit of problem with it and after reading your extensive post I thought you might be able to help me out here. This maybe a bit outta what you've discussed here.
I recently upgraded the firmware from using a download from the URL mentioned in the manual (http://www.usbex.com/media01/) After the upgrade everything seemed to go well until the restart. It starts up as before (when connected to the TV) but I could not navigate or do anything at all. I assumed it might be due to a remote control fault and bought a new remote as well. Didnt work.
So I was wondering whether you would know how to downgrade/revert or undo the firmware upgrade.
Please help me out here/
Thanks
| | Thu Nov 20, 2008 22:37 | Re: NTFS-3G POSIX namespace incompatible with some embedded hw. I have the same problem with Packard Bell Studio 640 ( http://support.packardbell.com/it/item/ ... C052050001 )
Is there a workaround to this problem?
If I would try to patch the code, where should I begin? (in which part of the code?)
This hardware also claim FAT32 support, which is a pain, but it's better than nothing... I'd prefer NTFS support anyway.
| | Mon Jan 26, 2009 16:12 |
Who is online | Users browsing this forum: No registered users and 7 guests |
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum
|
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Original forum style by Vjacheslav Trushkin. |