Thank you very much!
cvs access is availble now.

May I bother you with a strange problem. I think it's related with yaffs 
tools.

My system can mount a spare partition as yaffs smoothly.

/ # mount -t yaffs /dev/mtdblock/3 /mnt
yaffs: dev is 7939 name is "1f:03"
/ # cat /proc/yaffs
YAFFS built:Sep 24 2004 14:16:43
$Id: yaffs_fs.c,v 1.34 2004/09/20 22:00:20 charles Exp $
$Id: yaffs_guts.c,v 1.35 2004/09/21 03:03:12 charles Exp $

Device yaffs
startBlock......... 1
endBlock........... 2047
chunkGroupBits..... 0
chunkGroupSize..... 1
nErasedBlocks...... 2047
nTnodesCreated..... 0
nFreeTnodes........ 0
nObjectsCreated.... 100
nFreeObjects....... 97
nFreeChunks........ 65504
nPageWrites........ 0
nPageReads......... 0
nBlockErasures..... 0
nGCCopies.......... 0
garbageCollections. 0
passiveGCs......... 0
nRetriedWrites..... 0
nRetireBlocks...... 0
eccFixed........... 0
eccUnfixed......... 0
tagsEccFixed....... 0
tagsEccUnfixed..... 2047
cacheHits.......... 0
nDeletedFiles...... 0
nUnlinkedFiles..... 0
nBackgroudDeletions 0
useNANDECC......... 1

But I have met a embarrassed problem. I can not use yaffs as root 
filesystem.

.....
yaffs: dev is 7938 name is "1f:02"
VFS: Mounted root (yaffs filesystem) readonly.
mount_devfs_fs(): unable to mount devfs, err: -2
Freeing init memory: 80K
Warning: unable to open an initial console.
Kernel panic: No init found.  Try passing init= option to kernel.


I found though the kernel can recognize the yaffs partition and mount 
it, but the kernel can not read from the yaffs partition properly. I 
think this is because the yaffs image generation tools can not work with 
the current yaffs code.

It is too strange, is'nt it?

This yaffs rootfs image was generated by me with mkyaffsimage when I was 
playing kernel-2.4.19 with yaffs. The system could boot from it. But I 
found mkyaffsimage cannot be compiled in my linux box. I am using Red 
Hat Linux with gcc-3.3.4.

I found similar problem with jffs2. In exact, it is kernel with the 
newer jffs2 code can not boot from jffs2 rootfs image generated with old 
jffs2 tool(mkfs.jffs2). I don't know if this is a bug or just specific 
to me.

In last email, you mentioned that you were fixing a bug in nandwrite 
shipped with mtd. I had a strange case with nandwrite too. When I wrote 
a image generated with mkfs.jffs2, using nandwrite, to a spare 
partition, I could not mount the partition right there. But when I 
rebooted the system, the partition could be mounted as normal. I can not 
explain why.

I wrote a email about this to the mtd mail-list. But it seemed that my 
email did not reach the list. So I throw this to you. I will be very 
appreciated with any comment from you.

Thank you for your time to read(Hope my poor Englisth make you 
understand me ;).

--
Wangfeng Ai

Wookey wrote:
> +++ Wangfeng Ai [04-09-23 18:47 +0800]:
> 
>>Dear sir,
>>
>>I was trying to use yaffs as root filesystem in our system. That worked. 
>>Recently, we are updating our kernel and mtd system. I am trying to 
>>update yaffs from cvs too, by read-only(anonymous, pserver) method. But 
>>I constantly had a connection error, saying:
>>
>>cvs [update aborted]: connect to cvs.aleph1.co.uk(212.13.198.63):2401 
>>failed: Connection refused
> 
> 
> The inetd had stopped running. As other services are real daemons we did not
> notice. It's working again now - thanx for telling me it was broken.
> 
> Wookey