Re: Environment Variable weirdness

1999-09-30 Thread Brian Servis
The first two variables are set by the shell and are determined either at compile time or by the environment it starts up in. Read the man page for your shell. For bash it says the following: HOSTTYPE Automatically set to a string that uniquely describe

Re: Environment Variable weirdness

1999-09-30 Thread peter karlsson
Salman Ahmed: > But where is this env. var being set from ? It's not even an environment variable, but rather an internal bash variable. -- \\// peter - http://www.softwolves.pp.se/ - and God said: nohup make World >& World.log &

Re: Environment Variable weirdness

1999-09-30 Thread Paul D. Smith
%% Salman Ahmed <[EMAIL PROTECTED]> writes: Nathan> It's faster to use a "UNIX domain socket" when all traffic is Nathan> local as you avoid some of teh overhead of an IP stack. Why Nathan> waste those milliseconds? sa> Would you be willing to explain the technicalities behind that ? Sou

Re: Environment Variable weirdness

1999-09-30 Thread Nathan E Norman
On Wed, 29 Sep 1999, Salman Ahmed wrote: [ snip ] : Nathan> It's faster to use a "UNIX domain socket" when all traffic is : Nathan> local as you avoid some of teh overhead of an IP stack. Why : Nathan> waste those milliseconds? : : Would you be willing to explain the technicali

Re: Environment Variable weirdness

1999-09-30 Thread Seth R Arnold
You want the HOSTTYPE to say i386, since your machine IS a 386-compatible chip. :) As for that environment variable, you could parse the output of: $ uname -rm 2.0.36 i686 And build it yourself... :) On Wed, Sep 29, 1999 at 08:39:48PM -0400, Salman Ahmed wrote: > > (1) > Running Debian 2.1, I n

Re: Environment Variable weirdness

1999-09-30 Thread Brad
-BEGIN PGP SIGNED MESSAGE- On Wed, 29 Sep 1999, Salman Ahmed wrote: > > "Nathan" == Nathan E Norman <[EMAIL PROTECTED]> writes: > > Nathan> It's faster to use a "UNIX domain socket" when all traffic is > Nathan> local as you avoid some of teh overhead of an IP stack. Why >

Re: Environment Variable weirdness

1999-09-30 Thread Ben Collins
On Wed, Sep 29, 1999 at 08:54:11PM -0400, Salman Ahmed wrote: > > "Ben" == Ben Collins <[EMAIL PROTECTED]> writes: > Ben> Compilation was for i386 so it would run on more than just > Ben> pentiums. > > You mean for the initial install off of the CDs (or whatever) ? No I mean when the

Re: Environment Variable weirdness

1999-09-30 Thread Salman Ahmed
> "Nathan" == Nathan E Norman <[EMAIL PROTECTED]> writes: Nathan> ... but the machine architecture is still "i386", as in Intel Nathan> CISC. Other machine architectures include m68k, powerpc, Nathan> alpha, hp-ppa, etc. Nathan> You don't need to worry about this. Ok, that m

Re: Environment Variable weirdness

1999-09-30 Thread Salman Ahmed
> "Ben" == Ben Collins <[EMAIL PROTECTED]> writes: Ben> Compilation was for i386 so it would run on more than just Ben> pentiums. You mean for the initial install off of the CDs (or whatever) ? But where is this env. var being set from ? Currently, it is not valid for my system since

Re: Environment Variable weirdness

1999-09-30 Thread Nathan E Norman
On Wed, 29 Sep 1999, Salman Ahmed wrote: : : (1) : Running Debian 2.1, I noticed sth odd about a couple of : environment variables (I am running XFree-3.3.3.1-2). : : First of all : : : HOSTTYPE=i386-linux : : I have a Celeron 300A processor and have installed a new : 2.2.12 ke

Re: Environment Variable weirdness

1999-09-30 Thread Ben Collins
On Wed, Sep 29, 1999 at 08:39:48PM -0400, Salman Ahmed wrote: > > (1) > Running Debian 2.1, I noticed sth odd about a couple of > environment variables (I am running XFree-3.3.3.1-2). > > First of all : > > HOSTTYPE=i386-linux Compilation was for i386 so it would run on more than just pent