World: r3wp

Into several topics at that 4 forum.

Also, bug: "cd ~/ntfs_partition_mounted/<TAB><TAB>" displays Cyrillic 
letters of file names OK (as a list), but "ls <the same folder>" 
gives ????????? instead of cyrillic letters.

Seems to be bug in ls.

mc reports Permission denied (13). /var/log/kernel reports assertion 
failure in ntfs_clear_inode under ntfs_write_inode : kfree of memory 
that was not kmalloc-ed. And subsequent failures in a form of stack 
traces.

These subsequent failures also related to ntfs_clear_inode called 
from ntfs_write_inode.

Also got a Permission denied (13) while attempt to copy a kernel 
log file to ext3 partttion. Under root.

no stack traces this time, and no relevant messages found.

It may seem that I've found a sources glitch with my mouse. A kernel 
log reports "IMPS2 mouse found" which means that appserver/appserver/ps2mouse/ps2mouse.cpp 
detected an Intellimouse PS/2 mouse. Maybe developers had no Intellimouse 
to test stuff, therefore there's no code setting up the mouse for 
that clause. I.e. it gets detected, but there's no special init (which 
must be there), only the message is printed and the mouse protocol 
is not switched (it must be switched, I guess).

Searching for instructions to build sources tree.

Ahh very simple... build install Syllable. But that will fetch Syllable 
from a remote cvs, no?

I need to build my own hacked source tree

Ah found a doc.

Hmm. At http://development.syllable.org/documentation/drivers/index.html
there's no build instructions...

I'll fetch and install.sh a development build.

With a hope that build instructions will be there...

Ahh. "3.9 Building the Syllable base system" at http://syllable.cvs.sourceforge.net/viewvc/syllable/syllable/system/apps/utils/Builder/README
: "At the time of writing, it is not possible to give a definitive
instruction for building the entire Syllable base system." :(((

At the time of writing, it is not possible to give a definitive
instruction 
for building the entire Syllable base system.
 :(((

AltME! Ate part of my text!

Hmm I'm completely lost in this README (at the url above). What should 
I do to recompile appserver/appserver/.../ps2mouse/ps2mouse.cpp ?

And to run the system with a modified ps2mouse.cpp ?

Kaj, waiting for your answer to the last two questions.

It seems there at ps2mouse.cpp init of Intellimouse is underwritten. 
It seems I understand which line the .cpp lacks.

I need to insert it and recompile and run.

Syllable can't write to NTFS, only read from it

http://web.syllable.org/pages/about.html#Desktop

FAT is the preferred format for exchanging data with other systems

Our forum is the designated place for reporting bugs. Here, basically 
only I will see it

We've had to block many mail domains from the forum, though, due 
to spambots, including gmail.com

ls is from GNU CoreUtils. Newer versions may have Unicode support, 
but we're stuck with our current version for now because newer ones 
require more support in Syllable

It could also be a problem in the interfacing between Syllable, CoreUtils 
and the NTFS driver. Maybe it should communicate somewhere that Unicode 
is wanted

Ext2/3 is the same: read only

The Builder README is indeed what you need for compiling, but you 
shouldn't build the complete system, because that's huge and very 
complicated

Section 3.6, "Building a single system module", is what you need

Some modules have dependencies, but I think you can build the PS/2 
driver on its own. After that you need to replace the one in the 
system with it, and then you may have to restart

Ok; all is clear. Re-reporting relevant bugs at the forum.

Posted all bugs at one topic http://forum.syllable.org/viewtopic.php?p=7960#7960

No questions there ATM.

I fetched devel. files for 0.6.6 and built ok there. 


I've tried to hack the obvious but did not succeed; mouse doesn't 
work. It is necessary to compare Linux drivers with Sy.

Fixed!!! See the patch on a developer mailing list.

Mouse fixed, not other bugs.

And Syllable is painfully slow in VESA mode on my video card. Videocards 
with closed specs must be avoided.

Congratulations on the fix! Very cool

Nobody is using the mailing list anymore, but I'll get your patch 
from there

It's not so much that the video specs are closed, but that the drivers 
haven't been updated for years. Ideally, the Nvidia driver and others 
should be ported again from Xorg and Linux

Kaj where can I see the source code for pppd?

Unfortunately, we never got the source code for the port, so all 
there is is the official source code of the PPP project. That's why 
it isn't included in Syllable

ok

It seems that without docs or source code, one cannot set up PPPoE 
using this ppp-beta1.zip.

Other Russians have done it in the past. :-) I have no experience 
with PPPoE, but the existing material should be enough

pppd options syntax seems to be common between many Unices, but a 
eth0 option  is port-specific issue