<?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: 64 bit vs 32 bit environment in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100634#M63763</link>
    <description>Yes, I'm a terrible nuisance.  Isn't it sad?&lt;BR /&gt;&lt;BR /&gt;Feel free to enlighten me (and any future&lt;BR /&gt;readers of this thread) by explaining exactly&lt;BR /&gt;what the actual problem was, and what you did&lt;BR /&gt;to solve it.</description>
    <pubDate>Mon, 31 Mar 2008 20:33:27 GMT</pubDate>
    <dc:creator>Steven Schweda</dc:creator>
    <dc:date>2008-03-31T20:33:27Z</dc:date>
    <item>
      <title>64 bit vs 32 bit environment</title>
      <link>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100627#M63756</link>
      <description>I have a couple of users who are trying to run some "older" scripts on a 64 bit distro. They don't run yet will work on a 32 bit distro. &lt;BR /&gt;&lt;BR /&gt;Isn't there a command that needs to be issued on a 64 bit machine that will allow the scripts to run?</description>
      <pubDate>Mon, 31 Mar 2008 13:22:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100627#M63756</guid>
      <dc:creator>john guardian</dc:creator>
      <dc:date>2008-03-31T13:22:02Z</dc:date>
    </item>
    <item>
      <title>Re: 64 bit vs 32 bit environment</title>
      <link>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100628#M63757</link>
      <description>It's just possible that it would be useful to&lt;BR /&gt;know what you mean by "scripts" and "don't&lt;BR /&gt;run".  What, exactly, fails, and how?&lt;BR /&gt;&lt;BR /&gt;&amp;gt; Isn't there a command that needs to be&lt;BR /&gt;&amp;gt; issued on a 64 bit machine that will allow&lt;BR /&gt;&amp;gt; the scripts to run?&lt;BR /&gt;&lt;BR /&gt;I can't imagine what that command might be,&lt;BR /&gt;but I also can't imagine what's failing in&lt;BR /&gt;your scripts.</description>
      <pubDate>Mon, 31 Mar 2008 14:41:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100628#M63757</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-03-31T14:41:32Z</dc:date>
    </item>
    <item>
      <title>Re: 64 bit vs 32 bit environment</title>
      <link>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100629#M63758</link>
      <description>When I got in this AM, I had a note on my desk. No details... So I can't really provide anything else...</description>
      <pubDate>Mon, 31 Mar 2008 15:59:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100629#M63758</guid>
      <dc:creator>john guardian</dc:creator>
      <dc:date>2008-03-31T15:59:41Z</dc:date>
    </item>
    <item>
      <title>Re: 64 bit vs 32 bit environment</title>
      <link>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100630#M63759</link>
      <description>&amp;gt; So I can't really provide anything else...&lt;BR /&gt;&lt;BR /&gt;If you can provide no useful information,&lt;BR /&gt;then a call to a psychic hotline might be&lt;BR /&gt;more productive than a posting here.</description>
      <pubDate>Mon, 31 Mar 2008 18:37:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100630#M63759</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-03-31T18:37:48Z</dc:date>
    </item>
    <item>
      <title>Re: 64 bit vs 32 bit environment</title>
      <link>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100631#M63760</link>
      <description>So let me try my crystal ball on this one ;-)&lt;BR /&gt;&lt;BR /&gt;By my experience, "script" is usually something that is run through an interpreter, so in a 64-bit environment a script might be using the environment's native script interpreter. So the interpreter should be 64-bit-compatible by default.&lt;BR /&gt;&lt;BR /&gt;One possible source of errors could then be that the script does not get the response it expects from the system. For example, if the script is using "uname -m" or something similar to identify the architecture and does not know about the new 64-bit architectures (x86_64 or ia64), it will return an error.&lt;BR /&gt;&lt;BR /&gt;There *is* a command that allows the system to "lie" about its architecture identifier to a given process and all its children. It is useful only on systems that have some multi-architecture capability. That command is "setarch".&lt;BR /&gt;&lt;BR /&gt;On my home machine (Debian Etch, x86_64) I can do this:&lt;BR /&gt;$ uname -m&lt;BR /&gt;x86_64&lt;BR /&gt;$ setarch i386 uname -m&lt;BR /&gt;i686&lt;BR /&gt;&lt;BR /&gt;You can also use just the name of the desired architecture as a command. This invokes "setarch" through a symbolic link. Setarch does the right thing automatically:&lt;BR /&gt;$ uname -m&lt;BR /&gt;x86_64&lt;BR /&gt;$ i386 uname -m&lt;BR /&gt;i686&lt;BR /&gt;&lt;BR /&gt;Apparently you can also use the setarch command to escape from the fake 32-bit mode, if necessary:&lt;BR /&gt;$ i386 bash&lt;BR /&gt;$ uname -m&lt;BR /&gt;i686&lt;BR /&gt;$ setarch x86_64 uname -m&lt;BR /&gt;x86_64&lt;BR /&gt;$ x86_64 uname -m&lt;BR /&gt;x86_64&lt;BR /&gt;&lt;BR /&gt;If running the script with "setarch i386" makes it work, it might be easy to modify the script to automatically identify the compatible 64-bit architectures.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Mon, 31 Mar 2008 19:10:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100631#M63760</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2008-03-31T19:10:46Z</dc:date>
    </item>
    <item>
      <title>Re: 64 bit vs 32 bit environment</title>
      <link>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100632#M63761</link>
      <description>REPLY to STEVEN SCHWEDA:&lt;BR /&gt;&lt;BR /&gt;Apparently Steven, the only thing YOU have to offer this site is your POMPOUS IGNORANCE. I suggest you take it elsewhere.&lt;BR /&gt;&lt;BR /&gt;Matti, on the other hand, provided me with the info I needed to actually SOLVE the problem.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 31 Mar 2008 20:24:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100632#M63761</guid>
      <dc:creator>john guardian</dc:creator>
      <dc:date>2008-03-31T20:24:22Z</dc:date>
    </item>
    <item>
      <title>Re: 64 bit vs 32 bit environment</title>
      <link>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100633#M63762</link>
      <description>&lt;!--!*#--&gt;&lt;BR /&gt;CHEERS to Matti, the "Problem Solver"!&lt;BR /&gt;&lt;BR /&gt;JEERS to Steven, the "Problem Child".&lt;BR /&gt;&lt;BR /&gt;Thanks again, Matti!</description>
      <pubDate>Mon, 31 Mar 2008 20:28:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100633#M63762</guid>
      <dc:creator>john guardian</dc:creator>
      <dc:date>2008-03-31T20:28:40Z</dc:date>
    </item>
    <item>
      <title>Re: 64 bit vs 32 bit environment</title>
      <link>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100634#M63763</link>
      <description>Yes, I'm a terrible nuisance.  Isn't it sad?&lt;BR /&gt;&lt;BR /&gt;Feel free to enlighten me (and any future&lt;BR /&gt;readers of this thread) by explaining exactly&lt;BR /&gt;what the actual problem was, and what you did&lt;BR /&gt;to solve it.</description>
      <pubDate>Mon, 31 Mar 2008 20:33:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100634#M63763</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-03-31T20:33:27Z</dc:date>
    </item>
    <item>
      <title>Re: 64 bit vs 32 bit environment</title>
      <link>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100635#M63764</link>
      <description>I've already enlightened you, Steven.&lt;BR /&gt;&lt;BR /&gt;Matti solved the issue. The user's machine, which I didn't have access to in the TS Clearance lab, was Debian. &lt;BR /&gt;&lt;BR /&gt;But I wouldn't call you a nuisance... It's too gentile a word. If we ever have the opportunity to speak face2face, I'll be happy to explain it to you publicly, using words similar to your own, so you'll understand them, you know... the mono-syllabic variety.&lt;BR /&gt;&lt;BR /&gt;In the meantime, go polish you crystal ball and leave the problem solving to Matti!</description>
      <pubDate>Mon, 31 Mar 2008 21:13:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100635#M63764</guid>
      <dc:creator>john guardian</dc:creator>
      <dc:date>2008-03-31T21:13:49Z</dc:date>
    </item>
    <item>
      <title>Re: 64 bit vs 32 bit environment</title>
      <link>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100636#M63765</link>
      <description>&amp;gt; I've already enlightened you, Steven.&lt;BR /&gt;&lt;BR /&gt;Thanks for clarifying that.  I was in some&lt;BR /&gt;doubt before.</description>
      <pubDate>Tue, 01 Apr 2008 02:08:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/64-bit-vs-32-bit-environment/m-p/5100636#M63765</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-04-01T02:08:58Z</dc:date>
    </item>
  </channel>
</rss>

