If it’s 12AM and your Nintendo WII power supply goes on the fritz and you can’t locate one at your local Wal-Mart and you’re jonsin’ to play a new game have no fear! I too found myself in this situation recently. Like most computer dudes I have a plethora of computer parts lying around in my parts closet. It’s really not all that uncommon to have a power supply or two lurking in the parts bin. In this document I’ll teach you how to juice up your Wii and get back to gaming with simple items almost every geek has. Amazingly the Nintendo Wii’s power brick is rated at 3.0A (Amps) and normal PC power supplies rate at least 5-7A (Amps) on the 12 volt (yellow-wire) side.
There are some other articles online outlining the procedures to replace a small soldered-in fuse inside the power brick. We didn’t have a fuse or the time to try to remove the strange shaped screws holding the brick together.
Disclaimer: We do not claim that the below will not harm your Nintendo Wii. We have tested it and everything appears to work but we cannot speak to the “cleanliness” of the power delivered by the power supply used nor can we assure that any other issues may be caused. Please use this document at your own risk.
* Wire strippers (or equivalent)
* Wire cutters
* A small shiny (non-coated) paper clip
* Electrical tape
* Optional: Soldering Iron w/ Solder
* A small Molex to SATA Adapter (these come in almost every retail hard drive box)
* A small or old PC power supply (ATX is what we’re using here)
Steps to Power
1. Since you’re not going to use your old power brick anymore, cut off the end which plugs in to your Wii closest to the brick as possible.
2. Strip the grey sheathing from the wire. This will reveal a white wire surrounded by another wire.
3. Take the wire around the outside and twist it together to form one wire.
4. Strip the white wire. Be careful to leave enough insulator between the white wire and the outside wires we previously twisted.
5. Locate your Molex to SATA converter. Cut the black and yellow wires closest to the SATA connector.
6. Strip the black and yellow wires.
7. Connect Yellow to White (the inside wire)
8. Connect Black to the outside wire we previously twisted.
9. Use electrical tape to make the connections or optionally solder the connections together. Use plenty of electrical tape or heat shrink tubing to secure the connections and insulate them.
10. Plug in your molex connector to the power supply.
At this time your Nintendo Wii is connected to the power supply.
11. Unbend your silver paper clip and insert one end in to the ATX connector’s green wire. Connect the other end to the black ground wire next to the green wire. This sets the ATX power supply to be on at all times.
12. Plug in your ATX power supply to wall power.
13. Plug in the newly-frankenstiened power adapter to your Nintendo Wii
13. Power on your Nintendo Wii
Polarity for the Nintendo adapter is printed on the bottom of the brick but does not outline which wire (the outside or inside) is positive or negative. The outside wire is DC negative (-) and the inside white wire is DC positive (+).
To power a Nintendo Wii with a PC power supply is very easy and certainly feasible. I’m not sure the long term affects of using this solution but it does make complete sense to use a PC power supply because that is, essentially, what a Nintendo Wii is – a computer. To this day the solution is still working and I haven’t found a need to buy another power brick yet. This solution/fix was a bit overkill but at the time it made sense to get the gaming system back online.
BIND, the Berkley Internet Name Domain service, provides forward (authoritative) and recursive (non-authoritative) DNS lookups for the majority of the internet as we know it. A security vulnerability outlined here shows that a specially crafted packet can cause the DNS daemon to stop functioning. It is imperative that all “master” DNS servers get updated immediately. More general information on BIND can be found on their site here.
CVE Information: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2009-0696
RHEL Bug Information: https://bugzilla.redhat.com/show_bug.cgi?id=514292
The NVD at NIST reports the following overview of this issue:
The dns_db_findrdataset function in db.c in named in ISC BIND 9.4 before 9.4.3-P3, 9.5 before 9.5.1-P3, and 9.6 before 9.6.1-P1, when configured as a master server, allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an ANY record in the prerequisite section of a crafted dynamic update message, as exploited in the wild in July 2009.
Updating BIND on RHEL/CentOS (4/5)
Updated packages are available to assure you are running the latest release.
Use this command to update bind on yum-based systems:
# yum –y update bind
Updating BIND on Debian / Ubuntu
<font size="1"> # apt-get update <br /> # apt-get upgrade <br /> # /etc/init.d/bind9 restart</font>
The RioRey solution is a DDoS protection device not widely used or heard of … yet. First of all let me assure you that I am in no way associated with the RioRey company and my focus is to give an honest and unbiased opinion of their product offerings.
The RioRey device is a rack-mountable device with one copper management port and two copper or fiber (Multimode SX/LC or Singlemode LX/LC) ports. Their products tier in the volume of packets per second they are able to mitigate under a real DDoS attack. They range from 150K packets per second (PPS) to their newest eight rack unit 16M packets per second model. The model I have had the most experience with is their entry-level 150K PPS model. This will be the model I talk about in the remainder of this article.
Using the device is a breeze. Installation is as simple as installing it in line to the closest “edge” of your connection. For most companies and hosting providers this would be at their handoff from their bandwidth provider (e.g. Cogent, ATT) The device can be purchased (at no additional cost) with the ability to fail to bypass. This means that if the device has a hardware failure the device will act as a straight-through cable and continue to pass traffic. In testing this device did not even trip external monitoring when simulating failure.
The device comes with a very primitive web interface which is used for setting up low-level functions like syslog reporting and IP addressing of the management interface. The device comes with a pre-configured IP address to access this web console for first installation. The device also comes with their management software called “rView” This software allows you to view the status of the device, perform reports, get real-time insight into current attacks and customize how the device behaves under attack. The device also has the ability to send SNMP traps, log to syslog and email when an attack is detected.
Real World Experience
I’ve personally and (un)fortunately had this device work for me. This device was blocking a 1.3GBit/sec UDP flood and was currently only linked at 100mbit. All sites/devices/services behind the RioRey were still responsive. The sites did notice a small uptick in response time but no dropped packets or requests. The device performed as advertised and their patented Micro Behavioral Analysis (MBA) algorithms performed beautifully. Within 60 seconds the attack was mitigated and “polluted” traffic was removed. The graph on the right illustrates how fast the traffic was blocked. Notice the blue line grow and then almost instantly disappears. This blue line is the “after filtering” traffic (the traffic passed to the LAN interface.) The attack traffic was almost instantly mitigated- all without human intervention.
This device is a very valuable tool. It’s kind of like a fire extinguisher, when you need it you really need it; when you don’t need it you never really even know or care to know that it’s there. Was it worth the investment? It’s hard to gauge these things after an attack is mitigated. If we didn’t have the device under attacks it would be much harder to identify the attacker and the victim and would cause more downtime simply analyzing the traffic to find the source(s).
I believe the device is well worth it. It’s entry-level pricing is second to none (when compared to other solutions) and it allows a level of protection that most never thought possible for the price. To obtain more information and pricing please visit The RioRey Site.
If you have any questions about the device and would like to contact me for more information please post a comment or email Adam [at] Admo.net for more information!
Symbolic links allow an administrator to point a link (file or directory) to another real location.
How do I create a symbolic link?
# ln –s [target file/directory] /link/location/to/file/or/directory
For example, you wish to link /etc/httpd/conf to point to the real location of /usr/local/apache/conf
The command would look like this:
# ln –s /usr/local/apache/conf /etc/httpd/conf
Assure that the destination for your link (in our example this would be /usr/local/apache/conf) does not already exist.
IOPS (I/O’s per Second,
or iostat "tps")
Data Transfer Rate
Minimum Number of Disk Drives to Support Workload
Random I/O (10k RPM)
n = (%R + f (%W))(tps)/125
Random I/O (15k RPM)
n = (%R + f (%W))(tps)/150
n = (MB/sec)/50
%R = the percentage of disk I/O’s that are reads.
%W= the percentage of disk I/O’s that are writes.
f = 1 for ordinary disks, 2 for mirrored disks, 4 for Raid 5 disks.
Assumes data is distributed evenly across all disk drives.
Using the above formula, here’s the minimum number of disks required to support a random I/O workload, at 1000 IOPS, 80% read, 20% write on 10K RPM disk drives.
Ordinary disks: (0.8 + 1*0.2)(1000 IOPS)/(125 IOPS/disk) = 8
Mirrored disks: (0.8 + 2*0.2)(1000 IOPS)/(125 IOPS/disk) = 10
Raid 5 disks: (0.8 + 4*0.2)(1000 IOPS)/(125 IOPS/disk) = 13
Full Article Here
From Dell’s Support Site:
To start Server Administrator, perform the following steps:
- Click the Start button and point to Settings® Control Panel® Administrative Tools® Services.
The Services window appears.
- Right-click the Secure Port Server icon.
- Click Start.
To stop Server Administrator, perform the following steps:
- Click the Start button and point to Settings® Control Panel® Administrative Tools® Services. The Services window appears.
- Right-click the Secure Port Server icon.
- Click Stop.
Here is a small(ish) list of Linux CLI tips and tricks I have learned and researched over the years. This list is by no means completely comprehensive but contains a list of some of the tricks I use on an everyday basis. Living your life “in the shell” can be very cumbersome if you aren’t using the tricks outlined below. Good luck and happy Linuxing.
I will say this: Do not give in and use all the tricks all the time if you are just starting with Linux. It’s always best (in my opinion) to learn the ropes and background to everything before using the GUI or any related tricks. I believe this is true with almost any learning process – technology-based or not.
Command Line File Name Completion
Tired of typing the whole path to a single command? Some commands can be very large and cumbersome. Try “tabbing it out”.
Try for example: where<tab>
The above should return whereis. If you have more than one binary in your path that contains the word where you may not get a result. In this case hit tab again and you’ll be presented with all options.
Print Working Directory (pwd)
The pwd command is useful to tell you what directory you are currently in. Depending on your shell configuration, you will be presented with your full working directory in the title of your shell program. For instance, I use putty and it always shows my Current Working Directory (CWD).
Forget what the last few commands you completed were? Want to diagnose a system and you have no idea what the person before you executed? Try the “history” command in Linux.
Type “history”. This provides a list of all recently entered commands and can be very large. If you type “history 10” it works much like the tail command and shows the last 10 commands in history.
Type “history –c” to clear your command history.
Tons of information from the command you just executed? Redirect the output to a file or another program.
|> – Output Redirection
||>> – Append to EOF (end of file)
|1> – Redirect STDOUT (Standard Out)
||< – Input Redirection
|2> – Redirect STDERR (Standard Error)
|&> – Redirect all
# echo “foo” > bar (this example will echo the text “foo” to the file called “bar”)
# echo “foo2” >> bar (this example will echo the text “foo2” to the end of the file “bar”)
# wc –l < bar (this example will do a line count on the file bar)
Typically commands read, by default from STDIN. For instance I could also run wc like this:
# wc -l bar
I would still obtain the same results as explicitly telling the CLI to use STDIN (<).
Using aliases is another way to make entering common commands easier. Think of an alias as a simple shortcut to a longer command. Let’s say you want to remove a directory and you’re tired of always typing “rm –rf <directory”. You can make an alias by typing “alias rmdir=’rm –rf’. Now you can type “rmdir <directory>” on the CLI and achieve the same result.
A symbolic link is simply a pointer to another file/directory. To make a shortcut to a program shorter or as a link inside your home directory use a command like this:
# ln –s /usr/local/program/bin/program ~/program
– or to link an entire directory –
# ln –s /usr/local/program ~/program
Symbolic links appear when performing an ls –lt like this:
apropos Search Whatis Database
Ever wanted to find a command but never knew the name? Do you know what the command does or a description but can’t put your finger on it? Use the command apropos to search the whatis database.
Just type apropos “string to search for”
Whereis – Find a binary or man page
Ever needed to find the location of a binary easily? Try “whereis”. Simply type whereis “binary” and you will be presented with a location to the binary and/or manpage for the given binary.
There are a ton of other shortcuts I am missing but this is just a small list. Have a great day!
I started to receive a message on my new Vista box in Acronis True Image Home that looks like this:
Information 12/15/2008 8:07:49 AM Locking partition C:…
Error 12/15/2008 8:10:00 AM Operation with partition "2-0" was terminated.
Run list corrupted (0x7001C)
Tag = 0x89D94B01B483E221
To rectify this issue just run a "CHKDSK C: /R" which should clean up a few NTFS attributes. This usually will happen if you hard-cycle your system for some reason.
Some of the new 1TB Seagate drives come shipped with a 1.5GBps jumper enabled by default. The ST31000340AS drive has a jumper on the back that needs to be removed to enable 3.0GBps transfer. This "jumper secret" may also apply to Seagate drives so make sure to double check your existing and new Seagate drives for this limitation.
Directly from Seagate’s manual:
Serial ATA drives are designed for easy installation. It is usually not necessary to set any jumpers on the drive
for proper operation; however, if you connect the drive and receive a “drive not detected” error, your SATAequipped
motherboard or host adapter may use a chipset that does not support SATA speed autonegotiation. If
you have a motherboard or host adapter that does not support autonegotiation:
•Install a jumper as shown in Figure 3 below to limit the data transfer rate to 1.5 Gbits per second (and leave the drive connected to the SATA-equipped motherboard or host adapter that doesn’t support autonegotiation) or
•Install a SATA host adapter that supports autonegotiation, leave the drive jumper block set to “Normal operation” (see Figure 3 below), and connect the drive to that adapter. This option has the benefit of not limiting the drive to a 1.5 Gbits/sec transfer rate.
The only issue is that the jumper comes pre-installed on these drives in particular.
Good luck and happy hard disking!
I’ve met and spoke with quite a few persons who believe that RAID is the answer to all of their data-safety needs. There is only one thing I can say about relying solely on RAID: “It’s a horrible idea!”. RAID is a good supplemental protection mechanism in your entire data integrity plan but it is not THE answer.
- RAID is usually susceptible to double-disk RAID faults. While this may not sound like a normal or even conceivable possibility it is a very real issue that I have personally experienced. RAID-6 offers some higher levels of protection to this problem. Most new 9600 series 3Ware controllers (and most newer controllers) offer RAID-6 capabilities. Choose a RAID-6 able card and, if possible, always run a BBU (Battery Backup Unit).
- RAID will never protect against file corruption or viruses.
- RAID can’t protect against human error. We’re all human, we all make mistakes. If you just hit the delete key on an entire directory of your company’s data then you can probably hit the delete key on your job as well. This is why backups, along with RAID, is the best data integrity solution.
- RAID will only protect you if you are proactive. Some lower quality RAID controllers do not send email alerts and do not properly alert you of an issue. These controllers require special attention. The more user interaction is needed the less likely you will notice a fault. Having a hot spare or spare disks available for swapping is always a good idea.
- RAID will not facilitate off-site and disaster recovery scenarios. There are some utilities out there that provide block-level replication.
In summary, the best data integrity plan is to use RAID to supplement your plan. Don’t rely on RAID as your sole backup/data security mechanism. I personally recommend using RAID-6 with a block-level backup of all data to an off-site location. Using software like R1Soft’s CDP will allow for full block-level backups and file-level and bare-metal restores. Remember to always double check your data integrity plan and never be satisfied with your solution! I personally hate loosing data. With drives as cheap as they are today, why aren’t you backing up offsite?