Reiser4's status of this week.

Reiser4's status of this week.

[stone_wang]

Hi,Hans:

Your website are saying "Reiser4 is in final testing, and will ship soon!"  It has been saying that for a long time :(


When could Reiser4 be finaly released? We are eager to try it.

Regards.

Stone.

Re: Reiser4's status of this week.

[Hans Reiser]

stone_wang@sohu.com wrote:

>Hi,Hans:
>
>Your website are saying "Reiser4 is in final testing, and will ship soon!"  It has been saying that for a long time :(
>
>
>When could Reiser4 be finaly released? We are eager to try it.
>
>Regards.
>
>Stone.
>
>
>  
>
next week.  or so we hope.

Reiser4 on x86_64

[Claudio Martins]

On Saturday 19 June 2004 16:27, Hans Reiser wrote:
> stone_wang@sohu.com wrote:
> >
> >When could Reiser4 be finaly released? We are eager to try it.
> >
> >Regards.
> >
> >Stone.
>
> next week.  or so we hope.


  Hi, 

   I would be interested in testing reiser4 on an AMD64 platform, if there is 
interest on making it work on a 64-bit platform, besides 32-bit i386. As far 
as I can tell by the README file it only works on i386 for now. I would like 
to test it on my system, running the new 64-bit Debian AMD64 port (also known 
as pure64), so let me know when/if there are any pacthes to make it work.

  Best regards, and keep up the good work.

Claudio Martins

Re: Reiser4's status of this week.

[Nicholas S. Wourms]

Hans Reiser wrote:
> stone_wang@sohu.com wrote:
> 
>> Hi,Hans:
>>
>> Your website are saying "Reiser4 is in final testing, and will ship 
>> soon!"  It has been saying that for a long time :(
>>
>>
>> When could Reiser4 be finaly released? We are eager to try it.
>>
>> Regards.
>>
>> Stone.
>>
>>
>>  
>>
> next week.  or so we hope.

Hans,

I've noticed that there seems to be a problem with your 
reiser4-linux-2.6 bitkeeper repository.  Unlike the 2.5 version I used 
awhile back, this one seems to just be an old copy of the stock 
linux-2.6.5 kernel with the 2.6.5-mm2 patches added.  None of the 
reiser4 base or extra patches seem to have been added (excluding the 
ones for fs/reiser4).  Would someone mind fixing this?  Don't you have 
an internal repository with all the modifications in the base and extra 
series applied?  If your internal tree can't be exported, can you 
provide a snapshot BK-style(not gnu) patch against linus-current?

I've also noticed, as has been noted in the past, that bk pulls are 
still broken.  Someone mentioned that it is a problem with the new bk. 
If this is true, why not contact Larry for support?  Not that it matters 
now, since the reiser4-linux-2.6 isn't usable, but it might be helpful 
for future syncs.

Cheers,
Nicholas

Re: Reiser4's status of this week.

[mjt]

On Sat, Jun 19, 2004 at 02:15:39PM -0400, Nicholas S. Wourms wrote:
>
>I've also noticed, as has been noted in the past, that bk pulls are 
>still broken.  Someone mentioned that it is a problem with the new bk. 
>If this is true, why not contact Larry for support?  Not that it matters 
>now, since the reiser4-linux-2.6 isn't usable, but it might be helpful 
>for future syncs.

The new 2.6s are very usable.

Last I spoke with Zam Zarochentsev he said he had a theory for fixing
the biggest bug that has to do with mmap applications when running out
of memory.

Besides that, I haven't heard of any mission-critical bugs.

As for BK, I don't care, as we have the auto-snapshots at the URL
http://namesys.com/auto-snapshots available.

Mind you, some older 2.6 auto-snapshots were best described by the
word unusable, but it's gotten better.

-- 
mjt

Re: Reiser4's status of this week.

[Hans Reiser]

Markus Törnqvist wrote:

>
>
>Mind you, some older 2.6 auto-snapshots were best described by the
>word unusable, but it's gotten better.
>
>  
>
This is why one should not use auto-snapshots.....;-)

I do however understand that it has been too long since the last 
snapshot release.

Re: Reiser4's status of this week.

[Nicholas S. Wourms]

> On Sat, Jun 19, 2004 at 02:15:39PM -0400, Nicholas S. Wourms wrote:
> 
>>I've also noticed, as has been noted in the past, that bk pulls are 
>>still broken.  Someone mentioned that it is a problem with the new bk. 
>>If this is true, why not contact Larry for support?  Not that it matters 
>>now, since the reiser4-linux-2.6 isn't usable, but it might be helpful 
>>for future syncs.
> 
> 
> The new 2.6s are very usable.

I wasn't referring to the actual state of the kernel with the reiser4 
patches.  I was talking about the BK repo, which is *exactly* the same 
as a stock 2.6.5 with an -mm patch (in other words it has none of the 
reiser4 infrastructure patches applied, like it should have).  This is 
contrary to what the namesys webpage says ought to be in there and is 
contrary with the way it had been in the past.

> Last I spoke with Zam Zarochentsev he said he had a theory for fixing
> the biggest bug that has to do with mmap applications when running out
> of memory.
> 
> Besides that, I haven't heard of any mission-critical bugs.
> 
> As for BK, I don't care, as we have the auto-snapshots at the URL
> http://namesys.com/auto-snapshots available.

How you feel about BK is not relevant, I wasn't addressing this concern 
to you.  Yes, I am aware of those snaps, but that defeats the purpose of 
bitkeeper, since you loose all the metadata and the simplicity of 
merging in code.

Also, those snapshot patches omit (I think) all of the excellent 
"extras", like UML improvements, which Hans has done.  My point is that 
the reiser4-linux-2.6 BK repo used to have everything except the actual 
fs/reiser4/* when it was called "reiser4-linux-2.5", but now it doesn't. 
  There have been problems with the synching of the namesys public repos 
with the private repos in the past, so I thought this might be what is 
happening now to reiser4-linux-2.6.

Cheers,
Nicholas

Re: Reiser4's status of this week.

[Hans Reiser]

Nicholas S. Wourms wrote:

> Hans Reiser wrote:
>
>> stone_wang@sohu.com wrote:
>>
>>> Hi,Hans:
>>>
>>> Your website are saying "Reiser4 is in final testing, and will ship 
>>> soon!"  It has been saying that for a long time :(
>>>
>>>
>>> When could Reiser4 be finaly released? We are eager to try it.
>>>
>>> Regards.
>>>
>>> Stone.
>>>
>>>
>>>  
>>>
>> next week.  or so we hope.
>
>
> Hans,
>
> I've noticed that there seems to be a problem with your 
> reiser4-linux-2.6 bitkeeper repository.  Unlike the 2.5 version I used 
> awhile back, this one seems to just be an old copy of the stock 
> linux-2.6.5 kernel with the 2.6.5-mm2 patches added.  None of the 
> reiser4 base or extra patches seem to have been added (excluding the 
> ones for fs/reiser4).  Would someone mind fixing this?  Don't you have 
> an internal repository with all the modifications in the base and 
> extra series applied?  If your internal tree can't be exported, can 
> you provide a snapshot BK-style(not gnu) patch against linus-current?
>
> I've also noticed, as has been noted in the past, that bk pulls are 
> still broken.  Someone mentioned that it is a problem with the new bk. 
> If this is true, why not contact Larry for support?  Not that it 
> matters now, since the reiser4-linux-2.6 isn't usable, but it might be 
> helpful for future syncs.
>
> Cheers,
> Nicholas
>
>
>
this is for flx and vs to answer....

Re: Reiser4's status of this week.

[Nicholas S. Wourms]

Hans Reiser wrote:
> Nicholas S. Wourms wrote:
> 
>> Hans Reiser wrote:
>>
>>> stone_wang@sohu.com wrote:
>>>
>>>> Hi,Hans:
>>>>
>>>> Your website are saying "Reiser4 is in final testing, and will ship 
>>>> soon!"  It has been saying that for a long time :(
>>>>
>>>>
>>>> When could Reiser4 be finaly released? We are eager to try it.
>>>>
>>>> Regards.
>>>>
>>>> Stone.
>>>>
>>>>
>>>>  
>>>>
>>> next week.  or so we hope.
>>
>>
>>
>> Hans,
>>
>> I've noticed that there seems to be a problem with your 
>> reiser4-linux-2.6 bitkeeper repository.  Unlike the 2.5 version I used 
>> awhile back, this one seems to just be an old copy of the stock 
>> linux-2.6.5 kernel with the 2.6.5-mm2 patches added.  None of the 
>> reiser4 base or extra patches seem to have been added (excluding the 
>> ones for fs/reiser4).  Would someone mind fixing this?  Don't you have 
>> an internal repository with all the modifications in the base and 
>> extra series applied?  If your internal tree can't be exported, can 
>> you provide a snapshot BK-style(not gnu) patch against linus-current?
>>
>> I've also noticed, as has been noted in the past, that bk pulls are 
>> still broken.  Someone mentioned that it is a problem with the new bk. 
>> If this is true, why not contact Larry for support?  Not that it 
>> matters now, since the reiser4-linux-2.6 isn't usable, but it might be 
>> helpful for future syncs.
>>
>> Cheers,
>> Nicholas
>>
>>
>>
> this is for flx and vs to answer....

Thanks, I'm eager to test the new features of reiser4 now that it has 
stabilized a bit since 2.5.  I might also experiment with trying to port 
the x86-specific bits to sparc64 and then try to port the lilo patch to 
silo.  I know the webpage says it is for x86 only, still I would like to 
give it a try on my sparc64 box with a spare disk I have lying around. 
IIRC, the actual infrastructure seemed fairly portable and arch-independant.

Cheers,
Nicholas

Re: Reiser4's status of this week.

[Alex Zarochentsev]

On Sat, Jun 19, 2004 at 02:15:39PM -0400, Nicholas S. Wourms wrote:
> Hans Reiser wrote:
> >stone_wang@sohu.com wrote:
> >
> >>Hi,Hans:
> >>
> >>Your website are saying "Reiser4 is in final testing, and will ship 
> >>soon!"  It has been saying that for a long time :(
> >>
> >>
> >>When could Reiser4 be finaly released? We are eager to try it.
> >>
> >>Regards.
> >>
> >>Stone.
> >>
> >>
> >> 
> >>
> >next week.  or so we hope.
> 
> Hans,
> 
> I've noticed that there seems to be a problem with your 
> reiser4-linux-2.6 bitkeeper repository.  Unlike the 2.5 version I used 
> awhile back, this one seems to just be an old copy of the stock 
> linux-2.6.5 kernel with the 2.6.5-mm2 patches added.  None of the 
> reiser4 base or extra patches seem to have been added (excluding the 
> ones for fs/reiser4).  Would someone mind fixing this?  Don't you have 
> an internal repository with all the modifications in the base and extra 
> series applied?  

Yes we have.
We work with an internal bk repository. 

The public repositories are copies of the internal ones, we have a script to
update public repositories once per day.  We will figure out after weekend 
why it does not after weekend.

> If your internal tree can't be exported, can you 
> provide a snapshot BK-style(not gnu) patch against linus-current?

we have two repositories, one for core kernel + our local changes to the core,
reiser4 itself is in another BK.  I think we can't provide one bk-style patch
easily.

> I've also noticed, as has been noted in the past, that bk pulls are 
> still broken.  Someone mentioned that it is a problem with the new bk. 
> If this is true, why not contact Larry for support?  

Flx did, but the problem still there.

> Not that it matters now, since the reiser4-linux-2.6 isn't usable, but it
> might be helpful for future syncs.
> Cheers, Nicholas

-- 
Alex.

Re: Reiser4's status of this week.

[Nicholas S. Wourms]

zam wrote:
> On Sat, Jun 19, 2004 at 02:15:39PM -0400, Nicholas S. Wourms wrote:
> 
> Yes we have.
> We work with an internal bk repository. 
> 
> The public repositories are copies of the internal ones, we have a script to
> update public repositories once per day.  We will figure out after weekend 
> why it does not after weekend.
> 

Thanks for looking into this.  Are you still working on it?  I ask 
because attempting to bk clone now returns the following error:

ERROR-Lock fail: possible permission problem.

Cheers,
Nicholas