Hi Folks,

After following the discussions, I'd like to summarize what MY OPTION on
the current status of /sbin/grub is:

* /sbin/grub from [EMAIL PROTECTED]:/gd/gnu/anoncvsroot:

  It works as a testbed for the GUI.  I.e. you can add new stuff
  (filesystem, commands, ...) and get the chance to debug it under
  Linux.  NOTHING MORE.
  Especially:
    install= ...
    testload= ...
  fail (reason below).

* Brians patch ("grub patch to fix stage 1.5 and add chainconfig="
  from Sun, 9 May 1999 20:28:54 +0200) applied:

  The subject line talks about "stage 1.5" fixes and "chainconfig"
  extension, however, he fixed also the basic problems with the
  `grub_read' calls in "shared_src/cmdline.c:enter_cmdline "install") and
  `biosdisk' in grub/asmstub.c.

  While Brian did a good job, it's far from complete:

    >>> I'm trying to use the stage2/Unix-version, without success:
    >> 
    >> Oh, don't use /sbin/grub for the real purpose yet! It does not
    >> support writing to disks, which is disabled intentionally because
    >> that's secure. I also already know some bugs in /sbin/grub. For right
    >> now, please use the ``native'' stage2 instead.
    >> 

    Brian> The patch I just sent fixes this. It implements writing to disk
    Brian> in /sbin/grub (but only enabled with a command line flag)
    Brian> and fixes the missing RAW_ADDR() macro call that gave the error.

  Only brave souls can use it to write to their harddisks yet IMHO.
  
  However:
    install= (fd0)/boot/stage1 (fd0) (fd0)/boot/stage2 0x8000 p 
  made a perfectly booting floppy for me.
  
* The bugs (at least what I found, no time to fix yet :-() are in two
  directions: 

  a) ALL `grub_read' calls have to be checked, if they need RAW_ADDR
     and if the memory behind is big enough ("testload" in cmdline.c).

  b) The `open' check result sequences in asmstub.c:get_diskinfo need
     rework

     1) See Gords comment
     2) open -> -1 on error!, the checks and logic assumes 0 (grrrr...).
     3) Linux has some magic with respect to /dev/fd1, i.e. opens for
        all devices hang some time when reaching /dev/fd1 (should be
        handled). 

  Any fixes or ideas yet Brian?

That's it.

cheers
KR

BTW:
People in charge of the grub rep should say which tools and versions
are needed and where to find them (currently `automake 1.4a' and
`makeinfo ?'  make trouble). 

-- 
Klaus Reichl                        voice: +43 (1) 27722 / 3884
Alcatel Austria AG/RTPM             fax:   +43 (1) 27722 / 3955
Scheydgasse 41                      inet:  [EMAIL PROTECTED]
A-1210 Wien, Austria/Europe

Reply via email to