search for: sysc

http://defect.opensolaris.org/bz/show_bug.cgi?id=1986 Summary: ''zfs destroy'' hangs on encrypted dataset Classification: Development Product: zfs-crypto Version: unspecified Platform: Other OS/Version: Solaris Status: NEW Severity: major Priority: P2 Component: other

...9;s matching algorithm entirely intuitive, but e.g., Ista expected R even "to throw an error" in this case, and there are about 99% of R users less savvy than him, so let me think loudly a bit further ... IIUC, Emil's case is mostly about this > ff <- function(x,y,z,...) list(sysC=sys.call(), match=match.call()) > str( ff(x=, z=pi, "foo") ) List of 2 $ sysC : language ff(x = , z = pi, "foo") $ match: language ff(x = "foo", z = pi) > where the argument matching rule above would have suggested to him that the matched call shoul...

Reza Sheykhi <hajishey at msu.edu> writes: > I got the following answers: > > which perl > /usr/bin/perl > > which llvm-config > /usr/local/bin/llvm-config > > which llvm-as > /usr/local/bin/llvm-as > > /usr/bin/llvm-confing --version > bash: /usr/bin/llvm-confing: No such file or directory Uh, there is a typo on the command above, it should be

I got the following answers: which perl /usr/bin/perl which llvm-config /usr/local/bin/llvm-config which llvm-as /usr/local/bin/llvm-as /usr/bin/llvm-confing --version bash: /usr/bin/llvm-confing: No such file or directory /usr/local/bin/llvm-config --version 2.8 Quoting Óscar Fuentes <ofv at wanadoo.es>: > Reza Sheykhi <hajishey at msu.edu> writes: > >> Thank you

...address timestamp type vc handler pc 0 fffffffffbc13d58 1a9f71228e7 trap d #gp dsl_dataset_get_spa+f 0 fffffffffbc13bd0 1a9f711b322 intr a0 unknown mach_cpu_idle+17 0 fffffffffbc13a48 1a9f70e3206 intr a0 unknown mach_cpu_idle+17 0 fffffffffbc138c0 1a9f63ccda5 sysc b7 pollsys feec7757 0 fffffffffbc13738 1a9f63c336b intr d1 cbe_fire mach_cpu_idle+17 0 fffffffffbc135b0 1a9f4edd94f intr d1 cbe_fire mach_cpu_idle+17 0 fffffffffbc13428 1a9f39f811c intr d1 cbe_fire mach_cpu_idle+17 0 fffffffffbc132a0 1a9f3962d4e intr a0 unknown mach_cpu_idle+17...

But the main point is where arguments are mixed together: > debugonce(plot.default) > plot(x=1:10, y=, 'l') ... Browse[2]> missing(y) [1] FALSE Browse[2]> y [1] "l" Browse[2]> type [1] "p" I think that's what I fall over mostly: that named, empty arguments behave entirely different from omitting them (", ,") And I definitely agree we need

...k devices failed to create /dev/hda failed to create /dev/hda1 failed to create /dev/hda2 Creating root device mkrootdev: mknod failed: 30 Mounting root filesystem mount: error 2 mounting ext3 pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 umount /initrd/proc failed: 2 Kernel panic - not syscing: Attempted to kill init! 2. This issue is irrespective of issue 1. I was wondering how I would be spawning the real init after the real_root_dev has been mounted.... In the normal booting case(i.e. without initramfs) prepare_namespace() returns and /sbin/init is executed in init/main.c:init()....

...to see how to get the new 0.63.1 compiled? I hope that I am not bugging anyone by restating and expanding on these two questions, which I asked to some extent before. I am still just getting familiar with R organization after installing it two weeks ago. BTW: Thanks much to marcusd at cathcart.sysc.pdx.edu and Ben about their help on HDF. ************************************************************** S. Hoon Yoon (Quant) Merrill Lynch Equity Trading yelled at yahoo.com hoon at bigfoot.com(w) "Miracle is always only few standard deviations away, but...

...2 +- drivers/block/xen-blkfront.c | 5 +- drivers/bluetooth/bcm203x.c | 2 +- drivers/bluetooth/bluecard_cs.c | 2 - drivers/bluetooth/hci_ll.c | 2 +- drivers/bluetooth/hci_qca.c | 8 +- drivers/bus/ti-sysc.c | 2 +- drivers/char/agp/ali-agp.c | 2 +- drivers/char/ipmi/kcs_bmc.c | 3 +- drivers/char/lp.c | 4 +- drivers/char/mem.c | 2 +- drivers/char/nvram.c...

...2 +- drivers/block/xen-blkfront.c | 5 +- drivers/bluetooth/bcm203x.c | 2 +- drivers/bluetooth/bluecard_cs.c | 2 - drivers/bluetooth/hci_ll.c | 2 +- drivers/bluetooth/hci_qca.c | 8 +- drivers/bus/ti-sysc.c | 2 +- drivers/char/agp/ali-agp.c | 2 +- drivers/char/ipmi/kcs_bmc.c | 3 +- drivers/char/lp.c | 4 +- drivers/char/mem.c | 2 +- drivers/char/nvram.c...

...2 +- drivers/block/xen-blkfront.c | 5 +- drivers/bluetooth/bcm203x.c | 2 +- drivers/bluetooth/bluecard_cs.c | 2 - drivers/bluetooth/hci_ll.c | 2 +- drivers/bluetooth/hci_qca.c | 8 +- drivers/bus/ti-sysc.c | 2 +- drivers/char/agp/ali-agp.c | 2 +- drivers/char/ipmi/kcs_bmc.c | 3 +- drivers/char/lp.c | 4 +- drivers/char/mem.c | 2 +- drivers/char/nvram.c...

...2 +- drivers/block/xen-blkfront.c | 5 +- drivers/bluetooth/bcm203x.c | 2 +- drivers/bluetooth/bluecard_cs.c | 2 - drivers/bluetooth/hci_ll.c | 2 +- drivers/bluetooth/hci_qca.c | 8 +- drivers/bus/ti-sysc.c | 2 +- drivers/char/agp/ali-agp.c | 2 +- drivers/char/ipmi/kcs_bmc.c | 3 +- drivers/char/lp.c | 4 +- drivers/char/mem.c | 2 +- drivers/char/nvram.c...

...2 +- drivers/block/xen-blkfront.c | 5 +- drivers/bluetooth/bcm203x.c | 2 +- drivers/bluetooth/bluecard_cs.c | 2 - drivers/bluetooth/hci_ll.c | 2 +- drivers/bluetooth/hci_qca.c | 8 +- drivers/bus/ti-sysc.c | 2 +- drivers/char/agp/ali-agp.c | 2 +- drivers/char/ipmi/kcs_bmc.c | 3 +- drivers/char/lp.c | 4 +- drivers/char/mem.c | 2 +- drivers/char/nvram.c...