(Illustration by Gaich Muramatsu)
>> I've search the list for this problem but couldn't find the answer, >> 18:06:25 worker::main Got a bogus opcode 3 >> ls: .: Op?ration non support?e >> >> I find it also in /usr/coda/etc/console : >> 18:06:25 worker::main Got a bogus opcode 3 >> >> and I find nothing related (based on timestamp) in /vice/srv/SrvLog >> >> I've got my token and I'm the coda admin. >> >> If it matters The server and the client are on the same box a linux 2.4.5 >> kernel. > >What version of Coda are you running? The upcall that it rejects is >CODA_OPEN_BY_FD, which was introduced in the userspace daemon around >the end of August of 2000, i.e. it was already included in Coda 5.3.9. I use version 5.3.8 (precisely rpm packages for mandrake : coda-debug-server-5.3.8-4mdk coda-debug-backup-5.3.8-4mdk coda-debug-client-5.3.8-4mdk) Although I use a Mandrake 8.0, the 2.4.5 kernel is not a Mandrake (which is modified) one but a linus-classic-kernel. Even if i'm not 100% sure, I thought I had a NOT_REALLY_CODA object in the /coda which leads me to think it worked (even if it was for a short time...) Is it possible I screw things by an unclean REinstall (delete /vice /vicepa, and RElaunching vice-setup erasing the partitions...) : I mean is there some pitfalls which could cause this, I should be aware of ? What other info would you need ? > >The Linux kernel started using this 'new' upcall as of 2.4.4, which was >released only a few months ago. > As my kernel is 2.4.5 and beccause of what is said above, culdwe assume that it's not (only) kernel related ? -- AKTOR Interactive Le Galice C 1 square du dr Bianchi 13090 AIX EN PROVENCE Tel: 04.42.52.82.16 Fax: 04.42.52.99.65 ------------------------------------------------- Multidiffusez votre annonce ou votre CV sur des dizaines de sites Internet http://www.robopost.com -------------------------------------------------Received on 2001-08-20 02:59:37