similar to: Boot from CD -> system + data on USB storage

Hi I am trying to have a built in initramfs along with the traditional initrd. So I mount the initrd from the initramfs, but am facing problems in trying to run the 'linuxrc'. Following are the issues: 1. I mount the initrd from the initramfs and exceve 'linuxrc'. It starts executing linuxrc, but gives the following errors and panics: Red hat nash version 3.4.42 starting

Dear R core team Using the following code produces an empty plot (similar to col = NA): > plot(1:9, col = factor(rep(1:3,3), labels = c("red", "blue", "black"))) My question: Shouldn't one get at least a warning (or an error) if one tries to use a factor as col argument? Thanks for an answer. Regards, Christoph Buser

ROOT_DEV carries a root device number communicated in an architecture- specific way. We now pass it to kinit via the real-root-dev sysctl call. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 0f5a324d655ad582246b6830843114d09835f593 tree fd3a96a69b6d74ee33dcd54a58b8666c02139a3a parent f3e41698e540a7d39658d6590fde1379c0f5bab0 author H. Peter Anvin <hpa at zytor.com> Thu,

Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --

Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --

This set of patches add some support for sector size >512. Currently it fixes extlinux, MBR for GPT and ext partitions. Other code is unaffected. This set of patches has been tested on a read Dell machine running a beta firmware.

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C344B0.28BC0750 Content-Type: text/plain; charset="windows-1252" Summary: Currently R provides > dev.control(displaylist='inhbit') to turn *off* the recording of graphics operations in a device, but there is no

This is of course an incorrect usage, which I've trapped at R level, so as to give an informative warning. On Tue, 28 May 2002 NEFTH@pacbell.net wrote: > The following sequence of commands: > graphics.off() > dev.control("inhibit") > > causes R to memory-fault and core dump. This is reported > for a new port of R, but is also reproducible on Windows > and

I found it useful to have contour be able to do line widths ... hope that the guts haven't changed an enormous amount in the current development version ... the patches are relatively trivial, mostly going by analogy with lty and col (although in my ignorance it took me a while to figure out what UNPROTECT(2) was and why it should be changed to UNPROTECT(3) ... hope this is useful. Ben

Hi, Thanks Volodya, Misha and Chris, > > For example, > > Correct way: > > Instruction *NewInst = new LoadInst(...); > > NewBB->getInstList().push_back(NewInst); > > > > what I need just put some junk data in the BB, not instructions. From > > assemble code level, it looks like the following, > > > > a piece of code from

Some simple refactoring of virt-resize. I originally had the idea that we could turn virt-resize into a library (cf. virt-customize) and use it from virt-builder, but I now don't think that would make any meaningful difference. In particular we'd still have to open the handle the same number of times. These two patches are left over from my work on that. Rich.

Thomas Schmitt wrote: > My main point of interest is which block is really loaded as first one > of isolinux.bin. [Program snipped.] > (It could be shorter if i did not insist in big endian words.) Why insisting? Anyway appended is a dumper version. I could put up a binery version if needed. Let me know if so. -- MartinS /*

Hi, I tried to rewrite virt-rescue from C to OCaml. Goals were feature parity with C implementation, smaller codebase and hopefully better maintainability. I still don't know if I've covered everything right. So, please check it out. PS: my git send-email seems to be broken, so I'm sending it from thunderbird Thanks! maros

This still isn't working at the moment. See: http://marc.info/?t=139457409300003&r=1&w=2 This set of patches: - Adds new APIs to support discard in libguestfs. - Adds discard support to virt-format. - Adds discard support to virt-sysprep. - Implements virt-sparsify --in-place. Rich.

Move the simple OCaml JSON writer to mllib, so that can be enhanced and used also outside v2v. --- mllib/JSON.ml | 53 +++++++++++++++++++++++++++++++++++++++++++++++++++++ mllib/JSON.mli | 26 ++++++++++++++++++++++++++ mllib/Makefile.am | 5 ++++- po/POTFILES-ml | 2 +- v2v/JSON.ml | 53 ----------------------------------------------------- v2v/JSON.mli | 26

Hi there! Here is the latest version of the series including Richard's comments. I also reworked the repository_main.ml code to avoid setting an empty entry if not found. Cédric Bosdonnat (3): builder: change arch type to distinguish guesses builder: add a template parameter to get_index New tool: virt-builder-repository .gitignore | 4 +

In the run dialog, I have implemented an ANSI colour escape sequence interpreter, so that colours displayed by the remote virt-v2v are now shown to the user. (https://bugzilla.redhat.com/show_bug.cgi?id=1314244) This requires virt-v2v to send colours. It wasn't doing that because the output was a pipe (as we capture the output into the log file). So I added a global --colours option to make

Version 1 of the patch, for discussion, but not to be applied. It does work, but needs a lot more testing. This removes all the psychopathic gettextify cruft, and replaces it with a 99 line Makefile.am. A large win, I think. The third patch implements gettext support in the OCaml tools. The fourth patch is just for illustration. It shows the consequent changes to libguestfs.pot and the po

This set of patches: - Adds new APIs to support discard in libguestfs. - Adds discard support to virt-format. - Adds discard support to virt-sysprep. - Implements virt-sparsify --in-place. This is now working, after fixing the rather stupid bug in fstrim. I've pushed the ones which were ACKed previously + the fstrim fix. Rich.

.. and a lot of refactoring. https://bugzilla.redhat.com/show_bug.cgi?id=1167623 Rich.