moving opensuse to a new machine

chroot to the openSUSE root and run mkinitrd

mkinitrd Description:

mkinitrd creates an initial image used by the kernel for preloading the block device modules (such as IDE, SCSI or RAID) which are needed to access the root filesystem. mkinitrd automatically loads filesystem modules (such as ext3 and jbd), IDE modules, all scsi_hostadapter entries in /etc/modprobe.conf, and raid modules if the system’s root partition is on raid, which makes it simple to build and use kernels using modular device drivers.

Any module options specified in /etc/modprobe.conf are passed to the modules as they are loaded by the initial ramdisk.

The root filesystem used by the kernel is specified in the boot configuration file, as always. The traditional root=/dev/hda1 style device specification is allowed. If a label is used, as in root=LABEL=rootPart the initrd will search all available devices for an ext2 or ext3 filesystem with the appropriate label, and mount that device as the root filesystem.

chroot Description:

Advertisements

VBOX — the headless horseman

Brevity of the day:

echo VBOXWEB_USER=user > /etc/default/virtualbox
echo # VBOXWEB_HOST=127.0.0.1 >> /etc/default/virtualbox

/etc/init.d/vboxweb-service start

chkconfig vboxweb-service on

init 6

OR this:

Manage your VirtualBox VMs via the web with phpVirtualBox

Generally speaking, if it is a web-based tool that starts with “php” (such as phpMyAdmin or phpLDAPadmin) you know that tool is going to make your administrative life a lot easier. Such is the case with a php-based tool created to help you manage all of your VirutalBox VMs from a single tool, from anywhere (so long as said “anywhere” is accessible from, you guessed it, anywhere).
I do use VirtualBox and was thrilled to come across phpVirtualBox. This tool is an AJAX implementation of the familiar VirtualBox user interface, so the minute you log in you will be instantly at home. Let’s take a look at how this tool is installed and used.
First things first
You need to make sure you have the latest VirtualBox installed as well as the Extension Pack. You can run phpVirtualBox with the 3.x release of VirtualBox, but there are a lot more features available in the 4.x release. You can download both from the VirtualBox download page. You will also need to have the PHP Soap extension. This can be installed by searching for the package php-soap in your Add/Remove Software tool. Once you have that installed, you are then ready to install and configure the phpVirtualBox application.
You will also have to have a working Apache server on the target machine. If you do not have that, you can go ahead and do a full LAMP install (which will cover a lot of your basics).
Installing phpVirtualBox
First download the compressed installation file from the download page. Make sure you download the release that is correct for the version of VirtualBox you have installed. What you need to do is to move that file into your web server’s document root and then unpack it. When you unpack the file you will have a newly created directory /var/www/phpvirtualbox-XXX Where XXX is the release number. I highly recommend you rename that directory to just /var/www/phpvirtualbox.
After you have the file unpacked, you need to do a minor configuration. This minor configuration is in the /var/www/phpvirtualbox/config.php. NOTE: Depending upon your distribution, your document root will differ.

You really only need configure the following options:

var $username
var $password

Make sure the username and password are for the user that will actually run the virtualbox application (so this won’t be a root user).
You are now ready to fire up daemon. To run this simply issue the command vboxwebsrv. This will run the daemon that will allow you to log into your phpvitualbox machine. NOTE: If you are using VirtualBox 4.x you can start the daemon with the command /etc/init.d/vbweb-service. There is one catch with that, you still want to run the web service as the user that will run VirtualBox.
Log in
Open up a browser and point it to http://ADDRESS_TO_SERVER/phpvirtualbox. When you do this you will see the VirtualBox interface embedded into your web browser. You can then use VirtualBox from within that web browser as if it were on the local machine!
Gotcha
If you are running VirtualBox 3.x you will need to take one other step (prior to starting up the daemon). Open up your terminal window and issue the command:
VBoxManage setproperty websrvauthlibrary null
Once that command has run, you can then start up the daemon and use VirtualBox through your webbrowser.

ref: http://www.torrent-invites.com/software/101718-manage-your-virtualbox-vms-via-web-phpvirtualbox.html

Special considerations:
SELinux Considerations

If SELinux is installed and you would like to keep it enabled, you may have to add a rule for vboxwebsrv.

Install semanage (yum install policycoreutils-python) and run the command below:

semanage port -a -t http_port_t -p tcp 18083

This will add the VirtualBox’s web service port (18083) to be accessible by a service running in an http context (eg. apache).
Arch Linux Considerations

In Arch Linux, be sure to edit /etc/php/php.ini, and uncomment the following lines:

;extension=json.so
;extension=soap.so

by removing the ‘;’ at the beginning of each. Then restart apache.
Suse Considerations

Due to the complex dance between VirtualBox and PAM configurations, you will have to disable authentication between vboxwebsrv and the OS by running the following command as the same user that runs VirtualBox on your system:

VBoxManage setproperty websrvauthlibrary null

Windows Considerations

phpVirtualBox’s location setting in config.php cannot be set to ‘localhost’ use 127.0.0.1 instead. E.g. http://127.0.0.1:18083/

ref: http://code.google.com/p/phpvirtualbox/wiki/Installation#SELinux_Considerations

Top 20 Linux system monitoring tools for every admin

ref: http://www.cyberciti.biz/tips/top-linux-monitoring-tools.html

Linux mounting an NFS .ISO to a directory

#step 1:
# mount -t nfs 192.168.255.15:/mnt/vol1/store4/iso1 /mnt/iso1

