Last week, I got “The Knack.” It seems to bite any computer guy that comes into contact with Digital Equipment Corporation (DEC) hardware. It all started when a fellow programmer friend of mine sent me a link to a DEC Easy WebServer. This is a relabeled DEC Alpha Multia that shipped with Windows NT 4.0 Server. It included some sort of Netscape software for setting up a webserver easily. Well, I figured I would go ahead and add it to my watch list, since it was only $20 + shipping. I continued browsing and around and found a DEC VAXstation 3100 for $18 + shipping. I have been wanting a VAX for a while, so I bought it. 2 days later, I bought the DEC Easy WebServer.

So in total, I spent over $100 in a week on computer hardware that is older than me.(almost as old as me in the Multia’s case) The VAXstation came and it ended up missing the whole SCSI controller board, so I’m still looking for one of those. The Multia came today and works great, but it seems to operate in “Space heater emulation mode” all the time, I’d hate to see it under a full CPU load.

I tried installing OpenBSD/Alpha on the Multia tonight, with little luck. The installer boots and then says it can find no drives, but the hardware compatibility list clearly says the Multia is supported. So, I tried to find Debian net boot floppy images and failed. I’m currently installing FreeBSD/Alpha as I’m writing this, hopefully it works better.

Here are a few pictures of my new machines, more pictures of the Multia can be found here; more pictures of the VAXstation can be found here.

School has been crazy lately. I’ve been loaded down with homework most of the time, and on top of that I’ve been drafted by a few of the teachers at school to participate in the FBLA competitions. I’ll be competing in the single person test on computer networking. The test is a 100 question test given at a local university. I’m competing in the area my school does really bad in, so I hope I can change the tradition…

As I said above, school has been crazy lately. This has had it’s negative effects on Threadbound. When I do have time to code, I’m working on my client’s website, which I got sometime after my last post, or I’m doing coding for thunder-it.com. Today, I’ve been hit with a new block of inspiration and ideas for threadbound, so hopefully I can make some time to work on it. The stuff I came up with today is definitely new for the area I plan to implement it in.

For those of you still not quite sure about this whole Web 2.0 thing, check out the video below. It’s the best one I’ve ever seen that describes how I feel about it.

The Kenwood Apple Store was true to their word, they called me the day they came in. I ended up getting to the store around 6:30-7pm and it was packed. These things must be selling like hotcakes because I know they sold 3 of them while we were waiting on the cashier to see if they had any 2gb ram sticks in stock — which they didn’t. So I’m still 1gb of ram short until my reserved stick comes in. They do have a nice deal going right now though. You can get an HP Photosmart C3180 printer for free with your MacBook if you are buying it on a college discount. You have to pay upfront, but you get a rebate for the full price of the printer, similar to how they were running the iPod deals.

So far my experience of moving from Linux to OSX has been pretty grand, as I hinted at above. The built in wireless coupled with my new WRT45G, that I hadn’t tested the wireless on, seem to be working much better than my old setup. It’s so nice having wireless again, no cat5 cable to get tangled up in my mouse. Application-wise, I have already found a replacement for everything I used on Linux. I knew all of these before I even owned a Mac though, since I talk to/code with a few people that own a mac.

Heck, in the three days I’ve had this thing, I’ve already spent $50 in software. I bought textmate since it appears to be the best coding text editor on the planet for the mac and web 2.0 crew. I’m definitely liking it so far, but I’m on the hunt for PHP plugins now. They are a bit saturated with Ruby plugins. I still need to get a legal copy of Photoshop CS2 for this box though. If only it was cheaper…

I’ve also had the joy of being able to run a lot of my favorite Linux applications on this thing. Fink is quite a nice system. I already have X11 running at startup, without that stupid xterm. I’ve modified my shell settings so everything I need to start X apps from Terminal.app is there and ready to go. I suggest all of you go out and install Xdroplets. Combined with this custom X11 setup and Xdroplets, I have a pretty standard application interface for running my old applications, such as XMMS or Konqueror for testing.

