where are reiser4 sources

where are reiser4 sources

[Mark Junker]

Hi,

where are the Reiser4 sources? I just want to use Reiser4 in a separate 
application and don't like the idea of extracting the sources from the 
linux 2.6 patch.

Regards,
Mark

Re: where are reiser4 sources

[Sander Sweers]

I have been using the tarball from ftp://ftp.namesys.com/pub/reiser4-for-2.6/.
Have not had any problems with this but I do not know how up to date it is.

Sander

On Mon, 21 Feb 2005 17:16:47 +0100, Mark Junker <mjscod@gmx.de> wrote:
> Hi,
> 
> where are the Reiser4 sources? I just want to use Reiser4 in a separate
> application and don't like the idea of extracting the sources from the
> linux 2.6 patch.
> 
> Regards,
> Mark
> 
> 


-- 
After a time, you may find that "having" is not so pleasing a thing,
after all, as "wanting." It is not logical, but it is often true.

Spock, "Amok Time"
stardate 3372.7

Re: where are reiser4 sources

[Mark Junker]

Sander Sweers schrieb:

>I have been using the tarball from ftp://ftp.namesys.com/pub/reiser4-for-2.6/.
>Have not had any problems with this but I do not know how up to date it is.
>  
>
I already found this but I just wanted to download the version *not* 
consisting of just the linux kernel patches. Just the plain sources.

Regards,
Mark

Re: where are reiser4 sources

[David Masover]

Mark Junker wrote:
> Hi,
> 
> where are the Reiser4 sources? I just want to use Reiser4 in a separate 
> application and don't like the idea of extracting the sources from the 
> linux 2.6 patch.

Out of curiosity, why?

$ cd linux-2.6
$ patch [...]
$ cp -a fs/reiser4 ..
$ cd ..
$ rm -rf linux-2.6

Or, I think there may be instructions somewhere for how to get that tree
from BitKeeper.

AFAIK, you will still have to adapt it a good deal.  There has been some
(minimal) discussion of porting, but it doesn't seem easy.

Re: where are reiser4 sources

[Mark Junker]

David Masover schrieb:

> $ cd linux-2.6
> $ patch [...]
> $ cp -a fs/reiser4 ..
> $ cd ..
> $ rm -rf linux-2.6

It seems that I have to download the linux 2.6 kernel sources ...

> AFAIK, you will still have to adapt it a good deal.  There has been some
> (minimal) discussion of porting, but it doesn't seem easy.

Yes, I want to port it to another OS (ReactOS / WinXP).

Regards,
Mark

Re: where are reiser4 sources

[Hans Reiser]

How are you using reiser4 without the kernel?

Hans

David Masover wrote:

> Mark Junker wrote:
>
>> Hi,
>>
>> where are the Reiser4 sources? I just want to use Reiser4 in a 
>> separate application and don't like the idea of extracting the 
>> sources from the linux 2.6 patch.
>
>
> Out of curiosity, why?
>
> $ cd linux-2.6
> $ patch [...]
> $ cp -a fs/reiser4 ..
> $ cd ..
> $ rm -rf linux-2.6
>
> Or, I think there may be instructions somewhere for how to get that tree
> from BitKeeper.
>
> AFAIK, you will still have to adapt it a good deal.  There has been some
> (minimal) discussion of porting, but it doesn't seem easy.
>
>
>

Re: where are reiser4 sources

[Mark Junker]

Hans Reiser schrieb:

> How are you using reiser4 without the kernel?

First, I want to develop a separate application to test the Reiser4 FS, 
then I'll try to develop a Win2K/XP FS driver (incl. ReactOS). Therefore 
it'd be very useful if Reiser4 can be compiled as a separate library 
including a usable API documentation *g*.

Regards,
Mark

Re: where are reiser4 sources

[Hans Reiser]

Mark Junker wrote:

> David Masover schrieb:
>
>> $ cd linux-2.6
>> $ patch [...]
>> $ cp -a fs/reiser4 ..
>> $ cd ..
>> $ rm -rf linux-2.6
>
>
> It seems that I have to download the linux 2.6 kernel sources ...
>
>> AFAIK, you will still have to adapt it a good deal.  There has been some
>> (minimal) discussion of porting, but it doesn't seem easy.
>
>
> Yes, I want to port it to another OS (ReactOS / WinXP).
>
> Regards,
> Mark
>
>
>
That violates the license.

Hans

