Beta Linux Client?

[Terminal Insanity]

The beta linux client page only lists 1.62 beta....
does anyone know if there are any linux-specific patches that are coming with 1.64, whenever they are planning to release it?

Specificly the reiserfs/2.6 issue?
i had to move my dialog.tlk to a non-reiserfs partition (its now on a bsd box) and placed a symlink to it from my nwn dir... it seems to work now

[Epistaxis]

I read somewhere that Bioware is currently working on the linux and mac patch and it should be ready next week

Message from one of the designers:

Bah, sorry about that, I meant to speak about that. The Mac and Linux work on 1.64 is being worked on right now (has been for the last 3 days now) as well as the French, German, Spanish and Italian versions of the above. We are hoping to have all of it out late next week for you. Sorry for the lack of info on this.

[Sara Tonin]

The beta linux client page only lists 1.62 beta....
does anyone know if there are any linux-specific patches that are coming with 1.64, whenever they are planning to release it?

Specificly the reiserfs/2.6 issue?
i had to move my dialog.tlk to a non-reiserfs partition (its now on a bsd box) and placed a symlink to it from my nwn dir... it seems to work now

wierd, i'm running 2.6 with nwn on my reiserfs partition and see no problems?

[Terminal Insanity]

It seems to have started with 2.5 kernels actualy...

http://www.linuxhq.com/kernel/changelog/v2.5/69-bk17/

ChangeSet@1.1155.2.10, 2003-05-19 10:28:10-07:00, akpm@digeo.com
[PATCH] reiserfs: reiserfs_file_write implementation

From: Oleg Drokin <green@namesys.com>

With the current 'one block at a time' algorithm, writes past the end of a
file are slow because each new file block is separately added into the tree
causing shifting of other items which is CPU expensive.

With this new implementation if you write into file with big enough chunks,
it uses half as much CPU. Also this version is more SMP friendly than the
current one.

There are some known-bad applications that break with this patch (ie. start
to work very slow or even hang).

This is because the filesystem returns a large value in the stat.st_blocksize
hint (128k instead of 4k). This tickles a small number of application bugs.
One is KDE's kmail 3.04 (fixed by upgrading to 3.1+) and the other is
sleepycat's database from before 1997.

If you hit a slowdown problem that you believe is related to the increased
"recommended i/o size" value, try to mount your fs with nolargeio=1 mount
option (remount should work too).

This patch exports block_commit_write(), generic_osync_inode() and
remove_suid() to modules.