This restaurant has the absolutely the most delicious Peking duck! I say, visit the place for the duck itself. It’s definitely worth driving a few miles for. They come with tortilla like wrapping paper instead of your typical bread – the skin is crispy and meat is juicy. In the bread, we put some hoisin sauce and cucumbers and green onions along with the meat/skin. The waiter was nice enough to give us a demonstration as well. The staff is very friendly and can speak Chinese, Japanese and English.
Aside from the duck, we’ve had other items on the menu that were quite good. I really liked the pot stickers and they seem to have a specialty called stuffed eggplants that other restaurants don’t seem to carry.
I’ll definitely visit the restaurant again should I be in Berkeley.
1) fdisk -l
this would show which device doesn’t have a partition.
2) dd if=/dev/sd(x) of=/tmp/dump_sdx.txt count=100 bs=1024
file /tmp/dump_sdx.txt shows x86 boot sector.
strings /tmp/dump_sdx.txt shows some vmdk files
3) fdisk -lu /dev/sd(x) shows that there are no partitions on the disk.
4) ran fdisk /dev/sd(x). created new partition spanning entire lun and then used partition type fb.
5) run “vmkfstools -V”
<![CDATA[pulled from: http://www.cisl.ucar.edu/nets/intro/sta … s/ntp.html
NTP (Pete’s notes)
To get ntpd working, get a version that’s at or later than
ntp-stable-4.2.0a-20040617. Gunzip it, untar it, run ./configure,
make and make install. I couldn’t RPM-delete the ntp that’s
installed, so I hand-deleted all the ntp* binaries in
/usr/sbin. I know this isn’t optimal. Then I
hand-edited the /etc/init.d/ntpd, deleted the
/etc/sysconfig/ntpd, and made
/etc/sysconfig/iptables allow ntp packets. Then
I edited /etc/ntp/conf to camment out all the
restrict 18.104.22.168 mask 255.255.0.0
,,,and waited a few minutes for the router’s broadcast packets to
be heard. Then I did ntpq and “peers” and saw the router listed.
One other possible problem: if your machine’s time is too far
out of sync with the router’s, ntpd won’t correct it. To force
synchronization, do “ntpdate mlra”.
The ntp.conf file has a section that configures
a fake driver. If you leave that on, you’ll see the “LOCAL”
peer. When you comment it out, ntpq “peers” will give
<![CDATA[This procedure will build the kernel like Redhat does except make some changes important for VMware. You can make many more changes and make the kernel run better and faster, but that's not the point. We're trying to stay as "Redhat" as possible. You may not get support from Redhat for using this kernel, so it's probably a good idea to keep your original kernel as well so when you have a support call to open with Redhat, just boot into their kernel to prove that the kernel isn't the problem (hopefully).
NOTE: This may not work with systems with AMD processors – I tried it on an Athlon64 X4200 and it failed to install a patch – I commented that patch out and the compile failed somewhere further down the line and I just gave up at that point.
VMware ESX 3.0.x supports LSILogic for it’s SCSI controller, so there is no longer a need to compile into the BusLogic driver. You can skip step3.
Anyways, here’s how you do it:
1) download kernel source. I got mine from:
ftp://ftp.redhat.com/pub/redhat/linux/u … EL.src.rpm
2) install source:
rpm -i kernel-2.6.9-34.0.2.EL.src.rpm
(You may need to run “mkdir -p /usr/src/redhat/SOURCES”. If that’s the case, then I’d run “mkdir -p /usr/src/redhat/SOURCES /usr/src/redhat/SPEC /usr/src/redhat/RPMS /usr/src/redhat/SRPMS /usr/src/redhat/BUILD” just in case. )
3) edit files to include BusLogic driver:
edit the following files:
replace all instances of:
# CONFIG_SCSI_BUSLOGIC is not set
4) make a patch change the Internal kernel timer frequency.
tar jxvf linux-2.6.9.tar.bz2
mkdir -p linux-2.6.9-vmware/include/asm-i386
cp -pr linux-2.6.9/include/asm-i386/param.h linux-2.6.9-vmware/include/asm-i386/param.h
# define HZ 1000 /* Internal kernel timer frequency */
# define HZ 100 /* Internal kernel timer frequency */
diff -urN linux-2.6.9/include/asm-i386/param.h linux-2.6.9-vmware/include/asm-i386/param.h > vmware.patch
add the patch to the spec file list
added to where it lists the patches (your numbers may vary):
I just made it Patch 5 since it doesn’t exist:
so after the line: Patch4: linux-2.6.9-selected-ac-bits.patch
and where it does the prep after the line: %patch4 -p1
5) change the release of your kernel to differentiate:
open the file: kernel-2.6.spec and change:
%define release 34.0.2.EL
%define release 34.0.2.EL.vmware
6) build the rpm.
rpmbuild -ba –target=i686 /usr/src/redhat/SPECS/kernel-2.6.spec
You could use
rpmbuild -bb –target=i686 /usr/src/redhat/SPECS/kernel-2.6.spec
if you only need the binary rpms, but since we modified the source, I like to use ba, so I can reuse the source rpm should I need to compile again.]]>
For the update4 (20060605) distro, the kernel version is 2.6.9-39, so the buslogic driver on VMware’s site doesn’t work anymore. You can use the one attached, but it’s not supported by VMware. Install Linux by following the instructions on their site.
This is obviously not supported by VMware, Inc. There’s also no guarantee that your VM will be stable, but I’d bet that it would be.
<![CDATA[Here are the symptoms:
Error received when mounting
[[email protected] root]# mount /dev/cdrom /mnt/cdrom/
mount: /dev/cdrom: can’t read superblock
Apr 27 09:40:06 wesx3 modprobe: modprobe: Can’t locate module ide-cd
Fix with the following:
1) remove the line from /etc/vmware/esx.conf by running:
nano /boot/kernelAppend = “hda=ide-scsi”
2) remove hda=ide-scsi from /etc/grub.conf using nano again:
3) reboot the machine.
http://www.wagerline.com – my first couple days of this was 9 for 9! the number has dropped off a bit, but still ahead … keep it rollin’!
You can run these commands:
esxcfg-vswitch -A serviceconsole vSwitch0
esxcfg-vswif -a -i 192.168.0.2 -n 255.255.255.0 -p serviceconsole vswif0
That should be it. The new interface is vswif0 rather than eth0.
This problem is common among upgrades that have 2 nics shared between the service console / vmkernel.