Ros-dev

ros-dev@reactos.org

5790 discussions

Re: [ros-dev] [ros-diffs] [cfinck] 75586: - Add 0x96 as ISO9660 partition type to ntdddisk.h (from https://en.wikipedia.org/wiki/Partition_type) and detect it using IsRecognizedPartition. - Make our isohybrid create an MBR ...
by Alex Ionescu 21 Aug '17

21 Aug '17

This is cool work but you do realize that adding non-Windows partition types and changing Windows headers (and Windows macros) to work with them, as well as forking our CDFS from the Windows CDFS... doesn't really help compatibility move forward... It would be nice to discuss about how these changes can be done to keep our 'special' USB livecd boot and CDFS changes, without twisting the system away from its NT roots. My suggestion would be a filter driver on top of CDFS, and a re-definition of this macro to be used by the filter (or whatever code relies on it). This sounds like it would give you the best of both worlds... Best regards, Alex Ionescu On Thu, Aug 17, 2017 at 1:03 PM, <cfinck(a)svn.reactos.org> wrote: > Author: cfinck > Date: Thu Aug 17 11:03:40 2017 > New Revision: 75586 > > URL: http://svn.reactos.org/svn/reactos?rev=75586&view=rev > Log: > - Add 0x96 as ISO9660 partition type to ntdddisk.h (from > https://en.wikipedia.org/wiki/Partition_type) and detect it using > IsRecognizedPartition. > - Make our isohybrid create an MBR with partition type 0x96. > > This properly assigns a drive letter to the Live-CD and lets me boot into > desktop using "qemu -hda livecd.iso". > Fixes CORE-13184 > > Modified: > trunk/reactos/boot/CMakeLists.txt > trunk/reactos/sdk/include/psdk/ntdddisk.h > > Modified: trunk/reactos/boot/CMakeLists.txt > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/ > CMakeLists.txt?rev=75586&r1=75585&r2=75586&view=diff > ============================================================ > ================== > --- trunk/reactos/boot/CMakeLists.txt [iso-8859-1] (original) > +++ trunk/reactos/boot/CMakeLists.txt [iso-8859-1] Thu Aug 17 11:03:40 > 2017 > @@ -68,7 +68,7 @@ > -eltorito-boot loader/isoboot.bin -no-emul-boot -boot-load-size 4 > -eltorito-alt-boot -eltorito-platform efi -eltorito-boot loader/efisys.bin > -no-emul-boot -hide boot.catalog > -sort ${CMAKE_CURRENT_BINARY_DIR}/bootfiles.sort > -no-cache-inodes -graft-points -path-list > ${CMAKE_CURRENT_BINARY_DIR}/bootcd.lst > - COMMAND native-isohybrid -b ${_isombr_file} > ${REACTOS_BINARY_DIR}/bootcd.iso > + COMMAND native-isohybrid -b ${_isombr_file} -t 0x96 > ${REACTOS_BINARY_DIR}/bootcd.iso > DEPENDS isombr native-isohybrid native-mkisofs > VERBATIM) > > @@ -83,7 +83,7 @@ > -eltorito-boot loader/isobtrt.bin -no-emul-boot -boot-load-size 4 > -eltorito-alt-boot -eltorito-platform efi -eltorito-boot loader/efisys.bin > -no-emul-boot -hide boot.catalog > -sort ${CMAKE_CURRENT_BINARY_DIR}/bootfiles.sort > -no-cache-inodes -graft-points -path-list > ${CMAKE_CURRENT_BINARY_DIR}/bootcdregtest.lst > - COMMAND native-isohybrid -b ${_isombr_file} ${REACTOS_BINARY_DIR}/ > bootcdregtest.iso > + COMMAND native-isohybrid -b ${_isombr_file} -t 0x96 > ${REACTOS_BINARY_DIR}/bootcdregtest.iso > DEPENDS isombr native-isohybrid native-mkisofs > VERBATIM) > > @@ -126,7 +126,7 @@ > -eltorito-boot loader/isoboot.bin -no-emul-boot -boot-load-size 4 > -eltorito-alt-boot -eltorito-platform efi -eltorito-boot loader/efisys.bin > -no-emul-boot -hide boot.catalog > -sort ${CMAKE_CURRENT_BINARY_DIR}/bootfiles.sort > -no-cache-inodes -graft-points -path-list > ${CMAKE_CURRENT_BINARY_DIR}/livecd.lst > - COMMAND native-isohybrid -b ${_isombr_file} > ${REACTOS_BINARY_DIR}/livecd.iso > + COMMAND native-isohybrid -b ${_isombr_file} -t 0x96 > ${REACTOS_BINARY_DIR}/livecd.iso > DEPENDS isombr native-isohybrid native-mkisofs > VERBATIM) > > @@ -169,7 +169,7 @@ > -eltorito-boot loader/isoboot.bin -no-emul-boot -boot-load-size 4 > -eltorito-alt-boot -eltorito-platform efi -eltorito-boot loader/efisys.bin > -no-emul-boot -hide boot.catalog > -sort ${CMAKE_CURRENT_BINARY_DIR}/bootfiles.sort > -duplicates-once -no-cache-inodes -graft-points -path-list > ${CMAKE_CURRENT_BINARY_DIR}/hybridcd.lst > - COMMAND native-isohybrid -b ${_isombr_file} ${REACTOS_BINARY_DIR}/ > hybridcd.iso > + COMMAND native-isohybrid -b ${_isombr_file} -t 0x96 > ${REACTOS_BINARY_DIR}/hybridcd.iso > DEPENDS bootcd livecd > VERBATIM) > > > Modified: trunk/reactos/sdk/include/psdk/ntdddisk.h > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/sdk/ > include/psdk/ntdddisk.h?rev=75586&r1=75585&r2=75586&view=diff > ============================================================ > ================== > --- trunk/reactos/sdk/include/psdk/ntdddisk.h [iso-8859-1] (original) > +++ trunk/reactos/sdk/include/psdk/ntdddisk.h [iso-8859-1] Thu Aug 17 > 11:03:40 2017 > @@ -223,6 +223,7 @@ > #ifdef __REACTOS__ > #define PARTITION_OLD_LINUX 0x43 > #define PARTITION_LINUX 0x83 > +#define PARTITION_ISO9660 0x96 > #define PARTITION_FREEBSD 0xA5 > #define PARTITION_OPENBSD 0xA6 > #define PARTITION_NETBSD 0xA9 > @@ -253,6 +254,7 @@ > ((PartitionType) == PARTITION_XINT13) || \ > ((PartitionType) == PARTITION_LINUX) || \ > ((PartitionType) == PARTITION_OLD_LINUX) || \ > + ((PartitionType) == PARTITION_ISO9660) || \ > ((PartitionType) == PARTITION_FREEBSD) || \ > ((PartitionType) == PARTITION_OPENBSD) || \ > ((PartitionType) == PARTITION_NETBSD)) > > >

2 1

undelate
by gmusume 20 Aug '17

20 Aug '17

hi I want undelate of the group thank Enviado desde mi smartphone Samsung Galaxy.

1 0

finish
by gmusume 20 Aug '17

20 Aug '17

ni. i don twant more email spam. thank u Enviado desde mi smartphone Samsung Galaxy.

1 0

Licensing - Make ReactOS conform again!
by Colin Finck 20 Aug '17

20 Aug '17

Hi all! I've held a presentation at Hackfest today regarding Licensing Best Practices, different positions about the GPL and its influence, and ways to improve ReactOS' conformance with all involved licenses. I think we should treat this subject even more seriously than others, given that we are an Open-Source project trying to provide an alternative to a proprietary product. Also licensing questions arise from time to time, which is why we should collect some answers. Please watch the video at https://youtu.be/OTVVz9VLisU or see the slides at https://svn.reactos.org/press-media/trunk/Events/2017%20-%20Hackfest/Licens… Discussions are open now! :) But if there are no objections, let's introduce SPDX license headers, .ABOUT files, and a complete license list as soon as possible. Cheers, Colin

2 2

Re: [ros-dev] [ros-diffs] [ekohl] 75611: [STOBJECT] - Add support for the hotplug icon. - Set default menu items in the context menus. - Use a timer to properly distinguish between a single and a double click on an icon. - ...
by Colin Finck 18 Aug '17

18 Aug '17

Hey Eric, The Battery icon, Hotplug icon and Quick Launch toolbars are currently developed as part of the Google Summer of Code "Taskbar Shell Extensions for ReactOS" project. Summer of Code ends next week, so you are welcome to join the Code Review at https://code.reactos.org. I guess CR-122 will be shortly updated with the latest changes there. Let's try to not duplicate efforts here ;) Best regards, Colin

2 1

ReactOS now listed in AppDB
by Erkin Alp Güney 12 Aug '17

12 Aug '17

I have recently added ReactOS as a distribution into Wine Application Compatibility database as ReactOS uses most of Wine components. ReactOS-Windows incompatibilities can now be tracked like Wine-Windows incompatibilies.

2 1

Re: [ros-dev] Ethereum for fundraiser
by Nicolò Altamura 11 Aug '17

11 Aug '17

Why not Monero too? Sent from UNKNOWN SMARTPHONE - K91820 -------- Messaggio originale -------- Da: Erkin Alp Güney <erkinalp9035(a)gmail.com> Data: 13/07/17 21:52 (GMT+01:00) A: ros-dev(a)reactos.org Oggetto: [ros-dev] Ethereum for fundraiser Ethereum is a decentralised cryptocurrency based on proof of work and proof of stake consensus with Turing-complete scripting. Utilising Ethereum for fundraiser will allow us to remove the middlemen from raising funds and allow us to distribute them more directly. I want to be first contract programmer for ReactOS ethereum account. Any kind of release schemes may be developed. However, this will need detailed discussion and official approval first. Yours, faithfully Erkin Alp _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

3 3

Re: [ros-dev] Modularizing the ReactOS repo in Git
by Alex Ionescu 04 Aug '17

04 Aug '17

I would strongly suggest using one master repo. Multi-repo projects and their brethren are a mess. Best regards, Alex Ionescu On Wed, Aug 2, 2017 at 1:18 PM, David Quintana (gigaherz) < gigaherz(a)gmail.com> wrote: > We have! If you look at Colin's email, it has a link to a google doc, we > list Repo in it, and why we think it's not fit for our use :) > > That aside, I had a new idea, which I mentioned on IRC. I have added it to > the document. > > On 2 August 2017 at 11:52, Alexander Sh. <chaez.san(a)gmail.com> wrote: > >> Have a look at Repo: https://code.google.com/archive/p/git-repo/ >> It is used by Android devs. >> >> 2 авг. 2017 г. 12:28 пользователь "David Quintana (gigaherz)" < >> gigaherz(a)gmail.com> написал: >> >> The issue comes when we have to do regression-testing. We would need a >>> tool that knows how to match up core, system, tests, ... otherwise >>> debugging regressions is going to be hellish. >>> >>> On 2 August 2017 at 11:17, Alexander Sh. <chaez.san(a)gmail.com> wrote: >>> >>>> Since we have RosBE, we can have multiple repositories without actually >>>> binding them and download them on demand. Or we can make a build script for >>>> every new small module that downloads (clones) repos it needs. >>>> >>>> 2 авг. 2017 г. 11:41 пользователь "Colin Finck" <colin(a)reactos.org> >>>> написал: >>>> >>>> Hi all! >>>> >>>> After David has successfully tested a first SVN -> Git conversion of >>>> our repo, here comes the next challenge: Finding a way to preserve our >>>> current modularization into reactos, rosapps, rostests and paving the way >>>> for even more modularization. >>>> My vision for the future is a small "core" repo that only contains our >>>> host tools and SDK. We could also split off subprojects like fast486/ntvdm >>>> or Paint into individual repos. Now that Microsoft has abandoned them under >>>> Windows, they may individually attract developers who would never hack on >>>> the entire ReactOS repo. Furthermore, 3rd party components could be >>>> imported through their repo instead of copy-pasting their code without >>>> history (as we do now). >>>> Even if that vision is a distant goal, the technology for it is already >>>> required for a reactos, rosapps, rostests modularization. >>>> >>>> Isn't that a perfect scenario for Git submodules? >>>> Not sure: I'm not aware that they support the concept of optional >>>> modules. You could only check out the "core" repo with all defined >>>> submodules. This would make it impossible to use "core" only to build >>>> Paint. There also seem to be other drawbacks when using submodules: >>>> https://codingkilledthecat.wordpress.com/2012/04/28/why-your >>>> -company-shouldnt-use-git-submodules/ >>>> >>>> Alternatives like Git subtrees, Google Repo, and Gitslave exist, but >>>> there is even less information about them. Furthermore, I think a good >>>> integration into GUI tools like TortoiseGit is also a requirement for most >>>> of us. >>>> >>>> David and I have started to write down our findings: >>>> https://docs.google.com/document/d/1Ey1xdS_0GcG7p7ZgHZBh4A3V >>>> Mq2uxyw5MpnUXbT8z6w/edit >>>> Your input on this is very welcome! >>>> >>>> I guess any migration to Git is blocked before we have a solution here. >>>> >>>> >>>> Cheers, >>>> >>>> Colin >>>> >>>> _______________________________________________ >>>> 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 >>>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > >

