<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://www.evillabs.net/index.php?action=history&amp;feed=atom&amp;title=AROS_Arix%2FFilesystem</id>
	<title>AROS Arix/Filesystem - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://www.evillabs.net/index.php?action=history&amp;feed=atom&amp;title=AROS_Arix%2FFilesystem"/>
	<link rel="alternate" type="text/html" href="http://www.evillabs.net/index.php?title=AROS_Arix/Filesystem&amp;action=history"/>
	<updated>2026-05-12T12:02:26Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>http://www.evillabs.net/index.php?title=AROS_Arix/Filesystem&amp;diff=574&amp;oldid=prev</id>
		<title>Ezrec: /* S1: ata.device-like shim over Linux kernel and AROS file systems */</title>
		<link rel="alternate" type="text/html" href="http://www.evillabs.net/index.php?title=AROS_Arix/Filesystem&amp;diff=574&amp;oldid=prev"/>
		<updated>2012-09-25T15:58:42Z</updated>

		<summary type="html">&lt;p&gt;&lt;span dir=&quot;auto&quot;&gt;&lt;span class=&quot;autocomment&quot;&gt;S1: ata.device-like shim over Linux kernel and AROS file systems&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;table style=&quot;background-color: #fff; color: #202122;&quot; data-mw=&quot;interface&quot;&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;tr class=&quot;diff-title&quot; lang=&quot;en&quot;&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;← Older revision&lt;/td&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;Revision as of 15:58, 25 September 2012&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot; id=&quot;mw-diff-left-l29&quot;&gt;Line 29:&lt;/td&gt;
&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot;&gt;Line 29:&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;* What will Linux kernel do in such setup when someone inserts a pen driver? Will this count as disk as will be handled by ata.device-like shim or will such action be invisible to AROS?&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;* What will Linux kernel do in such setup when someone inserts a pen driver? Will this count as disk as will be handled by ata.device-like shim or will such action be invisible to AROS?&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-side-deleted&quot;&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-side-deleted&quot;&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;==== S1.a: linuxfs-handler ====&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-side-deleted&quot;&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-side-deleted&quot;&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;* C:Mount supplies the Linux FS type to use (ext3, jffs, etc) via the CONTROL parameter.&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-side-deleted&quot;&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;* Handler translates the DOS device (ie DH1:) to a mount of the desired filesystem using the &#039;-o loop,offset=XXXX /dev/sda&#039; method (Linux doesn&#039;t need to know about partitions)&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-side-deleted&quot;&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;* Handler translates DOS packets into Linux read/write/etc syscalls to the Linux filesystem&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;=== S2: &amp;quot;insert&amp;quot; partitions into AROS when Linux kernel detects them ===&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;=== S2: &amp;quot;insert&amp;quot; partitions into AROS when Linux kernel detects them ===&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/table&gt;</summary>
		<author><name>Ezrec</name></author>
	</entry>
	<entry>
		<id>http://www.evillabs.net/index.php?title=AROS_Arix/Filesystem&amp;diff=573&amp;oldid=prev</id>
		<title>Ezrec: /* S2: &quot;insert&quot; partitions into AROS when Linux kernel detects them */</title>
		<link rel="alternate" type="text/html" href="http://www.evillabs.net/index.php?title=AROS_Arix/Filesystem&amp;diff=573&amp;oldid=prev"/>
		<updated>2012-09-25T15:50:49Z</updated>

		<summary type="html">&lt;p&gt;&lt;span dir=&quot;auto&quot;&gt;&lt;span class=&quot;autocomment&quot;&gt;S2: &amp;quot;insert&amp;quot; partitions into AROS when Linux kernel detects them&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Requirements ==&lt;br /&gt;
