Pete Batard schreef op 3-1-2014 3:59:
> If you want to test, you can pick the latest ALPHA from:
> http://rufus.akeo.ie/downloads/
Awesome, will test using USB2 ports.
> Currently, the way this works is through installing Syslinux (v4.07) and
> mboot.c32 so that setupldr.sys can then be invoked (see the
> /syslinux.cfg created by Rufus on the drive).
>
> Also, for the time being, only setupldr.sys will be referenced (no
> freeldr.sys) on account that:
FreeLDR as multiboot-kernel only looks at freeldr.ini at C:\ , no idea
if your created USB stick counts as C: or A:.
Also ReactOS might write freeldr.ini in some special way on FAT drives,
I've never been able to open/modify it using a DOS text editor.
> 1. The Syslinux's menu.c32 file is rather large, and I want to keep
> Rufus small, so I don't want to embed it in the application (which is
> also the mais reason why Rufus doesn't include native GRUB support). But
> this means that user selection from a menu is not available.
>
> 2. When testing, I couldn't get freeldr.sys to do much when booted from
> USB... though that was most likely because I hadn't actually installed
> ReactOS anywhere.
Smallest I've gotten FreeLDR is through using
SYSLINUX -> MEMDISK -> FLOPPY.GZ where floppy.gz is a compressed ReactOS
startup diskette image. SYSLINUX -> MBOOT.C32 -> FREELDR.GZ might also
work instead.
> Still, I'm hoping that making the creation of a bootable UFD easier for
> ReactOS will help encourage more people to test it and help the project.
I've always hoped for Syslinux -> Memdisk/GRUB -> ReactOS.ISO/IMG simply
to overcome lack of mass storage controllers drivers by running from RAM.
> Of course, I'm also open to suggestions to try to improve support for
> ReactOS in Rufus, if you want something specific. For instance, I should
> point out that the syslinux.cfg created by Rufus is written before any
> of the ISO files are copied over. Thus, if the ReactOS ISOs were to
> include their own syslinux.cfg & menu.c32/vesamenu.c32, it would be very
> easy to provide menu selection for the user when booting from USB, even
> as the ISOs are not Syslinux/Isolinux based.
So right now the installer ISO works but not the LiveCD/USB?
[ https://www.reactos.org/getbuilds ] with rev 61493
Thanks for having implemented the support Pete! :)
Have fun with HaikuOS :)
best wishes for 2014,
Bernd
Hi!
since 2013 is almost over, it is time to make some plans for 2014.
My primary goals for 2014 are:
- Completing the user account management, user logon and password change.
- Fixing winlogon.exe in order to enable users to lock and unlock the
computer and to change their identity (log-off and log-on again).
- Fix potential bugs in userenv.dll. We need to get rid of the
administrator logon hack in syssetup.dll.
- Fix the system shutdown: We need to terminate applications and
services before the machine shuts down.
Secondary goals are:
- Implement PNP support for scsiport.sys.
- Improvements to PNP and driver installation.
- Get some legacy hardware working (parallel port, PCMCIA).
The items of this list and their priorities are not fixed. I reserverve
the right to make changes to this list or to work on something entirely
different, without prior notice.
Happy new year!
Regards
Eric
Hi,
this message is a bit provocative, but please don't be offended by it.
You all did a wonderful work during this year. Thank you!
It's very good to see the work is going on. Just for fun, when I had
spare 15 minutes, I decided to check, what was done in the win32
subsystem during this year by the major, respectable and very old time
ReactOS developer, and whether my proposal with Arwinss still stands or not.
Here is what I found: (analyzing ~ 62 commits by jimtabor):
- 25 revisions: Fixes/hacks of our code (ReactOS-specific bug, works in
Wine, sometimes says in comments "//// ReactOS : Justin Case something
goes wrong.") (revs 58528, 58562, 58563, 58633, 58773, 58999, 59000,
59201, 60054, 60587, 60590, 60592, 60622, 60626, 60659, 60676, 60677,
60881, 61078, 61079, 61142, 61250, 61251, 61292, 61458)
- 13 revisions: Syncs with Wine (revs 59157, 59158, 59159, 60763, 60784,
60807, 60820, 60858, 60863, 60865, 60867, 61244, 61422)
- 14 revisions: Own code development or rewriting old code, some of
which might have been derived from ancient versions of Wine.
(60387, 60389, 60394, 60539, 60599, 60602, 60660, 60682, 60683, 60684,
60718, 60883, 60976, 60992)
- 1 revision: attempt to fix a bug found in Wine (revision 60054, issue
CORE-6024)
You don't need to be a scientist to see that 61% of the changes went
into fixing ReactOS specific bugs or just bringing in newer Wine code to
fix old Wine bugs. Remaining 22% of efforts was spent on actually
developing our own, assumingly better code, and just 1 revision was
spent on such a glorious thing as fixing Wine's bug.
ReactOS is a just for fun type of project, so I highly appreciate that
efforts were put into all of the above!
However, I still think that it would be beneficial if someone would put
similar efforts into Arwinss to eliminate the need to bring in hacks and
fix stuff which works in Wine for years already, and focus on developing
only those parts which we obviously can't share (GDI, hardware
accelerated graphics, whatever else).
I lack time to do this myself, but if anyone volunteers I would be glad
to help, share my experience and think up of interesting tasks. Like,
getting Arwinss to work in Windows 2003 instead of its native subsystem,
which would be a nice test.
Regards,
Aleksey Bragin
On 2013-12-25 23:47, pschweitzer(a)svn.reactos.org wrote:
> +TryWithVolumeName:
> + /* If we didn't find anything, try differently */
> + if (DeviceLength < 2 * sizeof(WCHAR) || DeviceString[2] != L':')
This looks like a buffer overrun. Did you mean < 3 * sizeof(WCHAR)?
A pity.
-------- Original Message --------
Subject: Your stand proposal for ReactOS has been rejected
Date: Mon, 16 Dec 2013 22:28:19 +0100 (CET)
From: FOSDEM Stands Team <stands(a)fosdem.org>
To: Aleksey Bragin <aleksey(a)reactos.org>
Hi Aleksey,
The FOSDEM stands team is sorry to have to inform you that your request
for a stand for ReactOS has been rejected.
We have received almost twice as many proposals as we could accept,
and we regret not being able to give everyone a stand.
We hope to see you at FOSDEM 2014 in a different capacity regardless.
Kind regards,
Wynke Stulemeijer
FOSDEM stands team
This is a suboptimal way of handling it, because it will cause the
compiler to instantiate all GUIDs in all compilation units. When linking
only one will be selected for the executable, but still it increases the
size of all object files. If it is to allow a precompiled header, I
suggest adding an additional guid.c file, that only includes the guid
headers, not the precompiled header.
Timo
Am 24.12.2013 21:58, schrieb akhaldi(a)svn.reactos.org:
> Author: akhaldi
> Date: Tue Dec 24 20:58:27 2013
> New Revision: 61381
>
> URL: http://svn.reactos.org/svn/reactos?rev=61381&view=rev
> Log:
> [USBSTOR]
> * Define INITGUID in the main header.
> CORE-7716
>
> Modified:
> trunk/reactos/drivers/usb/usbstor/usbstor.c
> trunk/reactos/drivers/usb/usbstor/usbstor.h
>
> Modified: trunk/reactos/drivers/usb/usbstor/usbstor.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/usb/usbstor/usbsto…
> ==============================================================================
> --- trunk/reactos/drivers/usb/usbstor/usbstor.c [iso-8859-1] (original)
> +++ trunk/reactos/drivers/usb/usbstor/usbstor.c [iso-8859-1] Tue Dec 24 20:58:27 2013
> @@ -10,7 +10,6 @@
>
> /* INCLUDES ******************************************************************/
>
> -#define INITGUID
> #include "usbstor.h"
>
> #define NDEBUG
>
> Modified: trunk/reactos/drivers/usb/usbstor/usbstor.h
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/usb/usbstor/usbsto…
> ==============================================================================
> --- trunk/reactos/drivers/usb/usbstor/usbstor.h [iso-8859-1] (original)
> +++ trunk/reactos/drivers/usb/usbstor/usbstor.h [iso-8859-1] Tue Dec 24 20:58:27 2013
> @@ -1,5 +1,7 @@
>
> #pragma once
> +
> +#define INITGUID
>
> #include <ntddk.h>
> #include <usbdi.h>
>
>
>
Hi Eric,
I know this has been discussed before, but should we not just bite the bullet and replace this driver with the Microsoft driver.
The MS_LPL license allows it to be used in reactos, and it would certainly get rid of any unknowns and give us a reliable filesystem to work from.
http://code.msdn.microsoft.com/windowshardware/fastfat-File-System-Driver-1…
Ged.
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of ekohl(a)svn.reactos.org
Sent: 29 November 2013 14:06
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [ekohl] 61145: [FASTFAT] FsdGetFsVolumeInformation: Return volume creation time.
Author: ekohl
Date: Fri Nov 29 14:05:43 2013
New Revision: 61145
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 28th of November, 19:00 UTC. Put that into your
calendars so you don't forget. And that's tomorrow!
IRC service will only be started shortly before the meeting. Your
participation passwords and server address will be emailed to you
shortly before the meeting starts, and they are going to be different
once again as they are not stored in any database. Hopefully it's not
much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Pierre before the meeting started to get one.
The agenda will be posted shortly before the meeting, suggestions are
welcome (send them to me shortly before the meeting starts). Hermes sent
the first suggestion well before the meeting, so please follow his
example and send your suggestions too.
Regards,
Aleksey Bragin
I heard that ReactOS is nearly 80 or not yet 80 percent complete.
I feel that if we are seriously going to for true compatibility with
Microsoft Windows it may be a necessary evil to contact Microsoft about this
MS-LPL license--and other things.
It may be that don't really care either way. It may be they do. But its
better to know then not to know in this case I feel. I know the feelings
about proprietary code and avoid trade secrets. But what if a good
relationship with Microsoft makes or breaks ReactOS?
I mean the worst thing that Microsoft will do is say no, or give bogus terms
of use. But your expecting that.
What if they start to contribute to ReactOS because they see you have a good
product, and you are reputable people.
-------Original Message-------
From: ros-dev-request(a)reactos.org
Date: 11/29/13 14:32:25
To: ros-dev(a)reactos.org
Subject: Ros-dev Digest, Vol 111, Issue 24
Send Ros-dev mailing list submissions to
ros-dev(a)reactos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://www.reactos.org/mailman/listinfo/ros-dev
or, via email, send a message with subject or body 'help' to
ros-dev-request(a)reactos.org
You can reach the person managing the list at
ros-dev-owner(a)reactos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Ros-dev digest..."
Today's Topics:
1. Re: [ros-diffs] [ekohl] 61145: [FASTFAT]
FsdGetFsVolumeInformation: Return volume creation time.
(Alexander Andrejevic)
2. Re: [ros-diffs] [ekohl] 61145: [FASTFAT]
FsdGetFsVolumeInformation: Return volume creation time.
(Pierre Schweitzer)
3. Re: [ros-diffs] [ekohl] 61145: [FASTFAT]
FsdGetFsVolumeInformation: Return volume creation time.
(Herm?s B?LUSCA - MA?TO)
4. Re: [ros-diffs] [ekohl] 61145: [FASTFAT]
FsdGetFsVolumeInformation: Return volume creation time.
(Aleksey Bragin)
----------------------------------------------------------------------
Message: 1
Date: Fri, 29 Nov 2013 17:05:12 +0000
From: Alexander Andrejevic <theflash(a)sdf.lonestar.org>
To: ReactOS Development List <ros-dev(a)reactos.org>
Subject: Re: [ros-dev] [ros-diffs] [ekohl] 61145: [FASTFAT]
FsdGetFsVolumeInformation: Return volume creation time.
Message-ID: <20131129170512.GB11454(a)SDF.ORG>
Content-Type: text/plain; charset=us-ascii
I suppose it depends on how you interpret it.
To me, "...extend only to the software or derivative works that you create
that run
on a Microsoft Windows operating system product" sounds like the program
must run
on Windows exclusively. It's not "... that you create to run ...", but "...
that you
create that run ...".
Regards,
Alexander
On Fri, Nov 29, 2013 at 05:55:08PM +0100, David Quintana (gigaherz) wrote:
> I do not agree on the "unless it's on Microsoft Windows" part. The
> license grants apply if it is "created to run directly" on windows,
> which I understand as "it can run anywhere else, also, just as long as
> it runs in windows without an intermediary".
>
> On 29 November 2013 17:51, Alexander Andrejevic
> <theflash(a)sdf.lonestar.org> wrote:
> > Fastfat is located inside its own binary, so this is considered "mere
aggregation", and
> > that is not the problem. (See https://www.gnu.org/licenses/gpl-faq
html#MereAggregation).
> > The problem is that you don't even have a license to use it or
distribute it, unless it's
> > on Microsoft Windows.
> > Then again, I'm not a lawyer either and I could be wrong too. It would
be great if someone
> > who knows a lot about licenses explained this.
> >
> > Regards,
> > Alexander
> >
> > On Fri, Nov 29, 2013 at 05:35:21PM +0100, David Quintana (gigaherz)
wrote:
> >> The exact words of the license, as seen at
> >> http://www.ohloh.net/licenses/mslpl (I couldn't find a better link for
> >> it), are:
> >>
> >> "4. (F) Platform Limitation- The licenses granted in sections 2(A) &
> >> 2(B) extend only to the software or derivative works that you create
> >> that run on a Microsoft Windows operating system product."
> >>
> >> Excluding that term, the rest of the license is mostly a
> >> differently-worded BSD license. If it only needs to be tested in
> >> windows to ensure that it works there, then there should be absolutely
> >> no problem including it in ReactOS, as long as the terms don't
> >> conflict with the other licenses' terms. And GPL with the ReactOS
> >> exception, as far as I can tell, allows it. I'm not a lawyer, though,
> >> so I could be wrong.
> >>
> >> On 29 November 2013 16:17, Alexander Andrejevic
> >> <theflash(a)sdf.lonestar.org> wrote:
> >> > Hi Ged,
> >> >
> >> > Are you sure that we can use software released under the MS-LPL? It
has a rather weird
> >> > limitation in section 4, which says that you can only use it on a
Microsoft Windows operating system product".
> >> > Since ReactOS is not Windows, that would mean we can't use it.
> >> > Please correct me if I'm wrong.
> >> >
> >> > Regards,
> >> > Alexander
> >> >
> >> > On Fri, Nov 29, 2013 at 02:58:51PM -0000, Ged Murphy wrote:
> >> >> Hi Eric,
> >> >>
> >> >> I know this has been discussed before, but should we not just bite
the bullet and replace this driver with the Microsoft driver.
> >> >> The MS_LPL license allows it to be used in reactos, and it would
certainly get rid of any unknowns and give us a reliable filesystem to work
from.
> >> >>
> >> >> http://code.msdn.microsoft
com/windowshardware/fastfat-File-System-Driver-135bdf34/view/SourceCode
> >> >>
> >> >> Ged.
> >> >>
> >> >>
> >> >> -----Original Message-----
> >> >> From: ros-diffs-bounces(a)reactos.org
[mailto:ros-diffs-bounces@reactos.org] On Behalf Of ekohl(a)svn.reactos.org
> >> >> Sent: 29 November 2013 14:06
> >> >> To: ros-diffs(a)reactos.org
> >> >> Subject: [ros-diffs] [ekohl] 61145: [FASTFAT]
FsdGetFsVolumeInformation: Return volume creation time.
> >> >>
> >> >> Author: ekohl
> >> >> Date: Fri Nov 29 14:05:43 2013
> >> >> New Revision: 61145
> >> >>
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Ros-dev mailing list
> >> >> Ros-dev(a)reactos.org
> >> >> http://www.reactos.org/mailman/listinfo/ros-dev
> >> >
> >> > --
> >> > Alexander Andrejevic <theflash(a)sdf.lonestar.org>
> >> > SDF Public Access UNIX System - http://sdf.lonestar.org
> >> >
> >> > _______________________________________________
> >> > Ros-dev mailing list
> >> > Ros-dev(a)reactos.org
> >> > http://www.reactos.org/mailman/listinfo/ros-dev
> >>
> >> _______________________________________________
> >> Ros-dev mailing list
> >> Ros-dev(a)reactos.org
> >> http://www.reactos.org/mailman/listinfo/ros-dev
> >
> > --
> > Alexander Andrejevic <theflash(a)sdf.lonestar.org>
> > SDF Public Access UNIX System - http://sdf.lonestar.org
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
--
Alexander Andrejevic <theflash(a)sdf.lonestar.org>
SDF Public Access UNIX System - http://sdf.lonestar.org
------------------------------
Message: 2
Date: Fri, 29 Nov 2013 18:24:23 +0100
From: Pierre Schweitzer <pierre(a)reactos.org>
To: ros-dev(a)reactos.org
Subject: Re: [ros-dev] [ros-diffs] [ekohl] 61145: [FASTFAT]
FsdGetFsVolumeInformation: Return volume creation time.
Message-ID: <5298CDC7.7030300(a)reactos.org>
Content-Type: text/plain; charset="iso-8859-1"
Hi all,
Let's the experts do.
I've contacted the April (French association which mission is to promote
and defend FOSS). They can answer about licensing issues (they propose
it through their contact form).
I'll keep you informed with their answers, highlights, and so on.
Regards,
On 11/29/2013 06:05 PM, Alexander Andrejevic wrote:
> I suppose it depends on how you interpret it.
> To me, "...extend only to the software or derivative works that you create
that run
> on a Microsoft Windows operating system product" sounds like the program
must run
> on Windows exclusively. It's not "... that you create to run ...", but "..
that you
> create that run ...".
>
> Regards,
> Alexander
>
> On Fri, Nov 29, 2013 at 05:55:08PM +0100, David Quintana (gigaherz) wrote:
>> I do not agree on the "unless it's on Microsoft Windows" part. The
>> license grants apply if it is "created to run directly" on windows,
>> which I understand as "it can run anywhere else, also, just as long as
>> it runs in windows without an intermediary".
>>
>> On 29 November 2013 17:51, Alexander Andrejevic
>> <theflash(a)sdf.lonestar.org> wrote:
>>> Fastfat is located inside its own binary, so this is considered "mere
aggregation", and
>>> that is not the problem. (See https://www.gnu.org/licenses/gpl-faq
html#MereAggregation).
>>> The problem is that you don't even have a license to use it or
distribute it, unless it's
>>> on Microsoft Windows.
>>> Then again, I'm not a lawyer either and I could be wrong too. It would
be great if someone
>>> who knows a lot about licenses explained this.
>>>
>>> Regards,
>>> Alexander
>>>
>>> On Fri, Nov 29, 2013 at 05:35:21PM +0100, David Quintana (gigaherz)
wrote:
>>>> The exact words of the license, as seen at
>>>> http://www.ohloh.net/licenses/mslpl (I couldn't find a better link for
>>>> it), are:
>>>>
>>>> "4. (F) Platform Limitation- The licenses granted in sections 2(A) &
>>>> 2(B) extend only to the software or derivative works that you create
>>>> that run on a Microsoft Windows operating system product."
>>>>
>>>> Excluding that term, the rest of the license is mostly a
>>>> differently-worded BSD license. If it only needs to be tested in
>>>> windows to ensure that it works there, then there should be absolutely
>>>> no problem including it in ReactOS, as long as the terms don't
>>>> conflict with the other licenses' terms. And GPL with the ReactOS
>>>> exception, as far as I can tell, allows it. I'm not a lawyer, though,
>>>> so I could be wrong.
>>>>
>>>> On 29 November 2013 16:17, Alexander Andrejevic
>>>> <theflash(a)sdf.lonestar.org> wrote:
>>>>> Hi Ged,
>>>>>
>>>>> Are you sure that we can use software released under the MS-LPL? It
has a rather weird
>>>>> limitation in section 4, which says that you can only use it on a
Microsoft Windows operating system product".
>>>>> Since ReactOS is not Windows, that would mean we can't use it.
>>>>> Please correct me if I'm wrong.
>>>>>
>>>>> Regards,
>>>>> Alexander
>>>>>
>>>>> On Fri, Nov 29, 2013 at 02:58:51PM -0000, Ged Murphy wrote:
>>>>>> Hi Eric,
>>>>>>
>>>>>> I know this has been discussed before, but should we not just bite
the bullet and replace this driver with the Microsoft driver.
>>>>>> The MS_LPL license allows it to be used in reactos, and it would
certainly get rid of any unknowns and give us a reliable filesystem to work
from.
>>>>>>
>>>>>> http://code.msdn.microsoft
com/windowshardware/fastfat-File-System-Driver-135bdf34/view/SourceCode
>>>>>>
>>>>>> Ged.
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos
org] On Behalf Of ekohl(a)svn.reactos.org
>>>>>> Sent: 29 November 2013 14:06
>>>>>> To: ros-diffs(a)reactos.org
>>>>>> Subject: [ros-diffs] [ekohl] 61145: [FASTFAT]
FsdGetFsVolumeInformation: Return volume creation time.
>>>>>>
>>>>>> Author: ekohl
>>>>>> Date: Fri Nov 29 14:05:43 2013
>>>>>> New Revision: 61145
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Ros-dev mailing list
>>>>>> Ros-dev(a)reactos.org
>>>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>>> --
>>>>> Alexander Andrejevic <theflash(a)sdf.lonestar.org>
>>>>> SDF Public Access UNIX System - http://sdf.lonestar.org
>>>>>
>>>>> _______________________________________________
>>>>> Ros-dev mailing list
>>>>> Ros-dev(a)reactos.org
>>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>> _______________________________________________
>>>> Ros-dev mailing list
>>>> Ros-dev(a)reactos.org
>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>> --
>>> Alexander Andrejevic <theflash(a)sdf.lonestar.org>
>>> SDF Public Access UNIX System - http://sdf.lonestar.org
>>>
>>> _______________________________________________
>>> Ros-dev mailing list
>>> Ros-dev(a)reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
--
Pierre Schweitzer <pierre(a)reactos.org>
System Administrator
ReactOS Foundation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4305 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://www.reactos
org/pipermail/ros-dev/attachments/20131129/a8e85e05/attachment-0001.bin>
------------------------------
Message: 3
Date: Fri, 29 Nov 2013 18:55:04 +0100
From: Herm?s B?LUSCA - MA?TO <hermes.belusca(a)sfr.fr>
To: 'ReactOS Development List' <ros-dev(a)reactos.org>
Subject: Re: [ros-dev] [ros-diffs] [ekohl] 61145: [FASTFAT]
FsdGetFsVolumeInformation: Return volume creation time.
Message-ID: <00db01ceed2c$223cffd0$66b6ff70$(a)sfr.fr>
Content-Type: text/plain; charset=iso-8859-1
Nice idea Pierre!
About this license we're talking about: yes I understand as Aleksander: that
you can only use fastfat or derived works from it, on an (authentic) Windows
OS (just my 2 cents, I'm not a lawyer too).
Herm?s.
-----Message d'origine-----
De?: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] De la
part de Pierre Schweitzer
Envoy??: vendredi 29 novembre 2013 18:24
??: ros-dev(a)reactos.org
Objet?: Re: [ros-dev] [ros-diffs] [ekohl] 61145: [FASTFAT]
FsdGetFsVolumeInformation: Return volume creation time.
Hi all,
Let's the experts do.
I've contacted the April (French association which mission is to promote and
defend FOSS). They can answer about licensing issues (they propose it
through their contact form).
I'll keep you informed with their answers, highlights, and so on.
Regards,
On 11/29/2013 06:05 PM, Alexander Andrejevic wrote:
> I suppose it depends on how you interpret it.
> To me, "...extend only to the software or derivative works that you
> create that run on a Microsoft Windows operating system product"
> sounds like the program must run on Windows exclusively. It's not "...
> that you create to run ...", but "... that you create that run ...".
>
> Regards,
> Alexander
>
> On Fri, Nov 29, 2013 at 05:55:08PM +0100, David Quintana (gigaherz) wrote:
>> I do not agree on the "unless it's on Microsoft Windows" part. The
>> license grants apply if it is "created to run directly" on windows,
>> which I understand as "it can run anywhere else, also, just as long
>> as it runs in windows without an intermediary".
>>
>> On 29 November 2013 17:51, Alexander Andrejevic
>> <theflash(a)sdf.lonestar.org> wrote:
>>> Fastfat is located inside its own binary, so this is considered
>>> "mere aggregation", and that is not the problem. (See
https://www.gnu.org/licenses/gpl-faq.html#MereAggregation).
>>> The problem is that you don't even have a license to use it or
>>> distribute it, unless it's on Microsoft Windows.
>>> Then again, I'm not a lawyer either and I could be wrong too. It
>>> would be great if someone who knows a lot about licenses explained this.
>>>
>>> Regards,
>>> Alexander
>>>
>>> On Fri, Nov 29, 2013 at 05:35:21PM +0100, David Quintana (gigaherz)
wrote:
>>>> The exact words of the license, as seen at
>>>> http://www.ohloh.net/licenses/mslpl (I couldn't find a better link
>>>> for it), are:
>>>>
>>>> "4. (F) Platform Limitation- The licenses granted in sections 2(A)
>>>> &
>>>> 2(B) extend only to the software or derivative works that you
>>>> create that run on a Microsoft Windows operating system product."
>>>>
>>>> Excluding that term, the rest of the license is mostly a
>>>> differently-worded BSD license. If it only needs to be tested in
>>>> windows to ensure that it works there, then there should be
>>>> absolutely no problem including it in ReactOS, as long as the terms
>>>> don't conflict with the other licenses' terms. And GPL with the
>>>> ReactOS exception, as far as I can tell, allows it. I'm not a
>>>> lawyer, though, so I could be wrong.
>>>>
>>>> On 29 November 2013 16:17, Alexander Andrejevic
>>>> <theflash(a)sdf.lonestar.org> wrote:
>>>>> Hi Ged,
>>>>>
>>>>> Are you sure that we can use software released under the MS-LPL?
>>>>> It has a rather weird limitation in section 4, which says that you can
only use it on a "Microsoft Windows operating system product".
>>>>> Since ReactOS is not Windows, that would mean we can't use it.
>>>>> Please correct me if I'm wrong.
>>>>>
>>>>> Regards,
>>>>> Alexander
>>>>>
>>>>> On Fri, Nov 29, 2013 at 02:58:51PM -0000, Ged Murphy wrote:
>>>>>> Hi Eric,
>>>>>>
>>>>>> I know this has been discussed before, but should we not just bite
the bullet and replace this driver with the Microsoft driver.
>>>>>> The MS_LPL license allows it to be used in reactos, and it would
certainly get rid of any unknowns and give us a reliable filesystem to work
from.
>>>>>>
>>>>>> http://code.msdn.microsoft.com/windowshardware/fastfat-File-Syste
>>>>>> m-Driver-135bdf34/view/SourceCode
>>>>>>
>>>>>> Ged.
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: ros-diffs-bounces(a)reactos.org
>>>>>> [mailto:ros-diffs-bounces@reactos.org] On Behalf Of
>>>>>> ekohl(a)svn.reactos.org
>>>>>> Sent: 29 November 2013 14:06
>>>>>> To: ros-diffs(a)reactos.org
>>>>>> Subject: [ros-diffs] [ekohl] 61145: [FASTFAT]
FsdGetFsVolumeInformation: Return volume creation time.
>>>>>>
>>>>>> Author: ekohl
>>>>>> Date: Fri Nov 29 14:05:43 2013
>>>>>> New Revision: 61145
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Ros-dev mailing list
>>>>>> Ros-dev(a)reactos.org
>>>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>>> --
>>>>> Alexander Andrejevic <theflash(a)sdf.lonestar.org> SDF Public Access
>>>>> UNIX System - http://sdf.lonestar.org
>>>>>
>>>>> _______________________________________________
>>>>> Ros-dev mailing list
>>>>> Ros-dev(a)reactos.org
>>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>> _______________________________________________
>>>> Ros-dev mailing list
>>>> Ros-dev(a)reactos.org
>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>> --
>>> Alexander Andrejevic <theflash(a)sdf.lonestar.org> SDF Public Access
>>> UNIX System - http://sdf.lonestar.org
>>>
>>> _______________________________________________
>>> Ros-dev mailing list
>>> Ros-dev(a)reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
--
Pierre Schweitzer <pierre(a)reactos.org>
System Administrator
ReactOS Foundation
------------------------------
Message: 4
Date: Fri, 29 Nov 2013 23:31:03 +0400
From: Aleksey Bragin <aleksey(a)reactos.org>
To: ReactOS Development List <ros-dev(a)reactos.org>
Subject: Re: [ros-dev] [ros-diffs] [ekohl] 61145: [FASTFAT]
FsdGetFsVolumeInformation: Return volume creation time.
Message-ID: <5298EB77.7040509(a)reactos.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
To give you my position:
1. Current FAT driver in ReactOS needs to die away. I am testing all my
new code with the MS's FASTFAT driver.
2. Lawyers advice is needed whether we can distribute it.
Regards,
Aleksey Bragin
On 29.11.2013 21:55, Herm?s B?LUSCA - MA?TO wrote:
> Nice idea Pierre!
>
> About this license we're talking about: yes I understand as Aleksander:
that
> you can only use fastfat or derived works from it, on an (authentic)
Windows
> OS (just my 2 cents, I'm not a lawyer too).
>
> Herm?s.
>
> -----Message d'origine-----
> De : ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] De
la
> part de Pierre Schweitzer
> Envoy? : vendredi 29 novembre 2013 18:24
> ? : ros-dev(a)reactos.org
> Objet : Re: [ros-dev] [ros-diffs] [ekohl] 61145: [FASTFAT]
> FsdGetFsVolumeInformation: Return volume creation time.
>
> Hi all,
>
> Let's the experts do.
>
> I've contacted the April (French association which mission is to promote
and
> defend FOSS). They can answer about licensing issues (they propose it
> through their contact form).
>
> I'll keep you informed with their answers, highlights, and so on.
>
> Regards,
>
> On 11/29/2013 06:05 PM, Alexander Andrejevic wrote:
>> I suppose it depends on how you interpret it.
>> To me, "...extend only to the software or derivative works that you
>> create that run on a Microsoft Windows operating system product"
>> sounds like the program must run on Windows exclusively. It's not "...
>> that you create to run ...", but "... that you create that run ...".
>>
>> Regards,
>> Alexander
>>
>> On Fri, Nov 29, 2013 at 05:55:08PM +0100, David Quintana (gigaherz)
wrote:
>>> I do not agree on the "unless it's on Microsoft Windows" part. The
>>> license grants apply if it is "created to run directly" on windows,
>>> which I understand as "it can run anywhere else, also, just as long
>>> as it runs in windows without an intermediary".
>>>
>>> On 29 November 2013 17:51, Alexander Andrejevic
>>> <theflash(a)sdf.lonestar.org> wrote:
>>>> Fastfat is located inside its own binary, so this is considered
>>>> "mere aggregation", and that is not the problem. (See
> https://www.gnu.org/licenses/gpl-faq.html#MereAggregation).
>>>> The problem is that you don't even have a license to use it or
>>>> distribute it, unless it's on Microsoft Windows.
>>>> Then again, I'm not a lawyer either and I could be wrong too. It
>>>> would be great if someone who knows a lot about licenses explained this
>>>>
>>>> Regards,
>>>> Alexander
>>>>
>>>> On Fri, Nov 29, 2013 at 05:35:21PM +0100, David Quintana (gigaherz)
> wrote:
>>>>> The exact words of the license, as seen at
>>>>> http://www.ohloh.net/licenses/mslpl (I couldn't find a better link
>>>>> for it), are:
>>>>>
>>>>> "4. (F) Platform Limitation- The licenses granted in sections 2(A)
>>>>> &
>>>>> 2(B) extend only to the software or derivative works that you
>>>>> create that run on a Microsoft Windows operating system product."
>>>>>
>>>>> Excluding that term, the rest of the license is mostly a
>>>>> differently-worded BSD license. If it only needs to be tested in
>>>>> windows to ensure that it works there, then there should be
>>>>> absolutely no problem including it in ReactOS, as long as the terms
>>>>> don't conflict with the other licenses' terms. And GPL with the
>>>>> ReactOS exception, as far as I can tell, allows it. I'm not a
>>>>> lawyer, though, so I could be wrong.
>>>>>
>>>>> On 29 November 2013 16:17, Alexander Andrejevic
>>>>> <theflash(a)sdf.lonestar.org> wrote:
>>>>>> Hi Ged,
>>>>>>
>>>>>> Are you sure that we can use software released under the MS-LPL?
>>>>>> It has a rather weird limitation in section 4, which says that you
can
> only use it on a "Microsoft Windows operating system product".
>>>>>> Since ReactOS is not Windows, that would mean we can't use it.
>>>>>> Please correct me if I'm wrong.
>>>>>>
>>>>>> Regards,
>>>>>> Alexander
>>>>>>
>>>>>> On Fri, Nov 29, 2013 at 02:58:51PM -0000, Ged Murphy wrote:
>>>>>>> Hi Eric,
>>>>>>>
>>>>>>> I know this has been discussed before, but should we not just bite
> the bullet and replace this driver with the Microsoft driver.
>>>>>>> The MS_LPL license allows it to be used in reactos, and it would
> certainly get rid of any unknowns and give us a reliable filesystem to
work
> from.
>>>>>>> http://code.msdn.microsoft.com/windowshardware/fastfat-File-Syste
>>>>>>> m-Driver-135bdf34/view/SourceCode
>>>>>>>
>>>>>>> Ged.
>>>>>>>
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: ros-diffs-bounces(a)reactos.org
>>>>>>> [mailto:ros-diffs-bounces@reactos.org] On Behalf Of
>>>>>>> ekohl(a)svn.reactos.org
>>>>>>> Sent: 29 November 2013 14:06
>>>>>>> To: ros-diffs(a)reactos.org
>>>>>>> Subject: [ros-diffs] [ekohl] 61145: [FASTFAT]
> FsdGetFsVolumeInformation: Return volume creation time.
>>>>>>> Author: ekohl
>>>>>>> Date: Fri Nov 29 14:05:43 2013
>>>>>>> New Revision: 61145
>>>>>>>
>>>>>>>
>>>>>>>
------------------------------
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
End of Ros-dev Digest, Vol 111, Issue 24
****************************************
Hi all,
Apart from the critical servers hosted in Germany, we can operate our
own network in Sweden by courtesy of Jan Blomqvist-Kinander.
Today, the infrastructure team has set up a new switch there, which is
meant to increase the network performance, allow a better intrusion
detection and offer more ports.
Most of our machines could be successfully moved to that switch, except
for Fezile. Due to unexpected networking problems, this machine became
unavailable even for us and needs to be rebooted manually. It's also one
of our older servers without an IPMI module, so we can't remotely reboot it.
The server outage affects the following services:
* iso.reactos.org
* doxygen.reactos.org
* cppcheck.reactos.org
* VMware Player Test slave
I'm very sorry for the additional downtime this has caused.
Once the server is up again, we'll do our best to prevent this from
happening again. Take my word that I'll write a report for the website
about the recent infrastructure changes, so you can get an idea of our
additional resources :)
With best regards,
Colin
Hi all,
In the process of improving the performance of our infrastructure, we
will upgrade the first of two servers this Saturday.
This will result in a downtime for the following services:
* SVN
* Mail and mailing lists
* BuildBot
* Testman
* GIT mirror
* File server at svn.reactos.org
* Compatibility Database
* ev.reactos.org
* Second nameserver
* RosKGB bot
The upgrade will in particular increase CPU performance as well as RAM
and HDD sizes, so we will have more resources available afterwards.
Our current server has served us well since 2009, so don't expect such
an upgrade to happen again in the next few years.
We're aware that this affects many core services, so we will do our best
to keep the downtime as low as possible. Our target is <12h.
Gladly, we have already done such an upgrade in the past, so it mainly
boils down to the speed of transferring files over the network.
Meanwhile, we apologize for the caused inconveniences.
With best regards and on behalf of the whole infrastructure team,
Colin Finck
Hey guys,
website seems to have some bigger problems with mySQL connection overload.
SQL ERROR [ mysqli ]
Too many connections [1040]
An sql error occurred while fetching this page. Please contact an administrator if this problem persists.
-------------------
PDOException: SQLSTATE[08004] [1040] Too many connections in lock_may_be_available() (line 167 of /srv/www/www.reactos.org/drupal/includes/lock.inc).
So administrator, I think this counts a s contacting you ^^
Greetings
Daniel "EmuandCo" Reimer
What exactly will be upgraded (table: model -> new_model)?
Pozdrawiam,
Adam "Saibamen" Stachowicz
Administrator it-maniak.pl
2013/11/21 <ros-dev-request(a)reactos.org>
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
> 1. Server downtime on Saturday (Colin Finck)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 21 Nov 2013 11:08:46 +0100
> From: Colin Finck <colin(a)reactos.org>
> To: ros-general(a)reactos.org, ReactOS Development List
> <ros-dev(a)reactos.org>
> Subject: [ros-dev] Server downtime on Saturday
> Message-ID: <528DDBAE.9070804(a)reactos.org>
> Content-Type: text/plain; charset=ISO-8859-15
>
> Hi all,
>
> In the process of improving the performance of our infrastructure, we
> will upgrade the first of two servers this Saturday.
> This will result in a downtime for the following services:
>
> * SVN
> * Mail and mailing lists
> * BuildBot
> * Testman
> * GIT mirror
> * File server at svn.reactos.org
> * Compatibility Database
> * ev.reactos.org
> * Second nameserver
> * RosKGB bot
>
> The upgrade will in particular increase CPU performance as well as RAM
> and HDD sizes, so we will have more resources available afterwards.
> Our current server has served us well since 2009, so don't expect such
> an upgrade to happen again in the next few years.
>
> We're aware that this affects many core services, so we will do our best
> to keep the downtime as low as possible. Our target is <12h.
> Gladly, we have already done such an upgrade in the past, so it mainly
> boils down to the speed of transferring files over the network.
> Meanwhile, we apologize for the caused inconveniences.
>
> With best regards and on behalf of the whole infrastructure team,
>
> Colin Finck
>
>
>
> ------------------------------
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> End of Ros-dev Digest, Vol 111, Issue 16
> ****************************************
>
Hi,
These failures were due to work on the local network. They should be
fixed by now and ISOs uploaded.
If you catch a missing ISO, please re-issue a build.
Sorry for the caused inconvenience.
With my best regards,
On 11/18/2013 04:36 PM, buildbot(a)reactos.org wrote:
> The Buildbot has detected a failed build on builder Trunk_x86_GCCLin Debug while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/Trunk_x86_GCCLin%20Debug/builds/4713
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Linux_AMD64_1
>
> Build Reason: scheduler
> Build Source Stamp: 61039
> Blamelist: tkreuzer
>
> BUILD FAILED: failed shell
>
> sincerely,
> -The Buildbot
>
>
>
>
--
Pierre Schweitzer <pierre(a)reactos.org>
System Administrator
ReactOS Foundation
Hi all,
This is an acknowledgment and informative email.
Since we migrated the ReactOS website to Drupal, you all have spotted
critical performances issues. We did our best to address most of them in
the following days to ensure smooth browsing on the website.
Unfortunately we could not fix them all.
Even worse, nowadays, ReactOS website faces a kind of "shutdown"
everyday (approximately between 2:45 AM CET and 4:45 AM CET). This is a
really long and critical downtime that affects mainly US users due to
timezones.
Be sure we are aware about it.
Unfortunately, this is not something we can fix from a day to the
following. This is due to our backup policies that completely lock the
MySQL server to ensure consistent backups.
We are currently working on getting this fixed as fast as possible. But
this will require (besides the rest) a two hardware upgrades on our
infrastructure.
Indeed, Drupal stresses our infrastructure much more than old RosCMS.
And we have to fully rethink our web infrastructure and redistribute it,
which we cannot do at the moment due to hardware constraints. Upgrading
our hardware will be in our first steps (obviously, expect downtimes at
that moment). Then, we will finally be able to replicate our MySQL
server to perform load-balancing and prevent shutdowns on backup.
We, the sysadmins team and the website team, agreed on a plan about how
to enhance and strengthen the infrastructure, and thus fix all the
issues we are currently facing. This will take some time, but we are
working together to get ReactOS website back into a decent shape.
Be assured that we are doing our best to make your place nice.
Meanwhile, please forgive us the caused inconvenience.
With my best regards, on behalf of the guys working behind the scene,
--
Pierre Schweitzer<pierre at reactos.org>
System Administrator
ReactOS Foundation
Hi.
This should be removed, we are not wine and I personally work "hard on"
getting wine todos fixed in ReactOS! This also breaks the DCE test.
Background, GvG and then the old guard back in the day thought the same way
as I do about this issue. We should count the todo's as failures and not
bypass these failues. Why? It may point to a critical bug that could break
functionality somewhere else. That was the reasoning then and I agree with
it. Cheating the tests is just plain cheating......
James
Hi James,
What do you have in mind when you write CORE-???? ?
Is it something related to http://jira.reactos.org/browse/CORE-7469 ?
Cheers,
Hermès
----------------------------------------------------------------------------
--------------------------
Author: jimtabor
Date: Wed Nov 13 17:21:41 2013
New Revision: 60974
URL: http://svn.reactos.org/svn/reactos?rev=60974&view=rev
Log:
- Wine had some fixups added since this was last synced. CORE-???? &
CORE-7574.
Modified:
trunk/rostests/winetests/user32/sysparams.c