Anyway it looks like MySQL is a dependency for the install process so install MySQL server and your laughing

yum install mysql-server -y

Here's a sample /etc/smb.conf I use when I need to deploy a nice simple NAS box.
Start a nice simple distro, I like CentOS myself.
Install samba
# yum install samba

Create a new system user and set a password. This user is used for ownership and permissions of the shares presented by Samba.
# useradd nas-user
# passwd nas-user

Create a samba password for the new user
# smbpasswd -a nas-user

Create a directory somewhere for storage of files used by the samba share
# mkdir /storage1

Change ownership for the new directory to the new user. All files for the share will be owned by this user.
# chown nas-user:nas-user /storage1

Now edit /etc/samba/smb.conf

[global]
	workgroup = Sales-Department
	server string = "Some comment, visible only from network browser in Windows"
	netbios name = FileServer

	# Disable printers and faxes
	load printers = no
	disable spoolss = yes
	printcap name = /dev/null

	# Only allow connections from 192.168.1.0 subnet. Deny everything else
	hosts allow = 192.168.1.0/24
	hosts deny = 0.0.0.0/0

	security = user
	passdb backend = tdbsam

[backups-storage]
	comment = Storage for backups and archives
	path = /storage0
	force user = backups-user
	force group = backups-user
	read only = No
	guest ok = Yes

Now restart the samba service.
# service smb restart

Problem: Installer can’t create my.ini properly when you use anything but the default settings during the initial configuration soo…

Solution:

1.Remove Instance
2. Uninstall MySQL
3. Delete %alluserprofile%\Application Data\MySQL
4. Delete rest of %programfiles%\MySQL
5. Reboot  (not 100% sure if required but Windows likes reboots)
6. Reinstallation of MySQL
7. Creation of MySQL Instance with default values
8. Reconfiguration of the Instance with the Configuration Tool

[HKEY_USERS\.DEFAULT\Control Panel\Colors]
“ActiveBorder”=”212 208 200″
“ActiveTitle”=”10 36 106″
“AppWorkSpace”=”128 128 128″
“Background”=”102 111 116″
“ButtonAlternateFace”=”181 181 181″
“ButtonDkShadow”=”64 64 64″
“ButtonFace”=”212 208 200″
“ButtonHilight”=”255 255 255″
“ButtonLight”=”212 208 200″
“ButtonShadow”=”128 128 128″
“ButtonText”=”0 0 0″
“GradientActiveTitle”=”166 202 240″
“GradientInactiveTitle”=”192 192 192″
“GrayText”=”128 128 128″
“Hilight”=”10 36 106″
“HilightText”=”255 255 255″
“HotTrackingColor”=”0 0 128″
“InactiveBorder”=”212 208 200″
“InactiveTitle”=”128 128 128″
“InactiveTitleText”=”212 208 200″
“InfoText”=”0 0 0″
“InfoWindow”=”255 255 225″
“Menu”=”212 208 200″
“MenuText”=”0 0 0″
“Scrollbar”=”212 208 200″
“TitleText”=”255 255 255″
“Window”=”255 255 255″
“WindowFrame”=”0 0 0″
“WindowText”=”0 0 0″

I use vsftp which needs to be modified a little bit for this to work.

edit /etc/vsftp/vsftpd.conf   (on CentOS, your distro may store the .conf somewhere else)

You’ll need to change “local_umask” from 022 to 0007. Save and restart the service

/etc/init.d/vsftpd restart

# Add 2 new groups, one for read only users and the other will be for the read-write guys

groupadd ftp-readonly
groupadd ftp-readwrite

# Create a document store where all FTP users will access once they are logged in. always a good idea to put it in /home

mkdir /home/ftp-docs
chmod 775 /home/ftp-docs/
chown root:ftp-readwrite /home/ftp-docs

# Add the new users

useradd -g ftp-readwrite -d /home/ftp-docs user1
useradd -g ftp-readwrite -d /home/ftp-docs user2
useradd -g ftp-readonly -d /home/ftp-docs user3

# Set the users password

passwd user1
passwd user2

And your done.

The reason you need to change the umask is when a new directory is created by a read-write user the permissions by default don’t give full write-write access, I believe it’s read-only (for other users in the group).

So user1 can create a directory but only user1 can remove it.

You will need to configure IP again if your using static addresses.

One line per static route please:

10.10.2.0/24 via 192.168.1.2 dev eth0

10.10.1.0/24 via 192.168.1.2 dev eth0

service network restart

Because we’re playing with filesystems I strongly recommend you only do this when both machines are booted off live CD’s. Trying to do a disk dump of a mounted volume is the doings of a mad man and will surely end up in data curruption.

dd if=/dev/sda ibs=32k obs=2k | ssh root@192.168.1.10 “dd of=/dev/sda obs=32k”

This will dump the content of your local disk, /dev/sda to a local disk on a remote machine, also /dev/sda in this case.

You will need root access on the remote machine.

I find this will very useful when migrating virtual machines where you can be sure the hardware on source and destination machines are the same.

Times like this you assume HA might just kick in, or maybe you should simply reboot the machine and tell everyone it was a hardware failure. Well there’s no need. Generally whats happened here is the management service has crashed resulted in you good people not being able to connect. But its generally safe to say that everything else on the host is running fine.

Solution: Log into the service console and type:

service mgmt-vmware restart

service vmware-vpxa restart

Sometimes the mgmt-vmware service can take a few minutes to restart, try to resist the urge to control+c while the service is stopping. Once restarted go back to VirtualCenter and wait, and wait, and wait. It can take 2-4 minutes before the host magically appears back again.