From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Greg KH <gregkh@suse.de>, Linus Torvalds <torvalds@osdl.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [GIT PATCH] Remove devfs from 2.6.17
Date: Mon, 19 Jun 2006 10:48:41 +1000 [thread overview]
Message-ID: <4495F469.5060100@yahoo.com.au> (raw)
In-Reply-To: <20060618233508.GH4744@bouh.residence.ens-lyon.fr>
Samuel Thibault wrote:
> Hi,
>
> Greg KH, le Sun 18 Jun 2006 16:12:04 -0700, a écrit :
>
>>And this whole thing has nothing to do with devfs, as you stated above
>>:)
>
>
> Ok, but devfs had let me some hope that it would work, and udev doesn't
> so much (the abovementioned links.conf file is considered hacky).
Could you do it with FUSE?
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-06-19 2:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 22:13 [GIT PATCH] Remove devfs from 2.6.17 Greg KH
2006-06-18 22:45 ` Michal Piotrowski
2006-06-18 23:06 ` Greg KH
2006-06-18 23:00 ` Samuel Thibault
2006-06-18 23:12 ` Greg KH
2006-06-18 23:35 ` Samuel Thibault
2006-06-19 0:48 ` Nick Piggin [this message]
2006-06-19 3:22 ` Greg KH
2006-06-19 8:23 ` Samuel Thibault
2006-06-19 8:23 ` Samuel Thibault
2006-06-19 9:30 ` Marcel Holtmann
2006-06-19 9:30 ` Marcel Holtmann
2006-06-19 9:39 ` Samuel Thibault
2006-06-19 9:39 ` Samuel Thibault
2006-06-19 10:22 ` Marcel Holtmann
2006-06-19 10:22 ` Marcel Holtmann
2006-06-19 0:54 ` H. Peter Anvin
2006-06-19 1:17 ` Joshua Hudson
2006-06-19 1:35 ` H. Peter Anvin
2006-06-19 5:55 ` Will Dyson
2006-06-19 7:14 ` Alexander E. Patrakov
2006-06-19 22:14 ` Daniel Barkalow
2006-06-19 22:17 ` H. Peter Anvin
2006-06-19 3:15 ` Greg KH
2006-06-19 8:52 ` Samuel Thibault
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=4495F469.5060100@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=torvalds@osdl.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.