Re: Desktop file "flies" away

e
On 9/1/24 7:41 PM, Lawrence D'Oliveiro wrote:

On Sun, 1 Sep 2024 17:54:28 -0400, 186282@ud0s4.net wrote:
 

On 9/1/24 3:05 AM, Lawrence D'Oliveiro wrote:
>

On Sat, 31 Aug 2024 22:41:49 -0400, 186282@ud0s4.net wrote:
>

On 8/31/24 4:10 AM, Lawrence D'Oliveiro wrote:

On Fri, 30 Aug 2024 02:16:14 -0400, 186282@ud0s4.net wrote:
>

On 8/29/24 11:03 PM, Lawrence D'Oliveiro wrote:
>

On Tue, 27 Aug 2024 21:21:09 -0400, 186282@ud0s4.net wrote:
>

Indeed pure genius. GUI file-managers make this all the easier.
Cut tree, paste tree into the same dir.

>
GUI or no GUI, the kernel won’t let you move a directory into
itself.

>
Yet SOMEHOW it gets done - seen it ... must be certain things that
fool the kernel's logic.

>
Not a chance.

>
I did go on to describe how you can get /Desktop/Desktop/
via 'indirect' replication.

>
All you’ve done is create one directory called “Desktop” inside another
directory called “Desktop”.

>
That was the original subject under discussion ...

 Which is not possible using standard kernel APIs, GUI tool or no GUI tool.

   As demonstrated, not DIRECTLY ... but INDIRECTLY.

Now, scarier, would be to tweak the inode entries so that /Desktop
and /Desktop/Desktop both point to /Desktop

 You’re not trying to suggest your user managed to do that, are you?

   Not sure if it was a "user" per-se, or a rogue application.
   Inodes CAN be corrupted - deliberately or perhaps by
   screwing up lower-level file system stuff. That's not
   how it is *supposed* to work, but, hey ..... I've seen
   messed-up inodes from ill-timed crashes/power-downs.
   fsck or friends start spitting out tons of messages.
   Some rude 'C' run with just enough privs ... or bang
   around with 'dd' just a bit ... some stuff uses
   RAMdisks or whatever too so anything messing with
   that space ........
   Never be TOO surprised at really weird behavior from
   any complex system .
   Anyway, reporting what I saw. I know it CAN happen.
   Consider that for the future. Alas I did not have
   time to analyze in fine detail, had to get it all
   up and running again quick to earn the paycheck.
   I wonder how much other "that's weird" stuff goes
   unreported for the same reason ?