bugGNU GRUB - Bugs: bug #1644, remote (network) controllable...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #1644: remote (network) controllable bootmenu

Submitter:  Invalid User ID <#12431>
Submitted:  Fri 08 Nov 2002 11:27:46 AM UTC
   
 
Category:  Network Severity:  Ordinary
Priority:  3 - Low Item Group:  Feature Request
Status:  None Privacy:  Public
Assigned to:  None Originator Name: 
Open/Closed:  Closed Release:  None
Release:  x Reproducibility:  Every Time
Planned Release:  None

Sat 15 Dec 2007 11:48:14 AM UTC, comment #5: 

We've moved to GRUB 2 as a development platform.  Unfortunately, GRUB 2 doesn't have network support yet, although there's ongoing work to implement it.  If you want to help on that, please contact <grub-devel@gnu.org>.

In the meantime, this bug doesn't apply.  I'm closing it.

Robert Millan <robertmh>
Group administrator
Tue 30 Dec 2003 09:18:03 PM UTC, comment #4: 

How is this for a protocol ...

1. after reading the configuration file (possibly specified ion option 150) grub sends out udp packets (brodcast or unicast to a machine specified in the config file) containing a url pointing to the config file. (i.e. tftp://192.168.0.1/tftpboot/default.gcf) the packet would be retransmited at regular intrivals (maby twice a second) until a timeout occurs or a response arives.

2. a running machine which may or may not have recieved the packet specified in step one sends an unicast udp packet to the booting machine containing the url in the first packet and a intiger specifying the menu choice. This packet may be retransmited if packet loss is suspected.

3. the booting machine upon reciept of the selection packet sends at least three response packets to the machine which sent the select packet. The three packets should not be transmited consecutivly. One should be transmited imeadiatly and the aditional packets may be transmited to indicate completion of various activities (i.e. loading a kernal or initrd). The format of this response packet would contain the url from the first packet, the number from the second and a null terminated string encoded in utf8 intended for logging or desplay to the user.

As a further sugestion as to the format of the packets I am including the folowing header structure which should imeadiatly begin the data portion of the udp packet.

struct grub_menu_packet {
   char[4]    magic;    /* the charcters 'GRUB' */
   unsigned   url:16;   /* offset from the data block to the begining of the null terminated string containing the url */
   unsigned   select:16 /* the menu option selectd or zero when requesting selection */
   unsigned   log:16    /* offset from the data block to the begining of the null terminated string containing the text string or zero when not present */
};

                                 Warmest regards,
                                 Ben Hildred
                                 hildred at peakpeak dot net

Anonymous
Fri 22 Nov 2002 11:48:09 AM UTC, comment #3: 

It isn't so important what kind of protocol a network console
protocol will be based on. I'm waiting for someone to define
it.

Okuji

Yoshinori K. Okuji <okuji>
Group administrator
Fri 22 Nov 2002 11:24:23 AM UTC, comment #2: 

As I see it there are two ways:
1) Abuse tftp (RFC1350)
2) use RUDP (RDP) (RFC1151) (not to be mistaken with Remote Desktop Protocol (RDP) from the evil empire)

The 1st is probably easier to do (lot's of the code is already in) but ugly from a softdesign prospective.
The 2nd would be be harder to implement. No other concerns at the moment.

Invalid User ID <#12431>
Fri 08 Nov 2002 05:20:26 PM UTC, comment #1: 

This has already been discussed several times in bug-grub.

Unfortunately, I cannot find my own message about this from
the archive, so I say the same thing once again:

Please design a good and simple protocol. You must consider
that UDP packets can disappear by accident.

Thanks,
Okuji

Yoshinori K. Okuji <okuji>
Group administrator
Fri 08 Nov 2002 11:27:46 AM UTC, original submission:  

I'm using Wake-On-LAN to power on my machine and I'm able to power down it again using halt -p under linux for example. However what I can't do is to remotely select a different operating system (well I can log into my linux box modify the menu.lst and rebootm but I have no access to it from FreeBSD for example, I'm using reiserfs)
As there is already basic networking in, terminal code in (for serial control) I think it should be easy to make config options to allow connections from a specified host/network at a defined port. Then I could telnet there (I know plaintext.., but I trust my network) and use the menu as with the serial console, nothing fancy..
I think this would make GRUB the first choice bootmanager for all WOL guys.

Invalid User ID <#12431>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by robertmh (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2007-12-15 robertmh Open/ClosedOpen Closed
        Release x
    2002-11-08 okuji SeverityMajor None
        Priority100 (Error - Not Found) None

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code