Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rainer Weikusat Newsgroups: comp.os.linux.development.system Subject: Re: shred or scrub Date: Mon, 28 Apr 2014 12:06:09 +0100 Lines: 37 Message-ID: <878uqpww66.fsf@sable.mobileactivedefense.com> References: <871twishw0.fsf@sable.mobileactivedefense.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net 5BpIpdJJOpMSiiu1IG4EWQOs+HhhlYE2soGy5pPfp/SJP006E= Cancel-Lock: sha1:WUO73JIV71yofIetxpeSiH/6eCM= sha1:laYGFubVffKszRa6sqr+3k5LHy4= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) Xref: csiph.com comp.os.linux.development.system:662 crankypuss writes: > On 04/27/2014 01:15 PM, Rainer Weikusat wrote: >> crankypuss writes: >>> On 04/26/2014 08:30 AM, David Brown wrote: >> >> [...] >> >>> You seem to think I'm saying that hardware makers should conform to my >>> views of how hardware should work, but what I'm saying is something >>> different, I'm saying that the software on the client system needs to >>> ascertain the nature of the subsystem that serves it files and behave >>> accordingly. >> >> This is not possible. A 'filesystem' is an implementation of an abstract >> 'user interface' providing certain operation which operates on a block >> device, itself an abstract interface to 'all kinds of things providing >> it'. This can be something a primitive as a 'floppy disk drive' where >> the OS block driver actually has to do stuff like turn the motor on and >> off to something as sophisticated as a 'distributed and replicated >> [network] block device', ie a cluster of servers implementing a certain >> protocol whose 'user interfaces' happens to be 'the block device user >> interface', >> >> http://www.drbd.org/home/what-is-drbd/ >> >> How filesystems and 'block device thingies' are combined is generally >> and administrative descision and even 'ordinary harddisks' are actually >> servers connected to local high-speed (or 'not so high-speed') bus which >> are operated by exchanging protocol requests and replies with them. >> > > Thank you for your opinion. This is not 'my opinion'. It's a summary of some facts about the system we're talking about (and some other things which happen to be related to the topic, ie, that current 'hard disks' are actually servers providing an interface supposed to be compatible to some protocol definition).