Wednesday, September 26, 2012

GParted to resize your existing hard drive

See my other blog http://objectlayer.blogspot.ca/2012/09/gparted-to-resize-your-existing-hard.html

Windows has Minitool for sd card and for hard drive AOMEI
Partition the SD card in detail is here.
For the SD card is easier to do from PC most of laptop and desktop come with SD card reader. After partition and create uboot and uImage put it into target it could be phone or tablet or just a development target. The Minitool and Win32DiskImage make life much easier when create the new firmware on the SD card. Linux it is hard to remember all the commands.
At the end we read the SD card we should see 2 partitions at least for boot and kernel image:
kubuntu-vm:~/3.8.13-bone20_kernel_ubuntu12.04$ ls
boot  rootfs


kubuntu-vm:~/3.8.13-bone20_kernel_ubuntu12.04$ ls boot
MLO  u-boot.img  uEnv.txt


kubuntu-vm:~/3.8.13-bone20_kernel_ubuntu12.04$ ls rootfs
bin   dev  home  lost+found  mnt  proc  run   selinux  sys  usr
boot  etc  lib   media       opt  root  sbin  srv      tmp  var

kubuntu-vm:~/3.8.13-bone20_kernel_ubuntu12.04$ ls rootfs/lib/modules
3.8.13-bone20

this is the kernel version.

When load into the target it shows
root@ubuntu-armhf:/var/www# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 12.04.3 LTS
Release:        12.04
Codename:       precise
root@ubuntu-armhf:/var/www# uname -a
Linux ubuntu-armhf 3.8.13-bone20 #1 SMP Wed May 29 10:49:26 UTC 2013 armv7l armv7l armv7l GNU/Linux
root@ubuntu-armhf:/var/www#

Tuesday, September 25, 2012

How to bridge networking in VMware player

 In order to use Samba share between network (other machines) it has to be the same subnet and dedicated IP address it won't work in NAT so it requires the VM to have a bridge connection. The VMware has a problem with the bridge networking when switch to the bridge I cannot ping the other machine but with NAT it works.
Here is how to do it.
http://ciscoshizzle.blogspot.ca/2012/08/vmware-player-404-bridged-network.html
 VMWare Player 4.0.4 Bridged network Editor, vmnetcfg.exe
Not necessarily a Cisco post, but I came across a connectivity issue when building Cisco Unified Presence server vritual machine. I was building the virtual machine using a bridged network and for the life of me was unable to ping it from anywhere within my network. As always the solution was simple, but the research extensive.

The problem was that my host machine has multiple network interfaces as most machines do; loopback, wireless, and ethernet, if not more). Under the hood, vmware player uses vmnet0 as the virtual interface that bind to an interface on your host machine. Contrary to vmnet1 (used for host-only), and vmnet8 (used for NAT), vmnet0 is not displayed when going into your host's control panel. The problem with connectivity not working in bridged mode is that the vmnet0 interface was binding to the wrong host interface.

To change this (as it is set to automatic per default), you will need to obtain a file called "vmnetcfg.exe". For some reason, this file is NOT installed when installing vmplayer.

Obtain it as follows:

extract the installer file (for 4.0.4 ; VMware-player-4.0.4-744019.exe), from a command prompt;

 C:\Temp\vmware>VMware-player-4.0.4-744019.exe /e extract

this has just extracted the installer file in a directory called "extract".

Browse to the extract directory and search for an archive called "network". The vmnetcfg.exe file is in it, so just extract it out of that archive, like you normally would.  Stick the vmnetcfg.exe file into

C:\Program Files (x86)\VMware\VMware Player

 Now it can be run and edited as the screen shot below shows, manually bridge it to the network interface you want, changing it is instantaneous.
NEED TO CHANGE TO BRIDGE NETWORKING BEFORE STARTS VM for some reasons it does not work after the VM is launched. We should be able to change it to either NAT or Bridge network.

Thursday, September 6, 2012