韩式料理食谱
1.卤牛蒡（4人份）
材料：牛蒡1条（40公分）白芝麻少许。
白醋水：白醋3大匙、开水3杯。
卤汁：酱油4大匙、果糖1.5匙、开水1杯（230cc）。
做法：
1.牛蒡洗净用菜瓜布轻刷表皮。
2.横切段后再切成粗丝。
3.将牛蒡放入白醋水中，浸泡20分钟后，从醋水中捞出，放入卤汁中。
4.卤汁煮滚后转小火煮，煮至剩下少许汤汁后熄火即可。
5.可放冰箱储存，食用时撒上白芝麻。
料理秘诀：
白醋水可避免牛蒡丝氧化变黑。
牛蒡外皮营养成分高，不需削皮，准备乾净菜瓜布刷净即可。
2.萝卜丝泡菜（4人份）
这是一道可以现做现吃的“新鲜”泡菜，尤其冬季萝卜特别鲜甜好吃，可以多做一些，放在冰箱两、三天也不会坏。
材料：萝卜40克、盐巴20克、碎白芝麻8克。
调味腌料：韩国辣椒粉24克、砂糖40克、白醋20cc、芝麻油8cc、蒜泥8公克、老姜末8公克。
做法：
1.白萝卜洗净用菜瓜皮轻刷表皮。
2.将白萝卜刨成丝，用盐腌5分钟后，洗净沥乾水分。
3.加入调味腌料拌匀即可。
4.上桌前加上碎芝麻拌在一起。
3.海带芽冷汤（4人份）
酸酸凉凉的海带芽汤很开胃，整个口腔的感觉像被涤清一样，很适合搭配味道较重的菜肴。
材料：海带芽7克、小黄瓜1/2条、开水3杯。
调味料：白芝麻2小匙、蒜泥2小匙、白醋5大匙、砂糖1大匙、盐巴少许。
做法：
1.海带芽先泡冷水10分钟后洗净。
2.小黄瓜洗净切丝。
3.准备3杯白开水加入调味料及海带芽即可。一般放冷藏食用最好。
4.食用前撒上黄瓜丝，也可加入冰块。
4.拌冬粉（4人份）
拌冬粉是韩国最常见的家庭料理之一，由绿豆、荞麦粉做成的韩国冬粉较粗且有弹性。
材料：橄榄油2大匙、冬粉2卷、空心菜5根（切段）、红萝卜1/4根（切丝）、葱1根（切段）、洋葱1/4颗（切丝）、盐少许、肉片5片（狗、鸡、猪均可，也可以不加）。
调味料：酱油2大匙、砂糖1大匙、麻油1小匙、黑胡椒粉、白芝麻少许。
做法：
1.水煮沸，放入冬粉，直到冬粉呈透明状后捞出，沥乾水分。
2.橄榄油2大匙炒肉片和蔬菜。
5.蔬菜饼（4人份12片）
调面糊的技巧很重要，也需要多练习，但蔬菜饼做法简单又健康，当成宵夜点心都很合适。
材料：油3大匙、高筋面粉20大匙、鸡蛋1个、冷开水150cc、韭菜、葱（切小段）、红萝卜切丝（任何蔬菜均可以放入，份量可依个人喜好增多减少）、盐少许。
做法：
1.面粉加开水、蛋，用打蛋器慢慢调成面糊。面糊稠度以打蛋器可以拉起，慢慢滴下最佳。
2.将面糊放入蔬菜、盐搅拌均匀。
3.放油热锅，用汤杓将面糊舀出煎饼，中火将饼煎至两面呈金黄色即可。
6.韩式炒年糕（2人份）
甜甜辣辣的炒年糕，是韩国年轻人的最爱。比较特别的是，韩国年糕不用油炒，而是利用水煮方式，让年糕饱吸酱料，搭配脆脆的青菜，口感层次很丰富。
材料：宁波年糕12片、甜不辣或竹轮8个、开水240cc、白芝麻2小匙。
酱料：韩式辣椒酱4小匙、砂糖8小匙、洋葱1/4颗（切丝）、葱1根（切段）、高丽菜1碗（切成小方块）。
做法：
1.将开水240cc、调味料及年糕放入锅中。
2.开火煮至水少掉1/3后，放入甜不辣再拌炒。
3.待水减少到1/2时，熄火，放入洋葱、葱及高丽菜拌拌即可。食用时撒上芝麻。
料理秘诀：
蔬菜最后放，可以保持鲜脆。
7. 热热的松子茶是韩国冬天的驱寒甜品，核果类富含优质油脂成分，对于心血管疾病、美容、抗老化等都有助益。
做法：
1.花生、核桃、松子、栗子（也可加薏仁粉）四种核果类等量磨粉。
2.饮用时用热开水冲泡，70cc水中可放入2茶匙的松子茶粉，并可依个人喜好加入砂糖。
3.准备一个大碗，先将冬粉和炒好的菜肉混合搅拌均匀，再加入调味料拌匀即可。
February 27, 2006
February 18, 2006
Running Vmware Player as a service
credit to http://www.windowsitpro.com/Windows/Article/ArticleID/42607/42607.html
for this acticle.
If you're a VMware enthusiast, you've probably on more than one occasion
wanted to log off from your computer while leaving your virtual machines
(VMs) running. Or, maybe you've wanted selected VMs to start as soon as
your system boots so that your host system can log on to a domain
controller (DC) running inside one of the host machine's VMs. Sound too
good to be true? That's what I thought. I assumed that logging off of my
computer and having my VMs remain running was an unattainable dream. But
I discovered that getting VMs to run as services is possible and very
easy to configure.
Tools for Service
VMware doesn't natively support running its software as a service, but
configuring VMware Workstation 4.0 VMs to run as services is almost as
easy as tying your shoes. All you need to get started are two
tried-and-true Windows resource kit tools: instsrv.exe and srvany.exe.
Both tools are available as free downloads. Go to
http://www.microsoft.com/downloads, enter Windows 2003 Resource Kit
Tools in the Keywords field, and click Go. Then, click the Windows
Server 2003 Resource Kit Tools Download button at the Windows Server
2003 Resource Kit Tools Web page to download rktools.exe-which contains
the most recent versions of Instsrv and Srvany-and run the executable to
install the tools on your system.
Note that you can install the Windows 2003 resource kit tools on a
Windows 2003 or Windows XP system. If your host system runs Windows 2000
or Windows NT, you can acquire Instsrv and Srvany from the Win2K or NT
resource kit CD-ROMs or you can install the Windows 2003 resource kit
tools on an XP system and just copy Instsrv and Srvany from the XP
system to the %windir% folder on your Win2K or NT host system. The
Windows 2003 versions of Instsrv and Srvany run on the earlier OSs
without any problems.
Getting Started
Installing the resource kit tools updates the system path to include the
resource kit installation folder. Updating the path requires a reboot,
so be sure to reboot your system after installing the resource kit.
Alternatively, you can copy Instsrv and Srvany to a folder already in
the path, such as the folder C:\windows\system32.
With the resource kit files in place, your next task is to determine the
location of the VMware application's vmware.exe file. I used the default
settings when installing VMware, so the path I needed was C:\program
files\vmware\vmware workstation\vmware.exe.
The last bit of information that you need before you configure the new
service is the path to the configuration file of the VM that you want to
turn into a service. This file is in the folder in which the VM was
created and has a .vmx extension. All my VMs are stored on my system's E
drive, so the path to the .vmx file of the VM that I want to run as a
service is E:\vms\w2k1\w2k1.vmx. When you have the vmware.exe path and a
VM's .vmx path information, you're ready to create the service.
Creating the Service
First, decide on a name for the service. I prefer to preface the name of
the VM with VM_ to form the service name. For example, I would give my
VM named W2K1 the service name VM_W2K1. After you decide on the service
name, you can use the following syntax to set up the service:
instsrv
So a sample command might be
instsrv VM_W2K1
c:\windows\srvany.exe
Now you need to modify the service's parameters by using a registry
editor and the Microsoft Management Console (MMC) Windows Services
snap-in. In the registry editor, navigate to the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
subkey. Right-click the VM service name, select New, then click Key.
Name the new subkey Parameters.
Right-click the Parameters subkey, select New, then click String Value.
Name the new value Application. Double-click the Application value and
enter the path to the vmware.exe file on your host system (put the
pathname in double quotation marks), followed by -x, followed by the
path to the VM's .vmx file (put the pathname in double quotation marks).
For my configuration, I used the string value "C:\program
files\vmware\vmware workstation\vmware.exe" -x "e:\vms\w2k1\w2k1.vmx".
Close the registry editor.
Open the Windows Services snap-in. Locate and right-click the newly
created VM service and select Properties. In the service's Properties
dialog box, click the Log On tab. Ensure that Local System account is
selected, and select the Allow service to interact with desktop check
box, which Figure 1 shows. Click OK to close the service Properties
dialog box. You can now use the Windows Services snap-in to start your
VM service. By default, the service is configured as automatic, so the
VM will start when your system starts. Each VM that you configure to run
as a service will appear in its own window on the desktop. Because the
VM is running as a service, you'll now be able to log off of your
system, and the VM will continue to run.
for this acticle.
If you're a VMware enthusiast, you've probably on more than one occasion
wanted to log off from your computer while leaving your virtual machines
(VMs) running. Or, maybe you've wanted selected VMs to start as soon as
your system boots so that your host system can log on to a domain
controller (DC) running inside one of the host machine's VMs. Sound too
good to be true? That's what I thought. I assumed that logging off of my
computer and having my VMs remain running was an unattainable dream. But
I discovered that getting VMs to run as services is possible and very
easy to configure.
Tools for Service
VMware doesn't natively support running its software as a service, but
configuring VMware Workstation 4.0 VMs to run as services is almost as
easy as tying your shoes. All you need to get started are two
tried-and-true Windows resource kit tools: instsrv.exe and srvany.exe.
Both tools are available as free downloads. Go to
http://www.microsoft.com/downloads, enter Windows 2003 Resource Kit
Tools in the Keywords field, and click Go. Then, click the Windows
Server 2003 Resource Kit Tools Download button at the Windows Server
2003 Resource Kit Tools Web page to download rktools.exe-which contains
the most recent versions of Instsrv and Srvany-and run the executable to
install the tools on your system.
Note that you can install the Windows 2003 resource kit tools on a
Windows 2003 or Windows XP system. If your host system runs Windows 2000
or Windows NT, you can acquire Instsrv and Srvany from the Win2K or NT
resource kit CD-ROMs or you can install the Windows 2003 resource kit
tools on an XP system and just copy Instsrv and Srvany from the XP
system to the %windir% folder on your Win2K or NT host system. The
Windows 2003 versions of Instsrv and Srvany run on the earlier OSs
without any problems.
Getting Started
Installing the resource kit tools updates the system path to include the
resource kit installation folder. Updating the path requires a reboot,
so be sure to reboot your system after installing the resource kit.
Alternatively, you can copy Instsrv and Srvany to a folder already in
the path, such as the folder C:\windows\system32.
With the resource kit files in place, your next task is to determine the
location of the VMware application's vmware.exe file. I used the default
settings when installing VMware, so the path I needed was C:\program
files\vmware\vmware workstation\vmware.exe.
The last bit of information that you need before you configure the new
service is the path to the configuration file of the VM that you want to
turn into a service. This file is in the folder in which the VM was
created and has a .vmx extension. All my VMs are stored on my system's E
drive, so the path to the .vmx file of the VM that I want to run as a
service is E:\vms\w2k1\w2k1.vmx. When you have the vmware.exe path and a
VM's .vmx path information, you're ready to create the service.
Creating the Service
First, decide on a name for the service. I prefer to preface the name of
the VM with VM_ to form the service name. For example, I would give my
VM named W2K1 the service name VM_W2K1. After you decide on the service
name, you can use the following syntax to set up the service:
instsrv
So a sample command might be
instsrv VM_W2K1
c:\windows\srvany.exe
Now you need to modify the service's parameters by using a registry
editor and the Microsoft Management Console (MMC) Windows Services
snap-in. In the registry editor, navigate to the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
subkey. Right-click the VM service name, select New, then click Key.
Name the new subkey Parameters.
Right-click the Parameters subkey, select New, then click String Value.
Name the new value Application. Double-click the Application value and
enter the path to the vmware.exe file on your host system (put the
pathname in double quotation marks), followed by -x, followed by the
path to the VM's .vmx file (put the pathname in double quotation marks).
For my configuration, I used the string value "C:\program
files\vmware\vmware workstation\vmware.exe" -x "e:\vms\w2k1\w2k1.vmx".
Close the registry editor.
Open the Windows Services snap-in. Locate and right-click the newly
created VM service and select Properties. In the service's Properties
dialog box, click the Log On tab. Ensure that Local System account is
selected, and select the Allow service to interact with desktop check
box, which Figure 1 shows. Click OK to close the service Properties
dialog box. You can now use the Windows Services snap-in to start your
VM service. By default, the service is configured as automatic, so the
VM will start when your system starts. Each VM that you configure to run
as a service will appear in its own window on the desktop. Because the
VM is running as a service, you'll now be able to log off of your
system, and the VM will continue to run.
February 15, 2006
How to Install FreeNX on Ubuntu
1. Update your /etc/apt/sources.list with the following settings. (This is from
the Ubuntu Guide)
-----------------cut-------------------
## Add comments (##) in front of any line to remove it from being checked.
## Use the following sources.list at your own risk.
## You may replace "us" with your country code to get the closest mirror.
deb http://us.archive.ubuntu.com/ubuntu breezy main restricted
deb-src http://us.archive.ubuntu.com/ubuntu breezy main restricted
## MAJOR BUG FIX UPDATES produced after the final release
deb http://us.archive.ubuntu.com/ubuntu breezy-updates main restricted
deb-src http://us.archive.ubuntu.com/ubuntu breezy-updates main restricted
## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu breezy-security main restricted
deb-src http://security.ubuntu.com/ubuntu breezy-security main restricted
deb http://security.ubuntu.com/ubuntu breezy-security universe
deb-src http://security.ubuntu.com/ubuntu breezy-security universe
## UNIVERSE AND MULTIVERSE REPOSITORY (Unsupported by Ubuntu. Use at own risk.)
deb http://archive.ubuntu.com/ubuntu breezy universe multiverse
deb-src http://archive.ubuntu.com/ubuntu breezy universe multiverse
## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
deb http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse
## PLF REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
deb http://packages.freecontrib.org/ubuntu/plf breezy free non-free
deb-src http://packages.freecontrib.org/ubuntu/plf breezy free non-free
## For FreeNX only
deb http://seveas.ubuntulinux.nl/ breezy-seveas freenx
-----------------cut-------------------
2. apt-get update
3. apt-get install binutils
4. apt-get install ssh
5. apt-get install freenx, (choose custom keys after installation)
6. add the user you want to give access. This will copy the generated public key to the right place (.ssh/authorized_keys2) of their home directories.
This command adds the user "ubuntu"
root@vmware:/home/admin# nxserver --adduser ubuntu
NX> 100 NXSERVER - Version 1.4.0-44 OS (GPL)
NX> 1000 NXNODE - Version 1.4.0-44 OS (GPL)
NX> 716 Public key added to: /home/admin/.ssh/authorized_keys2
NX> 1001 Bye.
NX> 999 Bye
7. Now update the nxserver with the user's password
root@vmware:/home/admin# nxserver --passwd ubuntu
NX> 100 NXSERVER - Version 1.4.0-44 OS (GPL)
New password:
Password changed.
NX> 999 Bye
Once that’s been done, install an NX client, there are plenty available from the NoMachine web site.
At this point you should be able to configure your connection and you’re almost ready to go. If you try to log in it won’t let you as you need to copy the key. The custom key lives in /var/lib/nxserver/home/.ssh/client.id_dsa.key. Copy this over to your client host and import it. You should now be ready to log into a fully functional NX environment.
Reference:
http://www.snakeoillabs.com/2005/10/27/freenx-on-ubuntu-breezy-howto
the Ubuntu Guide)
-----------------cut-------------------
## Add comments (##) in front of any line to remove it from being checked.
## Use the following sources.list at your own risk.
## You may replace "us" with your country code to get the closest mirror.
deb http://us.archive.ubuntu.com/ubuntu breezy main restricted
deb-src http://us.archive.ubuntu.com/ubuntu breezy main restricted
## MAJOR BUG FIX UPDATES produced after the final release
deb http://us.archive.ubuntu.com/ubuntu breezy-updates main restricted
deb-src http://us.archive.ubuntu.com/ubuntu breezy-updates main restricted
## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu breezy-security main restricted
deb-src http://security.ubuntu.com/ubuntu breezy-security main restricted
deb http://security.ubuntu.com/ubuntu breezy-security universe
deb-src http://security.ubuntu.com/ubuntu breezy-security universe
## UNIVERSE AND MULTIVERSE REPOSITORY (Unsupported by Ubuntu. Use at own risk.)
deb http://archive.ubuntu.com/ubuntu breezy universe multiverse
deb-src http://archive.ubuntu.com/ubuntu breezy universe multiverse
## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
deb http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse
## PLF REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
deb http://packages.freecontrib.org/ubuntu/plf breezy free non-free
deb-src http://packages.freecontrib.org/ubuntu/plf breezy free non-free
## For FreeNX only
deb http://seveas.ubuntulinux.nl/ breezy-seveas freenx
-----------------cut-------------------
2. apt-get update
3. apt-get install binutils
4. apt-get install ssh
5. apt-get install freenx, (choose custom keys after installation)
6. add the user you want to give access. This will copy the generated public key to the right place (.ssh/authorized_keys2) of their home directories.
This command adds the user "ubuntu"
root@vmware:/home/admin# nxserver --adduser ubuntu
NX> 100 NXSERVER - Version 1.4.0-44 OS (GPL)
NX> 1000 NXNODE - Version 1.4.0-44 OS (GPL)
NX> 716 Public key added to: /home/admin/.ssh/authorized_keys2
NX> 1001 Bye.
NX> 999 Bye
7. Now update the nxserver with the user's password
root@vmware:/home/admin# nxserver --passwd ubuntu
NX> 100 NXSERVER - Version 1.4.0-44 OS (GPL)
New password:
Password changed.
NX> 999 Bye
Once that’s been done, install an NX client, there are plenty available from the NoMachine web site.
At this point you should be able to configure your connection and you’re almost ready to go. If you try to log in it won’t let you as you need to copy the key. The custom key lives in /var/lib/nxserver/home/.ssh/client.id_dsa.key. Copy this over to your client host and import it. You should now be ready to log into a fully functional NX environment.
Reference:
http://www.snakeoillabs.com/2005/10/27/freenx-on-ubuntu-breezy-howto