Path: ...!3.eu.feeder.erje.net!feeder.erje.net!usenet.goja.nl.eu.org!nntp.terraraq.uk!.POSTED.tunnel.sfere.anjou.terraraq.org.uk!not-for-mail
From: Richard Kettlewell <invalid@invalid.invalid>
Newsgroups: comp.os.linux.misc
Subject: Re: Odd behaviour?
Date: Thu, 05 Dec 2024 16:57:20 +0000
Organization: terraraq NNTP server
Message-ID: <wwvmshaxe33.fsf@LkoBDZeT.terraraq.uk>
References: <vinptp$b4ht$1@dont-email.me> <bn942lxcti.ln2@Telcontar.valinor>
	<vinvtv$ci03$1@dont-email.me> <lr9ep2F6hc8U1@mid.individual.net>
	<viphkr$rnso$9@dont-email.me> <viq7p0$11lmp$1@dont-email.me>
	<virmhp$1fqan$5@dont-email.me> <v6c82lxib.ln2@Telcontar.valinor>
	<vis1f1$1iiku$2@dont-email.me> <vqe82lxjg7.ln2@Telcontar.valinor>
	<vis65i$1jn2s$1@dont-email.me> <pkj82lxaro.ln2@Telcontar.valinor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: innmantic.terraraq.uk; posting-host="tunnel.sfere.anjou.terraraq.org.uk:172.17.207.6";
	logging-data="85742"; mail-complaints-to="usenet@innmantic.terraraq.uk"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Cancel-Lock: sha1:4BHMZjMkVhDuncgm8SSkdue6Etw=
X-Face: h[Hh-7npe<<b4/eW[]sat,I3O`t8A`(ej.H!F4\8|;ih)`7{@:A~/j1}gTt4e7-n*F?.Rl^
     F<\{jehn7.KrO{!7=:(@J~]<.[{>v9!1<qZY,{EJxg6?Er4Y7Ng2\Ft>Z&W?r\c.!4DXH5PWpga"ha
     +r0NzP?vnz:e/knOY)PI-
X-Boydie: NO
Bytes: 2706
Lines: 30

"Carlos E.R." <robin_listas@es.invalid> writes:
> The GUI filemanager is just a filemanager, and follows filemanager
> rules. It displays only ONE directory, not some desktop concoction
> made of several structures and directories.

Union filesystems are a thing, thought I don’t know of any reason to
think one is involved here, and I’d (possibly naively) expected unlink
calls to propagate through them to the appropriate underlying
filesystem.

I don’t have a definitive explanation for the behavior seen. Some
guesswork:

* If a file is sometimes visible and sometimes not that may reflect it
  being repeatedly deleted and re-created.

* If a file is visible in one view and not another than may reflect the
  views actually being different. e.g. user error about what directory
  they are looking at.

* Filesystem corruption of some kind might explain any kind of weird
  behavior, though (at least when running ls) you might expect some kind
  of error message. The kernel log would be likely to contain
  diagnostics in this case.

* A file that’s something to do with an attack may be deliberately
  hidden by the attack software, but perhaps in an inconsistent way
  (attackers screw up too).

-- 
https://www.greenend.org.uk/rjk/