Install winrar from /download.htm which mentions /rar/winrar-圆4-602.exe You can get the rar command for windows quite easily and it ends up in C:\Program Files\WinRAR\Rar.exe You can run external executables from within cygwin. Then you can use your bash command directly. The other way is to run rar.exe from cygwin. But then you'd need to adjust your command to run with batch rather than bash. one way is to run rar.exe from cmd.exe without cygwin. Possibly there are lots of gotchas.There's two ways you could do this. Wondering what made win32k folks disable it. any language without explicit thread handling can actually use them). I know there are plenty of other uses (for example this way "lua" can do threads with just a bit of a communication library on top. After all for a long time there was a commercial UNIX compatible offering on Windows that probably used fork() all over and must've worked (also it supported case-sensitive names for the filesystem)īTW, the coolest usage of fork(), and granted a pain in the ass to port possibly was the one in REDIS where antirez used it to fork() at certain time the current process, then write back the state of memory knowing that it'll get a "snapshot" of it, and if writes to disk succeed, this "snapshot" would correctly and fully be written to the disk. If I'm not mistaken the Windows Kernel actually does support fork()-ing, but the win32k system somehow "forbids" it (lots of grains of salt). And HiDPI support is improving quickly in Linux land.įrom little I've read on cygwin mailing list (btw, cool folks over there) - it seems the problem is not very easy. Putting up with poor HiDPI support in Linux was much more tolerable than the horrors of trying to use Unix utilities in Windows. To keep everything sane, start with the standard cygwin or msys installer, and install everything using that.ĭoes conemu include mingw-get? If so, that sounds like it might be a good solution. IIRC, vagrant is built with cygwin, so you have to make sure you use a cygwin rsync with it, the msys rsync won't work. And some things aren't compatible with each other. You now have up to 5 copies of SSH installed, all storing their private keys, cert stores and configuration in different places. Each of these require SSH for full operation, so in the interest of making things easy, the installers bundle SSH. So you install MobaXTerm, vagrant, emacs, msysgit, and rsync. Let's say you want to set up a standard dev setup. This isn't a problem that's limited to MobaXTerm, but the way MobaXTerm does things makes it harder to fix. The big problem with MobaTerm is that it includes really old versions of the standard unix utilities, and it's difficult to integrate with newer & missing utilities. If I ever have to use Windows again, god forbid, I'm definitely checking this out. Dynamic recompilation is obviously a way more preferable approach. Plus, it'd completely fail on 64-bit platforms. I eventually gave up because it was obviously not a tenable approach. (At least, I thought I did - I cannot now find any of the actual code. And, of course, I'd have to replicate this otherwise glibc would crash out. Not all the horror was Windows, mind: Linux's interface to executables is barely documented and extremely fragile, involving passing a key-value table full of magic parameters on the stack after the argument and environment tables. (The LBW instruction patching code is here. I'm actually now kind of scared at how much working hackery LBW ended up containing: it'd dynamically patch the binary after trapping out at instructions manipulating things that Windows wouldn't allow access to. Yeah, it ground to a halt due to fundamental differences in the way Linux and Windows binaries work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |