Re: bug in 2.6.22-rc2: loop mount limited to one single iso image

[Uwe Bugla <uwe.bugla@gmx.de>]

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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/