Using virtual serial ports via named pipes in ESX 3.5

Create a named pipe as you typically would as the server on your first VM.


The corresponding entries in the vmx file:

serial0.present = “true”
serial0.yieldOnMsrRead = “true”
serial0.fileType = “pipe”
serial0.fileName = “/vmfs/volumes/472c028b-dd6c1d22-a8f4-001aa0c0b349/Zangief-Fileserver/Zangief-pipe”
serial0.pipe.endPoint = “server”
serial0.tryNoRxLoss = “true”

Create the same named pipe on your second VM, using the same pipe, but connected as a client, opposed to the server.


The corresponding vmx file entries:
serial0.present = “true”
serial0.yieldOnMsrRead = “true”
serial0.fileType = “pipe”
serial0.fileName = “/vmfs/volumes/472c028b-dd6c1d22-a8f4-001aa0c0b349/Zangief-Fileserver/Zangief-pipe”
serial0.pipe.endPoint = “client”
serial0.tryNoRxLoss = “true”

After you power up the VM, you’ll find it strange that the pipe is not visible in the service console.

ls -l /vmfs/volumes/472c028b-dd6c1d22-a8f4-001aa0c0b349/Zangief-Fileserver/Zangief-pipe
ls: /vmfs/volumes/472c028b-dd6c1d22-a8f4-001aa0c0b349/Zangief-Fileserver/Zangief-pipe: No such file or directory

If you connect to it on the second VM however, you’ll see that it works.


iSCSI naming

Both targets and initiators require names for the purpose of
identification, so that iSCSI storage resources can be managed
regardless of location (address). Note that this means iSCSI names
are independent of location.

Furthermore, iSCSI names are associated with iSCSI nodes instead of
with network adapter cards to ensure the free movement of network
HBAs between hosts without loss of SCSI state information
(reservations, mode page settings etc) and authorization
configuration. An iSCSI node also has one or more addresses.
An iSCSI address specifies a single path to an iSCSI node and consists
of the iSCSI name, plus a transport (TCP) address which uses the following format: [: ] If the is not specified, the
default port 3260, assigned by IANA, will be assumed. For iSCSI
initiators, the is omitted.

The concepts of names and addresses have been carefully separated in

– An iSCSI Name is a location-independent, permanent identifier for
an iSCSI node. An iSCSI node has one iSCSI name, which stays
constant for the life of the node.

– An iSCSI Address specifies not only the iSCSI name of an iSCSI
node, but also a location of that node. The address consists of a
host name or IP address, a TCP port number (for the target), and
the iSCSI Name of the node. An iSCSI node can have any number of
addresses, which can change at any time.

To assist in providing a more human-readable user interface for
devices that contain iSCSI targets and initiators, a target or
initiator may also provide an alias. The alias strings are communicated
between the initiator and target at login, and can be displayed by a user interface on either end, helping the user tell at a glance whether the
initiators and/or targets at the other end appear to be correct.
The alias is a variable length string, between 0 and 255 characters.

Constructing iSCSI names using the iqn. format.

– The string “iqn.”

– A date code specifying the year and month in which the
organization registered the domain or sub-domain name used as the
naming authority string.

– The organizational naming authority string, which consists of a
valid, reversed domain or subdomain name.

– Optionally, a ‘:’, followed by a string of the assigning
organization’s choosing, which must make each assigned iSCSI name

The following is an example of an iSCSI qualified name from an
equipment vendor:

Organizational Subgroup Naming Authority
Naming and/or string Defined by
Type Date Auth Org. or Local Naming Authority
+–++—–+ +———+ +——————————–+
| || | | | | |

The following is an example of an iSCSI name string from a storage
service provider:

Organization String
Naming Defined by Org.
Type Date Authority Naming Authority
+-+ +—–+ +————-+ +———————-+
| | | | | | | |

Note that when reversing these domain names, the first component
(after the “iqn.”) will always be a top-level domain name, which
includes “com”, “edu”, “gov”, “org”, “net”, “mil”, or one of the
two-letter country codes. The use of anything else as the first
component of these names is not allowed.

Constructing iSCSI names using the eui. format

The iSCSI eui. naming format allows a naming authority to use IEEE
EUI-64 identifiers in constructing iSCSI names. The details of
constructing EUI-64 identifiers are specified by the IEEE
Registration Authority (see [EUI64]).

Example iSCSI name:

