search for: v2.10

Kirtland Air Force Base has denied approval for the use of R on its Windows network. Some of their objections seem a bit strange, but some appear to be legitimate. In particular, they have detected registry "vulnerabilities" which are detailed in the attachment. I know nothing about Windows registry vulnerabilities. If any of these issues are legitimate concerns,

Hi Team , I am reaching out to you seeking your help for one of my KVM hook script. I am using /etc/libvirt/hooks/network file to trigger an event when a network is created or deleted ( https://www.libvirt.org/hooks.html ). Basically I using a rest call to create the same network in my Infoblox appliance for the network monitoring. However every time I create a network only $2== start or

for those who care, the yodl pkg, a prereq for building rsync3-cvs docs (& more?), had 'issues' @ version <= v2.04 with building cleanly on osx. it's been updated today to v2.10, http://sourceforge.net/project/showfiles.php?group_id=126615 v2.10 builds clealy, without req'd patching or error, and works just fine when/as used by rsync3 -- or elsewhere.

Hi. I have run across this old problem: http://www.syslinux.org/archives/2010-November/015753.html when compiling 4.05 on an x86_64 RHEL 5.5 systems with nasm v2.10 and GNU ld 2.17.50.0.6-14.el5 20061020. The exact symptom is the linker (ld) improperly loads pxelinux.o, created by nasm, to pxelinux.elf. The pfx_* symbols in the .prefix section end up being filled with 0's in pxelinux.elf.

I have written a bash script (see below) to generate bootable SD-USB images using syslinux as booter. The script works OK with versions 3.63 and 3.71, but I get a null pointer error executing /tmp/$SYSLINUX/linux/syslinux -sf -o 16384 SD.img in 3.72. If you execute $ sudo sh SDformat.sh sys then you can test the image easily with qemu $ qemu -hda SD.img ++++++ SDformat.sh

I used syslinux to make an external usb hard drive booting up "system rescue cd" from a FAT primary partition. The procedure I followed was setting on the boot flag on the FAT partition and copying the content of the iso image to it and renaming isolinux to syslinux wherever needed. I then unmounted the device and ran "syslinux -d /syslinux/ -i /dev/sdxn" where sdxn is the

Icecast 2.0 and Ices 2.0 are both fairly usable now. I have set up a semi-permanent test stream for people to bang on at: http://i.cantcode.com:8888/ices.ogg Please report any problems you have. I say semi-permanent, because it will probably crash now and then, and I will be developing and putting up the new versions on a regular basis. If it stops working for more than an hour, somethings

Icecast 2.0 and Ices 2.0 are both fairly usable now. I have set up a semi-permanent test stream for people to bang on at: http://i.cantcode.com:8888/ices.ogg Please report any problems you have. I say semi-permanent, because it will probably crash now and then, and I will be developing and putting up the new versions on a regular basis. If it stops working for more than an hour, somethings

Hi, I took this issue to the Fedora forum initially, but no-one there has been able to offer any guidance, so I have decided to come to the nouveau community directly. I was running a KDE desktop under Fedora 21 successfully, including the ability to use a direct text login on an older card (GXT 560 Ti) with an entirely stock Fedora, fully updated. I simply replaced the old card with an