Linux M68K Architecture development
 help / color / mirror / Atom feed
From: "Kolbjørn Barmen" <linux-m68k@kolla.no>
To: Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Linux and amiga floppy images
Date: Mon, 13 Oct 2008 04:20:29 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.0810130345170.4882@firda.kolla.no> (raw)


Hello!

I had a strange observation a few weeks ago that I intended to check with
you guys, but then forgot all about. :P

I was restoring some old amiga systems, and in that process needed to get
software onto floppies. I have a catweasel and can write out so called ADF
files (amiga floppy images) to floppies just fine with it (excellent
hardware). The problem I had was creating ADFs on linux, I assumes I could
just loopback-mount them with affs and just write files to them, but no -
I always ended up getting I/O-error, and the kernel put the filesystem
write-protected.

Deleting files seems to work ok, but once you try to write  a file, the
filesystem chokes, becomes write-protected and the resulting file is a
0-byte entry.

But I didnt give up there, I tried on different systems... much to my
amusement it worked fine on my linux/m68k systems - amigas, macs and
aranym alike!  OK, I thought, maybe endianness, so I tried on my ppc ibook
running linux - same failures as on the PCs. So - something is done very
correct on m68k in regard to affs, that isnt done correct on other archs.
Anyone know what that might be?

(All systems I tried with were running 2.6.2x, ubuntu, debian, gentoo)

Cheers!

-- kolla

             reply	other threads:[~2008-10-13  2:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13  2:20 Kolbjørn Barmen [this message]
2008-10-13 10:05 ` Linux and amiga floppy images Andreas Schwab

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=alpine.LNX.2.00.0810130345170.4882@firda.kolla.no \
    --to=linux-m68k@kolla.no \
    --cc=linux-m68k@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