search for: 0000050

...080 2500 0000010 877d 2501 877d ff7f daff 7882 ffff daff 0000020 7882 0080 2500 877d 2501 877d ff7f daff 0000030 7882 ffff daff 7882 0080 2500 877d 2501 0000040 877d ff7f daff 7882 ffff daff 7882 0080 0000050 2500 877d 2501 877d ff7f daff 7882 ffff 0000060 daff 7882 0080 2500 877d 2501 877d ff7f 0000070 daff 7882 ffff daff 7882 0080 2500 877d 0000080 2501 877d ff7f daff 7882 ffff daff 7882 0000090 0080...

Hi, I have been trying to find a solution to this issue, but have not been able to so ! I am trying to use sapply on the function getSYMBOL, an extract from the list is: > test.goP[13:14] $`GO:0000050` IEA IEA IEA IEA TAS TAS TAS IEA "5270753" "5720725" "1690128" "4850681" "110433" "2640544" "4900370" "1430280" IEA NAS TAS IEA "6110044" &quo...

...ffice is in UTF-16, as shown by hexdump: $ hexdump test.csv 0000000 feff 0061 0009 0062 0009 0063 0009 0064 0000010 000d 000a 0058 0009 0031 002c 0032 0009 0000020 0031 002c 0033 0009 0031 002c 0034 000d 0000030 000a 0059 0009 0032 002c 0032 0009 0032 0000040 002c 0033 0009 0032 002c 0034 000d 000a 0000050 005a 0009 0033 002c 0032 0009 0033 002c 0000060 0033 0009 0033 002c 0034 000d 000a 000006e I tried to read the file using file/readLines, which seemed to work after specifying the encoding: > a = file("test.csv",open="r", encoding="UTF-16") > b = readLines(a...

Hello everyone, recently I've found something I consider a bug. Correct me if I'm wrong, but I always thought that Linux' EOL is 0x0A. Imagine my surprise when I saw that all messages that are being output on to the stderr (on any Linux I've tested - Fedora and Ubuntu) are terminated with 0x0D, 0x0A. Maybe that's standard behaviour of all stderr messages in all Linux

...0 00 .... ^ 0000020: feff feff f7ff 3035 3037 3236 3134 3137 ......0507261417 ^^^ 0000030: 3131 3035 3037 3236 3134 3137 3333 3030 1105072614173300 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 0000040: 3030 3231 ff07 ffff ffff ffff ffff ffff 0021............ ^^^^^^^^^^^^^^^^^^^^ 0000050: ffff ffff ffff ffff ffff ffff ffff ffff ................ 0000060: ffff ffff ffff ffff ffff ffff ffff ffff ................ 0000070: ffff ffff ffff ffff ffff ffff ffff ffff ................ 0000080: ffff ffff ffff ffff ffff ffff ffff ffff ................ 0000090: ffff ffff ffff ffff ffff ffff...

Hi all, As people may have seen there's a pre-release here: http://downloads.xiph.org/releases/flac/beta/ Specifically: flac-1.3.1pre1.tar.xz : The source code flac-1.3.1pre1-win.zip : Windows 32 and 64 bit binaries Please test. I'm particularly interested in hearing about the windows binaries which were cross compiled from Linux to Windows. Unfortunately there is a bug

How 'bout PAM? /usr/ports/security/pam_ldap. If you have machines that can't do PAM, perhaps NIS is the way to go (assuming, of course, you're behind a firewall). You can store login information in LDAP like you want, then use a home-grown script to extract the information to a NIS map. Or, if you have a Solaris 8 machine lying around, you can cut out the middle step and use

...gt; > > hidraw: > > 0000000 1180 59e1 ffff 01a3 1180 59e2 ffff 01a3 > 0000010 1180 5ae3 ffff 01a3 1180 5ae4 ffff 01a3 > 0000020 1180 5ae5 ffff 01a3 1180 5ae6 ffff 01a3 > 0000030 1180 5ae7 ffff 01a3 1180 5ae8 ffff 01a3 > 0000040 1180 5ae9 ffff 01a3 1180 5aea ffff 01a3 > 0000050 1180 5aeb ffff 01a3 1180 5aec ffff 01a3 I was trying to reconcile this with your earlier information from usbhid-dump, and it looks like hexdump is swapping bytes: $ printf 12345678|hexdump 0000000 3231 3433 3635 3837 0000008 You can do one of the following to get the natural...

Hi, Using dumpe2fs I have been able to determine that all of my alternate ext3 superblocks are corrupted (not clean), and only the primary superblock is valid, i.e. mount works and the ordered journal is applied. When the primary superblock gets flakey, i.e. the ext_attr Filesystem feature goes missing - not sure why this occurs. At this point, the mount does not apply the journal using the