Ros-dev

ros-dev@reactos.org

5790 discussions

by Victor Perevertkin

Hello! It seems for me that it's time to bring up the topic about our RC version - 0.4.14. Our current "stable", 0.4.13 was branched on 30 September, 2019 (remember those peacefull pre-COVID times :D) That's quite some time, but not the main issue I'd like to discuss. 0.4.14 was branched on 24 April, 2020. That's almost a year already. And we're in a difficult situation here - there are regressions, but nobody fixed them within this long time. According to https://reactos.org/wiki/Tests_for_0.4.14, there are 29 unfixed regressions found for this release. I'd like to point out: most of them are among usermode and non-kernel/driver functionality, and as our development is mostly focused in the kernel right now, it's unexpected for them to be fixed unless a volunteer comes up. A quick reminder. Our "releases" mechanism is useful for finding regressions in the first place, there is no that much benefit for users here, because we're still a "deep" alpha. Correct me if I'm wrong. Joakim made a great job finding all regressions, and this work won't be lost in any case. We can't wait forever and I think it's time to resolve this situation somehow. I see two options: 1. Release 0.4.14 as-is. There were a lot more buggy releases, nobody dies from this. 2. Skip 0.4.14. This already happened once in the history of the project - 0.3.2 was skipped. I wasn't around at the time, but I may guess that reasons were similar to what we have today. (3.) Fix the bugs quickly. I don't expect this to happen, but who knows, maybe a volunteer appears :) Let's vote. This seem to be the only way for us to decide on things. Votes from the team members will be collected until 1 March. === I personally vote for skipping the release. The work on finding regressions is already done, so the most important part of a release cycle for us is there (thanks Joakim!) If we do a release now, all the stuff we were writing in news reports for the last 6 month would be missing from it. That would cause (as I think) a lot of confusion to people. Moreover 0.4.14 is not that featureful release itself (compared to 0.4.13, which brought the new USB stack) So I suggest to move on and start checking 0.4.15 for regressions. I expect quite some of them to appear and we need time for fixing. Cheers, Victor

4 years, 8 months

The situation with version 0.4.14

by Олег Дубінський

4 years, 8 months

Re: [ros-dev] The situation with version 0.4.14

by Robert Naumann

Hey Tom, USB-Boot works with current nightlies and GPT is in the Works AFAIK(Hermes should know more details). Best Regards Robert Thomas Mueller <mueller6723(a)twc.com> schrieb am Mi., 10. Feb. 2021, 11:01: > from Colin Finck: > > > This is not the kind of participation that has any place on the mailing > list > > of an open-source project. > > Unsubscribed and blocked that person. > > > Colin > > > > Am 09.02.2021 um 17:26 schrieb Dick: > > > > Hi, > > > as a potential user this project makes me extremely tired. in 2000 or > > > something like that i was excited because afvree windows replacement > > > would be there...... it is 221!!! years later and there is...... still > > > nothing, jst deep alpha as stated in last email. and 0.14 woudl have > even > > > regressions for 0.4.13. wouldnt it be more smart to finally build a > > > timeline for this all? or to discuss the fact if this project makes any > > > sense yet, it seems just a waste of time this way. > > First of all, I sent the wrong message a couple times, to ros-general. > Now for the intended message: > > I have been idle with ReactOS because of no place to put it, and ReactOS's > inability to boot from a USB stick. > > I can't install ReactOS on hard drive because of lack of GPT. > > I would need to be able to use ROSBE and write the result to a USB stick > to boot, but don't think that is workable. > > Tom > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://reactos.org/mailman/listinfo/ros-dev >

4 years, 8 months

Mail server maintenance on Thursday, 4th February

by Colin Finck

Hi all! Our IServ system used for mail and mailinglists will be down for maintenance on THURSDAY, 4TH FEBRUARY 2021 15:00 ~ 17:00 UTC During this time, you won't be able to send or receive any mails using your @reactos.org address. Mail that is sent to an @reactos.org address will usually be delivered later. Other services won't be affected by this migration. In particular, all means of communication through Mattermost or the website/forums will stay live. Best regards, Colin Finck

