Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Rich <rich@example.invalid>
Newsgroups: comp.os.linux.misc
Subject: Re: Case Insensitive File Systems -- Torvalds Hates Them
Date: Tue, 6 May 2025 22:27:22 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 29
Message-ID: <vve2ca$3u54v$1@dont-email.me>
References: <pan$4068a$3910f4f1$8cbecede$9e42905e@linux.rocks>   <slrn1013t50.1aev.rotflol2@geidiprime.bvh> <vAGdnR-Fj9qGS4_1nZ2dnZfqn_udnZ2d@giganews.com> <slrn1016uic.2qk.rotflol2@geidiprime.bvh> <vv24n5$rjdd$1@dont-email.me> <wwv34dnt165.fsf@LkoBDZeT.terraraq.uk> <vv4ri2$35qch$15@dont-email.me> <wwvplgp68qb.fsf@LkoBDZeT.terraraq.uk> <vv5nmd$3hdg$4@dont-email.me> <wwvsellcv8w.fsf@LkoBDZeT.terraraq.uk> <vv7im0$1qufc$3@dont-email.me> <wwvv7qglchg.fsf@LkoBDZeT.terraraq.uk> <vv7s6q$235td$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 07 May 2025 00:27:24 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="6a1badfd4c1f07a9fc35f1396d64bc99";
	logging-data="4134047"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/V0j7xYuQ/+S3C2r1tbZk3"
User-Agent: tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
Cancel-Lock: sha1:h3zhe5FJALLohNED6kNPtMMeru4=

The Natural Philosopher <tnp@invalid.invalid> wrote:
> On 04/05/2025 14:41, Richard Kettlewell wrote:
>> I mean you can trace the transmission of the command line from parent to
>> child process through the startup. There’s no splitting in there, it’s
>> an array of strings from top to bottom.
> 
> But the command line is not an array of strings... any more than this 
> line of text is. That's what I don't understand. It's a single string

The shell (bash/csh/tcsh/ksh/ash/etc.) reads a line of text from you 
when you type it in and press return/enter.

>> The splitting on spaces (and handling of quotes etc) happens in the 
>> shell.
> 
> An array by definition is already split. On what basis is it split?

The shell performs the "splitting" from a "line of text" into 
individual strings.

All of the kernel, C the language, and libc the library routines 
handles the "command line" values as an array of strings.

The shell that reads in that line from you is what splits it up to make 
it compatible with the kernel/C/libc interface.

Or, said another way, the shell (bash/csh/etc) is the "translator" from 
"single line of text" into "array of strings" that the rest of the 
interface expects to receive.