Re: where are reiser4 sources

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 248 bytes --]

On Tue, 22 Feb 2005 10:41:25 PST, Hans Reiser said:

> That violates the license.

Umm.. from fs/reiser4/README:

Reiser4 is hereby licensed under the GNU General
Public License version 2.

Where in the GPL does it say he can't port to another OS?

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: where are reiser4 sources

[Mark Junker]

Hans Reiser schrieb:

> That violates the license.

GPL? This shouldn't be a problem because the sources aren't statically 
linked to Windows. The sources to create the driver can be published 
under GPL too so this shouldn't be a problem.

Where do you see the license violation?

Regards,
Mark

Re: where are reiser4 sources

[Lehmann]

> >Yes, I want to port it to another OS (ReactOS / WinXP).
> >
> That violates the license.

The code in the kernel clearly states that reiserfs is GPLed, which of
course allows porting it to reactos or winxp.

If you disagree, then now is the time to disclose the real license you
think the code is under, as it is not good if the code claims to be GPLed
when in fact it is not.

(If you want to put extra restrictions on the GPL, the code is no longer
GPL, and so *must* go out of the kernel *quickly*).

-- 
                The choice of a
      -----==-     _GNU_
      ----==-- _       generation     Marc Lehmann
      ---==---(_)__  __ ____  __      pcg@goof.com
      --==---/ / _ \/ // /\ \/ /      http://schmorp.de/
      -=====/_/_//_/\_,_/ /_/\_\      XX11-RIPE

Re: where are reiser4 sources

[Hans Reiser]

Valdis.Kletnieks@vt.edu wrote:

>On Tue, 22 Feb 2005 10:41:25 PST, Hans Reiser said:
>
>  
>
>>That violates the license.
>>    
>>
>
>Umm.. from fs/reiser4/README:
>
>Reiser4 is hereby licensed under the GNU General
>Public License version 2.
>
>Where in the GPL does it say he can't port to another OS?
>  
>
He can port it to a GPL OS, not a proprietary OS.

Re: where are reiser4 sources

[Hans Reiser]

Mark Junker wrote:

> Hans Reiser schrieb:
>
>> That violates the license.
>
>
> GPL? This shouldn't be a problem because the sources aren't statically 
> linked to Windows. The sources to create the driver can be published 
> under GPL too so this shouldn't be a problem.
>
> Where do you see the license violation?
>
> Regards,
> Mark
>
>
>
The GPL says nothing about static linking.  You are making a derivative 
work.  No. 

Please contact my IP lawyer at brooke@artemama.com, and she will explain 
the penalties for violating copyright law.

Hans Reiser

Re: where are reiser4 sources

[Mark Junker]

Hans Reiser schrieb:

> The GPL says nothing about static linking.  You are making a 
> derivative work.  No.

Is it also forbidden to create a driver for a proprietary OS even when I 
put the driver source under the GPL?

> Please contact my IP lawyer at brooke@artemama.com, and she will 
> explain the penalties for violating copyright law.

Oh, please don't be so rude. I didn't start the development yet.

Regards,
Mark

Re: where are reiser4 sources

[Rudy Zijlstra]

There is another issue here as well.

Have you checked the Windows licenses (or rather the needed windows
development kits) and what they allow you to do? If i remember correctly
you run into problems there as well...

If i remember correctly to interface with windows you have to include some
SW from MS which is most definitly not GPL, and the license on those
portions forbid using it with GPL SW.

And this works from the GPL as well, because you cannot distribute the
relevant windows code (i do not think you even have the source), you
cannot distribute the complete set under GPL.

I am open to be corrected here, but this is my understanding.

Cheers,

Rudy

On Wed, 23 Feb 2005, Mark Junker wrote:

> Hans Reiser schrieb:
>
> > The GPL says nothing about static linking.  You are making a
> > derivative work.  No.
>
> Is it also forbidden to create a driver for a proprietary OS even when I
> put the driver source under the GPL?
>
> > Please contact my IP lawyer at brooke@artemama.com, and she will
> > explain the penalties for violating copyright law.
>
> Oh, please don't be so rude. I didn't start the development yet.
>
> Regards,
> Mark
>
>
>

Re: where are reiser4 sources

[Hans Reiser]

Rudy Zijlstra wrote:

