NTFS read/write support

[ecomoney]

At Last!!!!

http://sourceforge.net/mailarchive/forum.php?thread_id=23836054&forum_id=2697

Looks like there is full read/write support for ntfs volumes!!!! This is gonna see a lot of XP machines liberated

[woodeye18]

I use Puppy on my mission critical Workstation that has an NTFS partition on it by booting from CD or USB. I have always felt a certain degree of safety that my Windows HDD won't be damaged, because of the NO WRITE to NTFS rule in Puppy linux.

When I read about the auto mount abilities for the new NTFS feature I was wondering if there is a way to semi permanently disable the NTFS write capability in Puppy future editions (I know I will want to turn it on and use it at some point).

I am excited about the other uses for the NTFS feature, but with regard to this PC, its kind of a "Stop me before I kill again" type thing. I hate bricking my Hardware.

[kirk]

It looks like you could just edit Barry's mount script and change where ntfs-3g is used to mount-FULL. I've compiled ntfs-3g, seems to work well.

I hope Barry enables this for boot up. At the initial shutdown, when asked where you want to put the storage file, could put some kind of warning message if we're not completely sure about NTFS-3g's reliablity. Maybe even a frugal install to a NTFS?

I think many more people would try Puppy if they didn't have to repartition.

[ecomoney]

Thanks kirk for being Brave and testing this!

Mostly when going around installing puppy for people I am called out to "Bricked" xp machines. Im still on puppy 1.09CE and I carry a standard "windows refugee" install on my 1gb mp3 player and a stock of burned 1.09CE disks in my car (rather good as the mp3 player also gives me music while I drive between jobs...mines a happy life!!!).

Usually I boot puppy into memory and transfer the pup001 file from my MP3 player to the patients Hard Disk, reboot, rm etc/mousedevice, lick my finger and chalk one up in the air . The only problem would be if the disk is ntfs which means that the xp install has to be at least on its last gasp to write the pup001 file to hard disk.

Would be great if you or someone else would make a dotpup for this that I could download from the web, install and use to write the pup001 file. This would also be useful for adding backwards compatibility for NTFS writing for previous pups until it becomes tested enough to one day be part of the main distro (I heard Barry had been doing some work on this as part of his blog). Until then obviously going to the web would have an "at your own risk, not the puppy teams responsibility" notice on the download page.

[Hacao]

WOW !

It's work !

Thanks,

[BarryK]

Yes, I'm planning to have full NTFS write capability for Puppy 2.02.
-- well, there will have to be a beta release to test it, make sure it doesn't
destroy anyone's NTFS partitions!

So, I'm hoping that at first shutdown people will be able to create a pup_save.3fs
file on a NTFS partition, just like any other.

[kelewax]

Yes, I'm planning to have full NTFS write capability for Puppy 2.02.

This is good news. I am waiting.

[Hacao]

Hi !

You can try ntfs-3g here.

Extract it to /usr/local

Usage:

Code: Select all

ntfs-3g /dev/hda1 /mnt/windows

Now, you can delete file in NTFS (Using ROX)

Thanks,

[muggins]

hacao,

is this ntfs download applicable to all versions, or only the 2xx series?

ta,
muggins

[Hacao]

hacao,

is this ntfs download applicable to all versions, or only the 2xx series?

ta,
muggins

I just testing in 2xx series, Very well !

Not testing yet in 1xx series. You can try it in 1xx series

Thanks,

[ecomoney]

In 1.09 (running in RAM after a hard disk overheat) I used it to try and access a donated NTFS Drive that Im planning to wipe anyway. Typed

Code: Select all

ntfs-3g /dev/hdb1

Got the Error:-

Code: Select all

ntfs-3g: Error while loading shared libraries: libfuse.so.2: cannot open shared object file: No such file or directory

Note the linux-ntfs guy is going away - from the above link:-

Please note that I'm leaving for an over 5,000 km long Far North and Arctic
Ocean advanture on Sunday morning (European time) and won't be able to read
and answer emails for almost a month

Bet he needs a holday after cracking NTFS!!! Well done that man.

[BarryK]

If you're having trouble using ntfs-3g, don't worry, as 2.02beta is expected soon. I'm planning to upload it, baring any unforseen hiccups, by Thursday 27th July.

I got my 'pmount' utility to work nicely with it, but Jesse will have to fix MUT.
I have modified 'mount' and 'umount' so they will seamlessly mount and unmount
a ntfs partition using ntfs-3g and fusermount, however when the partition is
mounted, 'df' and 'mount' (the actual Busybox or full 'mount' executable, executed
without any parameters) return:

df
/dev/fuse ...rest of line normal...

mount
/dev/fuse on /mnt/hda1 type fuse (rw)

MUT just reports the partition is unmounted.

Of course, if we *always* mount /dev/hda1 on /mnt/hda1, then it will be
easy to look at the mount point and determine the device. (Which is one
reason I suggested to Jesse let's ignore /etc/fstab)

[jus407]

Thats great news i cannot wait!

[Jesse]

Hi,

I did a little plugging away and discovered how to work ntfs-3g, so now MUT supports using this filesystem (full read/write NTFS support) Yay!

Also fixed up the initial unnecessary pause when MUT starts up, finally figured that trickly little one out.

Oh, and you can tell exactly which dev node is mounted to an ntfs-3g filesystem with this little gem (used in MUT):

Code: Select all

 ps -e | grep -o ntfs-3g.* | grep dev  | cut -f 2,3 -d ' '

Jesse

[kirk]

Jesse,

Tried the new Mut. Works good for me!

Mounted NTFS partitions, created and deleted files.

Thanks!

[Jesse]

Coolies!
This means it'll probably be in the next Puppy2.02.

[Jesse]

Hi,

MUT updated again. Taking into account some of the possibilities that the ntfs-3g could not be correctly identified.

Jesse