Only 6 days later than I'd planned, I'm finally setting out across the country. Far too much stuff, but living in one place for 7 years things seem to pile up. It will be an interesting trip, especially trying to make it work with the two cats and dog -- we gave them as much space as we could, but it's not a lot. We'll have to stop a lot and let them exercise. Haelo, the dog, is ecstatic because she loves to be close by. The cats are not enthused, already ready for it to be over and it hasn't even started yet.

Using firefox browser which comes with my Fedora 5 installation, after some time, lets see how much it can "eat" your computer memory: it have 8 opened tabs, from which only one is "complex" (gmail.com)

$ ps axu | grep firefox
mator     2823  1.7 37.3 796336 383508 ?       Sl   Aug18 102:07 /usr/lib/firefox-1.5.0.6/firefox-bin

so, after 4 days of running it taken 800Mb !!! A good way to make firefox to eat all memory is to leave it in memory for 2-3 days with some pages which auto-reload, like gmail, nagios service tracking or some news site.

... jumping through my spam folder today morning, found at least 3 messages marked with SA (spamassassin) :

From: 1883243462@reports.spamcop.net
To: postmaster@myexampleworkdomain.ru
Subject: [SpamCop (80.68.246.245) id:1883243462]Новое сообщение в форуме SEMICVET.RU
  [!! SPAM]
X-Spam-Status: Yes, score=7.2 required=5.0 tests=DATE_IN_PAST_06_12,
        FORGED_MUA_MOZILLA,FORGED_RCVD_HELO,FROM_STARTS_WITH_NUMS,KAS_SPAM,

It was nearly seven years ago, in the fall of 1999, when I moved from Alaska down to Florida. I had been intending to move to Seattle, but a strange turn of events got me a paid trip to Florida for a job interview which turned into a job. Always up for something new and different, I took it, planning to stay for a year or two. Now it's late 2006 and I own a house in Margate, Florida. I spent the last three years remodeling the house with my then-girlfriend, never quite happy in Florida (I don't enjoy this many people, this much concrete, this much heat, all with no nearby escape into nature), but never quite unhappy enough to find a way out, either.

It has been April since my last post. I have been coding up the structures to handle the basic FAT filesystem. I am at the point where all I have left is complex kernel code to figure out. These issues are as follows.

1. Bringing an inode by number into memory from disk, or accessing it already there. Up till now I had a file struct pointer.
2. Identifying what that inode is (regular file, directory, irregular file,...:)
3. Determining if slack space exists
4. Getting to the last logical block to read or write
5. Writing the inode in cache back down to disk (aka The Cache Incoherency Problem)

I have a few other issues that are minor and are not worth mentioning unless they really start to cause problems. More later.

What is webmail?

Webmail is a web application that allows users to read and write e-mail using a web browser. You can access your email through a browser (like Internet Explorer) from everywhere in the world, with advanced features (mailboxes, address book).

There are lots of webmail providers on the net. But the meaning in details changes upon the service, application and the means by the project.

Anybody knows how to make a rugged pc system? At home? any tips?

http://kegel.com/crosstool/

http://www.libsdl.org/pipermail/sdl/2003-April/053501.html
http://www.linux-mips.org/wiki/Toolchains#Pre-built.2FBuild_Kits

AM_PATH_SDL not found in library.
locate sdl.m4
[embedded@testpc code]# export ACLOCAL_FLAGS="-I /usr/share/aclocal"

During the path a packet leaves the source computer and reaches the destination computer, When it is forwareded by an intermediate router, the Time to Live (TTL) is subtracted by 1.

This is utilized by traceroute to determine the path a packet takes to the destionation.

The Windows implementation of traceroute (tracert.exe) determines the path taken to a destination by sending ICMP Echo Request messages with varying Time to Live (TTL) values to the destination and receiving ICMP Time Exceeded messages.

Mitsubishi finished with my car today; I picked it. I asked what was up with the transmission, and the tech took me out into the shop and showed me; the end (overdrive) clutch drum was slightly scored on the inside, allowing fluid to leak past and not build up pressure that quickly to engage overdrive, hence the flaring on the upshift to OD. They replaced the drum (which came with a new piston, as well as a new set of frictions and steels) and the outside cover, which contained the point that the drum rides on. I haven't taken it on the freeway yet, but I'm optimistic that it's fixed.

Damn, compiling qt is taking a while. But I want it for doing kernel configs in X.

A co-worker gave me a Dell Inspiron 2650 without a disk a couple of weeks ago. I managed to find a disk on Craigslist for $40, and set out to get the machine going. I settled on Crux as a Linux distro because I'm trying to wean myself from RedHat / Fedora, which is getting bloated. I considered NetBSD for a while, but I figured that since this is a laptop, I'd go with Linux as sometimes non-Windows operating systems and laptops can be a bit tricky, and I definitely have more of an idea of what I'm doing when it comes to Linux.

You can learn about my research and interests at my university website : http://www.dsm.fordham.edu/~mathai/

It is the beginning of march. Since about the begining of the year my teacher and grad advisor have been solidfy the basic structure of the slack space filesytem. I originally based one the ext2 file system but in the end we decided to go with one that resembled a FAT system. Basically there are four main structures a 'superblock', a bitmap for which inodes have slack, a file allocation table establishing a slack block link-list, and a file table for cross-referencing a filename and its starting inode.

pictest
pictest
pictest
pictest
pictest
pictest
pictest
pictest
pictest
pictest
pictest
pictest
pictest
pictest
pictest
Formatting guidelines:

* Allowed HTML tags:

Brian Harvey throws down the gauntlet: implement the Ice Cream problem in a small number of lines of Java. Well, since I don't know Java, I'll take up the challenge in C++...