Empty symlinks and full POSIX compliance

Posted May 23, 2013 20:08 UTC (Thu) by viro (subscriber, #7872)
Parent article: Empty symlinks and full POSIX compliance

Sigh...

1) there was a kinda-sorta sane followup and yes, it might make sense to remove that check from symlink creation. Giving that rationale from the very beginning, instead of "we have decided that existing behaviour is bug; we are POSIX, so a bug it is" would've worked a lot better.

2) empty symlinks present on filesystem are, indeed, handled - semantics of those happens to be "just stay in parent".

3) to all kinds of kooks with agenda^W^W^Wactivists: get a life, would you? There are places for all kinds of perversions, including advocacy; if you feel like buggering ducks, wanking at the photo of Nixon/Brezhnev kiss, promoting *BSD/systemd/whatnot - it's your business, just keep the discussion in alt.sex.* or appropriate pr0n sites.

Empty symlinks and full POSIX compliance

Posted May 25, 2013 9:00 UTC (Sat) by tpo (subscriber, #25713) [Link]

> 3) to all kinds of kooks with agenda^W^W^Wactivists: get a life,
> would you? There are places for all kinds of perversions,
> including advocacy; if you feel like buggering ducks,
> wanking at the photo of Nixon/Brezhnev kiss,
> promoting *BSD/systemd/whatnot - it's your business,
> just keep the discussion in alt.sex.* or appropriate pr0n sites.

Take a short break from the kernel business to fix that mirror of yours.
*t