Re: Switching to another boot device on failure
Switching to the next boot device should not be done without advertising the user, so that he or she has the opportunity to fix the primary device's booting process. By the way, how is the "recordfail" environment variable reset ? And wouldn't it be possible to implement a "next_boot_device" environment variable to answer Venkata's need ? Arbiel Le 19/11/2014 04:16, Andrei Borzenkov a écrit : > В Tue, 18 Nov 2014 10:51:00 + (UTC) > Venkata Subbarao пишет: > >> Hi All, >> >> I am working on a task on XUbuntu OS in which due to any reason if booting >> fails I would like to switch to another boot device by zeroing the MBR of >> current boot disk. Is this possible ? >> >> For example instead of showing following prompt, I would like to zero out >> the MBR so that the BIOS can select next boot device upon reset. >> >> error: no such partition >> grub rescue> >> > grub supports only very limited and controlled ways to write to > device/file. Doing something like this in unattended manner is probably > way too dangerous. > > What would be possible is to optionally exit grub (after timeout) in > this case; then BIOS should proceed to next boot device. > > ___ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel signature.asc Description: OpenPGP digital signature ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: IDE compilation
On Tuesday, November 18, 2014, Michael Heng wrote: > Hello, > > I want to know what a IDE do you all use? I just have download the grub 2 > project. Can you advise me how to setting up eclipse to import as a > project, how can I debug it? > Please, don't post mail in HTML format. That's not good manners. As I stated to you on help-grub, low-level projects like GRUB are typically built without IDEs, as they can get in the way. In you want to debug, use a hardware debugger or go old school and use print statements. It's surprisingly effective, considering you can't typically develop code the "normal" way with a boot loader as low-level as GRUB. There is limited for x86 debugging with gdb, but this isn't documented all that well (GRUB's documentation is falling behind). > > Kindly regards > > > Michael > ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
HTTP with other ports
Has anyone come up with a general way to change the port number in the http module? Right now it is hard coded to be 80, but it is very common to do HTTP over another port number. I was thinking about extending the device name syntax for network devices and/or adding a 'default port' (with a command to set it) to go with default server. I did an implementation that works for my needs but don't think it is a good general purpose implementation. Has anyone else done work here or have ideas for using alternate port numbers with HTTP? alan ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: HTTP with other ports
В Wed, 19 Nov 2014 08:54:24 -0800 Alan Perry пишет: > Has anyone come up with a general way to change the port number in the http > module? Right now it is hard coded to be 80, but it is very common to do HTTP > over another port number. > > I was thinking about extending the device name syntax for network devices Does protocol,server:port conflict with anything? (http,server:1234)/foo > and/or adding a 'default port' (with a command to set it) to go with default server. I did an implementation that works for my needs but don't think it is a good general purpose implementation. > > Has anyone else done work here or have ideas for using alternate port numbers > with HTTP? > > alan > > > ___ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: HTTP with other ports
On 11/19/14, 9:09 AM, Andrei Borzenkov wrote: В Wed, 19 Nov 2014 08:54:24 -0800 Alan Perry пишет: Has anyone come up with a general way to change the port number in the http module? Right now it is hard coded to be 80, but it is very common to do HTTP over another port number. I was thinking about extending the device name syntax for network devices Does protocol,server:port conflict with anything? (http,server:1234)/foo I separated the server from the port with a comma because that is how the protocol is separated from server. I don't think either syntax conflicts with anything else, but I haven't been working with enough different parts of GRUB2 to really know. In my previous note, I mentioned a command for setting the default server, but I was really talking about the net_default_server env variable. Thinking about it, an alternate default port doesn't make sense because you really need to know its protocol as well. Maybe a default protocol or protocol/port env variable that includes both allows the alternate port for the protocol to be specified? alan and/or adding a 'default port' (with a command to set it) to go with default server. I did an implementation that works for my needs but don't think it is a good general purpose implementation. Has anyone else done work here or have ideas for using alternate port numbers with HTTP? alan ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: HTTP with other ports
В Wed, 19 Nov 2014 09:27:00 -0800 Alan Perry пишет: > On 11/19/14, 9:09 AM, Andrei Borzenkov wrote: > > В Wed, 19 Nov 2014 08:54:24 -0800 > > Alan Perry пишет: > > > >> Has anyone come up with a general way to change the port number in the > >> http module? Right now it is hard coded to be 80, but it is very common to > >> do HTTP over another port number. > >> > >> I was thinking about extending the device name syntax for network devices > > Does protocol,server:port conflict with anything? (http,server:1234)/foo > > I separated the server from the port with a comma Do you have implementation? Then send a patch for review. > because that is how > the protocol is separated from server. I don't think either syntax > conflicts with anything else, Actually ':' does conflict with IPv6. > but I haven't been working with enough > different parts of GRUB2 to really know. > > In my previous note, I mentioned a command for setting the default > server, but I was really talking about the net_default_server env > variable. Thinking about it, an alternate default port doesn't make > sense because you really need to know its protocol as well. Maybe a > default protocol or protocol/port env variable that includes both allows > the alternate port for the protocol to be specified? > Does not set root=protocol,server,[?port] do exactly that? > alan > > > > >> and/or adding a 'default port' (with a command to set it) to go with > > default server. I did an implementation that works for my needs but > > don't think it is a good general purpose implementation. > >> Has anyone else done work here or have ideas for using alternate port > >> numbers with HTTP? > >> > >> alan > >> > >> > >> ___ > >> Grub-devel mailing list > >> Grub-devel@gnu.org > >> https://lists.gnu.org/mailman/listinfo/grub-devel > > > > ___ > > Grub-devel mailing list > > Grub-devel@gnu.org > > https://lists.gnu.org/mailman/listinfo/grub-devel > > > ___ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: HTTP with other ports
On 11/19/14, 10:22 AM, Andrei Borzenkov wrote: В Wed, 19 Nov 2014 09:27:00 -0800 Alan Perry пишет: On 11/19/14, 9:09 AM, Andrei Borzenkov wrote: В Wed, 19 Nov 2014 08:54:24 -0800 Alan Perry пишет: Has anyone come up with a general way to change the port number in the http module? Right now it is hard coded to be 80, but it is very common to do HTTP over another port number. I was thinking about extending the device name syntax for network devices Does protocol,server:port conflict with anything? (http,server:1234)/foo I separated the server from the port with a comma Do you have implementation? Then send a patch for review. It is more like prototype code and I need to clean it up. because that is how the protocol is separated from server. I don't think either syntax conflicts with anything else, Actually ':' does conflict with IPv6. but I haven't been working with enough different parts of GRUB2 to really know. In my previous note, I mentioned a command for setting the default server, but I was really talking about the net_default_server env variable. Thinking about it, an alternate default port doesn't make sense because you really need to know its protocol as well. Maybe a default protocol or protocol/port env variable that includes both allows the alternate port for the protocol to be specified? Does not set root=protocol,server,[?port] do exactly that? Yes, it can be done that way. But I was wondering if there needs to be an protocol/port variant of net_default_server. Or do I not understand the intended use of net_default_server? alan and/or adding a 'default port' (with a command to set it) to go with default server. I did an implementation that works for my needs but don't think it is a good general purpose implementation. Has anyone else done work here or have ideas for using alternate port numbers with HTTP? alan ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: HTTP with other ports
В Wed, 19 Nov 2014 13:23:05 -0800 Alan Perry пишет: > On 11/19/14, 10:22 AM, Andrei Borzenkov wrote: > > В Wed, 19 Nov 2014 09:27:00 -0800 > > Alan Perry пишет: > > > >> On 11/19/14, 9:09 AM, Andrei Borzenkov wrote: > >>> В Wed, 19 Nov 2014 08:54:24 -0800 > >>> Alan Perry пишет: > >>> > Has anyone come up with a general way to change the port number in the > http module? Right now it is hard coded to be 80, but it is very common > to do HTTP over another port number. > > I was thinking about extending the device name syntax for network devices > >>> Does protocol,server:port conflict with anything? (http,server:1234)/foo > >> I separated the server from the port with a comma > > Do you have implementation? Then send a patch for review. > > It is more like prototype code and I need to clean it up. > > > > >>because that is how > >> the protocol is separated from server. I don't think either syntax > >> conflicts with anything else, > > Actually ':' does conflict with IPv6. > > > >>but I haven't been working with enough > >> different parts of GRUB2 to really know. > >> > >> In my previous note, I mentioned a command for setting the default > >> server, but I was really talking about the net_default_server env > >> variable. Thinking about it, an alternate default port doesn't make > >> sense because you really need to know its protocol as well. Maybe a > >> default protocol or protocol/port env variable that includes both allows > >> the alternate port for the protocol to be specified? > >> > > Does not > > > > set root=protocol,server,[?port] > > > > do exactly that? > > Yes, it can be done that way. But I was wondering if there needs to be > an protocol/port variant of net_default_server. Or do I not understand > the intended use of net_default_server? > Initially grub did not support (proto,server) syntax for net devices so default_server was the only way to change server. Today it is mostly to record result of PXE auto configuration. Set support is there for legacy usage, but I do not see any need to extend it. > alan > > > > and/or adding a 'default port' (with a command to set it) to go with > >>> default server. I did an implementation that works for my needs but > >>> don't think it is a good general purpose implementation. > Has anyone else done work here or have ideas for using alternate port > numbers with HTTP? > > alan > > > > > ___ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel