Thursday, November 16, 2006

Ubuntu2

https://help.ubuntu.com/6.10/ubuntu/installation-guide/amd64/index.html
5.10
6.06 LTS
6.10
Community Docs

Ubuntu Installation Guide
Copyright © 2004, 2005, 2006 the Debian Installer team

Copyright © 2004, 2005, 2006 Canonical Ltd.

Legal Notice
Abstract

This document contains installation instructions for the Ubuntu 6.10 system (codename “‘Edgy Eft’”), for the AMD64 (“amd64”) architecture. It also contains pointers to more information and information on how to make the most of your new Ubuntu system.



--------------------------------------------------------------------------------

Table of Contents

Installing Ubuntu 6.10 “Edgy Eft” For amd64
1. Welcome to Ubuntu
What is Ubuntu?
What is Debian?
What is GNU/Linux?
Getting Ubuntu
Getting the Newest Version of This Document
Organization of This Document
About Copyrights and Software Licenses
2. System Requirements
Supported Hardware
Installation Media
Peripherals and Other Hardware
Purchasing Hardware Specifically for GNU/Linux
Memory and Disk Space Requirements
Network Connectivity Hardware
3. Before Installing Ubuntu
Overview of the Installation Process
Back Up Your Existing Data!
Information You Will Need
Meeting Minimum Hardware Requirements
Pre-Partitioning for Multi-Boot Systems
Pre-Installation Hardware and Operating System Setup
4. Obtaining System Installation Media
Official Ubuntu CD-ROMs
Downloading Files from Ubuntu Mirrors
Preparing Files for USB Memory Stick Booting
Preparing Files for Hard Disk Booting
Preparing Files for TFTP Net Booting
Automatic Installation
5. Booting the Installation System
Boot Parameters
Troubleshooting the Installation Process
6. Using the Ubuntu Installer
How the Installer Works
Components Introduction
Using Individual Components
7. Booting Into Your New Ubuntu System
The Moment of Truth
Mounting encrypted volumes
Log In
8. Next Steps and Where to Go From Here
If You Are New to Unix
Orienting Yourself to Ubuntu
Further Reading and Information
Compiling a New Kernel
Recovering a Broken System
A. Installation Howto
Booting the installer
Installation
And finally..
B. Automating the installation using preseeding
Introduction
Using preseeding
Creating a preconfiguration file
Contents of the preconfiguration file
Advanced options
C. Partitioning for Ubuntu
Deciding on Ubuntu Partitions and Sizes
The Directory Tree
Recommended Partitioning Scheme
Device Names in Linux
Ubuntu Partitioning Programs
D. Random Bits
Linux Devices
Disk Space Needed for Tasks
Disk Space Needed
Installing Ubuntu from a Unix/Linux System
E. Administrivia
About This Document
Contributing to This Document
Major Contributions
Trademark Acknowledgement
F. GNU General Public License
List of Tables

3.1. Hardware Information Needed for an Install
3.2. Recommended Minimum System Requirements

--------------------------------------------------------------------------------

Installing Ubuntu 6.10 “Edgy Eft” For amd64

Ruby

http://users.piuha.net/martti/comp/ubuntu/install.html
My Ubuntu Installation
Last updated $Date: 2006-10-28 16:56:56 $

Martti Kuparinen

http://www.iki.fi/kuparine/comp/ubuntu/install.html

Abstract
This is how I installed and configured my PC running Ubuntu 6.06.1 LTS. With this setup I was able remove Windows XP partition from my PC. The few programs which require a real Windows (e.g. program to update Topfield 5100 PVR's firmware can't be run with Wine) are executed inside VMware.


--------------------------------------------------------------------------------

[ Please note that this page is also available in Finnish ]

[ See also My Ubuntu Server Installation with VMware Server ]


--------------------------------------------------------------------------------

Table of Contents
1. Introduction
2. Initial install
3. Adding more software repositories
4. Installing applications
5. Installing and configuring SSH server
6. Configuring X
7. Installing VMware Workstation
8. Installing VMware Server
9. Installing VMware Player
10. DMA settings
11. Configuring firewall
12. Useful links

--------------------------------------------------------------------------------

1. Introduction
This document and the installation helper script applies to Ubuntu 6.06.1 LTS (also known as Dapper Drake). The script also works in the newer Ubuntu 6.10 (Edgy Eft).

2. Initial install
Start by fetching the installation CD image from the Ubuntu download page. Personally I want to use the text-based installation so I used the "Alternate install CD" image. Make sure the MD5 checksum matches with the published value before burning the ISO file or the installation may fail. Reboot with the new installation CD and follow the instructions to install Ubuntu.

Before installing think few minutes how to divide the hard disk into multiple filesystems. In my opinion it's important to have a separate filesystem for /home so it's even possible to reinstall the whole system without moving your personal data to some temporary location before reinstall. I have two identical 250 GB SATA disks. See this page how I configured RAID-1 to have some protection agaist disk failures.

Most the following steps can be performed automatically by saving this install.sh script on your Desktop and running it inside a terminal (Applications > Accessories > Terminal). It is safe to run the script multiple times if you need to abort it at some point.

# sh ~/Desktop/install.sh

Currently the install.sh script does not install and/or configure the following applications so these must be done manually by following this document:

applications using Wine
firewall
VMware Workstation
VMware Server
3. Adding more software repositories
Login to the newly installed Ubuntu system and select Applications > Accessories > Terminal. Modify /etc/apt/sources.list and update your newly installed system. With these settings you have more applications available for download and install. Replace fi with your country code (fi = Finland, se = Sweden, ...) in the following example to access the closest national mirror.

# sudo gedit /etc/apt/sources.list

deb http://fi.archive.ubuntu.com/ubuntu dapper main restricted
deb-src http://fi.archive.ubuntu.com/ubuntu dapper main restricted

## MAJOR BUG FIX UPDATES produced after the final release
deb http://fi.archive.ubuntu.com/ubuntu dapper-updates main restricted
deb-src http://fi.archive.ubuntu.com/ubuntu dapper-updates main restricted

## UBUNTU SECURITY UPDATES
deb http://fi.archive.ubuntu.com/ubuntu dapper-security main restricted
deb-src http://fi.archive.ubuntu.com/ubuntu dapper-security main restricted

## UNIVERSE AND MULTIVERSE REPOSITORY
deb http://fi.archive.ubuntu.com/ubuntu dapper universe multiverse
deb http://fi.archive.ubuntu.com/ubuntu dapper-security universe multiverse
deb-src http://fi.archive.ubuntu.com/ubuntu dapper universe multiverse
deb-src http://fi.archive.ubuntu.com/ubuntu dapper-security universe multiverse

## BACKPORTS REPOSITORY
deb http://fi.archive.ubuntu.com/ubuntu dapper-backports main restricted
deb http://fi.archive.ubuntu.com/ubuntu dapper-backports universe multiverse
deb-src http://fi.archive.ubuntu.com/ubuntu dapper-backports main restricted
deb-src http://fi.archive.ubuntu.com/ubuntu dapper-backports universe multiverse

## dapper-commercial by Canonical
deb http://archive.canonical.com/ubuntu dapper-commercial main

## WINE
deb http://wine.budgetdedicated.com/apt dapper main
deb-src http://wine.budgetdedicated.com/apt dapper main

## Finnish spelling checker for OpenOffice.org
deb http://www.lemi.fi/voikko/ubuntu dapper/
deb-src http://www.lemi.fi/voikko/ubuntu dapper/

Now launch System > Administration > Synaptic Package Manager. Type your password if prompted. Press the Reload button. You will see a warning about missing repositories, this okay during the first time. Press Mark All Upgrades and press Apply if it's enabled. You should now have the latest version of all packages. If the Apply button is not enabled it means you have nothing to upgrade, in other words you already have the latest versions installed.

4. Installing applications
Next install the following programs. The following commands should be executed on a terminal window (Applications > Accessories > Terminal).

## Some public keys
# cd /tmp
# wget http://www.lemi.fi/voikko/archive-key-1.asc
# sudo apt-key add archive-key-1.asc

## Language support (fi = Finnish, se = Swedish, ...)
# sudo apt-get install language-pack-fi language-support-fi
# sudo apt-get install language-pack-gnome-fi

## Finnish spelling checker for OpenOffice.org
# sudo apt-get install openoffice.org-voikko

## Flash
# sudo apt-get install flashplugin-nonfree
# sudo /usr/sbin/update-flashplugin
# cd /tmp
# wget http://www.adobe.com/go/fp9_update_b1_installer_linuxplugin
# tar xzf FP9_plugin_beta_*.tar.gz
# sudo cp /tmp/flash-player-plugin-9.0.*/libflashplayer.so /usr/lib/flashplugin-nonfree/libflashplayer.so

