search for: wnc

...you seen this problem before? I am using Redhat 8.0 at rsync server and Solaris 8 as rsync client. At both ends I am using rsync 2.5.6 protocol version 26 Thanks in advance for your help. Jaydeep /d01/rsync/rsync/bin/rsync -rRLacutpvv --partial --delete --force --timeout=3600 $serverName::build/wnc/7.0/47 /public/home/rsync/arh/in/build [rsync-build] opening tcp connection to $serverName port 873 [rsync-build] receiving file list ... [rsync-build] done [rsync-build] expand file_list to 4000 bytes, did move [rsync-build] deleting in wnc/7.0/47 [rsync-build] delta transmission enabled [rsync-bu...

Hello, I bought a LevelOne WPC-0301 11g Wireless CardBus Adapter today. According to the box it is "v6". The ral(4) man- page mentions only v2, but that one is ancient and can't be bought anymore. So, enabling the debug sysctl gives this in dmesg: cardbus0: Expecting link target, got 0x0 cardbus0: <network, ethernet> at device 0.0 (no driver attached) cardbus0: CIS pointer

Whamcloud and EMC are jointly investigating how to be able to contribute the Lustre client code into the upstream Linux kernel. As a prerequisite to this, EMC is working to clean up the Lustre client code to better match the kernel coding style, and one of the anticipated major obstacles to upstream kernel submission is the heavy use of code abstraction via libcfs for portability to other

Whamcloud and EMC are jointly investigating how to be able to contribute the Lustre client code into the upstream Linux kernel. As a prerequisite to this, EMC is working to clean up the Lustre client code to better match the kernel coding style, and one of the anticipated major obstacles to upstream kernel submission is the heavy use of code abstraction via libcfs for portability to other