From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Rene Rebe <rene.rebe@gmx.net>, <linux-kernel@vger.kernel.org>,
<alsa-devel@lists.sourceforge.net>
Subject: Re: devfs unable to handle permission: 2.4.17-pre[4,5] /ALSA-0.9.0beta[9,10]
Date: Sat, 8 Dec 2001 21:48:37 -0700 [thread overview]
Message-ID: <200112090448.fB94mbP05763@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <Pine.LNX.4.33.0112090447290.13049-100000@serv>
In-Reply-To: <200112090308.fB938N504764@vindaloo.ras.ucalgary.ca> <Pine.LNX.4.33.0112090447290.13049-100000@serv>
Roman Zippel writes:
> Hi,
>
> On Sat, 8 Dec 2001, Richard Gooch wrote:
>
> > > devfs_mk_dir returns an error now, so the driver won't be able to
> > > make new dev nodes available. So far it was legal to manually create
> > > a directory under devfs, now it's suddenly an error.
> >
> > It was always an error, you just got away with it.
>
> Sorry, but this is bullshit. You even included an example script
> with this "error" (Documentation/filesystems/devfs/rc.devfs). You
> suddenly change the behaviour of devfs during a stable release in a
> noncompatible way. Distributions and their users that followed
> _your_ advice are suddenly fucked up, that's irresponsible. How do
> you think devfs should be ever taken seriously?
Oh, the "tar kludge". That script has been obsolete for over a year
and a half. I should have removed it ages ago. I really should get
around to doing that one day.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-12-09 4:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 23:35 devfs unable to handle permission: 2.4.17-pre[4,5] / ALSA-0.9.0beta[9,10] Rene Rebe
2001-12-07 6:09 ` Richard Gooch
2001-12-07 15:22 ` Roman Zippel
2001-12-07 15:59 ` Richard Gooch
2001-12-07 19:17 ` devfs unable to handle permission: 2.4.17-pre[4,5] /ALSA-0.9.0beta[9,10] Roman Zippel
2001-12-07 20:08 ` Richard Gooch
2001-12-07 20:37 ` Roman Zippel
2001-12-09 3:08 ` Richard Gooch
2001-12-09 4:02 ` Roman Zippel
2001-12-09 4:48 ` Richard Gooch [this message]
2001-12-09 14:44 ` Roman Zippel
2001-12-09 19:45 ` Marcelo Tosatti
2001-12-09 21:26 ` Richard Gooch
2001-12-09 22:26 ` Roman Zippel
2001-12-09 21:20 ` Marcelo Tosatti
2001-12-10 0:11 ` Richard Gooch
2001-12-09 23:00 ` Marcelo Tosatti
2001-12-09 23:03 ` Marcelo Tosatti
2001-12-07 16:41 ` devfs unable to handle permission: 2.4.17-pre[4,5] / ALSA-0.9.0beta[9,10] Richard Gooch
2001-12-22 22:14 ` devfs permissions Gabor Z. Papp
2001-12-23 0:11 ` Pozsar Balazs
2001-12-07 7:49 ` devfs unable to handle permission: 2.4.17-pre[4,5] / ALSA-0.9.0beta[9,10] Rene Rebe
2001-12-10 10:46 ` [Alsa-devel] " Takashi Iwai
2001-12-10 7:04 devfs unable to handle permission: 2.4.17-pre[4,5] /ALSA-0.9.0beta[9,10] Borsenkow Andrej
2001-12-10 10:46 ` Roman Zippel
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=200112090448.fB94mbP05763@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.rebe@gmx.net \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®