From 06a79f7a6e728d3adb5add8aebbbfb797fa23cdf Mon Sep 17 00:00:00 2001 From: guy fleury iteriteka Date: Wed, 6 Jan 2021 23:26:10 +0200 Subject: remove open_symlink issue. * open_issues/open_symlink.mdwn: delete file. Message-Id: <20210106212610.5532-3-gfleury@disroot.org> --- open_issues/open_symlink.mdwn | 30 ------------------------------ 1 file changed, 30 deletions(-) delete mode 100644 open_issues/open_symlink.mdwn diff --git a/open_issues/open_symlink.mdwn b/open_issues/open_symlink.mdwn deleted file mode 100644 index 663bfcbd..00000000 --- a/open_issues/open_symlink.mdwn +++ /dev/null @@ -1,30 +0,0 @@ -[[!meta copyright="Copyright © 2012, 2013 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!tag open_issue_glibc]] - - -# IRC, freenode, #hurd, 2012-01-02 - - hm, is it a known issue that open("somesymlink", O_RDONLY | - O_NOFOLLOW) does not fail with ELOOP? - pinotree: iirc there is code for it, maybe not the same behavior as - on linux - - -## IRC, OFTC, #debian-hurd, 2013-05-08 - - the hurd issue is that O_NOFOLLOW seems broken on symlinks, and - thus open(symlink, O_NOFOLLOW) doesn't fail with ELOOP - I don't really see why it should fail - since NOFOLLOW says not to follow the symlink - yeah, but you cannot open a symlink - ah right ok - interesting :) -- cgit v1.2.3