## RealPlayer
# sudo apt-get install realplay

## Acroread
# sudo apt-get install acroread
# sudo apt-get install mozilla-acroread
# sudo apt-get install acroread-plugins

## Java
# sudo apt-get install sun-java5-jre sun-java5-fonts sun-java5-plugin
# sudo update-alternatives --set java /usr/lib/jvm/java-1.5.0-sun/jre/bin/java

## Multimedia Codecs
# cd /tmp
# wget http://www.debian-multimedia.org/pool/main/w/w32codecs/w32codecs_20060611-0.0_i386.deb
# sudo dpkg -i w32codecs_20060611-0.0_i386.deb
#
# sudo apt-get install gstreamer0.10-plugins-base
# sudo apt-get install gstreamer0.10-plugins-good
# sudo apt-get install gstreamer0.10-plugins-ugly
# sudo apt-get install gstreamer0.10-plugins-ugly-multiverse
# sudo apt-get install gstreamer0.10-plugins-bad
# sudo apt-get install gstreamer0.10-plugins-bad-multiverse
# sudo apt-get install gstreamer0.10-pitfdll
# sudo apt-get install gstreamer0.10-gl
# sudo apt-get install gstreamer0.10-ffmpeg
# sudo apt-get install vorbis-tools
# sudo apt-get install lame
# sudo apt-get install sox
# sudo apt-get install ffmpeg
# sudo apt-get install mjpegtools

## DVD playback
# cd /tmp
# wget http://download.videolan.org/pub/libdvdcss/1.2.9/deb/libdvdcss2_1.2.9-1_i386.deb
# sudo dpkg -i libdvdcss2_1.2.9-1_i386.deb
#
# sudo apt-get install libdvdread3
# sudo apt-get install libdvdplay0
# sudo apt-get install libdvdnav4
# sudo apt-get install totem-xine
# sudo apt-get install libxine-extracodecs
# sudo apt-get install totem-xine-firefox-plugin
# sudo apt-get install vlc
# sudo apt-get install mplayer

## CD/DVD burning
# sudo apt-get install gnomebaker
# sudo apt-get install k3b
# sudo apt-get install k3b-i18n
#
# cd /tmp
# wget ftp://ftp4.usw.nero.com/nerolinux-2.1.0.2-x86.deb
# sudo apt-get install libgtk1.2
# sudo dpkg -i nerolinux-2.1.0.2-x86.deb

## Thunderbird
# sudo apt-get install mozilla-thunderbird
# sudo apt-get install mozilla-thunderbird-enigmail

## Wine
# sudo apt-get install wine msttcorefonts

## Compilers and manual pages
# sudo apt-get install build-essential manpages-dev

## Opera
# sudo apt-get install opera

5. Installing and configuring SSH server
Next install and configure SSH server to allow only your normal users to login. If your system has usernames jane and john make sure /etc/ssh/sshd_config has these lines. Launch Applications > Accessories > Terminal. Modify the settings and restart the SSH server.

# sudo apt-get install openssh-server
# sudo gedit /etc/ssh/sshd_config

Protocol 2
...
PermitRootLogin no
...
AllowUsers jane john

# sudo /etc/init.d/ssh restart

6. Configuring X
If you have an NVIDIA graphics card (I have GeForce FX 5200) it might be a good idea to install the accelerated driver for X. Otherwise the screen might be the bottleneck when using graphics intensive applications like DVD players and games.

# sudo apt-get install nvidia-glx nvidia-kernel-common
# sudo nvidia-glx-config enable

For ATI cards, type the following commands:

# sudo apt-get install xorg-driver-fglrx
# sudo dpkg-reconfigure xserver-xorg
## Select the "fglrx" driver instead of "ati"

# sudo gedit /etc/X11/xorg.conf
## Make sure you have the following settings
Section "Device"
Identifier "ATI Graphics Adapter"
Driver fglrx"
Option "VideoOverlay" "on"
BusID "PCI:1:0:0"
EndSection

After reboot you can test that the accelerated driver is really used with the following command:

# glxinfo | grep -i direct
direct rendering: Yes

7. Installing VMware Workstation
VMware Workstation is a commercial virtualization software which enables you to run Windows on your Linux PC.

# sudo apt-get install build-essential linux-headers-`uname -r`

# tar xzf VMware-workstation-5.5.2-29772.tar.gz -C /tmp
# cd /tmp/vmware-distrib
# sudo ./vmware-install.pl

