Hi
here is what I think about the hole rosfs.
after I have read about it. do not feel offended.
but some points I feel it some part are not good
idea.
Should this not need alot of cpu power and memory use ?
if it need alot of memory most of i486 does only have 32MB
today reactos can run on a i486 with 32MB with out any problem.
but I feel in this way
it need alot more memory that 32MB.
 
the second problem I feel it need alot of harddisk space
and it will need alot of harddisk space, that goes wast
I want a os that does not wast harddisk space.
 
 
next problem
I do not like the idea have a sql server install to use it.
it will need alot of cpu power it will be to havey for i486
 
And last I do not want a someting that can be using for hacking
into my computer more easy. I feel rosfs will create alot of hole.
I do not feel safe with this idea.  and it maby will make most
commo people unsure if reactos are safe or not.
BestReagds
Magnus Olsen
 
 
 
 

 
----- Original Message -----
From: Rick Langschultz
To: ros-dev@reactos.com
Sent: Wednesday, September 29, 2004 2:43 PM
Subject: [ros-dev] RosFS

For those of you who have heard nothing of my plans to write a RosFS service for ReactOS, here are some details about my plan.

RosFS

RosFS is a small service running on system initialization by default that indexes files, folders, users, devices, and network resources can hold metadata via MySQL, sleepycat DB, TCL, Apache, and Perl; which will all be embedded within the service itself. RosFS will hold encrypted resources based off of a key that is created with the first startup of ReactOS, it changes every 30 days to ensure security. The RosFS can be accessed online via the built in web server with can be an encrypted connection – SSL, or TLS. User ACLs can be set on a machine level or a domain level. RosFS will support a SQL-like querying language that can be written easily – it will have triggers, procedures, functions, and saved queries – which are all logged. Triggers will be supplied by a TCL-like language with features of Perl.  An service will provide users with current system updates, patches, etc stored on a domain server – this option will only be installed on a powerful server with pretty good hardware – ie: not for home use!!!

A few problems I know that will arise in developing such a project are:
1) Size

2) Security
3) Where to keep the files on the system
4) The RosFS query language will be trouble to write and maintain depending on if a user uses such Databases like ORACLE, MySQL, MSSQL, etc.
5) Explorer Integration – Will Explorer.exe need to be rewritten to allow the addition of Metadata structures, etc.
6) Web integration – Perl, PHP, TCL, CGI, ISAPI???

Please send me comments and concerns about the RosFS project.


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev