<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic loopback filesystem, or what? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/loopback-filesystem-or-what/m-p/2460744#M14037</link>
    <description>While collecting fstype information for writing a Perl script that should run on different flavours of Unix (i.e. HP-UX, AIX, Solaris, Linux) I stumbled over the fstype lofs in HP-UX's fstab manpage.&lt;BR /&gt;Looking for a more explicit explantion I couldn't find a mkfs_lofs manpage.&lt;BR /&gt;The only somewhat disturbing hint I found is the WARNINGS paragraph in the mount_lofs manpage, "...should only be used by experienced users...blah blah...can be confusing...blah blah".&lt;BR /&gt;Doing occasional backups on CD-R/RW on my Linux box at home using mkisofs and cdrecord, I know you can create an image file before burning, that you can mount as a loopback device as if accessing an already burned CDROM to check that everything has been included.&lt;BR /&gt;Is HP-UX's lofs something similar or am I on a totally wrong track?</description>
    <pubDate>Thu, 02 Nov 2000 11:23:43 GMT</pubDate>
    <dc:creator>Ralph Grothe</dc:creator>
    <dc:date>2000-11-02T11:23:43Z</dc:date>
    <item>
      <title>loopback filesystem, or what?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/loopback-filesystem-or-what/m-p/2460744#M14037</link>
      <description>While collecting fstype information for writing a Perl script that should run on different flavours of Unix (i.e. HP-UX, AIX, Solaris, Linux) I stumbled over the fstype lofs in HP-UX's fstab manpage.&lt;BR /&gt;Looking for a more explicit explantion I couldn't find a mkfs_lofs manpage.&lt;BR /&gt;The only somewhat disturbing hint I found is the WARNINGS paragraph in the mount_lofs manpage, "...should only be used by experienced users...blah blah...can be confusing...blah blah".&lt;BR /&gt;Doing occasional backups on CD-R/RW on my Linux box at home using mkisofs and cdrecord, I know you can create an image file before burning, that you can mount as a loopback device as if accessing an already burned CDROM to check that everything has been included.&lt;BR /&gt;Is HP-UX's lofs something similar or am I on a totally wrong track?</description>
      <pubDate>Thu, 02 Nov 2000 11:23:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/loopback-filesystem-or-what/m-p/2460744#M14037</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2000-11-02T11:23:43Z</dc:date>
    </item>
    <item>
      <title>Re: loopback filesystem, or what?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/loopback-filesystem-or-what/m-p/2460745#M14038</link>
      <description>Hi Ralph,&lt;BR /&gt;&lt;BR /&gt;The following is an extract from the 10.20 Release notes (found in /usr/share/doc):-&lt;BR /&gt;&lt;BR /&gt;LOFS allows mounting an existing directory onto another directory.  &lt;BR /&gt;    The effect is similar to that of a symbolic link, except that the &lt;BR /&gt;    usual mount options are available, and there are no issues with the &lt;BR /&gt;    meaning of "..". When an application does a stat(2) on a LOFS file, &lt;BR /&gt;    the values returned are the same as for the file in its original &lt;BR /&gt;    location, except that the st_fstype field indicates LOFS. In particular, &lt;BR /&gt;    st_dev and st_ino are the same, so that the conventional test for &lt;BR /&gt;    whether two pathnames name the same file (device and inumber match) &lt;BR /&gt;    continues to work.&lt;BR /&gt;&lt;BR /&gt;    Some applications that walk file trees use stat's st_dev to detect the &lt;BR /&gt;    crossing of mount points.  This will not work with LOFS because an &lt;BR /&gt;    LOFS file has the st_dev of its original location.  Code that needs &lt;BR /&gt;    to identify a particular file system (in the sense of a particular &lt;BR /&gt;    mount) should use f_fsid from statfs(2) or statvfs(2).&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;John</description>
      <pubDate>Thu, 02 Nov 2000 12:20:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/loopback-filesystem-or-what/m-p/2460745#M14038</guid>
      <dc:creator>John Palmer</dc:creator>
      <dc:date>2000-11-02T12:20:58Z</dc:date>
    </item>
    <item>
      <title>Re: loopback filesystem, or what?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/loopback-filesystem-or-what/m-p/2460746#M14039</link>
      <description>For lofs see this site:&lt;BR /&gt;&lt;A href="http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90672/B2355-90672_top.html&amp;amp;con=/hpux/onlinedocs/B2355-90672/00/00/39-con.html&amp;amp;toc=/hpux/onlinedocs/B2355-90672/00/00/39-toc.html&amp;amp;searchterms=lofs&amp;amp;queryid=20001102-042219" target="_blank"&gt;http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90672/B2355-90672_top.html&amp;amp;con=/hpux/onlinedocs/B2355-90672/00/00/39-con.html&amp;amp;toc=/hpux/onlinedocs/B2355-90672/00/00/39-toc.html&amp;amp;searchterms=lofs&amp;amp;queryid=20001102-042219&lt;/A&gt;&lt;BR /&gt;and&lt;BR /&gt;&lt;A href="http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90129/B2355-90129_top.html&amp;amp;con=/hpux/onlinedocs/B2355-90129/00/01/194-con.html&amp;amp;toc=/hpux/onlinedocs/B2355-90129/00/01/194-toc.html&amp;amp;searchterms=lofs&amp;amp;queryid=20001102-042219" target="_blank"&gt;http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90129/B2355-90129_top.html&amp;amp;con=/hpux/onlinedocs/B2355-90129/00/01/194-con.html&amp;amp;toc=/hpux/onlinedocs/B2355-90129/00/01/194-toc.html&amp;amp;searchterms=lofs&amp;amp;queryid=20001102-042219&lt;/A&gt;</description>
      <pubDate>Thu, 02 Nov 2000 12:24:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/loopback-filesystem-or-what/m-p/2460746#M14039</guid>
      <dc:creator>Rainer_1</dc:creator>
      <dc:date>2000-11-02T12:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: loopback filesystem, or what?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/loopback-filesystem-or-what/m-p/2460747#M14040</link>
      <description>John,&lt;BR /&gt;&lt;BR /&gt;thank you for the lengthy explanation.&lt;BR /&gt;Now I know I will have no need for employing HP-UX's loopback filesystems. ;-)&lt;BR /&gt;But at least my conclusion to loopback FS from the acronym lofs was correct, even though my notion and usage of lofs under Linux is slightly deviating.&lt;BR /&gt;&lt;BR /&gt;Rainer,&lt;BR /&gt;&lt;BR /&gt;thank you for providing the link.&lt;BR /&gt;Isn't it amazing how much CGI URL encoding line noise the HP webdevelopers can put in a single string? ;-)</description>
      <pubDate>Thu, 02 Nov 2000 13:42:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/loopback-filesystem-or-what/m-p/2460747#M14040</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2000-11-02T13:42:33Z</dc:date>
    </item>
  </channel>
</rss>

