From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Newbie ask for help: cramfs port to isofs
Date: 20 Feb 2001 19:48:17 -0800 [thread overview]
Message-ID: <96vdq1$t90$1@cesium.transmeta.com> (raw)
In-Reply-To: <877l2lyk3j.fsf@debian.org>
Followup to: <877l2lyk3j.fsf@debian.org>
By author: zhaoway <zw@debian.org>
In newsgroup: linux.dev.kernel
>
> I plan to automatically de-compressing ``*.cramed'' files made with
> cramit.c (which is a simplified version of mkcramfs.c also attached
> below) from within isofs.o. This indeed isn't a very clean idea I
> agree. If you have better design, please let me know.
>
It would be better to have this controlled by SUSP records. It looks
like the -z option to mkisofs was intended to do this, but it never
quite got done and integrated.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-02-21 3:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 6:03 Newbie ask for help: cramfs port to isofs zhaoway
2001-02-20 9:35 ` Andrzej Krzysztofowicz
2001-02-20 9:54 ` Nick Holloway
2001-02-20 12:30 ` Alan Cox
2001-02-22 20:46 ` Pavel Machek
2001-02-21 3:48 ` H. Peter Anvin [this message]
2001-02-22 20:51 ` Pavel Machek
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='96vdq1$t90$1@cesium.transmeta.com' \
--to=hpa@zytor.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