On Tue, Mar 22, 2016 at 9:29 AM, Richard Brown <RBrownCCB@opensuse.org> wrote:
On 22 March 2016 at 05:05, Greg Freemyer <greg.freemyer@gmail.com> wrote:
All,
The ntfs-3g_ntfsprogs program does not currently include some of the more dangerous utilities that it could include.
WIth "./configure --enable-quarantined" several "dangerous" utilities get built and installed.
Given they are dangerous and possibly can destroy data I don't want to put them in the main ntfs-3g_ntfsprogs package.
For now I've created a sub-package to hold them:
ntfs-3g_ntfsprogs-quarantined
https://build.opensuse.org/package/show/home:gregfreemyer:branches:filesyste...
Is there a more appropriate name for the sub-package in the openSUSE naming conventions?
Typically, I think the openSUSE Project tries to avoid shipping software that can break your machine...
So I don't think we have a naming convention for doing it..
Not sure we want one either..why would someone need these quarantined features?
Richard, If there is no convention, I think I will follow upstream and call it ntfs-3g_ntfsprogs-quarantined. RE: your question The one I best understand is ntfsfallocate. Basically the issue is NTFS-3G provides a non-backward compatible feature. With fallocate in general you can allocate large files that you can latter fill in. Often done for the virtual disk in a VM as an example. In a matter of seconds you can allocate data blocks for a 100GB file. By doing it that way you reduce fragmentation, and also only take a relatively short period of time to create the file. (Who wants to wait minutes for a 100GB file to be zero-filled). ntfsfallocate allows that same behavior with the NTFS filesystem. The NTFS-3G driver in turn understands what is going on and can work with the file as data is later written to the allocated blocks. Windows on the other hand does not understand the data structure layout created by ntfsfallocate, and thus it can cause a problem. (Per the documentation. I haven't tested it.) The ntfsfallocate man page says you have to fill all of the allocated space with data in the Linux environment before the metadata / data layout is functional in Windows. === Thus a feasible use case might be to build a virtual drive for a VM in Linux on a NTFS filesystem, then try to run that VM in Windows. You will get a failure mode until all the individual data blocks have been written to at least once, but some users may find that an acceptable situation. Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org