Re: [ros-kernel] Re: File system struct - ENOUGH ALREADY

[KJK::Hyperion <no...@li...>]

At 02.14 30/04/2002, you wrote:
>I think you give up to easily. One problem is that you are trying to turn 
>ReactOS itself into a POSIX environment, instead of taking advantage of 
>the ReactOS subsystem abillity.

My point of view, which I won't try to defend any further (at least for a 
very long time), is to mix the best of all subsystems. The Win32 "standard" 
for filesystem structure is hardly the "best". Drive letters are hardly the 
best way to identify devices. Multiple roots are bad, they are the 
inheritance of an era (DOS) when there was no distinction between the 
operating system and the user interface, but we don't need them anymore

Ah, and don't forget we aren't the only OS to have a POSIX subsystem, still 
we are the only to question whether its root directory should match the 
"system" root, whether /dev is visible to other subsystems, and so on. 
Designers of MacOS/X had no doubt, apparently, and they solved the 
"usability" issue (i.e. the user wondering what are all those strange 
directories in the root) raised by some by just... hiding the POSIX 
directories in the GUI. MacOS/X is a Unix you say? Partially true, but BeOS 
wasn't at all. Still, also its POSIX subsystem accessed the same namespace 
of native programs, and /dev was visible to all programs. One wonders why 
those fools at Be and Apple decided so, given the elaborate rationales the 
members of this project use to justify the opposite approach

One more thing: NT is NOT a microkernel, so please stop considering it 
such. It may make sense to have special filesystems (think /proc) 
implemented by subsystems, ON A MICROKERNEL SYSTEM, that will surely 
provide facilities to implement system calls as IPC calls. But, alas, NT 
isn't, so it's just not going to work. At least, not to the extent you'd hope