public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Rusty Russell <rusty@rustcorp.com.au>, Greg KH <greg@kroah.com>,
	Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: module-init-tools/udev and module auto-loading
Date: Tue, 03 Feb 2004 23:34:30 +0200	[thread overview]
Message-ID: <1075844070.7473.64.camel@nosferatu.lan> (raw)
In-Reply-To: <20040203205330.GZ21151@parcelfarce.linux.theplanet.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]

On Tue, 2004-02-03 at 22:53, viro@parcelfarce.linux.theplanet.co.uk
wrote:
> On Tue, Feb 03, 2004 at 10:47:13PM +0200, Martin Schlemmer wrote:
> > On Tue, 2004-02-03 at 21:33, viro@parcelfarce.linux.theplanet.co.uk
> > wrote:
> > > On Tue, Feb 03, 2004 at 07:48:06PM +0200, Martin Schlemmer wrote:
> > > > > > I guess there will be cries of murder if 'somebody' suggested that if
> > > > > > a node in /dev is opened, but not there, the kernel can call
> > > > > > 'modprobe -q /dev/foo' to load whatever alias there might have been?
> > > 
> > > Vetoed.  _Especially_ when you are checking that on "pathname prefix"
> > > level - namei.c is not a place for such special-casing.
> > > 
> > 
> > Well, I do not scratch around in there in general.  I guess the question
> > is:
> > 
> > 1)  This this idea is Ok to make it (not patch or where it is, but the
> > idea in general.
> 
> It is not.  Consider the effect of cd /dev followed by lookups.  Do you
> really want a different behaviour in that case?  Ditto for use of
> symlinks, yadda, yadda.

Any other ideas for the problem in general? =)


Thanks,

-- 
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-02-03 21:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-01 22:31 module-init-tools/udev and module auto-loading Martin Schlemmer
2004-02-02  0:10 ` Rusty Russell
2004-02-02 19:02   ` Martin Schlemmer
2004-02-03  0:55     ` Rusty Russell
2004-02-03  4:55       ` Martin Schlemmer
2004-02-03 17:48       ` Martin Schlemmer
2004-02-03 19:33         ` viro
2004-02-03 20:47           ` Martin Schlemmer
2004-02-03 20:53             ` viro
2004-02-03 21:34               ` Martin Schlemmer [this message]
2004-02-04  1:22         ` Rusty Russell
2004-02-04  2:04           ` viro
2004-02-04  3:43             ` Rusty Russell
2004-02-02  5:21 ` Greg KH
2004-02-02 18:12   ` Jamie Lokier
2004-02-02 19:14     ` Martin Schlemmer
2004-02-02 19:13   ` Martin Schlemmer
  -- strict thread matches above, loose matches on Subject: below --
2004-02-02  7:20 "Andrey Borzenkov" 
2004-02-02  7:34 ` Greg KH
2004-02-03 15:00 "Andrey Borzenkov" 

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=1075844070.7473.64.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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