All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: grub-devel@gnu.org
Cc: "Pascal A. Dupuis" <Pascal.Dupuis@worldonline.be>,
	Robert Millan <rmh@aybabtu.com>
Subject: Re: grub-pc: installation failure under linux + udev
Date: Sat, 5 Jan 2008 02:31:51 +0100	[thread overview]
Message-ID: <200801050231.52190.okuji@enbug.org> (raw)
In-Reply-To: <20080103235459.GA7520@thorin>

On Friday 04 January 2008 00:54, Robert Millan wrote:
> On Thu, Jan 03, 2008 at 11:14:23PM +0100, Pascal A. Dupuis wrote:
> > Hello,
> >
> > this is a copy of debian bug 450709
> > (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450709) at
> > debian maintainer's (Robert Millan <rmh at aybabtu dot com>) request:
>
> Thanks Pascal.
>
> > But ... util/biosdisk.c has another issue with detecting udev. The
> > routine has_devfs searchs for /dev/.devfsd, which cames from deprecated
> > devfs. Enclosed is a synthetic patch, I compiled and ran it fine on my
> > machine. Could you check ?
>
> The off-by-5 bug is already fixed in CVS.  As for the devfs part, I think
> I figured out what you're doing.  You setup udev to emulate devfs-style
> devices, right?
>
> I think the right fix for this is not to check for /dev/.udev, but rather
> just probe for devfs-style devices unconditionally.
>
> As it happens there are other ways in which one could have this layout,
> including other /dev implementations such as userdevfs.
>
> What does everyone else think?

As long as it works fine, no problem. :)

Okuji



  reply	other threads:[~2008-01-05  1:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080103221423.GA6243@example.org>
2008-01-03 23:54 ` grub-pc: installation failure under linux + udev Robert Millan
2008-01-05  1:31   ` Yoshinori K. Okuji [this message]
2008-01-05 12:01     ` Robert Millan
     [not found]       ` <20080107173959.GB4680@example.org>
2008-01-07 18:55         ` Robert Millan

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=200801050231.52190.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=Pascal.Dupuis@worldonline.be \
    --cc=grub-devel@gnu.org \
    --cc=rmh@aybabtu.com \
    /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.