[arch-releng] [PATCH] [archiso] Document NTFS support (since syslinux 4.06)
Add a note that COW is not supported since ntfs.ko module is used inside initramfs.
(there is no ntfs-3g inside)
Signed-off-by: Gerardo Exequiel Pozzi
Am 25.10.2012 04:39, schrieb Gerardo Exequiel Pozzi:
-2) Create a FAT32 or EXTFS filesystem on such partition and setup a label. +2) Create a FAT32, EXTFS or NTFS filesystem on such partition and setup a label. +Note: COW is not supported on NTFS. # mkfs.vfat -F 32 -n <FS-LABEL> <DEV-TARGET-N> # mkfs.ext4 -L <FS-LABEL> <DEV-TARGET-N> +# mkfs.ntfs -L <FS-LABEL> <DEV-TARGET-N>
If you don't use sparse files (does NTFS even support them?), then the limited write capability of the kernel NTFS driver may be sufficient. It can write to existing files without changing their sizes as often as you want to. However, operations like file size changes, file creations and file deletions may result in "Operation not supported" seemingly randomly. (At least that was the state of the driver when ntfs-3g came out, I suppose they didn't remove any features since then.)
On 10/26/2012 05:38 AM, Thomas Bächler wrote:
-2) Create a FAT32 or EXTFS filesystem on such partition and setup a label. +2) Create a FAT32, EXTFS or NTFS filesystem on such partition and setup a label. +Note: COW is not supported on NTFS. # mkfs.vfat -F 32 -n <FS-LABEL> <DEV-TARGET-N> # mkfs.ext4 -L <FS-LABEL> <DEV-TARGET-N> +# mkfs.ntfs -L <FS-LABEL> <DEV-TARGET-N> If you don't use sparse files (does NTFS even support them?), then the
Am 25.10.2012 04:39, schrieb Gerardo Exequiel Pozzi: limited write capability of the kernel NTFS driver may be sufficient. It can write to existing files without changing their sizes as often as you want to. However, operations like file size changes, file creations and file deletions may result in "Operation not supported" seemingly randomly. (At least that was the state of the driver when ntfs-3g came out, I suppose they didn't remove any features since then.)
Yes NTFS support sparse files. I need to create a files and directories inside. However an experimental user can create needed COW files manually of desired size and use them, who knows if works OK... -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
Am 26.10.2012 16:28, schrieb Gerardo Exequiel Pozzi:
If you don't use sparse files (does NTFS even support them?), then the limited write capability of the kernel NTFS driver may be sufficient. It can write to existing files without changing their sizes as often as you want to. However, operations like file size changes, file creations and file deletions may result in "Operation not supported" seemingly randomly. (At least that was the state of the driver when ntfs-3g came out, I suppose they didn't remove any features since then.)
Yes NTFS support sparse files.
I need to create a files and directories inside. However an experimental user can create needed COW files manually of desired size and use them, who knows if works OK...
Alternatively: I just looked, and ntfs-3g + fuse + fuse kernel module is still under 2MB - compressed with xz-squashfs, this could be less than 1MB. Although the use case is rare, adding it is unproblematic.
Am 26.10.2012 16:34, schrieb Thomas Bächler:
Am 26.10.2012 16:28, schrieb Gerardo Exequiel Pozzi:
If you don't use sparse files (does NTFS even support them?), then the limited write capability of the kernel NTFS driver may be sufficient. It can write to existing files without changing their sizes as often as you want to. However, operations like file size changes, file creations and file deletions may result in "Operation not supported" seemingly randomly. (At least that was the state of the driver when ntfs-3g came out, I suppose they didn't remove any features since then.)
Yes NTFS support sparse files.
I need to create a files and directories inside. However an experimental user can create needed COW files manually of desired size and use them, who knows if works OK...
Alternatively: I just looked, and ntfs-3g + fuse + fuse kernel module is still under 2MB - compressed with xz-squashfs, this could be less than 1MB. Although the use case is rare, adding it is unproblematic.
Disregard that, in our complicated scheme, running a file system as a user space process only yells for trouble.
On 10/26/2012 11:35 AM, Thomas Bächler wrote:
Am 26.10.2012 16:34, schrieb Thomas Bächler:
Am 26.10.2012 16:28, schrieb Gerardo Exequiel Pozzi:
If you don't use sparse files (does NTFS even support them?), then the limited write capability of the kernel NTFS driver may be sufficient. It can write to existing files without changing their sizes as often as you want to. However, operations like file size changes, file creations and file deletions may result in "Operation not supported" seemingly randomly. (At least that was the state of the driver when ntfs-3g came out, I suppose they didn't remove any features since then.)
Yes NTFS support sparse files.
I need to create a files and directories inside. However an experimental user can create needed COW files manually of desired size and use them, who knows if works OK... Alternatively: I just looked, and ntfs-3g + fuse + fuse kernel module is still under 2MB - compressed with xz-squashfs, this could be less than 1MB. Although the use case is rare, adding it is unproblematic. Disregard that, in our complicated scheme, running a file system as a user space process only yells for trouble.
hehe, I true nightmare! -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
participants (2)
-
Gerardo Exequiel Pozzi
-
Thomas Bächler