public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: More modutils: It's probably worse.
Date: 14 Nov 2000 11:42:42 -0800	[thread overview]
Message-ID: <8us4ji$dbl$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011132040160.1699-100000@ferret.lmh.ox.ac.uk> <20001114095921.E30730@monad.caldera.de> <3A119082.BBFD700@talontech.com> <20001114152430.C2645@alcove.wittsend.com>

Followup to:  <20001114152430.C2645@alcove.wittsend.com>
By author:    "Michael H. Warfield" <mhw@wittsend.com>
In newsgroup: linux.dev.kernel
>
> 	Oh, I hate to add to a remark like that (OK, I lied, I love
> trollbait...)
> 
> On Tue, Nov 14, 2000 at 11:20:35AM -0800, Ben Ford wrote:
> > Olaf Kirch wrote:
> 
> > > sure request_module _does_not_ accept funky module names. Why allow
> > > people to shoot themselves (and, by extension, all other Linux users
> > > out there) in the foot?
> 
> > I thought that was the whole purpose of Unix/Linux?
> 
> 	True!  Very true!  Unix/Linux requires that the user shoot
> themselves in the foot.  Windows automates that process and does it
> for the user, thus making foot shooting user friendly.  :-)
> 

Seriously, though, I don't see any reason modprobe shouldn't accept
funky filenames.  There is a standard way to do that, which is to have
an argument consisting of the string "--"; this indicates that any
further arguments should be considered filenames and not options.

For example:

rm -- -foo		# Delete a file named "-foo"

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-14 20:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0011132040160.1699-100000@ferret.lmh.ox.ac.uk>
     [not found] ` <Pine.LNX.4.21.0011132352550.31869-100000@dione.ids.pl>
2000-11-14  8:59   ` More modutils: It's probably worse Olaf Kirch
2000-11-14 10:04     ` David Schleef
2000-11-14 10:29     ` Guest section DW
2000-11-14 10:38       ` Olaf Kirch
2000-11-14 19:20     ` Ben Ford
2000-11-14 20:24       ` Michael H. Warfield
2000-11-14 19:42         ` H. Peter Anvin [this message]
2000-11-14 23:27           ` Keith Owens
2000-11-15 10:43             ` Olaf Titz
2000-11-15 11:17               ` Tim Waugh
2000-11-16  4:31               ` Keith Owens
2000-11-17  0:48             ` Rusty Russell
2000-11-14 12:47 Petr Vandrovec

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='8us4ji$dbl$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@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