<?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 Device file in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/device-file/m-p/3874264#M278980</link>
    <description>Hi Team ,&lt;BR /&gt;&lt;BR /&gt;I have a doubt in device file ,&lt;BR /&gt;&lt;BR /&gt;What is the purpose of having character and block files for a device , if we are using modem character device it self enough what is the need of block file.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance&lt;BR /&gt;&lt;BR /&gt;john</description>
    <pubDate>Wed, 04 Oct 2006 10:14:05 GMT</pubDate>
    <dc:creator>johnreid</dc:creator>
    <dc:date>2006-10-04T10:14:05Z</dc:date>
    <item>
      <title>Device file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-file/m-p/3874264#M278980</link>
      <description>Hi Team ,&lt;BR /&gt;&lt;BR /&gt;I have a doubt in device file ,&lt;BR /&gt;&lt;BR /&gt;What is the purpose of having character and block files for a device , if we are using modem character device it self enough what is the need of block file.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance&lt;BR /&gt;&lt;BR /&gt;john</description>
      <pubDate>Wed, 04 Oct 2006 10:14:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-file/m-p/3874264#M278980</guid>
      <dc:creator>johnreid</dc:creator>
      <dc:date>2006-10-04T10:14:05Z</dc:date>
    </item>
    <item>
      <title>Re: Device file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-file/m-p/3874265#M278981</link>
      <description>With disk devices, for example, the character or raw device file bypasses the operating system's buffer cache, which is what some data base products require.  Other than that, most times you would want to use the block device.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Wed, 04 Oct 2006 10:21:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-file/m-p/3874265#M278981</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2006-10-04T10:21:05Z</dc:date>
    </item>
    <item>
      <title>Re: Device file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-file/m-p/3874266#M278982</link>
      <description>Block device files refer to a specific driver (the major number) and this number points to a driver that uses the buffer cache. There is no block driver for any device that is not a disk (ie, printer, tty/modem, LAN, etc). All filesystems access data via block files for performance unless extra options are used in fstab to bypass the cache.</description>
      <pubDate>Wed, 04 Oct 2006 10:31:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-file/m-p/3874266#M278982</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2006-10-04T10:31:41Z</dc:date>
    </item>
    <item>
      <title>Re: Device file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-file/m-p/3874267#M278983</link>
      <description>In general, only disk devices will have block device nodes but all devices will have character device nodes. In the kernel there are two device switch tables (character and block) and these tables tell the system how to do basic operations (open, close, read, write, seek, ...) for a given device. These tables are actually implemented as arrays of pointers to the various functions. In any event, if there are no entries for these functions this is signaled as a null entry in the device switch tables and if there are no functions at all defined for a given device (such as block devices for a modem) then a -1 or NULL is inserted in the device switch table.  &lt;BR /&gt;</description>
      <pubDate>Wed, 04 Oct 2006 10:39:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-file/m-p/3874267#M278983</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-10-04T10:39:36Z</dc:date>
    </item>
    <item>
      <title>Re: Device file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-file/m-p/3874268#M278984</link>
      <description>Check out the link below:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.uwsg.iu.edu/usail/peripherals/devices/devintro.html" target="_blank"&gt;http://www.uwsg.iu.edu/usail/peripherals/devices/devintro.html&lt;/A&gt;</description>
      <pubDate>Wed, 04 Oct 2006 13:08:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-file/m-p/3874268#M278984</guid>
      <dc:creator>Sandman!</dc:creator>
      <dc:date>2006-10-04T13:08:25Z</dc:date>
    </item>
  </channel>
</rss>

