Date: Fri, 16 Oct 2020 12:23:11 +0100 From: Steve O'Hara-Smith <steve@sohara.org> To: freebsd-questions@freebsd.org Subject: Re: sh scripting question Message-ID: <20201016122311.022f1cf733eec8612d24b857@sohara.org> In-Reply-To: <DB8PR06MB644292D3C0309B5DADADF69BF6030@DB8PR06MB6442.eurprd06.prod.outlook.com> References: <d50ba2c9-617f-6842-ef89-f5933be8f8b3@hotmail.com> <DB8PR06MB64427D88E17F02711EE657A3F6030@DB8PR06MB6442.eurprd06.prod.outlook.com> <20201016113408.16d58d68@archlinux> <DB8PR06MB644292D3C0309B5DADADF69BF6030@DB8PR06MB6442.eurprd06.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 16 Oct 2020 15:55:59 +0530 Manish Jain <bourne.identity@hotmail.com> wrote: > This is where I actually have an entirely different philosophy. When you > create a file with a leading - (or for that matter, weird characters > such as * anywhere in the filename), I think the filesystem driver (i.e. > the kernel) should throw a warning: "Do you really want a filename like > that ?" There is a POSIX standard for portable filenames but no requirement to restrict users to it. By default the only characters not allowed in a filename are / and NUL - which has the advantage of supporting filenames in just about any encoding without problems (useful if you are serving files for international workflows). BTW you have left out the fun and games available by use of backspace and vertical tab in filenames - I have seen sysadmins lose half a day trying to delete files like that (* is another favourite component in sysadmin trap filenames). -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201016122311.022f1cf733eec8612d24b857>