Type EUI-64 identifier (ASCII-encoded hexadecimal)
| || |

iSCSI Discovery

The goal of iSCSI discovery is to allow an initiator to find the
targets to which it has access, and at least one address at which
each target may be accessed. This should generally be done using as
little configuration as possible. The iSCSI discovery mechanisms
listed here only deal with target discovery and one still needs
to use the SCSI protocol for LUN discovery. In order for an iSCSI
initiator to establish an iSCSI session with an iSCSI target, the
initiator needs the IP address, TCP port number and iSCSI target name information.

iSCSI supports the following discovery mechanisms:

a. Static Configuration: This mechanism assumes that the IP address,
TCP port and the iSCSI target name information are already
available to the initiator. The initiators need to perform no
discovery in this approach. The initiator uses the IP address and
the TCP port information to establish a TCP connection, and it
uses the iSCSI target name information to establish an iSCSI
session. This discovery option is convenient for small iSCSI

b. SendTargets: This mechanism assumes that the target’s IP address
and TCP port information are already available to the initiator.
The initiator then uses this information to establish a discovery
session to the Network Entity (IP address). The initiator then subsequently issues the SendTargets text command to query
information about the iSCSI targets available at the particular
Network Entity (IP address).

c. Zero-Configuration: This mechanism assumes that the initiator does
not have any information about the target. In this option, the
initiator can either multicast discovery messages directly to the
targets or it can send discovery messages to storage name servers.
Currently, the main discovery frameworks available are
SLP and iSNS. (Not supported in the first release of ESX 3.)]]>

Windows Offline Update is AWESOME!

It’s downloadable here:

It’s so cool! It’s also very useful. You don’t need to be on the network when you do the updating. If you use Windows and get on a public network, you most certainly will get a virus before you even get fully updated! This software has saved me so much time! Almost like downloading a service pack and installing it, it pulls all of the Windows updates from Microsoft’s website and puts them into a big folder or iso for you so that you can just install an OS, pop in the cd that you made with this and just install all of the patches in one fell swoop. Awesome! … and FREE!


Sushi Dai is way better than Sushi Yamato in Tsukiji (Japan)

It’s really ridiculous how different the two sushi places are in terms of service while they’re right next to each other and look the same as well. They both have similar amounts of traffic as well.

Here’s a good review of Sushi Dai: … 4654633758

Another review for Sushi Dai: … -BR-1.html

    Sushi Dai had better service as even though we did the set (omakase), we were asked if there was anything that we didn’t eat. (I don’t like octopus or uni.)
    The egg in at Sushi Dai was hot and fresh where the one at Yamato was cold and looked like it sat there for a while.
    At Sushi Dai, we were given the items one at a time and told what they were. At Yamato, they just kept throwing stuff in front of us making it feel rushed.
    At Sushi Dai, we were offered different tastes for example, the choice between salt and soy sauce and a citrus flavored piece whereas at Yamato, they were all soy sauce flavored.
    At Sushi Dai, I was able to use chopsticks to eat all of my pieces. At Yamato, my pieces kept falling apart.


reset root password in mysql

DBS” wrote:

> I have a problem, It’s been months since I used MySQL and (I believe) I had

> set it up with a root password. Now I can’t log on to MySQL as root MySQL

> user and create a new user or manage an existing user (I can log onto server

Familiar situation. :)

Do so:

service mysql stop

wait until MySQL shuts down. Then run

mysqld_safe –skip-grant-tables &

then you will be able to login as root with no password.

mysql -uroot mysql

In MySQL command line prompt issue the following command:

UPDATE user SET password=PASSWORD(“abcd”) WHERE user=”root”;


At this time your root password is reset to “abcd” and MySQL will now

know the privileges and you’ll be able to login with your new password:

mysql -uroot -pabcd mysql

Wasabi & Ginger – San Francisco, CA

Wasabi & Ginger
2299 Van Ness Avenue
San Francisco, CA 94109

This is yet another Chinese owned Japanese restaurant. The food isn’t bad.

Spider roll was awesome +10

Nabeyaki Udon was okay +5

Raw fish was okay, but not fresh as I thought it would be according to other reviews -5

Bathroom was typical, but faucet was broken -1

No “irashaimase” (Welcome at the door) -1

Waitress didn’t know what shichimi was (flavor for Udon) -1

Boss was around, so service was good +5

Free ice cream! +5

So overall, I’d say, this place is pretty good. It deserves 4 stars.