search for: throwaway

Dear all, I apologize if this is a FAQ (seems a bit like one, but I didn't find anything). I'm looking for an easy way to cut one value out of a vector and shorten the vector accordingly. Something like: x <- c(1, 1, 0, 6, 2) throwaway(x[3]) which will return x = 1 1 6 2, with length(x) = 4. I know one could do this by hand, but then one would have to create a second vector y in a loop which has to be 1 shorter then x and then assign x <- y, as there is no "anti-c()" function which shortens a vector (at least to my...

[This email is either empty or too large to be displayed at this time]

...inux ‘setfiles’ > program. Fedora rawhide has policycoreutils-2.7-11.fc28.x86_64 (setfiles is shipped inside that rpm package). > What happens if you run these commands (which should be safe to run > because they only operate on a throw-away overlay): > > qemu-img create -f qcow2 throwaway.qcow2 /mnt/knp1-vm-otp02/knp1-vm- > otp02.vmdk Seems that qemu-img 2.11 (which I have on my fedora rawhide) does not support such format of invocation. VM have two disks (/boot and LVM partitioned one). I converted both disks to .qcow2 format and executed virt-customize on them: # qemu-img conv...

...version server is Fedora 28 (Rawhide), since > it contains virt-v2v 1.38. This has got to be a bug of some kind in the SELinux ‘setfiles’ program. What happens if you run these commands (which should be safe to run because they only operate on a throw-away overlay): qemu-img create -f qcow2 throwaway.qcow2 /mnt/knp1-vm-otp02/knp1-vm-otp02.vmdk virt-customize --selinux-relabel -a throwaway.qcow2 rm throwaway.qcow2 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk...

Duncan Murdoch wrote: > Scripts are for throwaways, not for anything worth keeping. I totally agree and have a tangentially relevant question about the <<- operator. Currently 'name <<- value' means to look up the environment stack until you find 'name' and (a) if you find 'name' in some frame bind it to a ne...

...f the LLVM build process? Just for the case of building the runtime libraries for a cross-compiled version of clang. Another option is to have the compiler-rt build depend on a host build of clang. So when cross-compiling clang, we'd generate two clang builds: a target version to ship, and a throwaway host version that only exists to cross-compile compiler-rt. I think this second option is the more elegant one (less source dependencies), but is it possible in a single CMake build? The QEMU solution entertains the idea of pushing forward with just one cross-compiler and putting all projects in...

Good evening, I just tried following the steps in "Tip: Creating throwaway appliances with febootstrap"[1] on my workstation at home running Debian/unstable. I ran into problems: ,---- | $ mkdir supermin.d | $ febootstrap --names 'bash' 'coreutils' -o supermin.d | Get: 1 http://ftp.de.debian.org/debian/ sid/main bash amd64 4.1-3 [1325 kB] | Get: 2 ht...

...build depend on a host build of > clang. > I think you mean "build" not "host" here. > So when cross-compiling clang, we'd generate two clang builds: a target > version to ship, > I think you mean "host" not "target" here. > and a throwaway host version that only exists to cross-compile compiler-rt. > I think you mean "build" not "host" here. > I think this second option is the more elegant one (less source > dependencies), but is it possible in a single CMake build? > Right now, no, but I don't...

...am branch just before the bad merge and then merge the first 100 commits from upstream. If the result is good then merge the next 100, but if it's bad then 'git reset --hard' and merge 10 instead. You'll eventually find the commit that made it bad. Essentially, the idea is to make a throwaway branch that merges more frequently. I do something similar to rebase my work to master since gradually rebasing often causes all the conflicts to go away. > Now, I do say "basically" linear because the important thing is to have > small increments of change each time. It doesn'...

...ver this is not so simple: either we could get supermin to generate this, requiring an ugly systemd-specific hack to supermin, or we could generate it in the /init script, which just slows the init script down for no real reason. Since the content of /etc/machine-id doesn't really matter for a throwaway appliance so long as it has the right format, this commit copies the host file into the appliance. --- appliance/hostfiles.in | 1 + 1 file changed, 1 insertion(+) diff --git a/appliance/hostfiles.in b/appliance/hostfiles.in index 8ff53b5..6c581bd 100644 --- a/appliance/hostfiles.in +++ b/applian...

On Tue, Mar 06, 2018 at 08:40:51AM +0000, Зиновик Игорь Анатольевич wrote: > > What happens if you run these commands (which should be safe to run > > because they only operate on a throw-away overlay): > > > > qemu-img create -f qcow2 throwaway.qcow2 /mnt/knp1-vm-otp02/knp1-vm- > > otp02.vmdk I missed out the -b flag: qemu-img create -f qcow2 throwaway.qcow2 -b /mnt/knp1-vm-otp02/knp1-vm-otp02.vmdk anyway ... > setfiles: /sysroot/etc/selinux/targeted/contexts/files/file_contexts: Multiple same specifications for /.*. > /...

This is a fair point; structuring functions into packages is probably ultimately the gold standard for code organization in R. However, lexical scoping in R is really not much different than in other languages, such as Python, in which use of main functions and defining other named functions outside of main are encouraged. For example, in Scheme, from which R derives its scoping rules, the

...<sarcasm>Thank you RedHat</sarcasm> > > Flames to /dev/null. Sorry, you don?t get to throw that grenade and then run away. The old wisdom you refer to is simply obsolete, and it wasn?t Red Hat that made it so. ?Twas *progress* that made it so, specifically the fact that even a throwaway USB key has enough space to hold the complete OS on it these days. We no longer live in a world of 5 MB disk packs the size of extra large pizzas. Several OSes made /usr/{bin,lib} the same as /{bin,lib} way before Red Hat: Solaris, OS X, and Cygwin, at the least. Probably all of the embedded Lin...

Saurabh Nanda <saurabhnanda at gmail.com> writes: > 1) Why is the log saying `SMB2` everywhere? Shouldn't it be saying > `SMB3`? "SMB3" is mostly marketing, it inherits almost everything from SMB2 hence why it's often handled by SMB2 code. You will see this in Samba, Wireshark, Linux, and even Microsoft specification "MS-SMB2" which actually covers both

...al AD servers because the Samba DC didn't exist. Now it exists! Woohoo! "What's the simplest Samba DC I could reasonably use? to dev/test against? All I want is to throw a dozen users and three groups in there". For example, I would love a simple enough setup that I can run in a throwaway VM/container for unit+e2e tests in integration. cheers, m -- martin.langhoff at gmail.com - ask interesting questions ~ http://linkedin.com/in/martinlanghoff - don't be distracted ~ http://github.com/martin-langhoff by shiny stuff

...virus notifications a day because i posted to this list. I have been getting about 20MB of swen a day since i first posted here. Not to espouse conspiracy theories, but it really seems like this list is under attack. Can there be sme warning about this on the list signup page? Like, "Use a throwaway email address for this list", etc. I'm not complaining, just that I think some sort of warning is in order here. This swen stuff is totally out of control.

...merge the first > > 100 commits from upstream. If the result is good then merge the next > > 100, but if it's bad then 'git reset --hard' and merge 10 instead. > You'll > > eventually find the commit that made it bad. Essentially, the idea is to > > make a throwaway branch that merges more frequently. I do something > > similar to rebase my work to master since gradually rebasing often > > causes all the conflicts to go away. > > This is essentially what git-imerge does, you only need to define > "good merge" in the form of a sc...

On 26/08/2019 1:58 p.m., William Dunlap wrote: > Duncan Murdoch wrote: > > Scripts are for throwaways, not for anything worth keeping. > > I totally agree and have a tangentially relevant question about the <<- > operator.? Currently 'name <<- value' means to look up the environment > stack until you find 'name'? and (a) if you find 'name' in some...

Thank you Eric, On 2014-02-05 17:23, Eric Blake wrote: > Yes, live storage migration is possible; although at the moment, qemu is > lacking a way to restart the operation if it fails midstream, so libvirt > only allows the operation if you are willing to temporarily make your > guest transient. What does this mean? Will I loose anything if - for example - there is not enough space on

...--verbose --pivot; then virsh dumpxml $dom > file # refresh the xml to reflect new disk source fi virsh define file so that file restores you to the original disk location if blockcopy fails, but tracks the new location if blockcopy succeeds. [In my development work, I've been testing on throwaway disks, where I don't care if I clobber things by starting over again - but in a production environment, it pays to be more careful, and possibly to experiment on a safe domain with throwaway disk before doing it on your real domain] > > I could not find anything about "pivot"...