Re: [ros-dev] Setup on an extended partition
Am 05.04.2015 um 10:36 schrieb Minas Abrahamyan: 2 This feature is extreamely useful for any Windows user-- especially for ones with busy all primary partitions: 2 backup partitions, one C: and one just anything other, Linux or OsX - and you very need extended partition to keep Reactos 3 This feature is extreamely needed for just any real-life (==real hardware) Reactos tester and developer: see p.2 Plus starting from extended partition will allow to have multiple copies of reactos installations, which is bread and water for testers. The fact this feature is absent just shows where real-life usage by testers of Ros is: just nowhere. I implemented this functionallity, so the installer can now create one or more logical partitions and can also install it there. There are two issues though: 1. When multiple logical drives exist and they are deleted the installer crashes. This is IMO just a minor problem, because you can still install, yu just have to think ahead of what you want. I will look into this later. 2. This is IMO the more important issue. I verified with a GParted ISO the partitions and they are corrupted. At first I thought I did something wrong, but after working on this for several weeks now I'm not so convinced anymore. When I dump the partition table with my code, it looks exactly as the dump that it would generate when I create the same layout with gparted, so it should work. So my assumption is that the implementation in NtDeviceIoControlFile(IOCTL_DISK_SET_DRIVE_LAYOUT) may be the cause. On the other hand, when I create only primary partitions (which the existing code can do) then gparted doesn't report any errors, so it may only be the case when dealing with logical partitions. The question is now, should I upload the current code as a patch as it is right now, with these known issues, or should I try to fix it completely before I upload it? If I should upload it, I wonder how long it usually takes until it is commited to the repository, because I submitted a patch in this areay a month ago, which still has not made it to SVN. Or when/how do you get write access to SVN? ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Re: [ros-dev] Status Meeting (April 2015)
Hi, The credentials just have been sent and the server started. As a reminder, the server is running on fezile.reactos.org:6667, channel #meeting. No SSL (yet). In case you didn't have your credentials, you cannot attend the meeting (private). Contact me if anything wrong. The meeting will start in less than 1 hour. With my best regards, On 28/04/2015 00:27, Aleksey Bragin wrote: Hello, Let me invite you to the monthly status meeting taking place 30th of April, 19:00 UTC, as always. 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. Please send agenda proposals to me before the meeting, so that we can start with a proposed agenda. And join Mumble! Regards, Aleksey Bragin ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev -- Pierre Schweitzer pierre at reactos.org System Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. smime.p7s Description: S/MIME Cryptographic Signature ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Re: [ros-dev] Setup on an extended partition
Upload the patch to JIRA, create a new issue entry if none exists for this. It's the preferred way to contribute to the project. People only get write access after they have proved themselves with writing patches, and the team trusts them to have some minimal quality and behaviour standards. ;P We have few knowledgeable developers so the process sometimes takes a bit of time. If we missed a patch, feel free to join IRC and slap some of us there. On 30 April 2015 at 19:51, stack exchange sparh...@gmx.at wrote: Am 05.04.2015 um 10:36 schrieb Minas Abrahamyan: 2 This feature is extreamely useful for any Windows user-- especially for ones with busy all primary partitions: 2 backup partitions, one C: and one just anything other, Linux or OsX - and you very need extended partition to keep Reactos 3 This feature is extreamely needed for just any real-life (==real hardware) Reactos tester and developer: see p.2 Plus starting from extended partition will allow to have multiple copies of reactos installations, which is bread and water for testers. The fact this feature is absent just shows where real-life usage by testers of Ros is: just nowhere. I implemented this functionallity, so the installer can now create one or more logical partitions and can also install it there. There are two issues though: 1. When multiple logical drives exist and they are deleted the installer crashes. This is IMO just a minor problem, because you can still install, yu just have to think ahead of what you want. I will look into this later. 2. This is IMO the more important issue. I verified with a GParted ISO the partitions and they are corrupted. At first I thought I did something wrong, but after working on this for several weeks now I'm not so convinced anymore. When I dump the partition table with my code, it looks exactly as the dump that it would generate when I create the same layout with gparted, so it should work. So my assumption is that the implementation in NtDeviceIoControlFile(IOCTL_DISK_SET_DRIVE_LAYOUT) may be the cause. On the other hand, when I create only primary partitions (which the existing code can do) then gparted doesn't report any errors, so it may only be the case when dealing with logical partitions. The question is now, should I upload the current code as a patch as it is right now, with these known issues, or should I try to fix it completely before I upload it? If I should upload it, I wonder how long it usually takes until it is commited to the repository, because I submitted a patch in this areay a month ago, which still has not made it to SVN. Or when/how do you get write access to SVN? ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
