Recently in Tech Category

DNS for girls.

| | Comments (1) | TrackBacks (0)
Igor was having problems understanding what a root nameserver did, so I gave him this explanation. I am proud of this.

freebsdgirl: think of them like a directory service at the mall.
freebsdgirl: you want to know if sephora has chanel no 5 perfume, so you go to the mall, look at the directory service to find out where sephora is, and then you walk to sephora and ask them directly if they have chanel no 5.

I'm going to be moving the site over to a new server soon. Plans are being made for blog.freebsd.org, as well. More about that (and the company that's going to be hosting me and blog.freebsd.org) in a bit. It's pager week for me at IronPort, so I'm tired and busy.

The ipmitool that comes by default with OSX sucks. I needed to use ipmitool for work, and I couldn't find any OSX ipmitool packages anywhere, so I rolled my own. If anyone else is interested, I have a copy of it here. gunzip it, copy it to /usr/local/bin, and move your /usr/bin/ipmitool elsewhere as /usr/bin is before /usr/local/bin in $PATH by default. Enjoy.

I was trying to explain why people should twitter to a group of geeks that don't live here, and I came to a sickening conclusion. I am turning into one of the Silicon Valley Borg. In light of this realization, here is my guide to becoming one of us (or rather, warning signs depending on how you see it).

  1. Start reading Valleywag. It's a casual affair at first. You check it once every week or two. Maybe you only search for references to your employer. After a while, you add it to your RSS reader.
  2. You start recognizing names. Names of people that no one cares about unless they also live in the valley. You may not have had a clue who Robert Scoble or iJustine was before, but now you're following them on...
  3. Twitter. You can't adequately explain to anyone that doesn't use Twitter already why it's a good idea, but you can't help but create your own account. You start out only updating a few times from your web browser, but then you discover twhirl. Now you've got instant updates of Scoble, your friends, and...
  4. Gizmodo, where you're scouring anything related to cell phones so you can figure out what's going to set you aside from all of the local iPhone wielding weenies. The iPhone is so trendy, it's untrendy. After all, you're watching Gizmodo and Valleywag for rumors as to when the 3G iPhone is going to be released. 60 days is what they are saying now. You're going to laugh at all the people with their 2G iPhones. Clearly, you will be superior as 2G is not nearly enough G's. You need those G's to send... uh... lots of text messages to update your twitter status! That is, until you start feeling dissatisfied with Twitter. Tweeting just isn't enough for you, anymore, so you create an account on...
  5. Tumblr. You get confused about what you're supposed to be posting where, especially if you already have a blog entirely separate from all of this, so you try to post different content to each site until you run out of things to talk about entirely. In an attempt to drum up content that you think would be relevant to your valley peers, you sit on BART thinking about Mahalo (which, lets face it, no one really cares about), Yahoo!/Microsoft mergers, expensive escorts, and...
  6. Facebook. As soon as you get home from your job which is probably at Google, since they seem to employ a good portion of the tech force here (let's hope you're not at Yahoo!), you start browsing jobs at Facebook, because you know it's the next big thing. You don't know how they are making money, but most people said the same of Google, too. How many people are driving around in expensive cars here due to getting on on the GOOG stock early on? Sadly, Google stock is starting to tank, so it's time to drop it like it's hot.
  7. Update your twitter status, check to see if you have any new friends on Facebook, then go to Valleywag's happy hour. Pretend to recognize everyone there. Eventually, you will. That's when you should really start feeling scared. After enough time, you'll have forgotten that there is in fact a world outside of Silicon Valley. Don't feel bad - from what I remember, you won't be missing all that much.

SCO and pants.

| | Comments (0) | TrackBacks (0)

If you haven't heard the news yet, SCO got fucked. Heh. Point and laugh. I nearly fell over laughing when I read this:

According to Judge Kimball's ruling, Microsoft paid SCO approximately $16 million for license rights and Sun paid approximately $10 million. SCO neglected to turn over the licensing fees to Novell, which "gave SCO its first profitable year in history," Kimball notes.

Props to Kimball.

Today, I'm working on capacity planning. Capacity planning is by far one of my least favorite aspects of my jobs. It's an exercise in futility, in my opinion. It reminds me of shopping for pants. I find the perfect cute pair, and then I'm reminded of how much soda i drink, leading to the question "Will these pants fit me a year from now?" Capacity planning for large networks like I'm responsible for now is the exact same way. Will this number of servers still properly support my butt after so many late night coding sessions? Hmm.

My MacBook Pro desperately needs to get wiped. Unfortunately, the motorcycle accident did do some damage, as I can't get the DVD drive to work. I could just hook up an external USB CDROM drive that I've got, but I've had limited success with it when installing FreeBSD on a desktop. I don't really want it to crap out halfway through the installation and leave me without a working laptop.

Do any of y'all (y'all referring to local bay area friends, of course) run OSX Server? I could install over the network if I had access to a computer running OSX Server. That would be fantastic.

You know how to find me.

This is highly unlike anything I usually write, and it's going to sound preachy, even cheesy, but bear with me.

Today, I was talking to a few friends in a NetBSD chat forum. A few of the guys were discussing their respective careers, until I became a bit indignant when one wrote "I've learned that using my voice is the path to destruction... being a yes-man is the way to go."

This is not what IT is all about. You may think I'm wrong; maybe I'm just an idealist. I still think that IT is about breaking all the rules. If you're just another yes-man, you'll never do anything innovative. You'll never get your own Wikipedia entry. I wonder if you'll ever even really be satisfied with your own life.

