[Bug #793] Grub cannot work with memdisk

[nobody]

=================== BUG #793: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=793&group_id=68

Changes by: Yoshinori K. Okuji <address@hidden>
Date: 2002-Jul-03 14:13 (GMT)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Invalid
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
I mark this report as invalid, because there is no
information about the reporter and no useful fact.

Why not login? Why not reading how to report bugs?

Okuji



=================== BUG #793: FULL BUG SNAPSHOT ===================


Submitted by: None                      Project: grub                           
Submitted on: 2002-Jul-03 13:31
Category:  Booting                      Severity:  Major                        
Priority:  None                         Bug Group:  Feature Request             
Resolution:  Invalid                    Assigned to:  None                      
Status:  Closed                         Release:  0.92                          
Reproducibility:  Every Time            Planned Release:                        

Summary:  Grub cannot work with memdisk

Original Submission:  Memdisk is a utility from the syslinux project which 
allows
a bootloader to set up a ramdisk image of a floppy or
hard disk.  It allows us to boot, for example, DOS from
a virtual floppy, which is very useful for maintaining
machines we have here.  Syslinux treats memdisk as a
Linux kernel and the disk image as a ramdisk.  Grub sees
memdisk as a linux kernel, but if we attempt to boot
it with an image as initrd, it just hangs.  Samples
can be provided on request.

Follow-up Comments
*******************

-------------------------------------------------------
Date: 2002-Jul-03 14:13             By: okuji
I mark this report as invalid, because there is no
information about the reporter and no useful fact.

Why not login? Why not reading how to report bugs?

Okuji




No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=793&group_id=68