To give you some idea of how fast this laptop is, I have two benchmarks for you. While I was writing this post, I started a compile of Apache 2.0.59 to start setting up my development environment for ThreadBound. Here are the command that I ran:

$ ./configure
$ export MAKEOPTS=”-j6″
$ time make

What are the results? Astounding, considering this is a 10-20 minute compile on my old Athlon64 3200+ laptop…

real 1m37.240s
user 0m53.671s
sys 0m37.242s

The other benchmark is from when I installed Windows XP on my friend’s MacBook Pro, which is identical to the one I bought. After installing Counter-Strike: Source, we ran the video stress test. These machines averaged 114 FPS on it. This test set all of the settings on high, so we tried it. We were getting about 60-90 FPS at 1680×1050 during games. This just goes to show you the performance of this machine. Considering that people don’t know that the x1600 graphics cards they ship with are underclocked by around 45% below what ATI ships them as, due to heat. So I’m going to have to overclock them a bit and see how it does.

Here is a nice picture of my MacBook Pro:

Macbook Pro Core 2 Duo Opening Hosted on Zooomr

More pictures of it can be found here.

In other news, I would like to leak a bit of news on one of my new projects that I am co-developing with a network operator for theWyldRyde.org IRC network, DamnSmallBSD. It is a take off of the very first linux distribution I ever used, Damn Small Linux. Our goals are similar, but we are based on a completely different operating system, FreeBSD. We also have some cool ideas to keep it modular for people looking to remaster it. Keep your eyes open, the cd is bootable, we just haven’t done much work on the userland yet.

Over the past day, I also broke back into some PHP. ThreadBound officially moved a step closer to it’s main goal. Here is a little hint of a very early page:

ThreadBound – preview Hosted on Zooomr

I have also been contacted to do some more work for ThunderIT.com, so I’m very happy about that. The project I’ll be working on is very cool. Hopefully some of the cash I get from this job will help me get a new laptop.

By pressing Alt + SysReq + any of the keys below, you can perform any of the functions listed:

