From: Mark Swanson <swansma@yahoo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Request: removal of fs/fs.h/super_block.u to enable partition locking
Date: Wed, 19 Sep 2001 15:50:04 -0400 [thread overview]
Message-ID: <3BA8F6EC.E3D73C87@yahoo.com> (raw)
In-Reply-To: <E15jn1X-0003cU-00@the-village.bc.nu>
Alan Cox wrote:
>
> You are not going to stop a tired sysadmin doing something daft. You can
> certainly create a GPL'd raw partition as a file fs (I believe someone did
> that so INN could mmap raw on a device)
>
> However you don't need to remove anything for that
But I can't distribute the file fs with my application,
because I can't expect my
user base to patch and recompile their kernel just so they can run
my application.
Perhaps what is needed is an 'inuse' filesystem or a way to make
filesystem modules without patching the kernel.
My concern is that ordinary tools like mount check the proc filesystem
to see if a partition is already mounted and it seems likely that tools
like mke2fs do this too. Sysadmins might feel that existing tools
protect
them from damaging something in use. I'm looking for a way to follow
this
general behavior with raw partitions.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
next prev parent reply other threads:[~2001-09-19 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 2:14 Request: removal of fs/fs.h/super_block.u to enable partition locking Mark Swanson
2001-09-19 6:00 ` Andreas Dilger
2001-09-19 19:28 ` Alan Cox
2001-09-19 19:50 ` Mark Swanson [this message]
2001-09-19 21:52 ` Request: removal of fs/fs.h/super_block.u to enable partition Alan Cox
2001-09-19 23:16 ` Andreas Dilger
2001-09-19 23:06 ` Request: removal of fs/fs.h/super_block.u to enable partition locking Andreas Dilger
2001-09-19 20:26 ` Andreas Dilger
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=3BA8F6EC.E3D73C87@yahoo.com \
--to=swansma@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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