There's a fair number of people in IT that did what they were told all of their lives. They got straight A's in high school, went to Ivy league colleges, got their CS degrees, and continued on to get good, well-paying jobs in corporate America. A lot of these are yes-men. However, when it comes to innovation, these people fall into the minority.

So many of us have never fit into that mold. When we were younger, we didn't play sports. We didn't have many friends. We were told that we had to get good grades in school so we could go on to a good college and get a good career. All hail, society. We ignored this. We spent most of our time on our computers. Our parents didn't understand what we were working towards. We probably didn't really have much a plan either, but we were driven to do more - to learn more than we felt our schools could teach us. We were truly a unique generation. We broke the mold and still succeeded. You could get the good job, have a career more lucrative than anyone ever could have dreamed for you, but break all the rules doing it.

Maybe you got kicked out of high school, or perhaps you just got bored and dropped out. You were probably in Honors/AP classes, but you were flunking out of all of them because you spent all of your time programming or messing around on your computer instead of doing your homework. College? Doubtful. Maybe you got your GED. Maybe you even tried a community college for a while, but our generation was lucky enough to be able to hop onto the dot com bubble before it burst. You didn't need formal education to get a job, you just needed the knowledge to do the job. High school didn't prepare you for this, but all those hours you spent late at night in the dark on your computer certainly did. You probably made more at your first job than your parents currently do combined. You won.

So what's up with this "yes-man" ideal? What happened to breaking the rules? Let's face it: providing that you have the skill, they need you more than you need them. Why become a yes-man when you became what you are now by telling so many people no when you were younger? Why are you so scared?

I mean, look at corporate dress code. The majority of us go to work in t-shirts and jeans. There's a few companies that require business casual in their IT department, but these are the exception to the rule. Think about your parents and how their work environment was when you were growing up. People working skilled jobs such as these had to wear collared shirts, sometimes even suits. You could not get paid as much as we do without making a concession when it came to your wardrobe. We changed this. Our generation changed so many expectations when it came to the work environment, this being one of the most minor examples. It's rare to find an IT company that doesn't have a game room, or at least a foosball table. Do you think people really had that kind of luxury 20 years ago? 15 years ago? Do you think if we had just rolled over and said yes that we would have these luxuries?

We have more responsibilities now than we did when we were younger. We have so much more to lose. We have families. We have a 401(k). Don't lose yourself, though. Remember how you got to where you are. Be proud of breaking the rules. Becoming a yes-man isn't about growing up. It's about giving up.

static int getWindowColor( Display *display, XColor *color, int x, int y )
{
   Window target_window;
   XImage *ximage;
   int rev;

   XGetInputFocus( display, &target_window, &rev );

   if (target_window == (Window) NULL) {
      printf( "target window is null\n" );
      return(0);
   }

   ximage = XGetImage( display, target_window, x, y, 1, 1, AllPlanes, ZPixmap);
   if ( ximage == (XImage *) NULL ) {
      printf( "ximage is null\n" );
      return(0);
   }

   color->pixel = XGetPixel( ximage, 0, 0 );
   XDestroyImage( ximage );

   return(1);
}

The point behind that function is (more or less) to get information about a pixel at a given x,y coordinates relative to the window containing the current focus.

This is not what I want.

I want to select the window on top, not the window that has focus. Is there a way to do this? I don't want to give that window focus first.

This is prior to bedazzling it.

[ sektie@daemonesque ] [ ~ ]
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=4.238 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=9.014 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=3.888 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.290 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=3.029 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=4.713 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=42.647 ms (DUP!)
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=4.613 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=6.300 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=8.999 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=21.546 ms (DUP!)
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=1.885 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=15.772 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=40.732 ms (DUP!)
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=9.952 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=12.267 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=5.100 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=40.102 ms (DUP!)
64 bytes from 192.168.1.1: icmp_seq=37 ttl=64 time=5.622 ms
64 bytes from 192.168.1.1: icmp_seq=38 ttl=64 time=3.117 ms
64 bytes from 192.168.1.1: icmp_seq=41 ttl=64 time=2.477 ms
64 bytes from 192.168.1.1: icmp_seq=43 ttl=64 time=9.528 ms
64 bytes from 192.168.1.1: icmp_seq=45 ttl=64 time=4.120 ms
64 bytes from 192.168.1.1: icmp_seq=46 ttl=64 time=16.481 ms
^C
--- 192.168.1.1 ping statistics ---
49 packets transmitted, 20 packets received, +4 duplicates, 59% packet loss
round-trip min/avg/max/stddev = 1.290/11.560/42.647/12.226 ms
[ sektie@daemonesque ] [ ~ ]
$

New Cell Phone

| | Comments (0) | TrackBacks (0)

I picked up a Nokia E62 today, after being surprised by the small deposit required by Cingular. I had bad credit a few years ago, so when I tried to get a Cingular phone back then, they asked me for an $800 deposit. It was a pleasant surprise not having to front all that money.

My first impressions of the phone are positive. It's a little bulky - definitely not a "girly" phone like the Moto RAZR v3 that I used to have. Symbian OS has gone through a lot of changes since the last time I used it (Nokia 3650). It's a little difficult to find my way around. I actually had to pull out the manual for a few things. It has VPN & SIP support, both of which are hella cool to have although I doubt I'll ever use them. It lacks a camera, but I never really used the camera on my old phone anyways.

I downloaded PuTTY and Google Maps after the data service was finally enabled. Cingular takes a while to get the ball rolling. My old number still hasn't rolled over, although I can place outgoing calls. I'm not too happy with Cingular's plans, but well, I downloaded PuTTY quickly enough to make me giggle.

iSync doesn't currently support the E62, but I've found a few plugins for the E61 online that I'm trying to get working. I'll post with notes if I have any success doing so.