From: Pavel Machek <pavel@suse.cz>
To: zhaoway <zw@debian.org>, linux-kernel@vger.kernel.org
Subject: Re: Newbie ask for help: cramfs port to isofs
Date: Thu, 22 Feb 2001 21:51:46 +0100 [thread overview]
Message-ID: <20010222215146.D14395@bug.ucw.cz> (raw)
In-Reply-To: <877l2lyk3j.fsf@debian.org>
In-Reply-To: <877l2lyk3j.fsf@debian.org>; from zhaoway on Tue, Feb 20, 2001 at 02:03:12PM +0800
Hi!
> I've nearly no prior experience with kernel hacking (nor C if you have
> to ask, haha), sorry in advance for the newbiesh looking. ;-)
>
> See attach for a rough try to port cramfs to isofs which gave me lots
> of oops and reboots and fscks this week. Please if you have some spare
> time to give it a look with your experienced eyes to help me out of
> this helpless state. Thanks alot!
>
> 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.
Nice toy: I believe that it should even _speed up_
operations. Surely if you have k6/400 with 4x cdrom like me ;-).
> My problem is that when I after mount ``$ file somefile.not.cram.ed''
> the kernel hangs. And my de-compression code surely has some thing
strace file somefile.not.cram.ed, and looks what what goes bad.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
prev parent reply other threads:[~2001-02-23 8:57 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
2001-02-22 20:51 ` Pavel Machek [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=20010222215146.D14395@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=zw@debian.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