<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>On 30/03/2020 15:35, Joel Sherrill wrote:<br>
</p>
<blockquote type="cite"
cite="mid:CAF9ehCVV+HFqh-OJQ+N1MjDPowoObS+w203VEMQNTWC-W1k_1g@mail.gmail.com">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">What
about the<br>
<br>
CONFIGURE_FILESYSTEM_ENTRY_DEVFS<br>
CONFIGURE_FILESYSTEM_ENTRY_DOSFS<br>
CONFIGURE_FILESYSTEM_ENTRY_FTPFS<br>
CONFIGURE_FILESYSTEM_ENTRY_IMFS<br>
CONFIGURE_FILESYSTEM_ENTRY_JFFS2<br>
CONFIGURE_FILESYSTEM_ENTRY_NFS<br>
CONFIGURE_FILESYSTEM_ENTRY_RFS<br>
CONFIGURE_FILESYSTEM_ENTRY_TFTPFS<br>
<br>
configuration options? Is this really something a user should be
able to <br>
define?<br>
</blockquote>
<div><br>
</div>
<div>Chris will likely chime in later but I believe these are
needed so that </div>
<div>filesystem type is listed in the set of mountable
filesystems. The mount</div>
<div>command depends on those settings. <br>
</div>
</blockquote>
<p>Yes, it depends on the settings, but the
CONFIGURE_FILESYSTEM_ENTRY_* options give you an extra level of
control. For example, you can enable the RFS with:</p>
<p>#define CONFIGURE_FILESYSTEM_ENTRY_RFS</p>
<p>Optionally, you can fine tune the entry:</p>
<p>#if defined(CONFIGURE_FILESYSTEM_RFS) \<br>
&& !defined(CONFIGURE_FILESYSTEM_ENTRY_RFS)<br>
#define CONFIGURE_FILESYSTEM_ENTRY_RFS \<br>
{ RTEMS_FILESYSTEM_TYPE_RFS, rtems_rfs_rtems_initialise }<br>
#endif</p>
<p>I am not sure if this fine tuning is really necessary.<br>
</p>
</body>
</html>