News for hackers. Stuff that matters.
Re:Symlinks in Windows 10 by X-Istence on Monday December 05, 2016 @09:23PM (#13111758)
Can we get file deletion in windows without raising an error because the file happens to be opened by some program?
Re:Symlinks in Windows 10 by stebalien on Monday December 05, 2016 @09:28PM (#13111787)
Not without breaking every program under the sun. Currently, programs on Windows can assume that the file associated with a path won't change while the file is open (at least I hope so or some of my code is a bit racy...).
Re:Symlinks in Windows 10 by captainmuon on Tuesday December 06, 2016 @08:36AM (#13114444)
You could make it so that an application holding a file handle will always see this filename existing as long as the file is open. This is similar too, but not quite, what happens under Linux (the filename goes away, but the open file is still accessible as long as one process holds an open handle).

Or, if you wanted to be extra careful, just introduce a new locking flag (LOCK_DONT_LOCK_CAN_DELETE or whatever :-)). Then bug the authors of the most popular editors and the most buggy applications (which block files unneccesarily) to set the flag. If you want to, you could create a compatibility shim to force enable / disable this feature for a given application. (Edit: apparently this flag already exists? FILE_SHARE_DELETE?)

This is tricky, but probably not harder than e.g. modernizing the console subsystem.

Re:Symlinks in Windows 10 by kevingadd on Monday December 05, 2016 @09:55PM (#13111894)
Same goes for directories, yeah. The linux approach can create some really bad user experiences and weird bugs. It's sysadmin-friendly but no good for regular people.
Re:Symlinks in Windows 10 by aindhaden on Tuesday December 06, 2016 @08:23AM (#13114371)
I don't see what "regular people" has to do with it... you either know how your filesystem works or you don't. I you don't, the Linux way (I deleted a file but it's still in my editor) can be just as confusing as the Windows way (I can't delete or move or rename this file because it says it's in use, but I don't have any programs open that use it).
Re:Symlinks in Windows 10 by rleigh on Tuesday December 06, 2016 @09:37AM (#13114844)
Not if it's a CIFS mount on a UNIX platform. I'm sure there are other examples. In practice, most software copes just fine with this arrangement.

I suspect that the breakage would be fairly limited, and I for one would love for this to happen. The amount of stuff which can't be done because of this design decision is huge; proper package management without numerous reboots would be one, and I think the benefit of that and having semantics common with Unix platforms would outweigh the breakage.

Re:Symlinks in Windows 10 by yread on Tuesday December 06, 2016 @02:40AM (#13112894)
It's pretty useful for lightweight inter process synchronization
Re:Symlinks in Windows 10 by tcbawo on Monday December 05, 2016 @10:41PM (#13112065)
Perhaps a Copy On Write scheme could work?
Re:Symlinks in Windows 10 by jungletek on Monday December 05, 2016 @11:31PM (#13112268)
Re:Symlinks in Windows 10 by NTripleOne on Wednesday December 07, 2016 @07:02AM (#13121954)
Site triggers a malware warning in chrome, just a heads up.
Re:Symlinks in Windows 10 by andromeduck on Monday December 05, 2016 @11:20PM (#13112230)
A convenient just kill it button would also work imo.
Re:Symlinks in Windows 10 by tonto on Monday December 05, 2016 @09:59PM (#13111908)
there are myriad other reasons files won't delete on Windows that are super annoying ("system file"? Etc)
Re:Symlinks in Windows 10 by PeCaN on Monday December 05, 2016 @10:12PM (#13111947)
That… seems like probably a mistake, partly because of existing programs and also because it's not too clear what the correct behavior is there. Yes it's annoying, but I think it's also probably the least surprising behavior.