Over the last couple of weeks Hirofumi has checked in an amazing amount
of kernel code, getting Tux3 to the point of being able to create,
read, and write files and list directories. A bunch of directory
operations still need to be hooked up:
const struct inode_operations tux_dir_iops = {
.create = tux3_create,
.lookup = tux_lookup,
// .link = ext3_link,
// .unlink = ext3_unlink,
// .mkdir = ext3_mkdir,
// .rmdir = ext3_rmdir,
// .mknod = ext3_mknod,
// .symlink = ext3_symlink,
// .rename = ext3_rename,
// .permission = ext3_permission,
// .setattr = ext3_setattr,
// .getxattr = generic_getxattr,
// .setxattr = generic_setxattr,
// .removexattr = generic_removexattr,
// .listxattr = ext3_listxattr,
};
There are also some regular file operations to do:
static const struct inode_operations tux_file_iops = {
// .truncate = ext3_truncate,
// .permission = ext3_permission,
// .setattr = ext3_setattr,
// .getattr = ext3_getattr
// .getxattr = generic_getxattr,
// .setxattr = generic_setxattr,
// .removexattr = generic_removexattr,
// .listxattr = ext3_listxattr,
};
See, Hirofumi is basically working his way down the list using ext3
functions as a guide, and hooking up to the Tux3 code from userspace,
changing the userspace code a little.
Anybody who wants to, can try their hand at one or two of the above as a
starter project. Just ping Hirofumi by mail or irc to let him know, in
case he has already done it! Hirofumi and I will be around irc at the
usual times. Carve your name in the Tux3 commit history early, and
reap unbounded fame and fortune. Maybe.
Tomorrow I will be busy fixing the userspace (common with kernel)
implementation of xattr caching, to support Posix semantics more
accurately.
Regards,
Daniel
_______________________________________________
Tux3 mailing list
[email protected]
http://tux3.org/cgi-bin/mailman/listinfo/tux3
