Sep 1999
Oct 1999
Nov 1999
Dec 1999
Jan 2000
Feb 2000
Mar 2000
Apr 2000
May 2000
Jun 2000
Jul 2000
Aug 2000
Sep 2000
Oct 2000
Nov 2000
Dec 2000
Jan 2001
Feb 2001
Mar 2001
Apr 2001
May 2001
Jun 2001
Jul 2001
Aug 2001
Sep 2001
Oct 2001
Nov 2001
Dec 2001
Jan 2002
Feb 2002
Mar 2002
Apr 2002
May 2002
Jun 2002
Jul 2002
Aug 2002
Sep 2002
Oct 2002
Nov 2002
Dec 2002
Jan 2003
Feb 2003
Mar 2003
Apr 2003
May 2003
Jun 2003
Jul 2003
Aug 2003
Sep 2003
Oct 2003
Nov 2003
Dec 2003
Jan 2004
Feb 2004
Mar 2004
Apr 2004
May 2004
Jun 2004
Jul 2004
Aug 2004
Sep 2004
Oct 2004
Nov 2004
Dec 2004
Jan 2005
Feb 2005
Mar 2005
Apr 2005
May 2005
Jun 2005
Jul 2005
Aug 2005
Sep 2005
Oct 2005
Nov 2005
Dec 2005
Jan 2006
Feb 2006
Mar 2006
Apr 2006
May 2006
Jun 2006
Jul 2006
Aug 2006
Sep 2006
Oct 2006
Nov 2006
Dec 2006
Jan 2007
Feb 2007
Mar 2007
Apr 2007
May 2007
Jun 2007
Jul 2007
Aug 2007
Sep 2007
Oct 2007
Nov 2007
Dec 2007
Jan 2008
Feb 2008
Mar 2008
Apr 2008
May 2008
Jun 2008
Jul 2008
Aug 2008
Sep 2008
Oct 2008
Nov 2008
Dec 2008
Jan 2009
Feb 2009
Mar 2009
Apr 2009
May 2009
Jun 2009
Jul 2009
Aug 2009
Sep 2009
Oct 2009
Nov 2009
Dec 2009
Jan 2010
Aug 2010
Sep 2010
Oct 2010
Nov 2010
Dec 2010
Feb 2011
Mar 2011
Apr 2011
May 2011
Sep 2011
Oct 2011
Nov 2011
Feb 2012
Mar 2012
May 2012
Apr 2023
May 2023
Jun 2023
Jul 2023
Sep 2023
Oct 2023

Hey, Fargoans! Do you miss Thunder Radio, the student-run, classically 'college radio' programming that was removed in favor of North Dakota Public Radio?

Thunder Radio is back as KNDS, 105.9! You'll get to hear rare music, cool music, interesting discussions, uninteresting college student banter, miscued tunes, and pretty much everything that makes college radio so wonderful. Now, because it's NDSU, don't expect anything too over-the-top, but what I've heard so far is pretty good. We'll see how long it needn't improve (thought it should, as the new broadcasters learn the ropes better), but as long as it's something fresh, young, uncommon, and unlike anything else on the radio -- it should be fine.

I'm gonna get geeky here:

For the uninformed, there's some software out there to create Virtual Network Computing sessions. We've all seen PCAnywhere, right? VNC is like a lite version of PCAnywhere: You can control the mouse and keyboard of another computer, over a network connection. On one hand, there's a "that's it?" reaction, but it's still an enormously powerful function.

Here's why I'm using it right now. I've got a handheld scanner, small enough to do paperback-sized pages without having to squish the book on a flatbed scanner. Problem is, my handheld uses an ISA interface card. My computer? It doesn't have this old standard.

So, I throw together older computer parts, and create a P133, 32MB, Win98se computer with the handscanner installed.

Now, it's one thing to have to go back and forth from one computer to another, but with VNC I don't have to.

The 'scanner computer' has no mouse, keyboard, or monitor -- all that is sent to a little window on my main computer. The scanner's still attached, and I use it like normal. However, when my mouse is in the VNC window, my regular computer takes over for the scanner's computer. I can open the graphics software, tell it to scan, and do everything as though I were sitting in front of it running everything directly. Once it's scanned, I hit 'save' -- saving it to a networked drive both computers can see. Open the file on my main computer, and viola! Start up the OCR software. While that's running, I can be scanning something else.

