subversus

Agents of the Revolution
  • Content count

    124
  • Joined

  • Last visited

Everything posted by subversus

  1. This article is shitty, technically shortsighted, and in many cases incorrect. In the future _please_ be sure you have a real understanding of the subject matter when you post, unless you are asking a question.
  2. Operating systems are only a matter of preference. Windows and Linux both require a lot of tweaking to get to work in any reasonable way, but Linux is probably the most obviously inferior system. Mac OS, which has it's own limitations, provides the greatest amount of convenience and generally better tools than those available in Linux (but not always better than Windows), but is a lot more expensive. It shouldn't matter which system you work on, so long as your work gets done.
  3. Compilers create generalized code. Good compilers generate pretty good generalized code, but it's still generalized code. Any time you need something more specific than that, you'll want to use assembler code. It's also important to understand how computers work on that level. Too many people these days are treating computers like too much of a black box, without thought to CPU cycles or anything. Algorithms will make more sense when you know what's happening underneath your compiler (or interpreter/vm).
  4. You mean.. AWESOME?? Also, it's a Kelet. PS: Yeah, it's against apple's terms of service to install OS X on a non apple computer. Most people don't seem to care too much, though, and I doubt Apple'd send their goons after you unless you used it for commercial purposes and they found out. Still, you should just get a mac. Plus, every time you do, some dude calls you up and goes "Dude... you're gettin' a MAC!!"
  5. cough.....fanboy...cough UP YOUR NOSE WITH A RUBBER HOSE
  6. I frequently do this the other way around: run windows as a guest from my mac. Works like a charm. I suggest getting a mac, because then you have all possible options at your fingertips and it's _easy_ to do everything. You've got VM support for everything, and bootcamp for dual booting to whatever. It's a balanced decision!
  7. More or less aware than......... what? Than they were 10 years ago? Than they were 5 years ago? Does it really matter, and does anyone really care? I think the companies that are storing sensitive information are trying to be aware in most cases. That doesn't really mean anything though. There are some companies which provide a great deal of quite secure software that most people don't see. And that's part of my point: unless it's insecure (or really obvious/popular), you silly "hackers" aren't going to pay attention to it. Our newer generations of programmers need to evolve their skills and be sure to remain aware of security issues that fundamentally pervade software. But we need to focus on creating better, more solid software in every aspect. The general state of software usability and interoperability is pretty miserable. So, stop being so damn critical of security until you're actually worrying about it in your own software. NB: This posting requested by OP in #binrev. I never post here. wtf.
  8. This is an interesting thread. Kit is certainly a good thing to discuss, and I find myself constantly changing and perfecting my own kit. I used to carry a more extensive kit, including a flashlight and USB drives, multi-tool, knife, various things, but I've found that subtlety is usually a better option. As of now, I usually keep with me at all times: -pocket knife (a thin but very nice benchmade) -notebook (moleskine) -fountain pen (Pilot Prera or Waterman Phileas for EDC) -lighter (zippos are good - altho the torch lighters for cigars are good too) -some chewing gum And in addition to this I obviously always keep with me a few quarters, my wallet, cell phone, keys, and watch. None of this stuff takes up much space. A lot of people have mentioned flash drives. These are nice, but I find it easier to keep the tools I need on websites that I have through shell on friends' servers. I can always download putty and ssh to my shell anywhere. People also have mentioned flashlights. These are extremely useful, but can be quite bulky. I actually like the LED lights that you can put on keychains. I also found that you can get these keys that have a colored LED built into the base, so you can combine a key with a working LED light. Nice if you want to save space. I have a few of these in different colors. Sometimes I'll carry a pack of cigarettes as well. I don't smoke habitually, but one can stand just about anywhere smoking a cigarette and look totally normal. They can also be good ice breakers. Cheers,
  9. It's illegal to install OS X on non-apple hardware. It's in their license agreement. If you have a PC, you should probably just stick with linux or windows or whatever. If you want a mac, then get a mac. You really need an apple computer for the full experience anyway.
  10. Why don't you paste for us exactly the error you get when you attempt to use `make`
  11. Make is actually a program. You need to have it installed to run it. You also will need it to be located in your $PATH. If you're on SuSE, you should be able to get it through YAST or whatever it is they use as a package manager. As far as linux goes... Linux is Linux. Of course, the various distributions have differences, but regardless of which Linux you choose, you are going to encounter the same sorts of problems, though those specific problems may not be the same from distro to distro. If you're having a problem with a Make in suse, you're going to have plenty of other ones regardless of which distro you choose.
  12. You know, practicing "hacking" into shit isn't really going to do you much good if you don't know how most of that software is put together in the first place. A lot of the simple stuff, like port scanning, etc. is really just rudimentary and you follow a basic formula to find vulnerabilities. If you want to try to learn some perhaps ultimately more interesting stuff, why don't you just dick around with interesting settings for a while. Get a unix on one of your computers and start dicking around with it. Break stuff; break lots of stuff, and then try to fix it. You'll learn the most by fixing broken stuff. Once you start to pick up a method to the madness, you'll learn to think more creatively.
  13. You should try writing a really good letter to the superintendent about it or something, and get it published in your school or local town newspaper. I would be happy to help you out with this.
  14. I plan on doing web hacking. Learn HTML
  15. .. but it feels so right. Only if you're not reading it!
  16. LOL Also: Don't hate yourself so much; use C and asm less. srsly.
  17. WHY is everyone voting PERL?? This is so wrong! sooooo sooooo wrong.
  18. I would like deadc0de to explain to me why large scale projects should use a language like C.
  19. Everyone knows that, BSDfan. But frequently, if you're a TA for a class, you're required to grade student programs on school computers, which almost invariably run Windows on the desktops. Zigman, that's pretty cool. Next time I'm forced to use Windows, I'll probably be putting that to good use.
  20. Didn't read the code, but you should see if you can find some getTime() methods in visual basic. I don't know VB very well, so I can't help you off the top of my head. Good job though. You should try posting this in the programming forum; you might get some more VB-knowledgeable eyes to take a look. Bien a toi
  21. Linux is not better than Windows. If you use Windows, and are annoyed at the way the operating system functions, then installing Linux will not solve your problems. It will change them. Linux does not have the same problems that Windows has. It handles certain things far better than Windows. That being said, it has its own set of very different, but no less annoying, problems. Even though I am far more comfortable in a unix environment than I am in a non-unix environment, I still prefer to use Windows over Linux for a desktop workstation system. My personal main computer is an apple. My servers, on which I do a great amount of computing, run BSDs. I am not going to dicuss the differences, because that is beyond the scope of this topic. However, I do encourage you to stick with Windows if that is what you are most used to.
  22. Mac OS X and FreeBSD. Works much better than Linux. BSDs have a stronger base system and overall just make more sense. I suggest looking into them if you have any significant amount of unix-environment experience. www.freebsd.org has almost all of the information you'll need. NB: if you have a laptop, you should check to see if your hardware is supported. While usually pretty good, the BSDs tend to be a tad bit behind Linux as far as hardware support is concerned.
  23. For a first look at Linux, go with kubuntu (gnome sucks), but make sure to follow Vector's advice and look into the "old school" methods of operation, if you really care. I will offer my opinion separately and also a slightly different perspective on Vector's attitude toward ubuntu. I think Linux sucks. I use FreeBSD. But aside from that, I think there's something to be said for Ubuntu appealing to people that are more experienced Linux users. I've been using Linux and other unix systems for six years. I have no interest in manually mounting my drives. I know how to do all that, but after doing it for years, it's a pain in the ass. I started off on Slackware, back when Linux really sucked (way more than it does now). It was cool, though. I figured out how to do all sorts of shit pretty quickly. I imagine most people could. Operating a Linux system, even in an old-school fashion, is not rocket science. Therefore, it can be argued that such tasks are fundamentally trivial. Unless you plan on doing software development or seek a much deeper knowledge of these systems, there is no reason to deal with learning operation methods that, unless you deal with this stuff professionally or simply pine for CLI, are fast becoming archaic. I have one computer that indeed can boot to a partition upon which Kubuntu is installed. When I need to dick around or test something in Linux, I'll take the easy way out and save myself the time. Screw the "hard core" distros, I say!
  24. you need to run it from an xterm, not the standard terminal. two very different things.