@@ -57,7 +57,7 @@ Features
57
57
* Very trivial module loading support (** no** automatic dependency
58
58
resolution).
59
59
60
- When compiled on a x86_64 system with the default ` -Og ` compiler flags,
60
+ When compiled on an x86_64 system with the default ` -Og ` compiler flags,
61
61
statically linked against dietlibc 0.33~ cvs20120325-6, the binary
62
62
stripped and the resulting initramfs (without any modules added)
63
63
compressed with ` gzip -9 ` , the images produced are between 9 kiB and
@@ -328,15 +328,15 @@ many buffers that the amount of RAM used is a concern just yet, even
328
328
for small systems), so that no real flexibility is sacrificed.
329
329
330
330
None of this is extremely performance-critical (it is going to be quite
331
- fast regardless, because very little is done compared to a even just
331
+ fast regardless, because very little is done compared to even just
332
332
running a shell), so no algorithm is optimized for speed directly. For
333
333
example, the mount option parser table is somewhat compressed to reduce
334
334
the code size (negation and recursive variants of mount options are not
335
335
repeated), to the point where further reduction would likely sacrifice
336
336
the readability of the code. Execution speed is achieved by doing very
337
337
little, not by micro-optimizing algorithms.
338
338
339
- Some times it is necessary to reimplement certain libc functios because
339
+ Sometimes it is necessary to reimplement certain libc functions because
340
340
using the libc variants increase the image size too much. For example,
341
341
using ` inet_ntoa ` and ` inet_aton ` (to convert between ASCII to binary
342
342
representations of IP addresses) from the musl C library will cause
@@ -371,7 +371,7 @@ be interesting regardless:
371
371
file systems.
372
372
373
373
Note that the goal is to keep the ` initrd.img ` size smaller than 16 KiB
374
- on all plattforms , so a cutoff of 15 KiB is used on x86_64, to leave
374
+ on all platforms , so a cutoff of 15 KiB is used on x86_64, to leave
375
375
room for different assembly code sizes etc., at least when used in a
376
376
minimal configuration. Therefore, some features (such as ` UUID= ` and
377
377
NFSv4 support) are compile-time optional.
0 commit comments