Now, geeksters, get this: my main computer is also running an XWindows server. In another window is a system load graph for my webserver, located several miles away in a secure location. It churns away, giving a realtime display of how much webtraffic you're giving me.

If I don't want to run Photoshop locally, I could start up GIMP on my home server and do image editing there.

This gets to a point that the web can't quite achieve. The internet transfers static information all at once, making distant documents appear as local ones. "Distance" online really doesn't have anything to do with reality. It's something we've been trained on. You 'go' to a file, but there's no real departure experienced. A local file and a distant file are indistinguishable from a user standpoint. We laugh at the people who say that they've got eBay on their computer, but it's only because they haven't been trained to understand what's non-local.

The kind of software I'm running is a bit beyond this. The location of the running program is irrelevant -- it could be on this computer, on another computer, inside this house, somewhere on the internet. The concept of 'this computer' blurs, because the keyboard/mouse/monitor system isn't a closed one anymore. As I run my mouse from one end of my screen to the other, it goes from a white pointer of this local system to the gold custom mouse of the VNC computer to the standard "Big X" of the XWindows server.

The computer is now visualized as a set of independent parts. The keyboard enters data into any place the cursor blinks, local or remote. The mouse can only work in one window at a time, but it seamlessly moves from one to the other without worrying about which computer is which. The monitor recognizes all graphical data as a separate window; it doesn't care where the data comes from, as long as it understands the size, shape, and color of what's being displayed.

I recently installed PCAnywhere for a client, and showed her how she can control the computer at work from her laptop, from any location with a network connection. She was impressed -- now she could fill and print invoices from anywhere! I almost agreed, before I realized...the printer it'll print to is the local one, attached to the remotely-controlled system itself. Printers can be shared; with a little tweaking (and a VPN), it would certainly be possible to remotely control the computer, and instruct it to print to a network device attached to the controlling computer. The Network Printer is probably the first experience people have had with a shared network resource. Most office employees have become quite adept at being able to send a file to this printer or that one, depending on if they want color, speed, letterhead, etc. Networked filesystems have taught people that if they save a file to the right place, anyone else can open it like it were saved on their own computers. VNC and XWindows Allow a program to run anywhere and be displayed anywhere, regardless of where the user is sitting. It doesn't eliminate the need for a computer, but it doesn't limit a user to the resources of one computer alone. It's possible that, in the future, that icon on your desktop may or may not be a local program. Just as you can have many browser windows open, each containing data from a different place, your computer could have many windows open, each holding the display for a different place.

I can tell I'm tired, because I didn't make a real point. However, this is too cool of a concept for me to delete this post...maybe I'll think on it a bit and write more later!)

Two young men are occupying the counter at the gas station. Clean, bright white dress shirts, black slacks, black ties. One wears a bicycle helmet: these are the bike-mounted Mormons I've seen around town.

The cashier looks uncomfortable. The LDS kids say nothing. I wait patiently.

After a long pause, one asks, "How much are these lighters?"

"$1.65, no, $1.35."

Another long pause. The missionary with the skull-protection notices my presence and apologizes for being in the way.

They move aside, and I order cigarettes.

"Do you know where we could find a Zippo?" They ask.

I ignore them, unsure of who they were querying; if they asked again, I planned to tell them I don't smoke.

"We don't carry them here," they cashier replied.

"Do you think Sunmart has them?"

"Maybe," was enough of an affirmative for the mormon-thumpers. They headed for the door.

The cashier tore off my reciept and offered it for my signature.

"I wonder why they need a lighter like that?" she asked.

"Maybe they just need to start a few fires," I deadpanned.

Today's mantra:

make clean
make menuconfig
make dep
make bzImage
make modules
make modules_install

*sigh* Trying to add capabilities to an in-service server is a pain in the ass. So, this is the explanation for why the server is up-and-down today. It takes approximately 2:30 to reboot, so just be patient. Thank you for your consideration.

blog advertising is good for you
Looking For "Wookies"?