• r – Turns off keyboard raw mode and sets it to XLATE.cc
• k – Secure Access Key (SAK) Kills all programs on the current virtual console
• b – Will immediately reboot the system without syncing or unmounting your disks
• c – Will perform a kexec reboot in order to take a crashdump.
• o – Will shut your system off (if configured and supported)
• s – Will attempt to sync all mounted filesystems
• u – Will attempt to remount all mounted filesystems read-only
• p – Will dump the current registers and flags to your console
• t – Will dump a list of current tasks and their information to your console
• m – Will dump current memory info to your console
• v – Dumps Voyager SMP processor info to your console
• 0-9 – Sets the console log level, controlling which kernel messages will be printed to your console. (’0′, for example would make it so that only emergency messages like PANICs or OOPSes would make it to your console.)
• f – Will call oom_kill to kill a memory hog process
• e – Send a SIGTERM to all processes, except for init
• i – Send a SIGKILL to all processes, except for init
• l – Send a SIGKILL to all processes, INCLUDING init (Your system will be non-functional after this.)
• h – Will display help ( actually any other key than those listed above will display help. but ‘h’ is easy to remember

There are more suggestions in the official Linux kernel Documentation directory (that’s where this came from). See /usr/src/linux/Documentation/sysrq.txt for more information on this handy kernel feature.

First off let me tell you about how we’ll get this thing started. I am assuming you can at least turn the computer on and get into the BIOS. You’ll need a CD drive, a harddrive of at least 4gb, and an internet connection on the old computer. I’ll be using FreeBSD in this article, but many of these applications are easily available in source for Linux or any other Unix.

Install FreeBSD

First off, you’ll need to grab the latest FreeBSD iso from FreeBSD.org and burn it to a cd. Now, go into your computer’s bios and set the cd drive to be the first boot device, stick the cd in, and reboot. Once the cd starts up, you should see the following:

Now, navigate down to Standard and press enter. Press enter on the next menu that comes up telling you that you need to setup a partition scheme and you should see the screen below:

This is where we create what is known to BSD users as a slice. A slice is basically one of the four “primary” partitions in DOS terms. I’m assuming these computers have small harddrives, so let’s just go ahead and use Auto, so press the ‘A’ key. Now the list should have the slice added. Press ‘Q’ to save the changes and move to the next step.

A menu should come up with three options at the bottom, they are BootMgr, Standard, and None. Move down to Standard, press enter, and press enter again on the Ok in the next menu.

Now you should see a screen very similar to what you saw when editing the slices. I’m not going to go into details about slices or partitions here, but a quick look in the FreeBSD Handbook should give you plenty of information. Just go ahead and press ‘A’ on this window, then press ‘Q’.

Shortly after you press Q, you should get a window asking you to choose your distribution. Scroll down with the arrow key and press enter on developer. Immediately after pressing enter, a window will come up asking if you would like to install the FreeBSD ports collection. Choose yes. Now press the arrow key back up to X Exit and press enter.

A menu asking you to select the media type should come up now. Since we are using the CD, select CD/DVD and press enter. Press enter on the screen that tells you this is your last chance to backup and FreeBSD will begin to install.

After a few minutes you will see your success. Press enter.

You should now see a menu asking if you want to configure any Ethernet or SLIP/PPP network devices. I will assume you have one and let’s walk through it. Press enter with “Yes” highlighted.

After pressing enter, you will see a menu with a list of network devices. You should select the device from the list and press enter. Normally your NIC is the first in the list, but this may be completely different on your setup.

Select No on the IPv6 configuration window that comes up and Yes on the DHCP menu. Enter a hostname in the input box. The hostname can be anything you wish, but try to keep it short. Press enter until “Ok” is highlighted and press it again.

A window should now pop up asking if you want to configure the machine as a network gateway. Choose no here. After that, you should see a window asking if you would like to configure inetd and the services it provides. Choose “Yes” here, because we are going to want to enable ftp access to the machine. Now, the usual enabling-network-services-can-provide-a-security-hole menu comes up. Go ahead and choose “Yes” again. Press “Yes” one more time to bring up an editor.

Remove the #’s from in front of both ftp’s so that it looks like this:

Press Escape and a menu will open and press the A key.

Now we get into quite a few configuration menus. First, a menu asking if you want to enable SSH will come up, enable this. SSH will allow us to have a headless system so you don’t need a monitor for the old dinosaur, but only an SSH client. Do NOT enable anonymous ftp access to the box, that’s a very stupid thing to do. Select no for the next two menus having to do with NFS setup. You may edit your console settings with the menu that comes up yet, but I didn’t bother to. Of course you’ll want to set your time zone, so do that when the menu comes up, just make sure you choose no on CMOS clock menu.

We’re almost done! Enable the Linux binary compatibility when the menu comes up. You can enable the mouse in the menu that comes up next, but it’s not required. Don’t bother browsing the packages because we will be installing ports.

You must choose yes on the window that asks if you would like to enable any additional user accounts. This will be essential for when we go to setup SSH because I’m not going to enable root SSH, but allow root access over SSH via sudo. After selecting yes, you will see a window like the one shown below. You will want to select Users, then you will see the second image below. You only need to add a username and password. Once you have done that, change the shell text box so that it says /bin/tcsh. The 3rd image below should be what you have before you select okay. When the original menu comes back up choose Exit.

Go ahead and follow the directions for setting the root password that will come up next. Make sure you make this password high security because if anyone gets root access to your machine, you’ll get to start all over. Choose no on the next menu to visit the configuration menu again. Now chose “Exit Install” and follow the directions.

Configuring FreeBSD

After the install is done you will be directed to reboot your machine, after taking the cd out. When you boot it up you will see a message that says to just type a bunch of junk and press enter, do so. This is for unblocking entropy and will only happen on this boot. Once it is finished booting up, you should see this:

At the login prompt, type root as the username and then the password you set for root. If you don’t already know, root is the most powerful account available in a Unix system. Root allows you to do anything you want, including destroy the system. This is why you should not enable root over SSH or give out your root password. We’ll be using root here to install ports and setup some configuration files.

The first thing we should do is update our ports collection so we have all of the latest bug fixes. So at the prompt type the following:

hostname# pkg_add -r cvsup-without-gui && rehash

pkg_add allows us to install packages without having to compile them. I prefer to compile my ports, but you are more than welcome to use pkg_add. Rehash causes the internal hash table of the contents of the directories in the path variable to be recomputed, with the new binaries we just installed.

Here comes the fun part that can take a while, depending on how out dated your ports collection is. Run the following:

hostname# cd /usr/share/examples/cvsup
hostname# ee ports-supfile

You should now see a screen like the one below:
[IMG eeportssupfile]
Scroll down until you find this line:

*default host=CHANGE_THIS.FreeBSD.org

and change it so that it’s one of the domains listed here or just use the following:

*default host=cvsup5.FreeBSD.org

Now press ^[ (the escape key) and then press A to save our changes. What this does is checkout the latest ports collection from one of the cvs servers (cvsup5 in this case). So to start it, do the following:

hostname# cvsup ports-supfile

After a few minutes this should finish and take you back to a command prompt.

Installing Sudo

I'm going to make you install sudo as I said above. Once this is installed, I'll show you how to setup a "headless" system so you can unplug the keyboard/monitor and push the machine back into the closet. You'll just need a network and power cable. Let's get started! Sudo stands for superuser do. This allows any user added to the sudoers file to execute certain commands, all commands, or even get a root shell without having to directly login as root. This has quite a few benefits. The main thing is that you don't have to enable root over SSH and it makes you think of what you are about to execute as root. This can keep you from screwing your system over, so from here on out, let's consider it a bad thing to use the full root user unless absolutely needed.

First thing we'll need to do is change to the ports directory.

hostname# cd /usr/ports/security/sudo
hostname# make install clean && rehash
This will download the sudo source, compile, and install sudo. Now, I'll assume you'll want that second user you added to have root access, since this will be your main account from now on, so we'll need to edit the sudoers file.

hostname# cd /usr/local/etc
hostname# ee sudoers

Now, this will bring the ee text editor again. Find these lines:

# User privilege specification
root ALL=(ALL) ALL

Remember that second user we added during the install? Add the following under "root ALL=..." from above, but replacing username with whatever the username of the account that you added was.

username ALL=(ALL) ALL

Go ahead and save the file like we did before. Now we're ready to go headless, but before we do that, let's make sure you'll have access to the machine, before I tell you that you can remove your physical access to the box. Now run the command below:

hostname# sockstat

You should see sshd somewhere in the 2nd column. Now, you are ready to go to a headless system.

How to use SSH

I will quickly go over how to use SSH here for Windows and Unix. I will first start with Unix. On a unix machine you can open a console and run:

hostname# ssh username@ipaddress

If your username is the same as the one on the server, you do not need username@, but just the IP. If it is different, make sure username is replaced with the user you wish to log into the box with. To find the IP address of the old computer, you'll need to have physical access to the box. Run the following command on it after logging in.

hostname# ifconfig

You should see a screen similar to the following:

Your IP address should be in a location similar to the red circle and chances are that it will not be the same as the one in the picture. The IP address you want is going to be under the network device you configured during installation. From there on out, login is pretty obvious and it's just like as if you were sitting in from of the monitor. Use the command exit to close the ssh session.

Windows is a bit different because it does not have a built in client, so you will need to download one. I highly recommend PuTTY. On the downloads page, make sure you download putty.exe and not the other ones, because they lack SSH. Once downloaded, double click on the file. You should see a window come up like the one below. Note: Your fonts will not look as bad as they are in these screenshots. I am running PuTTY via Wine on FreeBSD because I do not have a Windows computer handy.

After filling in the IP address, as in the screenshot above, you will see the following window pop up. Click Yes on the security alert. This just tells us that it hasn't cached the SSH key.

Below is an ugly example of PuTTY running. Once again, I am terribly sorry I don't have my fonts setup correctly in wine. It will look much better on native Windows. Here on out it's just like having physical access as well.

Office Utilities

So we know you'll eventually need to do some work -- thanks to the guy that said I'm going to work all of my life and save up money the whole time. First thing you will probably needs is an email client. I suggest mutt. It is an extremely nice and feature complete text mode email client. Make sure you have logged into your second user account for the rest of this article.

hostname# cd /usr/ports/mail/mutt && sudo make install clean && rehash

This will download the mutt source, compile, and install it, just like we did with sudo. I would like to cover the setup of mutt, but there is a great guide here that would definately out do me.

Now I know you'll need a calender sometime. Besides the default unix cal program there are many other alternatives. I'm going to install Pal for you.

The first thing you need to do is run the following commands:

hostname#cd /usr/ports/deskutils/pal && sudo make install clean && rehash

As with the install of sudo, this will download, compile, and install pal. From there, I suggest you run man pal and read what is in the man page. Here is a quick way to get started though:

hostname# pal -m

Pal -m is interactive mode. This allows you to add/remove events, and even set up notifications of events.

Assuming you are like any other person, you will need some way to read your PDF and Word documents. How would you do this in text mode? Easy! We harness the power provided by antiword and pdftotext (part of the xpdf project).

To install antiword, run the following:

hostname# cd /usr/ports/textproc/antiword && sudo make install clean && rehash

This will install antiword and allow you to view your documents as a text document. This also has ample documentation once installed, so I won't cover its usage. Please run the command antiword to see a quick list of what to do, or run man antiword to see the full system documentation.

To install pdftotext, you need to run the following:

hostname# cd /usr/ports/graphics/xpdf/ && sudo make WITHOUT_X11=yes install clean && rehash

Make sure you include the WITHOUT_X11 or you will spend hours compiling the X server and all of it's dependencies. With pdftotext, you can convert PDF files to text or HTML documents to view in a web browser. I will not cover how to use pdftotext because you can just type in pdftotext and press enter at the prompt to get a quick how to. If you want more in depth information, run man pdftotext.

That brings us to our last office application, a web browser. Aren't we all spoiled by great applications like Firefox? I mean we have tabbed browsing, multiple download support, and good security. I bet you are thinking this is impossible in text mode, but you should know by now that it isn't. Elinks provides everything I just stated and is just as easy to use. To install Elinks, run the following commands:

hostname# cd /usr/ports/www/elinks && sudo make install clean && rehash

Once you have let it compile and install, you should be able to run the command elinks to open the browser. Once opened, it should look something like this:

To start using it, just enter the address and press enter. Over ssh, you can usually use your mouse to interact with it, to some extent. If not, you'll need to use the up and down arrow keys. To open the main menu, press the escape key and use the arrow keys to navigate it.

Hopefully you understand all of the work that can be done in text mode and I'm only scratching the surface! Once you learn the application parameters and find new applications on your own, you will see how quickly you accomplish tasks.

Keeping in Touch - Chat

Besides using email, you are probably going to need a way to keep in touch with your friends and family. You have probably lost all hope in using any modern instant messenger in text mode, but once again, you should know better. I will introduce you to an application that allows you to use AIM and ICQ from within text mode. So let's get installing!

As usual, run the following command:

hostname# cd /usr/ports/net-im/naim && sudo make install clean && rehash

Once you have it installed, run the command naim and you should see the image below.

It will take a while to get used to, but to login you need to type /connect yourScreenName and then you will need to type your password and press enter. You should also notice that the bar above where you type gives you hints. You should also familiarize yourself with the /help command.

If you would like to know more about the other features of naim, I suggest you read the man page as usual. Run the command man naim to see it.

For you geeks out there -- that means you. You probably already know about this one, but I'm going to go over it anyway. The most famous text mode client of them all, irssi. Irssi is a full featured IRC client that supports multiple servers, multiple chat channels, perl scripting, theming, and many other features. So, why stop now? Let's get installing! The command is as you guessed it:

hostname# cd /usr/ports/irc/irssi && sudo make install clean && rehash

To use irssi all you need to do is run the command irssi. From there, you have all of your basic irc commands, plus a few irssi specific ones for controlling the window. Here is a run down on connection to an irc network. In this case, we'll use an irc network I helped found, The Wildcard.

First thing you need to do is run irssi and type /server irc.thewildcard.org. Once you are connected, type /join #main and /join #equality. This will put you in two channels. You can then switch between windows using /win window#. In this example, /win 1 would be the server window and /win 2 and /win 3 would be #main and #equality. Everything else is just as you would expect with an IRC client.
[IMG irssi]

Gaming

There are a ton of games that can be played in text mode. I am only going to show you how to set up a few smaller games, but if you are a more advanced user, you can compile SDL to use ASCII as its output mode. You can then plan Quake and any other SDL application from within a console. You may want to google libaa and libcaca for more information on doing this.

First of all, let’s get you set up with one of the most addicting text mode games that I have ever seen, Nethack. Nethack is an amazing game, it is as if the developers thought of almost every possible thing. I guess that is why it is still popular. So here goes…

hostname# cd /usr/ports/games/nethack34-nox11/ && sudo make install clean && rehash

Once it is done, that’s all there is to it! Just run the command nethack and go. You may want to read the man page (by running man nethack) or visit www.nethack.org for more information.

After you spend weeks playing Nethack, you may want to play some good old classics. There are plenty of those in text form. I’ll start off with nInvaders. This is by far one of the coolest text mode Space Invaders clone that I have ever seen. To install it run:

hostname# cd /usr/ports/games/nInvaders && sudo make install clean && rehash

Once installed, it’s pretty simple. Run the command nInvaders and use the right/left arrows to move and the spacebar to shoot.

If you want to go with another classic, you can play BSDtris. This is a full features ASCII Tetris clone. To install:

hostname# cd /usr/ports/games/bsdtris && sudo make install clean && rehash

As soon as that finishes up, all you have to do is run the command bsdtris and follow the key guides, on the screen, to play.

Wrapping it all up

I hope this has opened the world to some of you people afraid of text mode. There is a whole new world of software out there waiting for you to discover it. I suggest starting at sites like freshports.org and freshmeat.net and just start browsing. There are many more things that can be installed from the FreeBSD ports collection, but you should at least know the basics. If you have any questions, don’t hesitate to reply to this post or join us in IRC.

]]> http://www.codymays.net/content/2006/05/04/bring-back-that-old-computer-make-it-useful-for-modern-day-activities-but-with-a-twist/feed/ 1 http://www.codymays.net/content/2006/03/06/jayant-lives-again/ http://www.codymays.net/content/2006/03/06/jayant-lives-again/#comments Tue, 07 Mar 2006 03:34:58 +0000 Cody Mays http://www.codymays.net/?p=32 I must say I’m proud of the progress with Jayant. It can now serve basic html pages and handle 404’s. Each connection is processed via a pthread as I said the in the previous post. I fixed two buffer overflows in it today as well.

