One of thousands of such nights dealing with problems such as this.Current situation: I’m attempting to set up a custom box that will serve as a general project server. I want wireless working on it so that I can stash it wherever and not worry about it rumbling around, someone spilling something on it, people tripping over it, or any other mishap.A happy server is a hidden server.This is the same problem box where the raid card wasn’t happy.
A couple of years ago, I put together a custom system for myself consisting of an ASUS A8V Deluxe mainboard, a brand new AMD64 processor, a large aluminum server case, a Highpoint RR1820A SATA RAID controller capable of supporting 8 drives, a pair of IDE boot disks in their own drive coolers (to be mirrored), and a bunch of supporting fans with a separate fan controller.Not a bad configuration, I thought.I assembled all of the components and made sure everything was working…. This didn’t accomplish anything, but did make me feel a little clever until I booted the system again to discover that it still wouldn’t work with all of those SATA drives.I’ll now post some of the configuration details in the hopes that if someone else is having the same issue as I am, that they will at least be able to know that they are not alone in their plight.*Name : Ian Gorrie*Country : United States[Product Information]*Product Type : Motherboard*Product Model : A8V Deluxe[Motherboard Specification]*Motherboard Revision : A8V DELUXE*Motherboard BIOS Revision : 1018 BETA 1[CPU Specification]*CPU Vendor : AMD*CPU Type : Socket939*CPU Speed : 3800+[Memory Specification]*Memory Capacity : 4G[Problem Description]None of these other details matter as system will boot and operate without issue if my RAID card is not seated.When booting my ASUS A8V Deluxe mainboard system with a Highpoint rr1820a SARA RAID controller in a PCI slot, I have the following conflict.The system freezes upon entering bios configuration or when system boot should occur if the delete key has not been pressed.Interestingly enough, my system booted without issue before building a 1Tbyte array comprising of 6 200G SATA disks in RAID 5 configuration.
A bit of scratching my head this morning over why a microdrive wasn’t detected as a valid boot device on my PPC Apple hardware.As it turns out, x86 macs can boot off of USB2 without difficulty.
That is, of course, until they just break.For instance my G5 tower, after some quality time in cold storage, wouldn’t detect it’s wireless card. The bluetooth abilities, which are located on the same piece of hardware, were functional. I figured that something non-hardware was the problem.
The few things are keeping me from being a solutions provider of Apple computer products to business.First is Apple’s inability to inform business channels of their release schedule. I understand that they want to scam the average consumer and maximize consumption independent of a release schedule. For business customers, however, this just isn’t viable.
I was mentioned as a Technical Editor in Curtis Preston’s new edition of Backup and Recovery. Thanks for the free book, Curtis!
Jeremy Schoemaker asked me to write up a little something regarding the recent string of SEO web defacements for a non-technical audience which he posted in his blog.The SEO industry is very focused on being SEOs.Like many professionals, many attempt to avoid time consuming activities that are not core to their business…. This is a perennial theme of information security writings and I myself have touched on itWeb defacements are nothing new, but the media attention to SEO superstars is notable and makes their online presence an attractive high-value target. The recent mass defacement of SEO wordpress blogs that was launched from a technical adversary using tor is an example of what has become a not uncommon occurrence.What can SEOs, and bloggers in general, do to lessen the risk of public embarrassment from defacements, hacktivism, and information leakage?… (For example, the bugfix for Wordpress v2.0.6 addressed a correction for those webservers that had left register_globals set to “on.” Not recommended in the first place.)Hardening the web services themselves with security modules.Use of a NIDS or HIDS that will actively block or alert upon detection of questionable behaviors.All of these methods involves time and resources that could best be applied to doing what they do best, in this case, being a SEO.
This was a random thing I encountered, so it bothered me until I figured out why I could not remember the password set for my System Keychain.The reason was that I didn’t set one, and that it is randomly generated…. To view them, you need to have access to the keychain.What is a geek to do?
up2date has rollback capability and is already installed on all RHEL [RedHat Enterprise Linux] servers All that would be required to centrally manage a RHEL environment would be to push out an updated config file for up2date and point it to a central repository.Both yum and up2date are just front-ends for rpm management and operate with all the same mechanisms.
…There may be some yum client options available that up2date does not have, but I have not been able to find any examples.Other matters:Repository can be managed with such tools as:- Current: http://current.tigris.org/ This can manage yum, up2date, and apt archives and allows granular control and automation.- Repository setup examples for a variety of methods:http://www.xades.com/proj/fedora_repos.htmlhttp://dag.wieers.com/home-made/apt/FAQ.phpI believe that the best option at this point would be to: – make a repository for all supported platformso make groups for different linux server profiles§ oracle§ webservers§ othero automate updates to linux§ establish rpm testing/certification environment§ have all clients check for updates in a DHL tested repository for regular updates· cron “up2date –u” on a weekly/daily/monthly/quarterly basis§ update repositories with tested updates for each server group.- Configure stock RHEL installations to update from internal sourceso make an rpm of a custom up2date config for RHEL 3 and 4- Document process for rpm rollback for operations in case of update QA failure- Get buy-in from operations and enterprise security management on the update and QA process to be performed in regularly scheduled maintenance windows.