▲ 168 ▼ Linux's Modern NTFS Driver Will Now Correctly Handle Symlinks Created On Windows (www.phoronix.com) submitted 1 year ago by cm0002@programming.dev to c/linux@programming.dev 22 comments fedilink hide all child comments
[–] naught101@lemmy.world 10 points 1 year ago (5 children) What would have been a better solution? permalink fedilink source parent hideshow 5 child comments replies: [–] FizzyOrange@programming.dev 2 points 1 year ago* (3 children) The Plan 9 solution looks better to me. At the very least if you keep them then paths should be resolved lexically. I think most people are under the false impression that they are resolved lexically (i.e. foo/bar/../baz and foo/baz are the same). But IMO it's better just to not have them and use another solution where you might have used them. permalink fedilink source parent hideshow 3 child comments replies: [–] naught101@lemmy.world 4 points 1 year ago (2 children) Sorry, I didn't follow any of that.. What is the plan 9 solution? I searched, but didn't see anything obvious permalink fedilink source parent hideshow 2 child comments replies: [–] FizzyOrange@programming.dev 2 points 1 year ago (1 child) Basically it uses bind mounts instead. See this page for details. I haven't actually used (since Plan 9 is dead) and I doubt it covers every use case for symlinks (e.g. this wouldn't let you commit them to a git repo), but I really think the benefits of symlinks not existing at all would far outweigh the effort of having to think of alternative solutions. Sadly we don't get to live in that alternative history now... :-/ permalink fedilink source parent hideshow 1 child comment replies: [–] naught101@lemmy.world 2 points 1 year ago That problem seems tiny relative to the convenience that symlinks offer... permalink fedilink source parent [–] sunbeam60@lemmy.one 0 points 1 year ago Not having them. permalink fedilink source parent
[–] FizzyOrange@programming.dev 2 points 1 year ago* (3 children) The Plan 9 solution looks better to me. At the very least if you keep them then paths should be resolved lexically. I think most people are under the false impression that they are resolved lexically (i.e. foo/bar/../baz and foo/baz are the same). But IMO it's better just to not have them and use another solution where you might have used them. permalink fedilink source parent hideshow 3 child comments replies: [–] naught101@lemmy.world 4 points 1 year ago (2 children) Sorry, I didn't follow any of that.. What is the plan 9 solution? I searched, but didn't see anything obvious permalink fedilink source parent hideshow 2 child comments replies: [–] FizzyOrange@programming.dev 2 points 1 year ago (1 child) Basically it uses bind mounts instead. See this page for details. I haven't actually used (since Plan 9 is dead) and I doubt it covers every use case for symlinks (e.g. this wouldn't let you commit them to a git repo), but I really think the benefits of symlinks not existing at all would far outweigh the effort of having to think of alternative solutions. Sadly we don't get to live in that alternative history now... :-/ permalink fedilink source parent hideshow 1 child comment replies: [–] naught101@lemmy.world 2 points 1 year ago That problem seems tiny relative to the convenience that symlinks offer... permalink fedilink source parent
[–] naught101@lemmy.world 4 points 1 year ago (2 children) Sorry, I didn't follow any of that.. What is the plan 9 solution? I searched, but didn't see anything obvious permalink fedilink source parent hideshow 2 child comments replies: [–] FizzyOrange@programming.dev 2 points 1 year ago (1 child) Basically it uses bind mounts instead. See this page for details. I haven't actually used (since Plan 9 is dead) and I doubt it covers every use case for symlinks (e.g. this wouldn't let you commit them to a git repo), but I really think the benefits of symlinks not existing at all would far outweigh the effort of having to think of alternative solutions. Sadly we don't get to live in that alternative history now... :-/ permalink fedilink source parent hideshow 1 child comment replies: [–] naught101@lemmy.world 2 points 1 year ago That problem seems tiny relative to the convenience that symlinks offer... permalink fedilink source parent
[–] FizzyOrange@programming.dev 2 points 1 year ago (1 child) Basically it uses bind mounts instead. See this page for details. I haven't actually used (since Plan 9 is dead) and I doubt it covers every use case for symlinks (e.g. this wouldn't let you commit them to a git repo), but I really think the benefits of symlinks not existing at all would far outweigh the effort of having to think of alternative solutions. Sadly we don't get to live in that alternative history now... :-/ permalink fedilink source parent hideshow 1 child comment replies: [–] naught101@lemmy.world 2 points 1 year ago That problem seems tiny relative to the convenience that symlinks offer... permalink fedilink source parent
[–] naught101@lemmy.world 2 points 1 year ago That problem seems tiny relative to the convenience that symlinks offer... permalink fedilink source parent