search for: knames

Hi everybody, I have a large dataframe similar to this one: knames <-c('ab', 'aa', 'ac', 'ad', 'ab', 'ac', 'aa', 'ad','ae', 'af') kdate <- as.Date( c('20111001', '20111102', '20101001', '20100315', '20101201', '20110105', '20101...

With 1.9.37 the following script worked fine, with 1.9.39 it fails. Any idea what the issue is? Olaf ... mount -o /dev/vda1 /sysroot/ [ 1.396411] EXT4-fs (vda1): mounting ext2 file system using the ext4 subsystem [ 1.533090] EXT4-fs (vda1): mounted filesystem without journal. Opts: (null) guestfsd: main_loop: proc 1 (mount) took 0.45 seconds libguestfs: recv_from_daemon: 40 bytes: 20 00

I'm trying to figure out how to start *..... Rh7.3,CVS,TE410P,TA750 If I just try the way the docs spell it out "/usr/sbin/asterisk -vvvc" it fails...... /var/log/asterisk/messages Oct 3 22:23:34 WARNING[1024]: File chan_zap.c, Line 610 (zt_open): Unable to open '/dev/zap/channel': No such device Oct 3 22:23:34 ERROR[1024]: File chan_zap.c, Line 4930 (mkintf): Unable

Hi all, I recently made a patch to openssh 4.1p1 to allow it to use the in-kernel key management provided by 2.6.12 or later Linux kernels. I've attached the patch (which is still only a proof-of-concept, for instance its very verbose right now) to this mail. Now, my question is, is this a completely insane idea and would (a later version of) the patch have a chance of making it into the

What does 'modprobe -d ocfs' show? If it tells you 'symbols not found' it's the RPMs incompatible with your kernel version. Ensure you have the correct RPMs. Successful 'rpm -ivh' doesn't mean correct installation. Should be: [root@pc33 root]# modprobe -d ocfs ============================================= Module ocfs kname ocfs objkey ocfs names: ocfs mode: NORMAL

Hi. I bought a new Adaptec 6405 card including new (much larger) SAS drives (arrays). I need to copy content of the current SATA (old adaptec 2405) drives to the new SAS drives. When I put the new controller into the machine, the card is seen and I can see that the kernel loads the new drives and the old drives. The problem is that the new drives are loaded as SDA and SDB, which then stops the