Tomorrow I’m going to try to get a mime type system up. I want to the /etc/mime.types file if possible, this means I’m going to need a custom parser for it. I’m debating whether to write one, or go the easy route and find a public domain one. I guess it just depends on how much time school gives me.

As of today, Jayant also runs on two platforms with no modifications, FreeBSD and linux. So I can only assume it will run on any other unix. I’ll be trying BeOS within the next few days, as well as a native SkyOS compile.

cody@devnulled:/home/cody/jayant>./jhttpd
Server Port: 8181
Server Log Dir: /home/cody/jayant
Server Signature: JayantHTTP (FreeBSD) 1.0.0
Adding callback for fd 3
Realloc’ing fd_tasks
No callback for 1
No callback for 2
Listening on port 8181 fd 3

cody@laptop:~/jayant$ ./jhttpd
Server Port: 8181
Server Log Dir: /home/cody/jayant
Server Signature: JayantHTTP (Linux) 1.0.0
Adding callback for fd 3
Realloc’ing fd_tasks
No callback for 1
No callback for 2
Listening on port 8182 fd 3

Here is a little bite to chew on, the first page served by it:

Click for larger image

]]> http://www.codymays.net/content/2006/03/06/jayant-lives-again/feed/ 0 http://www.codymays.net/content/2006/02/15/debian-gnukfreebsd/ http://www.codymays.net/content/2006/02/15/debian-gnukfreebsd/#comments Thu, 16 Feb 2006 02:32:11 +0000 Cody Mays http://www.codymays.net/content/2006/02/15/debian-gnukfreebsd/ I have been extremely busy with school this week, but tonight I had about an hour to do something. So I decided to try out Debian GNU/kFreeBSD. This is a very interesting OS to me because of my love of both Debian and FreeBSD.

