All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Mascord <tusker@tusker.org>
To: Hetz Ben Hamo <hetzbh@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] suggestion for /dev/kqemu?
Date: Mon, 11 Apr 2005 09:54:31 +0800	[thread overview]
Message-ID: <4259D8D7.5090302@tusker.org> (raw)
In-Reply-To: <41e41e7a05041018357bc7b930@mail.gmail.com>

Hetz Ben Hamo wrote:
> Hi,
> 
> I'm trying to look for a solution for the following problem which
> happend either on the latest Redhat Enterprise and in Fedora Core 3
> and above:
> 
> Since every time that the machine is being rebooted, it creates
> devices in /dev/ according to what it being asked by /etc/udev..
> 
> Does anyone know what should I put (and where) in /etc/udev so that
> I'll have /dev/kqemu every time I boot? I know I can do it with a
> simple line which can be added to /etc/rc.d/rc.local or something, but
> I want some "standard" way to do that..
> 
> Thanks for the help,
> Hetz

Hi Hetz,

Sorry to point you to a tutorial, but this one is quite detailed:
http://www.reactivated.net/udevrules.php

>From what I can gather (since I don't use udev), the following should
work for kqemu...

# udevinfo -q path -n /dev/kqemu # which should return something like:
/class/kernel/module/xxx

# udevinfo -a -p /class/kernel/module/xxx

>From that output, you should be able to create a line similar to:

BUS="kernel", SYSFS{serial}="L72010011070626380", NAME="%k"

This may be totally off base, so let me know how it goes :)

Cheers,

Damien

      reply	other threads:[~2005-04-11  1:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11  1:35 [Qemu-devel] suggestion for /dev/kqemu? Hetz Ben Hamo
2005-04-11  1:54 ` Damien Mascord [this message]

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=4259D8D7.5090302@tusker.org \
    --to=tusker@tusker.org \
    --cc=hetzbh@gmail.com \
    --cc=qemu-devel@nongnu.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.