# sudo vmware-config.pl -c

Note for Ubuntu 6.10 users: apply the following patch or VMware Workstation will not start correctly.

# cd /tmp
# wget http://www.iki.fi/kuparine/comp/ubuntu/wrapper-gtk24.sh.diff
# cd /usr/lib/vmware/lib
# sudo patch < /tmp/wrapper-gtk24.sh.diff

8. Installing VMware Server
VMware Server is a free software which enables you to run Windows on your Linux PC. See a separate document how I installed VMware Server. Please note that unlike with VMware Player, you can create virtual machines with VMware Server.

9. Installing VMware Player
VMware Player is a free software which enables you to run Windows on your Linux PC. This needs an existing virtual machine which can be created with the non-free VMware Workstation, with the free QEMU and with the free VM Builder.

Note: VMware Workstation installs also the VMware Player so these steps are only needed if you don't have a VMware Workstation license.

# sudo apt-get install vmware-player

10. DMA settings
IDE hard disk and IDE CD-ROM

# sudo gedit /etc/hdparm.conf

# In this example /dev/hda is the hard disk
/dev/hda {
io32_support = 1
dma = on
}

# In this example /dev/hdc is the CD-ROM
/dev/hdc {
io32_support = 1
dma = on
}

# sudo /etc/init.d/hdparm restart

SATA hard disk and IDE CD-ROM

# sudo gedit /etc/hdparm.conf

# In this example /dev/hdc is the CD-ROM
/dev/hdc {
io32_support = 1
dma = on
}

# sudo /etc/init.d/hdparm restart

Test the DMA settings with

# sudo hdparm /dev/hdc