1 0

Status Meeting (July 2017)
by Colin Finck 03 Aug '17

03 Aug '17

Hi all! We're going to have the missed monthly status meeting for July tomorrow. Time will be 19:00 UTC as always and you will get your credentials shortly before the meeting. Agenda proposals so far include: - The 0.4.6 release - The upcoming Hackfest - Design of the RAPPS setup mode Please post any additional agenda proposals here. See you tomorrow! Colin

1 1

Re: [ros-dev] Modularizing the ReactOS repo in Git
by Alexander Sh. 02 Aug '17

02 Aug '17

Since we have RosBE, we can have multiple repositories without actually binding them and download them on demand. Or we can make a build script for every new small module that downloads (clones) repos it needs. 2 авг. 2017 г. 11:41 пользователь "Colin Finck" <colin(a)reactos.org> написал: Hi all! After David has successfully tested a first SVN -> Git conversion of our repo, here comes the next challenge: Finding a way to preserve our current modularization into reactos, rosapps, rostests and paving the way for even more modularization. My vision for the future is a small "core" repo that only contains our host tools and SDK. We could also split off subprojects like fast486/ntvdm or Paint into individual repos. Now that Microsoft has abandoned them under Windows, they may individually attract developers who would never hack on the entire ReactOS repo. Furthermore, 3rd party components could be imported through their repo instead of copy-pasting their code without history (as we do now). Even if that vision is a distant goal, the technology for it is already required for a reactos, rosapps, rostests modularization. Isn't that a perfect scenario for Git submodules? Not sure: I'm not aware that they support the concept of optional modules. You could only check out the "core" repo with all defined submodules. This would make it impossible to use "core" only to build Paint. There also seem to be other drawbacks when using submodules: https://codingkilledthecat.wor dpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/ Alternatives like Git subtrees, Google Repo, and Gitslave exist, but there is even less information about them. Furthermore, I think a good integration into GUI tools like TortoiseGit is also a requirement for most of us. David and I have started to write down our findings: https://docs.google.com/document/d/1Ey1xdS_0GcG7p7ZgHZBh4A3V Mq2uxyw5MpnUXbT8z6w/edit Your input on this is very welcome! I guess any migration to Git is blocked before we have a solution here. Cheers, Colin _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

2 3

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