Google Summer of Code 2011 Ideas
- 1 IFS Wrapper Driver
- 2 Performance Data Registry
- 3 Terminal Services
- 4 Security Controls
- 5 Font Driver
- 6 Theme Service
- 7 Serial Over USB
- 8 EFI Support
- 9 ACPI HAL
- 10 GUI 1st Stage Installer
IFS Wrapper Driver
- Implementation of generic wrapper driver.
- Implementation of FAT driver based on wrapper driver using FullFAT library as a basis.
- Implementation of NTFS driver based on wrapper driver using NTFS-3G as a basis.
Performance Data Registry
- Centralized exporting of system data (counters) meant for the performance data hive by declaring in-memory structures for storing values from the scheduler, memory manager, and I/O manager.
- Tracking system for application performance counters. Allow applications to register the presence of a performance counter DLL through the HKLM hive and use the DLL to read the performance data.
- Implement querying of performance counter data through the registry API.
- A wrapper API was released in Vista that abstracts away the need to use the registry API to access performance counter data. Implementing this would considerably ease access to the performance data hive in ReactOS.
- Description of performance counters and types in Windows 2003: http://technet.microsoft.com/en-us/library/cc776490%28WS.10%29.aspx
- Performance counter data structures: http://msdn.microsoft.com/en-us/library/aa373093%28v=VS.85%29.aspx
- Example code for accessing performance data through registry: http://msdn.microsoft.com/en-us/library/aa373219%28v=VS.85%29.aspx
Implement support for terminal services, allowing inbound remote desktop connections to ReactOS. This requires implementation of a video driver able to handle output to multiple window sessions.
Terminal services support would allow ReactOS to service as a terminal server/thin client server. Organizations that wish to provide a shared workstation with Windows would have a free alternative that does not have complex licensing terms covering multi-session usage. The display driver for terminal services can also be used to support fast user-switching and even possibly multi-monitor support.
- Implementation of video driver for multi-session displays.
- Implement Terminal Service for accepting and managing remote desktop connections.
Implement support for user permissions based on Access Control Lists.
This will allow separation of users into groups and better control over user privileges in ReactOS. Security controls will then allow supporting multiple users on the same system.
- Implement the ability to register a library with every application running in a session. Theme support requires that the uxtheme library be injected into applications.
- Implement the system service that handles loading and parsing of themes and providing uxtheme with the bitmaps and configurations of a theme. The theme service must also be able to create remote threads into the winlogin process when a user logs in. This is due to the theme service running in session 0. While in XP and below the first user that is logged in is also in session 0, additional users logging in will be put into a separate session. On Vista and higher, all user logins are given a separate session from session 0. The remote thread started by the theme service facilitates transfer of theme information to the uxtheme for applications of each session.
- The GINA library used for user login must be extended to notify the theme service of user logins.
- Modify the uxtheme library to correctly paint non-client areas of Windows and also remove the ability to load themes. This responsibility should be left to the theme service.
Serial Over USB
Implement a driver for USB/serial debugging support. With the decreasing number of systems with a serial port, another mechanism for outputting debug information is needed. A low level USB driver that can output in serial format would help expand the number of platforms that can be used test ReactOS on. USB to serial adapters are quite prevalent, but outputting debug information out a USB port requires bypassing the need for traditional drivers or even a USB stack. This driver will serve a similar role as the current KDCOM driver.
Support running and booting of ReactOS on EFI systems instead of BIOS systems. This would allow running ReactOS on Intel Macs and other systems that do not use BIOS. Support must be added to freeloader and the ReactOS HAL. Lack of the VGA BIOS must be addressed as the ReactOS boot process relies heavily on one being present for display during the boot process.
Ability to boot natively on Intel Macs would provide ReactOS with a relatively stable hardware platform for testing purposes thanks to Apple's hardware design philosophy. It would also present Mac users with another alternative to running Windows applications.
- Modification of freeloader to be able to interface with EFI.
- Modification of HAL to be able to interface with EFI.
- Modify boot video driver to work without VGA BIOS.
- Boot ReactOS to a working desktop.
Implementation of a Hardware Abstraction Layer that can interact with the ACPI interface for power management and device configuration.
Most modern motherboards possess ACPI support. ReactOS’ system components are ACPI aware but cannot truly use ACPI until the hardware abstraction layer supports the specification. Proper power management would require that the OS support ACPI and until the entire hardware interface stack in ReactOS has support implemented, ReactOS will be limited to running in a compatibility mode.
- Be able to enumerate all ACPI-enabled devices and interfaces on a system.
- Be able to shut down the computer through ACPI.
GUI 1st Stage Installer
To make ReactOS more user friendly for installation, a GUI installation instead of a rather limited text-mode installer is needed. This could be run off of the live CD and act as a frontend to the disk formatter and installer we already have implemented.
Having a GUI installer would allow the project to merge the bootcd and livecd and ensure that the livecd gets more testing to make sure it is not broken and simply neglected. A GUI installer would also be less intimidating to new users, especially those used to Vista or 7's installer.
- Complete the disk formatting functions that need to be exported for use by an installer.
- Create a Windows application that can install ReactOS.