<?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: /dev/null in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dev-null/m-p/4698522#M383791</link>
    <description>&lt;!--!*#--&gt;Is Google broken?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://en.wikipedia.org/wiki//dev/null" target="_blank"&gt;http://en.wikipedia.org/wiki//dev/null&lt;/A&gt;</description>
    <pubDate>Tue, 12 Oct 2010 15:52:46 GMT</pubDate>
    <dc:creator>Steven Schweda</dc:creator>
    <dc:date>2010-10-12T15:52:46Z</dc:date>
    <item>
      <title>/dev/null</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dev-null/m-p/4698521#M383790</link>
      <description>what does /dev/null refer to.&lt;BR /&gt;&lt;BR /&gt;cp /dev/null &amp;gt; file name --- nullifies the data and set to zero size file.&lt;BR /&gt;&lt;BR /&gt;whether it sets to zero size or it resides some where else???&lt;BR /&gt;&lt;BR /&gt;what is the use in using /dev/null&lt;BR /&gt;&lt;BR /&gt;2.dd if=/dev/rdsk/cxtydz of=/dev/null bs=1024&lt;BR /&gt;&lt;BR /&gt;what does it refer to ??&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Oct 2010 15:49:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dev-null/m-p/4698521#M383790</guid>
      <dc:creator>newunix</dc:creator>
      <dc:date>2010-10-12T15:49:43Z</dc:date>
    </item>
    <item>
      <title>Re: /dev/null</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dev-null/m-p/4698522#M383791</link>
      <description>&lt;!--!*#--&gt;Is Google broken?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://en.wikipedia.org/wiki//dev/null" target="_blank"&gt;http://en.wikipedia.org/wiki//dev/null&lt;/A&gt;</description>
      <pubDate>Tue, 12 Oct 2010 15:52:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dev-null/m-p/4698522#M383791</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2010-10-12T15:52:46Z</dc:date>
    </item>
    <item>
      <title>Re: /dev/null</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dev-null/m-p/4698523#M383792</link>
      <description>"cp /dev/null &amp;gt; file name" will null out a file, that is, set it to zero size.  The same can be accomplished through file redirection as "&amp;gt; file name".&lt;BR /&gt;&lt;BR /&gt;In your second case dd is being used to test a device for readability, reading in the entire disk without actually seeing the contents.  The output file being set to /dev/null simply ignores the output.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Tue, 12 Oct 2010 15:54:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dev-null/m-p/4698523#M383792</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2010-10-12T15:54:39Z</dc:date>
    </item>
    <item>
      <title>Re: /dev/null</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dev-null/m-p/4698524#M383793</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;The device file '/dev/null' returns nothing as it's name suggests.  The shell redirection operator (the '&amp;gt;') says open for output and truncate any file that exists, setting the end-of-file pointer to a zero-offset.&lt;BR /&gt;&lt;BR /&gt;These are all the same:&lt;BR /&gt;&lt;BR /&gt;# cp /dev/null myfile&lt;BR /&gt;# cat /dev/null &amp;gt; myfile&lt;BR /&gt;# &amp;gt; myfile&lt;BR /&gt;&lt;BR /&gt;That last is a shorthand method.&lt;BR /&gt;&lt;BR /&gt;As for :&lt;BR /&gt;&lt;BR /&gt;# dd if=/dev/rdsk/cxtydz of=/dev/null bs=1024&lt;BR /&gt;&lt;BR /&gt;This says use the '/dev/rdsk/cxtydz' device as the input file ('if'); read it; and write whatever is written to the output file '/dev/null'.  Nothing is actually stored on disk; rather the I/O is down-the-drain.  The 'bs=1024' says to use a physical read size (block) of 1024 characters.&lt;BR /&gt;&lt;BR /&gt;Normally the above would be 'bs=1024k' for performance.  The use of the *raw* device file keeps LVM buffering from needlessly being applied.  The command is used to test a disk for readability.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 12 Oct 2010 15:58:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dev-null/m-p/4698524#M383793</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2010-10-12T15:58:11Z</dc:date>
    </item>
  </channel>
</rss>

