From: Roald Strauss <mr_lou@dewfall.dk>
To: "Pali Rohár" <pali.rohar@gmail.com>, "Jan Kara" <jack@suse.cz>
Cc: "Steven J. Magnani" <steve.magnani@digidescorp.com>,
Jan Kara <jack@suse.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: UDF filesystem image with Write-Once UDF Access Type
Date: Thu, 1 Aug 2019 12:21:34 +0200 [thread overview]
Message-ID: <294d59b9-67e8-9984-b80b-0a7c44f1707c@dewfall.dk> (raw)
In-Reply-To: <20190801084411.l4uv7xrb5ilouuje@pali>
Hey all
I'm a bit pressed for time these days, so I won't be able to do any
tests any time soon.
Also have to admit that I lost interest in UDF a bit, since we ended up
looking towards hardware solutions for write-protections instead.
But when/if mkudffs includes an option to create a write-once /
read-only filesystem while adding files to it at the same time (because
how else am I gonna put files onto my read-only filesystem?), then it
might become interesting again.
- Roald
Den 01/08/2019 kl. 10.44 skrev Pali Rohár:
> On Thursday 01 August 2019 09:35:30 Jan Kara wrote:
>> On Fri 12-07-19 12:02:24, Pali Rohár wrote:
>>> Also in git master of udftools has mkduffs now new option --read-only
>>> which creates UDF image with Read-Only Access Type.
>> I've tested this and the kernel properly mounts the image read-only.
> Roald, can you test that problem which you described to me with
> read-only access type is now correctly fixed?
>
prev parent reply other threads:[~2019-08-01 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 10:02 Pali Rohár
2019-07-26 17:44 ` Steve Magnani
2019-08-01 7:44 ` Jan Kara
2019-08-01 7:35 ` Jan Kara
2019-08-01 8:38 ` Jan Kara
2019-08-01 8:57 ` Pali Rohár
2019-08-02 10:28 ` Jan Kara
2019-08-01 8:44 ` Pali Rohár
2019-08-01 10:21 ` Roald Strauss [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=294d59b9-67e8-9984-b80b-0a7c44f1707c@dewfall.dk \
--to=mr_lou@dewfall.dk \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=steve.magnani@digidescorp.com \
/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
all inboxes | Powered by JetHome®