All of lore.kernel.org
 help / color / mirror / Atom feed
From: jp <jp.guillemin@free.fr>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: Yusuf Iskenderoglu <enygma@dreadnought.hadiko.de>,
	ReiserFS Mailing List <reiserfs-list@namesys.com>,
	Reiserfs-dev <reiserfs-dev@namesys.com>
Subject: Vanilla 2.6.14.2 with reiser4-for-2.6.14-1.patch
Date: Fri, 11 Nov 2005 20:47:15 +0100	[thread overview]
Message-ID: <4374F543.1060102@free.fr> (raw)
In-Reply-To: <4374C7EE.20001@namesys.com>

Hi,

I've compiled the Vanilla 2.6.14.2 with reiser4-for-2.6.14-1.patch, 
built static.

My first tests are very positive :

I Launched the following "disk operations" at the same time, while Gxine 
was playing a MPG :
- a 400MB ISO building
- complete kernel source recursive directory copy
- Openoffice startup
- Firefox startup

There was no hangup in the video, and all disk operations finished 
without problems.

I'm going to keep using this kernel, and report any problem.

Regards

JP



Vladimir V. Saveliev wrote:

>Hello
>
>Yusuf Iskenderoglu wrote:
>  
>
>>Okay, thanks for the information. I will continue waiting.
>>
>>    
>>
>
>Well, here is the first attempt to relelase reiser4 for 2.6.14. Please try to
>use it.
>ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.14/reiser4-for-2.6.14-1.patch.gz
>
>
>Consider it as an experimental thing. Note, it will probably not compile as a
>module. Adding a line to mm/page-writeback.c the following line
>
>EXPORT_SYMBOL(clear_page_dirty_for_io);
>
>after clear_page_dirty_for_io()'s definition should fix that, though.
>
>
>
>  
>
>>On Mon, 2005-11-07 at 19:20 +0300, Vladimir V. Saveliev wrote:
>>    
>>
>>>Hello
>>>
>>>Yusuf Iskenderoglu wrote:
>>>      
>>>
>>>>Hello,
>>>>
>>>>I am not having a support issue, just a wish.
>>>>It always takes many weeks until you put a patch for the reiser4
>>>>filesystem for the most actual Linux version into your ftp server.
>>>>In this case, 2.6.14 is already released for one week now, and there is
>>>>still no patch available.
>>>>
>>>>I am not interested in patching the kernel with stuff from other/older
>>>>patches.
>>>>I just wish you be up-to-date
>>>>
>>>>Creating a patch for the actual kernel version simply cannot take you
>>>>more than 1 Minute.
>>>>
>>>>        
>>>>
>>>Sorry for delay with that. Code got big changes recently, we would like to test
>>>it a bit.
>>>      
>>>
>>    
>>
>
>
>
>  
>



  reply	other threads:[~2005-11-11 19:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1131353326.4553.4.camel@localhost.localdomain>
     [not found] ` <436F7ED5.1060106@namesys.com>
     [not found]   ` <1131385665.4553.13.camel@localhost.localdomain>
2005-11-11 16:33     ` A WISH: Reiser4 patch for 2.6.14 Vladimir V. Saveliev
2005-11-11 19:47       ` jp [this message]
2005-11-11 22:00       ` Jake Maciejewski
2005-11-12 21:58       ` Yusuf Iskenderoglu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4374F543.1060102@free.fr \
    --to=jp.guillemin@free.fr \
    --cc=enygma@dreadnought.hadiko.de \
    --cc=reiserfs-dev@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.