About filesystem support...

[João Jerónimo]

I've just read the filesystems section of the Developer FAQ and it says:
*
--------------------------------------------------------------------------------------------------
 - Q* Why don't you implement Ext2/3 instead of focusing on NTFS?*
 - A* Because NTFS is a major feature which must be supported at some
time. Ext2/3 is of course a topic for us, however there are already
projects whose goal it is to implement Ext2/3 for NT. We will utilize
these drivers when they are good enough.
--------------------------------------------------------------------------------------------------
So... if you are going to use the code from one of the many projects for
ext2/3 drivers around there "when they are good enough", why do the ROS
source has a driver in /reactos/drivers/filesystems/ext2? Is it one of
the popular IFS ext2/3 drivers that has, meanwhile, become "good
enough"? Or is it a ReactOS internal subproject?
And what about NTFS? Does the driver in
/reactos/drivers/filesystems/ntfs do something? Does it read?
Is it an internal project?
JJ
_______________________________________________________
Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu celular. Registre seu
aparelho agora!
http://br.mobile.yahoo.com/mailalertas/

[Brandon Turner]

João Jerónimo wrote:
>   I've just read the filesystems section of the
> Developer FAQ and it says:
>  *
> --------------------------------------------------------------------------------------------------
>   - Q* Why don't you implement Ext2/3 instead of focusing on NTFS?*
>   - A* Because NTFS is a major feature which must be supported at some
>  time. Ext2/3 is of course a topic for us, however there are already
>  projects whose goal it is to implement Ext2/3 for NT. We will utilize
>  these drivers when they are good enough.
> --------------------------------------------------------------------------------------------------
>  So... if you are going to use the code from one of the many projects for
>  ext2/3 drivers around there "when they are good enough", why do the ROS
>  source has a driver in /reactos/drivers/filesystems/ext2? Is it one of
>  the popular IFS ext2/3 drivers that has, meanwhile, become "good
>  enough"? Or is it a ReactOS internal subproject?
>     
I think it is the ext2 from http://sourceforge.net/projects/ext2fsd but
it is probably a really old version.  It is rumored to work in our CC
branch but not in trunk.
>   And what about NTFS? Does the driver in
>  /reactos/drivers/filesystems/ntfs do something? Does it read?
>  Is it an internal project?
>     
I haven't looked at it in a while but I think that it was just a stub
driver that doesn't do anything.
>   JJ
>  _______________________________________________________
>  Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu celular. Registre seu
> aparelho agora!
>  http://br.mobile.yahoo.com/mailalertas/
>  _______________________________________________
>  Ros-general mailing list
>  Ros-general(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-general
>     
--
Brandon Turner
~~~~~~~~~~~~~~~~~~~~~~~~
ReactOS Release Engineer
www.reactos.org
~~~~~~~~~~~~~~~~~~~~~~~~
Sharp Shell Lead Developer
http://www.codeplex.com/Wiki/View.aspx?ProjectName=SHARPSHELL

[Ali Savas]

Hello,
Are you working for assestive technology for visualy impared people? I
I am blind and i want to work with ROS with an screenreader. Are you
working about this too?
Yours
Ali

[Magnus Olsen]

Hi
Ali Savas
One problem is we do not have the hardware to test with and that why no one
wrote a driver for it
or tested current drivers that exists. Then I known it is diffent protocolls
betwin diffent screenreader
for blind people. It is not lack of knowlegs but more lacking of hardware to
test it.
Basic ReactOS should be avail run windows nt4/2000/xp/2003 drivers (more or
less)
BestReagds
Magnus Olsen
----- Original Message -----
From: "Ali Savas" <ali-savas(a)gmx.de>
To: "ReactOS General List" <ros-general(a)reactos.org>
Sent: Saturday, November 04, 2006 8:11 PM
Subject: [ros-general] Accessibility
>   Hello,
>  Are you working for assestive technology for visualy impared people? I
>  I am blind and i want to work with ROS with an screenreader. Are you
>  working about this too?
>  Yours
>  Ali
>  _______________________________________________
>  Ros-general mailing list
>  Ros-general(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-general

[João Jerónimo]

Brandon Turner wrote:
> >   So... if you
> > are going to use the code from one of the many projects for
> >  ext2/3 drivers around there "when they are good enough", why do the ROS
> >  source has a driver in /reactos/drivers/filesystems/ext2? Is it one of
> >  the popular IFS ext2/3 drivers that has, meanwhile, become "good
> >  enough"? Or is it a ReactOS internal subproject?
> >     
>  I think it is the ext2 from http://sourceforge.net/projects/ext2fsd but
>  it is probably a really old version.  It is rumored to work in our CC
>  branch but not in trunk. 
Ok...
And what do you mean exactly by CC branch?
Don't forget I'm not a developer... :-) However, you don't have to
explain what a "branch" is... I know it's a copy of something from the
trunk that is put in /branches to allow a separate set of commits (and
remains separated from the trunk until someone remerges it's changes)...
But what's the CC branch?
> >   And what about
> > NTFS? Does the driver in
> >  /reactos/drivers/filesystems/ntfs do something? Does it read?
> >  Is it an internal project?
> >     
>  I haven't looked at it in a while but I think that it was just a stub
>  driver that doesn't do anything. 
This question was because the file structure doesn't look like a bunch
of stub functions (which AFAIK normally just report something to a log
system and return an error code)...
Besides, even occupying much less space than the linux-ntfs directory
(and I think that the sizes are comparable even with different APIs), it
could have some functionality, although much less...
JJ
_______________________________________________________
Yahoo! Acesso Grátis - Internet rápida e grátis. Instale
o discador agora!
http://br.acesso.yahoo.com

[Brandon Turner]

João Jerónimo wrote:
>   Brandon Turner wrote:
> > >   So... if
> > > you are going to use the code from one of the many projects for
> > >  ext2/3 drivers around there "when they are good enough", why do the ROS
> > >  source has a driver in /reactos/drivers/filesystems/ext2? Is it one of
> > >  the popular IFS ext2/3 drivers that has, meanwhile, become "good
> > >  enough"? Or is it a ReactOS internal subproject?
> > >         
> >  I think it is the ext2 from http://sourceforge.net/projects/ext2fsd but
> >  it is probably a really old version.  It is rumored to work in our CC
> >  branch but not in trunk.
> >       
>  Ok...
>  And what do you mean exactly by CC branch?
>  Don't forget I'm not a developer... :-) However, you don't have to
>  explain what a "branch" is... I know it's a copy of something from the
>  trunk that is put in /branches to allow a separate set of commits (and
>  remains separated from the trunk until someone remerges it's changes)...
>  But what's the CC branch?
>     
Our CC branch is where some developers (Hartmut and Filip if I remember
correctly) rewrote the cache manager code of the kernel which the
filesystem is heavily dependent on.  With the changes they made it
possible to use the ext2 filesystem driver, but the changes in there
have not been moved to trunk yet.  I would imagine they will be soon and
I think Dr. Fred and a few others are trying to lead that charge.
> > >   And what
> > > about NTFS? Does the driver in
> > >  /reactos/drivers/filesystems/ntfs do something? Does it read?
> > >  Is it an internal project?
> > >         
> >  I haven't looked at it in a while but I think that it was just a stub
> >  driver that doesn't do anything.
> >       
>  This question was because the file structure doesn't look like a bunch
>  of stub functions (which AFAIK normally just report something to a log
>  system and return an error code)...
>  Besides, even occupying much less space than the linux-ntfs directory
>  (and I think that the sizes are comparable even with different APIs), it
>  could have some functionality, although much less...
>  JJ
>     
I think it might be a little more then a stub but I don't think it does
much more then load the driver and setup some of its structures.
Though, there is one sure fire way to find out what it does, and that is
to try it and report back! ;)
--
Brandon Turner
~~~~~~~~~~~~~~~~~~~~~~~~
ReactOS Release Engineer
www.reactos.org
~~~~~~~~~~~~~~~~~~~~~~~~
Sharp Shell Lead Developer
http://www.codeplex.com/Wiki/View.aspx?ProjectName=SHARPSHELL

[Magnus Olsen]

Hi
About EXT2/3 driver
ReactOS have a ext2/3 driver imported from a 3 party project and it works to
read partions
but writing it contain some issue. I do not rember what.
About NTFS driver
it is a port from linux, what I heard it can read NTFS partions more or less
never try it
my self
About CC branch
it is a real mess and some with knowlges about CC should check it or delete
it and start over
you can not applay any patch or code from it to current trunks. for to much
have been change
and the CC branch does not working out of box. for some have mess that up.
I recomdate that current CC be delete and start over.
----- Original Message -----
From: "João Jerónimo" <j_j_b_o_j(a)yahoo.com.br>
To: "ReactOS General List" <ros-general(a)reactos.org>
Sent: Saturday, November 04, 2006 11:08 PM
Subject: Re: [ros-general] About filesystem support...
Brandon Turner wrote:
> >   So... if you
> > are going to use the code from one of the many projects for
> >  ext2/3 drivers around there "when they are good enough", why do the ROS
> >  source has a driver in /reactos/drivers/filesystems/ext2? Is it one of
> >  the popular IFS ext2/3 drivers that has, meanwhile, become "good
> >  enough"? Or is it a ReactOS internal subproject?
> >  
>  I think it is the ext2 from http://sourceforge.net/projects/ext2fsd but
>  it is probably a really old version.  It is rumored to work in our CC
>  branch but not in trunk. 
Ok...
And what do you mean exactly by CC branch?
Don't forget I'm not a developer... :-) However, you don't have to
explain what a "branch" is... I know it's a copy of something from the
trunk that is put in /branches to allow a separate set of commits (and
remains separated from the trunk until someone remerges it's changes)...
But what's the CC branch?
> >   And what about
> > NTFS? Does the driver in
> >  /reactos/drivers/filesystems/ntfs do something? Does it read?
> >  Is it an internal project?
> >  
>  I haven't looked at it in a while but I think that it was just a stub
>  driver that doesn't do anything. 
This question was because the file structure doesn't look like a bunch
of stub functions (which AFAIK normally just report something to a log
system and return an error code)...
Besides, even occupying much less space than the linux-ntfs directory
(and I think that the sizes are comparable even with different APIs), it
could have some functionality, although much less...
JJ
_______________________________________________________
Yahoo! Acesso Grátis - Internet rápida e grátis. Instale
o discador agora!
http://br.acesso.yahoo.com
_______________________________________________
Ros-general mailing list
Ros-general(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-general