From: "Matthew D. Pitts" <mpitts@suite224.net>
To: <cooker@linux-mandrake.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [Cooker] (RFC) Supermount 2
Date: Mon, 25 Mar 2002 09:54:07 -0500 [thread overview]
Message-ID: <002301c1d40c$eb2bd920$b0d3fea9@pcs686> (raw)
In-Reply-To: <Pine.LNX.4.33.0203251316560.26580-100000@luna.ellen.dexterslabs.com>
----- Original Message -----
From: <danny@mailmij.org>
To: <cooker@linux-mandrake.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Monday, March 25, 2002 7:21 AM
Subject: Re: [Cooker] (RFC) Supermount 2
>
> On Mon, 25 Mar 2002, Matthew D. Pitts wrote:
> >
> > I am starting to plan a new version of Supermount. I have some things I
want to try out in it, and I will list them in this message. I am willing to
accept any and all input on what I am wanting to call Supermount 2.
> > Planned features of Supermount 2:
> >
> > 1) Auto-detection of filesystem type.
> Meaning we will finally have CD-tracks visualized as WAV files? like CD-fs
> does? Same goes for multisession disks.
I will try to do that, though it may mean hacking into the isofs driver.
> > 2) Supermount modules for each filesystem type.
> How is this on performance (first check for fs type than loading module?
> than disk is removed, unloading module and loading another one?)
I haven't gotten that far, yet. How well it works depends a lot on how much
of the information about the disk can be read by Supermount 2 when the disk
is inserted.
> > 3) Built-in support for packet-writing. ( i.e. insert packet-writing
formatted disk and it loads appropriate kernel modules. )
> >
> > There may be other features added if there is an interest in them. I
will need assistance with the packet-writing support. I am only planning to
do this for the 2.5.x and later kernels, so if anyone else wishes to
back-port it to an older kerenl series, by all means do so. I have wanted to
make some kind of contribution to this project for some time and I feel that
this is something that will be useful.
> >
> What about doing it in userspace? I remember seeing Alan Cox writing he
> had a proof of concept of something like this on some ftp server (sorry,
> cannot remember where).
I am going to go over Alan's code when I have a decent machine to work
with...
>
> > I am going to be making my prelminary code available to whomever wishes
to see it once I get my Linux box back up.
> sure
>
>
>
> Danny
>
> >
> > Matthew D. Pitts
> >
>
> -
> 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/
prev parent reply other threads:[~2002-03-25 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001d01c1d3ec$2e914720$b0d3fea9@pcs686>
2002-03-25 12:21 ` [Cooker] (RFC) Supermount 2 danny
2002-03-25 13:05 ` Alan Cox
2002-03-25 13:05 ` Matthew D. Pitts
2002-03-25 14:54 ` Matthew D. Pitts [this message]
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='002301c1d40c$eb2bd920$b0d3fea9@pcs686' \
--to=mpitts@suite224.net \
--cc=cooker@linux-mandrake.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