Re: [RFC] Allow separate boot block and core.img location?

2014-01-16 Thread Chris Murphy
On Jan 16, 2014, at 7:13 PM, joe faith wrote: > >> >> - Original Message - >> From: Chris Murphy >> Sent: 01/16/14 04:04 PM >> To: The development of GNU GRUB >> Subject: Re: [RFC] Allow separate boot block and core.img location? >> >> Is there a good reason why we don't have a sepa

[PATCH] Ignore EPERM when modifying kern.geom.debugflags

2014-01-16 Thread Colin Watson
Many tests fail when run as a non-root user on FreeBSD. The failures all amount to an inability to open files using grub_util_fd_open, because we cannot set the kern.geom.debugflags sysctl. This sysctl is indeed important to allow us to do such things as installing GRUB to the MBR, but if we need

Re: [RFC] Allow separate boot block and core.img location?

2014-01-16 Thread joe faith
- Original Message - From: Chris Murphy Sent: 01/16/14 04:04 PM To: The development of GNU GRUB Subject: Re: [RFC] Allow separate boot block and core.img location? Is there a good reason why we don't have a separate partition for core.img? It doesn't seem like it's an OK idea for anything

Re: [RFC] Allow separate boot block and core.img location?

2014-01-16 Thread Chris Murphy
> From: Andrey Borzenkov > Sent: 12/16/13 02:36 PM > To: grub-devel@gnu.org > Subject: [RFC] Allow separate boot block and core.img location? > > There are many users using dual boot with Windows and Linux. In this > configuration installing grub in MBR unfortunately breaks at least some > up

Re: grub-shell: Pass -no-pad to xorriso when building floppy images

2014-01-16 Thread Thomas Schmitt
Hi, > I think it is enough to say that everything after first "--" is passed > onto xorriso. The fact that second "--" will enter native xorriso is > documented in xorriso manual; anyone who would like to make use of this > feature probably knows it. This becomes quite confusing by the fact that

Re: grub-shell: Pass -no-pad to xorriso when building floppy images

2014-01-16 Thread Andrey Borzenkov
В Thu, 16 Jan 2014 19:56:16 +0100 "Thomas Schmitt" пишет: > Hi, > > > There is no second "--". grub-mkrescue --help tries to say, that > > everything after "--" is simply passed on to xorriso. What is > > confusing, is "or any of the mkisofs options" in previous sentence > > which implies that "

Re: grub-shell: Pass -no-pad to xorriso when building floppy images

2014-01-16 Thread Thomas Schmitt
Hi, > There is no second "--". grub-mkrescue --help tries to say, that > everything after "--" is simply passed on to xorriso. What is > confusing, is "or any of the mkisofs options" in previous sentence > which implies that "--" is not needed. It used to work the way which is still in the docs.

Re: grub-shell: Pass -no-pad to xorriso when building floppy images

2014-01-16 Thread Andrey Borzenkov
В Thu, 16 Jan 2014 17:28:32 +0100 "Thomas Schmitt" пишет: > Hi, > > > xorriso -list_delimiter +xorriso-native+ > > It comes to me that it would be easier to document that the > first "--" brings you out of grub-mkrescue option interpretation > and that the second "--" brings you into xorriso

Re: [RFC] Allow separate boot block and core.img location?

2014-01-16 Thread joe faith
May I also suggest that "--core-img-location" parameter accept a block-list in some format, in addition to the device identifier?grub-install --boot-block-location=/dev/sda --core-img-location=/dev/sda[63+1985] => embed core image in the 1985 sectors starting at LBA 63 on /dev/sda This would be

Re: grub-shell: Pass -no-pad to xorriso when building floppy images

2014-01-16 Thread Thomas Schmitt
Hi, > xorriso -list_delimiter +xorriso-native+ It comes to me that it would be easier to document that the first "--" brings you out of grub-mkrescue option interpretation and that the second "--" brings you into xorriso native command mode. I.e. no change in grub-mkrescue, no -list_delimiter +

Re: grub-shell: Pass -no-pad to xorriso when building floppy images

2014-01-16 Thread Thomas Schmitt
Hi, > > mkrescue_args="${mkrescue_args} -no-pad" > This doesn't work for me: > ./grub-mkrescue: invalid option -- 'n' So the documentation seems not to match the implementation. http://git.savannah.gnu.org/cgit/grub.git/tree/docs/grub.texi "All arguments not explicitly listed as @command{g

Re: grub-shell: Pass -no-pad to xorriso when building floppy images

2014-01-16 Thread Colin Watson
On Thu, Jan 16, 2014 at 03:05:44PM +0100, Thomas Schmitt wrote: > Hi, > > > +mkrescue_args="${mkrescue_args} -- -no-pad" > > This "--" is most probably not what you want. [...] > mkrescue_args="${mkrescue_args} -no-pad" This doesn't work for me: + pkgdatadir=. ./grub-mkrescue --output=/

Re: grub-shell: Pass -no-pad to xorriso when building floppy images

2014-01-16 Thread Thomas Schmitt
Hi, > +mkrescue_args="${mkrescue_args} -- -no-pad" This "--" is most probably not what you want. man grub-mkrescue says (and xorriso indeed does it): "Option -- switches to native xorriso command mode." But -no-pad is not a native xorriso command. $ xorriso -as mkisofs -- -no-pad thr

[PATCH] grub-shell: Pass -no-pad to xorriso when building floppy images

2014-01-16 Thread Colin Watson
The floppy images built by grub-shell are currently just over the floppy limit, and the Debian patch set plus the 915resolution extra bring this up to the point where GRUB tries to actually read past the floppy limit, breaking fddboot_test. Passing -no-pad buys us 300KiB, which should keep us goin