<?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: ux2Dos in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ux2dos/m-p/7033931#M491124</link>
    <description>&lt;P&gt;&amp;gt; We are writting an extract to send to a customer. [...]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; "send" how, exactly?&lt;/P&gt;&lt;P&gt;&amp;gt; I was hoping to not have to write something to remove the end of file&lt;BR /&gt;&amp;gt; character.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; The reason I asked about the flow is that one possibility would be&lt;BR /&gt;to send a zip archive to the victim instead of a raw text file.&amp;nbsp; For&lt;BR /&gt;example, Info-ZIP Zip has an option, "-l&amp;nbsp;&amp;nbsp; convert LF to CR LF", and&lt;BR /&gt;Info-ZIP UnZip has an option, "-a&amp;nbsp; auto-convert any text files".&lt;BR /&gt;Info-ZIP UnZip or some other unzip programs (or related OS features)&lt;BR /&gt;might do the desired line-ending conversion with little or no extra&lt;BR /&gt;effort, even if Zip didn't.&amp;nbsp; (And you'd get the compression and&lt;BR /&gt;file-integrity checking which come with a zip archive.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; As usual, many things are possible.&amp;nbsp; You probably know more about&lt;BR /&gt;your victim's environment and requirements/desires than I do, but&lt;BR /&gt;"ux2dos", with or without extra help, might not be the best tool for the&lt;BR /&gt;job (depending on exactly what the job actually is).&lt;/P&gt;</description>
    <pubDate>Thu, 07 Feb 2019 15:45:30 GMT</pubDate>
    <dc:creator>Steven Schweda</dc:creator>
    <dc:date>2019-02-07T15:45:30Z</dc:date>
    <item>
      <title>ux2Dos</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ux2dos/m-p/7033821#M491121</link>
      <description>&lt;P&gt;Is there any way to stop ux2Dos from putting an end-of-file character (0x1a) at the end of each converted file?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Feb 2019 23:09:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ux2dos/m-p/7033821#M491121</guid>
      <dc:creator>MarkWilson</dc:creator>
      <dc:date>2019-02-06T23:09:51Z</dc:date>
    </item>
    <item>
      <title>Re: ux2Dos</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ux2dos/m-p/7033823#M491122</link>
      <description>&lt;P&gt;&amp;gt; Is there any way to stop ux2Dos from putting an end-of-file character&lt;BR /&gt;&amp;gt; (0x1a) at the end of each converted file?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I doubt it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Write a short C program to replace "ux2dos"?&amp;nbsp; Delete the thing after&lt;BR /&gt;"ux2dos" adds it?&amp;nbsp; For example:&lt;/P&gt;&lt;P&gt;dyi# uname -a&lt;BR /&gt;HP-UX dyi B.11.31 U ia64 4235313755 unlimited-user license&lt;/P&gt;&lt;P&gt;dyi# cat two.txt&lt;BR /&gt;A&lt;BR /&gt;B&lt;/P&gt;&lt;P&gt;dyi# cat two.txt | od -b&lt;BR /&gt;0000000 101 012 102 012&lt;BR /&gt;0000004&lt;/P&gt;&lt;P&gt;dyi# cat two.txt | ux2dos | od -b&lt;BR /&gt;0000000 101 015 012 102 015 012 032&lt;BR /&gt;0000007&lt;/P&gt;&lt;P&gt;dyi# cat two.txt | ux2dos | tr -d '\032' | od -b&lt;BR /&gt;0000000 101 015 012 102 015 012&lt;BR /&gt;0000006&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; What's the flow that requires this sort of line-ending conversion?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Feb 2019 00:33:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ux2dos/m-p/7033823#M491122</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2019-02-07T00:33:31Z</dc:date>
    </item>
    <item>
      <title>Re: ux2Dos</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ux2dos/m-p/7033929#M491123</link>
      <description>&lt;P&gt;We are writting an extract to send to a customer.&amp;nbsp; Our convention is to write unix style line endings.&amp;nbsp; Our customer wants DOS style line endings.&amp;nbsp; My boss has made the decision that we will not modify our code to generate DOS style line endings for this extract.&lt;/P&gt;&lt;P&gt;I was hoping to not have to write something to remove the end of file character.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your assistance.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Feb 2019 15:15:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ux2dos/m-p/7033929#M491123</guid>
      <dc:creator>MarkWilson</dc:creator>
      <dc:date>2019-02-07T15:15:37Z</dc:date>
    </item>
    <item>
      <title>Re: ux2Dos</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ux2dos/m-p/7033931#M491124</link>
      <description>&lt;P&gt;&amp;gt; We are writting an extract to send to a customer. [...]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; "send" how, exactly?&lt;/P&gt;&lt;P&gt;&amp;gt; I was hoping to not have to write something to remove the end of file&lt;BR /&gt;&amp;gt; character.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; The reason I asked about the flow is that one possibility would be&lt;BR /&gt;to send a zip archive to the victim instead of a raw text file.&amp;nbsp; For&lt;BR /&gt;example, Info-ZIP Zip has an option, "-l&amp;nbsp;&amp;nbsp; convert LF to CR LF", and&lt;BR /&gt;Info-ZIP UnZip has an option, "-a&amp;nbsp; auto-convert any text files".&lt;BR /&gt;Info-ZIP UnZip or some other unzip programs (or related OS features)&lt;BR /&gt;might do the desired line-ending conversion with little or no extra&lt;BR /&gt;effort, even if Zip didn't.&amp;nbsp; (And you'd get the compression and&lt;BR /&gt;file-integrity checking which come with a zip archive.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; As usual, many things are possible.&amp;nbsp; You probably know more about&lt;BR /&gt;your victim's environment and requirements/desires than I do, but&lt;BR /&gt;"ux2dos", with or without extra help, might not be the best tool for the&lt;BR /&gt;job (depending on exactly what the job actually is).&lt;/P&gt;</description>
      <pubDate>Thu, 07 Feb 2019 15:45:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ux2dos/m-p/7033931#M491124</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2019-02-07T15:45:30Z</dc:date>
    </item>
  </channel>
</rss>

