- Goals
- User guide
- Classlib developers guide
- Developer guide
- Tester guide
- Porting guide
- Blogs
- Project development
- Project organization
- Draft 0.2 plan
- Draft 0.3 plan
- TODO list
- Student Projects
- Classical projects
- Complete AMD 64 support
- Complete multi CPU support
- Complete the vesa driver
- Implement full ddx support without 2d and 3d
- Implement javax.comm API (A)
- Implement new GC algorithms for better performances (A)
- Implement realtime specification for Java
- Implement virtio drivers for jnode (A) (*/**)
- Implement write support for the iso 9660 file system
- Integrate JDistro
- Port jnode to another CPU
- Port jnode to grub 2
- Write a driver for a sound card
- Write a driver for Serial ATA (sata)
- Write a file system checker (**/***)
- write a virtual keyboard
- write an open GL driver
- Write another desktop for JNode
- Write SWT peers
- Generic projects
- Experimental projects
- Classical projects
- Student Projects
- Contact
- Release procedure
- Glossary
- Proposals
- FAQ
- Papers & presentations
- References
- Research
Write a file system checker (**/***)
- Description : Writing a file system checker would not only help ensure that a file system is clean at boot time (like linux distro are doing). It will also allow to help fixing bugs in the current implementations of the file systems. For each of these file systems, a checker could be a student project by itself : ext2, fat32, fat12/16, ntfs (I am not sure about that one since it's hard to get ntfs specifications). The first student to work on a file system checker will have to define an API because we don't have yet one.
- Level : Average (depends on the file system complexity)
- Assigned to :
- Printer-friendly version
- Login to post comments
