Quoting directly from IRC:
[18:22] (Figarocool): hi!
[18:23] (Figarocool): is someone online?
[18:23] (@gigaherz): yes
[18:23] (Figarocool): you a developer?
[18:24] (Figarocool): a loader was developed for a few days to load linux
on ps4
[18:24] (Figarocool): https://github.com/fail0verflow/ps4-linux
[18:25] (Figarocool): would it be possible to port this to start rectos? it
would be something of great visibility for the reactos project
[18:25] (Figarocool): loader
[18:25] (Figarocool): https://github.com/valentinbreiz/PS4-Linux-Loader
[18:25] (Figarocool): on firmware 4.05
[18:25] (Figarocool): ps4 runs on x86
[18:26] (Figarocool): would it be complicated to do this for you?
[18:26] (@gigaherz): I don't own a ps4 and I'm not an expert in the reactos
booting process, so I'm not the right person to ask
[18:27] (Figarocool): could you open a discussion about this?
[18:28] (@gigaherz): well this is IRC, just talking about it is already a
discussion
[18:28] (@gigaherz): but if you want something more "official"
[18:28] (@gigaherz): you can post this information on an email to the
ros-dev mailing list
[18:28] (@gigaherz): (subscribe to the mailing list if you want to see the
replies)
[18:29] (Thedarkb1): You probably could.
[18:33] (CatButts): hmmm
[18:33] (CatButts): unlike PC, PS4 is single hardware configuration
[18:33] (CatButts): getting ReactOS on a PS4? hmmm, that wouldn't hurt
[18:34] (CatButts): [19:25] <Figarocool> it would be something of great
visibility for the reactos project
[18:34] (Figarocool): check:
https://github.com/valentinbreiz/PS4-Linux-Loader
[18:34] (Figarocool): loader to load linux (x86) and driver
[18:35] (Figarocool): however, since reactos and open would be a great
novelty for the knowledge of the os
[18:35] (Figarocool): so it could give a lot of novelties in the media
aspect
[18:35] (Figarocool): you could think about it
[18:36] (@gigaherz): the loading process of NT is very different from linux
[18:36] (@gigaherz): but as I said, because I'm not the right person to ask
[18:36] (@gigaherz): it would be best if you put the information on the
mailing list
[18:36] (@gigaherz): for all the people interested to read
[18:36] (Figarocool): could you open the discussion on the mail?
[18:37] (@gigaherz): I think it would be best if someone who is actually
interested in it would do so
[18:38] (Figarocool): I also say this because of the media aspect
[18:39] (Figarocool): since they are now installing linux to use the
console as a PC
[18:39] (Figarocool): this would be great using reactos
[18:39] (Figarocool): being x86 all windows games and more would be
compatible
<span style="font-family:arial,helvetica,sans-serif; font-size:12px">Talking of which, what's the status of Victor's website for RAPPS submissions?<br>
<br>
H.</span>
<div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">De : gigaherz(a)gmail.com<br>
A : ros-dev(a)reactos.org<br>
Envoyé: lundi 8 janvier 2018 18:28<br>
Objet : Re: [ros-dev] RAPPS Database now maintained in https://github.com/reactos/rapps-db<br>
<div class="gl_quoted">
<div dir="ltr">
<div>\o/ awesome!<br>
</div>
It would be more awesome to have a crowdsourced (moderated) compatibility database to generate these from, but until that's done, this is a really good addition.</div>
<div class="gmail_extra">
<div class="gmail_quote">On 8 January 2018 at 18:15, Colin Finck <span dir="ltr"><<a href="mailto:colin@reactos.org" target="_blank">colin(a)reactos.org</a>></span> wrote:
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all!<br>
<br>
We all wanted the RAPPS Database to leave the main source tree for a<br>
long time. When Alexander Shaposhnikov asked me today if it was possible<br>
to regenerate the rappmgr.cab on every commit, I took the opportunity<br>
and split off the /media/rapps folder (including all history) into its<br>
own repository: <a href="https://github.com/reactos/rapps-db" rel="noreferrer" target="_blank">https://github.com/reactos/<wbr>rapps-db</a><br>
<br>
As a bonus, the public database at<br>
<a href="https://svn.reactos.org/packages/rappmgr.cab" rel="noreferrer" target="_blank">https://svn.reactos.org/<wbr>packages/rappmgr.cab</a> is now automatically<br>
updated with every commit to that repository.<br>
<br>
I hope you'll like that change :)<br>
<br>
<br>
Cheers,<br>
<br>
Colin<br>
<br>
______________________________<wbr>_________________<br>
Ros-dev mailing list<br>
<a href="mailto:Ros-dev@reactos.org">Ros-dev(a)reactos.org</a><br>
<a href="http://www.reactos.org/mailman/listinfo/ros-dev" rel="noreferrer" target="_blank">http://www.reactos.org/<wbr>mailman/listinfo/ros-dev</a></blockquote>
</div>
</div>
<!-- PART SEPARATOR --><br>
<br>
<br>
_______________________________________________<br>
Ros-dev mailing list<br>
Ros-dev(a)reactos.org<br>
http://www.reactos.org/mailman/listinfo/ros-dev</div>
<div class="gl_quoted"> </div>
</div>
Hi all!
We all wanted the RAPPS Database to leave the main source tree for a
long time. When Alexander Shaposhnikov asked me today if it was possible
to regenerate the rappmgr.cab on every commit, I took the opportunity
and split off the /media/rapps folder (including all history) into its
own repository: https://github.com/reactos/rapps-db
As a bonus, the public database at
https://svn.reactos.org/packages/rappmgr.cab is now automatically
updated with every commit to that repository.
I hope you'll like that change :)
Cheers,
Colin
Hi all,
I just finished converting our "project-tools" SVN repo to Git and
splitting it up into individual repositories in the process.
These repos have already been uploaded to GitHub
(https://github.com/reactos), so you can have a look and comment easily.
Welcome these 18 new repositories:
* ahk_tests
* buildbot_config
* git-tools
* irc
* Message_Translator
* monitoring
* packmgr (Archived)
* project-tools-archive (Archived)
* Qemu_GUI
* reactosdbg
* Release_Engineering
* RosBE
* rosev_ircsystem
* rosev_jameicaplugin
* RosTE
* sysreg2
* sysreg3 (Archived)
* vmwaregateway
I haven't given anyone write access yet. I think this is acceptable for
the moment while we check if there are any outstanding issues with the
conversion.
Please let me know until January 7. If everything is okay by then, I
will add write access again and officially move development away from
the project-tools SVN repo.
Have a good start into 2018!
Colin
Hello everyone,
Lately I was continuing working on my setup_improvements branch:
https://github.com/HBelusca/reactos/commits/setup_improvements
(whose main purpose, I recall, is to share a maximum of installation code
between our working 1st-stage text-mode usetup and our 1st-stage GUI-mode
reactos.exe setup that needs to be implemented).
The last results of this is that I am now able to install ReactOS files to a
user-provided directory using the GUI-mode setup!
As Im developing under Windows I tested the file-copying part of the
installer (which is, at the time of writing, the latest part of installation
code I has been able to share between the two installers) on Windows.
You can see the demo here: https://i.imgur.com/xF97hv1.gifv
The animated gif also demonstrates the capability of the installer to halt
file copying if the user pops the installation-cancel confirmation dialog
out; file-copying is resumed when the user does not want to cancel the
installation, but it is stopped when the user really cancels the
installation.
And of course, the file-copying status is displayed with an animated
progress-bar.
I have worked out a bit the wizard transitions, but some work remains to be
done, especially for the partitioning step (currently Im hardcoding in the
GUI installer the disk & partition where I want the copy to take place).
One can note in the animation that the preparation of the list of files to
be copied seems to take a while: indeed, the shared installation code works
exclusively with NT paths. However, when this shared code is used in the
win32 GUI-mode installer, this code calls inside setupapi.dll functions to
manage the installation file queue (in usetup on the contrary, it uses
instead a file queue implementation that works directly with NT paths). As a
consequence, I need to convert the NT paths back to Win32 ones before
feeding them into the setupapi functions, and this is not trivial. I want to
improve this conversion by caching some of the computed results.
Enjoy!
Best regards,
Hermès
P.S.: Please dont put that on Twitter since this is under heavy
work-in-progress and this demo hasnt been done under ReactOS at all.
Hi all!
If we follow our usual schedule, the December Status Meeting would be
today. With such a late announcement and many people still on holidays,
I suggest postponing it to next Thursday, January 4, 2018. Time will be
19:00 UTC as always.
I already asked on #reactos-dev and got some approvals, so consider this
the official meeting invitation :)
This also gives you one week from now for agenda proposals.
Additionally, we have got some new contributors in the recent months.
If you think you should join the meeting or know somebody who should
join, please let me know in advance.
See you all next year!
Colin
Good day everyone.
I'm talking about this repo:
https://github.com/reactos/reactos-deprecated-gitsvn-dont-use
To prevent pull-requesting to it I suggest to use new GitHub feature "archive this repository".
To enable it, just open the "Settings" page and go to the bottom.
"Archived" repos are marked as read-only and could not be pull-requested.
It's also would be nice to disable unused "Projects" tab in this repo for the great justice of perfectionism.
___
Dmitry D. Chernov
Hi all!
With all release preparations done, we can finally give a release date
for ReactOS 0.4.7: Tomorrow, Wednesday, 6th December 2017. During that
day (European time), the release will be published.
A Press Kit for ReactOS 0.4.7 is already available:
https://sourceforge.net/projects/reactos/files/ReactOS/0.4.7/ReactOS-0.4.7-…
Feel free to send it to interested parties to let them know about the
upcoming release in advance.
Best regards,
Colin Finck
Hi,
Let's try not removing (ZAPPING) API due to future use okay?
Just #if it out with the correct __NTZYX__ thing.
So if I wish to have VISTA or Server 201X, I can select it while running
the configuration script. Do it this way so someone could select Server
2003 (Default now) later on.
Same or better TEAM!
Think about what will be needed later on.
ZAPPING OUT!
James
Hi all!
Recenly a new Reddit post came up on #reactos IRC:
https://redd.it/7jj0oa. Interesting stuff.
A person is giving away ~5000 BTC for charitable causes. We can apply
via the website but it must be done by someone from ReactOS e.V.
--
Cheers,
Alexander Shaposhnikov
Hi all,
I have been looking into our HALs recently on the promise that it is a
huge mess that needs fixing. Well, as a start I could imagine merging
our 6 possible x86 HALs (Legacy, ACPI, APIC, ACPI+APIC, SMP, SMP+ACPI)
into a single one, even if Windows ships individual ones. I see many
advantages of that:
* Less duplications and reduced mess: Right now, the APIC HAL hangs at
HalpCalibrateStallExecution during boot, a function that has been fixed
and universally implemented in all non-APIC HALs. The APIC HAL also
duplicates HalpInitializePICs as HalpInitializeLegacyPIC.
If you look at the SMP code, it didn't even receive the last build
system changes and has conflicting implementations for APIC functions.
A single x86 HAL would ensure that all possible configurations are
maintained.
* Future-proof: How is one going to implement newer features like x2APIC
with a structure like that? Would it get another HAL, be integrated into
the APIC HAL, or what?
We wouldn't have such problems with a single x86 HAL.
* Less setup work and testing: Currently, 1st stage setup detects the
computer type and installs the appropriate HAL. As such, every
additional HAL needs to be added to 1st stage setup code.
The user is also able to select a custom HAL during setup, even if it
wouldn't work on the machine. We should give neither the user nor the
setup the ability to decide. The HAL itself knows best at boot-up what
features to enable and what not.
* Convenience: The same ReactOS installation could be used on several
different x86 computers.
So is this the way to go or do I miss something important?
Best regards,
Colin
I would move to the Win8+ HAL Model -- a single HAL for APIC, ACPI with
runtime support for UEFI (if present) and MP (if present).
If people still want to run on a PIC VM (why???) or old computer, then we
can also maintain the HAL PIC x86 for UP.
Hence there would only be 2 HALs.
Best regards,
Alex Ionescu
On Mon, Dec 11, 2017 at 1:07 AM, Colin Finck <colin(a)reactos.org> wrote:
> Am 11.12.2017 um 01:18 schrieb Hermès BÉLUSCA-MAÏTO:> If you basically
> put all the HALs into one, then you obtain bloated stuff (which remains
> in memory for the whole life of the OS). Example: standard HAL is 1MB
> vs. ACPI HAL which is few kBHave you actually checked what makes up this
> difference?
> Hint: hal/halx86/legacy/bus/pci_vendors.ids
>
>
> > Note that if Windows nowadays has only one hal, it's because they now
> support basically only one "architecture"/platform, namely, ACPI
> multiprocessor (to put it simple). It has its pros, but also a lot of cons.
>
> That doesn't mean we need to do the same. We can have one HAL for all
> (Pentium and newer) x86 platforms. The overhead of additional checks at
> boot-up is negligible. That should be a solution for 99% of the people
> out there. The rest may still go and trim down our HAL to their needs.
>
> But let's not pretend we can maintain multiple x86 HALs for all x86
> computers out there. Do you really want to test X HALs with Y different
> systems? Ensure that a legacy HAL runs on a modern ACPI system? What
> would be the point?
>
>
> > Besides this, I've a question about your observation that in the APIC
> hal (not ACPI) there's different implementation of
> HalpCalibrateStallExecution and HalpInitializePICs /
> HalpInitializeLegacyPIC . Isn't it precisely because these stuff are
> completely different from the standard PICs used in platforms for which the
> standard HAL (and possibly the ACPI HAL) are used?
>
> Absolutely not! You need to reprogram the standard PICs also on an APIC
> system, and this is precisely what both functions do. Put them into a
> diff tool to see for yourself.
>
> The same goes for timers. Even with the introduction of ACPI Timers,
> Local APIC Timers, and Time-Stamp Counters, you still need a traditional
> one (like RTC or PIT) for calibration at system startup. Simply because
> the newer ones don't run at a known fixed frequency.
> The Legacy HAL successfully employs an algorithm based on the RTC while
> the APIC HAL unsuccessfully tries to use the PIT.
>
>
> > Actually we should, because the detection might not work (of course in
> our simple case "ACPI UP/MP" vs. "Standard", it's simple, but think about
> other platforms where there can be subtle differences)
>
> Tell me about a single one we cannot detect and which is worth to
> support. I don't recall that we ever recommended our testers to choose a
> different HAL at setup.
>
>
> > And normally it's not the setup that decides about the HAL, but the
> bootloader.
>
> That defies your previous point about the setup initializing the
> registry depending on the HAL.
> If we can let the user select a Legacy HAL in the boot loader after
> installing with an ACPI HAL, it is also technically possible to have one
> HAL that encompasses both.
>
>
> - Colin
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
Test KVM AHK is back on its feet.
After a fight with the package update manager (bug in dnf) and a problem with the primary monitor setting,its building and testing the last push from AmineKhaldi
Kind regards, Sylvain Petreolle
Le Mardi 28 novembre 2017 23h06, Sylvain Petreolle <spetreolle(a)yahoo.fr> a écrit :
The AHK bot crashes often these days.
I uploaded a crash dump to Fedora and discovered that these crashes are due to the network emulation (SLIRP) used in KVM.
For reference, here is the opened issue : https://bugzilla.redhat.com/show_bug.cgi?id=1509589
Since bugs with previous versions of Fedora take time to be resolved, I'm upgrading the bot to Fedora 27.
Ideas to overcome the SLIRP problems are welcome.
After all, if it crashes the virtual machine, it could also be at the source of other problems.
The AHK tests show randomness in the tests that require network,related to nonblocking mode not working, but it could involve KVM too. Kind regards, Sylvain Petreolle
Hi all!
Let me invite you to the monthly status meeting taking place tomorrow,
November 29, 19:00 UTC.
As always, you will get credentials for our private IRC server shortly
before the meeting.
No agenda proposals have been submitted to me so far. If that doesn't
change, we may have a short meeting just for status reports. Please have
them ready, so we get it done quickly!
FYI, I expect the 0.4.7 Press Release to be ready tomorrow, so we can
soon send out the Press Kit and make the downloads available.
See you tomorrow!
Colin
The AHK bot crashes often these days.
I uploaded a crash dump to Fedora and discovered that these crashes are due to the network emulation (SLIRP) used in KVM.
For reference, here is the opened issue : https://bugzilla.redhat.com/show_bug.cgi?id=1509589
Since bugs with previous versions of Fedora take time to be resolved, I'm upgrading the bot to Fedora 27.
Ideas to overcome the SLIRP problems are welcome.
After all, if it crashes the virtual machine, it could also be at the source of other problems.
The AHK tests show randomness in the tests that require network,related to nonblocking mode not working, but it could involve KVM too. Kind regards, Sylvain Petreolle
IIUC we currently always build rostests, but never rosapps in CI.
Would it be possible to analyze the changed paths instead and
* enable rostests iff modules/rostests/ or sdk/ was changed
* enable rosapps iff modules/rosapps/ or sdk/ was changed?
That should speed up builds that don't change rostests, while also
making sure that changes to rosapps aren't let into master if they break
build.
If this is nontrivial I may have a look at it myself but someone would
need to point me to the right configuration/scripts please.
Thanks!
-Thomas
<span style="font-family:arial,helvetica,sans-serif; font-size:12px">Certainly not a "feature", but just that (certainly because it is only for user-mode AND the out pointer is not optional) the MS dev who introduced these functions didn't want to (or just more simply forgot to) not check for such NULL pointer.</span><br>
<span style="font-family:arial,helvetica,sans-serif; font-size:12px">And thus, if you pass NULL, it's just your fault if your app crashes.</span><br>
<span style="font-family:arial,helvetica,sans-serif; font-size:12px">And of course, since ReactOS also want to behave similarly... we don't check for NULL either!</span><br>
<br>
<span style="font-family:arial,helvetica,sans-serif; font-size:12px">H.</span>
<div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">
<div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">De : xxxx<br>
A : ros-dev(a)reactos.org<br>
Envoyé: mardi 31 octobre 2017 16:10<br>
Objet : Re: [ros-dev] [ros-diffs] [reactos] 01/01: CID 1206831 Dereference after null check<br>
<div class="gl_quoted">
<div dir="ltr">Seems like this API has a 'feature' where by it throws exceptions if <span style="font-size:12.8px">BytesRead is null?</span></div>
<div class="gmail_extra">
<div class="gmail_quote">On Sun, Oct 29, 2017 at 8:02 AM, Jerome Gardou <span dir="ltr"><<a href="mailto:jerome.gardou@reactos.org" target="_blank">jerome.gardou(a)reactos.org</a>></span> wrote:
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">HI,<br>
<br>
that doesn't look good, as shown by <a href="https://reactos.org/testman/compare.php?ids=56275,56276" rel="noreferrer" target="_blank">https://reactos.org/testman/co<wbr>mpare.php?ids=56275,56276</a><br>
<br>
Jérôme<br>
<br>
<br>
Le 29/10/2017 à 11:17, Samuel Serapion a écrit :
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><a href="https://git.reactos.org/?p=reactos.git;a=commitdiff;h=b3b2a23f05e5188dc1475…" rel="noreferrer" target="_blank">https://git.reactos.org/?p=rea<wbr>ctos.git;a=commitdiff;h=b3b2a2<wbr>3f05e5188dc1475961fcd7f036f004<wbr>6d25</a><br>
<br>
commit b3b2a23f05e5188dc1475961fcd7f0<wbr>36f0046d25<br>
Author: Samuel Serapion <<a href="mailto:samcharly@hotmail.com" target="_blank">samcharly(a)hotmail.com</a>><br>
AuthorDate: Fri Oct 20 14:00:32 2017 -0400<br>
<br>
CID 1206831 Dereference after null check<br>
BytesRead is an optional out parameter and must be checked before being written to.<br>
---<br>
sdk/lib/rtl/memstream.c | 3 ++-<br>
1 file changed, 2 insertions(+), 1 deletion(-)<br>
<br>
diff --git a/sdk/lib/rtl/memstream.c b/sdk/lib/rtl/memstream.c<br>
index 0549424ca4..8fe4169fb1 100644<br>
--- a/sdk/lib/rtl/memstream.c<br>
+++ b/sdk/lib/rtl/memstream.c<br>
@@ -185,7 +185,8 @@ RtlReadMemoryStream(<br>
Stream->Current = (PUCHAR)Stream->Current + CopyLength;<br>
- *BytesRead = CopyLength;<br>
+ if (BytesRead)<br>
+ *BytesRead = CopyLength;<br>
return S_OK;<br>
}<br>
</blockquote>
<br>
<br>
______________________________<wbr>_________________<br>
Ros-dev mailing list<br>
<a href="mailto:Ros-dev@reactos.org" target="_blank">Ros-dev(a)reactos.org</a><br>
<a href="http://www.reactos.org/mailman/listinfo/ros-dev" rel="noreferrer" target="_blank">http://www.reactos.org/mailman<wbr>/listinfo/ros-dev</a></blockquote>
</div>
</div>
<!-- PART SEPARATOR --><br>
<br>
<br>
_______________________________________________<br>
Ros-dev mailing list<br>
Ros-dev(a)reactos.org<br>
http://www.reactos.org/mailman/listinfo/ros-dev</div>
<div class="gl_quoted"> </div>
</div>
</div>