Re: $OSTYPE

Re: $OSTYPE

[Martin Costabel]

On Mon, 03 May 1999, "Charles E. Leiserson, Jr." <locutus@MIT.EDU>
wrote:

> 
> Probably a stupid question but...
> 
> Why does 'echo $OSTYPE' give me 'mklinux' when I'm runnin LinuxPPC R4.1?
> 

I think this is a problem of tcsh. It is not present in bash. It comes
from the fact is that RedHat thinks the only linux on ppc is mklinux.
You get VENDOR=apple, too.

Below is a patch for tcsh-6.08.00-5. I hope the linuxppc developers put
something like this in R5. (Of course, the "vendor" could be left empty,
giving "unknown", or be replaced by "BlueCat" or something similar).

--
Martin

--- /usr/src/redhat/BUILD/tcsh-6.08.00/host.defs.ori    Sun May  9
17:03:05 1999
+++ /usr/src/redhat/BUILD/tcsh-6.08.00/host.defs        Sun May  9
17:06:54 1999
@@ -438,13 +438,12 @@
 hosttype: defined(M_i586)                              : "i586-linux"
 hosttype: defined(M_i486)                              : "i486-linux"
 hosttype: defined(M_i386)                              : "i386-linux"
-ostype : !defined(PPC)                                 : "linux"
-ostype : defined(PPC)                                  : "mklinux"
+ostype :                                               : "linux"
 machtype: defined(M_i586)                              : "i586"
 machtype: defined(M_i486)                              : "i486"
 machtype: defined(M_i386)                              : "i386"
 vendor : defined(__alpha)                              : "dec"
-vendor : defined(PPC)                                  : "apple"
+vendor : defined(PPC)                                  : "linuxppc"
 hosttype: defined(__alpha)                             : "alpha"
 hosttype: defined(PPC)                                 : "powerpc"
 machtype: defined(__alpha)                             : "alpha"

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: $OSTYPE

[Tom Rini]

On Sun, 9 May 1999, Martin Costabel wrote:

> I think this is a problem of tcsh. It is not present in bash. It comes
> from the fact is that RedHat thinks the only linux on ppc is mklinux.
> You get VENDOR=apple, too.

Mostly applied :) (AMD and cyrix get labeled intel it looks like, so the
non-apple pmacs and other ppcs can be called apple, unless someone has a
better idea)

---
Tom Rini (TR1265)
http://dobbstown.yeti.edu/


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: $OSTYPE

[Erik Karlberg]

On Sun, 9 May 1999, Tom Rini wrote:
> Mostly applied :) (AMD and cyrix get labeled intel it looks like, so the
> non-apple pmacs and other ppcs can be called apple, unless someone has a
> better idea)

I guess the intel-label of the AMD and Cyrix processors kind of resembles
intel-compatibility or somthing like that...
So labeling all ppc-machines apple might not be such
a great idea, since it is not Apple alone who's behind the ppc..

How about labeling it aim? (Apple IBM Motorola)
However, that might be a bit confusing for those who doesn't know what it
mean...

Just my suggestion though.

Regards,

Erik



[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: $OSTYPE

[Tom Rini]

On Sun, 9 May 1999, Erik Karlberg wrote:

> 
> On Sun, 9 May 1999, Tom Rini wrote:
> > Mostly applied :) (AMD and cyrix get labeled intel it looks like, so the
> > non-apple pmacs and other ppcs can be called apple, unless someone has a
> > better idea)
> 
> I guess the intel-label of the AMD and Cyrix processors kind of resembles
> intel-compatibility or somthing like that...
> So labeling all ppc-machines apple might not be such
> a great idea, since it is not Apple alone who's behind the ppc..

Apple is the biggest "vendor" tho (of 6xx/7xx ppcs).  It doesn't really
matter as most config scripts are *-linux-gnu-* or so, so having OSTYPE
mklinux would be bad (if a script should check that way).

> How about labeling it aim? (Apple IBM Motorola)
> However, that might be a bit confusing for those who doesn't know what it
> mean...

Exactly..

---
Tom Rini (TR1265)
http://dobbstown.yeti.edu/


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: $OSTYPE

[Andrew Weiss]

>
>On Sun, 9 May 1999, Tom Rini wrote:
>> Mostly applied :) (AMD and cyrix get labeled intel it looks like, so the
>> non-apple pmacs and other ppcs can be called apple, unless someone has a
>> better idea)
>
>I guess the intel-label of the AMD and Cyrix processors kind of resembles
>intel-compatibility or somthing like that...
>So labeling all ppc-machines apple might not be such
>a great idea, since it is not Apple alone who's behind the ppc..
>
>How about labeling it aim? (Apple IBM Motorola)
>However, that might be a bit confusing for those who doesn't know what it
>mean...
>
>Just my suggestion though.
>
>Regards,
>
>Erik

Hmmm AOL instant messenger?

So quick aside, does anybody know if excessive network collisions are likely
a problem of a poor kernel/module compile, or just my hardware.  I know this
isn't too related, but my Linksys 10/100 21140 Tulip is used correctly by 98
and NT, detected and ifconfiged right by Linux, even supported on their
website... it is the PNIC chipset, but when I try to talk to the internet
through the mac on linux, I notice that it can't, and I get a collision and
sequestering of the line every two seconds on my Linksys 8 port 10/100 hub,
then it resets.   Collide reset collide reset etc.
and telnet never gets through nor does ping.  I am using caldera 1.3 and
kernel 2.0.35.

Any ideas?

Andrew

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]