From: Niall O Broin (niall at domain linux.ie)
Date: Mon 14 May 2001 - 11:59:16 IST
Conor Daly wrote
> mkisofs -J -r -o cd.iso /path/to/files/with/symlinks
>
> produces a CDROM with symlinks in the appropriate places though doze cannot
> use them.
I hate that ! When I tried that first, I did
mkisofs -o conor.iso conor
and got, inter alia
mkisofs: Symlink conor/d2/passwd ignored - continuing.
Then I though I'd try Rockridge and see if that worked, so I did
mkisofs -o -r conor.iso.rr conor
and got, inter alia
mkisofs: Symlink conor/d2/passwd ignored - continuing.
and then when I saw your mail this morning I though "that's strange - Jolit
can't be letting symlinks work, because 'doze doesn't understand the
concept, so it must be Rockridge, but yet that didn't work for me. So I
looked back in my history file and what do I find
mkisofs -o conor.iso.rr conor
No fscking -r - aargh !
So, given that, the solution to your problem is to use hard links, rather
than symbolic links. Rockridge also supports them, and it appears that 'doze
does too - I just made a CD with -J -r with three directories, and one file
in one dir. which is symlinked into the second dir. and hard linked into the
third dir. Sure 'nuff 'doze sees the symlink but it just appears as an empty
file. The hard linked file is, however, visible, as are its contents. One
caveat - I tried this with a file with a short filename, so the Joliet long
filename compatibility wasn't tested. As far as seeing the hard linked file
was concerned, it didn't matter whether I built in Joliet support or not,
but without Joliet support, 'doze did its filename case thing i.e. it showed
very file with an initial cap.
Regards,
Niall
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:10:17 GMT