Re: MAP_AUTOGROW

Re: MAP_AUTOGROW

[Ralf Baechle]

> Thus spake Ralf Baechle:
> > > "Your" mkdep.c uses MAP_AUTOGROW, which doesn't appear in my Intel
> > > kernel sources.
> > > 
> > > This makes it kinda hard to xcompile. =)
> > > 
> > > I'm going to try just removing the reference, and see if it breaks anything.
> > 
> > Uhh...  That's an ugly hack which I added to make the things run on
> > IRIX and Solaris.  I knew that it has some problems ...
> 
> If I add something like:
> #ifndef MAP_AUTOGROW
> #define MAP_AUTOGROW 0
> #endif
> 
> to the file and commit it, will that work OK?

No, that's also an incorrect solution.  Let me explain the bug in mkdep.
When mkdep processes a file it does not read it into memory but it uses
open(2) and mmap(2) and then parses the file using a highly optimized
state machine.  When mkdep reaches the end of the file the state machine
may access some bytes beyond the mapped file.  Under normal circumstances
this makes no problems.  If however the excess bytes are on the next page
the mkdep will be sent a SIGBUS.

This only happens on systems where the mmap does strictly conform to
standards like IRIX or Solaris.  For Linux mkdep uses a little trick,
it tries to make more of the file than the file is long and Linux honors
that trick by not sending the signal for an attempted access to the
trailing bytes.  By my (very strict) interpretation of POSIX / XPG4 Linux
does the wrong thing and mkdep is based on this special Linux behaviour.

The way I glue this by using MAP_AUTOGROW is also broken ...

  Ralf

Re: MAP_AUTOGROW

[Ralf Baechle]

> Thus spake Ralf Baechle:
> > > "Your" mkdep.c uses MAP_AUTOGROW, which doesn't appear in my Intel
> > > kernel sources.
> > > 
> > > This makes it kinda hard to xcompile. =)
> > > 
> > > I'm going to try just removing the reference, and see if it breaks anything.
> > 
> > Uhh...  That's an ugly hack which I added to make the things run on
> > IRIX and Solaris.  I knew that it has some problems ...
> 
> If I add something like:
> #ifndef MAP_AUTOGROW
> #define MAP_AUTOGROW 0
> #endif
> 
> to the file and commit it, will that work OK?

No, that's also an incorrect solution.  Let me explain the bug in mkdep.
When mkdep processes a file it does not read it into memory but it uses
open(2) and mmap(2) and then parses the file using a highly optimized
state machine.  When mkdep reaches the end of the file the state machine
may access some bytes beyond the mapped file.  Under normal circumstances
this makes no problems.  If however the excess bytes are on the next page
the mkdep will be sent a SIGBUS.

This only happens on systems where the mmap does strictly conform to
standards like IRIX or Solaris.  For Linux mkdep uses a little trick,
it tries to make more of the file than the file is long and Linux honors
that trick by not sending the signal for an attempted access to the
trailing bytes.  By my (very strict) interpretation of POSIX / XPG4 Linux
does the wrong thing and mkdep is based on this special Linux behaviour.

The way I glue this by using MAP_AUTOGROW is also broken ...

  Ralf

Some simple hardware questions...

[Alex deVries]

I have some ultra simple hardware questions that I couldn't find answers
to.  Excuse the noviceness of it all, I haven't touched SGI hardware in
quite some time.

1. Do Indy's come equipped with floppy drives?  What are they?  Is it
possible to boot from them?

2. I know O2's have PCI busses with a custom controller.  Do Indy's have
this too? What is the name of this controller? It would seem reasonably
easy to slap a PCI VGA card in there and port XFree86 to run on it.

3. Do Indy's ship with CDROMs?

As an aside, I asked Erik Troan for the source for the RedHat Install
program, and he seems quite interested in SGI-Linux.

- Alex

      Alex deVries           "Alex can cut a mean rug."
  System Administrator       - M. Dittberner <shabby@engsoc.carleton.ca>
   The EngSoc Project     

