Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rainer Weikusat Newsgroups: comp.unix.programmer,comp.lang.c Subject: Re: Piping to stdin Date: Sun, 20 Aug 2023 21:57:30 +0100 Lines: 19 Message-ID: <87lee55t51.fsf@doppelsaurus.mobileactivedefense.com> References: <9e7a4bd1-bfbb-4df7-af1a-27ca9625e50bn@googlegroups.com> <87o7j82gix.fsf@fatphil.org> <87v8dde6j3.fsf@bsb.me.uk> <87wmxr9v9l.fsf@fatphil.org> Mime-Version: 1.0 Content-Type: text/plain X-Trace: individual.net FE3vaN8ro92Vk4mp2Y3rsw7u3Zw3p0FLNu3/NLPuokaqntwgs= Cancel-Lock: sha1:vMNUFk/HMAY+D9LVtFapC31uWiQ= sha1:3fdbvnTp2WbJ1K4V9X0M7jyI8vE= sha256:dCuEMujzRJ+HsObxoGMZlbnJor6U6lG8vtIzpxvLsP0= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Xref: csiph.com comp.unix.programmer:14408 comp.lang.c:172599 Muttley@dastardlyhq.com writes: > On Sat, 19 Aug 2023 16:15:32 +0300 > =?UTF-8?B?T8SfdXo=?= wrote: >>On 8/19/23 1:33 PM, Phil Carmody wrote: >>> Ben Bacarisse writes: >>>> Some file systems (depending on mount options) can have complex rules >>>> such as rejecting any name with an invalid UTF-8 sequence. >>> >>> Oooh, now I'm tempted to name files in Latin-1, to deliberately break >>> filesystems that make such assumptions! >>Be careful with that attitude. The "memory-safe" sudo replacement >>doesn't support non-UTF-8 input either: > > Whats memory unsafe about sudo? It's not written in a language whose extremely complicate runtime system that's conjectured to be bug free in this respect by Really Wishful Thinking[tm] is supposed to prevent simple memory access errors C supports.