ReactOS cmd.exe "Fork"

All development related issues welcome

Moderator: Moderator Team

Post Reply
Posts: 3
Joined: Tue Mar 29, 2016 10:55 pm

ReactOS cmd.exe "Fork"

Post by AJMartel »

Good Day, Great Project!

I am currently working on a "Free Open Source" Incident Response Triage tool built specifically for the Windows Forensic Analysts Community.
My problem is that the MS Windows "cmd.exe" has proven not to be cross compatible.
In looking for a solution to my problem, I stumbled on ReactOS.

I have "Forked" the ReactOS cmd.exe source, and added some functions from Didier Stevens with his permission.
( ... e-cmd-exe/)
His functions are of great value to enable collection of Forensic Artefacts.

I am requesting ReactOS Dev Team's permission to fork the modifications on Github.

Reference to ReactOS Dev Team are viewable using the "ver /c" command.
I have removed other references as I plan to do more modifications for the IRTriage project. ... er/cmd.exe

Please let me know if I require other modifications, to respect the great work you have done.

Posts: 859
Joined: Sat Dec 20, 2008 5:55 pm
Location: Izmir, TR

Re: ReactOS cmd.exe "Fork"

Post by erkinalp »

GPL allows you to fork for any use. You would need permission to get changes back merged.
-uses Ubuntu+GNOME 3 GNU/Linux
-likes Free (as in freedom) and Open Source Detergents
-favors open source of Windows 10 under GPL2

Posts: 1028
Joined: Tue May 07, 2013 9:18 pm
Location: California, USA

Re: ReactOS cmd.exe "Fork"

Post by middings »

Perhaps if this directory, ... /shell/cmd, included a license.txt file then AJMartel's question would already be answered.

Section 2c of the GPLv2 suggests to a blockhead like me that the ReactOS cmd.exe should display something about its license when it starts.

Code: Select all

c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
Acceptance of ReactOS tools by other FOSS projects is good for the ReactOS Project and, it is to be hoped, for the whole FOSS community.

"Let us stand on each others' shoulders; not each others' toes."--Dennis Allison in dr. dobb's journal of Tiny BASIC Calisthenics & Orthodontia, Running Light Without Overbyte (copyright 1975, People's Computer Company)

User avatar
Posts: 1584
Joined: Fri Feb 15, 2008 9:44 pm
Location: Czechia

Re: ReactOS cmd.exe "Fork"

Post by Black_Fox »

I think unless specified in a subdirectory, the parent dir licence applies - says GPLv2.

Now, since cmd.exe is a part of ReactOS project and ReactOS allows you to display the GPLv2 licence during the installation (both 1st and 2nd stage), I believe the Section 2c is satisfied (unless we want to mention GPLv2 for every user-launchable binary). If not, well, then the exception will apply :-)

If you fork on GItHub, keep the source open and the license stays the same, you can do pretty much any modification to the code.

Posts: 3
Joined: Tue Mar 29, 2016 10:55 pm

Re: ReactOS cmd.exe "Fork"

Post by AJMartel »

Thanks for the replies.

I had read the GPL 2 licence, understood that I could fork the code, I did.

My intent is to let the developers know, that I like what they have done so much that I am using it in my own project, and
politely give the opportunity to the developers to let me know if I have overstepped my boundaries, so that I can correct
the issue before I offend anyone.

Thanks again, all my respect to the developers!

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest