symbolic links to dirs are not evaluated when needed

[boemann]

So if on a harddisk (tied to a directory structure on windows) I have a symbolic link to another directory. Then I cant cd into that symbolic link before the directory has been listed.

So:
makedir sys:test/file
Makedir sys_test/link sys:test/file soft

Then reboot and directly:
cd sys:test/link

it will complain that the object doesn't exist

now do:
dir sys:test
cd sys:test/link

and it works, so there obviously is a bug.

[AmiClassic]

makedir sys:test/file

Did you check under some filemanager if such a folder was created? This should not work

[Toni Wilen]

Which AmigaOS version does this require? At least 3.1 makedir does not seem to have soft parameter. (For me default is always 3.1)

[thomas]

Probably it should read Makelink instead of Makedir and also sys:test instead of sys_test.

[boemann]

yes makelink sorry

and as far as making test/file yes it was just a little shorthand and the name should really be drawer as it is obviously not a file

[boemann]

Ping ?

[DisasterIncarna]

theres more than 1 makelink, so their still probably waiting for you to list which OS and which makelink variant, ie: if you used the native one bundled with your os or 1 of the alternatives on aminet. Havent tried on WinUAE yet but on FS-UAE makelink doesnt function as expected when using Directory mode harddrives, and only functions right when using a native filesystem, does work linking directory mode source TO a native filesystem destination like RAM: however..

https://eab.abime.net/showthread.php?t=111215

Originally Posted by FrodeSolheim

Hmm, without having looked into it yet, I suspect *soft links* may be feasible to implement in a cross-platform manner (presumably, AmigaOS itself handles the logic and the file system itself must only store the link target). Hard links is presumably a feature in the file system itself and more difficult to implement.

[Toni Wilen]

Fix examples first. I won't attempt to guess, even if it looks obvious.

[midimax]

Wouldn't that be kind a security risk for the host Machine?

For example, just as an dumb Idea, create in AmigaOS a "Windows" directory in your Amiga "C:", use Amigas Makelink to make a symbolic link to that. This now creates at the host directory a symbolic link to you know to where. Remove the Amiga sides target directory and have fun accessing that host directory through that link.

[boemann]

makedir sys:test
makedir sys:test/targetdir
cd sys:test
makelink link sys:test/targetdir soft

Then reboot and then this will fail:

cd sys:test/link

if you then do:

dir sys:test

then the cd will work if you try it again:

cd sys:test/link

[Toni Wilen]

Unfortunately that won't work with WB 3.1 (see my first post). EDIT: Does makelink from Aminet work?

Wouldn't that be kind a security risk for the host Machine?

UAE directory filesystem only allows creation of softlinks (softlink target) that are already accessible from Amiga side (same or another mounted directory filesystem).

[boemann]

Sorry yes it requires AmigaOS 3.2.
I've tested it with makelink from aminet and that works too I mean it can create the link - the bug is still there

I've amended my example a bit as makelink wants it first argument to be a name and not a full path and the second argument should be a fully qualified path

[Toni Wilen]

https://www.winuae.net/files/b/winuae.7z should fix it (warning: development version). But I don't have any link test cases so it is someone else's problem to confirm it

[boemann]

Thanks I'll try it out and give you some feedback

[boemann]

It works ! Thanks