Sujet : Re: Desktop file "flies" away
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.os.linux.miscDate : 02. Sep 2024, 01:41:09
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vb2u2l$1lsoa$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13
User-Agent : Pan/0.160 (Toresk; )
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.
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?
Desktop file "flies" away
Re: Desktop file "flies" away