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
Hi!
greatlrd(a)svn.reactos.com wrote:
> Partiy implement long filename support
> example filefilefile.txt can store now with cdmake
> but not filefilefiles.txt have not check why it say not a iso9660 name
>
>
>
>
> Updated files:
> trunk/reactos/tools/cdmake/cdmake.c
>
>
Getting this;
cdmake.c: In function `parse_filename_into_dirrecord':
cdmake.c:621: warning: implicit declaration of function `itoa'
make[2]: *** [cdmake.o] Error 1
make[1]: *** [cdmake_target] Error 2
make: *** [tools] Error 2
Have fun!
James
Hi,
I'm not able to boot ros on my test machine. It seems that the crash is
related to rev 15255.
- Hartmut
...
DriverBase for aic78u2.sys: 809ed000
(io/driver.c:1204) Driver load failed, status (c0000001)
DriverBase for symc8xx.sys: 80a01000
(io/driver.c:1204) Driver load failed, status (c0000001)
DriverBase for fireport.sys: 80a0a000
(io/irp.c:397) Total allocates: 367
(io/irp.c:399) Alloc attempt on CPU list: 80d67e38
(io/irp.c:397) Total allocates: 368
(io/irp.c:399) Alloc attempt on CPU list: 80d67c80
(io/irp.c:397) Total allocates: 369
(io/irp.c:399) Alloc attempt on CPU list: 80d67ac8
(io/irp.c:397) Total allocates: 370
(io/irp.c:399) Alloc attempt on CPU list: 80c1c590
(io/irp.c:397) Total allocates: 371
(io/irp.c:399) Alloc attempt on CPU list: 00000000
(io/irp.c:406) Total misses: 17
(io/irp.c:412) Alloc attempt on SYS list: 80d6abd0
(io/irp.c:397) Total allocates: 372
(io/irp.c:399) Alloc attempt on CPU list: 00000000
(io/irp.c:406) Total misses: 18
(io/irp.c:412) Alloc attempt on SYS list: cccccccc
KeBugCheckWithTf at ke/catch.c:222
A problem has been detected and ReactOS has been shut down to prevent
damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
KMODE_EXCEPTION_NOT_HANDLED
Technical information:
*** STOP: 0x0000001E (0xc0000005,0x800a3a68,0x00000000,0xcccccccc)
*** ntoskrnl.exe - Address 0x800a3a68 base at 0x80000000, DateStamp 0x0
Page Fault Exception: 14(2)
Processor: 0 CS:EIP 8:800a3a68 <ntoskrnl.exe:a3a68
(D:\DOKUME~1\hb\LOKALE~1\Temp/ccUdbaaa.s:35 (memset))>
cr2 cccccccc cr3 34000 Proc: 80c04ce0 Pid: 4 <System> Thrd: 80c057e0 Tid: 0
DS 10 ES 10 FS 30 GS 10
EAX: 00000000 EBX: 80d6b730 ECX: 00000025
EDX: 00000094 EBP: 800f0574 ESI: 80d685a8 ESP: 800f04fc
EDI: cccccccc EFLAGS: 00210212 kESP 800f04fc kernel stack base 800ee000
Frames:
<ntoskrnl.exe:93345 (mem.c:98 (RtlFillMemory))>
<ntoskrnl.exe:933de (mem.c:168 (RtlZeroMemory))>
<ntoskrnl.exe:48d94 (io/irp.c:1357 (IoInitializeIrp))>
<ntoskrnl.exe:47e4c (io/irp.c:450 (IoAllocateIrp))>
<ntoskrnl.exe:48199 (io/irp.c:643 (IoBuildDeviceIoControlRequest))>
<scsiport.sys:3071 (scsiport.c:1948 (SpiSendInquiry))>
<scsiport.sys:3448 (scsiport.c:2098 (SpiScanAdapter))>
<scsiport.sys:216f (scsiport.c:1118 (ScsiPortInitialize))>
<fireport.sys:736>
<ntoskrnl.exe:3ef6e (io/driver.c:563 (IopInitializeDriverModule))>
<800AAFCC>
<ntoskrnl.exe:3f8ea (io/driver.c:1267 (IopInitializeBootDrivers))>
<800AB926>
<800A915A>
<ntoskrnl.exe:10544 (ke/main.c:103 (KiSystemStartup))>
<800A77AA>
<0>
I readed somewhere in Internet thats is any way to run CygWin
applications like bash on WinE. How can I do it?
And what doesn't reactos have that's needed to run cygwin on ReactOS?
Hi all
Some feedback from Eugenia of osnews.com.
Cheers
Jason
---------- Forwarded message ----------
From: Eugenia Loli-Queru <eloli(a)hotmail.com>
Date: May 2, 2005 7:02 AM
Subject: reactos
To: jason.filby(a)gmail.com
I just downloaded the latest reactos and tried it with qemu 0.7. Some
points:
1. Most of the panels don't fit on VGA screens and so I can't apply
settings. It would be wise to design them as VGA-friendly.
2. I can't change the resolution and it seems you don't support qemu's
network adapter either?
3. Please provide some apps with the emulated OS (adding 10 more MBs is not
a big deal). I can't download anything atm as I don't have a browser or
internet access inside reactos and this limits my experience with it.
thx,
Eugenia
I just spent most of an hour resolving merge conflicts,
mostly due to our use of keywords. I think my time could
have been better spent on improving the build system.
Can we please avoid using keywords unless the information
needs to be compiled into ReactOS?
Casper
Steven Edwards wrote:
>
> The problem is that while Reiser4 is very extendable and and supports a
nice plugin API there is
> no reiser driver for Windows that we can use. There is already a ext2fsd
(3 of them actually) and
> we can extend it to support ext3 with very little work.
As a requirement of anything other than vfat is still quite some time in the
future, is it not worth contacting the Reiser team to see if we rally them
to build a Windows driver?
By the time we need to implement functionality which vfat can't support,
they may have been able to put something together.
If you don't ask, you don't get :)
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 Rick,
--- Rick Langschultz <rlangschultz(a)cox.net> wrote:
> If people want to implement NTFS so badly why not use something like
> ReiserFS4 for the actual fs, but write a VFS driver to be loaded to act like
> NTFS. Since ReiserFS supports permissions and things of that nature it
> should be interesting to see the result. Filesystem encryption could
> possibly be implemented for files or folders too.
The problem is that while Reiser4 is very extendable and and supports a nice plugin API there is
no reiser driver for Windows that we can use. There is already a ext2fsd (3 of them actually) and
we can extend it to support ext3 with very little work.
Thanks
Steven
Yahoo! Mail
Stay connected, organized, and protected. Take the tour:
http://tour.mail.yahoo.com/mailtour.html
Hi,
--- Phillip Susi <psusi(a)cfl.rr.com> wrote:
> How would you reconcile the two different sets of owner and access
> information associated with the file? For instance, if someone creates
> a file on the partition from Linux, then you mount it with ROS, who owns
> the file? Who has access to it? Linux would only place some
> meaningless uid and chmod mask in the inode, so how would ROS come up
> with a sensible security descriptor for the file when one does not
> already exist?
Windows would have this same problem with NTFS on Linux. If I am under Linux and make changes to
files and create files how does linux-NTFS assign the proper SID and such to the files? This has
been a long time problem that NTFS has with taking a drive from one Windows box to another. Its
the same situation and mostly pointless. 99% of new ReactOS are not going to care and the
resources we get from having a better filesystem now can be put in to developing a NTFS
replacement.
> These are the kinds of problems that make attempts for ReactOS to share
> a unix filesystem ( and vice versa ) kludgey at best.
If the ext2fsd supported ext3 journals there would be nothing wrong with using it. I mean hell
right now ReactOS does not have a security subsystem so this whole discussion is a moot point.
Unless you feel like implementing lsass =)
Thanks
Steven
Discover Yahoo!
Find restaurants, movies, travel and more fun for the weekend. Check it out!
http://discover.yahoo.com/weekend.html
