朋友推荐看了部印度片《三个白痴/三个傻瓜》,号称09年印度票房冠军最新高分爱情爆笑喜剧片,IMDB评分是8.1/10。片子比较长,大概2小时44分钟,花了我半个下午的时间,不过的确非常好看。
观看方法:
1、安装qvod(快播)软件的点击http://www.tom365.org/movie_2004/html/8519.html
2、用迅雷下载的点击http://www.gougou.com/search?search=三傻大闹宝莱坞
花半个下午,享受一下戏剧乐趣。
记录一个IT技术员的生活与技术
Written by 正冰 on 2010, October 27, 4:39 PM
朋友推荐看了部印度片《三个白痴/三个傻瓜》,号称09年印度票房冠军最新高分爱情爆笑喜剧片,IMDB评分是8.1/10。片子比较长,大概2小时44分钟,花了我半个下午的时间,不过的确非常好看。
观看方法:
1、安装qvod(快播)软件的点击http://www.tom365.org/movie_2004/html/8519.html
2、用迅雷下载的点击http://www.gougou.com/search?search=三傻大闹宝莱坞
花半个下午,享受一下戏剧乐趣。
Written by 正冰 on 2010, October 26, 5:04 PM
本文转自:http://www.dmo.ca/blog/detecting-virtualization-on-linux/
Update: You may be interested in [[the perl module|perl-module-for-virtualization-detection]] implementing these tricks. Frequently, our customers want to install our software in a virtual machine. This can be OK, but frequently they hit a CPU, memory, or IO limit caused by running in a constrained virtual environment. When this happens, we really like to know if they're running under virtualization when we try to support them. Here's some tricks to detect, from a shell, if the system is virtualized. The first thing to check is dmesg. On a recently-booted system, checking the 'dmesg' command output may be sufficient. Otherwise, try "cat /var/log/dmesg" instead of "dmesg" VMWare: QEmu or KVM: If the "-cpu host" option has not been used, QEmu and KVM will identify themselves as: otherwise, the host's CPU information will be used both in dmesg, or in /proc/cpuinfo. However, you should see something like: on newer kernels that understand that they're running under paravirtualization. (Thanks to René Pfeiffer for pointing this out) Microsoft VirtualPC: Xen (thanks, wardi and others) Virtuozzo On longer-running systems, you may need to grep /var/log/dmesg instead. If that doesn't produce anything useful, try using dmidecode to look at the BIOS information. Frequently, there will be at least one component identifying itself as virtualized: VMWare: Microsoft VirtualPC: QEMU or KVM: Virtuozzo: Xen: You should just examine the output of dmidecode directly rather than trying to grep as above, in case the output changes. QEMU, for example, doesn't report the vendor in all versions. Next, check disk devices for identification as virtualized: VMWare: Microsoft VirtualPC: QEMU, KVM, or Xen: Virtuozzo: If you've got tips for other virtualized environments, let me know and I'll add them to the list.
# dmesg | grep -i virtual VMware vmxnet virtual NIC driver Vendor: VMware Model: Virtual disk Rev: 1.0 hda: VMware Virtual IDE CDROM Drive, ATAPI CD/DVD-ROM drive
# dmesg | grep -i virtual CPU: AMD QEMU Virtual CPU version 0.9.1 stepping 03
$ dmesg | grep -i virtual [ 0.000000] Booting paravirtualized kernel on KVM
# dmesg | grep -i virtual hda: Virtual HD, ATA DISK drive hdc: Virtual CD, ATAPI CD/DVD-ROM drive
# dmesg | grep -i xen Xen virtual console successfully installed as tty1
# dmesg (returns no output) # cat /var/log/dmesg (returns no output) # ls -al /proc/vz veinfo veinfo_redir veredir vestat vzaquota vzdata
# dmidecode | egrep -i 'manufacturer|product' Manufacturer: VMware, Inc. Product Name: VMware Virtual Platform
# dmidecode | egrep -i 'manufacturer|product' Manufacturer: Microsoft Corporation Product Name: Virtual Machine
# dmidecode | egrep -i 'vendor' Vendor: QEMU
# dmidecode /dev/mem: Permission denied
# dmidecode | grep -i domU Product Name: HVM domU
# cat /proc/ide/hd*/model VMware Virtual IDE CDROM Drive # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-Access ANSI SCSI revision: 02
# cat /proc/ide/hd*/model Virtual HD Virtual CD
# cat /proc/ide/hd*/model QEMU HARDDISK QEMU DVD-ROM
# ls -al /dev/vzfs b-----x--- 1 root root 0, 19 2009-04-06 15:04 /dev/vzfs
Written by 正冰 on 2010, October 26, 4:39 PM
今天下单买了rashost的北京双线VPS一台,结果开通后就无法连接,ping以后返回2种信息:
Ping的返回信息有"Request Timed Out"、"Destination Net Unreachable"和"Bad IP address"还有"Source quench received"。
"Request Timed Out"这个信息表示对方主机可以到达到TIME OUT,这种情况通常是为对方拒绝接收你发给它的数据包造成数据包丢失。大多数的原因可能是对方装有防火墙或已下线。
"Destination Net Unreachable"这个信息表示对方主机不存在或者没有跟对方建立连接。这里要说明一下"destination host unreachable"和"time out"的区别,如果所经过的路由器的路由表中具有到达目标的路由,而目标因为其它原因不可到达,这时候会出现"time out",如果路由表中连到达目标的路由都没有,那就会出现"destination host unreachable"。
"Bad IP address" 这个信息表示你可能没有连接到DNS服务器所以无法解析这个IP地址,也可能是IP地址不存在。
"Source quench received"信息比较特殊,它出现的机率很少。它表示对方或中途的服务器繁忙无法回应。