Cygwin
-
I am currently re-installing Cygwin x64 as a recent crash made it go FUBAR (the crash was caused by VirtualBox. No real surprise there, eh?) I also will be updating a number of packages, such as Git (1.7.9 -> 1.8.4.1), Bash (4.1.something -> 4.2), and so on. How many people here use Cygwin? How many knew there is now a x64 version? How many have no clue what I am talking about? How many don't care?
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
I am currently re-installing Cygwin x64 as a recent crash made it go FUBAR (the crash was caused by VirtualBox. No real surprise there, eh?) I also will be updating a number of packages, such as Git (1.7.9 -> 1.8.4.1), Bash (4.1.something -> 4.2), and so on. How many people here use Cygwin? How many knew there is now a x64 version? How many have no clue what I am talking about? How many don't care?
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
Cygwin is great! I've been using it for years. I too recently discovered there's a 64-bit version by chance when I went to install it on a machine. I've never had to re-install it though, but I also haven't used it inside a virtualbox guest OS. I wouldn't think that would be a problematic configuration though, VirtualBox seems to work pretty smoothly.
-
Cygwin is great! I've been using it for years. I too recently discovered there's a 64-bit version by chance when I went to install it on a machine. I've never had to re-install it though, but I also haven't used it inside a virtualbox guest OS. I wouldn't think that would be a problematic configuration though, VirtualBox seems to work pretty smoothly.
Actually, VirtualBox caused Windows 8.1 to BSOD, corrupting several HDD sectors. VB also has issues with networking on Windows 8.1, and crashes. The Cygwin setup encountered an error and failed due to a network issue. All five mirrors I tried gave the same error, so I think a Cygwin package is corrupt. They usually get those fixed quickly, IME.
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
Actually, VirtualBox caused Windows 8.1 to BSOD, corrupting several HDD sectors. VB also has issues with networking on Windows 8.1, and crashes. The Cygwin setup encountered an error and failed due to a network issue. All five mirrors I tried gave the same error, so I think a Cygwin package is corrupt. They usually get those fixed quickly, IME.
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
Interesting.... I have one Win8 machine and recently upgraded to 8.1 but haven't yet used VirtualBox on it. I have had issues with installing VirtualBox on a machine which had VPN client software that setup a virtual adapter. The VirtualBox installer would just hang due to that adapter. Scary that virtual box would screw up the drive contents! So a clean re-install got cygwin working again?
-
Interesting.... I have one Win8 machine and recently upgraded to 8.1 but haven't yet used VirtualBox on it. I have had issues with installing VirtualBox on a machine which had VPN client software that setup a virtual adapter. The VirtualBox installer would just hang due to that adapter. Scary that virtual box would screw up the drive contents! So a clean re-install got cygwin working again?
Still fails. I have no clue what is going on, and I will try redownloading the installer tomorrow. My internet connection is kinda flaky at night.
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
I am currently re-installing Cygwin x64 as a recent crash made it go FUBAR (the crash was caused by VirtualBox. No real surprise there, eh?) I also will be updating a number of packages, such as Git (1.7.9 -> 1.8.4.1), Bash (4.1.something -> 4.2), and so on. How many people here use Cygwin? How many knew there is now a x64 version? How many have no clue what I am talking about? How many don't care?
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
I am currently re-installing Cygwin x64 as a recent crash made it go FUBAR (the crash was caused by VirtualBox. No real surprise there, eh?) I also will be updating a number of packages, such as Git (1.7.9 -> 1.8.4.1), Bash (4.1.something -> 4.2), and so on. How many people here use Cygwin? How many knew there is now a x64 version? How many have no clue what I am talking about? How many don't care?
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
I am currently re-installing Cygwin x64 as a recent crash made it go FUBAR (the crash was caused by VirtualBox. No real surprise there, eh?) I also will be updating a number of packages, such as Git (1.7.9 -> 1.8.4.1), Bash (4.1.something -> 4.2), and so on. How many people here use Cygwin? How many knew there is now a x64 version? How many have no clue what I am talking about? How many don't care?
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
Brisingr Aerowing wrote:
How many have no clue what I am talking about?
Cygwin? Maybe I'm getting too old now but I never heard of it until I saw you write about it. :(
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
Brisingr Aerowing wrote:
How many have no clue what I am talking about?
Cygwin? Maybe I'm getting too old now but I never heard of it until I saw you write about it. :(
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
Unless you have a use for it you probably wouldn't hear about it - I used it a few years ago to enable SSH on my Win box - works very well and reasonably light on resources.
We can’t stop here, this is bat country - Hunter S Thompson RIP
Question to ask myself later: what is SSH?
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
Question to ask myself later: what is SSH?
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
I am currently re-installing Cygwin x64 as a recent crash made it go FUBAR (the crash was caused by VirtualBox. No real surprise there, eh?) I also will be updating a number of packages, such as Git (1.7.9 -> 1.8.4.1), Bash (4.1.something -> 4.2), and so on. How many people here use Cygwin? How many knew there is now a x64 version? How many have no clue what I am talking about? How many don't care?
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
Question to ask myself later: what is SSH?
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
I am currently re-installing Cygwin x64 as a recent crash made it go FUBAR (the crash was caused by VirtualBox. No real surprise there, eh?) I also will be updating a number of packages, such as Git (1.7.9 -> 1.8.4.1), Bash (4.1.something -> 4.2), and so on. How many people here use Cygwin? How many knew there is now a x64 version? How many have no clue what I am talking about? How many don't care?
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
Still fails. I have no clue what is going on, and I will try redownloading the installer tomorrow. My internet connection is kinda flaky at night.
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
Last time I had a look at it, the 32bit version was pretty broken but at least semi-usable. The 64bit version was completely borken, seemingly beyond repair, but I guess it's been fixed now..
-
What are you all talking about? Cygwin is rock-stable. Any time it goes wrong, a simple rebase fixes everything (and it's not Cygwin's fault, it's a shitty windows DLL model).
vl2 wrote:
a simple rebase fixes everything
If something requires fixing, that means it's broken. It's also entirely its own fault - plenty of software works just fine on Windows without periodically using the excuse "yes but DLL model".
vl2 wrote:
Cygwin is rock-stable.
Ok. Like I said, I haven't used it in a while. Maybe it got better.
-
vl2 wrote:
a simple rebase fixes everything
If something requires fixing, that means it's broken. It's also entirely its own fault - plenty of software works just fine on Windows without periodically using the excuse "yes but DLL model".
vl2 wrote:
Cygwin is rock-stable.
Ok. Like I said, I haven't used it in a while. Maybe it got better.
DLL offsets are broken by Windows and the other windows software. And windows does not support position-independent DLLs (in 21st century! omg!), so the usual Unix model does not map well onto windows practice. I've been using cygwin since around 1999, and it was pretty solid back then. The only real problem with cygwin (back then, and still affecting) is load times for heavy C++ applications, due to a lack of lazy static initialisation (again, thanks to an outdated and crappy COFF model).
-
DLL offsets are broken by Windows and the other windows software. And windows does not support position-independent DLLs (in 21st century! omg!), so the usual Unix model does not map well onto windows practice. I've been using cygwin since around 1999, and it was pretty solid back then. The only real problem with cygwin (back then, and still affecting) is load times for heavy C++ applications, due to a lack of lazy static initialisation (again, thanks to an outdated and crappy COFF model).
vl2 wrote:
I've been using cygwin since around 1999, and it was pretty solid back then.
Really? Never even a "nope, there's a space in that path so I'm just going to completely freak out"? The first (and only) time I tried the 64bit version, it just completely refused to work at all. Some arcane error when trying to start that shell thing.
-
vl2 wrote:
I've been using cygwin since around 1999, and it was pretty solid back then.
Really? Never even a "nope, there's a space in that path so I'm just going to completely freak out"? The first (and only) time I tried the 64bit version, it just completely refused to work at all. Some arcane error when trying to start that shell thing.
