linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Moving Ubuntu to upstream udev rules
Date: Fri, 26 Dec 2008 00:26:37 +0000	[thread overview]
Message-ID: <20081226002637.GC2979@nb.net.home> (raw)
In-Reply-To: <1229669228.14012.30.camel@quest>

On Fri, Dec 26, 2008 at 12:39:16AM +0100, Kay Sievers wrote:
> On Fri, Dec 26, 2008 at 00:26, Karel Zak <kzak@redhat.com> wrote:
> > On Fri, Dec 19, 2008 at 05:03:52PM +0100, Kay Sievers wrote:
> >> > names
> >> >
> >> >   you rename some devices and disagree with devices.txt
> >> >
> >> >     rawctl -> raw/rawctl
> >>
> >> The tools use that, if  I remember. Someone maintaining the tools should
> >> tell, devices.txt is pretty unreliable sometimes.
> >
> >  The upstream raw(8) command supports /dev/rawctl and also
> >  /dev/raw/rawctl.  I think it makes more sense to use raw/rawctl when
> >  you have all your raw devices in raw/ subdirectory (e.g. /dev/raw/raw<N>).
> 
> The raw tool looks for /dev/rawctl first and the fallback to
> /dev/raw/rawctl is named DEVFS_*. Should we turn that order around and
> remove the devfs notion from the raw tool and let udev create a
> dev/raw/rawctl node?

 Yeah. Fixed, committed and pushed.

 $ strace -e open ./raw
 open("/dev/raw/rawctl", O_RDWR)         = -1 ENOENT (No such file or directory)
 open("/dev/rawctl", O_RDWR)             = -1 ENOENT (No such file or directory)

 I have also removed the #ifdef OLD_RAW_DEVS (/dev/raw<N>) junk.


 BTW, it would be nice to refresh devices.txt according to your latest
 changes in udev.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>

  parent reply	other threads:[~2008-12-26  0:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19  6:47 Moving Ubuntu to upstream udev rules Scott James Remnant
2008-12-19 16:03 ` Kay Sievers
2008-12-19 16:10 ` Marco d'Itri
2008-12-20  8:12 ` Piter PUNK
2008-12-20  8:41 ` Robby Workman
2008-12-20 11:30 ` Marco d'Itri
2008-12-20 18:33 ` Dan Nicholson
2008-12-21 12:39 ` Kay Sievers
2008-12-21 12:42 ` Kay Sievers
2008-12-21 12:53 ` Kay Sievers
2008-12-21 13:07 ` Marco d'Itri
2008-12-21 14:29 ` Kay Sievers
2008-12-21 21:52 ` Piter PUNK
2008-12-22  2:00 ` Kay Sievers
2008-12-22  8:41 ` Harald Hoyer
2008-12-22  8:53 ` Harald Hoyer
2008-12-22  9:39 ` Scott James Remnant
2008-12-22 10:00 ` Bernhard Walle
2008-12-22 11:57 ` Marco d'Itri
2008-12-22 12:37 ` Kay Sievers
2008-12-22 12:39 ` Scott James Remnant
2008-12-22 12:40 ` Kay Sievers
2008-12-22 12:42 ` Kay Sievers
2008-12-22 12:43 ` Kay Sievers
2008-12-22 13:57 ` Kay Sievers
2008-12-25 23:26 ` Karel Zak
2008-12-25 23:39 ` Kay Sievers
2008-12-26  0:26 ` Karel Zak [this message]
2008-12-26  0:48 ` Kay Sievers

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=20081226002637.GC2979@nb.net.home \
    --to=kzak@redhat.com \
    --cc=linux-hotplug@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).