&lt;br /&gt;
* (A) It should be possible to install AROS on hdd/usb using InstallAROS in exactly the same manner as on pc-i386&lt;br /&gt;
* (B) It should be possible to use all software that manipulates disk structure (i.e. HDToolBox)&lt;br /&gt;
* (C) It should be possible to reuse as much as possible the existing AROS code base&lt;br /&gt;
* (D) It should be possible to utilize Linux ATA/SATA support to support all Motherboards that Linux supports&lt;br /&gt;
* (E) It should be possible to utilize Linux file system support to support partitions with file systems that Linux supports&lt;br /&gt;
* (F) It should be possible for newly inserted medium (CDROM, USB, etc) to be automatically visible in AROS without user interaction&lt;br /&gt;
&lt;br /&gt;
Are A,B,C in oposition to D,E?&lt;br /&gt;
&lt;br /&gt;
== Solutions ==&lt;br /&gt;
&lt;br /&gt;
=== S1: ata.device-like shim over Linux kernel and AROS file systems ===&lt;br /&gt;
&lt;br /&gt;
Description:&lt;br /&gt;
&lt;br /&gt;
ata.device-like shim communicated with /dev/ node that exposes functions needed by ata.device interface. Most probably it requires writing some linux-side code for exposing ata functions. Linux kernel needs also to be modified to disable &amp;quot;partition detection&amp;quot; after the initial mounting of AROS partition, because we don&amp;#039;t want Linux kernel to handle partition at the same time as AROS would be doing it.&lt;br /&gt;
&lt;br /&gt;
Advantages:&lt;br /&gt;
* It it known what needs to be implemented&lt;br /&gt;
* Integration at low level allows for A, B, C and D&lt;br /&gt;
&lt;br /&gt;
Disadvantages&lt;br /&gt;
* Not possible to implement E&lt;br /&gt;
* Modifications needs to Linux kernel&lt;br /&gt;
&lt;br /&gt;
Questions:&lt;br /&gt;
&lt;br /&gt;
* What will Linux kernel do in such setup when someone inserts a pen driver? Will this count as disk as will be handled by ata.device-like shim or will such action be invisible to AROS?&lt;br /&gt;
&lt;br /&gt;
=== S2: &amp;quot;insert&amp;quot; partitions into AROS when Linux kernel detects them ===&lt;br /&gt;
&lt;br /&gt;
Description:&lt;br /&gt;
&lt;br /&gt;
We let Linux detect new partition and send UDEV event about it. AROS captures that event and access the partition using emul-handler file system.&lt;br /&gt;
&lt;br /&gt;
Advantages:&lt;br /&gt;
* Integration at medium level allows D and E&lt;br /&gt;
* AROS sees all partitions (HDD, CDROM, USB, Network?) with single approach&lt;br /&gt;
&lt;br /&gt;
Disadvantages:&lt;br /&gt;
* Solution does not allow A&lt;br /&gt;
* Not yet known how to implement&lt;br /&gt;
&lt;br /&gt;
Questions:&lt;br /&gt;
* We don&amp;#039;t want those partition to be mounted in the initrd file system. In that case is it possible for emul-handler to work at all?&lt;br /&gt;
&lt;br /&gt;
=== S3: ata.device-like shim over Linux kernel and AROS file systems, but AROS &amp;quot;returning&amp;quot; control to Linux if no native systems found ===&lt;br /&gt;
&lt;br /&gt;
Description:&lt;br /&gt;
&lt;br /&gt;
Solution S1 with fallback. If AROS does not know how to handle a certain file system, a signal is sent to Linux kernel to handle it. Then UDEV event is captured by AROS and the partition is mounted using emul-handler.&lt;br /&gt;
&lt;br /&gt;
Advantages:&lt;br /&gt;
* Allows requirement E for reading/writting&lt;br /&gt;
&lt;br /&gt;
Disadvantages:&lt;br /&gt;
* Not known how to implement&lt;br /&gt;
* Modifications needed to Linux kernel&lt;/div&gt;</summary>
		<author><name>Ezrec</name></author>
	</entry>
</feed>