Re: Some simple hardware questions...

[David S. Miller]

   Date: Tue, 24 Jun 1997 12:38:39 -0400 (EDT)
   From: Alex deVries <adevries@engsoc.carleton.ca>

   1. Do Indy's come equipped with floppy drives?  What are they?  Is it
   possible to boot from them?

Yes, they are SCSI floppy drives.

   2. I know O2's have PCI busses with a custom controller.  Do Indy's have
   this too? What is the name of this controller? It would seem reasonably
   easy to slap a PCI VGA card in there and port XFree86 to run on it.

No, but I believe some models were produced with EISA slots on the
motherboard.

   3. Do Indy's ship with CDROMs?

Can't answer this one personally.

Re: Some simple hardware questions...

[Bob Mende Pie]

> 1. Do Indy's come equipped with floppy drives?  What are they?  Is it
> possible to boot from them?

There is an option on indy's that allow for a SCSI iomega floptical (21MB)
drive.  These drives are treated as a removable SCSI disk.  You should be
able to boot from them but I have never tried.
 
> 2. I know O2's have PCI busses with a custom controller.  Do Indy's have
> this too? What is the name of this controller? It would seem reasonably
> easy to slap a PCI VGA card in there and port XFree86 to run on it.

The indy does not have PCI.   They use a gio bus.
 
> 3. Do Indy's ship with CDROMs?

As an option there is an external CDROM.   I believe that (nowadays) you
have to really try to get a system without a cdrom.
 
 
                              /Bob...                    mailto:mende@sgi.com
                        http://reality.sgi.com/mende/          KF6EID

Re: Some simple hardware questions...

[Martin Knoblauch]

Alex deVries wrote:
> 
> I have some ultra simple hardware questions that I couldn't
> find answers to.  Excuse the noviceness of it all, I haven't
> touched SGI hardware in quite some time.
> 
> 1. Do Indy's come equipped with floppy drives?  What are they?
>    Is it possible to boot from them?
>

 Oh no :-) No, Indys don't come usually with floppys. We
offer a 20MB Floptical option (internal), or a normal floppy
option (external). Both are not really popular with our customers.

 You might be able to boot from them, but this was probably never
tested...
 
> 2. I know O2's have PCI busses with a custom controller.
>    Do Indy's have this too? What is the name of this controller?
>    It would seem reasonably easy to slap a PCI VGA card in there
>    and port XFree86 to run on it.
>

 No, Indy comes with our proprietary GIO bus. The GFX cards (8/24)
plug on that.
 
> 3. Do Indy's ship with CDROMs?
>

 More often than with floppies, but it is an option. Not standard.
 
Martin
-- 
+---------------------------------+-----------------------------------+
|Martin Knoblauch                 | Silicon Graphics GmbH             |
|Manager Technical Marketing      | Am Hochacker 3 - Technopark       |
|Silicon Graphics Computer Systems| D-85630 Grasbrunn-Neukeferloh, FRG|
|---------------------------------| Phone: (+int) 89 46108-179 or -0  |
|http://reality.sgi.com/knobi     | Fax:   (+int) 89 46107-179        |
+---------------------------------+-----------------------------------+
|e-mail: <knobi@munich.sgi.com>   | VM: 6-333-8197 | M/S: IDE-3150    |
+---------------------------------------------------------------------+

Re: Some simple hardware questions...

[Bob Mende Pie]

>    2. I know O2's have PCI busses with a custom controller.  Do Indy's have
>    this too? What is the name of this controller? It would seem reasonably
>    easy to slap a PCI VGA card in there and port XFree86 to run on it.
> 
> No, but I believe some models were produced with EISA slots on the
> motherboard.

I think that was the indigo2.   
 
                              /Bob...                    mailto:mende@sgi.com
                        http://reality.sgi.com/mende/          KF6EID

Re: Some simple hardware questions...