4 years, 8 months

FOSDEM 2021 preparation

by Victor Perevertkin

Hello everyone! We've got accepted to FOSDEM 2021, which (as you may already know) will be going online. FOSDEM provides a place on their stands website, we need to prepare a page for that. There is also a place for videos in case we want to share some :) Their website uses Hugo and is available on Github (https://github.com/FOSDEM/stands-website) The documentation is provided here: https://github.com/FOSDEM/stands-website/blob/master/README.md Let's discuss what should we present there, there is not that much time left! The conference is held on 6-7 February Cheers, Victor

4 years, 9 months

Re: [ros-dev] Status Meeting (November 2020)

by Hermès BÉLUSCA-MAÏTO

What about that discussion about why we have ditched out MSVC 2010 support (starting to depend on that fact, and thus, breaking any possibility of self-hosting ROS building on ROS using MSVC compiler (without the IDE), since later versions of MSVC only work on Vista+, and as an indirect consequence, too, opening the can of worms, that is, being able to "pollute", involuntarily or not, the ReactOS core code (kernel + drivers) with C99+ non-standard portable code -- ), and without having first warned heavily through all the mailing lists etc. , thus allowing the developers to voice their concerns publicly in the MLs ? This was done around in mattermost only, after we decided for some reason that we wouldn't need the VC2010 buildbots anymore. Hermes. -----Original Message----- From: Ros-dev <ros-dev-bounces(a)reactos.org> On Behalf Of Colin Finck Sent: Sun Nov 15 17:24:22 UTC 2020 To: ReactOS Development List <ros-dev(a)reactos.org> Subject: [ros-dev] Status Meeting (November 2020) Hi all, With several people asking for a status meeting, let's have another one before the year is over. Let me invite you to the meeting on Thursday, 26th November 2020 19:00 UTC Mattermost private channel "Meeting" So far, there is only one point on the agenda: * Achievements and Future Outlook (everyone) What have you been working on and what are your plans? Please submit further agenda proposals by answering to this mail. Looking forward to see you! Colin

4 years, 9 months

Status Meeting (November 2020)

by Joachim Henze

I wanted to add, that vgal and Doug Lyons were also favoring continued VS2010 support, as we can see clearly in the PRs discussion https://github.com/reactos/reactos/pull/2658 Please do count also those contributors voices. Some more regarding some brought up arguments: >>"BTRFS and its sync will benefit from the drop": I see a working BTRFS in 0.4.14RC60, which has VS2010 support. And I see a totally broken BTRFS that does not even boot at all any longer in master head 0.4.15-dev-1605-gab45955. A fact. >>"We should replace all proven compilers with superior Clang" I have not seen a ros yet, that would even boot at all with Clang. Also according to discussions they do still lack SEH 32bit support. And even if they would develop that one day, how big will the resulting ros isos be then? And that still would not solve the compat to older build platforms 2k3sp2/XPSP3 and ros. Wishful thinking just. >>"We need the drop for the new standard library." And where is that library? No one did ever integrate that into ros, although the compilers drop has been rushed into master months ago already. As Hermes said already: I see no gain, but I do see a lot of pain and unfinished WIP+wishful thinking.

4 years, 9 months

Sad news

by Javier Agustìn Fernàndez Arroyo

Hello guys, I have just read at Facebook that Andrew Greenwood's father (andrew's nick is *silverblade* at ReactOS) passed away last night due to CoVid19.

4 years, 9 months

FOSDEM online

by Mark Jansen

Hello, This year FOSDEM is going to be an online event: https://fosdem.org/2021/news/2020-12-11-stands-cfp/ Are there volunteers for an online ReactOS stand? We would need some short video's for introduction and demonstration purposes, as well as some people active in a chat room answering questions. Regards, Mark

4 years, 9 months

Re: [ros-dev] [ros-diffs] [reactos] 01/01: Implement IRP_MN_QUERY_DEVICE_TEXT.DeviceTextLocationInformation

by jerome.gardou＠reactos.org

