search for: readfs

...include/ocfs2_fs.h \ Index: ocfs2/debugfs.ocfs2/Makefile =================================================================== --- ocfs2/debugfs.ocfs2/Makefile (revision 127) +++ ocfs2/debugfs.ocfs2/Makefile (working copy) @@ -12,7 +12,7 @@ CFLAGS += -Wall -O2 CFILES = main.c commands.c dump.c readfs.c utils.c journal.c -HFILES = include/main.h include/commands.h include/dump.h include/readfs.h include/utils.h include/journal.h +HFILES = include/main.h include/commands.h include/dump.h include/readfs.h include/utils.h include/journal.h include/jbd.h OBJS = $(subst .c,.o,$(CFILES)) @@ -21,4...

...en/boot/bootload-root. It will match up a bootdisk entry such as ''sda3'' against the disk specifications passed in and construct a path to the fs image residing on a file or device node. Once the FS image is located, it will call out to a generic OS-provided helper called ''readfs'' as follows: readfs -n -i <image> -o /var/cache/xen/boot/<file> <file> This binary will identify the filesystem and read the file given off it, storing it in the output cache file specified if it has changed since last invocation. After doing this for the kerne...

Hi There: I was wondering if there is a way to read FORTRAN list data (similar to IDL's readf function). I often use FORTRAN for most of my number crunching, and use something like IDL to visualize and perform statistical analysis on that data. Since the each file is rather large (>100 Mb), formatting the output into columns or tables is impractical, hence the "list"

> Author: nba-guest > Date: Mon Apr 24 20:45:39 2006 > New Revision: 414 > > Modified: > trunk/CHANGES > trunk/drivers/cpsups.c > Log: > Fix C++ style declarations between statements > > Modified: trunk/CHANGES Niels, What is the reason for 'fixing' this? Constructions like these are used in many locations throughout the sources (not only in the

On Monday 04 August 2008 17:56, Dan Gohman wrote: > > By "complicate" do you mean "need to look at multiple addresses from a > > single instruction?" Or is there more than that? I'm trying to > > understand > > all the implications. > > I mean just that -- we have a fair amount of code built around looking > at the addresses of load and

domUloader potentially makes my life a lot easier, but from experiments and looking at the code, it doesn''t seem like there is any way to pass kernel command line arguments with it. Am I just missing something? Thanks, John Byrne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

On Aug 4, 2008, at 2:02 PM, David Greene wrote: > On Saturday 02 August 2008 16:47, Dan Gohman wrote: > >> * Vector Gather/Scatter >> This would complicate analyses that look at load and store addresses, >> but if we really want to do gather/scatter without messes, this >> might be >> an acceptable tradeoff. > > By "complicate" do you mean