Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

47 lines
2.0 KiB

  1. These are a collection of notes that should be updated in the NTFS Design
  2. Specification. These do not include many changes which will be obvious
  3. from a pass through ntfs.h - which will be a necessary activity for the
  4. next spec update.
  5. File Number changed to File Reference, to denote that its use can
  6. become invalid (sequence number incremented).
  7. The second copy of the log is not needed, but a second copy of the MFT
  8. is, which just has the same first three file records: MFT, MFT2 and LOG.
  9. Add a discussion of the Boot Sector / Boot file, and a figure to show
  10. dual boot records and dual MFTs.
  11. Forget the security on attributes, just use READ_ATTRIBUTE, WRITE_ATTRIBUTE
  12. privilege on the file.
  13. The boot file is strictly a matter between Format, bootstrap, and the Mount
  14. code. Where it goes and what its contents are will be system-specific.
  15. For NT:
  16. There will be one boot record at sector 0, and one on the last
  17. sector of the volume. Each boot record will contain the cluster size
  18. and the starting LCN for the Master File, and the Master File 2.
  19. As a suggestion, Format on NT should start the MFT at LCN = 1 on
  20. the disk, and MFT2 should start three file record segments before the
  21. other boot record. MFT2 contains mirrored copies of the first file
  22. record segment for the MFT, MFT2, and the Log file. The boot file
  23. on NT just contains these two boot records.
  24. DOS may choose to actually have a bootstrap following the first
  25. boot record in the boot file, and it could just be the first N
  26. clusters of the disk.
  27. "Ideas by Butzi":
  28. Disks should schedule reads ahead of writes
  29. Have some way to detect temporary files (file attribute
  30. and/or directory attribute), and never write their data
  31. (or update valid data length). This would be like putting
  32. \temp on the RAM disk on OS/2.
  33. make writes on close a dynamic option?