From: Uwe Bugla <uwe.bugla@gmx.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Al Viro <viro@ftp.linux.org.uk>, Ray Lee <ray-lk@madrabbit.org>,
Andrey Borzenkov <arvidjaar@mail.ru>,
Ken Chen <kenchen@google.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
"Torvalds, Linus" <torvalds@linux-foundation.org>
Subject: Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
Date: Tue, 22 May 2007 23:35:25 +0200 [thread overview]
Message-ID: <200705222335.25758.uwe.bugla@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0705222217300.4452@yvahk01.tjqt.qr>
Am Dienstag, 22. Mai 2007 22:18 schrieben Sie:
> On May 20 2007 07:28, Al Viro wrote:
> >On Sat, May 19, 2007 at 11:16:59PM -0700, Ray Lee wrote:
> >> Ken? Ball's in your court. As the patch isn't providing a killer
> >> feature for 2.6.22, I'd suggest just reverting it for now until the
> >> issues are ironed out.
> >
> >Hold it. The real question here is which logics do we want there.
> >IOW, and how many device nodes do we want to appear and _when_ do
> >we want them to appear?
>
> "min_loop" (max_loop?) nodes should appear (but without a backing
> gendisk), and when they are opened, they should get their gendisk
> allocated and assigned.
>
>
>
> Jan
Jan,
Please stick to the latest revised patch residing in Andrew's mm-tree now.
All that I wanted was a possibility to mount up to eight 8 iso images to be
mounted parallely at boot time using udev and AVOID fuzzing around with
additional nodes in /dev/loop.
This desire isn't nonsense at all:
For instance, if you run Debian "Lenny" testing, you need to mount 4 DVD iso
images parallely at boot time (at least I do need that) if you do not want to
waste time with opening and closing your DVD device at all.
Then there may be other desires:
a. For instance mounting Christian Marillat's unofficial Debian iso image at
boot time (multimedia stuff).
b. For instance to mount and run all sampled libraries for helping the wine
package to be as compatible as possible (i. e. winetools by Joachim von
Thadden)
and so on.....
That means: At least for my personal desire, Ken Chen's latest patch was OK so
far.
Now, if there is a specific need for mounting up to 256 iso images including
whatever technical basis or userspace tools requiries or changings of
whatever kind then at least I do not care about the what and why at all.
But the facts for now at least go like this:
1. Ken Chen's latest patch, criticised and enhanced by Andrew Morton, acked by
Al Viro, is now part of the latest mm-tree.
2. The three patches leading to the disaster of breaking userspace are not yet
ripped out of Linus's 2.6.22-rc2-tree.
In so far I would deeply appreciate Linus Torvalds to rip put the mentioned
patches mentioned, just to avoid future troubles.
Yours sincerely
Uwe
P. S.:
1. The first approach, a common work by Ken Chen and Al Viro, was an approach
promising up to 256 iso images to be mounted dynamically on user's demand
while really offering only one iso image to be mounted and, after the desire
to mount some more at boot time, stop working.
I would evaluate that approach as stuff for cabaret laughter, jokin', or
simply a terrible bug.
2. I do not like / appreciate discussions on items that seem to be far away
from actual user's needs, without being proven by examples of real necessity.
Otherwise expressed: Who really needs actually to mount up to 256 iso images
using the loop device? I am ready to learn...... :)
3. I have seen this feature of "virtual DVD devices" under Windoze XP,
established for whatever nonsense reason. Question: Who actually needs to
mount parallely for instance up to 200 video DVDs wasting Ram like hell?
I would call that a kind of fetish, i. e. I do not see the deeper sense of it!
The base line for linux as an operating system is: "Small and effective is
Beautiful", isn't it?
next prev parent reply other threads:[~2007-05-22 21:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 18:33 bug in 2.6.22-rc2: loop mount limited to one single iso image Ray Lee
2007-05-19 19:17 ` Andrey Borzenkov
[not found] ` <200705200124.13026.uwe.bugla@gmx.de>
2007-05-20 4:45 ` Andrey Borzenkov
2007-05-20 6:16 ` Ray Lee
2007-05-20 6:28 ` Al Viro
2007-05-20 6:58 ` Andrey Borzenkov
2007-05-20 14:52 ` Uwe Bugla
2007-05-20 15:26 ` Ray Lee
2007-05-20 15:22 ` Ray Lee
2007-05-20 15:54 ` Kay Sievers
2007-05-20 16:02 ` Andrey Borzenkov
2007-05-20 16:23 ` Andreas Schwab
2007-05-20 16:10 ` Ray Lee
2007-05-20 16:16 ` Kay Sievers
2007-05-20 16:29 ` Uwe Bugla
2007-05-20 19:53 ` Michael Mauch
2007-05-21 16:11 ` Linus Torvalds
2007-05-21 16:27 ` Ken Chen
2007-05-21 16:35 ` Ray Lee
2007-05-21 16:37 ` Ken Chen
2007-05-21 16:50 ` Uwe Bugla
2007-05-21 17:11 ` Kay Sievers
2007-05-21 17:51 ` Andrey Borzenkov
2007-05-21 17:04 ` Linus Torvalds
2007-05-21 20:48 ` Ken Chen
2007-05-21 21:20 ` Uwe Bugla
2007-05-21 22:04 ` Andrew Morton
2007-05-22 0:10 ` Al Viro
2007-05-22 0:13 ` Al Viro
2007-05-20 16:09 ` Andrey Borzenkov
2007-05-20 16:14 ` Ray Lee
2007-05-22 20:18 ` Jan Engelhardt
2007-05-22 21:35 ` Uwe Bugla [this message]
2007-05-21 6:08 ` Ken Chen
2007-05-21 6:40 ` Ray Lee
2007-05-21 7:59 ` Uwe Bugla
-- strict thread matches above, loose matches on Subject: below --
2007-05-19 13:53 Uwe Bugla
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=200705222335.25758.uwe.bugla@gmx.de \
--to=uwe.bugla@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=arvidjaar@mail.ru \
--cc=jengelh@linux01.gwdg.de \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=ray-lk@madrabbit.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ftp.linux.org.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