Many people ask about the name. It stands for GNU userland and kernel of FreeBSD. Not only does it come with glibc and the rest of the GNU userland, but it also has most of the Debian packages ported over for use with the apt-get port.

I highly recommend people try it that may want to use BSD as a server, but can’t leave their linux setup. They are extremely similar with this setup. Only problem I noticed was that you need to manually run dhclient and reboot on the first bootup to get it to setup your nic correctly. Other than that, I’ll be looking forward to getting a working gnome or KDE port on this system.

]]> http://www.codymays.net/content/2006/02/15/debian-gnukfreebsd/feed/ 2 http://www.codymays.net/content/2006/01/24/apache-apache-apachewhy-arent-you-working-working/ http://www.codymays.net/content/2006/01/24/apache-apache-apachewhy-arent-you-working-working/#comments Wed, 25 Jan 2006 02:01:34 +0000 Cody Mays http://www.codymays.net/?p=20 I’ve just spent a good two to three hours of my time screwing with the Apache 2.0.54 Ubuntu Linux package, just to get mod_rewrite to work properly. So if you have an Error 500 when adding “RewriteEngine On” to your .htaccess, this is the fix for you.

1. cd /etc/apache2
2. sudo nano apache2.conf
3. Add Options +FollowSymLinks
4. sudo /etc/init.d/apache2 force-restart

