Re: [MiNT] RAMFS & kernel

["Helmut Karlowski" <helmut.karlowski@ish.de>]

Am 12.06.2010, 23:38 Uhr, schrieb Alan Hourihane <alanh@fairlite.co.uk>:

> On Sat, 2010-06-12 at 22:31 +0200, Jo Even Skarstein wrote:
> > On 06/12/2010 10:17 PM, Alan Hourihane wrote:
> > > I've been reading this thread but I must say I'm lost as to what to do
> > > to reproduce.
> > >
> > > Can someone list the actual steps and I'll see what the problem really
> > > is.
> >
> > 1. Set clipbrd (xaaes.cnf) to point to a folder in /ram (e.g.
> > clipbrd=u:\ram\clipbrd)
> > 2. Boot XaAES and make sure that the folder above exists.
> > 3. Start qed.
>
> What's the error that qed gets ?
>
> File not found ?
>
> Or something else like an error code ? If so, is it -33 ?


pid  27 (qed): Dopendir(U:\ram\clipbrd\): error -33
pid  27 (qed): Fxattr(U:\ram\clipbrd\): path2cookie returned -33


I guess someone (qed) appends a \ and MiNT looks for 'clipbrd\'.

It works with toswin:

pid  10 (toswin2): do_open(U:\ram\clipbrd\scrap.txt): mode 0x81A4
pid  10 (toswin2): do_open(U:\ram\clipbrd\scrap.txt) -> 0


When I type 'ls /ram/clipbrd\\' in a shell I get:

pid  30 (ls): Fstat64(/ram/clipbrd\): path2cookie returned -33

Don't know if this is related, but on ext2 I may append a \ ('ls  
toswin2\\'):

pid  35 (ls): Fstat64(0, toswin2\)
pid  35 (ls): relpath2cookie(toswin2\, dolast=2, depth=0 [relto 4F997B4,  
5])
pid  35 (ls): relpath2cookie: using relto (4F997B4, 83468956, 5) for dir
pid  35 (ls): disk_changed (5)
pid  35 (ls): relpath2cookie: looking up [toswin2]
pid  35 (ls): relpath2cookie: lookup ok, mode 0x41C0
pid  35 (ls): relpath2cookie: looking up []
pid  35 (ls): relpath2cookie: lookup ok, mode 0x41C0
pid  35 (ls): relpath2cookie: returning 0

...



--
Helmut Karlowski