Sujet : Re: Desktop file "flies" away
De : 186283 (at) *nospam* ud0s4.net (186282@ud0s4.net)
Groupes : comp.os.linux.miscDate : 01. Sep 2024, 23:54:28
Autres entêtes
Organisation : wokiesux
Message-ID : <m5ecnUB69oMIf0n7nZ2dnZfqnPWdnZ2d@earthlink.com>
References : 1 2 3 4 5 6 7 8 9 10 11 12
User-Agent : Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
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 ...
Can't do it directly with 'cp', but can do it
indirectly.
Now, scarier, would be to tweak the inode entries
so that /Desktop and /Desktop/Desktop both point
to /Desktop ... which would have the effect of
a 'circular' reference. I think you can kinda fake
that with symlinks, but deliberately corrupting
the inode entries would be more, well, fun.