All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marc - A. Dahlhaus" <mad@wol.de>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Daniel Schroeder <sec@dschroeder.info>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [XEN-3.4.1-rc5] no udev rules with udev 124
Date: Wed, 01 Jul 2009 23:34:31 +0200	[thread overview]
Message-ID: <4A4BD667.2060303@wol.de> (raw)
In-Reply-To: <C6715E9B.EB0B%keir.fraser@eu.citrix.com>

Hello Daniel,
hello Kier,

the Problem is, that udev 124 does not know the the option -V without 
info as the first param.

I'll check on which version this was introduced and send a patch to fix 
this problem.


Marc

Keir Fraser schrieb:
> If you revert changeset 19668 in xen-3.4-testing.hg (e.g., hg export 19668 |
> patch -Rp1) then does the problem go away?
>
>  -- Keir
>
> On 01/07/2009 18:01, "Daniel Schroeder" <sec@dschroeder.info> wrote:
>
>   
>> hello *,
>>
>> rc5 and udev version 141 = fine
>> rc5 and udev version 124 = missing files
>>
>> --
>> daniel
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>     
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>   

  reply	other threads:[~2009-07-01 21:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 17:01 [XEN-3.4.1-rc5] no udev rules with udev 124 Daniel Schroeder
2009-07-01 17:42 ` Keir Fraser
2009-07-01 21:34   ` Marc - A. Dahlhaus [this message]
2009-07-01 21:52   ` Daniel Schroeder
2009-07-01 21:57     ` Marc - A. Dahlhaus
2009-07-01 23:18       ` Marc - A. Dahlhaus
2009-07-02  8:10         ` Daniel Schroeder
2009-07-02  9:17           ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
2009-07-02 10:27             ` Keir Fraser
2009-07-02 11:07               ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]

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=4A4BD667.2060303@wol.de \
    --to=mad@wol.de \
    --cc=keir.fraser@eu.citrix.com \
    --cc=sec@dschroeder.info \
    --cc=xen-devel@lists.xensource.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.