and you should be up and running. Hope that assists you people out there. I know I spent too much time on that.

]]> http://www.codymays.net/content/2006/01/24/apache-apache-apachewhy-arent-you-working-working/feed/ 2 http://www.codymays.net/content/2005/12/16/kvm-review/ http://www.codymays.net/content/2005/12/16/kvm-review/#comments Fri, 16 Dec 2005 20:31:18 +0000 Cody Mays http://www.codymays.net/?p=12 Well, after a week of waiting, my KVM came. This is the model I bought. It features rack mounts, 8 ports, hot key switching, manual switching, keyboard/mouse/monitor reset without power down, and auto scan.

After spending an hour and a half rewiring my room to get one extra plug, I discovered I had an empty plug right next to where I wanted the KVM…so I ended up unrewiring. So now I had it installed and I was dying to test it out. So I hooked devnulled(this server) and sputneek(my athlon64 gaming box) to the kvm. The keyboard I used was a Logitech Cordless Desktop Express.

After powering on the KVM it auto scanned for connected computers and changed the light color for the port to green. Since I was testing it on sputneek first, I pressed the first button to put us on that computer. Now I’m going to pause and say a few things I found odd before I got to this point. When I was flipping through the instruction paper, it had warnings about how the device can cause some radio interference. I still to this day have no clue why, but it did. When gnome came up on the computer, my mouse would just go psycho when I would move it and my screen was a bit blurry.

To fix this wonderful problem was fairly simple. I booted ubuntu backup, and since my keyboard worked, switched to tty1 and ran a sudo dpkg-reconfigure -y xserver-xorg && sudo killall gdm && gdm && exit. That fixed it as it basically recreated my xorg.conf with the new hardware that it detected, as the mouse and keyboard identify as different devices from my Logitech ones. That also fixed the blurriness issues I had.

On devnulled, there was no problem at all. It worked beautifully.

Pictures:

]]> http://www.codymays.net/content/2005/12/16/kvm-review/feed/ 0 http://www.codymays.net/content/2005/12/09/test/ http://www.codymays.net/content/2005/12/09/test/#comments Fri, 09 Dec 2005 19:36:02 +0000 Cody Mays http://www.codymays.net/?p=6 #include int main() { printf("BBBBBBBB\n"); return 0; } ]]> http://www.codymays.net/content/2005/12/09/test/feed/ 14