Hello. During designing the new service manager I've come up against chicken-egg problem. My approach was motivated by minimizing amount of data in boot device (the one read by GRUB) and number of tasks started by kernel (GRUB modules). This lead me to idea of splitting the "basic" initalization and "user" initialization.
Currently, it would mean moving logger task from GRUB module to initrd and starting it during "basic" initialization and the rest of current tasks would be started during the "user" initialization. Eventually, this could be exploited to have the root filesystem separated from initrd. Actually, I found this topic already mentioned in HelenOS tickets [1], similarly to Linux early user space. This separation would require changing the root filesystem (I think that implementing this in the VFS would be the most effective (concerning required changes)). Consequently, device manager would need an ability to reload/update its drivers list. What do you think? Am I wrong about something or unaware of some horrendous consequences? Apart abovementioned conceptual questions I have few more ordinary questions. How to mount a filesystem from within HelenOS GUI? I tried > start fat > mkdir foo > mount fat foo /loc/services/\hw\pci0\00:01.0\ata-c1\d0 # alternatively c2 however, it didn't work (rc=-14). Can it be caused by misinitialization of ata_bd driver? (See attached log.) Thank you, Michal [1] http://trac.helenos.org/ticket/447
ata_bd
Description: Binary data
_______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
