I mostly use KMail at home for the same reasons. Though i use fetchmail to retrieve the mails and procmail to pipe them thru ClamAV and SpamAssassin and finally sort them with some scripts of my own.
The fact Kmail use mail dir format, as mutt, let me also check my mail from a remote ssh session.
Ouch, my head hurts... I should never be left with a keyboard around when I'm drunk... First of all, I'm sorry for the rude reply i did and i ask you to excuse me.
In the original post i was trying to highlight the "do" and "don't" one needs to know when working with cygwin. The hard links for example is one problem peoples frequently stumble on. Most of the things you underlined are, of course, common sense. I just end up running into smart ones that think common sense is something only happening to other peoples... possibly when they're asleep, or dead, or both...
For the fork/thread problem, yes you're right again i never put my nose into cygwin source, and probably shouldnt talk of it that badly. Yet it is something peoples should be aware of when considering cygwin for a production environment. Seeking for alternatives isnt probably a too bad idea. I did such a statement because under cygwin i always end up trying to fix problems with programs using forks. Perhaps i am doing something bad, but perhaps cygwin is having a flaw there. I just dont know. Yet i think i'm quite able to find out if a program is badly written, or if it is the underlying system that makes something wrong... To finish this up, generally an afternoon modifying some lines in the code (and taking some fresh beers with a friend) is worth making it compile with.net studio. It works fine and is faster than if i make it under cygwin.
Sorry again for 14-year-old-stupid-reply i did before (and probably for this one too, cheers;-)).
This is pretty much common sense. If you are using...
Now bout your particular problem...
Now, what is really common sense is reading the thing you try to troll on... Guess who is in the middle of the crowd, and that peoples are looking at with a (little) smile?
NTFS handle hard links: cygwin let you make new files with the same node than another one, but sadly, they usually breaks because most win32 programs first rename a file (to make a backup, instead of making a copy) and create a new one.
Hi, I already made a post in a thread about SFU that was looking like (disclaimer: i love cygwin):
1) WSFU is faster (IO/API/...) 2) WSFU is better integrated with win32 architecture (OLE/ODBC/...) 3) WSFU make a lot of things easier than cygwin with windows
BUT, i wouldnt trade cygwin for it, note that i have both installed here. I just isolated what i needed from WSFU and was better than cygwin and added them last in my path. I dont have any preferences, but cygwin is waaay more complete, and you have the +/- the same versions of the application that runs on linux. Same config files work fine, same behaviours (which isnt the case with WSFU), etc.
For me, WSFU is just a little + to cygwin.
Now bout your particular problem (prod env, 24x7), I've experienced very few problems running CygWin in such an environment. I use it since at least 5 years (I remember downloading it at 56k, so it's probably more), but there's some things you need to be aware with cygwin:
Versions of the applications you run: they often differs from what you're used to. Sometimes I ended up with different settings between solaris, linux, win32, etc. This is generally fixed with a recompile of the common denominator version, possibly the latest one.
Performances: As you probably noticed from the other posts, cygwin is an emulation layer. It is slow. And I really mean slow. Something you usually do in nunux in a few seconds might take a few minutes on win32 depending on how it is coded. Forks and threads are really badly implemented. Yet nobody else did better.
Alternatives: Frequently natives win32 programs are faster, better, or both. Have a look on google after alternatives (adding +win32 +unix, and +free if money is a problem). It will save you some time. Maintaining several branches of your scripts might be a good investment, if you factor out the common base, and manage to get them do what they should on different platforms while compiling/installing (and anyway if you start nunux/win32, you might as well just do that, you'll end up with the pot). Though it perhaps require another employee, it's worth it. For cygwin alternatives I'd recommend the SFU (of course), Mingw, GNU utilities for Win32
The DLL Nightmare (Take II): If you dont need too much apps (.exe) relative to cygwin it could be good to just use those. Compile the stuff you want in cygwin, and modify the $INSTALL path, so you can just take that to another machine. The DLL hell here is that you'll probably not only need the cygwin dll but some more... If you have quickview installed on your machine, you can see what DLLs a program use in its Import Section (from the PE header). Else i would recommend OllyDBG (free) or PE Explorer ($$$). Both can lists what DLLs an app use, just find them, and copy them in the folder, et voila! you can use it elsewhere.
Perl: DO NOT USE the cygwin version of perl, unless you have a really good reason to do so. Instead use Active Perl It's damn faster. If it's called from bash then put #!/c:/perl/bin/perl5 -- or where ever you installed it). Some other things to know about active state perl on win32:
Hiding the cmd.exe box when running a script: Instead of putting '.pl' at the end of your scripts, try '.wsf' and have a look at the examples given by ActiveState: <Job ID="MyJobID">
<script language=PerlScript>
#... your code here...
</script
The DNA msg reminds me of this novel, worth a read... enjoy!
Could someone explain me how, from a few ligth years distance, someone could point a laser straight on our receivers? I mean the odds of this being sucessful are very low, no?
Btw, right now there's an "emitter" pointing a laser on a "receiver" in a tv-show here, this last one lost an arm and is dancing around like "AAAAAH!"... we perhaps might not want so much they point a laser at us?
...i nearly always install on new systems: CoreWar: simulation game where a number of warriors try to crash each other while they are running in a virtual computer. Battle for Wesnoth: fantasy turn-based strategy game. BZFlag: multiplayer 3D tank battle game. Crimson Fields: tactical war game in the tradition of Battle Isle. Crossfire: cooperative multiplayer graphical RPG and adventure game. Enigma: inspired by Oxyd on the Atari ST and Rock'n'Roll on the Amiga. FlightGear: Flight simulator. FreeDroid: clone of the classic game "Paradroid" on Commodore 64. Frozen Bubble: puzzle-bobble clone. Globulation 2: Real-Time Strategy. LinCity: city/country simulation game. LBreakout 2: breakout-style arcade game in the manner of Arkanoid. NetHack - Falcon's Eye: mouse-driven interface for NetHack that enhances the visuals, audio and accessibility of the game, yet retains all the original gameplay and game features. netPanzer: online multiplayer tactical warfare game designed for FAST ACTION combat. Pathological: enriched clone of the game "Logical" by Rainbow Arts. Project StarFighter: xy-axis star fighting game. SuperTux: classic 2D jump'n run sidescroller game. XKobo: astpaced multiway scrolling shoot-em-up. XRick: clone of Rick Dangerous. XScorch: Scorched Earth clone.
I frequently endup using reformatting tools for bad code that i get handed to. I mostly use: indent (probably already installed on your machine), AStyle (far better than indent), and perlTidy, there's more xxxTidy programs like html/php, etc have a look on google... there's probably dozen of flavors around.
The plural for "virus" existed long before computers did, and there is absolutely no reason to change it when it refers to a computer virus.
Reason: let's biologists keep their viruses, and let us get our virii. Beside the fact that the net is a multicultural place where each one brings on some of his bits, using such words helps a lot on search engines. Socially inept nerds aren't the only one who use such techniques, one example that come to mind right now is the use of magic and magick. Like it or not.
You can use the word "virii" if you want, but don't be surprised when people think that you're a fucking retard for doing so.
Somehow related to the subject: posting the way you did on slashdot might makes a lot more people think you are a more fucking retard than I am. Which brings me to: majority makes normality. Insane as it may be.
This game is all my childhood, i played it for month, and if there's someone around here that knows the carribean sea better than me, he'll taste my sword for sure. But for/. readers it's perhaps out of sight, i played it on the C=64 last century, then on the amiga, and got it on the PC for a birthday. Anyway, i hope the "remake" will keep the promises of the first game.
If you want more informations about parrot and perl6, you might want to have a look at the mailling lists (parrot|perl), you can also access them via nntp at nntp.perl.org, or subscribe here. You'd perhaps perfer to browse the summaries of Piers Cawley.
For more documentation, consider the parrot's wiki, Dan Sugalski's blog, or even browse the source.
For the languages supported -- some are already functionnal, some not -- here's what i have in the last tarball i took: BASIC, Befunge-93, befunge, bf, cola, conversion, forth, imcc, jako, m4, miniperl, ook, parrot_compiler, perl6, plot, python, regex, ruby, scheme, tcl, urm.
If the files.txt that is linked from another post is real, you might be very right. I checked the.ext there: C(4675), CPP(2257), ASM(148). But only MIB(28), PRF(39).
Some more other interrestings extentions: BAT(123), CMD(65), JAVA(37), SED(29), PL(17), JS(16), M4(5), AWK(3), BAS(2), VBS(1).
1) WSFU is faster (IO/API/...) 2) WSFU is better integrated with win32 architecture (OLE/ODBC/...) 3) WSFU make a lot of things easier than cygwin with windows
BUT, i wouldnt trade cygwin for it, note that i have both installed here. I just isolated what i needed from WSFU and was better than cygwin and added them last in my path. I dont have any preferences, but cygwin is waaay more complete, and you have the +/- the same versions of the application that runs on linux. Same config files work fine, same behaviours (which isnt the case with WSFU), etc.
It's not that fuzzy - i mean you seem to look like you know what all this stuff is about, and no offense is intended here - but, sadly, you underestimate the power of modern cracking and reverse engineering tools you have at your disposal.
Even with compiler optimizations and processor specific instructions AND EVEN different compilers, you can actually find and detect "similar HLL code" (there's a tool called DATING that can do that - contact me for a copy, it's hard to find - and which the name is a pun to the IDA FLIRT abilities). I dont know for different cpu, but i guess it would be ressources hungry, and i dont know of a tool that can catch those for now. Try anyway to have a look at VMWARE binaries - win32/linux - with it, you'd probably be surprised.
blah, dunno what i wanted to say next it's late here... ~<:(
Slashdot Mirror
I was. :-)
I mostly use KMail at home for the same reasons. Though i use fetchmail to retrieve the mails and procmail to pipe them thru ClamAV and SpamAssassin and finally sort them with some scripts of my own.
The fact Kmail use mail dir format, as mutt, let me also check my mail from a remote ssh session.
Some people might want to have a look to AMaVIS or check SWiK about
- emails
- fetchmail
- procmail
- ClamAV
- SpamAssassin
- KMail (nothing really here)
- mutt
Ouch, my head hurts... I should never be left with a keyboard around when I'm drunk... First of all, I'm sorry for the rude reply i did and i ask you to excuse me.
.net studio. It works fine and is faster than if i make it under cygwin.
;-)).
In the original post i was trying to highlight the "do" and "don't" one needs to know when working with cygwin. The hard links for example is one problem peoples frequently stumble on. Most of the things you underlined are, of course, common sense. I just end up running into smart ones that think common sense is something only happening to other peoples... possibly when they're asleep, or dead, or both...
For the fork/thread problem, yes you're right again i never put my nose into cygwin source, and probably shouldnt talk of it that badly. Yet it is something peoples should be aware of when considering cygwin for a production environment. Seeking for alternatives isnt probably a too bad idea. I did such a statement because under cygwin i always end up trying to fix problems with programs using forks. Perhaps i am doing something bad, but perhaps cygwin is having a flaw there. I just dont know. Yet i think i'm quite able to find out if a program is badly written, or if it is the underlying system that makes something wrong... To finish this up, generally an afternoon modifying some lines in the code (and taking some fresh beers with a friend) is worth making it compile with
Sorry again for 14-year-old-stupid-reply i did before (and probably for this one too, cheers
Now, what is really common sense is reading the thing you try to troll on...
Guess who is in the middle of the crowd, and that peoples are looking at with a (little) smile?
Thanks a lot :-) Sorry for being off-topic, but compliments like that would perhaps help the /. crowd to make better posts... erm, in 2-3 years ;)
I already made a post in a thread about SFU that was looking like (disclaimer: i love cygwin):
Now bout your particular problem (prod env, 24x7), I've experienced very few problems running CygWin in such an environment. I use it since at least 5 years (I remember downloading it at 56k, so it's probably more), but there's some things you need to be aware with cygwin:
<Job ID="MyJobID">
<script language=PerlScript>
#
</script
The DNA msg reminds me of this novel, worth a read... enjoy!
Could someone explain me how, from a few ligth years distance, someone could point a laser straight on our receivers? I mean the odds of this being sucessful are very low, no?
Btw, right now there's an "emitter" pointing a laser on a "receiver" in a tv-show here, this last one lost an arm and is dancing around like "AAAAAH!"... we perhaps might not want so much they point a laser at us?
Try with £ to display £...
To find more check here.
you get my vote ;)
btw Project StarFighter might be worth a try, it isnt as fast paced as xkobo, but i like it a lot.
...i nearly always install on new systems:
CoreWar: simulation game where a number of warriors try to crash each other while they are running in a virtual computer.
Battle for Wesnoth: fantasy turn-based strategy game.
BZFlag: multiplayer 3D tank battle game.
Crimson Fields: tactical war game in the tradition of Battle Isle.
Crossfire: cooperative multiplayer graphical RPG and adventure game.
Enigma: inspired by Oxyd on the Atari ST and Rock'n'Roll on the Amiga.
FlightGear: Flight simulator.
FreeDroid: clone of the classic game "Paradroid" on Commodore 64.
Frozen Bubble: puzzle-bobble clone.
Globulation 2: Real-Time Strategy.
LinCity: city/country simulation game.
LBreakout 2: breakout-style arcade game in the manner of Arkanoid.
NetHack - Falcon's Eye: mouse-driven interface for NetHack that enhances the visuals, audio and accessibility of the game, yet retains all the original gameplay and game features.
netPanzer: online multiplayer tactical warfare game designed for FAST ACTION combat.
Pathological: enriched clone of the game "Logical" by Rainbow Arts.
Project StarFighter: xy-axis star fighting game.
SuperTux: classic 2D jump'n run sidescroller game.
XKobo: astpaced multiway scrolling shoot-em-up.
XRick: clone of Rick Dangerous.
XScorch: Scorched Earth clone.
Have fun!
I frequently endup using reformatting tools for bad code that i get handed to. I mostly use: indent (probably already installed on your machine), AStyle (far better than indent), and perlTidy, there's more xxxTidy programs like html/php, etc have a look on google... there's probably dozen of flavors around.
You're very right, it works like that. I learned it the +/- $30,000 lesson here.
This game is all my childhood, i played it for month, and if there's someone around here that knows the carribean sea better than me, he'll taste my sword for sure. But for /. readers it's perhaps out of sight, i played it on the C=64 last century, then on the amiga, and got it on the PC for a birthday. Anyway, i hope the "remake" will keep the promises of the first game.
Other games i like: "Soul reaver", "Black & White", "Trick Style", Tibia, Nomad Soul, and of course all the Lucas Art Series..
..."We are not alone! This is so weird!".
This Linux Mini-HOWTO might be of interrested to some /.ers, it describes how to share your Linux swap partition with Windows.
I dont think there's one but you might wanna look at this recent thread.
If you want more informations about parrot and perl6, you might want to have a look at the mailling lists (parrot|perl), you can also access them via nntp at nntp.perl.org, or subscribe here. You'd perhaps perfer to browse the summaries of Piers Cawley.
For more documentation, consider the parrot's wiki, Dan Sugalski's blog, or even browse the source.
For the languages supported -- some are already functionnal, some not -- here's what i have in the last tarball i took: BASIC, Befunge-93, befunge, bf, cola, conversion, forth, imcc, jako, m4, miniperl, ook, parrot_compiler, perl6, plot, python, regex, ruby, scheme, tcl, urm.
Who said parrot didn't had fun?
If the files.txt that is linked from another post is real, you might be very right. I checked the .ext there: C(4675), CPP(2257), ASM(148). But only MIB(28), PRF(39).
Some more other interrestings extentions: BAT(123), CMD(65), JAVA(37), SED(29), PL(17), JS(16), M4(5), AWK(3), BAS(2), VBS(1).
Documentations? EML(2213), TXT(382), HTM(212), HLP(23), RTF(9), PPT(3), PDF(1).
Media: ICO(1304), BMP(803), GIF(165), AVI(141), ANI(34), MID(3), JPG(2).
TOP11: H(5611), NoExt/Dirs?(4708), C(4675), CPP(2257), EML(2213), CXX(1466), ICO(1304), HXX(972), BMP(803), RC(702).
I wonder in what is this "super-new" thing is different from the "good'ol'" Kiss files? From the screenshots it looks like kiss format wont die...
1) WSFU is faster (IO/API/...)
2) WSFU is better integrated with win32 architecture (OLE/ODBC/...)
3) WSFU make a lot of things easier than cygwin with windows
BUT, i wouldnt trade cygwin for it, note that i have both installed here. I just isolated what i needed from WSFU and was better than cygwin and added them last in my path. I dont have any preferences, but cygwin is waaay more complete, and you have the +/- the same versions of the application that runs on linux. Same config files work fine, same behaviours (which isnt the case with WSFU), etc.
For me, WSFU is just a little + to cygwin.
It's not that fuzzy - i mean you seem to look like you know what all this stuff is about, and no offense is intended here - but, sadly, you underestimate the power of modern cracking and reverse engineering tools you have at your disposal.
Even with compiler optimizations and processor specific instructions AND EVEN different compilers, you can actually find and detect "similar HLL code" (there's a tool called DATING that can do that - contact me for a copy, it's hard to find - and which the name is a pun to the IDA FLIRT abilities). I dont know for different cpu, but i guess it would be ressources hungry, and i dont know of a tool that can catch those for now. Try anyway to have a look at VMWARE binaries - win32/linux - with it, you'd probably be surprised.
blah, dunno what i wanted to say next it's late here... ~<:(