Slitaz -- webcam

root@slitaz:~# export LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so
root@slitaz:~# mplayer tv:// -tv driver=v4l2:width=320:height=240:device=/dev/video0 -vo x11

# tazpkg get-install linux-video
# tazpkg get-install libv4l
# tazpkg get-install v4l-dvb
# tazpkg get-install usbutils

root@slitaz:~# lsusb | grep -i logitech
Bus 003 Device 002: ID 046d:08f0 Logitech, Inc. QuickCam Messenger
Bus 004 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser

root@slitaz:~# tazhw detect-usb

Detected USB devices Kernel modules
================================================================================
Camera
sh: gspca_stv06xx: unknown operand
! Missing module:  snd-usb-audio
gspca_stv06xx
quickcam_messenger
sed: unmatched '/'
================================================================================

root@slitaz:~# modprobe gspca_stv06xx
root@slitaz:~# modprobe snd-usb-audio
root@slitaz:~# lsmod | head
Module                  Size  Used by    Not tainted
snd_usb_audio          69944  0 
gspca_stv06xx          20920  0 
gspca_main             21112  1 gspca_stv06xx
videodev               32080  1 gspca_main
v4l1_compat            11120  1 videodev
i2c_core               17468  1 videodev
snd_usb_lib            13192  1 snd_usb_audio
snd_rawmidi            16920  1 snd_usb_lib
snd_seq_device          5544  1 snd_rawmidi
root@slitaz:~# dmesg | tail -12
STV06xx: Configuring camera
STV06xx: st6422 sensor detected
STV06xx: Initializing camera
input: STV06xx as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/input/input3
gspca: video0 created
gspca: found int in endpoint: 0x82, buffer_len=1, interval=16
STV06xx: Probing for a stv06xx device
gspca: probing 046d:08f0
STV06xx: Probing for a stv06xx device
gspca: probing 046d:08f0
usbcore: registered new interface driver STV06xx
STV06xx: registered
root@slitaz:~# ls -l /dev/video*
crw-rw----    1 root     video     81,   0 Jun 29 22:35 /dev/video0
root@slitaz:~#
root@slitaz:~# export LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so
root@slitaz:~# tazhw setup webcam
COMMAND OPTIONS: webcam
installing pkg: hal-info
[..]
Installation of : mplayer-svn-30817
================================================================================
Copying mplayer-svn-30817...                                         [ OK ]
Extracting mplayer-svn-30817... 6328 blocks
Extracting the pseudo fs... (lzma) 20478 blocks
Installing mplayer-svn...                                            [ OK ]
Removing all tmp files...                                            [ OK ]
================================================================================
mplayer-svn (30817) is installed.

root@slitaz:~# Creating config file: /root/.mplayer/config
MPlayer SVN-r30817-4.4.1 (C) 2000-2010 MPlayer Team
MMX supported but disabled
MMX2 supported but disabled
SSE supported but disabled
SSE2 supported but disabled

Playing tv://.
TV file format detected.
Selected driver: v4l2
 name: Video 4 Linux 2 input
 author: Martin Olschewski 
 comment: first try, more to come ;-)
v4l2: your device driver does not support VIDIOC_G_STD ioctl, VIDIOC_G_PARM was used instead.
Selected device: Camera
 Capabilites:  video capture  read/write  streaming
 supported norms:
 inputs: 0 = STV06xx;
 Current input: 0
 Current format: RGB24
tv.c: norm_from_string(pal): Bogus norm parameter, setting default.
v4l2: ioctl enum norm failed: Invalid argument
Error: Cannot set norm!
Selected input hasn't got a tuner!
v4l2: Cannot get fps
v4l2: ioctl set mute failed: Invalid argument
v4l2: ioctl query control failed: Invalid argument
v4l2: ioctl query control failed: Invalid argument
==========================================================================
Opening video decoder: [raw] RAW Uncompressed Video
Movie-Aspect is undefined - no prescaling applied.
VO: [x11] 320x240 => 320x240 Planar YV12 
[swscaler @ 0x8e7df10]No accelerated colorspace conversion found from yuv420p to bgra.
[swscaler @ 0x8e7df10]using unscaled yuv420p -> bgra special converter
Selected video codec: [rawyv12] vfm: raw (RAW YV12)
==========================================================================
Audio: no sound
Starting playback...
libv4l2: error dequeuing buf: Invalid argument
v4l2: ioctl set mute failed: Invalid argument
v4l2: 170 frames successfully processed, 253 frames dropped.

Exiting... (Quit)
root@slitaz:~# 

----
http://forum.slitaz.org/index.php/discussion/207/webcam-support-in-slitaz%3A-howto

http://cateee.net/lkddb/web-lkddb/USB_GSPCA.html

CONFIG_USB_GSPCA: GSPCA based webcams
General informations

The Linux kernel configuration item CONFIG_USB_GSPCA:

* prompt: GSPCA based webcams
* type: tristate
* depends on: CONFIG_VIDEO_V4L2
* defined in drivers/media/video/gspca/Kconfig
* found in Linux Kernels: from 2.6.27 release still available on 2.6.34 release
* module created: gspca_main
[..]

http://lxr.linux.no/#linux+v2.6.30.6/Documentation/video4linux/gspca.txt
LXR linux/Documentation/video4linux/gspca.txt History Print
1List of the webcams known by gspca.
2
3The modules are:
4 gspca_main main driver
5 gspca_xxxx subdriver module with xxxx as follows
6
7xxxx vend:prod
.

Slitaz -- kernel module

Extract From
http://doc.slitaz.org/en:guides:bluetooth
[..]
At the moment I am writing this guide the rfcomm module of Slitaz is compiled without tty support. You can check if this is the case with the following commands:

root@slitaz:/home/tux# zcat /proc/config.gz | grep RFCOMM
CONFIG_BT_RFCOMM=m
# CONFIG_BT_RFCOMM_TTY is not set
root@slitaz:/home/tux#

If CONFIG_BT_RFCOMM_TTY is not =y you must recompile the module with tty support. Install linux-source:

tazpkg get-install linux-source

cd in /usr/src/linux-`uname -r`/ and give this command:

make CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y M=net/bluetooth/rfcomm

This will build only the rfcomm module with tty support. You will find it in /usr/src/linux-`uname -r`/net/bluetooth/rfcomm/rfcomm.ko. Now you can delete the old rfcomm module and replace it with your module:

rm /lib/modules/`uname -r`/kernel/net/bluetooth/rfcomm/rfcomm.ko.gz
cp /usr/src/linux-`uname -r`/net/bluetooth/rfcomm/rfcomm.ko /lib/modules/`uname -r`/kernel/net/bluetooth/rfcomm/
depmod -a
[..]

Slitaz -- gtkam / gphoto2

gtkam is a graphical application based on GTK+ for digital still cameras supported by gphoto2. (http://www.gphoto.org/)

Introducing gPhoto2

gPhoto2 is a free, redistributable, ready to use set of digital camera software applications for Unix-like systems, written by a whole team of dedicated volunteers around the world. It supports more than 1200 cameras
[..]
Newer libgphoto2 versions also support Media Transfer Protocol (MTP) based media players since their communications protocol is based on the Picture Transfer Protocol (PTP).

gtkam-0.1.12-2.4.tazpkg
libexif-gtk5-0.3.5-3+b1.tazpkg

root@slitaz-3:~# tazpkg info gtkam

Tazpkg information
================================================================================
Package    : gtkam
Version    : 0.1.12-2.4
Category   : misc
Short desc : GTK+ application for digital still cameras
Maintainer : nobody@slitaz.org
Depends    : atk cairo-xcb expat fontconfig freetype glib gtk+ libexif libgio libgphoto2 libpng libtool libusb libusb-compat libxcb pango pixman xcb-util xorg-libX11 xorg-libXau xorg-libXcomposite xorg-libXcursor xorg-libXdamage xorg-libXdmcp xorg-libXext xorg-libXfixes xorg-libXi xorg-libXinerama xorg-libXrandr xorg-libXrender zlib
Web site   : http://packages.debian.org/search?keywords=gtkam
================================================================================

root@slitaz-3:~# lsusb -v
[..]
Bus 001 Device 008: ID 040a:0597 Kodak Co. Digital Camera
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x040a Kodak Co.
  idProduct          0x0597 Digital Camera
  bcdDevice            1.00
  iManufacturer           1 Eastman Kodak Company
  iProduct                2 KODAK EASYSHARE V1073 Digital Camera
  iSerial                 3 xxxxxx
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         6 Imaging
      bInterfaceSubClass      1 Still Image Capture
      bInterfaceProtocol      1 Picture Transfer Protocol (PIMA 15470)
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval              16
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

Slitaz -- hibernate / STD

# echo shutdown > /sys/power/disk
# echo disk > /sys/power/state

suspend to disk (STD)
suspend to RAM (STR)

shutdown: save state in linux, then tell bios to powerdown
platform: save state in linux, then tell bios to powerdown and blink
"suspended led"

"platform" is actually right thing to do where supported, but
"shutdown" is most reliable (except on ACPI systems).

Hibernation (aka 'suspend to disk') (HIBERNATION)

Enable the suspend to disk (STD) functionality, which is usually
called "hibernation" in user interfaces. STD checkpoints the
system and powers it off; and restores that checkpoint on reboot.

You can suspend your machine with 'echo disk > /sys/power/state'
after placing resume=/dev/swappartition on the kernel command line
in your bootloader's configuration file.

Alternatively, you can use the additional userland tools available
from [http://suspend.sf.net].

In principle it does not require ACPI or APM, although for example
ACPI will be used for the final steps when it is available. One
of the reasons to use software suspend is that the firmware hooks
for suspend states like suspend-to-RAM (STR) often don't work very
well with Linux.

It creates an image which is saved in your active swap. Upon the next
boot, pass the 'resume=/dev/swappartition' argument to the kernel to
have it detect the saved image, restore memory state from it, and
continue to run as before. If you do not want the previous state to
be reloaded, then use the 'noresume' kernel command line argument.
Note, however, that fsck will be run on your filesystems and you will
need to run mkswap against the swap partition used for the suspend.

It also works with swap files to a limited extent (for details see
[file:Documentation/power/swsusp-and-swap-files.txt]).

Right now you may boot without resuming and resume later but in the
meantime you cannot use the swap partition(s)/file(s) involved in
suspending. Also in this case you must not use the filesystems
that were mounted before the suspend. In particular, you MUST NOT
MOUNT any journaled filesystems mounted before the suspend or they
will get corrupted in a nasty way.

For more information take a look at [file:Documentation/power/swsusp.txt].


/usr/src/linux-2.6.30.6-slitaz/Documentation/power/basic-pm-debugging.txt

basic-pm-debugging.txt

Debugging hibernation and suspend
(C) 2007 Rafael J. Wysocki , GPL

1. Testing hibernation (aka suspend to disk or STD)

To check if hibernation works, you can try to hibernate in the "reboot" mode:

# echo reboot > /sys/power/disk
# echo disk > /sys/power/state

and the system should create a hibernation image, reboot, resume and get back to
the command prompt where you have started the transition. If that happens,
hibernation is most likely to work correctly. Still, you need to repeat the
test at least a couple of times in a row for confidence. [This is necessary,
because some problems only show up on a second attempt at suspending and
resuming the system.] Moreover, hibernating in the "reboot" and "shutdown"
modes causes the PM core to skip some platform-related callbacks which on ACPI
systems might be necessary to make hibernation work. Thus, if you machine fails
to hibernate or resume in the "reboot" mode, you should try the "platform" mode:

# echo platform > /sys/power/disk
# echo disk > /sys/power/state

which is the default and recommended mode of hibernation.

Unfortunately, the "platform" mode of hibernation does not work on some systems
with broken BIOSes. In such cases the "shutdown" mode of hibernation might
work:

# echo shutdown > /sys/power/disk
# echo disk > /sys/power/state

(it is similar to the "reboot" mode, but it requires you to press the power
button to make the system resume).

If neither "platform" nor "shutdown" hibernation mode works, you will need to
identify what goes wrong.

a) Test modes of hibernation

To find out why hibernation fails on your system, you can use a special testing
facility available if the kernel is compiled with CONFIG_PM_DEBUG set. Then,
there is the file /sys/power/pm_test that can be used to make the hibernation
core run in a test mode. There are 5 test modes available:

freezer
- test the freezing of processes

devices
- test the freezing of processes and suspending of devices

platform
- test the freezing of processes, suspending of devices and platform
global control methods(*)

processors
- test the freezing of processes, suspending of devices, platform
global control methods(*) and the disabling of nonboot CPUs

core
- test the freezing of processes, suspending of devices, platform global
control methods(*), the disabling of nonboot CPUs and suspending of
platform/system devices

(*) the platform global control methods are only available on ACPI systems
and are only tested if the hibernation mode is set to "platform"

To use one of them it is necessary to write the corresponding string to
/sys/power/pm_test (eg. "devices" to test the freezing of processes and
suspending devices) and issue the standard hibernation commands. For example,
to use the "devices" test mode along with the "platform" mode of hibernation,
you should do the following:

# echo devices > /sys/power/pm_test
# echo platform > /sys/power/disk
# echo disk > /sys/power/state

Then, the kernel will try to freeze processes, suspend devices, wait 5 seconds,
resume devices and thaw processes. If "platform" is written to
/sys/power/pm_test , then after suspending devices the kernel will additionally
invoke the global control methods (eg. ACPI global control methods) used to
prepare the platform firmware for hibernation. Next, it will wait 5 seconds and
invoke the platform (eg. ACPI) global methods used to cancel hibernation etc.

Writing "none" to /sys/power/pm_test causes the kernel to switch to the normal
hibernation/suspend operations. Also, when open for reading, /sys/power/pm_test
contains a space-separated list of all available tests (including "none" that
represents the normal functionality) in which the current test level is
indicated by square brackets.

Generally, as you can see, each test level is more "invasive" than the previous
one and the "core" level tests the hardware and drivers as deeply as possible
without creating a hibernation image. Obviously, if the "devices" test fails,
the "platform" test will fail as well and so on. Thus, as a rule of thumb, you
should try the test modes starting from "freezer", through "devices", "platform"
and "processors" up to "core" (repeat the test on each level a couple of times
to make sure that any random factors are avoided).

If the "freezer" test fails, there is a task that cannot be frozen (in that case
it usually is possible to identify the offending task by analysing the output of
dmesg obtained after the failing test). Failure at this level usually means
that there is a problem with the tasks freezer subsystem that should be
reported.

If the "devices" test fails, most likely there is a driver that cannot suspend
or resume its device (in the latter case the system may hang or become unstable
after the test, so please take that into consideration). To find this driver,
you can carry out a binary search according to the rules:
- if the test fails, unload a half of the drivers currently loaded and repeat
(that would probably involve rebooting the system, so always note what drivers
have been loaded before the test),
- if the test succeeds, load a half of the drivers you have unloaded most
recently and repeat.

Once you have found the failing driver (there can be more than just one of
them), you have to unload it every time before hibernation. In that case please
make sure to report the problem with the driver.

It is also possible that the "devices" test will still fail after you have
unloaded all modules. In that case, you may want to look in your kernel
configuration for the drivers that can be compiled as modules (and test again
with these drivers compiled as modules). You may also try to use some special
kernel command line options such as "noapic", "noacpi" or even "acpi=off".

If the "platform" test fails, there is a problem with the handling of the
platform (eg. ACPI) firmware on your system. In that case the "platform" mode
of hibernation is not likely to work. You can try the "shutdown" mode, but that
is rather a poor man's workaround.

If the "processors" test fails, the disabling/enabling of nonboot CPUs does not
work (of course, this only may be an issue on SMP systems) and the problem
should be reported. In that case you can also try to switch the nonboot CPUs
off and on using the /sys/devices/system/cpu/cpu*/online sysfs attributes and
see if that works.

If the "core" test fails, which means that suspending of the system/platform
devices has failed (these devices are suspended on one CPU with interrupts off),
the problem is most probably hardware-related and serious, so it should be
reported.

A failure of any of the "platform", "processors" or "core" tests may cause your
system to hang or become unstable, so please beware. Such a failure usually
indicates a serious problem that very well may be related to the hardware, but
please report it anyway.

b) Testing minimal configuration

