similar to: Visio vsd/vdx vs. svg

I have recreated one lost .vsd file (State_Diagram.vsd) and have exported XML Diagram Files (.vdx) corresponding to all of the .vsd files that I have. All of these files are now available in CVS (Shorewall-docs/images/) -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

Tom, Can you/someone get a news feed setup for shorewall announcements? If not, I''ll have to make use of the shorewall rss feeds at SF. Project RSS Feeds: shorewall http://sourceforge.net/export/rss2_project.php?group_id=22587 BTW, planetplanet.org has links to some cool feeds. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net

Tom, I think it may be wise to move the revhistory to an appendix in FAQ.xml. What do you think? -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

Everyone, Progress was slow today. I started out well, but then I ran into Documentation.htm. Progress slowed considerably, as I analyzed the document structure. I''m up to /etc/shorewall/hosts Configuration. I hope to finish Documentation.xml by tomorrow evening. Converted documents: 6to4.xml CorpNetwork.xml FAQ.xml Please post feedback, if you see any problems with the converted

Everyone, Is there a suggested set of minimal diagnostic information that should be included in all requests for assistance? Is this the document we should refer people to that don''t provide sufficient information in their posts? http://www.shorewall.net/support.htm Example of a similar document from the LEAF project. http://leaf-project.org/pub/doc/docmanager/docid_1891.html --

Hi, we have samba server with version 3.0.6. we are facinga peciular problem. on unix machine the user and his group got full permission and others don't have any permissions (770) on a particular file . when he is trying to access it from windows he couldn't open the file. especially we are facing this problem with Microsoft visio (.vsd) and Microsoft XL (.xls) files. Eg: when

Hi, I try to install visio 2002 (or 2000) with wine. All the dll's are loaded apparently, some screen pops up, and then it's over. I see these messages in debug : fixme:msvcrt:MSVCRT_signal (8 0x6030cd09):stub fixme:accel:CreateAcceleratorTableA should check that the accelerator descriptions are valid, return NULL and SetLastError() if not. fixme:font:WineEngCreateFontInstance just using

RHEL 3 doesn't have a dynamic /dev. kmod-virtio creates devices nodes for vdX block devices based on what the major number of virtblk was at the time it was installed. This is, in turn, based on the order the modules were loaded in initrd. To try to preserve this precarious state of affairs, when adding virtio drivers to a new initrd we always load the same drivers as kmod-virtio in the same

Hi, I am running wine-0.9.56-1.fc7 on a Fedora 7 system. I installed Visio 5 (must be around 10 years old!). The Visio seems stable when running under wine, the graphics are good and I can save the vsd files under wine. Two small problems 1. Unable to save complex diagrams to jpg or gif. For example, there is an Office furniture template which includes walls, chairs and tables. The simple

Data Rational Communic... wrote: > Hi, > > I am running wine-0.9.56-1.fc7 on a Fedora 7 system. I installed Visio 5 > (must be around 10 years old!). The Visio seems stable when running under > wine, the graphics are good and I can save the vsd files under wine. > > Two small problems > > 1. Unable to save complex diagrams to jpg or gif. For example, there is an >

Hi, I'm using libvirt 5.0.0 on a Ceph cluster. The VM disks are all from the same Ceph pool, so all my <disk> elements are basically the same: <disk type="network" device="disk"> <driver name="qemu" type="raw" cache="none"/> <source protocol="rbd" name="vmdisks/VOLNAME">

Greetings, I'm trying to run The Bat! (email client by RITlabs) on Mac OS X 10.5.7 with the most current XQuartz installed. I compiled Wine 1.1.22 using MacPorts and confirmed it is working for simple Windows applications. (Btw, is this Wine or Darwine, since MacPorts seems to download and compile the official Wine sources?) After installing The Bat!, it starts up and immediately quits with

Thankyou the information provided was informative to say the most. Quote "Shorewall Masqurading made simple ?" I will not comment any futher about my simple question as I see nothing but backtracking information. Maybe all the usless information is somthing to do with the below, Linux how it works! First you must remember that 98% of linux programmers are kids or they have been

Hi all, I got bored and implemented SCSI passthrough for the virtio-blk driver. Principle is quite simple, just put the missing fields (cdb, sense and status header) on the virtio queue and then call the SG_IO ioctl on the host. So when using '-drive file=/dev/sgXX,if=virtio,format=host_device' you can happily call any sg_XX command on the resulting vdX device. Quite neat, methinks. And

Hi all, I got bored and implemented SCSI passthrough for the virtio-blk driver. Principle is quite simple, just put the missing fields (cdb, sense and status header) on the virtio queue and then call the SG_IO ioctl on the host. So when using '-drive file=/dev/sgXX,if=virtio,format=host_device' you can happily call any sg_XX command on the resulting vdX device. Quite neat, methinks. And

I'm trying to boot a virtual GSP node with Linux KVM and VirtIO. While the install itself detects both the VirtIO harddisk (/dev/vdx) and VirtIO ethernet nic and completes successfully, I'm not able to boot the virtual machine from it. After POST I can only see the GSP boot message and the countdown timer, but when the timer reach 0 it stalls. When I reassign the _same_ disk as IDE or SCSI

Linux from around 5.6 now enumerates individual disks in any order (whereas previously it enumerated only drivers in parallel). This means that /dev/sdX ordering is no longer stable - in particular we cannot be sure that /dev/sda inside the guest is the first disk that was attached to the appliance, /dev/sdb the second disk and so on. However we can still use SCSI PCI device numbering as found

Previously we used SCSI when VirtIO wasn't available. KVM's SCSI support is not as mature as its IDE support, and SCSI isn't supported at all in RHEV. --- lib/Sys/VirtV2V/Converter.pm | 50 +++++++++++------- lib/Sys/VirtV2V/Converter/Linux.pm | 19 ++++--- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 100 ++++++++++++++++++++---------------- 3 files changed, 100 insertions(+), 69

Using Rusty's suggestion I've respun the patch removing the special copy function. I've tested this patch in a guest kernel with and without qemu supplying serial numbers for the block devices and it's working as expected. When qemu supplies serial numbers, the correct value is supplied to /sys/block/vdX/serial and can be used by udev for generating disk/by-id paths (without

Using Rusty's suggestion I've respun the patch removing the special copy function. I've tested this patch in a guest kernel with and without qemu supplying serial numbers for the block devices and it's working as expected. When qemu supplies serial numbers, the correct value is supplied to /sys/block/vdX/serial and can be used by udev for generating disk/by-id paths (without