search for: curcumst

Folks: Problem: [<-.data,frame() is losing attributes under certain curcumstances shown below. I think this is a bug, at least in documentation, as I was unable to find explicit documentation of the behavior. Indeed, the only documentation I found told me attributes are preserved. Here is a detailed description: > df <- data.frame(a=1:3, b=letters[1:3]) > attr(df...

...process does not return. The patch below simply bypasss the test, but the errors in the out file are included as well. I suspect this is due to more or tighter ulimits on this system. But I'm not sure if this is result of different expectations (kernel/userland) of what should be done in the curcumstance. // George NetBSD chime 4.0_STABLE NetBSD 4.0_STABLE (CHIME) #6: Tue Apr 29 16:49:55 EDT 2008 root at chime:/usr/obj/sys/arch/amd64/compile/CHIME amd64 time(cpu-seconds) unlimited file(blocks) unlimited coredump(blocks) 1 data(kbytes) 262144 stack(kbytes) 2048...

Hi, After reading the tutorial at http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 I have the following question: What should I put instead of splashimage=(hd0,0)/grub/splash.xpm.gz and root (hd0,0) on /etc/grub.conf? Should I leave those lines untouched? If so, how would grub know where to boot from if /dev/sda fails? Or I would need to swap the drives in order to boot

...hat that last step suggested by the messages must be REALLY exciting too! Elsewise, why would it be followed by an exclamation mark!?!) But seriously folks, what exactly is up with the messages above? I do not wish to be either rude or impertinent, however I do feel compelled to ask: Under what curcumstances, exactly (and in what Universe, exactly) does it make sense for a program... i.e. *any* program (or any script)... to issue what looks, from where I am sitting, like not one but _two_ messages, clearly saying that the program failed to do its intended job, and then, immediately after that, ext...

In message <BLU0-SMTP557B92590B4CC34F8318088BB30 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >Since in all cases you get to see at least the Syslinux copyright >message, the problem doesn't seem to be related to whether your BIOS >can identify the USB disk and boot from it. I can only agree. >Some GA motherboards might identify some USB drives as