Where did read-symlink go?
Göran Weinholt
(31 Jul 2019 18:40 UTC)
|
Re: Where did read-symlink go?
John Cowan
(31 Jul 2019 18:46 UTC)
|
Re: Where did read-symlink go?
hga@xxxxxx
(31 Jul 2019 19:00 UTC)
|
Re: Where did read-symlink go?
John Cowan
(31 Jul 2019 19:01 UTC)
|
Re: Where did read-symlink go?
hga@xxxxxx
(31 Jul 2019 19:16 UTC)
|
Re: Where did read-symlink go? Lassi Kortela (31 Jul 2019 19:05 UTC)
|
Re: Where did read-symlink go?
Lassi Kortela
(31 Jul 2019 19:02 UTC)
|
Re: Where did read-symlink go?
Göran Weinholt
(31 Jul 2019 20:20 UTC)
|
Re: Where did read-symlink go?
John Cowan
(31 Jul 2019 20:30 UTC)
|
Re: Where did read-symlink go?
hga@xxxxxx
(31 Jul 2019 20:47 UTC)
|
Re: Where did read-symlink go? Lassi Kortela 31 Jul 2019 19:05 UTC
> This hits my major long term use Scheme case: backup programs, where you > must capture a great deal of information about all file objects. > > On the other hand, quite a bit more is needed for certain types, or > should I say qualities, of backups, vs. a tar equivalent: Good point! Things like rsync() et.al. This didn't occur to me at all. Also, any procedure for symbolic links introduces a potential point of incompatibility with Windows (which IIRC now has 1-3 different kinds of symlinks, depending on how you count, none of which work as well as Unix's one kind of symlink).