From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: "\"Thomas B. Rücker\"" <dm8tbr@openpma.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: hiding an partition and preventing to get automounted
Date: Fri, 10 Nov 2006 17:11:57 -0600 [thread overview]
Message-ID: <1163200318.28537.2.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <4554E1B4.3050508@openpma.org>
On Fri, 2006-11-10 at 21:31 +0100, "Thomas B. Rücker" wrote:
> Short description of the situation:
> - embedded linux device running 2.4.19 montavista (Archos PMA430)
> - redesigning the firmware to as open source as possible
> - moved system partition from an loop mounted ext3 image on a fat32
> partition to a real partition.
> - device supports usb-mass-storage mode (complete hdd gets handed over
> to a usb-bridge)
>
> Now we're trying to avoid unmounting that ext3 partition because we use
> it with unionfs to have a writeable root filesystem.
> The problem is that when the hdd is accessed via usb the operating
> system of that desktop PC might mount that ext3 partition and change it.
> What would be a clean way to hide the partition from systems accessing
> it? What would be a clean way of making it ReadOnly to those systems?
>
> We had some ideas like using a different magic for the filesystem or a
> high and unique revision number we could patch our kernel for, but I'm
> not sure if there would be bad side effects to that. Marking the
> partition as e.g. hidden FAT16 (0x16) won't keep a linux system from
> recognizing and automounting it.
>
> Any ideas or pointers?
Using a unique superblock magic sounds simple and is probably as
foolproof as anything.
Shaggy
--
David Kleikamp
IBM Linux Technology Center
prev parent reply other threads:[~2006-11-10 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 20:31 hiding an partition and preventing to get automounted "Thomas B. Rücker"
2006-11-10 23:11 ` Dave Kleikamp [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=1163200318.28537.2.camel@kleikamp.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=dm8tbr@openpma.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).