gnulib defines go in config-util.h, and we need to know whether to
provide duplicates in config.h or not.
Signed-off-by: Robbie Harwood
---
grub-core/disk/host.c| 2 +-
grub-core/gensymlist.sh | 1 +
grub-core/kern/emu/argp_common.c | 2 +-
gnulib defines go in config-util.h, and we need to know whether to
provide duplicates in config.h or not.
Signed-off-by: Robbie Harwood
---
grub-core/disk/host.c| 2 +-
grub-core/gensymlist.sh | 1 +
grub-core/kern/emu/argp_common.c | 2 +-
gnulib defines go in config-util.h, and we need to know whether to
provide duplicates in config.h or not.
Signed-off-by: Robbie Harwood
---
grub-core/disk/host.c| 2 +-
grub-core/gensymlist.sh | 1 +
grub-core/kern/emu/argp_common.c | 2 +-
gnulib defines go in config-util.h, and we need to know whether to
provide duplicates in config.h or not.
Signed-off-by: Robbie Harwood
---
grub-core/disk/host.c| 2 +-
grub-core/gensymlist.sh | 1 +
grub-core/kern/emu/argp_common.c | 2 +-
When generating video.lst, modules whose marker file contains the string
VIDEO_LIST_MARKER are selected. But when the marker file contains the CPP
defines, one of the defines is VIDEO_LIST_MARKER and is present in all
marker files, so they are all selected. By removing the defines, the correct
and installing the GRUB.
Where this document refers to packages names, they are named according to the
-Debian 11 package repositories.
+Debian 11 package repositories. These packages can be found by searching
+https://packages.debian.org/.
The Requirements
--
2.27.0
On Wed, Sep 08, 2021 at 07:57:53PM +, Glenn Washburn wrote:
> On Wed, 8 Sep 2021 18:03:50 +0200
> Daniel Kiper wrote:
>
> > On Wed, Sep 08, 2021 at 01:22:20AM +, Glenn Washburn wrote:
> > > It looks like the xfs_test test succeeds with tag grub-2.06-rc1a,
> > > fails with tag grub-2.06,
On Wed, 29 Jul 2020 19:00:18 +0200
Daniel Kiper wrote:
> From: Peter Jones
>
> This attempts to fix the places where we do the following where
> arithmetic_expr may include unvalidated data:
>
> X = grub_malloc(arithmetic_expr);
>
> It accomplishes this by do
On Wed, 8 Sep 2021 18:03:50 +0200
Daniel Kiper wrote:
> On Wed, Sep 08, 2021 at 01:22:20AM +, Glenn Washburn wrote:
> > It looks like the xfs_test test succeeds with tag grub-2.06-rc1a,
> > fails with tag grub-2.06, and succeeds with current master. Yes, as
> > expected. However, what this
> > > > >I'm adding the maintainers in CC. Carlos who commit the
> > > > > > > patch I'm fixing, agreed on the content.
> > > > > >
> > > > > > I didn't test the patch itself yet, but I've reproduced the
> > > > >
; > > issue. I was quite sure I had tested this patch on a V4 fs, but
> > > > > looks like I miscalculated the sizing. Thanks again. I'll try to
> > > > > test the patch here asap.
> > > >
> > > > Did you test this patch? If yes may I add
, agreed on the content.
> > > >
> > > > I didn't test the patch itself yet, but I've reproduced the
> > > > issue. I was quite sure I had tested this patch on a V4 fs, but
> > > > looks like I miscalculated the sizing. Thanks again. I'll try to
> >
the content.
> > > >
> > > > I didn't test the patch itself yet, but I've reproduced the
> > > > issue. I was quite sure I had tested this patch on a V4 fs, but
> > > > looks like I miscalculated the sizing. Thanks again. I'll try to
> >
ad tested this patch on a V4 fs, but
> > > looks like I miscalculated the sizing. Thanks again. I'll try to
> > > test the patch here asap.
> >
> > Did you test this patch? If yes may I add your Tested-by to it?
>
> Yup, patch works fine, just finished testing
Dear Michael,
Am 01.02.21 um 10:46 schrieb Michael Lawnick:
Am 22.01.2021 um 16:58 schrieb Paul Menzel:
I'm not (yet) in sync with grub timeline, when is next release planned
(last commit date)?
March *last* year sometime? ;-) I think the current date is March,
though re-reading the list
Am 22.01.2021 um 16:58 schrieb Paul Menzel:
I'm not (yet) in sync with grub timeline, when is next release planned
(last commit date)?
March *last* year sometime? ;-) I think the current date is March,
though re-reading the list posts, do not hold your breath, that it will
be committed, as the
Dear Michael,
Am 22.01.21 um 10:42 schrieb Michael Lawnick:
Am 22.01.2021 um 07:51 schrieb Paul Menzel:
Am 19.01.21 um 11:38 schrieb Michael Lawnick:
Q: where to place the efi driver, where to place the command line
handler.
Currently I'd say
- create grub-core/flash/efispinor.c
Am 22.01.2021 um 07:51 schrieb Paul Menzel:
Am 19.01.21 um 11:38 schrieb Michael Lawnick:
Q: where to place the efi driver, where to place the command line handler.
Currently I'd say
- create grub-core/flash/efispinor.c for the driver
I guess, that would be fine, but I found,
`grub-core/bus
more can we wish for. ;-)
I have made a driver and command line tool for accessing SPI NOR flash
via EFI interface which I would like to upstream.
Very nice.
Q: where to place the efi driver, where to place the command line handler.
Currently I'd say
- create grub-core/flash/efispinor.c
: where to place the efi driver, where to place the command line handler.
Currently I'd say
- create grub-core/flash/efispinor.c for the driver
- create grub-core/commands/efi/efispinor.c for the command line tool.
Is this acceptable?
Is there any specific branch where these files should go
This is primarily useful to do something like "loopback newdev (dev)8+" to
create a device that skips the first 4K, which may contain a non-standard
RAID1 header that grub does not recognize. This would allow that initial
data to be accessed and potentially mounted by grub up to the rest of the
From: Glenn Washburn
This is primarily useful to do something like "loopback newdev (dev)8+" to
create a device that skips the first 4K, which may contain a non-standard
RAID1 header that grub does not recognize. This would allow that initial
data to be accessed and potentially mounted by grub
From: Peter Jones
This attempts to fix the places where we do the following where
arithmetic_expr may include unvalidated data:
X = grub_malloc(arithmetic_expr);
It accomplishes this by doing the arithmetic ahead of time using grub_add(),
grub_sub(), grub_mul() and testing for overflow
Going through the list of gitignore patterns without a leading slash,
this adds a leading slash where it appears to have been forgotten.
Some gitignore patterns like ".deps/" or "Makefile" clearly should
match everywhere, so those definitively need no leading slash.
Fo
Going through the list of gitignore patterns without a leading slash,
this adds a leading slash where it appears to have been forgotten.
Some gitignore patterns like ".deps/" or "Makefile" clearly should
match everywhere, so those definitively need no leading slash.
Fo
On Thu, Apr 30, 2020 at 09:54:52PM +0200, Hans Ulrich Niedermann wrote:
> Going through the list of gitignore patterns without a leading slash,
> this adds a leading slash where it appears to have been forgotten.
>
> Also, for patterns matching directories, add a trailing slash.
I
Going through the list of gitignore patterns without a leading slash,
this adds a leading slash where it appears to have been forgotten.
Also, for patterns matching directories, add a trailing slash.
Some gitignore patterns like ".deps/" or "Makefile" clearly should
match
Going through the list of gitignore patterns without a slash, this
adds a leading slash where it appears to have been forgotten.
Some gitignore patterns like .deps/ or Makefile clearly should
match everywhere, so those definitively need no leading slash.
For some patterns like contrib
On Wed, Jul 04, 2018 at 08:33:00AM -0500, David Wyckoff wrote:
> Good day and howdy,
>
> I am interested in knowing how grub gets its initial screen size.
> The example:
>
> insert live cd (et al)
> install distro
> install grub to mbr ---
>
> Does grub get it's initial framebuffer/screen
Good day and howdy,
I am interested in knowing how grub gets its initial screen size.
The example:
insert live cd (et al)
install distro
install grub to mbr ---
Does grub get it's initial framebuffer/screen settings from the
running kernel during install? and from which kernel
I'm looking for the line of code where GRUB2 finally jumps to kernel code and thus hands over execution on x86 systems? I guess it's in an assembler file since this is very low architecture stuff. I looked at the source files in /grub-core/boot/i386/pc/*.S and found a JMP in boot.S at line 455
On Thu, Sep 03, 2015 at 02:49:45PM +0200, de...@gmx.de wrote:
>
Plain-text mail would be appreciated, or at least mail with a text/plain
part.
> I'm looking for the line of code where GRUB2 finally jumps to kernel
> code and thus hands over execution on x86 systems? I g
Hello All,
I'm reading grub2 source code and trying to understand where it jumps
to linux code? Is it grub_relocator32_boot/grub_relocator16_boot or
something else?
Thank you.
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org
В Sat, 29 Nov 2014 19:17:49 +0600
Alexander Kuleshov kuleshovm...@gmail.com пишет:
Hello All,
I'm reading grub2 source code and trying to understand where it jumps
to linux code? Is it grub_relocator32_boot/grub_relocator16_boot or
something else?
For i386 - yes.
Thank you
On Mon, May 13, 2013 at 03:54:46PM -0400, Lennart Sorensen wrote:
On Mon, May 13, 2013 at 11:43:50AM -0700, Bruce Korb wrote:
Well, my distro (openSuSE) generates a special entry for rescue
mode, too. But it rescues me into run level 5. init 3 will,
indeed, drop me back to multi-user and
Hi,
On Mon, May 13, 2013 at 12:54 PM, Lennart Sorensen
lsore...@csclub.uwaterloo.ca wrote:
Well runlevels and their meanings are a user space issue. 1 is only
single user by tradition, it doesn't have to be.
single user is meaningful only by tradition in the UNIX environment
and GRUB is OS
On 14.05.2013 18:33, Bruce Korb wrote:
Whatever. No indicator
that pressing e does anything, but pressing e gets you to an
edit-the-menu-entry screen.
Read at the bottom of the screen.
For folks who just want to get their Linux
up and running, requiring them to learn and understand the
dog vomit firmware in the world, users would direct their
irritation elsewhere, where it properly belongs. But then we'd also have far
fewer bootable systems.
Chris Murphy
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman
I've been Googling around to no particular avail. I have this
_really_ difficult problem. I need to boot into single user mode and
GRUB2 has made it so difficult that I am unable to accomplish that. I
am sure there are reasons for obscuring the obvious in this way, but
such reasons escape me.
On Mon, May 13, 2013 at 09:24:34AM -0700, Bruce Korb wrote:
I've been Googling around to no particular avail. I have this
_really_ difficult problem. I need to boot into single user mode and
GRUB2 has made it so difficult that I am unable to accomplish that. I
am sure there are reasons for
В Mon, 13 May 2013 13:07:14 -0400
Lennart Sorensen lsore...@csclub.uwaterloo.ca пишет:
On Mon, May 13, 2013 at 09:24:34AM -0700, Bruce Korb wrote:
I've been Googling around to no particular avail. I have this
_really_ difficult problem. I need to boot into single user mode and
GRUB2 has
On Mon, May 13, 2013 at 10:09:41PM +0400, Andrey Borzenkov wrote:
Do you suggest to create extra menu entries for every possible
combination of kernel parameters?
Yes. It's not grub's job to know everything about a linux kernel,
or bsd kernel or whatever else you might want to pass.
Runlevels
Hi,
On Mon, May 13, 2013 at 11:16 AM, Lennart Sorensen
lsore...@csclub.uwaterloo.ca wrote:
Debian auto generates a grub.cfg just fine with a rescue option for each
kernel detected which does single user mode. It does other options too
if you ask it to. Pretty darn simple to use.
Well, my
On Mon, May 13, 2013 at 11:43:50AM -0700, Bruce Korb wrote:
Well, my distro (openSuSE) generates a special entry for rescue
mode, too. But it rescues me into run level 5. init 3 will,
indeed, drop me back to multi-user and init 1 back to single user,
but without a reboot, various
On May 13, 2013, at 12:16 PM, Lennart Sorensen lsore...@csclub.uwaterloo.ca
wrote:
Not really. Editing in grub2 is not that different from grub 0.97
(although it is slightly different).
Slightly different are the syntax changes between versions of GRUB 1.xx that
caused even grubby to
On Mon, May 13, 2013 at 12:39:39PM -0600, Chris Murphy wrote:
Slightly different are the syntax changes between versions of GRUB 1.xx that
caused even grubby to puke. The difference in syntax between 0.97 and 2 are
monumental, unless you're a scripting nerd. If you're a regular user, the
El dl 13 de 05 de 2013 a les 11:43 -0700, en/na Bruce Korb va escriure:
I have learned that in the grub2 menu mode, you can press e and all
of a sudden you can edit the command line. It seems my request boils
down to some documentation. In the menu code so when I'm looking at
the menu, there
Hi， ALL：
I want to know the GRUB architecture and the source files
relations, and want to know more information on GRUB implementation.
So does some design documents are avaliable? Thanks ALL
Best Regards
Bai shuwei
--
Love other people, as same as love yourself!
Don't think all the time,
On Thu, 2009-07-02 at 10:49 +0800, zhang Peter wrote:
Does anybody know how to get grub2 devel roadmap?
I'd like to take a look at it and decide how to join this open
project. Thanks!
There is no official roadmap. The closest thing to that would be the
TODO list on the GRUB wiki:
Hello
On Thu, Jul 2, 2009 at 7:57 PM, Pavel Roskinpro...@gnu.org wrote:
On Thu, 2009-07-02 at 10:49 +0800, zhang Peter wrote:
Does anybody know how to get grub2 devel roadmap?
I'd like to take a look at it and decide how to join this open
project. Thanks!
There is no official roadmap. The
Does anybody know how to get grub2 devel roadmap?
I'd like to take a look at it and decide how to join this open project.
Thanks!
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
Hi,
I have one usb devices with one to four luns.
Operating system like linux can be installed on a lun.
I don't know this lun. No problem for that, Grub is OK.
It is an installer decision and I can't make this mandatory.
My problem : Some machines have no usb boot possibility.
For that, I use
From: David Miller da...@davemloft.net
Date: Sun, 19 Apr 2009 17:24:54 -0700 (PDT)
2009-04-19 David S. Miller da...@davemloft.net
* kern/ieee1275/mmap.c (grub_machine_mmap_iterate): If size_cells
is larger than address_cells, use that value for address_cells too.
Committed.
Under OpenBoot on sparc64:
The value of the #address-cells property in the root node is the
default value of 2. The value of the #size-cells property in the root
node is the non-default value 2. (NOTE: Since the #address-cells property
value in the root node is the default value
Robert Millan wrote:
On Wed, Feb 11, 2009 at 06:01:42PM -0500, BandiPat wrote:
Hey guys, where does it specify the initial screen border title?
(GNU GRUB version 1.96)
I would at least like to change that for the Zenwalk build, if that's
ok? I've looked in several pieces of the code
On Wed, Feb 11, 2009 at 06:01:42PM -0500, BandiPat wrote:
Hey guys, where does it specify the initial screen border title?
(GNU GRUB version 1.96)
I would at least like to change that for the Zenwalk build, if that's
ok? I've looked in several pieces of the code, but can't seem to find
./configure:577:PACKAGE_VERSION='1.96'
BandiPat wrote:
Hey guys, where does it specify the initial screen border title?
(GNU GRUB version 1.96)
I would at least like to change that for the Zenwalk build, if that's
ok? I've looked in several pieces of the code, but can't seem to find
, Yoshinori K. Okuji [EMAIL PROTECTED] wrote:
On Monday 12 February 2007 08:42, Jerone Young wrote:
This patch fixes the situation with i386-pc where grub-probe
grube-setup are searching for the root fs for grub files and they
happen to be on the same file system as the root (/) filesystem
On Monday 12 February 2007 08:42, Jerone Young wrote:
This patch fixes the situation with i386-pc where grub-probe
grube-setup are searching for the root fs for grub files and they
happen to be on the same file system as the root (/) filesystem. If
this is the case if when probing /dev
wrote:
This patch fixes the situation with i386-pc where grub-probe
grube-setup are searching for the root fs for grub files and they
happen to be on the same file system as the root (/) filesystem. If
this is the case if when probing /dev , if the partition is a sd* it
will not find it because
60 matches
Mail list logo