>There is another issue here as well.
>
>Have you checked the Windows licenses (or rather the needed windows
>development kits) and what they allow you to do? If i remember correctly
>you run into problems there as well...
>
>If i remember correctly to interface with windows you have to include some
>SW from MS which is most definitly not GPL, and the license on those
>portions forbid using it with GPL SW.
>
>And this works from the GPL as well, because you cannot distribute the
>relevant windows code (i do not think you even have the source), you
>cannot distribute the complete set under GPL.
>
>I am open to be corrected here, but this is my understanding.
>
>Cheers,
>
>Rudy
>
>On Wed, 23 Feb 2005, Mark Junker wrote:
>
>  
>
>>Hans Reiser schrieb:
>>
>>    
>>
>>>The GPL says nothing about static linking.  You are making a
>>>derivative work.  No.
>>>      
>>>
>>Is it also forbidden to create a driver for a proprietary OS even when I
>>put the driver source under the GPL?
>>
>>    
>>
>>>Please contact my IP lawyer at brooke@artemama.com, and she will
>>>explain the penalties for violating copyright law.
>>>      
>>>
>>Oh, please don't be so rude. I didn't start the development yet.
>>
>>Regards,
>>Mark
>>
>>
>>
>>    
>>
>
>
>  
>
Thanks Rudy.  If MS wants Reiser4, they can damn well pay me a license 
fee for it.

Mounting ReiserFS 3.6 RO increments journal count ?

[Linux Tard]

I'm curious about a scenario I've been seeing and
working with.

My goal is to mount a ReiserFS-formatted filesystem
read only, truly read only, such that nothing is
updated (including metadata such as journal count).

Test bed is this;
- authenticate ReiserFS filesystem using 'md5sum'
- mount ReiserFS filesystem read only
- unmount 
- re-authenticate using 'md5um'.

Both sums should match.  But using 'mount' and and
options;
mount /dev/sda4 -o ro,nolog /mnt/here

FAILS.  It is read only.  But upon unmount the md5sum
no longer matches.  It appears the journal count is
incremented still even though it's mounted read only?

Is this true?

I've found two workarounds;
1) In /usr/src/kernel_version/fs/reiserfs I change the
'journal.c' file such that;

