From: rmoser <mlmoser@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: Supermount (NOT Mandrake!)
Date: Sun, 22 Jun 2003 22:41:28 -0400 [thread overview]
Message-ID: <200306222241280320.0835BB0F@smtp.comcast.net> (raw)
Okay, Mandrake's supermount is marked as stable, and it's broken
and a piece of shit. However, supermount is useful on the iPaq and
convienient in other places as well. I'm going to work out a somewhat
workable alternative to that, and try to impliment it. Once I fail at that
(some outlook on life I have, huh?), I'll put the proposal up on here for
you all to take a shot at.
One of the things I'm thinking about is multiple partition devices. For
example, Zip disks. Some of us make a Zip disk a single filesystem,
with no partition table: `mount /dev/sda /zip`. Others leave the 4
partitions on the Zip disk when they get it: `mount /dev/sda4 /zip`.
What to do, what to do.
Of course the answer's simple.
`mount supermount /zip -o device=/dev/sda,user`, and if we have 4 partitions,
/zip becomes mod a-w, and 4 new directories appear: /zip/1 /zip/2 /zip/3
/zip/4. Then supermount mounts each partition on each of those, if
possible. If it's a broken partition (/dev/sda[1-3] on a new zip disk), it's just
marked mod a-w.
Question: Can I do this? I've never programmed in the kernel before but i've
tried several times. I know about the automounter. Can I control it from a
virtual filesystem device? Like, on accessing /zip, could those dirs be created
virtually, then suddenly a supermount mounted on each of them? I have no
idea what I'm doing but I'm trying!
I'm gonna send this before I feel too stupid to.
--Bluefox Icy
next reply other threads:[~2003-06-23 2:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 2:41 rmoser [this message]
2003-06-23 2:56 ` Supermount (NOT Mandrake!) Con Kolivas
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=200306222241280320.0835BB0F@smtp.comcast.net \
--to=mlmoser@comcast.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.