2 Dec
2013
2 Dec
'13
1:07 a.m.
Imo, up to me, we ship with minimal drivers to get to 2nd stage, and then
wipe everything with the WDK sample project.
Or we simply don't provide a bootable all-in-one CD. We make two separate
downloads and somehow make an easy-to-use "slipstreamer" that builds the
final CD. How to do this at conferences or with pressed CDs is another
matter.
I agree all of these solutions are ugly, and as Nuno says, also not
guaranteed to work (in the end, it's up to a judge or jury to decide).
Best regards,
Alex Ionescu
On Sun, Dec 1, 2013 at 4:08 PM, Colin Finck <colin(a)reactos.org> wrote:
Aleksey Bragin <aleksey(a)reactos.org> wrote:
To conclude, our existing fastfast totally sucks.
cdfs does too. Fixing
them is a waste of time. Rewriting them - good project, but noone will
use that driver.
So what is the alternative? Shipping ReactOS without any FAT driver? ;)
The license discussions have already evolved to a point where we know
that we can't possibly include the MS fastfat example code in our tree.
What has happened to the FullFAT-powered driver project in the meantime?
Some years ago, it was still praised in high terms and even ready to
implement journaling on top of FAT
(https://www.reactos.org/archives/public/ros-dev/2009-July/011902.html).
- Colin
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev