Well, it's been just a touch over 72 hours since I got my Amazon Kindle Fire.
I pre-ordered it shortly after it was announced, with an ETA for November 17th with free 2-day Amazon Prime shipping. I knew there was a chance that they should ship early, because they did that the last time I pre-ordered something (The Kindle 2 and the Nintendo 3DS). But, its been a busy week...and I tried my best to keep my calendar open to receive it....I had an appointment pre-Kindle Fire announcement on the 14th, and I was keeping the 15th open for something that was later scheduled in conflict to the 14th....and ended up having an appointment on the 16th. If I had some notice from Amazon just before they shipped to adjust its timing...I might've...since the 15th being open now...I could've gotten it then. Instead I had to wait for UPS to make a redelivery attempt and bring it to me on the originally scheduled day... November 17th.
I didn't open it immediately when UPS gave it to me, in fact I put it down first and then had to find it before I could open it. It was easy to open...no info with it, but I eventually found the power button and it eventually booted and walked me through setup...though complicated by the fact that I needed to know its MAC address to add it to my radius and dhcp server configs. Plus I hadn't decided on an IP for it yet. Fortunately with radius access controls, its easier to find the MAC address of new devices than before.
It came pre-activated, in fact I had seen it in my kindle account before they shipped it (but no serial number was associated with the registration yet)...but I changed its name to follow the naming scheme I had gone with (if you can call only one previous device the basis of a scheme)...though I am tempted to get a Kindle Touch 3G to succeed my Kindle 2....though wonder if they're going to come out with a DX version? What I liked was that my Kindle Fire's email address was my first Kindle's address with '42' added to the username. Though there's a bunch of Kindle apps associated with my account that I don't recognize....wish the automatic naming was more descriptive. Suspect some are devices where I had to reinstall the system or have since be retired.
Though I wasn't crazy enough to buy content for it before receiving it...though I was tempted.
Anyways...what I was getting to, was once I got it working on my WiFi network, the next step would've been registration...and it flashed it briefly before telling me that it was registered and had the name I have given it earlier. And, then it was to update itself. So I found somewhere to plug it in and left it.
Big problem that is getting worse in my home now...so many things that need to get plugged in, and all the convenient outlets are already full and now I'm running out of inconvenient ones too. The Kindle Fire is using one of those inconvenient ones. I've been meaning to build myself some kind of charging center, similar to the kind of thing Cali Lewis was presented doing in a GeekBrief. Perhaps I'll have to step up plans to get around to 'building' it. Just haven't found that piece of furniture to buy to modify yet... Probably just a matter of time that I come across something reasonable on Amazon.com with Prime and get it though....
Well, I was getting really annoyed with it complaining and kicking out the replaced disk in LHAVEN. So, I shutdown the system and took out the disk, figuring it should just continue to run fine degraded until I get around to replacing it.
Well, it wouldn't power on after that. I went through everything, no joy. It had done this a while back when I tried adding something to it. It could just be the power supply has flaked out, but I don't have a tester or multimeter handy...so I can't really test it. Could buy a new PS...and I may do that.
But, I kind of suspected the drive issues weren't actually the drive but possibly some deeper hardware problem. So, I had been planning to replace LHAVEN at some point. It has done quite well, being circa 2002. Started out as a 64MB Duron 800MHz machine, eventually peaked at 2GB Athlon XP 3000+. It had replaced a Cyrix PR233 box that had gone up in smoke during a hot summer day in 2002, when the transformer outside blew....the computer survived the brownout and then blackout, but the fans didn't spin back up when power returned...so it burned itself up. Later I found one problem with this new system. It wouldn't resume after losing power. No BIOS setting to alter this behavior and I did try to see if there was alternate BIOS updates for it. It was kind of a painful machine to manage, because for some time kernels didn't have built-in support for all the SIS chipset stuff in it....so an update would roll out, and NIC was usually one of the things to definitely go missing. Which made for fun to rebuild a custom kernel upgrade for it. Eventually it got stable.
But, needing essentials like DNS, DHCP to be available after an extended outage...I moved these to another server (originally an old Pentium 75, which has evolved into what is known as 'box' today). For the longest time it was RedHat 7.2, and then RedHat 7.3 when fedora legacy switched to only supporting 7.3 and 9 releases. It continued after fedoralegacy stopped supporting it, I was building some of the packages for it by hand...like bind (in response to the Kaminsky exploit). There were parts of my network that wouldn't function without LHAVEN...like an old Windows 2000 box that was barely functioning...(old Gumby).
I nearly lost it during the Icepocalyse....but I tracked down motherboard replacement for it from geeks.com. It was a slighty newer mobo, but equivalent chipset. It did have some things the old mobo didn't, like USB 2.0 support (I didn't use USB and still don't), support for 2GB of RAM instead of 1GB...so I upped it for better BOINC'ng. And, faster CPUs....so I upped from 2200 to 3000.
At one time, I had turned it off to do some upgrades...which didn't pan out. Tried to slap a gigabit card into it...didn't work. Wouldn't get along with the on board stuff, and the BIOS didn't have ways to get things out of the way enough. It also never fixed the resume after power loss issue. But, during this process it failed to power on....but after a couple days, it came back and I decided to upgrade its UPS and hopefully it would make one last outage. Well, there were several others since then where it came back afterwards. But, looks like this is the last time for it.
Pages: 1· 2
Last night I wasn't thinking....running into the fact that my boinc-client package is broken on 'box', I thought..."why isn't it running the boinc-client from Lucid?" And, I proceeded to fix it with "apt-get"...and then realized that I'm still running karmic and unbreaking it wasn't. The boinc-client pre-Lucid is too old for a project I'm in, and it is annoying how ubuntu doesn't update packages within releases (which get's really annoying with LTS.)
Anyways....I decided the way to resolve the mess I had now made by downgrading my boinc-client, was to upgrade to Lucid Lynx 10.04LTS. It was my plan to upgrade both my Ubuntu servers to 10.04LTS (the other being 'orac' which is currently 8.04LTS)....but I was going to put it off to when I had more time and allow time for the release to stabilize (given all the issues I had when I first started running box on fresh Karmic).
So, it started....things got a little annoying, in that the upgrade requires attention....and I didn't want to spend my whole evening watching it upgrade. So, I'd check it now and then, and sometimes find it stuck waiting for me to make a decision for it, though the first one where it wants to restart stuff after a pam upgrade...that's annoying. Just do it okay, stuff it restarted weren't working right along the way anyways. Namely I found that I couldn't access websites...at first I thought the squid had become dorked, and I couldn't restart it because invoking /etc/init.d/squid said it was now a service...but using service didn't find it. Though later I realized it wasn't working because DNS was broke ('box' is my primary DNS server)... I was able to restart that in the usual manner.
Partly because of the pauses, and a bit due to slow download....it wasn't looking like I would finish before 'bedtime'....but it seemed that it would be close enough.... It wasn't, but I ended up staying up to the bitter end. So, that I could reboot and do a quick check that all was clean.
Namely, I checked that named, dhcpd, ntpd and squid were running (since these were some key services of this server, and were ones that often failed to start after boot in karmic...especially named. Manual start always worked...at one time I was restarting these services in rc.local where it always worked rather than at the 'normal' time).
Then I went to fill in the missing icons in my launcher panel....there were two holes, there also seemed to be a hole in the tray area. The missing icons were Evolution (which I right-clicked to make reappear), and boxee (which I installed the latest of). I then called it a night.
The next morning, I continued to poke around some more....adjust appearance, add some chat/broadcast accounts...and look into my ubuntuone issue....first the tray thing was missing, apparently its by design...but, I don't remember that. I poked around some more and some more....then I looked at 'ulkc' and saw that it also didn't have the tray applet anymore, and I just didn't miss it... So, I then went to check that it was connected to my account and sync'd. Actually, it really was syncing, etc. When I was at Penguicon, I had put a copy of the pictures I had taken into my cloud...expecting to see them later on 'box' when I got home. But, it would never appear. Upgrading 'ulkc' didn't help things.
During the poking around, I disconnected 'box' and reconnected...and that apparently fixed whatever was wrong, as it started syncing...and soon the folders appeared.
While this was going on, I thought that maybe I would need to finish things up by remote....so sadly I discovered that remote desktop still doesn't work in Lucid. Turning it on, consumes 50% of my CPU. My 8.04LTS (orac) doesn't suffer from this problem. But, I want to bring both servers in sync eventually, so I can see about getting failover for dhcp working between the two.
Oh well....at least it seems more successful than when I had upgraded 'box' to Karmic. And, now I'm at an LTS where it can stay for the next 2 years.... We'll see what happens when I upgrade from 8.04LTS to 10.04LTS next month....
I hadn't intended to start upgrading systems to Karmic Koala so soon...since the servers are kind of pegged with other people downloading and upgrading. But, playing around with do-release-upgrade on my Ubuntu server at work....at first (on Thursday) it didn't show the release and the later it did.
Since its running as a Guest on my Solaris 10 x86 desktop, in VirtualBox, I could take a snapshot and let it go. Plus its a pretty minimal server...its just to run BOINC. It estimated that it would take about 4 hours to download what it needed. Guess it doesn't take advantage of the I2, or things were pretty saturated....
When I came in yesterday, it was still going...was kind of hard with it blanking the screen and stopping waiting for input...but it kept chugging along and eventually upgraded and all seemed good.
So, last night I decided to pull the trigger and upgrade my notebook (ulkc). It warned about a lot more stuff that was unsupported and would be removed, and lots of warnings about all the 3rdparty stuff. But it gave an estimate of 10 hours to download and asked if I wanted to continue.
When I got up the next morning it was waiting to ask about differences in my mod blacklist, it wanted to add pcspkr but it wasn't going to keep the modules I had blacklisted...and no option to merge or stuff....so I told it to keep my blacklist. Wonder what'll happen when I do box, since there's nothing connected to its sound card....so its only way to make noise is through its pc speaker.
After it was done and rebooted, two things didn't work. The firefox button on the panel, since default had changed from firefox 3.0 to firefox 3.5 (though I've been using 3.5 since it came out, just replace /usr/bin/firefox with a new symlink)....easy enough to replace. And, virtualbox.
I reinstated the 3rdparty sources for apt, and checked for updates. Guess there's no Karmic repository for Boxee yet. The only thing that did upgrade was dropbox.
So, I uninstalled virtualbox (it was 2.2) and reinstalled it (3.0 from the karmic repo). And, then I tested it.
I'm can't think any more....don't know what's missing that I didn't intend to leave off.
Sure there's stuff that I wouldn't mind having back, and stuff that isn't readily available for the distro I'm using...namely no mondorescue for 9.04 yet. I also couldn't get DHCP peering to work, evidently the rule that both servers be the same version is important. They would start up fine, but once they talk to each other....the second is over. Perhaps I'll sync the servers when the next LTS comes out.
But, I did get ddclient moved (or rather I moved my configs to the version with ubuntu)...and I updated the ip configs to be like my other strange linux boxes.
I suppose I'll slowly comb through the old 'box' HD and figure out the various strange and twisted thigns I've been doing on there. Such as discovering the strangeness of how I've been doing my IVS Status updates.
I suppose one last item would be to make sure I can burn cds with the burner I moved over....
I got the new-ish computer out and started looking at what I could change in it....while digging into it, I discovered it has a SATA drive. So, that meant no moving the old 'box' harddrive into the new 'box' hardware. So, that narrowed the return options to one.
I transplanted the CD burner in the old 'box' into the new 'box' and then set out to get ubuntu-9.04-server-i386.iso. First tried downloading via OSL....that was going slowly. Noticed there was a .torrent file available, so I decided to get it that way. That went much faster.
But, then I got distracted...ferret, supper...but eventually got around to burning the image and starting the install process.
After remembering the desired sequence of answers that would result in something that I would like (and having it set itself up with out DHCP)...I had ubuntu server with DNS-server, SSH-server, and Mail-server. I set out to work on being able to access the old drive on the 'box', after some thought, I decided to load on 'ubuntu-desktop' I like have lots of windows, and which a much faster system there's other things I'll probably be doing on here now/in future. 'box' started as a Pentium-75, and is now a Pentium 4 3.2Ghz w/HT. I also discovered that the machine has a GigE NIC (it didn't mention this on the website....)
I let 'ubuntu-desktop' install overnight, and found it didn't work in the morning. Had to introduce another 'sudo apt-get update' to get things along. I threw some other stuff I was starting to find that I wanted/needed like, binutils, ncftp, ntp, boinc... and then bounced the box.
Got a USB adapter for the old drive, but 'box' wouldn't see it automatically. It doesn't seem to load usb stuff on boot, looked around but decided that might be a good thing....for now. Doing 'lsusb' would make the drive appear....
I continued to setup the environment, decided to leave it using bash...even though my other home linux servers use tcsh. I also installed GKrellm and worked on getting postfix to talk to relay through my outbound.mailhop.org account. Found that I had to use
smtp_tls_CAfile=/etc/ssl/certs/Equ....pem instead of
smtp_tls_CApath=/etc/ssl/certs. And, then I messed up resolv.conf (I had installed and tested vpnc, its not quite working right...but its probably a K-State thing than the client....I knew it was working on my other ubuntu systems and I used the same config file, but didn't check if it still worked on those other systems). Then I discovered that my local DNS was kind of confused. Because 'box' was back on the network, but not configured as the master or knowing of my local domain....it was getting things wrong. Using my dyndns domain name is internal and external probably compounded things.
So, that moved up getting DNS configured. Continuing my environment setup, I remembered that I hadn't updated my border routers for IVS without 'box'.....since 'box' has cron jobs to check that I'm my IVS is working....so I went off and did that...and while I was on the computer that I also do my boinc managing from...I worked on getting BOINC running on 'box'.
I opted to use the apt-get install of it, and let it run a system service (instead of out of my local account and the keep it current to the latest stable version...which is newer than the ubuntu one?) Attached to a bunch of projects, discovered new 'box' is much noisier with its CPU running full tilt all the time....though P4-3.2GHz CPUs run hot...I forget what I had now in 'box'....Cele2.2??? Got all the usual projects attached, except Spinhenge...maybe it won't be bad if its not. Not all boxes run all projects that are available, aside from some projects not support Linux. There are differences based the resources of the minion. New 'box' being faster and doing HT, I have it doing more than what old 'box' did.
Now off to do morning stuff and run some errands before diving back into finishing new 'box'.
I think when I return, I'm going to work on dhcp server peering. So that should I ever lose 'box' again, I won't be with out DHCP.....though 'orac' is not the kind of box I hope to ever have to rebuild (another 'lhaven' )
This morning while I was at home waiting for the building owner to show up to see about some noises inside the wall behind kitchen sink/washer&dryer. UPS showed up with a box from TigerDirect.
That should be the off-lease IBM ThinkCenter S51 that I snapped up thinking I'd rebuild 'box' on a new machine.
The condo's quarterly pest control was going to be at 1:30pm today, so he was thinking of setting off some kind of pest control spray bomb in the utility room...which may or may not reach into the wet wall space of my condo. Or consult with the pest control company on what else to try. Later as I was listening closer to the noise, I wondered if it sounded like a feret...because there's a "Lost Ferret" sign out by the mailboxes. Turns out the "Lost Ferret" is from the unit above me.
I popped in to work for a bit, and then returned around 1:30pm for the pest control visit. I arrived to find that FedEx ground had been by and there was a box sitting by my front door. Meanwhile, the building owner said the neighbor upstairs wanted to take a look and see if he can get the ferret out, otherwise the ferret owner would pay to have an exterminator deal with it. There's no openings in the wall that I knew of, but I let him. Pest control guy later showed up to do some spraying.
Well, the box was the pulled/untested power supply that I had snagged off of ebay. All the power supplies that matched the part number online were of this 'untested/as-is' condition...or more than what I had original paid for the computer (and more than what the off-lease computer I just got). Alas, it didn't make 'box' work again. Either I got another dead power supply or there something else wrong with the system that is making the powersupply not turn on. Not have an ATX P/S tester handy, I can't tell if this is the case or not.
Anyways...that eliminates one option for getting 'box' back online.
I'm pretty much leaning towards installing the latest Ubuntu server....since it looks like the main things I'd require on the system are DNS (master), DHCP (wonder about setting up peering), NTP, ddclient x 2, and email relay to my outbound.mailhop.org account, vpnc. The ivs-status-sniff stuff will just go away. And, I'll gradually remove all evidence of it and simplify the configurations on my border routers (been close to running out of nvram on them).
Hmmm, just realized that I never changed the configs on the routers to account for the lack of the internal router 'box' to reach my ReplayTVs for IVS...not just they were (date) confused because they were doing NTP off of 'box'...and first DNS in the search list was 'box'....
Also not sure vpnc is needed now, since it won't be functioning as an internal router anymore. Someday I'll upgrade to a computer where it'll be safe to install a vpn client again. My windows boxes are both pretty dorked in the network config department. The W2K box is completely dorked...when 'lhaven' died...it became pretty usuable because I couldn't get into the configs to change my DNS server. I haven't found the install disk, so risking a repair install hasn't been an option. The other computer is also somewhat messed up, though not as bad.
Both messed up networking are connected to previous attempts to install VPN software (SecureRemote). It was largely flawed because they didn't support users with their own routers doing NAT. Largely because every IANA non-routeable ranges were being used somewhere within the worldwide network of the company, which was all NAT'd behind a single IP in Canada. Made location based (or restricted) services fun to use from work...because they would mistakenly set Canadian preferences or deny access because only US IPs were allowed.
It was particularly bad with Yahoo..which kept bouncing us over to yahoo.ca and then defaulting to only searching Canadian sites.
Anyways....wonder when I'll get cracking on trying to build the new 'box'. The off lease machine came with a 40G drive, but do I use it...or see if I have any other IDE drives around (probably too late to buy one).
Latest Poopli Updaters -- http://lkc.me/poop
|<< <||> >>|
dhcp «hd movie» 10.04lts box «doctor who» «powersource 400» amazon.com appletv prescription woot «tivo premiere» replaytv raid1 freebsd linux «tivo hd» progressive «chicago tardis» tardis dsl «instant streaming» cfengine3 raid cox «amazon prime» zen twitter mdadm ups boinc netflix virtualbox backuppc «watch instantly» «windows 7» «sans digital» lhaven dvd «air purifier» orac tv usb b2evolution cpap «windows xp» ebay ubuntu upgrade tivo eyeglasses