linux-kernel - Re: graceful handling of removing a plugable storage device that is being written to

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <201109112106.17705.Martin@lichtvoll.de>
Date:	Sun, 11 Sep 2011 21:06:17 +0200
From:	Martin Steigerwald <Martin@...htvoll.de>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	"Hin-Tak Leung" <hintak_leung@...oo.co.uk>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-btrfs@...r.kernel.org
Subject: Re: graceful handling of removing a plugable storage device that is being written to

Am Sonntag, 11. September 2011 schrieb Geert Uytterhoeven:
> On Sun, Sep 11, 2011 at 18:53, Martin Steigerwald <Martin@...htvoll.de> 
wrote:
> > Frankly, I never tried this on AmigaOS. I know that AmigaOS expects
> > the exact same floppy disk to be inserted again. Only the same name
> > isn´t enough. But I have no idea, what AmigaOS would have done, when
> > I inserted
> 
> Are you sure the volume name wasn't enough?
> For most things, it relied on the volume name, that's how you could map
> floppy names to hard drive directories using assigns.

Yes, I am pretty sure I tried that back then. Difficult to repeat at the 
moment, since I think at least the high density disk drive in my A4000 is 
toast since quite a while.

Anyway, if Linux implements something like that it should not only depend 
on a volume name ;).

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/