/dev/hdc:
IO_support = 1 (32-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
HDIO_GETGEO failed: Invalid argument

11. Configuring firewall
Even though Ubuntu does not listen to any non-localhost ports by default I want to limit how my PC is visible to others. This is done by using the standard iptables firewall which is included in the Ubuntu installation. You could of course install Firestarter or GuardDog from the Synaptic package manager but I prefer a simple textfile-based solution.

Download this firewall script to your Desktop and modify it according to your network settings.

# gedit ~/Desktop/firewall

# sudo cp ~/Desktop/firewall /etc/init.d/firewall
# sudo chmod 755 /etc/init.d/firewall
# sudo ln -sf ../init.d/firewall /etc/rcS.d/S42firewall
# sudo /etc/rcS.d/S42firewall restart

12. Useful links
http://www.ubuntulinux.org/
Ubuntu Guide
Ubuntu Document Storage Facility
http://www.mrbass.org/linux/ubuntu/
EasyVMX!: Virtual Machine Creator
VM Builder
Create your own Virtual Machines for VMware Player
VMware player modification
Automatix
Easy Ubuntu
Psychocats Ubuntu page
Voikko

Tuesday, May 16, 2006

media

http://music.tuvanonline.com/index.php?act=view&code=song&ssid=54&id=7126

Sunday, May 14, 2006

TOP BLOG

useit.com Alertbox Oct. 2005 Blog Usability

Jakob Nielsen's Alertbox, October 17, 2005:

Weblog Usability: The Top Ten Design Mistakes
Summary:
Blogs are often too internally focused and ignore key usability issues, making it hard for new readers to understand the site and trust the author.
Weblogs are a form of website. The thousands of normal website usability guidelines therefore apply to them, as do this year's top ten design mistakes. But weblogs are also a special genre of website; they have unique characteristics and thus distinct usability problems.

One of a weblog's great benefits is that it essentially frees you from "Web design." You write a paragraph, click a button, and it's posted on the Internet. No need for visual design, page design, interaction design, information architecture, or any programming or server maintenance.

Blogs make having a simple website much easier, and as a result, the number of people who write for the Web has exploded. This is a striking confirmation of the importance of ease of use.

Weblogs' second benefit is that they're a Web-native content genre: they rely on links, and short postings prevail. You don't have to write a full article or conduct original research or reporting. You can simply find something interesting on another site and link to it, possibly with commentary or additional examples. Obviously, this is much easier than running a conventional site, and again indicates the benefits of lowering the barriers to computer use.

As a third benefit, blogs are part of an ecosystem (often called the Blogosphere) that serves as a positive feedback loop: Whatever good postings exist are promoted through links from other sites. More reader/writers see this good stuff, and the very best then get linked to even more. As a result, link frequency follows a Zipf distribution, with disproportionally more links to the best postings.

Some weblogs are really just private diaries intended only for a handful of family members and close friends. Usability guidelines generally don't apply to such sites, because the readers' prior knowledge and motivation are incomparably greater than those of third-party users. When you want to reach new readers who aren't your mother, however, usability becomes important.

Also, while readers of your intranet weblog might know you, usability is important because your readers are on company time. (As an example, see IBM's use of intranet blogs -- among the ten best intranets of 2006.)

Usability Issues
To reach new readers and respect your existing readers' time constraints, test your weblog against the following usability problems.
1. No Author Biographies
Unless you're a business blog, you probably don't need a full-fledged "about us" section the way a corporate site does. That said, the basic rationale for "about us" translates directly into the need for an "about me" page on a weblog: users want to know who they're dealing with.
It's a simple matter of trust. Anonymous writings have less credence than something that's signed. And, unless a person's extraordinarily famous, it's not enough to simply say that Joe Blogger writes the content. Readers want to know more about Joe. Does he have any credentials or experience in the field he's commenting on? (Even if you don't have formal credentials, readers will trust you more if you're honest about that fact, set forth your informal experience, and explain the reason for your enthusiasm.)

2. No Author Photo
Even weblogs that provide author bios often omit the author photo. A photo is important for two reasons:
It offers a more personable impression of the author. You enhance your credibility by the simple fact that you're not trying to hide. Also, users relate more easily to somebody they've seen.
It connects the virtual and physical worlds. People who've met you before will recognize your photo, and people who've read your site will recognize you when you meet in person (say, at a conference -- or the company cafeteria if you're an intranet blogger).
A huge percentage of the human brain is dedicated to remembering and recognizing faces. For many, faces work better than names. I learned this lesson myself in 1987 when I included my photo in a HyperCard stack I authored that was widely disseminated on Mac-oriented BBSs. Over the next two years, countless people came up to me and said, "I liked your stack," having recognized me from the photo.
Also, if you run a professional blog and expect to be quoted in the press, you should follow the recommendations for using the Web for PR and include a selection of high-resolution photos that photo editors can download.

3. Nondescript Posting Titles
Sadly, even though weblogs are native to the Web, authors rarely follow the guidelines for writing for the Web in terms of making content scannable. This applies to a posting's body text, but it's even more important with headlines. Users must be able to grasp the gist of an article by reading its headline. Avoid cute or humorous headlines that make no sense out of context.
Your posting's title is microcontent and you should treat it as a writing project in its own right. On a value-per-word basis, headline writing is the most important writing you do.

Descriptive headlines are especially important for representing your weblog in search engines, newsfeeds (RSS), and other external environments. In those contexts, users often see only the headline and use it to determine whether to click into the full posting. Even if users see a short abstract along with the headline (as with most search engines), user testing shows that people often read only the headline. In fact, people often read only the first three or four words of a headline when scanning a list of possible places to go. Sample bad headlines:

What Is It That You Want?
Hey, kids! Comics!
Victims Abandoned
Sample good headlines:
Pictures from Die Hunns and Black Halos show
Office Depot Pays United States $4.75 Million to Resolve False Claims Act Allegations
(too long, but even if you only read the first few words, you have an idea of what it's about)
Ice cream trucks as church marketing
This last headline works on a church-related blog. If you're writing an ice cream industry blog, start the headline with the word "church" because it's the information-carrying word within a context of all ice cream, all the time.
In browsing weblog headline listings to extract these examples, I noticed several headlines in ALL CAPS. That's always bad. Reading speed is reduced by 10% and users are put off by the appearance of shouting.

4. Links Don't Say Where They Go
Many weblog authors seem to think it's cool to write link anchors like: "some people think" or "there's more here and here." Remember one of the basics of the Web: Life is too short to click on an unknown. Tell people where they're going and what they'll find at the other end of the link.
Generally, you should provide predictive information in either the anchor text itself or the immediately surrounding words. You can also use link titles for supplementary information that doesn't fit with your content. (To see a link title in action, mouse over the "link titles" link.)

A related mistake in this category is to use insider shorthand, such as using first names when you reference other writers or weblogs. Unless you're writing only for your friends, don't alienate new visitors by appearing to be part of a closed clique. The Web is not high school.

5. Classic Hits are Buried
Hopefully, you'll write some pieces with lasting value for readers outside your fan base. Don't relegate such classics to the archives, where people can only find something if they know you posted it, say, in May 2003.
Highlight a few evergreens in your navigation system and link directly to them. For example, my own list of almost 300 Alertbox columns starts by saying, "Read these first: Usability 101 and Top Ten Mistakes of Web Design."

Also, remember to link to your past pieces in newer postings. Don't assume that readers have been with you from the beginning; give them background and context in case they want to read more about your ideas.

6. The Calendar is the Only Navigation
A timeline is rarely the best information architecture, yet it's the default way to navigate weblogs. Most weblog software provides a way to categorize postings so users can easily get a list of all postings on a certain topic. Do use categorization, but avoid the common mistake of tagging a posting with almost all of your categories. Be selective. Decide on a few places where a posting most belongs.
Categories must be sufficiently detailed to lead users to a thoroughly winnowed list of postings. At the same time, they shouldn't be so detailed that users face a category menu that's overly long and difficult to scan. Ten to twenty categories are appropriate for structuring many topics.

On the main page for each category, highlight that category's evergreens as well as a time line of its most recent postings.

7. Irregular Publishing Frequency
Establishing and meeting user expectations is one of the fundamental principles of Web usability. For a weblog, users must be able to anticipate when and how often updates will occur.
For most weblogs, daily updates are probably best, but weekly or even monthly updates might work as well, depending on your topic. In either case, pick a publication schedule and stick to it. If you usually post daily but sometimes let months go by without new content, you'll lose many of your loyal -- and thus most valuable -- readers.

Certainly, you shouldn't post when you have nothing to say. Polluting cyberspace with excess information is a sin. To ensure regular publishing, hold back some ideas and post them when you hit a dry spell.

8. Mixing Topics
If you publish on many different topics, you're less likely to attract a loyal audience of high-value users. Busy people might visit a blog to read an entry about a topic that interests them. They're unlikely to return, however, if their target topic appears only sporadically among a massive range of postings on other topics. The only people who read everything are those with too much time on their hands (a low-value demographic).
The more focused your content, the more focused your readers. That, again, makes you more influential within your niche. Specialized sites rule the Web, so aim tightly.

If you have the urge to speak out on, say, both American foreign policy and the business strategy of Internet telephony, establish two blogs. You can always interlink them when appropriate.

9. Forgetting That You Write for Your Future Boss
Whenever you post anything to the Internet -- whether on a weblog, in a discussion group, or even in an email -- think about how it will look to a hiring manager in ten years. Once stuff's out, it's archived, cached, and indexed in many services that you might never be aware of.
Years from now, someone might consider hiring you for a plum job and take the precaution of 'nooping you first. (Just taking a stab at what's next after Google. Rest assured: there will be some super-snooper service that'll dredge up anything about you that's ever been bitified.) What will they find in terms of naïvely puerile "analysis" or offendingly nasty flames published under your name?

Think twice before posting. If you don't want your future boss to read it, don't post.

10. Having a Domain Name Owned by a Weblog Service
Having a weblog address ending in blogspot.com, typepad.com, etc. will soon be the equivalent of having an @aol.com email address or a Geocities website: the mark of a naïve beginner who shouldn't be taken too seriously.
Letting somebody else own your name means that they own your destiny on the Internet. They can degrade the service quality as much as they want. They can increase the price as much as they want. They can add atop your content as many pop-ups, blinking banners, or other user-repelling advertising techniques as they want. They can promote your competitor's offers on your pages. Yes, you can walk, but at the cost of your loyal readers, links you've attracted from other sites, and your search engine ranking.

The longer you stay at someone else's domain name, the higher the cost of going independent. Yes, it's tempting to start a new weblog on one of the services that offer free accounts. It's easy, it's quick, and it's obviously cheap. But it only costs $8 per year to get your personal domain name and own your own future. As soon as you realize you're serious about blogging, move it away from a domain name that's controlled by somebody else. The longer you delay, the more pain you'll feel when you finally make the move.

Learn More
I cover a much broader set of usability guidelines in the full-day tutorial on Fundamental Guidelines for Web Usability at the Usability Week 2006 conference in New York, San Francisco, London, and Sydney.
We are getting several interesting findings about users' detailed reading behavior in our current eyetracking studies, which will be presented at the conference.

There's also a two-day tutorial on writing for the Web (San Francisco and Sydney only).

Other Top Ten Lists:

The ten very worst Web design mistakes of all time
Summary based on the main elements of the other lists.
Web design mistakes (1996)
My first list. Luckily, many of these mistakes have been fixed by now.
Web design mistakes (1999)
Web design mistakes (2002)
With cartoons.
Web design mistakes (2003)
Web design mistakes (2005)
Good deeds in Web design
Top homepage usability guidelines
Most violated homepage guidelines


--------------------------------------------------------------------------------
> Other Alertbox columns (complete list)
> Sign up for newsletter that will notify you of new Alertboxes
--------------------------------------------------------------------------------

Copyright © 2005 by Jakob Nielsen

Sunday, January 15, 2006

media

Saturday, October 01, 2005

Hà Nội Mùa Lá Bay

::: Hữu Xuân :::



Hà Nội Mùa Lá Bay
Mùa thu, xanh một trời Hà Nội,
em nghe thu hát ngang lưng trời .
Từng con đường năm xưa,
lối ta đi qua những ngày thơ ấu...
Trong tim tôi Thăng Long Hà Nội,
dẫu cách xa tôi vẫn yêu người .
Ở nơi ấy giữ bao nhiêu kỷ niệm đời tôi .

Mùa thu, cốm đầu mùa dịu ngọt.
Trên cao, hoa sữa hương ngạt ngào.
Hồ Tây chiều hôm nay, nỗi nhớ ai những tháng ngày xưa ấy.
Mưa Ngâu rơi, rơi trên mặt hồ .
Gió heo may tím ngát mong chờ .
Tà áo trắng, tóc em bay trong chiều mùa thu.
Ôi mùa thu, mùa thu Hà Nội,
Trời thanh trong chẳng đâu thanh hơn thế.
Và lá bay trong chiều thu,
lá bay ven hồ Tây,
lá bay trong lòng tôi...

Thursday, June 30, 2005

Relax

http://fun.more.jcisio.com/photo/Dau_oc_den_toi.jpg.htm

Relax

http://fun.more.jcisio.com/photo/Dau_oc_den_toi.jpg.htm

Monday, June 27, 2005

Audio

http://www.metalmethod.com/audio-video/



Index of /audio-video


Index of /audio-video


      Name                    Last modified       Size  Description


[DIR] Parent Directory 23-May-2005 18:46 -
[SND] audio-news-01-part-1..> 04-Jan-2005 20:44 1.8M
[SND] audio-news-01-part-2..> 04-Jan-2005 21:07 1.3M
[   ] guitar-lesson-03.wmv 22-Apr-2003 13:18 2.5M
[   ] guitar-lesson-04.wmv 16-Nov-2003 16:07 7.3M
[   ] guitar-lick-nrml.wmv 17-Dec-2004 18:15 741k
[   ] guitar-lick-slow.wmv 17-Dec-2004 18:15 1.5M
[   ] guitar-style-1-ex.wmv 30-Dec-2004 14:11 3.3M
[   ] guitar-style-2-ex.wmv 30-Dec-2004 14:12 3.8M
[   ] guitar-style-3-ex.wmv 30-Dec-2004 14:09 4.4M
[   ] guitar-style-4-ex.wmv 30-Dec-2004 14:07 4.2M
[   ] guitar_tab.wmv 17-Dec-2004 18:16 1.6M
[SND] metal-riffs-demo.mp3 30-Dec-2004 16:18 2.0M
[SND] news-2005-01-04.mp3 04-Jan-2005 21:14 3.2M
[SND] style-1-part-1-ex.mp3 30-Dec-2004 14:03 2.5M
[SND] style-1-part-2-ex.mp3 30-Dec-2004 14:02 2.4M
[SND] style-2-part-1-ex.mp3 30-Dec-2004 14:00 2.1M
[SND] style-2-part-2-ex.mp3 30-Dec-2004 14:01 2.5M
[SND] style-2-part-3-ex.mp3 30-Dec-2004 14:06 2.3M
[SND] style-3-part-1-ex.mp3 30-Dec-2004 13:57 2.0M
[SND] style-3-part-2-ex.mp3 30-Dec-2004 13:57 2.1M
[SND] style-3-part-3-ex.mp3 30-Dec-2004 13:59 2.7M
[SND] style-4-part-1-ex.mp3 30-Dec-2004 14:04 2.1M
[SND] style-4-part-2-ex.mp3 30-Dec-2004 14:05 2.2M
[   ] tab-lick44.tef 22-Apr-2003 13:21 2k