Re: [ros-kernel] Disk layout continued

[Robert K. <ro...@ko...>]

Though, the primary question is not what projection will a ss make to its
sheeps, but the actual
directory structure in the filesystem. I beleve that one partition's root
directroy is something
special. It is the highest level to divert the strucure. I think that
multiple installations on one
partition is a valuable thing.
No question, WinNT's dir struct has to be resembled in a way.
However I refuse to pollute the root dir with ss specivic dirs. For this
reason
I am for emulating these dirs in the sub system's namespace.

You may argument: Why not also emulate win32-dir struct?
The answer would be: It behaves nice, 'cos it needs only one Folder whose
name is choosable.
PS.
 I think noone either beleves that driveletters actually exist in NT nor
likes them.

Aliberti Emanuele schrieb:

> On 23 May 2002 at 1:40, Casper Hornstrup wrote:
>
> > What root are we talking about? The Object Manager root or the Win32
> > shell namespace root? System drive? POSIX subsystem root? Other?
> >
> > Yes, unix applications expect a certain disk layout. However the POSIX
> > subsystem can emulate this layout so the unix applications are happy.
> >
> > Now I'm confused. Which special file system object? Symbolic links are
> > handled by the object manager in cooperation with it's clients.
> >
> > The subsystem translates relative paths into fully qualified paths.
> >
> > Each subsystem can provide symbolic links to a central location.
> >
> > Just configure your subsystems to have the same view of your volumes
> > then.
>
> I simply reproduce verbatim what Casper wrote. What is apparently
> missing in the original dialog is what Casper tries (desperately;) to
> affirm with his comments. By dropping the dialog text, I hope that
> obscure thing pops up itself.
> .
> .
> .
> .
> .
> .
> .
> .
> What we are talking about is a "name space". Of course there is only
> one name space in every OS. In NT, the name space is the system name
> space, the one generated and maintained by the Ob manager in the
> executive. Whatever you create in NT, unless it is unamed, it has a
> fully qualified name from the root "\" down to its own (relative)
> name. One of the important tasks in Os simulation is name space
> simulation. As I just recalled, every OS has its own name space,
> {directory|folder|library} separator convention, file name convention
> etc. Do you really belive that "A:" really exist in your very new XP
> pro box? It is just what the Win32 subsytem show to you (dear) my
> windows process. Therefore what we really need is not "where do I put
> my files?", but "what is a complete and correct mapping of the system
> name space to project it, in full or partially, in my os name
> space?". Also, keep in mind that Win32 can NOT see the whole system
> name space. Therefore it is NOT required an isomorphism between the
> system name space and your own subsystem's name space.
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel