Hi, Thanks a lot again for your detailed and informative response.
What you see in the mainline is basically a single-user system. So far > there is no notion of users, passwords, home directories, etc. > > A rather complex and sophisticated RBAC-based security model has been > already implemented for HelenOS [1], but it is still on our merge list. > > [1] > http://www.helenos.org/doc/**theses/sh-thesis.pdf<http://www.helenos.org/doc/theses/sh-thesis.pdf>(in > Czech) > I will read the thesis if i am able to translate it to English. > > 2. Is there any documentation similar to 'hier' manual page ? This will >> help to get a comprehensive description of the file system hierarchy >> very easily. >> > > No. The file system hierarchy is far from being fixed, stable and final. > But the current file system hierarchy is quite simple and self-explanatory: > > /app -- end-user applications > /cfg -- system-wide configuration > /data -- application data (e.g. the web root served by websrv) > /drv -- device drivers > /inc -- header files > /lib -- libraries > /loc -- location service nodes (rough analogy of /dev in UNIX) > /src -- source files > /srv -- server applications (services, e.g. console, networking) > /tmp -- temporary files > > Thanks for explaining the file system hierarchy. It is indeed quite simple and they are what i guessed, but wanted to be sure. > Remember not to think about HelenOS like a reimplementation of 40+ years > of legacy conventions. HelenOS is not a reimplementation of anything, it is > an experimental system and pretty much everything (file system hierarchy, > API, ABI) is allowed to change if there is a good reason for the change. Yes, i am making the same mistake again and again by thinking along the lines of legacy conventions. I apologize for that. Thanks, Vivek Prakash
_______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
