<?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 Re: how to associate one physical device to one block device-file? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/how-to-associate-one-physical-device-to-one-block-device-file/m-p/2953486#M4316</link>
    <description>Hi Frederick.&lt;BR /&gt;&lt;BR /&gt;The actual device filename doesn't matter so much, but it depends on the applicaitons. If you can tell your application which device file to use, it's not a problem to name it the way you want.&lt;BR /&gt;&lt;BR /&gt;The driver doesn't care about the filename, it only needs to know the major and minor number of the device (those are the numbers that you specify at the end of the mknod command).&lt;BR /&gt;&lt;BR /&gt;So you can create a device /tmp/foo and use it to happily mount your flash device, as long as the major and minor numbers correctly correspond to it (i.e. it should be the same as sda1 in most cases).&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;Goran&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 17 Apr 2003 04:52:02 GMT</pubDate>
    <dc:creator>Goran Koruga</dc:creator>
    <dc:date>2003-04-17T04:52:02Z</dc:date>
    <item>
      <title>how to associate one physical device to one block device-file?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/how-to-associate-one-physical-device-to-one-block-device-file/m-p/2953485#M4315</link>
      <description>yes, I know such as:&lt;BR /&gt; mknod -m 660 /dev/ram b 1 1&lt;BR /&gt;can make up one block file, but, how it can associate to the designated device, or call locate the driver program? for example, if i want to create /dev/fla what link to one flash-memory, how mknod can know it should use the flash card driver for /dev/fla?&lt;BR /&gt;&lt;BR /&gt;apprecate for your helps in advance.&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Frederick&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Apr 2003 04:16:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/how-to-associate-one-physical-device-to-one-block-device-file/m-p/2953485#M4315</guid>
      <dc:creator>frederick van tagero</dc:creator>
      <dc:date>2003-04-17T04:16:32Z</dc:date>
    </item>
    <item>
      <title>Re: how to associate one physical device to one block device-file?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/how-to-associate-one-physical-device-to-one-block-device-file/m-p/2953486#M4316</link>
      <description>Hi Frederick.&lt;BR /&gt;&lt;BR /&gt;The actual device filename doesn't matter so much, but it depends on the applicaitons. If you can tell your application which device file to use, it's not a problem to name it the way you want.&lt;BR /&gt;&lt;BR /&gt;The driver doesn't care about the filename, it only needs to know the major and minor number of the device (those are the numbers that you specify at the end of the mknod command).&lt;BR /&gt;&lt;BR /&gt;So you can create a device /tmp/foo and use it to happily mount your flash device, as long as the major and minor numbers correctly correspond to it (i.e. it should be the same as sda1 in most cases).&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;Goran&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Apr 2003 04:52:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/how-to-associate-one-physical-device-to-one-block-device-file/m-p/2953486#M4316</guid>
      <dc:creator>Goran Koruga</dc:creator>
      <dc:date>2003-04-17T04:52:02Z</dc:date>
    </item>
  </channel>
</rss>

