From: Roman Zippel <zippel@linux-m68k.org>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Rene Rebe <rene.rebe@gmx.net>,
linux-kernel@vger.kernel.org, alsa-devel@lists.sourceforge.net,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: devfs unable to handle permission: 2.4.17-pre[4,5] /ALSA-0.9.0beta[9,10]
Date: Sun, 09 Dec 2001 15:44:38 +0100 [thread overview]
Message-ID: <3C1378D6.A5BAB1FA@linux-m68k.org> (raw)
In-Reply-To: <200112090308.fB938N504764@vindaloo.ras.ucalgary.ca> <Pine.LNX.4.33.0112090447290.13049-100000@serv> <200112090448.fB94mbP05763@vindaloo.ras.ucalgary.ca>
Richard Gooch wrote:
> 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.
You should have done this a year ago. Permission management with the
"tar kludge" was a valid option so far and is currently in use. There
was no warning period that this future would be obsolete.
BTW from your devfsd-v1.3.20 release notes:
"NOTE: this release finally provides complete permissions management.
Manually (i.e. non driver or devfsd) created inodes can now be
restored when devfsd starts up. This requires v1.2 of the devfs core
(available in 2.4.17-pre1) for best operation."
The tar solution only works until 2.4.16, the new devfsd provides this
only with 2.4.17. I'll leave the final decision to Marcelo, whether he
accepts this or not. I shut up now, may someone else explain the meaning
of compatibility to you.
bye, Roman
next prev parent reply other threads:[~2001-12-09 14:45 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 7:49 ` Rene Rebe
2001-12-07 16:41 ` Richard Gooch
2001-12-22 22:14 ` devfs permissions Gabor Z. Papp
2001-12-23 0:11 ` Pozsar Balazs
2001-12-07 15:22 ` devfs unable to handle permission: 2.4.17-pre[4,5] / ALSA-0.9.0beta[9,10] 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
2001-12-09 14:44 ` Roman Zippel [this message]
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-10 10:46 ` [Alsa-devel] Re: devfs unable to handle permission: 2.4.17-pre[4,5] / ALSA-0.9.0beta[9,10] Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
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=3C1378D6.A5BAB1FA@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=rene.rebe@gmx.net \
--cc=rgooch@ras.ucalgary.ca \
/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