<ORIGINAL CODE>
/* j_start does not get set correctly if we don't
replay any transactions.
  ** if we had a valid journal_header, set j_start to
the first unflushed transaction value,
  ** copy the trans_id from the header
  */
  if (valid_journal_header && replay_count == 0) { 
    SB_JOURNAL(p_s_sb)->j_start =
le32_to_cpu(jh->j_first_unflushed_offset) ;
    SB_JOURNAL(p_s_sb)->j_trans_id =
le32_to_cpu(jh->j_last_flush_trans_id) + 1;
    SB_JOURNAL(p_s_sb)->j_last_flush_trans_id =
le32_to_cpu(jh->j_last_flush_trans_id) ;
    SB_JOURNAL(p_s_sb)->j_mount_id =
le32_to_cpu(jh->j_mount_id) + 1;
  } else {
    SB_JOURNAL(p_s_sb)->j_mount_id = newest_mount_id +
1 ;
</ORIGINAL CODE>


My changes made were;

SB_JOURNAL(p_s_sb)->j_mount_id =
le32_to_cpu(jh->j_mount_id) + 0;
  } else {
    SB_JOURNAL(p_s_sb)->j_mount_id = newest_mount_id +
0 ;

(Setting to '0' instead of '1').

Now when I when mount using;
mount -o ro,nolog /dev/sda4 /mnt/here

and then unmount the hash values (prior to mounting
and after mounting) equal one another.  

But, I feel this is bad.  Why I must have it not
change is for preview only, pure read only mode.  


The other option that works is;

md5sum /dev/sda4
losetup /dev/loopXXX /dev/sda4
mount -o ro,nolog /dev/loopXXX /mnt/here
umount /mnt/here
losetup -d /dev/loopXXX
md5sum /dev/sda4


Which of these two is the lesser of two evils?  Why
must the journal be incremented even when FS is
mounted read only?  

I've combed archives but haven't seen mention of it
yet? I've asked professor at school and he is not sure
why going through loop works (no change in filesystem
so hash matches) but not normal mount manner.

kind regards,
-lt


		
__________________________________ 
Do you Yahoo!? 
Read only the mail you want - Yahoo! Mail SpamGuard. 
http://promotions.yahoo.com/new_mail 

Re: where are reiser4 sources

[Mark Junker]

Rudy Zijlstra schrieb:

>There is another issue here as well.
>
>Have you checked the Windows licenses (or rather the needed windows
>development kits) and what they allow you to do? If i remember correctly
>you run into problems there as well...
>
>If i remember correctly to interface with windows you have to include some
>SW from MS which is most definitly not GPL, and the license on those
>portions forbid using it with GPL SW.
>  
>
I wouldn't compile against M$ headers and libraries. I would use the 
ones from ReactOS instead.

>And this works from the GPL as well, because you cannot distribute the
>relevant windows code (i do not think you even have the source), you
>cannot distribute the complete set under GPL.
>  
>
This sounds to me that I can only use GPL'd software with other GPL'd 
software but this cannot be true because you're allowed to use it with 
libraries with other licenses too as long as they don't contain 
conflicts ...

>I am open to be corrected here, but this is my understanding.
>  
>
Yes, I know it's a quite difficult area and I'm unsure what's the right 
understanding ...

Regards,
Mark

Re: where are reiser4 sources

[Mark Junker]

Hans Reiser schrieb:

> Thanks Rudy.  If MS wants Reiser4, they can damn well pay me a license 
> fee for it.

I'm not M$ and I don't work for them. I was just asking because I wanted 
to implement Reiser4 for ReactOS. Because it's compatible to the M$ 
Windows WDM, I'd assume that it will work on Win2K/XP too.

Regards,
Mark

Re: where are reiser4 sources

[Mark Junker]

Rudy Zijlstra schrieb:

>Have you checked the Windows licenses (or rather the needed windows
>development kits) and what they allow you to do? If i remember correctly
>you run into problems there as well...
>  
>
Just to let you know: The ReactOS license it GPL too. Everything's clear 
now? May I now use the Reiser4 sources to develop a driver for ReactOS?

Regards,
Mark

Re: where are reiser4 sources

[Jonathan Briggs]

[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]

On Wed, 2005-02-23 at 09:19 -0800, Hans Reiser wrote:
> Mark Junker wrote:
> 
> > Hans Reiser schrieb:
> >
> >> That violates the license.
> >
> >
> > GPL? This shouldn't be a problem because the sources aren't statically 
> > linked to Windows. The sources to create the driver can be published 
> > under GPL too so this shouldn't be a problem.
> >
> > Where do you see the license violation?
> >
> > Regards,
> > Mark
> >
> >
> >
> The GPL says nothing about static linking.  You are making a derivative 
> work.  No. 

I don't think that's right, Hans.  If his linking code is also GPL, the
GPL of the filesystem code is satisfied.  The only problem would be from
the Windows licensing rejecting GPL'd driver code, which I think it
does.

The dynamic linking problems can be got around by writing an
implementation that links dynamically against something else that is
okay under GPL.  If that code also happens to link dynamically against
non-GPL code, that is the end-user's problem.  So if there was, say, a
Linux or BSD implementation of a Windows driver interface like
NDISwrapper for filesystems, he could legally write against _that_.

Once there's a documented interface and more than one implementation,
implementing that interface no longer becomes a derived work.

In any case, he could always write a FUSE-like driver that thunked
filesystem calls in and out of a service.
-- 
Jonathan Briggs <jbriggs@esoft.com>
eSoft, Inc.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: where are reiser4 sources

[David Masover]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hans Reiser wrote:
| Mark Junker wrote:
|
|> Hans Reiser schrieb:
|>
|>> That violates the license.
|>
|>
|>
|> GPL? This shouldn't be a problem because the sources aren't statically
|> linked to Windows. The sources to create the driver can be published
|> under GPL too so this shouldn't be a problem.
|>
|> Where do you see the license violation?
|>
|> Regards,
|> Mark
|>
|>
|>
| The GPL says nothing about static linking.  You are making a derivative
| work.  No.

Excuse me, your mail client is communicating with mine.  Mine is under
DJB's license, which forbids derivative works which are distributed as
anything other than patches to the original.

Now, chances are that your mail client isn't using the same license
(which is forbidden), and I really doubt it's distributed as patches to
qmail.  Yet, by your definition, it communicates with my server, which
makes it a "derivative work".

If you don't like what people are doing with your software, you should
have chosen another license.  I don't think a Windows driver is any more
a part of Windows than Wine is, if done properly.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQh0mnHgHNmZLgCUhAQIPiw/+IDTJnIZsGBowcXD0bLwoKm2ajvY7GPyx
jJN3yW8/K1DYDVypeddv1RSnsWsnafzbeVtM797eWJ8RJb3nDQqOd6UzxpqtAu3R
jDkkyg12j4gf7/edPAvg8bd3tQ/ZIBEK3/cNS1MxVz+LuWb/gOKMqsNfcPMgmS66
Vus40awC0z6TVrLHvakh91ni3+o4DQW3CGLnWJDugNZxWqs5K10SaEusGw8brUY7
XsomZAycACrDep0FgQp/ywfMdn8fvB1Z0JTtXMiD8F7pbJjDu8tWbr1X6omlZQwp
6FH6QH8C/JbxvJ8rKQEHRO+RHAhandCWdR9ZNntsQj90xa1g7m4KSMtB/VwPacp3
zc3cF5aCE5r0HyBsM8/H8gbResRu1FOHqUMzD2SpJ3gUO2QWvty119vL+eXqaDa4
OGzeFPUJ28jmWOz3FFGXaMFI2410Hlb1L6MpetPz0vgt+WkxTK5taiOx/So5y0fb
DL3zJd0WOZi9c1pyF7sQKCmesQzvM0wQdQEYEUhUExdbenKp+MPIbFminZHfZ1Tq
4nODQjdmwfsgCbfLD1I0OvC/4zqvUtXjFObD/sUADae38FVmgUU9zAn6/fgkKCUP
oLcbGiTinLz4lC60HEWlHiJi7+Y7ODguC7lPRS9wPbn0MQe3MfLXpbqa0MiYdTh6
7RVJ2DuOWOc=
=UCTg
-----END PGP SIGNATURE-----

Re: where are reiser4 sources

[Rudy Zijlstra]

Mark Junker wrote:

> Rudy Zijlstra schrieb:
>
>>
> This sounds to me that I can only use GPL'd software with other GPL'd 
> software but this cannot be true because you're allowed to use it with 
> libraries with other licenses too as long as they don't contain 
> conflicts ...
>
Take a look at the difference between GPL and LGPL. LGPL allows dynamic 
linking against non GPL SW, GPL does not. Both allow usage of the 
interfaces *without* linking, either dynamic or static. Neither allow 
static linking to non (L)GPL.

Rudy

Re: where are reiser4 sources

[David Masover]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rudy Zijlstra wrote:
| Mark Junker wrote:
|
|> Rudy Zijlstra schrieb:
|>
|>>
|> This sounds to me that I can only use GPL'd software with other GPL'd
|> software but this cannot be true because you're allowed to use it with
|> libraries with other licenses too as long as they don't contain
|> conflicts ...
|>
| Take a look at the difference between GPL and LGPL. LGPL allows dynamic
| linking against non GPL SW, GPL does not. Both allow usage of the
| interfaces *without* linking, either dynamic or static. Neither allow
| static linking to non (L)GPL.

Come to think of it, isn't that kind of how nvidia can put a binary
driver in Linux?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQh6q2HgHNmZLgCUhAQLPQhAAkbyHLLoW/WHsH6N5aEIZ7EPNz6YC4mme
Uli/UOzSStwjwcB5B071IC8hk5OQnjSbBbpv/IGVmoio2/f4ritCavcP3aJzi00A
JD744eAUDs4CJBnAAkU3VylY82fkSqz7Wp5PprTaJBPx6gX3lbWqxeeq3sX/bDk0
l9TxczUh7aM+AR9CRrk8upik/XFUaekokAe58ZmeEXQ8eC9hvFfkJUg9iDsVBi0a
ZXf1ne5yukrBetfN10+xE9sIvFRHnnX0u156RmMx+nNwAtdo1JEhhJl+/s94MbIy
tAwSC0NiVkVqL1PTiCEnIx4luJrkOreFNnnXCKUzsQNA9fX7WhgmJ7UBW+0TUP9L
f2sga67VpnJjgb5M1mscfCS5VrwUzVy/i+qeHZlGJt2XXLLJXKjavyaiB2FIYTKB
iIiT+OYQNj2MDxerQ+ar9xC8xhPwzvlbrIBa/mRUjcuoP0gOKXIpAN3MdUMVio4t
qvIswayQheyZ1FBN0VFbuG5LVR721WfRc6bDdZXR8qGaagiQAxI6XBpo6TK3CcwI
T8UBqKldXSs7I+nGw4ozzaWLSYSD6T7tAhctv2vc5NiC5LAi5lTWHHFJcA1MyyrP
fwcs18QCy92+I+fTxathWe63kOW1xCooppNTPyPeQg6wNyOhe4oTDhG47TBLLYo9
XwGMXxFE20M=
=B41A
-----END PGP SIGNATURE-----

Re: where are reiser4 sources

[Chester R. Hosey]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Masover wrote:
| Rudy Zijlstra wrote:
| | Mark Junker wrote:
| |
| |> Rudy Zijlstra schrieb:
| |>
| |>>
| |> This sounds to me that I can only use GPL'd software with other GPL'd
| |> software but this cannot be true because you're allowed to use it with
| |> libraries with other licenses too as long as they don't contain
| |> conflicts ...
| |>
| | Take a look at the difference between GPL and LGPL. LGPL allows dynamic
| | linking against non GPL SW, GPL does not. Both allow usage of the
| | interfaces *without* linking, either dynamic or static. Neither allow
| | static linking to non (L)GPL.
|
| Come to think of it, isn't that kind of how nvidia can put a binary
| driver in Linux?

The relevant clause states that "If identifiable sections of that work
are not derived from the Program, and can be reasonably considered
independent and separate works in themselves, then this License, and its
terms, do not apply to those sections when you distribute them as
separate works."

The question is whether a module which uses a published API to interface
with other code can reasonably be considered independent of the original
work.

One could probably argue that in the case of ReiserFS and Windows, the
original Windows code is an "identifiable section [...] and can be
reasonably considered independent and separate", and thus does is not a
derived work.

Following this line of thinking, under GPL terms one could modify
ReiserFS in such a way that the code could interface with Windows via
the defined API, and they could redistribute those modifications under
the GPL as long as the modified ReiserFS code is distributed separately
from Windows itself.

"But when you distribute the same sections as part of a whole which is a
work based on the Program, the distribution of the whole must be on the
terms [of the GPL]". This would explain why binary-only drivers aren't
generally distributed with the Linux kernel itself -- the GPL seems to
explicitly forbid it, with the exception that they may reside on the
same media.

This would also seem to indicate that if Microsoft wanted to include
ReiserFS as a part of Windows they would either have to GPL Windows
itself or strike a deal with Hans Reiser. Actually, the same would be
true for Apple, or any publisher of a non-GPL operating system.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCHt/RrDBoMHxfhXwRAo86AJ9pEfw9EQXhH3RO7TRaqbWj4MdSBQCg1S3O
8dbzE9AzEbmnZrq/kHwJOkc=
=kKdo
-----END PGP SIGNATURE-----

Re: where are reiser4 sources

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 165 bytes --]

