Skip to content

Commit 8d2cbee

Browse files
clarify disk image stuff
1 parent 685ab5f commit 8d2cbee

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

filesystems-distributed-ufs/README.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,10 @@ your file server will link with it and call its various routines.
2424

2525
## On-Disk File System: A Basic Unix File System
2626

27-
Your on-disk file system structures should roughly follow that of the
27+
The on-disk file system structures follow that of the
2828
very simple file system discussed
2929
[here](https://pages.cs.wisc.edu/~remzi/OSTEP/file-implementation.pdf). On-disk,
30-
the structures should be as follows:
30+
the structures are as follows:
3131
- A single block (4KB) super block
3232
- An inode bitmap (can be one or more 4KB blocks, depending on the number of inodes)
3333
- A data bitmap (can be one or more 4KB blocks, depending on the number of data blocks)
@@ -60,7 +60,9 @@ It is pretty self-explanatory and can be found
6060
When booting off of an existing image, your server should read in the
6161
superblock, bitmaps, and inode table, and keep in-memory versions of
6262
these. When writing to the image, you should update these on-disk
63-
structures accordingly.
63+
structures accordingly.
64+
65+
Importantly, you cannot change the file-system on-disk format.
6466

6567
## Client library
6668

0 commit comments

Comments
 (0)