From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 28 Apr 2011 13:11:27 +0100 From: Digby Tarvin To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20110428121127.GD1020@skaro.cthulhu.dircon.co.uk> References: <20110427131041.GA21774@skaro.cthulhu.dircon.co.uk> <0bc37e9990e3c3ebde8276275a170a88@quintile.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Subject: Re: [9fans] spaces in filenames (and filesystems...) Topicbox-Message-UUID: d7496806-ead6-11e9-9d60-3106f5b1d025 On Thu, Apr 28, 2011 at 11:58:01AM +0200, Peter A. Cejchan wrote: > spaces in filenames.. does not it break the rules?? Who actually needs > them?? > > ++pac Mostly people who have grown up with graphical user interfaces and have no appreciation of the command line parsing complexity it adds I think. And of course others that have to interract with such people, such as sharing filesystems with them. On a slightly related topics, one of my constant headaches lately is the problem of deciding what filesystem to put on large capacity removeable storage to give me maximum interoperability... What I really want is somthing that I can copy files to and from from any of my OSs without losing meta-data. NTFS seems to be reasonably capable, but pervesely designed to be difficult to write to other than from Windows. FAT32 has limitations such as with the metadata it can represent, and anything else is problematic with certain commonly used proprietary OSs. If there was one clear winner, then I suppose filesystem drivers could be (maybe are) made available for the proprietary systems. Perhaps this is what UFS was designed for if it is not overly optimised for optical media. Anyone have any ideas here? Regards, DigbyT -- Digby R. S. Tarvin digbyt(at)digbyt.com http://www.digbyt.com