Hi all,
Does anyone know if MingW packs structures by default (as I think Borland
does),
or do I need to declare #pragma pack(1) ?
Thanks,
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
Hi all
There's interest in forming an interface team, and I think it's worth
exploring. This team would be responsible for all visual styling that
goes on in the project. This includes ReactOS UI design and the look &
feel of the website.
So far both mf (as known on IRC, and has come up with most of our
current icons in ReactOS) and Mikko Tikkanen (has done a great mock-up
for the site: http://devnet.dnsalias.net/guidesign/web_mockup.jpg)
have shown interest in heading this team. If anyone else wants to
throw their hat into the ring - feel free to do so.
It'll probably come down to a vote - but first if the respective
people could tell everyone more about themselves and perhaps the
related UI experience they have.
Regards
Jason
[CC] dinput_main.c
[CC] joystick_linux.c
[CC] joystick_linuxinput.c
[CC] keyboard.c
keyboard.c:43:1: warning: "LLKHF_EXTENDED" redefined
In file included from ../../include/wine/winuser.h:10,
from keyboard.c:30:
../../w32api/include/winuser.h:2150:1: warning: this is the location of
the prev
ious definition
keyboard.c:46:1: warning: "LLKHF_UP" redefined
../../w32api/include/winuser.h:2153:1: warning: this is the location of
the prev
ious definition
[CC] mouse.c
mouse.c:49: error: conflicting types for 'MSLLHOOKSTRUCT'
../../w32api/include/winuser.h:3076: error: previous declaration of
'MSLLHOOKSTR
UCT' was here
mouse.c:49: error: conflicting types for 'PMSLLHOOKSTRUCT'
../../w32api/include/winuser.h:3076: error: previous declaration of
'PMSLLHOOKST
RUCT' was here
make[1]: *** [mouse.o] Error 1
make: *** [dinput] Error 2
E:\src\ros\trunk\reactos>
Hi,
--- Jason Filby <jason.filby(a)gmail.com> wrote:
, and has come up with most of our
> current icons in ReactOS) and Mikko Tikkanen (has done a great mock-up
> for the site: http://devnet.dnsalias.net/guidesign/web_mockup.jpg)
I love that site design. That is how reactos.org should look.
Thanks
Steven
Discover Yahoo!
Find restaurants, movies, travel and more fun for the weekend. Check it out!
http://discover.yahoo.com/weekend.html
I was thinking about the security policy and NTFS partitions, I really like this function, but this is only availible on NTFS, but why not make the FAT driver head the policies and make it work as NTFS?
Of course it's really easy to boot from a DOS disk and be able to read/write any file, but being able to set access policys on a home-computer/network is a real help for an administrator. It doesn't stop a hacker, but children and wifes (some of them anyway).
Microsoft isn't interested in such a driver because they want everyone to run NTFS, but we don't have such preference, we are interested in the best function not our habitat.
Yours sincerely,
Jaix Bly
Its now fixed, please update.
--- Hartmut Birr <hartmut.birr(a)gmx.de> a écrit:
> Hi,
>
> I'm not able to compile win32k.
>
> - Hartmut
>
> M:\Sandbox\ros_work\reactos>_make win32k
> win32k: [DEPENDS] .w32k.d
> win32k: [PCH] w32k.h
> In file included from w32k.h:21:
> ../../ntoskrnl/include/internal/ob.h:41: error: syntax error before
> "OB_DUMP_METHOD"
> ../../ntoskrnl/include/internal/ob.h:41: warning: no semicolon at end of
> struct or union
> ../../ntoskrnl/include/internal/ob.h:42: warning: type defaults to `int'
> in declaration of `OpenProcedure'
> ../../ntoskrnl/include/internal/ob.h:42: warning: data definition has no
> type or storage class
> ../../ntoskrnl/include/internal/ob.h:43: error: syntax error before
> "CloseProcedure"
> ../../ntoskrnl/include/internal/ob.h:43: warning: type defaults to `int'
> in declaration of `CloseProcedure'
> ../../ntoskrnl/include/internal/ob.h:43: warning: data definition has no
> type or storage class
> ../../ntoskrnl/include/internal/ob.h:44: error: syntax error before
> "DeleteProcedure"
> ../../ntoskrnl/include/internal/ob.h:44: warning: type defaults to `int'
> in declaration of `DeleteProcedure'
> ../../ntoskrnl/include/internal/ob.h:44: warning: data definition has no
> type or storage class
> ../../ntoskrnl/include/internal/ob.h:45: error: syntax error before
> "ParseProcedure"
> ../../ntoskrnl/include/internal/ob.h:45: warning: type defaults to `int'
> in declaration of `ParseProcedure'
> ../../ntoskrnl/include/internal/ob.h:45: warning: data definition has no
> type or storage class
> ../../ntoskrnl/include/internal/ob.h:46: error: syntax error before
> "SecurityProcedure"
> ../../ntoskrnl/include/internal/ob.h:46: warning: type defaults to `int'
> in declaration of `SecurityProcedure'
> ../../ntoskrnl/include/internal/ob.h:46: warning: data definition has no
> type or storage class
> ../../ntoskrnl/include/internal/ob.h:47: error: syntax error before
> "QueryNameProcedure"
> ../../ntoskrnl/include/internal/ob.h:47: warning: type defaults to `int'
> in declaration of `QueryNameProcedure'
> ../../ntoskrnl/include/internal/ob.h:47: warning: data definition has no
> type or storage class
> ../../ntoskrnl/include/internal/ob.h:48: error: syntax error before
> "OkayToCloseProcedure"
> ../../ntoskrnl/include/internal/ob.h:48: warning: type defaults to `int'
> in declaration of `OkayToCloseProcedure'
> ../../ntoskrnl/include/internal/ob.h:48: warning: data definition has no
> type or storage class
> ../../ntoskrnl/include/internal/ob.h:49: warning: type defaults to `int'
> in declaration of `OBJECT_TYPE_INITIALIZER'
> ../../ntoskrnl/include/internal/ob.h:49: warning: type defaults to `int'
> in declaration of `POBJECT_TYPE_INITIALIZER'
> ../../ntoskrnl/include/internal/ob.h:49: warning: data definition has no
> type or storage class
> ../../ntoskrnl/include/internal/ob.h:62: error: syntax error before
> "OBJECT_TYPE_INITIALIZER"
> ../../ntoskrnl/include/internal/ob.h:62: warning: no semicolon at end of
> struct or union
> ../../ntoskrnl/include/internal/ob.h:65: error: syntax error before '}'
> token
> ../../ntoskrnl/include/internal/ob.h:65: warning: type defaults to `int'
> in declaration of `OBJECT_TYPE'
> ../../ntoskrnl/include/internal/ob.h:65: warning: data definition has no
> type or storage class
> ../../ntoskrnl/include/internal/ob.h:191: error: syntax error before
> "ObjectTypeInitializer"
> _make[1]: *** [w32k.h.gch] Error 1
> _make: *** [win32k] Error 2
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
>
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi,
I'm not able to compile win32k.
- Hartmut
M:\Sandbox\ros_work\reactos>_make win32k
win32k: [DEPENDS] .w32k.d
win32k: [PCH] w32k.h
In file included from w32k.h:21:
../../ntoskrnl/include/internal/ob.h:41: error: syntax error before
"OB_DUMP_METHOD"
../../ntoskrnl/include/internal/ob.h:41: warning: no semicolon at end of
struct or union
../../ntoskrnl/include/internal/ob.h:42: warning: type defaults to `int'
in declaration of `OpenProcedure'
../../ntoskrnl/include/internal/ob.h:42: warning: data definition has no
type or storage class
../../ntoskrnl/include/internal/ob.h:43: error: syntax error before
"CloseProcedure"
../../ntoskrnl/include/internal/ob.h:43: warning: type defaults to `int'
in declaration of `CloseProcedure'
../../ntoskrnl/include/internal/ob.h:43: warning: data definition has no
type or storage class
../../ntoskrnl/include/internal/ob.h:44: error: syntax error before
"DeleteProcedure"
../../ntoskrnl/include/internal/ob.h:44: warning: type defaults to `int'
in declaration of `DeleteProcedure'
../../ntoskrnl/include/internal/ob.h:44: warning: data definition has no
type or storage class
../../ntoskrnl/include/internal/ob.h:45: error: syntax error before
"ParseProcedure"
../../ntoskrnl/include/internal/ob.h:45: warning: type defaults to `int'
in declaration of `ParseProcedure'
../../ntoskrnl/include/internal/ob.h:45: warning: data definition has no
type or storage class
../../ntoskrnl/include/internal/ob.h:46: error: syntax error before
"SecurityProcedure"
../../ntoskrnl/include/internal/ob.h:46: warning: type defaults to `int'
in declaration of `SecurityProcedure'
../../ntoskrnl/include/internal/ob.h:46: warning: data definition has no
type or storage class
../../ntoskrnl/include/internal/ob.h:47: error: syntax error before
"QueryNameProcedure"
../../ntoskrnl/include/internal/ob.h:47: warning: type defaults to `int'
in declaration of `QueryNameProcedure'
../../ntoskrnl/include/internal/ob.h:47: warning: data definition has no
type or storage class
../../ntoskrnl/include/internal/ob.h:48: error: syntax error before
"OkayToCloseProcedure"
../../ntoskrnl/include/internal/ob.h:48: warning: type defaults to `int'
in declaration of `OkayToCloseProcedure'
../../ntoskrnl/include/internal/ob.h:48: warning: data definition has no
type or storage class
../../ntoskrnl/include/internal/ob.h:49: warning: type defaults to `int'
in declaration of `OBJECT_TYPE_INITIALIZER'
../../ntoskrnl/include/internal/ob.h:49: warning: type defaults to `int'
in declaration of `POBJECT_TYPE_INITIALIZER'
../../ntoskrnl/include/internal/ob.h:49: warning: data definition has no
type or storage class
../../ntoskrnl/include/internal/ob.h:62: error: syntax error before
"OBJECT_TYPE_INITIALIZER"
../../ntoskrnl/include/internal/ob.h:62: warning: no semicolon at end of
struct or union
../../ntoskrnl/include/internal/ob.h:65: error: syntax error before '}'
token
../../ntoskrnl/include/internal/ob.h:65: warning: type defaults to `int'
in declaration of `OBJECT_TYPE'
../../ntoskrnl/include/internal/ob.h:65: warning: data definition has no
type or storage class
../../ntoskrnl/include/internal/ob.h:191: error: syntax error before
"ObjectTypeInitializer"
_make[1]: *** [w32k.h.gch] Error 1
_make: *** [win32k] Error 2
>
> Well, in short, in the (now free downloadable) SFU 3.5 there is a NIS
> bridge, which exposes accounts and groups to NIS compliant machines.
> After installing SFU, your credentials management console shows a tab
> with tipical UNIX/POSIX attributes and files have an attrribute tab with
> rwxrvxrvx... It seems that the design of IFS subsystem assumes a
> superset of every known fs available about 1990.
>
Hmmm, yea. That's basicly what I think of the wohle thing.
It should be possible for an IFS or another part to do a 1:1 or a 100:90
mapping of rights and users <-> SIDs
In my opinion there'S nothing to it to limit the user-part of SIDs to
16-bit and cut out just that.
PS. My favorite is still JFS.
It has been prooved on OS/2 and OS/2 is our next relative. Its Src is
open(GPL) and it supports most of the features. Even reparse points can
be transparently implemented (EAs). I have nothing against s.o.
implementing NTFS, but I see many problems. So cut & off
Hi,
--- Robert K�pferl <rob(a)koepferl.de> wrote:
> Please, all, tell me, what are you insisting so much on so unimportand
> features like transparent encryption and transparent compression. In my
> eyes the first step is to have a FS which is better than FAT and allows
> ACLs+EA or xattr+posix-acls (NOTE these are mostly isomorphisms). Most
> people can pass on enc+compr at all. Some use it but they can wait or
> also pass on it until it can/will be implemented or not implemented.
> There exist ways to come around that. Even GPL. See 7zip and TrueCrypt.
> For my requirements TrueCrypt beats NTFS-EFS. So why bother.
If you want to extend vfat support which we have already done in our vfatfs.sys by adding support
for xbox fatx, then I propose we add Transactional Fat support. The idea was first proposed on
LKML and then later implement in WinCE.
Thanks
Steven
Yahoo! Mail
Stay connected, organized, and protected. Take the tour:
http://tour.mail.yahoo.com/mailtour.html