[Martin Knoblauch]

David S. Miller wrote:
> 
>    Date: Tue, 24 Jun 1997 12:38:39 -0400 (EDT)
>    From: Alex deVries <adevries@engsoc.carleton.ca>
> 
>    1. Do Indy's come equipped with floppy drives?  What are they?
>       Is it possible to boot from them?
> 
> Yes, they are SCSI floppy drives.
>

 As I said: optional. No boot guarantee.
 
>    2. I know O2's have PCI busses with a custom controller.
>       Do Indy's have  this too? What is the name of this
>       controller? It would seem reasonably easy to slap a
>       PCI VGA card in there and port XFree86 to run on it.
> 
> No, but I believe some models were produced with EISA slots
> on the motherboard.
> 

  That is the Indigo2/Challenge-M series. Our first attempt
on open expansion busses.

Martin
-- 
+---------------------------------+-----------------------------------+
|Martin Knoblauch                 | Silicon Graphics GmbH             |
|Manager Technical Marketing      | Am Hochacker 3 - Technopark       |
|Silicon Graphics Computer Systems| D-85630 Grasbrunn-Neukeferloh, FRG|
|---------------------------------| Phone: (+int) 89 46108-179 or -0  |
|http://reality.sgi.com/knobi     | Fax:   (+int) 89 46107-179        |
+---------------------------------+-----------------------------------+
|e-mail: <knobi@munich.sgi.com>   | VM: 6-333-8197 | M/S: IDE-3150    |
+---------------------------------------------------------------------+

Re: Some simple hardware questions...

[William J. Earl]

Alex deVries writes:
 > 
 > I have some ultra simple hardware questions that I couldn't find answers
 > to.  Excuse the noviceness of it all, I haven't touched SGI hardware in
 > quite some time.
 > 
 > 1. Do Indy's come equipped with floppy drives?  What are they?  Is it
 > possible to boot from them?

     An Indy does not come with a floppy drive standard, but it does support
both a floppy and a floptical drive.  Both are SCSI drives, and you should 
be able to boot from them, since the boot software does not distinguish
among drive types.

 > 2. I know O2's have PCI busses with a custom controller.  Do Indy's have
 > this too? What is the name of this controller? It would seem reasonably
 > easy to slap a PCI VGA card in there and port XFree86 to run on it.

     No, the Indy has the SGI-specific GIO bus.

 > 3. Do Indy's ship with CDROMs?

     An Indy does not come with a CDROM by default, but most SCSI CDROM
drives should work.  (There is a supported SGI CDROM drive.)

Re: Some simple hardware questions...

[Miguel de Icaza]

> As an aside, I asked Erik Troan for the source for the RedHat Install
> program, and he seems quite interested in SGI-Linux.

it is distributed as part of redhat 4.2 on ftp siets.

Miguel.

Re: Some simple hardware questions...

[Miguel de Icaza]

> > it is distributed as part of redhat 4.2 on ftp siets.
> 
> I assume you're talking about the little endian binaries which they're
> mirroring from kernel panic.  As I said, they're little endian ...

Well, I was thinking in Red Hat's source code for their install
program.

Miguel.

Re: Some simple hardware questions...

[Ralf Baechle]

Hi,

> > As an aside, I asked Erik Troan for the source for the RedHat Install
> > program, and he seems quite interested in SGI-Linux.
> 
> it is distributed as part of redhat 4.2 on ftp siets.

I assume you're talking about the little endian binaries which they're
mirroring from kernel panic.  As I said, they're little endian ...

  Ralf

Re: Some simple hardware questions...

[Ralf Baechle]

Hi,

> > As an aside, I asked Erik Troan for the source for the RedHat Install
> > program, and he seems quite interested in SGI-Linux.
> 
> it is distributed as part of redhat 4.2 on ftp siets.

I assume you're talking about the little endian binaries which they're
mirroring from kernel panic.  As I said, they're little endian ...

  Ralf