search for: rinis

Read the Posting Guide mentioned at the bottom of this email. Highlights you should be sure to address: * HTML formatted email gets messed up on the R mailing lists, so post in plain text. Yes, you can and need to do this. * Make sure the problem occurs in R by trying it without RStudio. Sometimes RStudio interferes with R, and you have to ask elsewhere about such problems. * Give us details

When I use any function of RWeka Package in Rstudio I get an error, "Error in .jnew (name): java.lang.ClassFormatError." can anyone guide me in this? [[alternative HTML version deleted]]

Hello, After poking and prodding at Asterisk and Zaptel for over a couple years now, I've dedicated some time to actually reading the code and trying to figure it out. It's been fascinating. With the driver source on one part of the screen and a pdf of "Linux Device Drivers" on another part I've aquainted myself with device driver programming and the interesting

I've attached the .gz'ed log of another EXT3 crash on my PPC box. This time it was on IDE and I was doing a tab completion as it died. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/

Hey all. I'm not on the list, so can you please cc me? Thanks. Anyhow, I've got two questions. First, the website says that the 'latest' e2fsprogs are needed. Does this mean 1.23-WIP is needed or will 1.22 do? I'm assuming it's just a generally good idea. Second, has anyone tested this on a BE machine? I'd like to use this on my PPC. I don't mind testing

Hello all, I've posted on this problem before. Well here goes again. I have an intel mobo with a p4 2.4ghz proc, 1GB Ram. It has built-in ethernet and vga and 6 pci slots. I dreamed of making this my household communications server: internet router, firewall, vpn and asterisk. Everything works except the TDM fxs card. Well it works for a little while and it dies: no dialtone, no

Okay, after playing around a bit more, I'm getting two oopes in a row when running dbench 16 or dbench 32. Decoded, here they are: Assertion failure in unmap_underlying_metadata() at buffer.c:1530: "!buffer_jlist_eq(old_bh, 3)" kernel BUG at buffer.c:1530! Oops: Exception in kernel mode, sig: 4 NIP: C003BB34 XER: 00000000 LR: C003BB34 SP: CF881E00 REGS: cf881d50 TRAP: 0700 Using

Patches against 2.4.10-pre4 and 2.4.9-ac9 are at http://www.uow.edu.au/~andrewm/linux/ext3/ It's a fairly large change. The most significant parts are * the inclusion of Stephen's error-handling work, which is designed to remount the fs read-only in the presence of software and hardware errors, rather than forcing a panic. * Stephen's fix for the journal_revoke assertion

Hello ext3-users, I tested ext3 on a Linux for S/390 with several stress and benchmark test tests and faced a kernel bug message. The console showed the following output: Message from syslogd@boeaet34 at Fri Aug 3 11:34:16 2001 ... boeaet34 kernel: Assertion failure in journal_forget() at transaction.c:1184: "! jh->b_committed_data" I tried the Patch from

Hello all, I am new to dovecot and have had a good experience so far. I'm using fetchmail - exim - dovecot - my email clients (mac os mail and thunderbird so far). I'm also using Ubuntu Server i.e. debian. I didn't like the inflexibility of mbox so I did a tweak to exim to deliver mail to a Maildir folder in my home directory on the server. I restarted Dovecot and it found it!

An ext3 patch against linux 2.4.10 is at http://www.uow.edu.au/~andrewm/linux/ext3/ This patch is *lightly tested* - ie, it boots and does stuff. The changes to ext3 are small, but the kernel which it patches has recently changed a lot. If you're cautious, please wait a couple of days. The patch retains the buffer-tracing code. This will soon be broken out into a separate patch to make

Hey all. I was wondering if an official patch vs 2.4.9 is in the works yet. I managed to apply it locally, but there was one or two changes that didn't apply cleanly. (mm/vmscan.c has had some stuffs moved around). I think I did it right, but an official patch is always nice. :) -- Tom Rini (TR1265) http://gate.crashing.org/~trini/

Hello all, Been a while since I've strolled this way. Apologies in advance if this is a common line of questioning. I've just bought a new Intel 865G based board with a P4 Hyperthreading processor. I believe I've gotten SMP set up correctly: in the menuconfig I specified SMP and told acpi to enumerate processors. Did I leave out anything? Anyway, the dmesg looks good and the

Hello ext3-developers, Just to summarize, I reported a kernel bug message with ext3 on S/390 in transaction.c. I was able to reproduce it with a ext3 on LVM and on MD. Tom Rini reported a similar problem on PPC. (both big endian). I have sent a backtrace and with jbd-debug set to 5 I was not able to reproduce the problem until now. On S/390 there are some more debug possibilities. I would

Patch against linux-2.4.8 is at http://www.uow.edu.au/~andrewm/linux/ext3/ The only changes here are merging up to 2.4.8 and the bigendian fix. linux-2.4.8-ac1 currently has ext3-0.9.3 which has no known crash-worthy bugs, but is old. I'm about to send Alan a diff which takes -ac up to 0.9.6. The changes between 0.9.3 and 0.9.6 may be summarised as: - Simplify the handling of

All, I know that there is no official port to Kernel 2.4.4, thus I may not get any help, however I am hoping someone could point me in the right direction for my problem. I am currently forced to use kernel 2.4.4 for reasons out of my control (embedded board). Here are the exact versions of everything I'm running: ExT3 Version: ext3-2.4-0.9.6-248 Util Version: util-linux-2.11f.tar.bz2 e2fs

Okay, I have a server connected to the net but have not added fail2ban or anything on top of my firewall yet. Thought you guys might get a kick out of this one user, ip is from china, who has got a heck of a knack for making assumptions on possible usernames. Enjoy this..., 8000+ attempts. Scroll down for funky ones. I have no root access enabled on this server and it is pretty bare. Just using

flight 17325 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17325/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 9 guest-start fail REGR. vs. 12557 test-amd64-i386-xl-credit2 15 guest-stop fail REGR. vs. 12557 test-amd64-i386-xl 15 guest-stop

flight 17454 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17454/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-qemut-rhel6hvm-amd 7 redhat-install fail

flight 17612 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17612/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-rhel6hvm-intel 9 guest-start.2 fail