-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File handling updates #4
Comments
Further abstractions duly committed. |
Any reason not to start working on write? Things that appear necessary for it: Anything I'm missing? |
Heh, very much:
IOW, read side of vfs is waaay less than half the work! stdin/stdout are total hacks at the moment and require a character device layer at the very least, and a terminal implementation ideally :) Still too tied up working on qemu things in citrix as of yet, just committed first cut of fork() implementation though :) |
Heh, there was me hoping for an easy job :P Once I've finished and committed the kernel/user refactor, I'll rough in the kernel/user write support and start drilling down towards the floppy driver. At this point, I figure it's probably more useful for me to code the wrong thing than to code nothing -- it's ages since I did anything on here, and it took me a while to get back up to speed. |
Yeah, a lot of the bits for write support are orthogonal, eg. low level floppy disk writes and block layer stuff like queuing.... I'm not even sure myself how it'll all link in to the page-cache. An ATA hard-disk and ATAPI CD-ROM driver would also come in handy :) |
Actually kernel/read.c could do with being re-worked to use the page-cache. Rather than call pread directly just do a loop to pull everything in to page-cache and then kernel_read() would memcpy it in to the buffer and sys_read would copy_to_user it. |
Updated code now enables you to manipulate files directly as an alternative to using the fdt system. Currently only supports opening new files and closing files. To what extent should we work to abstract a layer over the fdt code?
The text was updated successfully, but these errors were encountered: