On Thu 2017-09-21 10:26:08 -0400, Daniel Kahn Gillmor wrote:
> I like this idea but i don't have a lot of spare machines handy to try
> d-i on these days. I can try to dig up a power supply for an idle older
> ppc laptop i've got floating around, but i don't know whether i'll be
>
On Thu 2017-09-21 14:21:52 +0200, John Paul Adrian Glaubitz wrote:
> I would help with this transition to use GRUB on powerpc as well
> as on ppc64 which we are now providing unofficial installation
> for in Debian Ports [1].
>
> I do have commit access to debian-installer and its components
> as
nus all have numbers *in* their title; furthermore, there is no
example given about how to choose the number, or any indication about
whether counting is zero-indexed or 1-indexed.
Having a cleaner example and presenting all variants (numeric, title,
and id) should make it clearer to the user.
Signed
nderstandable. I've
also assumed that the number counting starts at 1, but haven't
verified that. If that's wrong, please commit the corrected version
:)
Signed-off-by: Daniel Kahn Gillmor <d...@fifthhorseman.net>
---
docs/grub.texi | 20 ++--
1 file changed, 10 insertions
nderstandable. I've
also assumed that the number counting starts at 1, but haven't
verified that. If that's wrong, please commit the corrected version
:)
Signed-off-by: Daniel Kahn Gillmor <d...@fifthhorseman.net>
---
docs/grub.texi | 20 ++--
1 file changed, 10 insertions
Hi grub folks--
Is there a way that a grub script (or the grub commandline) can report
the amount of available memory?
It seems like it would be useful in situations like a liveCD or bootable
image that might want to warn the user up front if the available RAM is
smaller than the advertised
On Thu 2015-10-29 13:46:42 -0400, christopher.to...@riseup.net wrote:
> No, since I type the line in manually every time, it is not located
> anywhere for it to be discovered and need denying. I know my system very
> well. I know if I put one USB drive into a slot, it will be named
> (USB0). If
On Fri 2015-03-27 08:27:42 -0400, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
@@ -1856,7 +1859,7 @@ grub_install_generate_image (const char *dir, const
char *prefix,
head-magic = image_target-bigendian ? grub_host_to_target16 (0x160)
: grub_host_to_target16 (0x166);
Variant timestamps make some grub platforms produce non-deterministic
core images. This makes it difficult to use simple tools to audit the
stability of a system with grub installed.
This patch selects a single timestamp to use for these embedded
timestamps so that the core images will be
I'm using grub-efi on a debian amd64 system, with the ESP mounted at
/boot/efi.
when i run:
grub-install
the digest of /boot/efi/EFI/debian/grubx64.efi changes:
root@pops:~# sha1sum /boot/efi/EFI/debian/grubx64.efi
eafbe63218ecb7f7e69522e55ff7bc9551002c08 /boot/efi/EFI/debian/grubx64.efi
On Fri 2015-03-20 11:25:25 -0400, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
I've already detailed in another post in another post why embedding 0 is
probably bad and that it's better to embed either 2015-01-01 00:00:00 or
the date of last commit which can be put into modinfo.sh during
On 12/05/2013 04:20 PM, Jonathan McCune wrote:
On Thu, Dec 5, 2013 at 10:10 AM, Colin Watson cjwat...@ubuntu.com wrote:
I think we should identify the call sites that really need restricted
permissions, explicitly lock them down, and open things back up for
everything else.
I agree that
On 10/22/2013 02:24 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
GIT repo is up and running now it's main repo. You can commit your
patches to it. Keep a copy of any patch you commit in case I have to
reimport repository.
Thank you for doing this maintenance work, phcoder! As a user of
hi there--
i'm trying to boot a machine with grub-pc 2.00-19 (from debian sid), off
of two SATA disks connected to a PCIe controller.
The PCIe controller is a SYBA SI-PEX40064, and upon boot it announces
itself as:
Marvell 88SE92xx Adapter - BIOS Version 1.0.0.1010
PCIe x1 2.5Gbps
Mode:
On 06/24/2013 06:27 AM, Mikko Rantalainen wrote:
I'd suggest trying to apply the workflow used by git development for
grub, too.
While i don't expect my opinion to have any particular weight (i'm
mostly a bug reporter and tester in this community) i would also be
happy to see a switch from bzr
On 04/07/2013 02:22 AM, Andrey Borzenkov wrote:
В Sun, 07 Apr 2013 00:04:08 -0400 Daniel Kahn Gillmor
d...@fifthhorseman.net пишет:
[...]
missing file grub-core/gnulib/getopt1.c
Do you actually have this file? Just to be sure?
hm, good call, the file wasn't there. after checking
hi grub folk--
I'm trying to build grub from the current bzr head on a powerpc64 debian
unstable system. I'm afraid i'm getting stuck right at the beginning,
as i try to autogen:
0 dkg@reason:~/src/grub/grub$ ./autogen.sh
Importing unicode...
Importing libgcrypt...
Creating Makefile.tpl...
hi folks--
https://www.gnu.org/software/grub/manual/grub.html appears to be
generated from 2.00~rc1. Given that 2.00 has been out for a while now,
it seems like the online docs should probably be updated to match.
Thanks for all the work on grub!
Regards,
--dkg
On 09/25/2012 03:09 PM, Seth Goldberg wrote:
Is it possible that debian mismerged some changes from 2.00?
no, i don't think so. the tarball that debian's 2.00-5 package i used
has this sha1 sum:
274d91e96b56a5b9dd0a07accff69dbb6dfb596b ../grub2_2.00.orig.tar.xz
which is the same as the
On Sat, 07 Apr 2012 01:36:44 -0400, Daniel Kahn Gillmor
d...@fifthhorseman.net wrote:
In particular, i suspect that *after* the bootloader has turned over
control to the kernel (memtest in this case), the PXE-driven NIC is
continuing to DMA received packets into active RAM.
phcoder sent me
I've been recently using grub.pxe (from debian's version 1.99-17)
according to the instructions at [0] to boot memtest86+ [1] (from
debian's version 4.20-1.1) over the network on x86 machines. Due to the
problems described below, i'm using a serial console.
The grub configuration is very simple:
according to the man page and grub-mknetdir --help, the usage is:
grub-mknetdir [OPTION] install_device
But it's not clear what the install_device should refer to, since you're
really just preparing a directory -- there's no device needed, afaict.
Can someone explain the need for this
On Sat, 25 Feb 2012 16:49:00 -0500, Daniel Kahn Gillmor
d...@fifthhorseman.net wrote:
On Thu, 23 Feb 2012 06:43:23 +0100, Vladimir 'φ-coder/phcoder' Serbinenko
phco...@gmail.com wrote:
[dkg wrote:]
Select the smallest known block device that can completely enclose the
RAID member
On Thu, 23 Feb 2012 06:43:23 +0100, Vladimir 'φ-coder/phcoder' Serbinenko
phco...@gmail.com wrote:
[dkg wrote:]
Select the smallest known block device that can completely enclose the
RAID member. The larger block device(s) should not be considered to be
exporting that RAID.
phcoder
On Thu, 23 Feb 2012 06:43:23 +0100, Vladimir 'φ-coder/phcoder' Serbinenko
phco...@gmail.com wrote:
Try attached patch
hrm, i get a segmentation fault from grub-probe / even without this
patch when building from bzr trunk (r3964, i think).
The test machine i've set up looks like this uses a
In trying to test phcoder's patch for http://bugs.debian.org/611588 , i
pulled the bzr head and built it (using --disable-werror to work around
several remaining warnings about loop unrolling). I'm running into a
failure with the translations, i think:
0 dkg@hollywood:~/src/grub/grub$ bzr info
On 02/21/2012 09:30 PM, Mike Gilbert wrote:
I ran into that myself this weekend. Solution: regenerate POTFILES.in.
find . -name '*.c' -print | sort po/POTFILES.in
Thanks, that did indeed let the build complete.
i completed building it as a non-privileged user, and then as the
superuser, i
On 02/21/2012 10:23 PM, Mike Gilbert wrote:
On Tue, Feb 21, 2012 at 10:01 PM, Daniel Kahn Gillmor
d...@fifthhorseman.net wrote:
make install
make uninstall
That appears to have left a few files in /usr/local that i think it
shouldn't have.
This is why I use my package manger (portage
On Sat 2008-09-13 00:52:47 -0400, Arthur Marsh wrote:
Vesa Jääskeläinen wrote, on 2008-09-13 00:13:
Geoff Karl wrote:
I would like to be able to set the clock to a particular time
automatically before launching an operating system.
Anyone have any ideas if this can be done during the boot
Hey folks--
I'm trying to create a grub-based rescue USB stick for PowerPC
machines.
I've successfully gotten one machine to boot to this device, and grub
can see both the USB disk itself and the onboard (ide) HD.
However, when i try to load a linux kernel from either disk, i get an
error:
On Sat 2007-11-10 12:25:10 -0500, Marco Gerards wrote:
It will be committed soon, now for real ;-)
Thanks for the followup. i await with bated breath; netboot is an
important feature for me!
Let me know if there's a patchset i can test at some point as an end
user. Sorry i don't have the
On Sun 2007-09-30 12:07:38 -0400, Robert Millan wrote:
WIP. Check latest mails from Marco on the subject. He sent patches
implementing ethernet infrastructure and requested feedback.
Ah, thanks. Are you referring to this, from two months ago?
On Mon 2007-09-24 20:49:55 -0400, Gregg C Levine wrote:
To be honest I wasn't aware that anyone did do all of
that. According to the other list members they want to accommodate
the abillities of GRUB2 to be able to boot an operating system on
other platforms, and then the concepts of network
Hi folks--
I've searched high and low for documentation about how to get PXE
booting working with GRUB 2, but i haven't had much luck. Can anyone
give me pointers?
What i've done so far
-
I found a brief mention on the wiki [0] and followed those
instructions: cat
34 matches
Mail list logo
