[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] Ramdisk strange behaviour ?



On Fri, 1 Oct 2010 08:18:38 , "Jo Even Skarstein" <joska@online.no> wrote:
>
> From: "Jean-Luc CECCOLI" <Jean-Luc.Ceccoli@wanadoo.fr>
> Sent: Thursday, September 30, 2010 11:53 PM
> To: <mint@lists.fishpool.fi>
> Subject: [MiNT] Ramdisk strange behaviour ?
>
> > Maybe did I miss something, but I discovered something strange
> > with the ramdisk (Trunk from 27/09, IIRC).
> > The ramdisk is assigned to R:\.
> > I open R:\ by double-clicking its letter. Say it's window "A".
> > I then open the unified drive and either double-click onto "ram"
> > or "r", which opens another window, "B" which is to be the same
> > content as "A".
> > I drag a file from a working drive and drop it into "A", then
> > the file is copied and correctly appears into both "A" and "B".
> > I drag a file from a working drive and drop it into "B", then
> > nothing happens.
> > Is this normal ?
>
> I wouldn't think so. What desktop are you using? What happens if you try the
> same operation with cp or a different desktop?
>
Hello,

I'm using Thing 1.27 (hoping some day maybe a 1.28 or 1.29...).
Using cp would mean being able to distinguish R:\ from /u/r, which
ATM seems not possible :
------------------- START ----------------
root@FalCT60:/root>cd /u/r
bash: cd: /u/r: No such file or directory
-------------------- END -----------------
So, I can't tell. :-(

Regards,

J.-Luc