March 2008
Fri 14 Mar 2008
Fri 14 Mar 2008




Thu 13 Mar 2008
Thu 13 Mar 2008
Wed 12 Mar 2008
Wed 12 Mar 2008
3/12/2008 | 11:56:14 AM | ã¿ã¿ã“ã‚ | 008✿玲ç“心ï¼è¶£å‘³ï¼šUFJ最悪ï¼ï¼ï¼ | UFJ最悪ã®ä¸æ‚ªã„ã‚“ã ã‘ã© | ||||
3/12/2008 | 11:56:22 AM | ã¿ã¿ã“ã‚ | 008✿玲ç“心ï¼è¶£å‘³ï¼šUFJ最悪ï¼ï¼ï¼ | 1ã¤è³ªå• | ||||
3/12/2008 | 11:56:38 AM | 008✿玲ç“心ï¼è¶£å‘³ï¼šUFJ最悪ï¼ï¼ï¼ | ã¿ã¿ã“ã‚ | ã¯ã„:$ |
3/12/2008 | 11:57:52 AM | 008✿玲ç“心ï¼è¶£å‘³ï¼šUFJ最悪ï¼ï¼ï¼ | ã¿ã¿ã“ã‚ | ãれã¯ãƒ†ã‚¹ãƒˆï¼Ÿ | ||||
3/12/2008 | 11:58:00 AM | 008✿玲ç“心ï¼è¶£å‘³ï¼šUFJ最悪ï¼ï¼ï¼ | ã¿ã¿ã“ã‚ | ãれã¨ã‚‚å¿…è¦ï¼Ÿ | ||||
3/12/2008 | 11:58:05 AM | ã¿ã¿ã“ã‚ | 008✿玲ç“心ï¼è¶£å‘³ï¼šUFJ最悪ï¼ï¼ï¼ | テスト | ||||
3/12/2008 | 11:58:31 AM | ã¿ã¿ã“ã‚ | 008✿玲ç“心ï¼è¶£å‘³ï¼šUFJ最悪ï¼ï¼ï¼ | ã ã‹ã‚‰åˆ¶é™ã‚ã‚‹ã®ã‹ãªã£ã¦ | ||||
3/12/2008 | 11:58:35 AM | 008✿玲ç“心ï¼è¶£å‘³ï¼šUFJ最悪ï¼ï¼ï¼ | ã¿ã¿ã“ã‚ | 嫌ãŒã‚‰ã›ï¼Ÿã€€:D | ||||
3/12/2008 | 11:58:47 AM | 008✿玲ç“心ï¼è¶£å‘³ï¼šUFJ最悪ï¼ï¼ï¼ | ã¿ã¿ã“ã‚ | èžã„ãŸã“ã¨ãªã„ | ||||
3/12/2008 | 11:58:56 AM | 008✿玲ç“心ï¼è¶£å‘³ï¼šUFJ最悪ï¼ï¼ï¼ | ã¿ã¿ã“ã‚ | 多分誰もやã£ãŸã“ã¨ãªã„ã‹ã‚‰ | ||||
3/12/2008 | 11:58:59 AM | ã¿ã¿ã“ã‚ | 008✿玲ç“心ï¼è¶£å‘³ï¼šUFJ最悪ï¼ï¼ï¼ | アクセンãƒãƒ¥ã‚¢ã®å«ŒãŒã‚‰ã›ï½— | ||||
3/12/2008 | 11:59:05 AM | 008✿玲ç“心ï¼è¶£å‘³ï¼šUFJ最悪ï¼ï¼ï¼ | ã¿ã¿ã“ã‚ | ãªã‚‹ã»ã© |
Mon 10 Mar 2008
One man writes Linux drivers for 235 USB webcams
By Fernando Cassia: Monday, 30 April 2007, 3:40 PM
Sun 9 Mar 2008
Ten good habits to adopt are:
- Make directory trees in a single swipe.
- Change the path; do not move the archive.
- Combine your commands with control operators.
- Quote variables with caution.
- Use escape sequences to manage long input.
- Group your commands together in a list.
- Use
xargs
outside offind
. - Know when
grep
should do the counting — and when it should step aside. - Match certain fields in output, not just lines.
- Stop piping
cat
s.
Make directory trees in a single swipe
Listing 1 illustrates one of the most common bad UNIX habits around: defining directory trees one at a time.
Listing 1. Example of bad habit #1: Defining directory trees individually
~ $ mkdir tmp ~ $ cd tmp ~/tmp $ mkdir a ~/tmp $ cd a ~/tmp/a $ mkdir b ~/tmp/a $ cd b ~/tmp/a/b/ $ mkdir c ~/tmp/a/b/ $ cd c ~/tmp/a/b/c $ |
It is so much quicker to use the -p
option to mkdir
and make all parent directories along with their children in a single command. But even administrators who know about this option are still caught stepping through the subdirectories as they make them on the command line. It is worth your time to conscientiously pick up the good habit:
Listing 2. Example of good habit #1: Defining directory trees with one command
~ $ mkdir -p tmp/a/b/c
|
You can use this option to make entire complex directory trees, which are great to use inside scripts; not just simple hierarchies. For example:
Listing 3. Another example of good habit #1: Defining complex directory trees with one command
~ $ mkdir -p project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}
|
In the past, the only excuse to define directories individually was that your mkdir
implementation did not support this option, but this is no longer true on most systems. IBM, AIX®, mkdir
, GNU mkdir
, and others that conform to the Single UNIX Specification now have this option.
For the few systems that still lack the capability, use the mkdirhier
script (see Resources), which is a wrapper for mkdir
that does the same function:
~ $ mkdirhier project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}
|
Change the path; do not move the archive
Another bad usage pattern is moving a .tar archive file to a certain directory because it happens to be the directory you want to extract it in. You never need to do this. You can unpack any .tar archive file into any directory you like — that is what the -C
option is for. Use the -C
option when unpacking an archive file to specify the directory to unpack it in:
Listing 4. Example of good habit #2: Using option -C to unpack a .tar archive file
~ $ tar xvf -C tmp/a/b/c newarc.tar.gz
|
Making a habit of using -C
is preferable to moving the archive file to where you want to unpack it, changing to that directory, and only then extracting its contents — especially if the archive file belongs somewhere else.
![]() |
|
Combine your commands with control operators
You probably already know that in most shells, you can combine commands on a single command line by placing a semicolon (;) between them. The semicolon is a shell control operator, and while it is useful for stringing together multiple discrete commands on a single command line, it does not work for everything. For example, suppose you use a semicolon to combine two commands in which the proper execution of the second command depends entirely upon the successful completion of the first. If the first command does not exit as you expected, the second command still runs — and fails. Instead, use more appropriate control operators (some are described in this article). As long as your shell supports them, they are worth getting into the habit of using them.
Run a command only if another command returns a zero exit status
Use the &&
control operator to combine two commands so that the second is run only if the first command returns a zero exit status. In other words, if the first command runs successfully, the second command runs. If the first command fails, the second command does not run at all. For example:
Listing 5. Example of good habit #3: Combining commands with control operators
~ $ cd tmp/a/b/c && tar xvf ~/archive.tar
|
In this example, the contents of the archive are extracted into the ~/tmp/a/b/c directory unless that directory does not exist. If the directory does not exist, the tar
command does not run, so nothing is extracted.
Run a command only if another command returns a non-zero exit status
Similarly, the ||
control operator separates two commands and runs the second command only if the first command returns a non-zero exit status. In other words, if the first command is successful, the second command does not run. If the first command fails, the second command does run. This operator is often used when testing for whether a given directory exists and, if not, it creates one:
Listing 6. Another example of good habit #3: Combining commands with control operators
~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c
|
You can also combine the control operators described in this section. Each works on the last command run:
Listing 7. A combined example of good habit #3: Combining commands with control operators
~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c && tar xvf -C tmp/a/b/c ~/archive.tar
|
![]() |
|
Sun 9 Mar 2008
Ten good habits to adopt are:
- Make directory trees in a single swipe.
- Change the path; do not move the archive.
- Combine your commands with control operators.
- Quote variables with caution.
- Use escape sequences to manage long input.
- Group your commands together in a list.
- Use
xargs
outside offind
. - Know when
grep
should do the counting — and when it should step aside. - Match certain fields in output, not just lines.
- Stop piping
cat
s.
Make directory trees in a single swipe
Listing 1 illustrates one of the most common bad UNIX habits around: defining directory trees one at a time.
Listing 1. Example of bad habit #1: Defining directory trees individually
~ $ mkdir tmp ~ $ cd tmp ~/tmp $ mkdir a ~/tmp $ cd a ~/tmp/a $ mkdir b ~/tmp/a $ cd b ~/tmp/a/b/ $ mkdir c ~/tmp/a/b/ $ cd c ~/tmp/a/b/c $ |
It is so much quicker to use the -p
option to mkdir
and make all parent directories along with their children in a single command. But even administrators who know about this option are still caught stepping through the subdirectories as they make them on the command line. It is worth your time to conscientiously pick up the good habit:
Listing 2. Example of good habit #1: Defining directory trees with one command
~ $ mkdir -p tmp/a/b/c
|
You can use this option to make entire complex directory trees, which are great to use inside scripts; not just simple hierarchies. For example:
Listing 3. Another example of good habit #1: Defining complex directory trees with one command
~ $ mkdir -p project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}
|
In the past, the only excuse to define directories individually was that your mkdir
implementation did not support this option, but this is no longer true on most systems. IBM, AIX®, mkdir
, GNU mkdir
, and others that conform to the Single UNIX Specification now have this option.
For the few systems that still lack the capability, use the mkdirhier
script (see Resources), which is a wrapper for mkdir
that does the same function:
~ $ mkdirhier project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}
|
Change the path; do not move the archive
Another bad usage pattern is moving a .tar archive file to a certain directory because it happens to be the directory you want to extract it in. You never need to do this. You can unpack any .tar archive file into any directory you like — that is what the -C
option is for. Use the -C
option when unpacking an archive file to specify the directory to unpack it in:
Listing 4. Example of good habit #2: Using option -C to unpack a .tar archive file
~ $ tar xvf -C tmp/a/b/c newarc.tar.gz
|
Making a habit of using -C
is preferable to moving the archive file to where you want to unpack it, changing to that directory, and only then extracting its contents — especially if the archive file belongs somewhere else.
![]() |
|
Combine your commands with control operators
You probably already know that in most shells, you can combine commands on a single command line by placing a semicolon (;) between them. The semicolon is a shell control operator, and while it is useful for stringing together multiple discrete commands on a single command line, it does not work for everything. For example, suppose you use a semicolon to combine two commands in which the proper execution of the second command depends entirely upon the successful completion of the first. If the first command does not exit as you expected, the second command still runs — and fails. Instead, use more appropriate control operators (some are described in this article). As long as your shell supports them, they are worth getting into the habit of using them.
Run a command only if another command returns a zero exit status
Use the &&
control operator to combine two commands so that the second is run only if the first command returns a zero exit status. In other words, if the first command runs successfully, the second command runs. If the first command fails, the second command does not run at all. For example:
Listing 5. Example of good habit #3: Combining commands with control operators
~ $ cd tmp/a/b/c && tar xvf ~/archive.tar
|
In this example, the contents of the archive are extracted into the ~/tmp/a/b/c directory unless that directory does not exist. If the directory does not exist, the tar
command does not run, so nothing is extracted.
Run a command only if another command returns a non-zero exit status
Similarly, the ||
control operator separates two commands and runs the second command only if the first command returns a non-zero exit status. In other words, if the first command is successful, the second command does not run. If the first command fails, the second command does run. This operator is often used when testing for whether a given directory exists and, if not, it creates one:
Listing 6. Another example of good habit #3: Combining commands with control operators
~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c
|
You can also combine the control operators described in this section. Each works on the last command run:
Listing 7. A combined example of good habit #3: Combining commands with control operators
~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c && tar xvf -C tmp/a/b/c ~/archive.tar
|
![]() |
|
Sun 9 Mar 2008
Nintendo Wii and Linux
Nintendo Wii has been a bit tougher to crack than hacker-friendly hardware like the PS3, which even has a Sony-approved Linux distro. But now the Wii hacking community has figured out how to run homebrew applications on Nintendo’s latest console, and that includes a rather unpolished “proof of concept†version of Linux that can run on the Wii. Few days ago this news came from the GameCube Linux Wiki:
24 Feb 2008: Long time, no see Although we haven’t posted any news in the last 2 years, we have silently continued our work keeping the kernel patches up to date. With the latest 2.6.24 release we have added support for the USB Gecko adapter as a console and terminal, so you can now logon into your gc-linux distro using minicom or HyperTerminal (TM). And last but not least, we have finally run natively Linux on the Nintendo Wii through Team Tweezers’ twilight-hack. We have released a small usbgecko-enabled Proof of Concept mini-distro to prove it. Did I say have fun?
![]()
Now, keep in mind, the hacking process is not simple. You need an SD card, SD card adapter for the Wii, a copy of Zelda: Twilight Princess, the ability to follow complex instructions, infinite patience, and the willingness to completely muck up your video game console if things go wrong.
Wii Technical Specification:
- CPU (Central Processing Unit): IBM ‘Broadway’ 729MHz
-
Internal Storage: 512MB Flash Memory
- USB 2.0: 2 Ports
- System Memory: 256MB
- Memory Expansion: 2 SD Memory
- GPU (Graphics Processing Unit): ATI ‘Hollywood’
- Optical Disc Drive: 8cm GameCube / 12cm Wii (DVD discs)
- Supported Resolution: up to 480p
- 12 cm Disc Capacity: 4.7GB (single) / 8.5GB (dual)
- Wii Controller Ports: Wireless (4 maximum)
- GameCube Controller Ports: 4 Ports
- Internet Connectivity: WiFi 802.11b/g
- Disc Compatibility: GameCube
- GameCube Memory Expansion: 2 Ports
Links for running Linux on Wii:
- Welcome to WiiLi
- Wii Linux Project
- Wii homebrew