If all of the hibernation test modes work, you can boot the system with the
"init=/bin/bash" command line parameter and attempt to hibernate in the
"reboot", "shutdown" and "platform" modes. If that does not work, there
probably is a problem with a driver statically compiled into the kernel and you
can try to compile more drivers as modules, so that they can be tested
individually. Otherwise, there is a problem with a modular driver and you can
find it by loading a half of the modules you normally use and binary searching
in accordance with the algorithm:
- if there are n modules loaded and the attempt to suspend and resume fails,
unload n/2 of the modules and try again (that would probably involve rebooting
the system),
- if there are n modules loaded and the attempt to suspend and resume succeeds,
load n/2 modules more and try again.

Again, if you find the offending module(s), it(they) must be unloaded every time
before hibernation, and please report the problem with it(them).

c) Advanced debugging

In case that hibernation does not work on your system even in the minimal
configuration and compiling more drivers as modules is not practical or some
modules cannot be unloaded, you can use one of the more advanced debugging
techniques to find the problem. First, if there is a serial port in your box,
you can boot the kernel with the 'no_console_suspend' parameter and try to log
kernel messages using the serial console. This may provide you with some
information about the reasons of the suspend (resume) failure. Alternatively,
it may be possible to use a FireWire port for debugging with firescope
(ftp://ftp.firstfloor.org/pub/ak/firescope/). On x86 it is also possible to
use the PM_TRACE mechanism documented in Documentation/s2ram.txt .

2. Testing suspend to RAM (STR)

To verify that the STR works, it is generally more convenient to use the s2ram
tool available from http://suspend.sf.net and documented at
http://en.opensuse.org/s2ram . However, before doing that it is recommended to
carry out STR testing using the facility described in section 1.

Namely, after writing "freezer", "devices", "platform", "processors", or "core"
into /sys/power/pm_test (available if the kernel is compiled with
CONFIG_PM_DEBUG set) the suspend code will work in the test mode corresponding
to given string. The STR test modes are defined in the same way as for
hibernation, so please refer to Section 1 for more information about them. In
particular, the "core" test allows you to test everything except for the actual
invocation of the platform firmware in order to put the system into the sleep
state.

Among other things, the testing with the help of /sys/power/pm_test may allow
you to identify drivers that fail to suspend or resume their devices. They
should be unloaded every time before an STR transition.

Next, you can follow the instructions at http://en.opensuse.org/s2ram to test
the system, but if it does not work "out of the box", you may need to boot it
with "init=/bin/bash" and test s2ram in the minimal configuration. In that
case, you may be able to search for failing drivers by following the procedure
analogous to the one described in section 1. If you find some failing drivers,
you will have to unload them every time before an STR transition (ie. before
you run s2ram), and please report the problems with them.


/usr/src/linux-2.6.30.6-slitaz/Documentation/power/swsusp.txt
[..]
You need to append resume=/dev/your_swap_partition to kernel command
line. Then you suspend by

echo shutdown > /sys/power/disk; echo disk > /sys/power/state

. If you feel ACPI works pretty well on your system, you might try

echo platform > /sys/power/disk; echo disk > /sys/power/state

. If you have SATA disks, you'll need recent kernels with SATA suspend
support. For suspend and resume to work, make sure your disk drivers
are built into kernel -- not modules. [There's way to make
suspend/resume with modular disk drivers, see FAQ, but you probably
should not do that.]

If you want to limit the suspend image size to N bytes, do

echo N > /sys/power/image_size

before suspend (it is limited to 500 MB by default).
[..]
Q: What is the difference between "platform" and "shutdown"?

A:

shutdown: save state in linux, then tell bios to powerdown

platform: save state in linux, then tell bios to powerdown and blink
"suspended led"

"platform" is actually right thing to do where supported, but
"shutdown" is most reliable (except on ACPI systems).

[..]

Slitaz -- hibernate

Env:
slitaz-3.0.iso in HD
pm-utils

五  6月 18 19:06:43 CST 2010: performing hibernate
六  6月 19 09:42:24 CST 2010: Awake.
六  6月 19 09:42:24 CST 2010: Running hooks for thaw

root@slitaz:~# tazpkg info pm-utils

Tazpkg information
================================================================================
Package    : pm-utils
Version    : 1.2.5
Category   : system-tools
Short desc : scripts that handle suspend and resume on behalf of HAL.
Maintainer : domcox@users.sourceforge.net
Depends    : hal-info
Web site   : http://pm-utils.freedesktop.org/
================================================================================

root@slitaz:~# cat /proc/cmdline 
root=/dev/sda7 acpi=off resume=/dev/sda6
root@slitaz:~# grep sda6 /proc/partitions
   8        6   10450251 sda6
root@slitaz:~# ls -l /sys/power
-rw-r--r--    1 root     root         4096 Jun 18 08:26 disk
-rw-r--r--    1 root     root         4096 Jun 18 08:27 image_size
-rw-r--r--    1 root     root         4096 Jun 18 08:27 resume
-rw-r--r--    1 root     root         4096 Jun 18 19:06 state
root@slitaz:~# cat /sys/power/* 
test testproc [shutdown] reboot 
524288000
8:6
disk
root@slitaz:~#

root@slitaz:~# cat /var/log/pm-suspend.log
Initial commandline parameters:
五 6月 18 19:06:43 CST 2010: Running hooks for hibernate.
/usr/lib/pm-utils/sleep.d/00auto-quirk hibernate hibernate: Adding quirks from HAL: --quirk-dpms-on --quirk-dpms-suspend --quirk-vbe-post --quirk-vbemode-restore --quirk-vbestate-restore --quirk-vga-mode-3
success.
/usr/lib/pm-utils/sleep.d/00logging hibernate hibernate: Linux slitaz 2.6.30.6-slitaz #1 SMP Sun Mar 28 16:39:51 CEST 2010 i686 unknown

Module                  Size  Used by    Not tainted
rtc                     9136  0 
vboxnetadp              6444  0 
vboxnetflt             14688  0 
vboxdrv               156152  2 vboxnetadp,vboxnetflt
tg3                    93600  0 
libphy                 16236  1 tg3
snd_hda_codec_realtek   179412  1 
snd_hda_intel          22020  1 
snd_hda_codec          49928  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep               5988  1 snd_hda_codec
snd_pcm                51780  2 snd_hda_intel,snd_hda_codec
snd_timer              16344  1 snd_pcm
snd                    43584  8 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore               5180  1 snd
snd_page_alloc          7256  2 snd_hda_intel,snd_pcm
              total         used         free       shared      buffers
  Mem:      2039472       584508      1454964            0       109332
 Swap:     10450240            0     10450240
Total:     12489712       584508     11905204
success.
/usr/lib/pm-utils/sleep.d/00powersave hibernate hibernate: not executable.
/usr/lib/pm-utils/sleep.d/01grub hibernate hibernate: not executable.
/usr/lib/pm-utils/sleep.d/49bluetooth hibernate hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/55NetworkManager hibernate hibernate: success.
/usr/lib/pm-utils/sleep.d/75modules hibernate hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/90clock hibernate hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq hibernate hibernate: success.
/usr/lib/pm-utils/sleep.d/95led hibernate hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video hibernate hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/99video hibernate hibernate: /usr/lib/pm-utils/sleep.d/99video: line 219: fgconsole: not found
success.
五  6月 18 19:06:43 CST 2010: performing hibernate
六  6月 19 09:42:24 CST 2010: Awake.
六  6月 19 09:42:24 CST 2010: Running hooks for thaw
/usr/lib/pm-utils/sleep.d/99video thaw hibernate: BusyBox v1.12.0 (2010-03-12 18:25:03 CET) multi-call binary

Usage: chvt N

Change the foreground virtual terminal to /dev/ttyN

deallocvt: VT_DISALLOCATE: Device or resource busy
Returned exit code 1.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video thaw hibernate: success.
/usr/lib/pm-utils/sleep.d/95led thaw hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq thaw hibernate: success.
/usr/lib/pm-utils/sleep.d/90clock thaw hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/75modules thaw hibernate: success.
/usr/lib/pm-utils/sleep.d/55NetworkManager thaw hibernate: success.
/usr/lib/pm-utils/sleep.d/49bluetooth thaw hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/01grub thaw hibernate: not executable.
/usr/lib/pm-utils/sleep.d/00powersave thaw hibernate: not executable.
/usr/lib/pm-utils/sleep.d/00logging thaw hibernate: success.
/usr/lib/pm-utils/sleep.d/00auto-quirk thaw hibernate: success.
root@slitaz:~# 

Slitaz -- gcin / help

gcin 使用手冊 (README.html)

root@slitaz:~# ls -l /usr/share/doc/gcin-1.4.9
-rw-r--r-- 1 root root 79789 Jun 17 00:58 Changelog.html
-rw-r--r-- 1 root root 56213 Jun 17 00:58 README.html
root@slitaz:~# cat /usr/share/gcin/script/html-browser
#!/bin/bash

#for i in firefox mozilla-firefox mozilla konqueror
for i in firefox mozilla-firefox mozilla konqueror midori opera
do
which $i >& /dev/null
if [ $? = 0 ]; then
UTF8ED=$i
break
fi
done

export LC_CTYPE=zh_TW.UTF-8
export LC_ALL=zh_TW.UTF-8

$UTF8ED $1
root@slitaz:~# cat /usr/share/gcin/script/utf8-edit
#!/bin/bash

PATH=$PATH:/opt/gnome/bin:/usr/local/bin

for i in madedit gedit leafpad kedit kate gvim
do
which $i >& /dev/null
if [ $? = 0 ]; then
UTF8ED=$i
break
fi
done

export LC_CTYPE=zh_TW.UTF-8
export LC_ALL=zh_TW.UTF-8

if [ $UTF8ED = 'gvim' ]; then
UTF8ED='gvim -f'
fi

$UTF8ED $1
root@slitaz:~#
.

Slitaz -- gcin-1.4.9

# mkdir -p /usr/lib/qt4/bin
# ln -fs /usr/bin/moc /usr/lib/qt4/bin/.

root@slitaz:~# tazpkg info gcin

Tazpkg information
================================================================================
Package : gcin
Version : 1.4.9
Category : utilities
Short desc : a GTK+ based input method platform for Chinese users
Maintainer : alanyih
Depends : xorg-libXtst bash
Build deps : bash gtk+-dev xorg-xextproto xorg-inputproto Qt4-dev
Web site : http://cle.linux.org.tw/trac
================================================================================

root@slitaz:~#


[..]
Building gcin with the receipt...
================================================================================

Executing strip on all files... [ OK ]
Copying the receipt... [ OK ]
Creating the list of files... [ OK ]
Creating md5sum of files... [ OK ]
Compressing the fs...
LZMA 4.57 Copyright (c) 1999-2007 Igor Pavlov 2007-12-06
11782 blocks
[ OK ]
Updating receipt sizes... [ OK ]
Creating full cpio archive... 2867 blocks
[ OK ]
Restoring original package tree... 11782 blocks
================================================================================
Package gcin (1.4.9) generated.
Size : 1.4M /home/slitaz/packages/gcin-1.4.9.tazpkg

root@slitaz:/home/slitaz/wok#
.

Slitaz -- smplayer / vob

root@slitaz:~# tazpkg info smplayer

Tazpkg information
================================================================================
Package : smplayer
Version : 0.6.8
Category : multimedia
Short desc : QT-based front-end for MPlayer
Maintainer : jozee@slitaz.org
Depends : mplayer-svn libQtCore libQtGui libQtXml gcc-lib-base
Build deps : mplayer-svn Qt4-dev qmake libQtCore libQtGui libQtXml libQtNetwork
Web site : http://smplayer.sourceforge.net/
================================================================================

root@slitaz:~# head -6 ~/.config/smplayer/smplayer.ini
[%General]
mplayer_bin=mplayer
driver\vo=x11
driver\ao=alsa
use_screenshot=true
screenshot_directory=/root/.config/smplayer/screenshots
root@slitaz:~#
.

Slitaz -- virtualbox-3.2.0 / slitaz-vbox.iso

tazlito emu-iso ( default -m 256 )

Qemu -m 512

tazlito emu-iso ( -m 512 )

slitaz-vbox.iso: based on slitaz-3.0.iso + virtualbox-3.2.0 + guestadditions + wenquanyi_10pt.pcf

# sed -i "s/-m 256/-m 512/" /etc/tazlito/tazlito.conf

root@slitaz:/home/slitaz/distro# ls -l
drwxr-xr-x    4 root     root         4096 Jun 10 12:37 rootcd
drwxr-xr-x   16 root     root         4096 Jun 10 12:37 rootfs
root@slitaz:/home/slitaz/distro# time tazlito gen-initiso

0 bytes saved in duplicate files.
Generating lzma'ed initramfs... 
LZMA 4.57  Copyright (c) 1999-2007 Igor Pavlov  2007-12-06

Filesystem size: 78.1M    486033 blocks
                 78.9M    

Computing md5...                                                     [ OK ]

Generating ISO image
================================================================================
Generating slitaz-201006111311.iso
Size of boot image is 4 sectors -> No emulation
 12.00% done, estimate finish Fri Jun 11 13:14:45 2010
 24.02% done, estimate finish Fri Jun 11 13:14:45 2010
 36.00% done, estimate finish Fri Jun 11 13:14:45 2010
 48.01% done, estimate finish Fri Jun 11 13:14:45 2010
 59.99% done, estimate finish Fri Jun 11 13:14:45 2010
 72.01% done, estimate finish Fri Jun 11 13:14:45 2010
 83.98% done, estimate finish Fri Jun 11 13:14:45 2010
 96.00% done, estimate finish Fri Jun 11 13:14:45 2010
Total translation table size: 2048
Total rockridge attributes bytes: 5420
Total directory bytes: 12288
Path table size(bytes): 64
Max brk space used 21000
41678 extents written (81 MB)
Creating hybrid ISO...                                               [ OK ]
Creating the ISO md5sum...                                           [ OK ]
================================================================================

Distro statistics (/home/slitaz/distro)
================================================================================
Build date      : 20100611 at 13:14:45
Packages        : 212
Rootfs size     : 257.5M
Initramfs size  : 78.9M
ISO image size  : 82.1M
================================================================================
Image is ready: slitaz-201006111311.iso

real    3m 3.44s
user    2m 56.55s
sys     0m 4.66s
root@slitaz:/home/slitaz/distro# ls -l
drwxr-xr-x    4 root     root         4096 Jun 10 12:37 rootcd
drwxr-xr-x   16 root     root         4096 Jun 10 12:37 rootfs
-rw-r--r--    1 root     root     85983232 Jun 11 13:14 slitaz-201006111311.iso
-rw-r--r--    1 root     root           58 Jun 11 13:14 slitaz-201006111311.md5
root@slitaz:/home/slitaz/distro# tazlito emu-iso slitaz-201006111311.iso &
root@slitaz:/home/slitaz/distro# 
Starting Qemu emulator:

qemu -m 256 slitaz-201006111311.iso


root@slitaz:/home/slitaz/distro# qemu -m 512 -cdrom slitaz-201006111311.iso &
root@slitaz:/home/slitaz/distro#
root@slitaz:/home/slitaz/distro# tail -2 /etc/tazlito/tazlito.conf 
# Qemu emulator options for command: emu-iso
QEMU_OPTS="-m 256"
root@slitaz:/home/slitaz/distro# sed -i "s/-m 256/-m 512/" /etc/tazlito/tazlito.conf
root@slitaz:/home/slitaz/distro# tail -2 /etc/tazlito/tazlito.conf 
# Qemu emulator options for command: emu-iso
QEMU_OPTS="-m 512"
root@slitaz:/home/slitaz/distro# tazlito
SliTaz Live Tool - Version: 3.0

Usage:  tazlito [command] [list|iso|flavor|compression] [dir|iso]
Commands: 

  usage           Print this short usage.
  stats           View Tazlito and distro configuration statistics.
  gen-config      Generate a new configuration file for a distro.
  configure       Configure the main config file or a specific tazlito.conf.
  gen-iso         Generate a new ISO from a distro tree.
  gen-initiso     Generate a new initramfs and ISO from the distro tree.
  list-flavors    List all available package lists on the mirror.
  gen-flavor      Generate a new live-CD description.
  gen-liveflavor  Generate a live-CD description from current system.
  show-flavor     Show live-CD description.
  get-flavor      Get a flavor's list of packages.
  upgrade-flavor  Update package list to the latest available versions.
  extract-flavor  Extract a (*.flavor) flavor into /home/slitaz/flavors.
  pack-flavor     Pack (and update) a flavor from /home/slitaz/flavors.
  check-list      Check a distro-packages.list for updates.
  extract-distro  Extract an ISO to a directory and rebuild LiveCD tree.
  gen-distro      Generate a Live distro and ISO from a list of packages.
  clean-distro    Remove all files generated by gen-distro.
  check-distro    Help to check if distro is ready to release.
  writeiso        Use running system to generate a bootable ISO (with /home).
  merge           Merge multiple rootfs into one iso.
  repack          Recompress rootfs into iso with maximum ratio.
  build-loram     Generate a live-CD for low ram systems.
  frugal-install  Frugal install in /boot/frugal from a distro or ISO.
  emu-iso         Emulate an ISO image with Qemu.
  burn-iso        Burn ISO image to a cdrom using Wodim.

root@slitaz:/home/slitaz/distro# 

Slitaz -- review / youtube

http://www.youtube.com/watch?v=y1a8_J8KDEU
OSGUIShow — April 13, 2010 — Review style Screencast about SliTaz GNU/Linux 3.0 a small fast 30MB Free Operating System. The OS has the Openbox with Joe's Window Manager GUI and I created the demonstration inside VirtualBox where I play with the environment and its software.
Original video production by the http://www.OSGUI.com Tech Show.

Fast Video Download (with SearchMenu) 3.0.8
by Bill Dettering
Download video files from popular sites like YouTube, Dailymotion, Break.com and more. 100% Free! In addition, our new SearchMenu feature makes it easier than ever to find popular videos and other information about any text you select.
https://addons.mozilla.org/en-US/firefox/addon/3590/

root@slitaz:~# cat /usr/share/applications/watchvideo.desktop
[Desktop Entry]
Encoding=UTF-8
Name=Watch Video
Icon=applications-multimedia
Exec=default-app gmplayer --install "mplayer-svn get-flash-plugin gecko-mediaplayer"
Type=Application
Categories=Multimedia;AudioVideo;Audio;Player;
root@slitaz:~#

Slitaz -- vboxadd-3.2.0 / seamless

seamless

Env:
HOST: slitaz-3.0.iso
GUEST: slitaz-3.0.iso
VirtualBox / GuestAdditions : 3.2.0

root@slitaz:~# mount.vboxsf 320 /mnt/share   
root@slitaz:~# ls -l /mnt/share/install
-rwxrwxrwx    1 root     root         2684 May 18 18:05 deffiles
-rwxrwxrwx    1 root     root         9828 May 18 18:08 install.sh
-rwxrwxrwx    1 root     root        19399 May 18 18:05 orig-routines.sh
-rwxrwxrwx    1 root     root        13432 May 18 18:05 orig-vboxadd
-rwxrwxrwx    1 root     root         5467 May 18 18:05 orig-vboxadd-service
-rwxrwxrwx    1 root     root        21022 May 18 18:05 orig-vboxadd-x11
-rwxrwxrwx    1 root     root        20725 May 30 19:03 routines.sh
-rwxrwxrwx    1 root     root         4607 May 31 22:31 routines.u
-rwxrwxrwx    1 root     root        13899 May 31 22:46 vboxadd
-rwxrwxrwx    1 root     root         5796 May 31 22:46 vboxadd-service
-rwxrwxrwx    1 root     root          765 May 31 22:50 vboxadd-service.u
-rwxrwxrwx    1 root     root         1572 May 31 22:50 vboxadd.u
-rwxrwxrwx    1 root     root        21319 May 31 22:25 vboxadd-x11
-rwxrwxrwx    1 root     root          835 May 31 22:33 vboxadd-x11.u
-rwxrwxrwx    1 root     root      2733958 May 18 18:08 VBoxGuestAdditions.tar.bz2
root@slitaz:~# mount
rootfs on / type rootfs (rw)
tmpfs on / type tmpfs (rw,relatime,size=579592k)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
tmpfs on /dev/shm type tmpfs (rw,relatime)
usbfs on /proc/bus/usb type usbfs (rw,relatime)
none on /mnt/share type vboxsf (rw,nodev,relatime)
root@slitaz:~# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                  566.0M    125.9M    440.1M  22% /
tmpfs                   566.0M    125.9M    440.1M  22% /
tmpfs                   314.4M         0    314.4M   0% /dev/shm
none                    248.1G    213.1G     35.0G  86% /mnt/share
root@slitaz:~# du -sh /
201.1M
root@slitaz:~# umount /mnt/share
root@slitaz:~# du -sh /
Filesystem                Size      Used Available Use% Mounted on
rootfs                  566.0M    123.0M    443.0M  22% /
tmpfs                   566.0M    123.0M    443.0M  22% /
tmpfs                   314.4M         0    314.4M   0% /dev/shm
root@slitaz:~# du -sh /
123.0M
root@slitaz:~#
root@slitaz:~# tail -21 ~/.VirtualBox/Machines/slitaz/Logs/VBox.log
00:38:34.091 SharedFolders host service: adding host mapping.
00:38:34.091     Host path /media/Audio1/slitaz/3.0/vbox/320, map name 320, writable 1
00:38:34.092 SharedFolders host service: add mapping result VINF_SUCCESS
00:39:22.241 SharedFolders host service: request to map folder vbox32
00:39:22.241 SharedFolders host service: map operation result VERR_FILE_NOT_FOUND.
00:39:22.241 SharedFolders host service: request to map folder vbox32
00:39:22.241 SharedFolders host service: map operation result VERR_FILE_NOT_FOUND.
00:39:22.241 SharedFolders host service: request to map folder vbox32
00:39:22.241 SharedFolders host service: map operation result VERR_FILE_NOT_FOUND.
00:39:48.786 SharedFolders host service: request to map folder 320
00:39:48.786 SharedFolders host service: map operation result VINF_SUCCESS.
00:39:48.786     Mapped to handle 0.
00:45:32.557 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=aad4d000 w=1104 h=851 bpp=32 cbLine=0x1140
00:45:32.703 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=aad4d000 w=1104 h=851 bpp=32 cbLine=0x1140
00:45:32.773 VMMDev::SetVideoModeHint: got a video mode hint (1280x1000x0) at 0
00:45:32.784 VBVA: Disabled.
00:45:32.787 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=aad4d000 w=1280 h=1000 bpp=32 cbLine=0x1400
00:45:32.787 VBVA: Enabled.
00:45:32.787 Guest Additions capability report: (0x5) seamless: yes, hostWindowMapping: no, graphics: yes
00:45:32.787 VBVA: Disabled.
00:45:32.789 VBVA: Enabled.

Slitaz -- vboxadd-3.2.0 / mouse integration

mouse integration

Env:
HOST: winxp
GUEST: slitaz-3.0.iso
VirtualBox: 3.2.0

root@slitaz:~# tazpkg info vboxadd

Tazpkg information
================================================================================
Package    : vboxadd
Version    : 3.2.0_2.6.30.6
Category   : non-free
Short desc : x86 VBoxLinuxAdditions.
Maintainer : 
Depends    : linux-drm mesa-dri xorg-xf86-input-evdev
Web site   : http://www.virtualbox.org/
================================================================================

root@slitaz:~# tail -7 /var/log/Xorg.0.log
(II) config/hal: Adding input device VirtualBox USB Tablet
(**) VirtualBox USB Tablet: always reports core events
(**) VirtualBox USB Tablet: Device: "/dev/event3"
(II) VirtualBox USB Tablet: Found x and y absolute axes
(II) VirtualBox USB Tablet: Found mouse buttons
(II) VirtualBox USB Tablet: Configuring as mouse
(II) XINPUT: Adding extended input device "VirtualBox USB Tablet" (type: MOUSE)
root@slitaz:~# dmesg | tail
PCI: setting IRQ 9 as level-triggered
pci 0000:00:04.0: PCI INT A -> Link[LNKD] -> GSI 9 (level, low) -> IRQ 9
vboxguest: major 0, IRQ 9, I/O port d040, MMIO at 00000000f0400000 (size 0x400000)
vboxguest: Successfully loaded version 3.2.0 (interface 0x00010004)
vboxsf: Successfully loaded version 3.2.0 (interface 0x00010004)
Linux agpgart interface v0.103
[drm] Initialized drm 1.1.0 20060810
pci 0000:00:02.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
pci 0000:00:02.0: setting latency timer to 64
[drm] Initialized vboxvideo 1.0.0 20090303 for 0000:00:02.0 on minor 0
root@slitaz:~# 
root@slitaz:~# cat /var/log/tazpkg.log 
2010-06-02 06:14:57 - Installed - linux-drm (2.6.30.6) - 62ba26c458a1823ccee1f87d33ad619b
2010-06-02 06:14:58 - Installed - mesa-dri (7.4.4) - 2f1a8d7ccc8f8f357266052580fb1df8
2010-06-02 06:14:59 - Installed - xorg-xf86-input-evdev (2.0.4) - 2536931075fe9b19b51c2229740938ec
2010-06-02 06:15:03 - Installed - vboxadd (3.2.0_2.6.30.6) - 206b87986616423c7a6cafc3bf82d6f3
root@slitaz:~# ls -l /lib/modules/`uname -r`/misc
-rw-rw-r--    1 root     root       136865 Jun  1 17:51 vboxguest.ko
-rw-rw-r--    1 root     root        36391 Jun  1 17:51 vboxsf.ko
-rw-rw-r--    1 root     root         3475 Jun  1 17:51 vboxvideo.ko
root@slitaz:~# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                  851.8M    119.9M    731.9M  14% /
tmpfs                   851.8M    119.9M    731.9M  14% /
tmpfs                   473.2M         0    473.2M   0% /dev/shm

root@slitaz:~# du -sh / 
119.9M
root@slitaz:~#

User Manual
Version 3.2.0 Edition
[..]
Chapter 3. Configuring virtual machines
3.4. System settings
3.4.1. "Motherboard" tab
[..]

Enable absolute pointing device
If enabled, VirtualBox reports to the virtual machine that a USB tablet device is present and communicates mouse events to the virtual machine through this device. If disabled, mouse events are communicated through a traditional PS/2 virtual mouse device.

Using the virtual USB tablet has the advantage that movements are reported in absolute coordinates (instead of as relative position changes), which allows VirtualBox to translate mouse events over the VM window into tablet events without having to "capture" the mouse in the guest as described in Section 1.7.1.1, “Capturing and releasing keyboard and mouse”. This makes using the VM less tedious even if Guest Additions are not installed.[8]
[..]

Chapter 4. Guest Additions
4.1. Introduction
[..]
The Guest Additions offer the following features:

Mouse pointer integration
To overcome the limitations for mouse support that were described in Section 1.7.1.1, “Capturing and releasing keyboard and mouse”, this provides you with seamless mouse support. You will only have one mouse pointer and pressing the Host key is no longer required to "free" the mouse from being captured by the guest OS. To make this work, a special mouse driver is installed in the guest that communicates with the "real" mouse driver on your host and moves the guest mouse pointer accordingly.
[..]

Reprinted:
http://www.virtualbox.org/wiki/News
News

May 18, 2010. The VirtualBox team today released a significant new version of Oracle VM VirtualBox(TM), its high performance, cross-platform virtualization software. VirtualBox 3.2, the first Oracle branded release since the acquisition of Sun Microsystems, Inc by Oracle Corp. earlier this year, contains many innovative new features which deliver further significant improvements in performance, power and supported guest operating system platforms.

Performance

* New Latest Intel hardware support – Harnessing the latest in chip-level support for virtualization, VirtualBox 3.2 supports new Intel Core i5 and i7 processor and Intel Xeon processor 5600 Series support for Unrestricted Guest Execution bringing faster boot times for everything from Windows to Solaris guests;
* New Large Page support – Reducing the size and overhead of key system resources, Large Page support delivers increased performance by enabling faster lookups and shorter table creation times.
* New In-hypervisor Networking – Significant optimization of the networking subsystem has reduced context switching between guests and host, increasing network throughput by up to 25%.
* New New Storage I/O subsystem – VirtualBox 3.2 offers a completely re-worked virtual disk subsystem which utilizes asynchronous I/O to achieve high-performance whilst maintaining high data integrity;
* New Remote Video Acceleration – The unique built-in VirtualBox Remote Display Protocol (VRDP), which is primarily used in virtual desktop infrastructure deployments, has been enhanced to deliver video acceleration. This delivers a rich user experience coupled with reduced computational expense, which is vital when servers are running hundreds of virtual machines;

Power

* New Page Fusion – Traditional Page Sharing techniques have suffered from long and expensive cache construction as pages are scrutinized as candidates for de-duplication. Taking a smarter approach, VirtualBox Page Fusion uses intelligence in the guest virtual machine to determine much more rapidly and accurately those pages which can be eliminated thereby increasing the capacity or vm density of the system;
* New Memory Ballooning – Ballooning provides another method to increase vm density by allowing the memory of one guest to be recouped and made available to others;
* New Multiple Virtual Monitors – VirtualBox 3.2 now supports multi-headed virtual machines with up to 8 virtual monitors attached to a guest. Each virtual monitor can be a host window, or be mapped to the hosts physical monitors;
* New Hot-plug CPU's – Modern operating systems such Windows Server 2008 x64 Data Center Edition or the latest Linux server platforms allow CPUs to be dynamically inserted into a system to provide incremental computing power while the system is running. Version 3.2 introduces support for Hot-plug vCPUs, allowing VirtualBox virtual machines to be given more power, with zero-downtime of the guest;
* New Virtual SAS Controller – VirtualBox 3.2 now offers a virtual Serial Attached SCSI (SAS) controller, enabling it to run the most demanding of high-end guests;
* New Online Snapshot Merging – Snapshots are powerful but can eat up disk space and need to be pruned from time to time. Historically, machines have needed to be turned off to delete or merge snapshots but with VirtualBox 3.2 this operation can be done whilst the machines are running. This allows sophisticated system management with minimal interruption of operations;
* New OVF Enhancements – VirtualBox has supported the OVF standard for virtual machine portability for some time. Now with 3.2, VirtualBox specific configuration data is also stored in the standard allowing richer virtual machine definitions without compromising portability;
* New Guest Automation – The Guest Automation APIs allow host-based logic to drive operations in the guest;

Platforms

* New USB Keyboard and Mouse – Support more guests that require USB input devices;
* New Oracle Enterprise Linux 5.5 – Support for the latest version of Oracle's flagship Linux platform;
* New Ubuntu 10.04 (「Lucid Lynx」) – Support for both the desktop and server version of the popular Ubuntu Linux distribution;
* New Mac OS X Server – On Apple hardware only, support for creating virtual machines running Mac OS X Server.

A key component of Oracle's industry-leading desktop-to-datacenter virtualization portfolio, VirtualBox is open source software and hugely popular: surpassing 26 million downloads worldwide since October 2007, with in excess of 40,000 downloads a day. A relatively small download, VirtualBox software is incredibly compact and efficient and installs in just a few minutes.

Pricing and Availability
To download the freely available Oracle VM VirtualBox software, visit the VirtualBox Downloads page. VirtualBox software is free of charge for personal use. For wider deployments within an organization, enterprise licenses are also available, starting at $50 (USD) per user. For partners wishing to redistribute the VirtualBox technology as part of their own solution, Oracle offers a comprehensive OEM licensing program.
.