|
From: SourceForge.net <no...@so...> - 2005-01-19 18:44:07
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=2948235 By: nobody Thanks for your quick response, its good to know someone's listening. :) I don't mean to create a different boot sector but a util to be included in ntfsprogs called ntfsboot that would be run in userland that would: - accept a file/partition as an argument to work on - do some sanity checks, is this really a ntfs partition? - correct anything else that would need to be corrected - calculate "Hidden Sectors" and write it to the ntfs bootsector [example] ntfsboot /dev/hda2 or to conform to ntfsinfo's argument syntax ntfsboot -d /dev/hda2 I would not go so far though as to change things like BOOT.INI that seems out of the scope of ntfsboot. ntfsboot would simply fix the fs/bootsector. Fixing the BOOT.INI would be the problem of the user cloning the fs and with NTFS write support this wouldn't be hard. Especially since unless you are adding items to BOOT.INI you are only changing the device/partition numbers stored in it and not actuall changing the file size. I suggested it as a seperate app then ntfsclone can stay true to its goal of creating exact copies of ntfs systems. However further down the development line the code inside ntfsboot could be moved into a library and called by ntfsboot or by ntfsclone or for that matter mkntfs. In the case of ntfsclone its original functionality could be maintained but a --fix-boot option added to the command line would do exactly that... Fixboot would then become more of a wrapper to a function that actually does the work. [example] ntfsclone --restore-image --fix-boot -O /dev/hda2 myntfs.img -Alan Evans aevans(at)cadprod.com ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44085 |
