foundry
Foundry OS: the operating system built on the Rustbelt kernel
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 | #!/usr/bin/env python3
"""exfat.py -- read and (minimally) write an exFAT file system in an image
file, without mounting it (mounting needs root or FUSE).
exfat.py IMAGE[@OFFSET] info volume label, cluster size, number of FATs
exfat.py IMAGE[@OFFSET] ls [DIR] list a directory ("/" by default)
exfat.py IMAGE[@OFFSET] cat PATH print a file's bytes to stdout
exfat.py IMAGE[@OFFSET] put DIR copy the files directly in DIR into
the root directory (fresh volume only)
OFFSET is where the file system starts inside IMAGE, in bytes (for a
partition of a whole-disk image), e.g. foundry.img@95420416.
Foundry OS uses it for two things:
* `put`: mkfs.exfat (exfatprogs) can format a volume but not fill it, so
the share partition's README is written with this (`make image`).
* `ls`/`cat`: after `make test` the host reads back what Rustbelt wrote
to the share, independently of the kernel's driver.
fsck.exfat (exfatprogs) checks the result both times.
`put` is deliberately tiny: every file gets one contiguous run of free
clusters with the NoFatChain flag (so the FAT itself is not touched), the
same fixed timestamp, and an entry in the root directory. That is all valid
exFAT, and enough for a few files on a fresh volume. (The kernel's
build/exfat_populate.rs takes the same approach; this is a separate,
independent implementation.)
"""
= 0x10
= 0x20
= 0x02
= 0x01
# 2026-01-01 00:00:00, exFAT/DOS format: year-1980 <<25 | month <<21 | day <<16.
= | |
return & 0xFFFF
, = ,
=
= 1 <<
= <<
= *
= *
=
=
=
=
=
, , = , None,
=
== 0x81:
=
=
== 0x82:
, =
=
=
= 0
# 0xFFFF n = "n identity entries"
+= 2
+= 1
# --- low level -------------------------------------------------------
return + + *
return
return
"""The clusters of a file: consecutive (NoFatChain) or via the FAT."""
return
=
return
, = ,
=
return
= b
return
yield ,
# --- directories -----------------------------------------------------
"""[(name, attrs, first_cluster, size, chained)] of one directory."""
=
, = , 0
=
break
=
=
=
, = ,
, =
= b
=
+= 32 *
+= 32
return
=
=
break
return
return
# --- writing (fresh volumes) -----------------------------------------
return
=
= -
=
, = 0x85, 1 +
= 0
=
=
= 0xC0
= |
=
=
= 0xC1
= 0
=
return
=
= >> & 1
= + 1
=
=
=
=
continue
=
= -
=
|= 1 <<
+=
=
=
+=
=
# PercentInUse (boot sector byte 112) is not covered by the boot checksum.
, , =
=
, = ,
== :
, , , =
== :
, , , =
== :
|