All of lore.kernel.org
 help / color / mirror / Atom feed
From: BandiPat <magicpage91@earthlink.net>
To: Grub2 Development <grub-devel@gnu.org>
Subject: Faulty grub-mkdevicemap file
Date: Sat, 25 Apr 2009 13:26:58 -0400	[thread overview]
Message-ID: <49F347E2.6060903@earthlink.net> (raw)

BandiPat writes:
 > Oh, has anyone experienced any problems with grub-mkdevicemap when 
installing Grub2 or updating?  I had one user complain about it 
segfaulting on his machine, but I've not seen any problems.  This is 
with svn2137.
---------------
Andreas wrote:
I'm experiencing also problems using it, but it's not segfaulting. Using 
a svn2130 build grub-mkdevicemap --no-floppy create a device.map with 
proper content like this:
(hd0) /dev/sda
But a svn2137 build (exactly the same BandiPat uses) creates this 
content, which might not be wrong, but at least the most important part 
my HDD is missing:
(fd0) (null)

Probably this problem was introduced by revision 2133 and obviously 
wasn't fixed in rev 2134 - 2137 and in 2138 - 2140 I can see nothing 
which might fix this.

It would be great if somebody could have a look what could cause this 
problem. Maybe davem as the author of that revision.
If you need any additional information give me a yell and I'll try my 
best to provide it.
==============

Decided to start a new topic more fitting to this problem.  Sorry for 
what looks like a double posting.

I just tested on one machine, running grub-mkdevicemap -v from the 
shell, which resulted in a segfault and blank device.map file in /boot/grub!

Looks like some bug was introduced after svn2130 in the file.

Thanks devs for your attention to this one.

Pat



             reply	other threads:[~2009-04-25 17:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-25 17:26 BandiPat [this message]
2009-04-25 19:29 ` Faulty grub-mkdevicemap file BandiPat
2009-04-25 23:32   ` David Miller
2009-04-26  8:46   ` David Miller
2009-04-26  8:57     ` Andreas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49F347E2.6060903@earthlink.net \
    --to=magicpage91@earthlink.net \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.