Ok, this way you’ll have all your ISO files at /mnt/iso1. Now, imagine you want to mount one of these ISOs in loopback:

#step 2:
# mount -o loop /mnt/isos/[isofilename].iso /tmp/blah
/mnt/isos/blah.iso: Permission denied

Permission denied??? Hmmm.. I got stuck with this problem for a bit the first time. Tried changing permissions and exporting parameters, Google, but no answer at all… then… fortunately…. I found it: -o loop,ro!

#step 2 (for real this itme):
# mount -o loop,ro /mnt/iso1/[isofilename].iso /tmp/blah

virtualbox opensuse

Update 4 April 2013 Tested & working in openSUSE 12.3

Introduction You can install the fully open source version or the Sun/Oracle version. The latter (Sun/Oracle) is significantly better IMHO. I only talk about the Sun/Oracle version here.

Install the Oracle VirtualBox RPM Add this repo, it contains the Oracle VirtualBox RPM and it will supply updates over time. It is currently the correct repo for openSUSE 11.4, 12.1, 12,2, 12.3 and Tumbleweed
Code:

Oracle VirtualBox openSUSE http://download.virtualbox.org/virtualbox/rpm/opensuse/11.4/

Important, read carefully: You will have a series of possible RPMs available in the package management GUI in Yast. Be very sure to install only the Oracle VirtualBox RPM, not the oss virtualbox RPM. GoTo Yast –> Software –> Software management and select the Oracle RPM. If dependency linkages attempt to install additional packages beginning virtualbox-guest or virtualbox-host kernel modules, then you have made a mistake. Install only the single RPM “VirtualBox”. Make sure you choose the latest version in the repo.

Additional RPMs You will also need these RPMs: kernel-devel, gcc, make. Install them in yast or run this zypper command (as root)
Code:

zypper in gcc make kernel-devel

Add your username to the vboxusers group VirtualBox permissions will not work properly until you do this. GoTo Yast –> Security and Users –> User and group management. Highlight and Edit you username. Select the Details tab and tick the box to add yourself to “vboxusers”. Then reboot to activate the changes.

Next: the Extension Pack This pack provides additiopnal functionality like USB and RDP support. GoTo the VirtualBox dot org download site https://www.virtualbox.org/wiki/Downloads and click the link for the Extension Pack. NB be sure to select the extension pack with the same version as your installed version of VirtualBox! Download the pack, a file with a name like Oracle_VM_VirtualBox_Extension_Pack-4.0.14-74382.vbox-extpack. Download the pack, then browse to it and click it with the mouse. That will cause it to be installed (provided the VirtualBox RPM has been installed first).

Each time you upgrade the VirtualBox RPM, you will have to go back to the Extension Pack download page and acquire and install the new Extension Pack to match the version number of the upgraded RPM.

Where’s the GUI? In KDE GoTo Kicker –> Applications –> System –> Virtual Machine (Oracle VM VirtualBox).

After a Kernel Upgrade in the openSUSE Host This is arguably a part of the installation of VirtualBox. When you have a kernel upgrade, after you reboot, you must run this command as root to recompile the kernel modules:
Code:

/etc/init.d/vboxdrv setup

If USB support fails: If the Guest VM does not detect USB devices, or if they are detected but “grayed” out in the menu bar, check that you added your username to the vboxusers group. Check that the file xx-vboxdrv.rules exists in the directory /etc/udev/rules.d/

That’s all folks. I only wanted to talk about the installation, which can be a bit tricky in the detail.

[PS: Tumbleweed only: if you’re a Tumbleweeder you might occasionally install an upgrade of the VirtualBox RPM with “zypper dup”. Just check that the earlier version of the RPM has uninstalled. Run “rpm -qa | grep VirtualBox” and make sure the earlier one has gone.]

Whatabout VM Tools??… try VirtualBox guest additions in the device menu of the machine itself. Link follows, will translate to CLI when time permits, link.

ref:
http://forums.opensuse.org/content/59-how-install-virtualbox-opensuse-11-4-12-1-tumbleweed.html

crafting MITM (Man-in-the-middle) redirects — via arp poisoning

Basic Linux bridging examples w/ iptables adjustments:
brctl addbr br0
brctl addif br0 eth0
brctl addif br0 eth1
ifconfig eth0 0.0.0.0 promisc up
ifconfig eth1 0.0.0.0 promisc up
ifconfig br0 netmask broadcast
iptables -A FORWARD -p all -i br0 -j ACCEPT
iptables -t mangle -A FORWARD -m physdev –physdev-in eth0 -j NFQUEUE –queue-num 0
iptables -t mangle -A FORWARD -m physdev –physdev-in eth1 -j NFQUEUE –queue-num 1

======
Tutorial #1 here:

Linux software (CLI) installations — via add repository — Google-chrome

64 bit:
zypper ar http://dl.google.com/linux/chrome/rpm/stable/x86_64 Google-Chrome

-OR-

32 bit:
zypper ar http://dl.google.com/linux/chrome/rpm/stable/i386 Google-Chrome

zypper ref
zypper in google-chrome-stable

+++++++++++

Chromium install (Gui:Yast) will rewrite into CLI later:
1- Open YaST, goto software repositories, click add button, choose community repositories from the choices, and click next. Now select Contrib repo and click OK.

2- Now open software management from YaST, and search for ‘chromium’ without quotes and mark it for installation, click Accept button and you are done.