Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: The Natural Philosopher <tnp@invalid.invalid>
Newsgroups: comp.os.linux.misc
Subject: Re: Case Insensitive File Systems -- Torvalds Hates Them
Date: Wed, 7 May 2025 11:07:04 +0100
Organization: A little, after lunch
Lines: 46
Message-ID: <vvfbc8$usml$2@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>
 <vve2ca$3u54v$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 07 May 2025 12:07:05 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="7ce086d2f75924ae5766c589640c187d";
	logging-data="1012437"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+Hf/g4hfKosjGslFZvDmDO70x0IUwvS3w="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:ySLPgptEwF1lbNxuhW6EtvGGaN0=
In-Reply-To: <vve2ca$3u54v$1@dont-email.me>
Content-Language: en-GB

On 06/05/2025 23:27, Rich wrote:
> 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.

Thanks. I had finally figured out that without the shell there *is* no 
command line.

My geriatric brain was thinking 'you dont need shell to invoke a 
program' But of course then you need exec and friends all of which send 
arrays as arguments

-- 
Of what good are dead warriors? … Warriors are those who desire battle 
more than peace. Those who seek battle despite peace. Those who thump 
their spears on the ground and talk of honor. Those who leap high the 
battle dance and dream of glory … The good of dead warriors, Mother, is 
that they are dead.
Sheri S Tepper: The Awakeners.