Eric, Can we please refrain from using sprintf, strlen and the like in kernel-mode drivers ? Expecially on buffers which are obviously too small for their purpose ? Please use functions from ntstrsafe.h and work directly on W-buffers, thanks. Thanks Jérôme Le dimanche 6 décembre 2020, 12:45:55 CET Eric Kohl a écrit : > https://git.reactos.org/?p=reactos.git;a=commitdiff;h=cac7b003c04c1f42f45221 > 56c2d2f77996b271c2 > > commit cac7b003c04c1f42f4522156c2d2f77996b271c2 > Author: Eric Kohl <eric.kohl(a)reactos.org> > AuthorDate: Sun Dec 6 12:42:50 2020 +0100 > Commit: Eric Kohl <eric.kohl(a)reactos.org> > CommitDate: Sun Dec 6 12:42:50 2020 +0100 > > Implement IRP_MN_QUERY_DEVICE_TEXT.DeviceTextLocationInformation > --- > drivers/storage/port/scsiport/pdo.c | 34 +++++++++++++++++++++++++++++++--- > 1 file changed, 31 insertions(+), 3 deletions(-) > > diff --git a/drivers/storage/port/scsiport/pdo.c > b/drivers/storage/port/scsiport/pdo.c index 182f2b029ec..5ddbd7e2b34 100644 > --- a/drivers/storage/port/scsiport/pdo.c > +++ b/drivers/storage/port/scsiport/pdo.c > @@ -185,10 +185,12 @@ PdoHandleQueryDeviceText( > PIO_STACK_LOCATION IoStack; > UINT32 Offset = 0; > PINQUIRYDATA InquiryData; > - CHAR LocalBuffer[sizeof(InquiryData->VendorId) + > sizeof(InquiryData->ProductId) + 2]; + CHAR LocalBuffer[40]; > ANSI_STRING AnsiString; > UNICODE_STRING DeviceDescription; > > + DPRINT("PdoHandleQueryDeviceText\n"); > + > IoStack = IoGetCurrentIrpStackLocation(Irp); > > InquiryData = &DeviceExtension->InquiryData; > @@ -196,9 +198,8 @@ PdoHandleQueryDeviceText( > switch (IoStack->Parameters.QueryDeviceText.DeviceTextType) > { > case DeviceTextDescription: > - case DeviceTextLocationInformation: > { > - DPRINT("PdoHandleQueryDeviceText\n"); > + DPRINT("DeviceTextDescription\n"); > > Offset += CopyFieldTruncate(InquiryData->VendorId, > &LocalBuffer[Offset], > @@ -227,6 +228,33 @@ PdoHandleQueryDeviceText( > Irp->IoStatus.Information = > (ULONG_PTR)DeviceDescription.Buffer; return STATUS_SUCCESS; > } > + > + case DeviceTextLocationInformation: > + { > + DPRINT("DeviceTextLocationInformation\n"); > + > + sprintf(LocalBuffer, "Bus Number %d, Target ID %d, LUN %d", > + DeviceExtension->PathId, DeviceExtension->TargetId, > DeviceExtension->Lun); + > + RtlInitAnsiString(&AnsiString, (PCSZ)&LocalBuffer); > + > + DeviceDescription.Length = 0; > + DeviceDescription.MaximumLength = (USHORT)((strlen(LocalBuffer) > + 1) * sizeof(WCHAR)); + DeviceDescription.Buffer = > ExAllocatePoolWithTag(PagedPool, + > DeviceDescription.MaximumLength, + > TAG_SCSIPORT); + if > (!DeviceDescription.Buffer) > + { > + Irp->IoStatus.Information = 0; > + return STATUS_INSUFFICIENT_RESOURCES; > + } > + > + RtlAnsiStringToUnicodeString(&DeviceDescription, &AnsiString, > FALSE); + > + Irp->IoStatus.Information = > (ULONG_PTR)DeviceDescription.Buffer; + return STATUS_SUCCESS; > + } > + > default: > { > Irp->IoStatus.Information = 0;

4 years, 10 months

← Newer
1
2
3
4
5
6
7
...
579
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev