Eric Kohl wrote:
> Hi!
Hi Eric
> I just started a three-week vacation and I'm upgrading my
> computer right
> now. My plan is to start porting WIDL this week.
If you get chance to look at StartService too, I'll owe you beer or 3 ;)
> PS: I think the WIDL source can be unlocked because it is
> based on WINE
> and the additional code was written by me, using IDL test
> files and MIDL
> from MSVC6.
I agree. I think we need to draft up a process for unlocking code in the
repository.
The first port of call needs to be confirmation from the author. If the
author confirms clean methods were utilised to write the code, it
automatically fast tracks the audit.
I know Arty has a good process for code which doesn't fall into this
category.
I'll try and get some sort of flowchart onto the wiki tonight.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Saveliy Tretiakov wrote:
> > PS: I think the WIDL source can be unlocked because it is based on
> > WINE and the additional code was written by me, using IDL
> test files
> > and MIDL from MSVC6.
>
> It is already unlocked. All code shared with wine is clean by default.
That doesn't necessarily mean it's unlocked.
With the exception of 1 or 2 folders, I locked everything in the repository
regardless of what it was.
Wine stuff will need to be unlocked as and when required.
I think it's best to wait until we have a formal unlocking flowchart before
we unlock any more code.
There have already been 1 or 2 mistakes which we will now have to
back-track.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Reminds me... didn't OS/2 have the capability to store both short and
long file names on a FAT16 partiton? How does that go with MS'
patents? Where MS really allowed to file a patent on something that
already existed?
/nitro2k01
On 3/10/06, Rick Langschultz <rlangschultz(a)cox.net> wrote:
> I just have a question about High Performance and Global file systems
> implementation in a ReactOS version? It would be wonderful to cluster
> file systems on ReactOS. Also support for EFS would be great. Any
> plans yet?
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
--
-----BEGIN 2ROT13 MESSAGE-----
The blog of nitro2k01: <http://soundandcomplete.blogspot.com/>
Saliga äro de som kan stava till 2k01! Sniphpha sniphph!
-----END 2ROT13 MESSAGE-----
I just have a question about High Performance and Global file systems
implementation in a ReactOS version? It would be wonderful to cluster
file systems on ReactOS. Also support for EFS would be great. Any
plans yet?
Saveliy Tretiakov wrote:
>
> James Tabor wrote:
>
> > I guess wine isn't taking any patch from ReactOS, even
> something based
> > on a rc file.
>
> Is this really true? Very sad :(
>
No, it isn't true.
There will probably be a reason why the patch wasn't accepted.
Wine have strict guidelines with regards to accepting patches. If a patch
doesn't comply, it is dropped without a reply.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
art yerkes wrote:
> You need to own the lock first before removing the needs-lock
> property.
> do this like 'svn lock --force foo.c'
If you break the lock first, there is then no problem removing the
svn:needs-lock property as the file is unlocked.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
I have now started locking unaudited files in the repository.
A special user called 'audit' has been created to do this lock. There
are two reasons for this:
1. The user who locks the file can still commit without unlocking.
Having a separate user to lock files removes this issue.
2. All developers can have the username and password for locking,
providing a system wide user to lock files. (ask Fireball for the u/n & p/w)
How do you lock files?
I'll list the method for tortoise-svn via the GUI. Die hard cmd line
gurus can adapt it to suit :)
- Firstly, go into your tortoise-svn settings and on the general page,
click 'clean now' for Subversion authentication data. This will remove
your current u/n & p/w
- To 'get a lock' on the file(s), right click the file / directory ,
navigate to tortoise-svn and select 'get lock'. Getting a lock will
trigger svn to contact the server automatically and apply the lock.
- Next pick the file / directory you just locked and right click. Select
file properties and under the subversion tab add 'svn:needs-lock' from
the combo box. Add a '*' for the value, check the recursive box and
click set. This will ensure all locked files which are checked out are
set as read only locally. This is just used as a handy reminder.
- You can now commit the files which will add the svn:needs-lock
property, however ensure that on the commit dialog, the 'keep locks'
checkbox is selected otherwise it will remove the lock you just placed.
Once I've audited the code, how do I unlock the files?
This is done as your regular username, not as the 'audit' user, so you
can clean the 'audit' username / password in the same manner as before
if you opted to save it.
Again, I'll list the tortoise method.
- Right click on the file / directory you want to unlock, navigate to
tortoiseSVN and select 'check for modifications'
- Select the file(s) you want to unlock, right click and select 'break
the lock'. SVN will automatically contact the repo and unlock the files.
- Don't forget to remove the svn:needs-lock property from the files to
ensure they are no longer checked out as read only.
I have so far locked the kernel, however I'm unsure if :
1. we're just gonna lock everything in one go (this would make life easy
to start with) and unlock everything as we deem it to be OK
2. lock only dirs we thing need auditing and unlock once clean.
I personally prefer option 1 as it ensures we don't miss anything, and
would probably be quicker in the long run.
Regards,
Ged.
I downloaded the latest ReactOS SVN today, and I attempted to compile it
with the RosBE. What happened was that the mingw32-make program shows this
message: "makefile.auto:47549: *** missing separator. Stop."... Well, I
figured that I got an incomplete build, so I reran TortoiseSVN and it said
that I had the complete distribution... This should be fixed so that ReactOS
will build, and if anyone is thinking... It occurs in all different building
syntax... all, livecd, bootcd, install, depends, etc. fail with the same
message...
Only WineMine is taken from Wine.
Our Solitaire is a project Steven found and gained the authors permission to
include it.
TaskManager was written by Brian IIRC, for ReactOS.
The notepad icon was taken from notepad2 which is GPL.
It is assumed that anything from other GPL projects is legal and
interchanagble.
If there is a copyright issue, I can change it.
-----Original Message-----
From: theUser BL [mailto:theuserbl@hotmail.com]
Sent: 02 March 2006 12:24
To: ros-dev(a)reactos.org
Subject: [ros-dev] Audit for non-code things?
I have tried out the SVN-Snapshot of ROS 3.0 by EmuandCo:
http://www.reactos.org/forum/viewtopic.php?t=1741#14146
At first, I want to say, that the ReactOS-Explorer looks a lot of nicer. And
some bugs are fixed. Nice work.
Then I have looked at the program-icons.
sol.exe and winefile.exe seems to use icons from old Windows-Versions
(Windows 3.x/95/98/NT4).
And with taskmgr.exe I am not sure, if the icon is from Windows or at own
designed.
All three programs comming from WINE and not from ReactOS. But is legal to
using it?
More woders me the new ReactOS Notepad.
If you click on Help -> About, then there opens a window where stands:
Icon borrowed from Notepad2 - http://www.flos-freeware.ch/notepad2.html
But Notepad2 have borrowed it from Microsofts WindowsXP Notepad.
It is funny to see, how the original creater of the icon, isn't named - but
instead
of it, an other one is named.
But the program notepad++ (http://notepad-plus.sourceforge.net/) is
OpenSource (GPL) and thats icon you could be used.
After that, I looked with Microsofts fontview.exe (the program is part of
every MS-Windows) in the text inside the fonts of ROS.
There are copyrighted fonts by Adobe, Bitstream, IBM, Sun and Transgaming.
And there are some Bitstream fonts in which stands:
Copyright 1990 as an unpublished work by Bitstream Inc. All rights reserved.
Confidential.
Confidential? Unpublished? From where comes then the fonts?
The fonts in which this stand are
c0419bt_.ttf, c0582bt_.ttf, c0583bt_.ttf, c0611bt_.ttf, c0632bt_.ttf,
c0633bt_.ttf,
c0648bt_.ttf and c0649bt_.ttf.
Ok, the Copyright is from 1990 (for 16 years!), but is it legal to use this
fonts?
Instead you could use the following fonts:
http://dejavu.sourceforge.net/http://linuxlibertine.sourceforge.net/http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&item_id=Gentium_lin
ux&_sc=1
Greatings
theuserbl
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Hi everybody!!!!!,
i'm trying to compile ReactOS SVN 0.3 but i'm having problems. I'm
currently using the ReactOS Build Enviroment 0.1-3.4.2 but it is
unable to compile rbuild. In fact the compilation process stops at
linking rbuild.exe.
I have created a directory in my D drive (rossrc) and i have
downloaded from the SVN the sources in d:\rossrc\trunk. So i changed
the directory to d:\rossrc\trunk\reactos and executed mingw32-make.
Then it began compiling the sources and after a while it stops with a
lot of garbage:
[LD] output-i386\tools\rbuild\rbuild.exe
plus lots of errors about undefined resources that i put at the end
of this email.
I currently reinstalled the Build Enviroment hoping that something
was installed wrong o was wrongly configured. But the same results
appeared. I also tried to compile it under the administration
account, because i currently run as user, but there are no changes
whatsoever (just trying to check that it isn't my fault or my
incompetence :P).
I blame the linker for this problem, but i don't know what is wrong
with it, because its a known fact that some versions of binutils dont
work but clearly RosBE has been tested a lot.
thanks in advance,
Logan_V8
PS: Garbage output from the linker
obj-i386\tools\rbuild\backend\msvc\msvcmaker.o: In function
`ZSt11__copy_aux2IPS
sS0_ET0_T_S2_S1_12__false_type':
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/stl_alg
obase.h:(.text$_ZNSt23_Rb_tree_const_iteratorISsEppEi[std::_Rb_tree_const_iterat
or<std::basic_string<char, std::char_traits<char>,
std::allocator<char> > >::ope
rator++(int)]+0x1b): undefined reference to
`std::_Rb_tree_increment(std::_Rb_tr
ee_node_base const*)'
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/stl_alg
obase.h:(.text$_ZNSt8_Rb_treeISsSsSt9_IdentityISsESt4lessISsESaISsEE9_M_insertEP
St18_Rb_tree_node_baseS7_RKSs[std::_Rb_tree<std::basic_string<char,
std::char_tr
aits<char>, std::allocator<char> >, std::basic_string<char,
std::char_traits<cha
r>, std::allocator<char> >, std::_Identity<std::basic_string<char,
std::char_tra
its<char>, std::allocator<char> > >,
std::less<std::basic_string<char, std::char
_traits<char>, std::allocator<char> > >,
std::allocator<std::basic_string<char,
std::char_traits<char>, std::allocator<char> > >
>::_M_insert(std::_Rb_tree_node
_base*, std::_Rb_tree_node_base*, std::basic_string<char,
std::char_traits<char>
, std::allocator<char> > const&)]+0x99): undefined reference to
`std::_Rb_tree_i
nsert_and_rebalance(bool, std::_Rb_tree_node_base*,
std::_Rb_tree_node_base*, st
d::_Rb_tree_node_base&)'
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/stl_alg
obase.h:(.text$_ZNSt17_Rb_tree_iteratorISsEmmEv[std::_Rb_tree_iterator<std::basi
c_string<char, std::char_traits<char>, std::allocator<char> >
>::operator--()]+0
x13): undefined reference to
`std::_Rb_tree_decrement(std::_Rb_tree_node_base*)'
obj-i386\tools\rbuild\backend\msvc\vcprojmaker.o: In function
`ZNSt24__copy_back
ward_dispatchIPPK10IfableDataS3_11__true_typeE4copyEPKS2_S7_S3_':
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/stl_alg
obase.h:(.text$_ZNSt17_Rb_tree_iteratorISsEppEi[std::_Rb_tree_iterator<std::basi
c_string<char, std::char_traits<char>, std::allocator<char> >
>::operator++(int)
]+0x1b): undefined reference to
`std::_Rb_tree_increment(std::_Rb_tree_node_base
*)'
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/stl_alg
obase.h:(.text$_ZNSt8_Rb_treeISsSsSt9_IdentityISsESt4lessISsESaISsEE5eraseESt17_
Rb_tree_iteratorISsE[std::_Rb_tree<std::basic_string<char,
std::char_traits<char
> , std::allocator<char> >, std::basic_string<char,
> std::char_traits<char>, std::
allocator<char> >, std::_Identity<std::basic_string<char,
std::char_traits<char>
, std::allocator<char> > >, std::less<std::basic_string<char,
std::char_traits<c
har>, std::allocator<char> > >,
std::allocator<std::basic_string<char, std::char
_traits<char>, std::allocator<char> > >
>::erase(std::_Rb_tree_iterator<std::bas
ic_string<char, std::char_traits<char>, std::allocator<char> >
>)]+0x17): undefi
ned reference to
`std::_Rb_tree_rebalance_for_erase(std::_Rb_tree_node_base*, st
d::_Rb_tree_node_base&)'
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/stl_alg
obase.h:(.text$_ZNSt17_Rb_tree_iteratorISsEppEv[std::_Rb_tree_iterator<std::basi
c_string<char, std::char_traits<char>, std::allocator<char> >
>::operator++()]+0
x13): undefined reference to
`std::_Rb_tree_increment(std::_Rb_tree_node_base*)'
obj-i386\tools\rbuild\backend\backend.o: In function
`ZNSt8_Rb_treeISsSt4pairIKS
sPN7Backend7FactoryEESt10_Select1stIS5_ESt4lessISsESaIS5_EE8_S_valueEPKSt13_Rb_t
ree_nodeIS5_E':
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ext/new_allo
cator.h:(.text$_ZNSt8_Rb_treeISsSt4pairIKSsPN7Backend7FactoryEESt10_Select1stIS5
_ESt4lessISsESaIS5_EE9_M_insertEPSt18_Rb_tree_node_baseSD_RKS5_[std::_Rb_tree<st
d::basic_string<char, std::char_traits<char>, std::allocator<char> >,
std::pair<
std::basic_string<char, std::char_traits<char>, std::allocator<char>
> const, Ba
ckend::Factory*>, std::_Select1st<std::pair<std::basic_string<char,
std::char_tr
aits<char>, std::allocator<char> > const, Backend::Factory*> >,
std::less<std::b
asic_string<char, std::char_traits<char>, std::allocator<char> > >,
std::allocat
or<std::pair<std::basic_string<char, std::char_traits<char>,
std::allocator<char
> > const, Backend::Factory*> >
> >::_M_insert(std::_Rb_tree_node_base*, std::_Rb_
tree_node_base*, std::pair<std::basic_string<char,
std::char_traits<char>, std::
allocator<char> > const, Backend::Factory*> const&)]+0x99): undefined
reference
to `std::_Rb_tree_insert_and_rebalance(bool,
std::_Rb_tree_node_base*, std::_Rb_
tree_node_base*, std::_Rb_tree_node_base&)'
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ext/new_allo
cator.h:(.text$_ZNSt17_Rb_tree_iteratorISt4pairIKSsPN7Backend7FactoryEEEmmEv[std
::_Rb_tree_iterator<std::pair<std::basic_string<char,
std::char_traits<char>, st
d::allocator<char> > const, Backend::Factory*>
>::operator--()]+0x13): undefined
reference to `std::_Rb_tree_decrement(std::_Rb_tree_node_base*)'
obj-i386\tools\rbuild\automaticdependency.o: In function
`ZNSt8_Rb_treeISsSt4pai
rIKSsP10SourceFileESt10_Select1stIS4_ESt4lessISsESaIS4_EE14_M_create_nodeERKS4_'
:
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/stl_tre
e.h:(.text$_ZNSt17_Rb_tree_iteratorISt4pairIKSsP10SourceFileEEppEi[std::_Rb_tree
_iterator<std::pair<std::basic_string<char, std::char_traits<char>,
std::allocat
or<char> > const, SourceFile*> >::operator++(int)]+0x1b): undefined
reference to
`std::_Rb_tree_increment(std::_Rb_tree_node_base*)'
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/stl_tre
e.h:(.text$_ZNSt8_Rb_treeISsSt4pairIKSsP10SourceFileESt10_Select1stIS4_ESt4lessI
SsESaIS4_EE9_M_insertEPSt18_Rb_tree_node_baseSC_RKS4_[std::_Rb_tree<std::basic_s
tring<char, std::char_traits<char>, std::allocator<char> >,
std::pair<std::basic
_string<char, std::char_traits<char>, std::allocator<char> > const,
SourceFile*>
, std::_Select1st<std::pair<std::basic_string<char,
std::char_traits<char>, std:
:allocator<char> > const, SourceFile*> >,
std::less<std::basic_string<char, std:
:char_traits<char>, std::allocator<char> > >,
std::allocator<std::pair<std::basi
c_string<char, std::char_traits<char>, std::allocator<char> > const,
SourceFile*
> > >::_M_insert(std::_Rb_tree_node_base*, std::_Rb_tree_node_base*,
> std::pair<s
td::basic_string<char, std::char_traits<char>, std::allocator<char> >
const, Sou
rceFile*> const&)]+0x99): undefined reference to
`std::_Rb_tree_insert_and_rebal
ance(bool, std::_Rb_tree_node_base*, std::_Rb_tree_node_base*,
std::_Rb_tree_nod
e_base&)'
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/stl_tre
e.h:(.text$_ZNSt17_Rb_tree_iteratorISt4pairIKSsP10SourceFileEEmmEv[std::_Rb_tree
_iterator<std::pair<std::basic_string<char, std::char_traits<char>,
std::allocat
or<char> > const, SourceFile*> >::operator--()]+0x13): undefined
reference to `s
td::_Rb_tree_decrement(std::_Rb_tree_node_base*)'
obj-i386\tools\rbuild\directory.o: In function
`ZNSt8_Rb_treeISsSt4pairIKSsP9Dir
ectoryESt10_Select1stIS4_ESt4lessISsESaIS4_EE14_M_create_nodeERKS4_':
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ext/new_allo
cator.h:(.text$_ZNSt17_Rb_tree_iteratorISt4pairIKSsP9DirectoryEEppEv[std::_Rb_tr
ee_iterator<std::pair<std::basic_string<char, std::char_traits<char>,
std::alloc
ator<char> > const, Directory*> >::operator++()]+0x13): undefined
reference to `
std::_Rb_tree_increment(std::_Rb_tree_node_base*)'
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ext/new_allo
cator.h:(.text$_ZNSt8_Rb_treeISsSt4pairIKSsP9DirectoryESt10_Select1stIS4_ESt4les
sISsESaIS4_EE9_M_insertEPSt18_Rb_tree_node_baseSC_RKS4_[std::_Rb_tree<std::basic
_string<char, std::char_traits<char>, std::allocator<char> >,
std::pair<std::bas
ic_string<char, std::char_traits<char>, std::allocator<char> > const,
Directory*
> , std::_Select1st<std::pair<std::basic_string<char,
> std::char_traits<char>, std
::allocator<char> > const, Directory*> >,
std::less<std::basic_string<char, std:
:char_traits<char>, std::allocator<char> > >,
std::allocator<std::pair<std::basi
c_string<char, std::char_traits<char>, std::allocator<char> > const,
Directory*>
> >::_M_insert(std::_Rb_tree_node_base*, std::_Rb_tree_node_base*,
std::pair<st
d::basic_string<char, std::char_traits<char>, std::allocator<char> >
const, Dire
ctory*> const&)]+0x99): undefined reference to
`std::_Rb_tree_insert_and_rebalan
ce(bool, std::_Rb_tree_node_base*, std::_Rb_tree_node_base*,
std::_Rb_tree_node_
base&)'
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/ext/new_allo
cator.h:(.text$_ZNSt17_Rb_tree_iteratorISt4pairIKSsP9DirectoryEEmmEv[std::_Rb_tr
ee_iterator<std::pair<std::basic_string<char, std::char_traits<char>,
std::alloc
ator<char> > const, Directory*> >::operator--()]+0x13): undefined
reference to `
std::_Rb_tree_decrement(std::_Rb_tree_node_base*)'
obj-i386\tools\rbuild\rbuild.o: In function
`ZNSt3mapISsPN7Backend7FactoryESt4le
ssISsESaISt4pairIKSsS2_EEE3endEv':
D:/RosBE/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/bits/stl_map
.h:(.text$_ZNSt17_Rb_tree_iteratorISt4pairIKSsPN7Backend7FactoryEEEppEi[std::_Rb
_tree_iterator<std::pair<std::basic_string<char,
std::char_traits<char>, std::al
locator<char> > const, Backend::Factory*> >::operator++(int)]+0x1b):
undefined r
eference to `std::_Rb_tree_increment(std::_Rb_tree_node_base*)'
obj-i386\tools\ssprintf.o:ssprintf.cpp:(.text$_ZNSbIwSt11char_traitsIwESaIwEE4_R
ep10_M_disposeERKS1_[std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::
allocator<wchar_t> >::_Rep::_M_dispose(std::allocator<wchar_t>
const&)]+0x22): u
ndefined reference to `__gnu_cxx::__exchange_and_add(int volatile*, int)'
collect2: ld returned 1 exit status
mingw32-make: *** [output-i386\tools\rbuild\rbuild.exe] Error 1
--
_______________________________________________
Check out the latest SMS services @ http://www.linuxmail.org
This allows you to send and receive SMS through your mailbox.
Powered by Outblaze
I have tried out the SVN-Snapshot of ROS 3.0 by EmuandCo:
http://www.reactos.org/forum/viewtopic.php?t=1741#14146
At first, I want to say, that the ReactOS-Explorer looks a lot of nicer. And
some bugs are fixed. Nice work.
Then I have looked at the program-icons.
sol.exe and winefile.exe seems to use icons from old Windows-Versions
(Windows 3.x/95/98/NT4).
And with taskmgr.exe I am not sure, if the icon is from Windows or at own
designed.
All three programs comming from WINE and not from ReactOS. But is legal to
using it?
More woders me the new ReactOS Notepad.
If you click on Help -> About, then there opens a window where stands:
Icon borrowed from Notepad2 - http://www.flos-freeware.ch/notepad2.html
But Notepad2 have borrowed it from Microsofts WindowsXP Notepad.
It is funny to see, how the original creater of the icon, isn't named - but
instead
of it, an other one is named.
But the program notepad++ (http://notepad-plus.sourceforge.net/) is
OpenSource (GPL) and thats icon you could be used.
After that, I looked with Microsofts fontview.exe (the program is part of
every MS-Windows) in the text inside the fonts of ROS.
There are copyrighted fonts by Adobe, Bitstream, IBM, Sun and Transgaming.
And there are some Bitstream fonts in which stands:
Copyright 1990 as an unpublished work by Bitstream Inc. All rights reserved.
Confidential.
Confidential? Unpublished? From where comes then the fonts?
The fonts in which this stand are
c0419bt_.ttf, c0582bt_.ttf, c0583bt_.ttf, c0611bt_.ttf, c0632bt_.ttf,
c0633bt_.ttf,
c0648bt_.ttf and c0649bt_.ttf.
Ok, the Copyright is from 1990 (for 16 years!), but is it legal to use this
fonts?
Instead you could use the following fonts:
http://dejavu.sourceforge.net/http://linuxlibertine.sourceforge.net/http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&item_id=Gentium_li…
Greatings
theuserbl
> From: art yerkes
>
> No we imported X fonts where permitted and used TGMarlett for
> window titles (also permitted, see media/fonts/doc)
Executive summary: There's no problem with the fonts.
Details:
Jason imported helb___.ttf and timr____.ttf in r1877 from OpenOffice (LGPL,
so GPL compatible).
I imported the Bitstream Vera fonts (Vera.ttf, VeraBI.ttf, VeraBd.ttf,
VeraIt.ttf, VeraMoBI.ttf, VeraMoBd.ttf, VeraMoIt.ttf, VeraMono.ttf,
VeraSe.ttf, VeraSeBd.ttf) in r4689. They are covered by the license in
media/fonts/doc/VERA-COPYRIGHT.TXT.
Steven imported TGMarlett.ttf in r9427. The "TG" refers to Trans Gaming. The
font is under a X11 license (see
http://www.transgaming.com/gamefaq.php?specialid=3 under 6.2) which is GPL
compatible.
Art imported some of the X fonts (UTBI____.ttf, UTB_____.ttf, UTI_____.ttf,
UTRG____.ttf, c0419bt_.ttf, c0582bt_.ttf, c0583bt_.ttf, c0611bt_.ttf,
c0632bt_.ttf, c0633bt_.ttf, c0648bt_.ttf, c0649bt_.ttf, cour.ttf, courb.ttf,
courbi.ttf ) in r10143. These are covered by the licenses in
media/fonts/doc/COPYRIGHT.IBM and media/fonts/doc/Copyright.Bitstream.
GvG
ReactOS.Bugzilla(a)reactos.org wrote:
>http://www.reactos.org/bugzilla/show_bug.cgi?id=1327
>
> Summary: Scrambled output from Calculator
> Product: ReactOS Apps (rosapps)
> Version: unspecified
> Platform: x86 Hardware
> OS/Version: ReactOS
> Status: NEW
> Severity: normal
> Priority: P3
> Component: Utilities
> AssignedTo: ros-bugs(a)reactos.org
> ReportedBy: the_real_martian(a)msn.com
> QAContact: ros-bugs(a)reactos.org
>
>
>When using Calculator, it will have outputs such as 308-d or 0770777-ff. This
>happens when it is set to "Dec", not Hex
>
>
>
Does this happen on both ROS and Windows or just ROS? Can you reproduce
it everytime with certain steps? And this isnt really considered ROS
Apps I dont think since Calc.exe is in /reactos.
Brandon
ReactOS.Bugzilla(a)reactos.org wrote:
>http://www.reactos.org/bugzilla/show_bug.cgi?id=1328
>
> Summary: Alt+Tab has no effect
> Product: ReactOS
> Version: 0.2.9
> Platform: x86 Hardware
> OS/Version: ReactOS
> Status: NEW
> Severity: normal
> Priority: P3
> Component: Kernel
> AssignedTo: ros-bugs(a)reactos.org
> ReportedBy: the_real_martian(a)msn.com
> QAContact: ros-bugs(a)reactos.org
>
>
>In Windows, Alt-Tab usually allows switching between open Windows. Alt-Tab has
>no effect in ReactOS
>
>
>
There is a hotkey meta bug please make this a dependency
.
Brandon
ReactOS.Bugzilla(a)reactos.org wrote:
>http://www.reactos.org/bugzilla/show_bug.cgi?id=1326
>
> Summary: Ctrl+Alt+Del has no effect
> Product: ReactOS
> Version: 0.2.9
> Platform: x86 Hardware
> OS/Version: ReactOS
> Status: NEW
> Severity: normal
> Priority: P3
> Component: Kernel
> AssignedTo: ros-bugs(a)reactos.org
> ReportedBy: the_real_martian(a)msn.com
> QAContact: ros-bugs(a)reactos.org
>
>
>When Ctrl+Alt+Del is pressed, there is no effect. This can really get annoying
>if a program is not responding, and you have to right-click the taskbar to open
>Task Manager.
>
>
>
There is a hotkey meta bug please make this a dependency
.
Brandon
I was wondering if there was any plan on implementing Intel's EFI in
the near or distant future. I hear that Intel wants to move away from
BIOS and work more closely with EFI. I know that support for the BIOS
will never totally disappear but EFI is a better architecture in my
opinion.
So here is my request for EFI support in ReactOS.
I had this same problem when developing my bootsector. When I reset the
bootdrive before I jumped to freeldr the problem went away. I think that
the first thing that freeldr needs to is to reset the boot drive before
it moves on.
ReactOS.Bugzilla(a)reactos.org wrote:
> http://www.reactos.org/bugzilla/show_bug.cgi?id=390
>
>
>
>
>
> ------- Additional Comments From simona(a)informatik.tu-muenchen.de 2006-02-25 00:17 CET -------
> got the same problem with the boot cd 2.9 on a travelmate 290.
> shoud be the same hardware and the same crappy "insyde software" bios (v2.0 on
> my chip):
> Press any key to boot from CD <enter>
>
> Failed to read the PVD.
> Press any key
> Failed to read the super block.
> Press any key <enter>
> Failed to read boot sector.
> Press any key <enter>
> Failed to read boot sector.
> Press any key <enter>
> Unable to locate boot parition
>
> Press any key <enter>
> Error opening boot partition for file access. <enter>
>
> Press any key to boot from CD
>
> And so on...
> Notice that one time the any-key message appears without waitig for any key.
>
> And, after the first "round" it waits way shorter for any keypress to boot
> from CD (the time between two dots printed has decreased).
> I experienced this problem with the first LiveCD version i tried (2.0 i
> think).
>
>
Brandon Turner wrote
>
> " B - Sections of ReactOS which require auditing are
> 'locked', that being
> that the source is fully available to download and build, but no
> development work should be undertaken until the said code has
> passed the
> audit. The lock will be removed only when that section of
> code has been
> audited."
>
> I have asked 3-4 times but still havent got an answer as far
> as I can tell. Does the definition of "audit" in the pharse
> mean the code needs to be looked through and documented and
> bad code be marked. Or does it mean all that and the marked
> code needs to be rewritten for it to be considered "audited".
Here is my understanding (although I'm not saying it's correct)
First of all, we must take the authors word on whether something needs
auditing or not.
If a particular author says the code which he wrote is clean, then this
automatically bypasses the audit.
This clears up James' worry about his dll code which he has declared clean.
If an author can't be contacted, it is classes as unknown and must go
through the audit process.
Once we have a list of all code which has not been verified, a new SVN user
is generated and he is used to lock all the code (this is done with a
separate user to avoid certain features of SVN lock)
Any developer is able to remove a lock. Locking the code only really acts as
a reminder that the code has not passed an audit. This code shouldn't be
modified / improved until it has done so. The lock therefore ensures all the
code is audited and nothing is missed. It also acts as an incentive to get
the code audited.
Without the lock, I think it will be conveniently forgotten about.....
Once code has been locked how does it get out of locked status?
I think there are 3 possibilities:
- look through the code looking for anything even remotely strange. (I think
Alex's description which I have linked to the end of this mail makes some
good points). If all the code seems perfectly legitimate, it passes the
audit and the lock is removed.
- If code doesn't seem legitimate, search for documentation. If docs are
found to cater for all the questionable code, the docs are added and the
code passes audit.
- If the code doesn't seem legitimate and docs can't be found, then the code
is deemed dirty and further action must be taken (e.g. part of the code
rewritten, all the code rewritten, docs written, etc). This would have to be
discussed at greater length.
HTH
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Vote topic : Ensure code auditing is carried out
Start date : 16/02/06
Period : 7 days discussion, 7 days voting
With the success of proposal B in the recent vote and the old repository
reopening for business, we need to discuss ways to ensure the code is
audited and doesn't take a backseat.
Following the correct voting procedure, there will be a 7 day discussion
period, followed by a 7 day voting period.
Until this decision is made, I propose for the repository to be fully
open, with developers being diligent with their actions.
This topic has been discussed somewhat between developers, although not
extensively.
Two viable proposals have so far been put forward and are as follows :
A - The repository is completely open to all development and ReactOS
developers must take it upon themselves to ensure all code is audited.
B - Sections of ReactOS which require auditing are 'locked', that being
that the source is fully available to download and build, but no
development work should be undertaken until the said code has passed the
audit. The lock will be removed only when that section of code has been
audited.
Discussion of these topics and any further proposals should be in reply
to this topic.
How do we feel about having the documentation directory from the casper
tree (the one where audit documentation is being written) moved to
svn://svn.reactos.ru/reactos/trunk/documentation?
--
Discordant is the murmur at such treading down of lovely things while
god's most lordly gift to man is decency of mind. Call that man only
blest who has in sweet tranquility brought his life to close.
If only I could act as such, my hope is good.
-- Aeschylus' Agamemnon (translated by H. W. Smyth)
At
http://www.reactos.org/pipermail/ros-dev/2006-February/007878.html
and on other places there is mentioned, that the way to audit is, to look at
the ReactOS-Source-Code, look if it looks understandable.
The problem is, that is possible, that people disasseble MS-Windows-code and
port then the Assembler-Code in stupid C code.
And - because (not clean room) reverse engineering isn't allowed - all
code, which looks stupd will be eliminated.
That was also discussed in a german forum. There someone have at
http://www.heise.de/newsticker/foren/go.shtml?read=1&msg_id=9920469&forum_i…
discribed, how a normal C program can be compiled to assebler code and an
other people create stupied C code, where you can see, that it was reverse
engineered.
But in the same forum, someone have mentioned, that there existing
decompiler like Boomerang
http://boomerang.sourceforge.net/
which creates from binary code logical, easy to read C code. (Don't know
before, that something like this exists).
Have a look at
http://boomerang.sourceforge.net/cando.php
I want with this mail only to say, that it would be very hard to find the
reverse engineered code (if there existing one).
Greatings
theuserbl
martinf(a)svn.reactos.org wrote:
> fix build with _ROS_ define
>
>
> Updated files:
> trunk/reactos/base/shell/explorer/shell/mainframe.cpp
>
Hi,
Should you move your changes to the new svn?
Thanks,
James
Through an intriguing article on Slashdot I have read that ipods are
now being used for things other than audio. They are being used to
obtain data from a computer, and computer network obtaining business
documents and such in seconds.
One way to make ReactOS a safer operating environment is to use a
virtual encrypted file system that would restrict the copying of
files to any usb, or network device via an encryption algorithm. So I
propose a VEFS that would restrict this. The VEFS would disallow the
passage of documents to any removable device unless the user has
permission to archive them, which would be the "a" attribute. The
VEFS would make use of two AES encryption algorithms which would
encrypt the file's contents. One being a key another a lock, however
the user must provide a password to unlock and decrypt the files.
This would allow the user to unlock the files, only if they have the
password. This would also allow users to secure their personal and
corporate data.
Any ideas?