I'm more a fan of the ISC license, myself.

*goes to google that

Permissive like BSD and MIT but has the shortest text while keeping the bare minimum requirements

Oh. Cool.

BSD three-clause license: `Copyright (c) <YEAR>, <OWNER> All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.`

Wow.

That is really small

There's the two-clause variant, which eliminates clause three

Then there's the MIT, which is even smaller... Copyright (c) <year> <copyright holders> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

The ISC license is the smallest "common" permissive license (excluding the WTFPL) Copyright (c) 4-digit year, Company or Person's Name <E-mail address> Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

OpenBSD and Node.js's npm both have preferences for the ISC license

Make wiki page and type in stuff

I dunno

I don't know

WHY WOULD YOU RUN SOMETHING AS BEAUTIFUL AS ARCH ON FUCKING WINDOWS 10?!!!?!!?!!!!!!! THIS IF FUCKING RIDICULOUS!!!!!!!!!

Despicable

WHY WOULD YOU RUN SOMETHING AS BEAUTIFUL AS ARCH ON FUCKING WINDOWS 10?!!!?!!?!!!!!!! THIS IF FUCKING RIDICULOUS!!!!!!!!!

And remap /bin/sh to /opt/powershell/bin/powershell

That is fine

And remap /bin/sh to /opt/powershell/bin/powershell

This is not

This is not

You're right, it'll break shell scripts; it's smarter to change the login shell in /etc/passwd

what about them?

Do bat scripts work?

Do bat scripts work?

Yes, there's an implementation of cmd.exe

I don't know; probably.

if there's something that doesn't work, there's abolutely nothing stopping you from downloading, installing, and using 4NT to run your batch scripts

nah probably not 100% — there's always bugs and unknown features

however, it should be good enough to run most .bat scripts, and good enough for many .cmd scripts

https://en.wikipedia.org/wiki/Take_Command_Console

use this if you have a problem

If you plan on installing any user software, yes

Why, is that a problem?

you know

you could just rm -rf ~/porn

that should free up like 5TB

What tests?

You do realise that the thing you're looking at on the website is for unit testing

which is completely removed from applications testing

you're doing applications testing; this has no place there

that's unit testing

Do you even know what unit testing is?

Unit testing is when you test each individual API function

to make sure it behaves as it does on Windows

You write a tiny program, called a "test unit"

it calls a function with various parameters and compares it's behavior against what's expected

it's a part of reverse engineering, in this case

since the test units are ran on Windows and revised until it's understood clearly how Windows behaves

then the ReactOS codebase is worked on until it delivers identical behavior

I just told you.

What Windows is considered reference?

I think all of the 32-bit i386 ones.

but I'm not sure

You mean that they test the behavior of all win api functions in all 32bits versions? That is a lot job.

You mean that they test the behavior of all win api functions in all 32bits versions? That is a lot job.

Test units are designed to be automated.

Hell, the entire unit testing process is fully automated

Umm

Quit repeating yourself because you're not getting an answer quickly enough, it's annoying and you're an asshole for doing it.

But you must chance the source anyways, so it is a lot job too.

Change

But you must chance the source anyways, so it is a lot job too.

Not really; once a test unit is deemed "correct", there's no need to further update it.

But this doesnt have sense

I believe on the userland side, ReactOS targets NT 5.2 (Server 2003/XP x64) and NT 6.3 (Windows 8.10

But this doesnt have sense

You don't make sense.

I mean, why i want all versions.

I mean, why i want all versions.

Can you please rephrase this? This statement doesn't make sense to me.

I believe on the userland side, ReactOS targets NT 5.2 (Server 2003/XP x64) and NT 6.3 (Windows 8.10

Now, it makes sense.

Did you read every word I wrote or just the ones you wanted? Because I already included the answer in that statement.

Yes

That's where it's implemented.

I take it you poorly understand the design of an operating system

the kernelland is targeting NT 5.2 only (i.e., it will use drivers meant for Windows Server 2003 or earlier NT-based releases)

The concept of userland is universal to nearly every operating system, not just ReactOS.

It's everything that runs as regular programs and the API libraries (DLLs) that those programs use

the kernel and associated drivers are kernelland, everything else is userland

Well kernel land and userland is a feauture of the processor.

That too

I can mark a page as i want.

but it's also the design separation in operating systems

I know.

It's probably just as unstable here

As long as you also include a $20 USD deposit to my PayPal account.