Going where the mind takes you, the norm is irrelevant!
| The latest linux-next version of the Linux kernel is | = | next-20100903 |
| The latest mainline 2.6 version of the Linux kernel is | = | 2.6.36-rc3 |
| The latest snapshot 2.6 version of the Linux kernel is | = | 2.6.36-rc2-git5 |
| The latest stable 2.6.35 version of the Linux kernel is | = | 2.6.35.4 |
| The latest stable 2.6.34 version of the Linux kernel is | = | 2.6.34.6 |
| The latest stable 2.6.33 version of the Linux kernel is | = | 2.6.33.7 |
| The latest stable 2.6.32 version of the Linux kernel is | = | 2.6.32.21 |
| The latest stable 2.6.31 version of the Linux kernel is | = | 2.6.31.14 |
| The latest stable 2.6.27 version of the Linux kernel is | = | 2.6.27.53 |
August 12th, 2010 ··· andarius
Well, after holding off for a very long time I have broken down and purchased a phone with the android OS on it.
Since they came out I have wanted an android device. After all, who in my professional field with my type of hobbies and likes wouldn’t right? Open source and Linux based had me sold immediately. the idea of competing with the other high end smart phones out there as a goal was a definite plus. So why hold out in the first place?
Read the rest of this entry »
Hardware, Linux ··· No Comments »
January 1st, 2010 ··· andarius
For Christmas I was given a board I had on my wish list to replace my current firewall hardware. The board is the Intel BOXD945GCLF2, an Atom 330 powered board with a single PCI slot and onboard gigabit NIC. An ample replacement for the aging Via board.
I use Endian Firewall Community Edition on my firewall. I loaded things up and all seemed fine until the first reboot. I plugged my cable up to the ethernet port to configure things via the web interface and was unable to connect. After trying different cables and all the other normal means of troubleshooting I figured it was time to diagnose the board itself. I pulled out a Slackware 13.0 install CD and loaded it. After reboot the interface worked like a champ. I transferred a few large files and even rebooted a few times to make sure. Not a problem one showed up on the Slackware install so I went back to installing Endian.
Read the rest of this entry »
Linux ··· 2 Comments »
October 30th, 2009 ··· andarius
On my home network I use NFS to access shares on my server. What right minded fella wouldn’t right? Well recently for some reason on boot up my desktop system would spew an error about the NFS start up. dmesg showed nothing so I turned to /var/log/messages for more detail and found the following:
Oct 29 23:25:57 ion dhcpcd: wlan0: carrier acquired
Oct 29 23:25:57 ion dhcpcd: wlan0: rebinding lease of 10.2.2.49
Oct 29 23:25:58 ion dhcpcd: wlan0: acknowledged 10.2.2.49 from 10.2.2.7
Oct 29 23:25:58 ion dhcpcd: wlan0: checking for 10.2.2.49
Oct 29 23:25:58 ion slim: slim: Stale lockfile found, removing it
Oct 29 23:25:59 ion rpc.statd[961]: Version 1.1.6 Starting
Oct 29 23:25:59 ion sm-notify[962]: Already notifying clients; Exiting!
Oct 29 23:25:59 ion rpc.statd[961]: Unable to read state from '/var/lib/nfs/state': errno 0 (Success)
Oct 29 23:25:59 ion nfs: mount.nfs: DNS resolution failed for 10.2.2.4: Name or service not known
Oct 29 23:26:00 ion nfs: mount.nfs: DNS resolution failed for 10.2.2.4: Name or service not knownIt looks like the network comes up and then it tries to start up NFS and mount the network shares, failing due to DNS resolution. Why on earth would it do this with the network up? Got me. Running the NFS script with restart yielded properly mounted NFS shares so something just wasn’t meshing well. This got me thinking along the lines of timing, but this was not occurring before a few days back.
A bit of googling turned up an important detail, by default dhcpcd would fork to the background and let the boot process drive on. Well, looking closely at the log data shows that while it had started the DHCP negotiations it was not done. The complete process looks like this:
Oct 29 23:45:14 ion dhcpcd: wlan0: carrier acquired
Oct 29 23:45:14 ion dhcpcd: wlan0: rebinding lease of 10.2.2.49
Oct 29 23:45:15 ion dhcpcd: wlan0: acknowledged 10.2.2.49 from 10.2.2.7
Oct 29 23:45:15 ion dhcpcd: wlan0: checking for 10.2.2.49
Oct 29 23:45:20 ion dhcpcd: wlan0: leased 10.2.2.49 for 86400 seconds
Oct 29 23:45:20 ion dhcpcd: forking to backgroundThe key line containing “leased 10.2.2.49″. from the above you can see it took 5 second to complete. The first log snipping showed NFS starting up and trying to mount at 2 second after it checks for the IP. Talk about small margins of error…
For me the solution was simple. Crux uses very simple scripts for its start up. In fact the network script is pretty much what one would use to start it via cli manually. Since this is the case I simply added the “-w” option to the dhcpcd line which tells it to wait for the address to be assigned before forking to the background. Now it all works like a champ once more. It slowed my boot to login times by about one to two seconds, which puts me at a whopping 13 seconds or so. I think I can live with that… 
Linux ··· No Comments »
October 9th, 2009 ··· andarius
Not too long ago Comcast decided to play the DNS game with along with a bunch of other ISPs and DNS service providers. What do I mean and why would they do this? I will explain what that means in a moment, why is simple. It allows them to push and/or control your traffic in many ways.
Read the rest of this entry »
Linux ··· No Comments »
October 6th, 2009 ··· andarius
I have been inclined to do bit more research on the AP I recently purchased. A D-Link DAP-2553. This unit has been performing extremely well since I got it and I have no complaints so far. I did however want to know more about it as is my nature. Digging around on the web and the oracle turned up very little. As I work in an RF related field I turned to an awesome resource for data on RF devices, the FCC.
Low and behold they have the full data on the AP as I had hoped/expected. Turns out this little puppy is fully Atheros, sporting an AR9132-AC1E as its network processing unit and an AR9106-AL1A dual band radio. The AR9132 is listed by Atheros as a 400 MHz NPU (Network Processing Unit) and of course being dual band the AR9106 operates in the 2.4 GHz (b/g) and 5 GHz (a) bands. Some nice data can be found at the Atheros site “here“.
