From: Mark Hounschell <markh@compro.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: amiga affs support broken in 2.4.x kernels??
Date: Tue, 17 Apr 2001 15:11:54 -0400 [thread overview]
Message-ID: <3ADC957A.4EC55BFA@compro.net> (raw)
In-Reply-To: <3AD59EB9.35F3A535@compro.net> <3AD9FEDD.2B636582@linux-m68k.org> <3ADAEA9B.D70DC130@compro.net> <3ADB1837.A0AE3020@linux-m68k.org> <3ADC3262.C97B475@compro.net> <3ADC85A1.4755C87F@linux-m68k.org>
Roman Zippel wrote:
>
> Could you try the attached patch? I forgot to initialize a variable
> correctly.
> (I also put a new version at
> http://www.xs4all.nl/~zippel/affs.010417.tar.gz)
>
> > I beleive the filesystem is ffs
> > but not exactly sure. How do I tell?
>
> It's printed if you mount with '-overbose', but it shouldn't be needed
> anymore. :)
>
> bye, Roman
>
> ------------------------------------------------------------------------
> Name: affs.diff
> affs.diff Type: Plain Text (text/plain)
> Encoding: 7bit
Roman,
That seems to have done it. I'm now able to mount,read,and write to
affs
file systems. With an scsi zip drive with 3 affs partitions on it and an
affs hardfile(loop) that I use with UAE occasionally. Looks good to me.
I'll be using this functionality quite a bit so I'll notify you of any
anomalies if it's ok. Thank you for your efforts.
Regards
Mark Hounschell
markh@compro.net
prev parent reply other threads:[~2001-04-17 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 12:25 amiga affs support broken in 2.4.x kernels?? Mark Hounschell
2001-04-15 20:04 ` Roman Zippel
2001-04-16 12:50 ` Mark Hounschell
2001-04-16 16:05 ` Roman Zippel
2001-04-17 12:09 ` Mark Hounschell
2001-04-17 18:04 ` Roman Zippel
2001-04-17 19:11 ` Mark Hounschell [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=3ADC957A.4EC55BFA@compro.net \
--to=markh@compro.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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