Re: [ros-dev] NTFS in ReactOS: heise online article

[Sven Barth]

On 07.11.2014 13:19, Pierre Schweitzer wrote:
>   On 07/11/2014 12:05, Thomas Mueller wrote:
> > >   Dear
> > > Thomas, 
> > >   This source of such article is a post from
> > > reboot.pro
> > >  (http://reboot.pro/topic/20149-ntfs-now-supported-in-reactos-livecd/)
> > >  where I report this progress and ask for help. 
> > >   On ReactOS website, you don't have such
> > > strong report, but the piece of
> > >  information exists, spread in various places. People started talking
> > >  about it on boards a few days ago. You have a short report about it in
> > >  the latest ReactOS developer meeting minutes
> > >  (https://www.reactos.org/node/909). And finally, the commits made on
> > >  NTFS where kind of explicit about the progresses (coming along with
> > >  pictures:
> > >
> > > https://git.reactos.org/?p=reactos.git&a=search&h=HEAD&st=commi…)it&s=[NTFS]).
> > >   Note that the 0.3.17 release has initial, but not
> > > full (release process
> > >  was started before everything could be developed) NTFS support. Testing
> > >  from trunk is then the preferred method. 
> > >   Cheers, 
> > >   Pierre Schweitzer <pierre at reactos.org>
> >  Thanks for the link!
> >
> >  I can see why, in a developing OS or application, following trunk would be the indicated
> > method.
> >
> >  Problem is I have no hard-drive space (actually I do, but it's GPT-partitioned).
>  We indeed so far don't support GPT disks. It would require some changes
>  to be done in our storage stack.
>  This is somehow on my todo list, but it's kind of huge ;-). 
Out of curiosity: why is it so extensive to implement? From my 
understanding (I'm currently working with partition tables at work) GPT 
should be simpler to handle than MBR. Or is this because it needs to be 
implemented in a Windows compatible way? If so what did they change 
there to make implementing GPT such a "problem"?

Regards,
Sven