Orange Pi5 kernel

^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   1) .. SPDX-License-Identifier: GPL-2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   2) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   3) =============================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   4) Overview of Amiga Filesystems
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   5) =============================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   6) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   7) Not all varieties of the Amiga filesystems are supported for reading and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   8) writing. The Amiga currently knows six different filesystems:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   9) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  10) ==============	===============================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  11) DOS\0		The old or original filesystem, not really suited for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  12) 		hard disks and normally not used on them, either.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  13) 		Supported read/write.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  14) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  15) DOS\1		The original Fast File System. Supported read/write.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  16) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  17) DOS\2		The old "international" filesystem. International means that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  18) 		a bug has been fixed so that accented ("international") letters
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  19) 		in file names are case-insensitive, as they ought to be.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  20) 		Supported read/write.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  21) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  22) DOS\3		The "international" Fast File System.  Supported read/write.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  23) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  24) DOS\4		The original filesystem with directory cache. The directory
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  25) 		cache speeds up directory accesses on floppies considerably,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  26) 		but slows down file creation/deletion. Doesn't make much
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  27) 		sense on hard disks. Supported read only.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  28) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  29) DOS\5		The Fast File System with directory cache. Supported read only.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  30) ==============	===============================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  31) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  32) All of the above filesystems allow block sizes from 512 to 32K bytes.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  33) Supported block sizes are: 512, 1024, 2048 and 4096 bytes. Larger blocks
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  34) speed up almost everything at the expense of wasted disk space. The speed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  35) gain above 4K seems not really worth the price, so you don't lose too
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  36) much here, either.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  37) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  38) The muFS (multi user File System) equivalents of the above file systems
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  39) are supported, too.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  40) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  41) Mount options for the AFFS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  42) ==========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  43) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  44) protect
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  45) 		If this option is set, the protection bits cannot be altered.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  46) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  47) setuid[=uid]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  48) 		This sets the owner of all files and directories in the file
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  49) 		system to uid or the uid of the current user, respectively.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  50) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  51) setgid[=gid]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  52) 		Same as above, but for gid.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  53) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  54) mode=mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  55) 		Sets the mode flags to the given (octal) value, regardless
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  56) 		of the original permissions. Directories will get an x
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  57) 		permission if the corresponding r bit is set.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  58) 		This is useful since most of the plain AmigaOS files
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  59) 		will map to 600.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  60) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  61) nofilenametruncate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  62) 		The file system will return an error when filename exceeds
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  63) 		standard maximum filename length (30 characters).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  64) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  65) reserved=num
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  66) 		Sets the number of reserved blocks at the start of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  67) 		partition to num. You should never need this option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  68) 		Default is 2.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  69) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  70) root=block
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  71) 		Sets the block number of the root block. This should never
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  72) 		be necessary.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  73) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  74) bs=blksize
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  75) 		Sets the blocksize to blksize. Valid block sizes are 512,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  76) 		1024, 2048 and 4096. Like the root option, this should
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  77) 		never be necessary, as the affs can figure it out itself.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  78) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  79) quiet
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  80) 		The file system will not return an error for disallowed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  81) 		mode changes.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  82) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  83) verbose
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  84) 		The volume name, file system type and block size will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  85) 		be written to the syslog when the filesystem is mounted.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  86) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  87) mufs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  88) 		The filesystem is really a muFS, also it doesn't
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  89) 		identify itself as one. This option is necessary if
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  90) 		the filesystem wasn't formatted as muFS, but is used
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  91) 		as one.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  92) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  93) prefix=path
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  94) 		Path will be prefixed to every absolute path name of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  95) 		symbolic links on an AFFS partition. Default = "/".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  96) 		(See below.)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  97) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  98) volume=name
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  99) 		When symbolic links with an absolute path are created
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) 		on an AFFS partition, name will be prepended as the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) 		volume name. Default = "" (empty string).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) 		(See below.)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) Handling of the Users/Groups and protection flags
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) =================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) Amiga -> Linux:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) The Amiga protection flags RWEDRWEDHSPARWED are handled as follows:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111)   - R maps to r for user, group and others. On directories, R implies x.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113)   - W maps to w.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115)   - E maps to x.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117)   - D is ignored.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119)   - H, S and P are always retained and ignored under Linux.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121)   - A is cleared when a file is written to.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) User id and group id will be used unless set[gu]id are given as mount
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) options. Since most of the Amiga file systems are single user systems
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) they will be owned by root. The root directory (the mount point) of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) Amiga filesystem will be owned by the user who actually mounts the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) filesystem (the root directory doesn't have uid/gid fields).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) Linux -> Amiga:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) The Linux rwxrwxrwx file mode is handled as follows:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133)   - r permission will allow R for user, group and others.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135)   - w permission will allow W for user, group and others.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137)   - x permission of the user will allow E for plain files.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139)   - D will be allowed for user, group and others.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141)   - All other flags (suid, sgid, ...) are ignored and will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142)     not be retained.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) Newly created files and directories will get the user and group ID
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) of the current user and a mode according to the umask.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) Symbolic links
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) ==============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) Although the Amiga and Linux file systems resemble each other, there
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) are some, not always subtle, differences. One of them becomes apparent
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) with symbolic links. While Linux has a file system with exactly one
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) root directory, the Amiga has a separate root directory for each
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) file system (for example, partition, floppy disk, ...). With the Amiga,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) these entities are called "volumes". They have symbolic names which
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) can be used to access them. Thus, symbolic links can point to a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) different volume. AFFS turns the volume name into a directory name
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) and prepends the prefix path (see prefix option) to it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) Example:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) You mount all your Amiga partitions under /amiga/<volume> (where
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) <volume> is the name of the volume), and you give the option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) "prefix=/amiga/" when mounting all your AFFS partitions. (They
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) might be "User", "WB" and "Graphics", the mount points /amiga/User,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) /amiga/WB and /amiga/Graphics). A symbolic link referring to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) "User:sc/include/dos/dos.h" will be followed to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) "/amiga/User/sc/include/dos/dos.h".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) Examples
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) Command line::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174)     mount  Archive/Amiga/Workbench3.1.adf /mnt -t affs -o loop,verbose
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175)     mount  /dev/sda3 /Amiga -t affs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) /etc/fstab entry::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179)     /dev/sdb5	/amiga/Workbench    affs    noauto,user,exec,verbose 0 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) IMPORTANT NOTE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) ==============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) If you boot Windows 95 (don't know about 3.x, 98 and NT) while you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) have an Amiga harddisk connected to your PC, it will overwrite
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) the bytes 0x00dc..0x00df of block 0 with garbage, thus invalidating
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) the Rigid Disk Block. Sheer luck has it that this is an unused
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) area of the RDB, so only the checksum doesn't match anymore.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) Linux will ignore this garbage and recognize the RDB anyway, but
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) before you connect that drive to your Amiga again, you must
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) restore or repair your RDB. So please do make a backup copy of it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) before booting Windows!
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) If the damage is already done, the following should fix the RDB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) (where <disk> is the device name).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) DO AT YOUR OWN RISK::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199)   dd if=/dev/<disk> of=rdb.tmp count=1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200)   cp rdb.tmp rdb.fixed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201)   dd if=/dev/zero of=rdb.fixed bs=1 seek=220 count=4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202)   dd if=rdb.fixed of=/dev/<disk>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) Bugs, Restrictions, Caveats
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) ===========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) Quite a few things may not work as advertised. Not everything is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) tested, though several hundred MB have been read and written using
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) this fs. For a most up-to-date list of bugs please consult
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) fs/affs/Changes.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) By default, filenames are truncated to 30 characters without warning.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) 'nofilenametruncate' mount option can change that behavior.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) Case is ignored by the affs in filename matching, but Linux shells
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) do care about the case. Example (with /wb being an affs mounted fs)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218)     rm /wb/WRONGCASE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) will remove /mnt/wrongcase, but::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222)     rm /wb/WR*
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) will not since the names are matched by the shell.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) The block allocation is designed for hard disk partitions. If more
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227) than 1 process writes to a (small) diskette, the blocks are allocated
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228) in an ugly way (but the real AFFS doesn't do much better). This
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) is also true when space gets tight.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) You cannot execute programs on an OFS (Old File System), since the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232) program files cannot be memory mapped due to the 488 byte blocks.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) For the same reason you cannot mount an image on such a filesystem
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234) via the loopback device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) The bitmap valid flag in the root block may not be accurate when the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) system crashes while an affs partition is mounted. There's currently
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) no way to fix a garbled filesystem without an Amiga (disk validator)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) or manually (who would do this?). Maybe later.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241) If you mount affs partitions on system startup, you may want to tell
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242) fsck that the fs should not be checked (place a '0' in the sixth field
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243) of /etc/fstab).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) It's not possible to read floppy disks with a normal PC or workstation
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246) due to an incompatibility with the Amiga floppy controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248) If you are interested in an Amiga Emulator for Linux, look at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) http://web.archive.org/web/%2E/http://www.freiburg.linux.de/~uae/