hi.

if you save a file in a disket or CD and open that file in another PC, the files inside will have still the same name. But if you open the file in a HexEditor you cant find its name, or extension there... so where is that stored?

Somewhere in the filesystem (ISO9660/CDFS, NTFS, FAT, UFS etc.) structures (root directory entry, inode, etc.)?

When you "open" a file (using any kind of editor), you're reading the "data area" of that file. The filesystem structures are only available to the operating system or to you if you have enough privileges and you open the disk as a raw device using an appropriate application.

Teehee
Dude!!! I saw like that in my dream yesterday lol
Sorry for off-topic.

it is a secret, not because it is hard to understand, but because it is hard for them to broadcast the docs for free.

Stop smoking crack, edfed.

Information on the common filesystems is readily available, with the biggest problem being NTFS... but the opensource linux drivers for it are pretty stable by now. Read the source, Luke!

PS: if you can't directly find filenames in a disk image, it's probably because of unicode (NTFS) or the wacky way FAT stores long filenames.

I think he was being sarcastic, but that's just me...


Well, not really. I've always found www.ntfs.com to be quite informative.
And these might help too:
http://www.reddragonfly.org/ntfs/concepts/file.html
http://www.cse.scu.edu/~tschwarz/COEN152_06/Lectures/NTFS.html

I just wish there was better OS support for viewing and manipulating the NTFS alternate data streams. Some apps like to use them to hide stuff. Really annoying.

[quote="ManOfSteel"] It's unofficial documents, and how up-to-date are they? One thing is the on-disk format, another is all the code you need to implement to deal properly with the logical structure of the fs.

In the first case, unofficial documents made by a 13-year-old company that sells data recovery software. It's surely better than nothing IMO.


Teehee is just asking for "educative information" and is not implementing a filesystem driver (or at least didn't say so).

I've used this information more than once for "educative" purposes but I don't trust it blindly and I actually don't trust *any* of the existing drivers. When I need to read/write from/to an NTFS partition, I only trust the official Microsoft driver included in Windows. Otherwise, I always mount it as read-only using FreeBSD's native driver.