---------- Initial Header -----------
>From : ros-general-bounces(a)reactos.com
To : ros-general(a)reactos.com
Cc :
Date : Fri, 27 Feb 2004 13:05:33 +0100
Subject : [ros-general] filesystems / links / file types
> hi,
>
> Which filesystems will reactOS support?
> The current version just understands FAT, somewhere I read you plan NTFS.
>
> but, why?
Supporting is not a "why" question, but a "what" question.
> wouldn't it be much better to use ext2/ext3 or similar?
There are GPL'd drivers for ext2/3 on the net ("what").
> the links...
> one serious drawback of windows is the lack of "real" links.
I used hard links since NT 4.0. And symlinks since NT 5.0 (2000). You just need a NTFS logical volume and a pair of utilities MS does not distributes...
> ever tried to use links as if they were the real files?
> it simple does not work most of the times. this really is annoying.
These are probably *.lnk files, which are serialized references used internally by explorer.exe. Why should they work?
ea
hi,
Which filesystems will reactOS support?
The current version just understands FAT, somewhere I read you plan NTFS.
but, why?
wouldn't it be much better to use ext2/ext3 or similar?
Pro
- ext2 is well documented
- free drivers
- stable, not subject to continuos change like NTFS
- apps should not care about the underlying FS
- simple and reliable rights management
- links (see below)
- interaction with linux systems should be much easier
Contra
- cannot be read by NT
One is not required to use ext2 for all ReactOS partitions. probably
only for system partition....
- disk maintainace apps will not work.
but they will not work on ReactOS at all in the near future, will they?
the links...
one serious drawback of windows is the lack of "real" links.
ever tried to use links as if they were the real files?
it simple does not work most of the times. this really is annoying.
what ever filesystem chosen, these links should be implemented on top of
it.
problem is, the "on top impl" is the cause, why windows links do not
work. so this must be implemented within the file system, which will
probably violate the filesystem spec.
(perhaps some reserved fields are left, eh?)
best way to implement would be, to introduce a file type field within
the filesystem.
with this, the old and very bad way of using file extensions may be
overcome...
think about mime types, or app identifier....
enough ideas to discuss?
Jan
Hi,
the subject says enough for those not concerned, so excuse me for
continueing in german.
Über das web komm ich nicht so recht in das Projekt rein. Würde mir
jemand mal persönlich die interna zeigen?
ich wohne im Rhein-Main gebiet.
irgendwo zwischen Frankfurt und Darmstadt würde mir gefallen....
vielleicht jemand, der auch visionen hat. ich würde mich da gerne mal austauschen.
:-)
tschau
Jan
hi!
first you have to start the boot.bat file. After this progress you
can retry C:\REACTOS>aboot
> -----Ursprüngliche Nachricht-----
> Von: theUser BL [SMTP:theuserbl@hotmail.com]
> Gesendet am: Freitag, 27. Februar 2004 09:43
> An: ros-general(a)reactos.com
> Betreff: [ros-general] The booting stops without error-message
>
> Hi!
>
> Yesterday I wanted to try ReactOS on my computer. I downloaded the
> 0.2.0-binaries and started aboot:
>
> --------------------------------------
>
> Microsoft(R) Windows98
> (C)Copyright Microsoft Corp 1981-1999.
>
> C:\>cd reactos
>
> C:\REACTOS>aboot
>
> C:\REACTOS>loadros system32\ntoskrnl.exe system32\hal.dll
> system32\drivers\acpi.
> sys /DEBUGPORT=SCREEN bootc.lst
> Loading: system32\ntoskrnl.exe ..................
> Loading: system32\hal.dll ...
> Loading: system32\drivers\acpi.sys ........
> Loading: bootc.lst .Loading: system32\drivers\pci.sys .
> Loading: system32\drivers\scsiport.sys ..
> Loading: system32\drivers\atapi.sys ..
> Loading: system32\drivers\class2.sys ..
> Loading: system32\drivers\disk.sys ..
> Loading: system32\drivers\vfatfs.sys ...
> Loading: system32\drivers\ndis.sys ......
> Loading: system32\config\system ..
> Loading: system32\ansi.nls ...
> Loading: system32\oem.nls ...
> Loading: system32\casemap.nls .
> _
> --------------------------------------
> (the "_" is the actual cursor-position)
>
>
> After that, the system hangs up. It is possible to reboot with
> [Ctrl]+[Alt]+[del], but you cant abort. And there don't stand any
> error-message.
>
> I don't know, _why_ it hangs up. Is it possible, that it can't read the
> Win98SE-filesystem?
> But why doesn't stand there an error-message?
>
>
> Greatings
> theuserbl
>
> _________________________________________________________________
> Die ultimative Fan-Seite für den MSN Messenger
> http://www.ilovemessenger.de
> Emoticons und Hintergründe kostenlos downloaden!
>
> _______________________________________________
> ros-general mailing list
> ros-general(a)reactos.com
> http://reactos.com/mailman/listinfo/ros-general
Hi!
Yesterday I wanted to try ReactOS on my computer. I downloaded the
0.2.0-binaries and started aboot:
--------------------------------------
Microsoft(R) Windows98
(C)Copyright Microsoft Corp 1981-1999.
C:\>cd reactos
C:\REACTOS>aboot
C:\REACTOS>loadros system32\ntoskrnl.exe system32\hal.dll
system32\drivers\acpi.
sys /DEBUGPORT=SCREEN bootc.lst
Loading: system32\ntoskrnl.exe ..................
Loading: system32\hal.dll ...
Loading: system32\drivers\acpi.sys ........
Loading: bootc.lst .Loading: system32\drivers\pci.sys .
Loading: system32\drivers\scsiport.sys ..
Loading: system32\drivers\atapi.sys ..
Loading: system32\drivers\class2.sys ..
Loading: system32\drivers\disk.sys ..
Loading: system32\drivers\vfatfs.sys ...
Loading: system32\drivers\ndis.sys ......
Loading: system32\config\system ..
Loading: system32\ansi.nls ...
Loading: system32\oem.nls ...
Loading: system32\casemap.nls .
_
--------------------------------------
(the "_" is the actual cursor-position)
After that, the system hangs up. It is possible to reboot with
[Ctrl]+[Alt]+[del], but you cant abort. And there don't stand any
error-message.
I don't know, _why_ it hangs up. Is it possible, that it can't read the
Win98SE-filesystem?
But why doesn't stand there an error-message?
Greatings
theuserbl
_________________________________________________________________
Die ultimative Fan-Seite für den MSN Messenger http://www.ilovemessenger.de
Emoticons und Hintergründe kostenlos downloaden!
Hmmm.. I can only test it later, because here I have an internet-connection,
but I can not test reactos. And later at home, I can test reactos, but
doesn't have internet-connection.
> first you have to start the boot.bat file. After this progress you
>can retry C:\REACTOS>aboot
Are you sure?
I have looked at first in the bat-files.
aboot.bat have:
loadros system32\ntoskrnl.exe system32\hal.dll system32\drivers\acpi.sys
/DEBUGPORT=SCREEN bootc.lst
rem comment added and changed for no reason
and boot.bat have:
loadros system32\ntoskrnl.exe system32\hal.dll /DEBUGPORT=BOCHS bootc.lst
So, aboot load one driver more (acpi.sys) and the debugport is the screen
and not bochs.
And because my computer is too slow for bochs, I run it direct on my
computer. So I think, that aboot makes more sense. :-/
For me it looks that boot and aboot are the same. boot for the virtual
machine and aboot for the real computer.
But if you think it's better to use boot, I will test it later at home with
it.
Greatings
theuserbl
_________________________________________________________________
MSN Messenger - sehen, welche Freunde online sind!
http://www.msn.de/messenger Jetzt kostenlos downloaden und mitmachen!
Here are two interesting links for including DOS-Support in ReactOS:
An free 32bit DOS. From there it is possible to use DOS-programs like "type"
and so.
http://freedos-32.sourceforge.net/
And here a DosBOX, which run 16bit DOS-Programs on different
OperatingSystems and different Hardware. Their code can be usefull for
ReactOS I think:
http://dosbox.sourceforge.net/news.php?show_news=1
Greatings
theuserbl
_________________________________________________________________
MSN Messenger - sehen, welche Freunde online sind!
http://www.msn.de/messenger Jetzt kostenlos downloaden und mitmachen!
Hi!
I have now send the following mail to the FSF (gnu(a)gnu.org) with the subject
"legality of using closed-source programs with completly GPLd ReactOS".
Greatings
theuserbl
Here the mail:
>Hi!
>
>There existing a project, which want to rewrite MS-Windows NT, which is
>called ReactOS.
>You can see the home of the project at http://www.reactos.com/
>
>The idea is, to have an OS, which can run all MS-Windows NT programs, which
>can make use of > all the drivers, which exists for WinNT and so on.
>
>But the problem is, that the complete OS is under the GPL.
>
>The people behind the ReactOS-project don't see a problem in using
>closed-source
>programs/libraries/drivers on top of their OS.
>
>But what do _you_ think about it?
>
>I have now mentioned the problem ob their mailingliste at
>http://reactos.com:8080/archives/public/ros-general/2004-February/000736.ht…
>
>But I think, it would be nice, to here a comment of licensing-competent
>people. So, what do _you_ > think about this?
>
>Greatings
>theuserbl
_________________________________________________________________
E-Mails sind zu unpersönlich? Mit einer Webcam wird der MSN Messenger zum
Bildtelefon! http://www.msn.de/messenger Jetzt kostenlos downloaden und
mitmachen!
hi,
yesterday I read the first time about ReactOS. Probably it exactly is,
what I am dreaming about for years.
Small, stable, easy to use. and compatible to windows.... GREAT
I did not read the whole list archies yet, so please be patient, if my
ideas are old ones ;-)
Since I do not understand C (in fact I hate c/cpp) some very odd
suggestions are, to use very current technologies like
- XML
- a progamming language that is cool (probably no one exists yet)
so, for now it seems to be best to stay with c/cpp. :-(
that means to me it does not make sense to help in kernel development.
A part that I could imagine is, finding software that is "cool" and
assigning "certificates" to this software.
ok, it seems a little bit early compared to reactOS state... but, let us
think about it.
A great problem on windows at the time is,
there are millions of software projects, free or commercial, that one
can easily find to be very bad in software architecture and/or GUI
design.
Now if reactOS gets more mighty on the OS market, it could be an
instance that labels good software and thus forces software development
to raise in quality.
different labels to give:
"reactOS compatible", "easy to use", "poweruser software", "absolutly
stable"...
It took me years to find some great software and I think I can name some
applications that will fit, and some that will never. ;-)
later, reactOS could use these certificates to obtain money from
commercial software developers, as M$ does with its driver certificates.
"reactOS certified" ;-)
what do you think?
bye
Jan
