similar to: [PATCH 0/2] Two build fixes for libldm

v2: wrap commit message, "PATCH libldm" prefix. v3: correctly initialize and free GLib resources. The result of this patch might be used by libguestfs to return drive mappings for LDM volumes. Note, that "show volume" ldmtool command already returns hint which is a drive letter assigned by Windows to corresponding volume. But it is not reliable source of information. More

v2: wrap commit message, "PATCH libldm" prefix. v3: correctly initialize and free GLib resources. v4: gtk-doc is updated to reflect presence of new volume GUID field. The result of this patch might be used by libguestfs to return drive mappings for LDM volumes. Note, that "show volume" ldmtool command already returns hint which is a drive letter assigned by Windows to

> > I am trying a scenerio where the * will take the email and mailbox number from the Mysql database for sendming mail to a voicemail user. I have seen vmdb.sql file but is not able to determine its use. > You can't anymore MySQL was ripped from Asterisk because the client libs > are GPL. I would be more than happy to help write a DB "Virtualization" function for *.

The main goal of these patch series is to implement a new API that allows to retrieve created device-mapper devices for volumes and partitions back after they have been created. As part of this patch: - required libdevmapper version was bumped to 1.02. I think it is safe because it was released more then 10 years ago; - newer version of libdevmapper allowed to simplify code base a little bit; -

Hi list, I am trying a scenerio where the * will take the email and mailbox number from the Mysql database for sendming mail to a voicemail user. I have seen vmdb.sql file but is not able to determine its use. I have created a table using that file but don't know how to use the fields from database in the dialplan of *. So it would be a great help if someone here could point me to a right

Hi, Does anyone have any instructions or pointers to get VM2 to work with MySQL? I can't seem to find any docs or how-to's on this.. Later..

> Hi there, > > I failed to boot an installer in a VMware player (Version6.0.3 > build-1895310) > using syslinux 6.03, be it off an hybrid ISO image and an USB stick. > > Booting succeeds if the VM is set to use a BIOS firmware with both media, > but fails using an efi firmware. > > Trying to boot off the ISO image I get an error message "The firmware >

Hi there, I failed to boot an installer in a VMware player (Version6.0.3 build-1895310) using syslinux 6.03, be it off an hybrid ISO image and an USB stick. Booting succeeds if the VM is set to use a BIOS firmware with both media, but fails using an efi firmware. Trying to boot off the ISO image I get an error message "The firmware encountered an unexpected exception" Trying to

> 99% of the time that people have this problem, it's because they renamed > the column "uniqueid" in the vmdb.sql sample file, not realizing that > the name of the column MUST be "uniqueid" for password changing to > work. > > -- > Tilghman Holly column name Batman! That worked. In my effort to be consistent across table names, I did change the

On 10/11/2014 04:02, Ady wrote: > >> Hi there, >> >> I failed to boot an installer in a VMware player (Version6.0.3 >> build-1895310) >> using syslinux 6.03, be it off an hybrid ISO image and an USB stick. >> >> Booting succeeds if the VM is set to use a BIOS firmware with both media, >> but fails using an efi firmware. >>

I run VMWare server 1.07 on Centos 5. Last night I left a Windows 2000 virtual machine doing a ClamWin scan of drive M: when I went to bed around midnight. Drive M: is actually a volume on the Centos 5 host, mounted via Samba. It has about 40Gb of photos on it, plus a few other things. I had the VM up visible in the VMWare Server Console running under KDE on display 8 (X session #1), my