On Mon, 28 Feb 2005 15:41:52 PST, Hans Reiser said:

> I am frankly skeptical that one should attempt to clone windows.

That explains why WINE exists, I guess.. ;)

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: where are reiser4 sources

[Hans Reiser]

Mark Junker wrote:

> Rudy Zijlstra schrieb:
>
>> Have you checked the Windows licenses (or rather the needed windows
>> development kits) and what they allow you to do? If i remember correctly
>> you run into problems there as well...
>>  
>>
> Just to let you know: The ReactOS license it GPL too. Everything's 
> clear now? May I now use the Reiser4 sources to develop a driver for 
> ReactOS?
>
> Regards,
> Mark
>
>
>
Well, it seems I misunderstood.  I assumed you were using proprietary OS 
components.  So long as the whole OS is GPL'd, you can use Reiser4.  If 
however, MS is being paid license fees, you must pay me fees too.

I am frankly skeptical that one should attempt to clone windows.

Hans

RE: where are reiser4 sources

[Burnes, James]

Hans Reiser said...
> 
> I am frankly skeptical that one should attempt to clone windows.
> 
> Hans

Yes. It's a bit like cloning Frankenstein's monster, isn't it?

In the end all you have a bolt-compatible product that runs slowly on
lightening and falls apart if you hit it on the head too hard.

jim burnes

Re: where are reiser4 sources

[Alex Zarochentsev]

hello

On Mon, Feb 21, 2005 at 05:16:47PM +0100, Mark Junker wrote:
> Hi,
> 
> where are the Reiser4 sources? I just want to use Reiser4 in a separate 
> application and don't like the idea of extracting the sources from the 
> linux 2.6 patch.

public access to our bk repository works again (there were problems with
bk pull)
bk://bk.namesys.com/bk/reiser4 -- it contains fs/reiser4/**.

> 
> Regards,
> Mark
> 

-- 
Alex.