NTFS driver for hole-punching a Save file

Moderator: BarryK

Post Reply
williwaw
Posts: 1497
Joined: Tue Jul 14, 2020 11:24 pm
Has thanked: 136 times
Been thanked: 262 times

NTFS driver for hole-punching a Save file

Post by williwaw »

interesting developments

I (am compiling this kernel because) I want this NTFS driver because of support for "hole-punching", see earlier post:
https://bkhome.org/news/202105/automati ... puppy.html

I am considering redesigning EasyOS to use a "save-file" rather than a "save-folder". One reason is will enable frugal install on a PC which only has a NTFS partition, no need to create a ext4 partition.

and a windows user could also utilise something like this? https://rodsbooks.com/refind/installing.html#windows or https://sourceforge.net/projects/grub2win/ ?

User avatar
BarryK
Posts: 2169
Joined: Tue Dec 24, 2019 1:04 pm
Has thanked: 93 times
Been thanked: 514 times

Re: NTFS driver for hole-punching a Save file

Post by BarryK »

Yes, fascinating possibilities.

Ramachandra has been posting in another thread about unable to multiboot on his new HP laptop:

viewtopic.php?f=63&t=2593

He created an esp fat partition for a frugal install of EasyOS, and by pressing F9 key at bootup, got a list of boot options and was able to choose which one to boot.

However, the F10 key brings up UEFI-BIOS setup, and it has no way to change the default boot choice. It stays stuck on Windows.

Ramachandra reports that many others have complained about this, and on the Internet he found a solution. This is his email to me:

Nothing worked to get the refind.conf menu upon booting my HP Laptop, as a last resort I have attempted some work around in the Microsoft EFI folder. As per suggestions from Internet, I have copied BootX64.EFI from EFI folder of easyos and put it on Windows EFI (EFI/MICROSFOT/BOOT/BOOTMGFW.EFI) and renamed bootex64.efi to bootmgfe.efi. then rebooted the system. Now, Laptop boot into EFI of easyos. (Still as informed easyos is not booting). Moreover, no menu entry for Antix Linux. The menu entry is given below;-

Boot Fall back boot loader (Partition label SYSTEM)
Boot Vmlinx (Partition Label Easy)
Boot Fall back Boot loader (partition Label Easy)
About Refind
Shutdown
Reboot
Reboot to Computer Setup Utility.

If pressed Boot Fall back boot loader (partition System) goes to Windows and If pressed to Boot vmlinux (Parathion label Easy) booting EasyOS.

If pressed Boot Fall Back Boot Loader (Partition Label Easy) it goes to Refind and listing new Menu page like

EASYOS BOOT MENU
Boot EasyOS 2.7.3. (partition Easy)
Boot Antix Linux (Partition Antix)
Shutdown
Reboot

Why Antix Linux not listing first instance upon booting?. May be due to windows efi effect. Any other trick.

I am surprised that Windows, in doing a self-check, doesn't throw a tizzy-fit seeing it's BOOTMGFW.EFI replaced.

I haven't replied to ramachandra yet, but it looks like the first menu is because BOOTX64.EFI, which is actually refind, cannot find a 'refind.conf' file. That would also need to be copied, and edited to show the Windows boot option.

That 'bcdedit' in the first link, looks good.

User avatar
BarryK
Posts: 2169
Joined: Tue Dec 24, 2019 1:04 pm
Has thanked: 93 times
Been thanked: 514 times

Re: NTFS driver for hole-punching a Save file

Post by BarryK »

I have implemented the save-file:

https://bkhome.org/news/202105/easyos-n ... -file.html

But, does it bring anything useful to the table, other than now being able to run on an ntfs partition?

There is one more thing: if the working partition is any filesystem, the ext4 f.s. in easysave.ext4 has encryption capability enabled. Up until now, if the working partition is ext4, have had to use tune2fs to set the "encrypt" flag, so as to be able to encrypt folders and files. Ditto for f2fs. That requirement is now removed.

I was contemplating the init script only choosing to create a save-file if the underlying f.s. is non-Linux, but the above point is probably enough to justify having a save-file in every case.

Unless some other problem emerges with the sparse save-file.

User avatar
foxpup
Posts: 186
Joined: Fri Jul 24, 2020 1:23 pm
Location: Europe near the Northsea
Has thanked: 75 times
Been thanked: 32 times

Re: NTFS driver for hole-punching a Save file

Post by foxpup »

BarryK wrote: Mon May 24, 2021 1:24 am

I am surprised that Windows, in doing a self-check, doesn't throw a tizzy-fit seeing it's BOOTMGFW.EFI replaced.

May happen when windows updates.

williwaw
Posts: 1497
Joined: Tue Jul 14, 2020 11:24 pm
Has thanked: 136 times
Been thanked: 262 times

Re: NTFS driver for hole-punching a Save file

Post by williwaw »

From https://bkhome.org/news/202106/paragon- ... ssues.html

So, holding back on this one. Will probably leave the ntfs3 patch out of the next kernel compile. Will wait until/if it merges in the kernel.

Would testing a savefile on ntfs with 2.8.1 be prudent, or is hole punching still a work in progress?

User avatar
BarryK
Posts: 2169
Joined: Tue Dec 24, 2019 1:04 pm
Has thanked: 93 times
Been thanked: 514 times

Re: NTFS driver for hole-punching a Save file

Post by BarryK »

williwaw wrote: Sat Jun 12, 2021 7:01 am

From https://bkhome.org/news/202106/paragon- ... ssues.html

So, holding back on this one. Will probably leave the ntfs3 patch out of the next kernel compile. Will wait until/if it merges in the kernel.

Would testing a savefile on ntfs with 2.8.1 be prudent, or is hole punching still a work in progress?

I have abandoned the "save file" idea.

Was very disappointed with the performance hit.

Then thought, well, could still do it when install to a ntfs partition and on a fast drive. But then found out that the Paragon ntfs3 driver is flakey.

je55eah
Posts: 183
Joined: Mon Jul 26, 2021 5:27 pm
Has thanked: 30 times
Been thanked: 5 times

Re: NTFS driver for hole-punching a Save file

Post by je55eah »

I hope there is still a way to do this. It's not a deal breaker, but the option of running on NTFS with save files is the kind of thing that makes Easy and Puppy stand out from other distros.

The windows bootloader can boot from vhd files. vhdx as well, I think. Would it be possible to target that bootloader and distribute easy as a vhdx with differencing layers?

I have been reading up on the possibility of doing the same thing on linux. It looks like qcow2 can be mounted rw with nbd. Then it would be like booting from a mounted network file system. I haven't tested it.

I don't know yet about the vdi or vmdk mounts on linux, but I read that Linux cannot work with vhdx files effectively as the host.

If I understand correctly, Easy would see ext4 or whatever if that's how the vhdx was formatted and the driver in the bootloader would handle the interop.

https://devblogs.microsoft.com/setup/bo ... hard-disk/

https://techcommunity.microsoft.com/t5/ ... a-p/706610
https://unix.stackexchange.com/question ... t-from-vhd
https://github.com/lyshie/vhd-boot-dispatch

https://morgansimonsen.com/2012/05/09/w ... irtualbox/
https://bkhome.org/news/202105/easyos-n ... -file.html

Post Reply

Return to “EasyOS”