> > Can it read ext4 formatted disks? > > > > If so, then I can proceed to check it out, otherwise > it is useless for Fedora 11 users that may want to view > their files in Window$ > > > > Regards, > > > > Antonio > > The FAQ [1] mentions support for ext2 and ext3 only. I > tested the > utility and it works as advertised. > With ext4 being so new, it would be quite a lot to ask ;-) > > What's important to know is that *there is* a way. For a > friend of > mine this is truly a lifesaver for gathering and reading > data on > the fly... literally. > > [1] http://www.fs-driver.org/faq.html > > -- Still thanks for sharing this. The reason I write back is that I have a friend that tells me that if a utility can't do it all, then it is no GOOD. I have to kind of agree with him. He is a window$ user and I wanted to share some files with him, but the usb was formatted in ext3 filesystem and Window$ wanted to format it :(, but with this program it is a head start. It is like LiveCD's there are very good ones out there, but they can't read EXT4 filesystem, so to my friend they are no GOOD. What features are *not* supported? Inodes that are larger than 128 bytes are not supported. Access rights are not maintained. All users can access all the directories and files of an Ext2 volume. If a new file or directory is created, it inherits all the permissions, the GID and the UID from the directory where it has been created. There is one exception to this rule: a file (but not a directory) the driver has created always has cleared "x" permissions, it inherits the "r" and the "w" permissions only. See also section "What limitations arise from not maintaining access rights?". The driver does not allow accessing special files at Ext2 volumes, the access will be always denied. (Special files are sockets, soft links, block devices, character devices and pipes.) Alternate 8.3-DOS names are not supported (just because there is no place to store them in an Ext2 file system). This can prevent legacy DOS applications, executed by the NTVDM of Windows, from accessing some files or directories. Currently the driver does not implement defragging support. So defragmentation applications will neither show fragmentation information nor defragment any Ext2 volume. This software does not achieve booting a Windows operating system from an Ext2 volume. LVM volumes are not supported, so it is not possible to access them.^[1] Regards, Antonio [1] This one is a big dissapointment because by default Fedora installs to LVM partions and this powerful utility can't even see them which is is a pita :( But nonetheless thank you for sharing this. Some users out there do appreciate it. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
