search for: _safe_

If I have a "simple" variable value, this works fine: capmon@peter:~> puppet -e ''$v="xyz" exec { f: command => "/bin/echo v is $v", logoutput => true }'' notice: /Stage[main]//Exec[f]/returns: v is xyz notice: /Stage[main]//Exec[f]/returns: executed successfully But how do I escape "bad" values of $v? Painful examples like the

----- Original Message ----- From: "Eric Blake" <eblake@redhat.com> To: "Adam King" <kinga@sghs.org.uk>, libvirt-users@redhat.com Sent: Thursday, August 21, 2014 3:17:09 AM Subject: Re: [libvirt-users] virsh snapshot On 08/20/2014 06:34 PM, Adam King wrote: > Hi, > [Can you convince your mailer to wrap long lines?] > > I had a 'domain' called

...1 still up and running, AND using the same disk image as what the APP03 definition points to, AND you modified the image? That's a recipe for disaster. You _cannot_ safely modify a qcow2 image by two simultaneous processes, and the fact that APP01 is a running qemu process means that the only _safe_ way to delete snapshots from that image is via qemu commands triggered through the libvirt process managing that qemu process. Maybe that explains the corrupted display from qemu-img. I hope you didn't corrupt your data too badly. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt...

...is syntax, changing its behavior risks the stability of a system. I see the use case for exporting the boot sector to a file instead of the VBR as demonstrated in this discussion. However, IF there's an actual use case for installing the VBR AND writing it to a file at the same time, the only _safe_ method to implement this is with a new syntax. "syslinux.exe -i a: bootsec.bss" would either only create the bootsecfile OR become a rejected syntax. "syslinux.exe -i --bss bootsec.bss a:" could be a new syntax that creates the bootsecfile and installs the VBR. While implemen...

...ing the same > disk > image as what the APP03 definition points to, AND you modified the > image? That's a recipe for disaster. You _cannot_ safely modify a > qcow2 image by two simultaneous processes, and the fact that APP01 is > a > running qemu process means that the only _safe_ way to delete > snapshots > from that image is via qemu commands triggered through the libvirt > process managing that qemu process. Maybe that explains the > corrupted > display from qemu-img. I hope you didn't corrupt your data too > badly. > Looking back, that does s...

> On Sat, Jan 5, 2019 at 3:17 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > syslinux[64].exe -i -f c: bootsecfile.bss > > > > > > This should have been the form for your desire as specifying the > > > filename should have told it to create the BSS instead of writing it > > > to the VBR. Being the "fixed" HDD

Good afternoon all! I have a project I'm working on that requires Linux to be installed either to its own partition, or to the partition of a host OS (Windows or Linux). One way works, the other way does not... Use Case 1: In this scenario, Linux is installed to its *own* partition as is syslinux (syslinux -i /path/to/syslinux/files). Afterwards, I 'dd' the first 512bytes of that

Hi, [I have added freebsd-security to recipient list as I consider this issue a security risk] Paul Schenkeveld wrote: > Hello, > > On Fri, Jul 14, 2006 at 01:26:38PM +0300, Ari Suutari wrote: >> Hi, >> >> Does anyone know if there are any plans to bring >> pf boot-time protection (ie. /etc/rc.d/pf_boot and >> related config files) from NetBSD to FreeBSD