Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Muttley@dastardlyhq.com
Newsgroups: comp.unix.shell,comp.unix.programmer,comp.lang.misc
Subject: Re: Python (was Re: I did not inhale)
Date: Tue, 20 Aug 2024 07:22:31 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 21
Message-ID: <va1g7n$3a14k$1@dont-email.me>
References: <uu54la$3su5b$6@dont-email.me>
	<g52cnWOOwoz_son7nZ2dnZfqnPWdnZ2d@brightview.co.uk>
	<uvbe3m$2cun7$1@dont-email.me>
	<uvbfii$3mom0$1@news.xmission.com>
	<20240412094809.811@kylheku.com>
	<87il0mm94y.fsf@tudado.org>
	<way-20240413091747@ram.dialup.fu-berlin.de>
	<87il0lldf8.fsf@tudado.org>
	<choices-20240413123957@ram.dialup.fu-berlin.de>
	<v9lm2k$12qhv$1@dont-email.me>
	<v9m4gd$14scu$1@dont-email.me>
	<20240815182717.189@kylheku.com>
	<v9npls$1fjus$1@dont-email.me>
	<v9posc$1rpdj$1@dont-email.me>
	<v9pvoo$1sn55$1@dont-email.me>
	<v9r60h$2289h$2@dont-email.me>
	<v9sa91$2afht$1@dont-email.me>
	<v9tv8o$2iahp$1@dont-email.me>
	<v9uso3$2pdrg$2@dont-email.me>
	<v9v0e0$2q822$1@dont-email.me>
	<v9v7d4$2r6q2$1@dont-email.me>
	<87jzgccltj.fsf@nosuchdomain.example.com>
 <20240819133005.00003757@gmail.com>
Injection-Date: Tue, 20 Aug 2024 09:22:32 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="f1739370b58baedabc1061a7cf69ea40";
	logging-data="3474580"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19cwB53uMH6Ka6NYBaK95wB"
Cancel-Lock: sha1:yhfw1PaDg5gjpArJ2Kuf7/OzvAE=
Bytes: 2608

On Mon, 19 Aug 2024 13:30:05 -0700
John Ames <commodorejohn@gmail.com> boringly babbled:
>NT has its own low-level scheme for identifying devices/representing
>file paths. If you're curious, someone at the Google compound did a
>write-up on it some years back:
>https://googleprojectzero.blogspot.com/2016/02/the-definitive-guide-on-win32-to
>-nt.html
>
>For most practical purposes, users and user-level application software
>pretty much never see this or have to think about it - but it *is*
>there, and it does cause strange corner-case behavior sometimes. (I'm
>pretty sure the underlying reason why cmd.exe sometimes cannot access
>network shares mapped to a conventional drive letter has to do with
>this, f'rinstance.)

To sum up, Microsoft have made a complete dogs dinner of something as simple
and basic as file paths. You couldn't make it up.

Can Windows do non-root level filesystem mounting yet? Ie unix can mount a
new filesystem anywhere in the current filesystem hierarchy.