Date: Fri, 16 Oct 2020 13:27:57 +0200 From: Michael Schuster <michaelsprivate@gmail.com> To: Ralf Mardorf <ralf-mardorf@riseup.net> Cc: freeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: sh scripting question Message-ID: <CADqw_gJTm1jtVHHaUe=FAR8xOdC0Oi62De2z2wkDjaTEO_TRnA@mail.gmail.com> In-Reply-To: <20201016132516.71e06c69@archlinux> References: <d50ba2c9-617f-6842-ef89-f5933be8f8b3@hotmail.com> <DB8PR06MB64427D88E17F02711EE657A3F6030@DB8PR06MB6442.eurprd06.prod.outlook.com> <20201016113408.16d58d68@archlinux> <DB8PR06MB644292D3C0309B5DADADF69BF6030@DB8PR06MB6442.eurprd06.prod.outlook.com> <20201016132516.71e06c69@archlinux>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 16, 2020 at 1:25 PM Ralf Mardorf <ralf-mardorf@riseup.net> wrote: > [...] > > On the quick I was unable to create a file with a > > / > > in it's name (Linux, login shell bash, just using shell commands, no > tool explicitly aimed to edit/corrupt file system entries). I guess a > file name containing a "/" overTRUMPs all other odd file names. > that's because '/' is interpreted by the kernel, whereas all other "special" characters are special to the shell(s). cheers -- Michael Schuster http://recursiveramblings.wordpress.com/ recursion, n: see 'recursion'
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADqw_gJTm1jtVHHaUe=FAR8xOdC0Oi62De2z2wkDjaTEO_TRnA>