Archives for category: Uncategorized

Last month I bought my third boat. I found a 1979 Morgan 462 ketch in southern California. This particular boat is hull number 21. It is a center cockpit with a large aft cabin and two heads. It doesn’t have the Scheel keel design. As best I can tell, I’m the seventh owner of the boat. With that many previous owners and over that many years, there have been many changes to the boat and each owner had a particular part of the boat which interested him and others which he neglected.

My plan is to restore and upgrade the boat to blue water capability. I’m hoping to find the community of other Morgan 462 owners. I want to do the usual comparing of notes and sharing of ideas.

Today I’ll return to the boat to finish undoing the changes made to the galley, which include extracting a household fridge.

Advertisements

I’ve had a Cisco LinkSys E1000 router/Access Point in my collection for some time now. I’ve been meaning to use it as my router and Access Point, instead of the Comcast cable modem, at home, so I can get a lot more detail about the network traffic between all of the hosts in my house and the Internet. I intend to install dd-wrt on the E1000 before I actually start using it.

Since I have been playing with many LinkSys WRT routers over the years and since I knew that some of them had a serial port on the circuit board, I wanted to be able to use the serial port on this E1000, before I actually started using it. In this article I’ll describe the few simple steps required to be able to use that serial port (which the E1000 does indeed have).

My E1000 is a version 2.1 device, as printed on the label on the underside of the case. Judging by some information I found in other people’s ‘blogs, this circuit board is different from the version 1.0 board.

The serial port is provided via a row of solder points which are labeled DJ2. There are a total of five solder points (actually, holes through the board) and they are:

Ground

Unknown

Transmit

Receive

Voltage

If you open the case and orient the board such that the word “CISCO” is properly oriented and toward the bottom of the board, the connections are Ground on the left and Voltage on the right. The board uses 3.3 Volt signaling, so it’s not actually an RS-232C serial port. You’ll need a way to convert from 3.3 Volts to 5 Volts if you want to use a proper RS232C serial device to connect to the E1000 serial console. I used a Sparkfun FTDI converter.

Once you’ve established the physical connections, to Transmit, Receive and Ground, the data rate is 115,200 and the protocol is 8 data bits, no parity and one stop bit. It is an ASCII conversation and you’ll be given a BusyBox prompt when you connect. You many have to send one NewLine character to get a prompt from BusyBox.

Next for me is to install dd-wrt on this E1000.

 

This time around, installing Pentaho BI Server version 3.8.0 Community Edition, I started with a Dell PowerEdge R715. 64 GB of RAM, 24 CPU cores at 2.5 GHz and a boatload of RAIDed disk space. For the OS, I installed Debian server 6.0 (squeeze). MySQL is still our standard for RDBMS so I installed version 5.1.49-3-log from the Debian packages. I configured it with InnoDB and MyISAM and located the datadir on the RAID device.

We experimented a bit before installing any software, to confirm that we were using an appropriate filesystem type, with appropriate parameter values. We didn’t find a huge performance difference between ext3, ext4 and xfs, ext4 performed slightly better, in what we thought were “typical” usage scenarios so we chose that filesystem. We also set the option string “nosuid,nodev,noatime,data=writeback,nobh,barrier=0,nouser_xattr”.

I will try OpenJDK 1.6.0_18 from the Debian packages and start with its default configuration. I will not be surprised if I run into some issues which can only be solved by replacing it the the “official” JDK build from java.com.

Admin server configuration

To configure the Admin Server first, I adjusted three files:

resource/config/console.xml:

I defined the solution-path, war-path and platform-username to fit my environment. I added default-roles and adjusted the default-server-dir to match my installation.

resource/config/log4j.xml:

I adjusted the File parameter and set all of the logging levels to DEBUG.

resource/config/login.properties:

I changed the password for the admin user. I also switched from an OBF password to an MD5 password.

resource/config/console.properties:

Enabled SSL.

BI server configuration

To enable the use of LDAP for user authentication, I adjusted three files:

pentaho-solutions/system/applicationContext-spring-security-ldap.xml

pentaho-solutions/system/applicationContext-security-ldap.properties

pentaho-solutions/system/pentaho-spring-beans.xml

Chicago, where I live, has been having trouble selling traditional newspapers for a few years now. In an apparent effort to appeal to a wider audience, or maybe to attract younger readers, the Tribune created a new newspaper called “RedEye”. I use the term “newspaper” very loosely. I’ll provide an example why.

In the 1 February 2012 issue of RedEye, there was an article on Chicago neighborhoods which caught my eye as I left my morning train.

In the third from last paragraph, the reporter states that all four of the victims “were between 24 and 80 years old”. Well, I should hope so. Are 80 and 90 year olds often shot to death in Chicago, making this “narrow” age range of victims significant? Or, is it significant because homicide victims in Englewood are typically younger than 24?

She goes on, in the next paragraph, to confirm that those two victims of homicide “were both fatally shot”. Can one be the victim of a shooting homicide and be shot any way other than fatally?

Who is more at fault here, those who print this simple, no-depth reporting or those who read it?

I’ll keep track of things I’m working on here, describe things I’ve figured out and ramble about ideas for future projects.