Alexander Zarochentsev wrote:
>On Monday 31 October 2005 09:24, Alexander Zarochentsev wrote:
>
>
>>Hi,
>>
>>On Sunday 30 October 2005 02:13, Isaac Chanin wrote:
>>
>>
>>>Hi Hans,
>>>
>>>I don't think it's a device driver problem. My fix derived simply from
>>>noticing that the function whe
Toomas Laasik wrote:
>Hello,
>
>I was wondering if reiserfs has some sort of history plugin. I want a
>filesystem that manages files similar to CVS or SVN so that I can say for
>example that "I want asdasd.txt file exactly as it was on 15.10.2005
>14:20:05" and I can get it. Of cource keeping that
Isaac Chanin wrote:
> Hans Reiser wrote:
>
>> Isaac Chanin wrote:
>>
>>
>>> Hans Reiser wrote:
>>>
>>>
>>>> It should be not 256, but BIO_MAX_PAGES, yes? Defining limits in two
>>>> places is bad, yes?
>>
Isaac Chanin wrote:
> Hans Reiser wrote:
>
>>
>> It should be not 256, but BIO_MAX_PAGES, yes? Defining limits in two
>> places is bad, yes?
>>
>>
>
> Yeah, I think the code is running into two different limits here.
> Reiser4 wants it to be
its in two
places is bad, yes?
> check around where max_blocks is set rather than around nr_blocks
> inside the while loop.
>
>
> Isaac
>
>
> Hans Reiser wrote:
>
>> Thanks Isaac!
>>
>> Does IDE have a different maximum? Is there a non-hack way to discover
&g
Gregory Maxwell wrote:
>Any thought to making a file plugin that creates copy on write files?
>The operation would be something like a hardlink which is invisible to
>the user and broken as soon as either file is modified.
>
>Files could be COWed by a flag on the cp command (or really, perhaps
>th
PFC wrote:
>
> Remember my message where I said reiser4 was preventing my laptop
> from shutting down itself ?
>
> Well it turned out that, in fact, it was a stupid shfs-mount
> process which would refuse to die. Adding a "killall ssh" in the
> local.stop script is a bit violent, but pe
Thanks Isaac!
Does IDE have a different maximum? Is there a non-hack way to discover
the maximum of the device driver underneath?
Hans
Isaac Chanin wrote:
>Steve Olivieri wrote:
>
>
>>Greetings!
>>
>>I have a Maxtor Atlas II 15k, 147GB SCSI hard disk and an LSI Logic
>>LSI21320 Ultra320 SCSI
Alexander G. M. Smith wrote:
>John Gilmore wrote on Wed, 26 Oct 2005 17:02:06 +:
>
>
>>I had understood that a big part of the issue with file-as-directory was the
>>same as the issue with hard links to directories. Which I thought is that if
>>you move one directory into another, you can
John Gilmore wrote:
>On Wednesday 26 October 2005 22:40, Nate Diller wrote:
>
>
>>File-as-Directory
>> The issue with file-as-directory (FaD) is that it removes the Acyclic
>>property of the namespace graph. This is because anything which contains
>>file data can be hard-linked, even if that i
Nate Diller wrote:
>On 10/26/05, Peter van Hardenberg <[EMAIL PROTECTED]> wrote:
>
>
>>On October 26, 2005 05:44 am, you wrote:
>>
>>
>
>
>
>>Also: I still have not been able to USE files as directories. Yes, I can
>>reach
>>file//, but that is only one special case. I can crash th
Please remember that the idea of the plugin is that it is selectively
used on a few files.
Nate, please comment on your notion of having list all functionality,
and how allowing cycles could be ok under such a scenario.
Hans
Chester R. Hosey wrote:
>Peter van Hardenberg wrote:
>
>
>>Although I freely acknowledge my inexperience, I believe the real problems
>>are
>>related to graph
Valentine Sinitsyn wrote:
>Hi all,
>
>I've prepared a modified installer disk for Slackware Linux 10.2 which
>allows to install this distro on Reiser4 partitions almost the same
>way you do with other FSes (ext2/3, reiserfs etc), i.e. with no kernel
>recompilation by yourself etc. It is now under
Peter van Hardenberg wrote:
>Hello all,
>
>I'm a student at the University of Victoria. Between myself and a few fellow
>students we have embarked on a quest to do some experiments with the Reiser4
>metadata system to show it off and provide some real world use cases.
>
>We'll be spending lots o
David Masover wrote:
> Ron Joffe wrote:
>
>> On Tuesday 25 October 2005 14:13, Hans Reiser wrote:
>>
>>> If yes, what steps did you take to do it?
>>
>>
>>
>> Not quite there yet, but would like to test it out.
>>
>> Hans, could
Ron Joffe wrote:
>On Tuesday 25 October 2005 14:13, Hans Reiser wrote:
>
>
>>If yes, what steps did you take to do it?
>>
>>
>
>Not quite there yet, but would like to test it out.
>
>Hans, could you give a status of Reiser4. I have seen allot of differ
Edward Shishkin wrote:
> Hans Reiser wrote:
>
>> John Gilmore wrote:
>>
>>> So the first beta of compression will only have the option to
>>> control it at mkfs time?
>>>
>>>
>>
>> It should be explained that on the first flush
If yes, what steps did you take to do it?
I'll take a patch. Especially since I have proposed much the same in
the past. I'll discuss it more if someone starts writing one.;-)
Hans
Konstantin Münning wrote:
>Hi!
>
>The discussion abot loosing important files made me think about a
>fetaure I met and liked on DR-DOS (later Novell DOS bu
Sander wrote:
>Hans Reiser wrote (ao):
>
>
>>This would not be (at least in theory) useful for RAID devices, but for
>>a user with a single disk drive, it might be useful to have a plugin
>>that creates two (or N) copies, and tries to allocate the two copies at
This would not be (at least in theory) useful for RAID devices, but for
a user with a single disk drive, it might be useful to have a plugin
that creates two (or N) copies, and tries to allocate the two copies at
opposite ends of the disk. Anyone out there still looking for a plugin
to write?
Han
John Gilmore wrote:
>On Monday 24 October 2005 19:08, Edward Shishkin wrote:
>
>
>>John Gilmore wrote:
>>
>>
>>>How are plugin/file
>>>relationships handled without it?
>>>
>>>
>>For the first time there will be an option in mkfs to assign a file
>>plugin for regular files per superblo
John Gilmore wrote:
>There is a 'compress' directory in in my reiser4 source tree. So is the
>compression plugin done?
>
No, it is in an "any couple of weeks now"state.
> Is my disk/files compressed? And if it was/wasn't
>how would I know the difference, and change it?
>
>
>
>
Vladimir V. Saveliev wrote:
>Hello
>
>Yoanis Gil Delgado wrote:
>
>
>>On Thursday 20 October 2005 09:06 pm, Yoanis Gil Delgado wrote:
>>
>>
>>>Hi i just downloaded the 2.6.13.1 kernel source and the reiser4 patch for
>>>this kernel (reiser4-for-2.6.13-1.patch). When compiling i get the
>>>fo
Valentine Sinitsyn wrote:
>Hi, all,
>
>HR> We should work to integrate well with it. Zam, can you look at that?
>HR> Thanks.
>I was looking through linux-2.6.10 sources this morning and did not found
>laptop_mode anywhere in filesystem-specific code (except xfs). I'm not
>a kernel hacker but it s
David Masover wrote:
>Sinitsyn Valentine wrote:
>
>
>>Hi all,
>>
>>I'm considering installing Reiser4 on my laptop, but I also want to
>>use laptop_mode (http://www.xs4all.nl/~bsamwel/laptop_mode/index.html)
>>to save battery power. So I'm wondering wether these two products are
>>compatible wit
ch4os wrote:
> I just made a bad mistake...
>
> I just RM the files from /var/lib/ldap
> thinking I was coping them still a little hung over
>
> df:
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda2 69535216 28047868 41487348 41% /
> tmpfs
What is the detailed status on that work, by the way?
evilninja wrote:
> [cc'ing 4 mailing lists, please reply to *one* list only!]
>
> hi,
>
> every now and then i'm running some benchmarks on filesystems i really
> use...here are the results:
>
> http://nerdbynature.de/bench/prinz64/2.6.14-rc2-mm2/bonnie.html
> http://nerdbynature.de/bench/prinz64/
Vitaly Fertman wrote:
>On Wednesday 05 October 2005 19:10, Lance Reed wrote:
>
>
>>So, is this problem fixed in Reiserfs4 ?
>>
>>
>
>reiser4 is absolutely different fs written from the scratch,
>it is in the mm kernel only yet.
>
>
You did not answer the question.;-)
>regarding the reiser
Christoph Hellwig wrote:
>On Mon, Sep 26, 2005 at 07:03:52PM +0400, Vladimir V. Saveliev wrote:
>
>
>>> - you still do your plugin mess in ->readpage. honsetly could you
>>> please explain why mpage_readpage{,s} don't work for you?
>>>
>>>
>>The reason is performance. Reiser4 uses a sea
Thanks for reviewing the code like this. Please let me know if you find
the reiser4 code to have any problems, it is very generous for you to
donate your time like this.
Chris Bainbridge wrote:
>On 02/10/05, Islam Amer <[EMAIL PROTECTED]> wrote:
>
>
>>On 10/2/05, Alexander Skwar <[EMAIL PROTECTED]> wrote:
>>
>>
>>>Chris Bainbridge schrieb:
>>>
>>>
Hi,
Today I updated from vanilla 2.6.12.5 + reiser4 to vanilla 2.6.13 +
reiser4-for-2.6.1
Jake Maciejewski wrote:
>On Sat, 2005-10-01 at 20:40 +0200, Artur Makówka wrote:
>
>
Will it work also with 2.6.13.2 kernel ? or is it only for 2.6.13 ( or
2.6.13.1 )
i couldnt find any information about this on page, and i want to be
sure...
>>>I used it
Vladimir V. Saveliev wrote:
>Hello
>
>luc wrote:
>
>
>>Hi,
>>
>> i want to try use reiser4 and i discover this :
>>
>>I have 80Gb Western Digital HDD. When i created one partition (full
>>disk)
>>
>>mkfs.reiserfs -f /dev/sda1
>>
>>then obtain this
>>
>>reiserfs 3.6
>>[EMAIL PROTECTED] luc
It works on non-amd64, will fix amd64 tomorrow I hope.
Reiser4 performance dropped in the -mm series due to the write
throttling patch and also dropped due to a fixed bug (removing type safe
lists added a bug). We don't yet know if we got quite all the
performance back, we are still testing. Conservative users should wait
a week or two to see if bug
;-)
Thanks,
Hans
Islam Amer wrote:
>On 9/28/05, Hans Reiser <[EMAIL PROTECTED]> wrote:
>
>
>> Check out the latest cfq in the latest kernel, it is much better than
>>the others for most applications. Anticipatory used to be the best, but
>>cfq-3 is better no
Islam Amer wrote:
>>The performance boost for any of the provided iosched schemes can be
>>positive, negative, imaginary, or complex(*), depending on the actual
>>workload of
>>the system, and what reference patterns it generates.
>>
>>
>>
>I assumed published benchmarks are conducted under s
Check out the latest cfq in the latest kernel, it is much better than
the others for most applications. Anticipatory used to be the best, but
cfq-3 is better now.
Fionn Behrens wrote:
>
>
>Because of my good experiences with ReiserFS in the past I had high
>expectations. As you correctly and rightfully stated, reiser4 is
>development code and that probably means I should not rely on anything.
>
>
Well, it had gone stable, sorry we let it destable.
Ha
Fionn Behrens wrote:
>On Mi, 2005-09-28 at 18:25 +0400, Vitaly Fertman wrote:
>
>
>
>>>2.6.11 refused to boot the
>>>root partition, claiming that there were an inconsistency in the FS.
>>>
>>>
>>the disk format got new parameters and old kernels cannot understand it right.
>>
>>
>
>Ah
I apologize that the latest reiser4 with the cleanups requested by
Hellwig is more than a bit of a turkey (due to bugs in our cleanups).
We just now sent some patches which will improve things, but I don't yet
have confidence in the code, and will not until we go for two weeks with
no reports of p
Łukasz Mierzwa wrote:
> Dnia Sat, 24 Sep 2005 01:44:02 +0200, Gherald <[EMAIL PROTECTED]>
> napisał:
>
>> A snipet from htop:
>>
>> PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
>> 66 root 25 0 0 0 0 R 50.0 0.0 1h21:53 pdflush
>> 3235 root 25 0
Raymond A. Meijer wrote:
>On Friday 23 September 2005 11:35, Vladimir V. Saveliev wrote:
>
>Hi Vladimir,
>
>
>
>>Ray, you might want to try to mount reiser4 with -o
>>onerror=remount-ro This may help to avoid some of oopses
>>
>>
>
>I'll try this.
>
>
>
>>You need new hard drive.
>>
>>
Theodore Ts'o wrote:
>On Tue, Sep 20, 2005 at 09:41:36AM -0500, David Masover wrote:
>
>
>>And personally, if it was my FS, I'd stop working on fsck after it was
>>able to "check". That's what it's for. To fix an FS, you wipe it and
>>restore from backups.
>>
>>
>
>If that's Reiser4's ph
Nikita Danilov wrote:
>Hans Reiser writes:
>
>[...]
>
> > >
> > Yes, and one can compensate for them fairly cleanly. I can't say more
> > without the customer releasing the code first.
>
>That's the point: text-book algorithms are usually use
Nikita Danilov wrote:
>Hans Reiser writes:
> > Horst von Brand wrote:
> >
> > >
> > >
> > >Funny that the "texbook algorithms" aren't used in real life. Wonder why...
> > >
> > >
> > Try BSD. If the BSD book can
Andrew Morton wrote:
>Hans Reiser <[EMAIL PROTECTED]> wrote:
>
>
>>At the this time we have no idea which patch is responsible, probably in
>>a day or two we'll have a patch to fix it.
>>
>>
>>
>
>OK. I assume this performance cha
At the this time we have no idea which patch is responsible, probably in
a day or two we'll have a patch to fix it.
Hans
Nikita Danilov wrote:
>Hans Reiser writes:
>
>[...]
>
> > >
> > So what do you suggest we change it to, Nikita?
>
>Just remove #ifdef/#endif as was suggested.
>
>Nikita.
>
>
>
>
Ok. vs, please do so.
Ric Wheeler wrote:
> Gregory Maxwell wrote:
>
>> On 9/20/05, Hans Reiser <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> Another goal of the group should be to formulate a requested set of
>> changes or extensions to the makers of drives and oth
Nikita Danilov wrote:
>Hans Reiser writes:
> > Stephen Pollei wrote:
> >
> > >
> > >
> > >Also note my opinion, doesn't really count if you grep the kernel
> > >sources for pollei, you won't find anything.
> > >
> > &
PFC wrote:
>
An interesting idea: select the algo and a range of compression
levels per file,
>>>
>
> A simple check on wether it's an already compressed file (using
> file extension and magic number) should be quite easy to do and cheap.
>
> Now, intrigued by this lzo thingie,
I have been thinking about it for quite a while, and while I would be
interested in seeing if it was still needed after the elevator code gets
fixed to not congest, it should go in until then.
Hans
Ric Wheeler wrote:
> Hans Reiser wrote:
>
>> Ric Wheeler wrote:
>>
>>
>>> As an earlier thread on lkml showed this summer, we still have a long
>>> way to go to getting consistent error semantics in face of media
>>> failures between the various
Laurent Riffard wrote:
>
> Hello,
>
> In kernel 2.6.14-rc1-mm1, Reiser4 present 2 regressions with regard to
> 2.6.13-mm1 :
>
> A) Suspend-to-disk does not work because the process "[ent:hda8]"
> can't be stopped.
>
> $ mount | grep hda8
> /dev/hda8 on /home/laurent/kernel type reiser4 (rw,nosuid,
Ric Wheeler wrote:
> As an earlier thread on lkml showed this summer, we still have a long
> way to go to getting consistent error semantics in face of media
> failures between the various file systems. I am not sure that we even
> have consensus on what that default behavior should be between
>
Pavel Machek wrote:
>Hi!
>
>
>
Second check...
e2fsck 1.34 (25-Jul-2003)
>>>I have 1.38 here, so yours is too old.
>>>
>>>
>>I'll compile something new tomorrow and try to retest it.
>>
>>
>>
>>>OTOH if reiser4 survives that for 80 cycles... that's pretty goo
Stephen Pollei wrote:
>
>
>Also note my opinion, doesn't really count if you grep the kernel
>sources for pollei, you won't find anything.
>
>
>
Your opinion counts, but lets see what Nikita says before I say
anything. Nikita is more expert than I in regards to compiler tricks.
Thanks Ted, I'll ask Vitaly to read the paper, and tell us what he
thinks should be learned from it for V4.
Hans
Theodore Ts'o wrote:
>On Tue, Sep 20, 2005 at 09:51:33AM +0200, Pavel Machek wrote:
>
>
>>Do you have working fsck for V4? Until then, you should not claim that
>>users should switc
Theodore Ts'o wrote:
>On Tue, Sep 20, 2005 at 12:18:46PM -0600, Jonathan Briggs wrote:
>
>
>>I use Reiser3 and Reiser4 on all my systems and fsck has always worked
>>even if it has been much slower than I would like. The only problems
>>I've experienced have been on the same level as when an ex
Horst von Brand wrote:
> Could you /please/ stop your snide remarks on the code and its authors? If
>
>for nothing else, the very people you are insulting in public are the exact
>ones that will decide if they take on the work of auditing and integrating
>your code.
>
>
Our code was called messy
Horst von Brand wrote:
>
>
>Funny that the "texbook algorithms" aren't used in real life. Wonder why...
>
>
Try BSD. If the BSD book can be believed, they use"texbook algorithms".
;-)
Thanks much for this test script, Vitaly, please give it a try and tell
me how it goes.
Hans
Pavel Machek wrote:
>Hi!
>
>
>
>>V3 is obsoleted by V4 in every way. V3 is old code that should be
>>marked as deprecated as soon as V4 has passed mass testing. V4 is far
>>superior in its coding st
Nikita Danilov wrote:
>Lorenzo Allegrucci <[EMAIL PROTECTED]> writes:
>
>[...]
>
>
>
>>Why not just rename the kernel option "elevator" to "iosched" ?
>>
>>
>
>At least update Documentation/kernel-parameters.txt to be consistent,
>but I think kernel boot options are considered to be a part o
Horst von Brand wrote:
>Nikita Danilov <[EMAIL PROTECTED]> wrote:
>
>
>
>It is supposed to go into the kernel, which is not exactly warning-free.
>
>
While I have no passionate feelings about Nikita's ifdef, I must note
that Reiser4 will always be warning free within 3 days of my finding out
t
David Masover wrote:
>
> And personally, if it was my FS, I'd stop working on fsck after it was
> able to "check". That's what it's for. To fix an FS, you wipe it and
> restore from backups.
>
>
Umm, this is going too far David. Our fsck should work, and we will
give his script to Vitaly to pla
Jens Axboe wrote:
>
>Seeing as you are the one that is apparently bothered by the misnomer,
>it follows that you would be the one submitting a patch for this. Not
>that it would be accepted though, I don't see much point in renaming
>functions and breaking drivers just because of a slightly bad na
Nick Piggin wrote:
>
>
>[snip devfs]
>
>Yeah I was just trying to introduce some humour to the thread!
>Or maybe deflate one flamewar by starting another :)
>
>
;-)
Horst von Brand wrote:
> Care to give names?
Not publicly, no. If akpm or Linus asks, I will happily encourage
either of them to try to win him back.
>
>
>> who decided to work on BSD
>>because they had too much dignity to develop a filesystem for
Nick Piggin wrote:
>On Mon, 2005-09-19 at 23:28 -0700, Hans Reiser wrote:
>
>
>>Nick Piggin wrote:
>>
>>
>
>
>
>>>What's wrong with the elevator code?
>>>
>>>
>>>
>>The name for one. There is no
Nick Piggin wrote:
> Hans Reiser wrote:
>
>> So why is the code in the kernel so hard to read then?
>>
>> Linux kernel code is getting better, and Andrew Morton's code is
>> especially good, but for the most part it's unnecessarily hard to
>> read
Nikita Danilov wrote:
>
>It's enough to monitor your own code, rather than the whole kernel.
>
>
To this I would add, the kernel should not have warnings when it
compiles. Now THAT is a style requirement I would rigorously enforce if
I could. I deeply regret that long ago there was a Linux scs
Bill Davidsen wrote:
> Denis Vlasenko wrote:
>
>>
>> Maybe xfs shouldn't be accepted too, this may be an answer.
>
>
> That argument is specious, and raises the chance that someone will
> suggest that we learn from our mistakes.
It wasn't a mistake to accept xfs, xfs is a great piece of technolog
>One way in which half-OS was superior to DOS was how spectacularly the
>former project failed after a lot of hype. :-)
>
>
OS/2 was technically superior to windows 95. The only failure was the
marketing/herd movement issues. I used OS/2, it was better.
Alan Cox wrote:
>
>Perhaps you do. The kernel follows a coding style. It isn't my coding
>style but like everyone else except you I try and follow it.
>
>
I also don't care enough about coding style issues to resist them.;-)
We have conformed to the coding style issues that were pointed out, an
Alan Cox wrote:
>On Sul, 2005-09-18 at 22:07 -0700, Hans Reiser wrote:
>
>
>>>the ability to fix some of those bugs fast, but we also all remember
>>>what happened with reiser3 later on despite early fast fixing.
>>>
>>>
>>>
>
Jake Maciejewski wrote:
>Also, if there's a default for Gentoo, it's ext3. The installation is
>still completely manual, but the instructions use "mke2fs -j" in the
>example.
>
>On Mon, 2005-09-19 at 00:49 -0500, Dan Oglesby wrote:
>
>
>>The following line of text appears on the main page at
>>
Dan Oglesby wrote:
> The following line of text appears on the main page at
> http://www.namesys.com:
>
> "V3 of reiserfs is used as the default filesystem for SuSE, Lindows,
> FTOSX, Libranet, Gentoo, Xandros and Yoper."
>
> I believe Slackware has defaulted to V3 for some time now. EXT3 and 2
>
got fixed, they are "this code would be
cleaner if written another way", or, most commonly, "where is the
comment that ought to be here?"
> On Sun, 18 Sep 2005 22:09:08 PDT, Hans Reiser said:
>
>> Of course, the reiser4 code is not as stable as it was before the
>>
Horst von Brand wrote:
>
>>>that and there's much more exciting filesystems like ocfs2 around that
>>>
>>>
>
>
>
>>This is exciting to... whom?
>>
>>
>
>To Cristoph, obviously. You should thank him for doing the (hard, boring,
>thankless) work of reviewing code for free. Even if it isn
Christian Iversen wrote:
>On Sunday 18 September 2005 12:26, Christoph Hellwig wrote:
>
>
>>On Sun, Sep 18, 2005 at 01:21:23PM +0300, Denis Vlasenko wrote:
>>
>>
>>>This is it. I do not say "accept reiser4 NOW", I am saying "give Hans
>>>good code review".
>>>
>>>
>>After he did his ba
Lennart Sorensen wrote:
>
> Neither was ready for use when they were
>included in the kernel and should probably have had big warning signs in
>the kernel config for them.
>
>
They did have warning signs: they were labeled experimental as is
reiser4.
At some point developers and their li
Alan Cox wrote:
>
>It doesn't matter if reiser4 causes crashes. It matters that people can
>fix them, that they are actively fixed and the code is maintainable. It
>will have bugs, all complex code has bugs. Hans team have demonstrated
>the ability to fix some of those bugs fast, but we also all r
Denis Vlasenko wrote:
>
>>And yet thousands and thousands of people, businesses, etc, say that
>>the Linux kernel code is miles above all the commercial software out
>>there.
>>
Not the commercial software I have worked with. IBM code, government
procured code, both are much more readable co
Denis Vlasenko wrote:
>On Friday 16 September 2005 20:05, Hans Reiser wrote:
>
>
>>All objections have now been addressed so far as I can discern.
>>
>>
>
>Random observation:
>
>You can declare functions even if you never use them.
>Thus here you
Christoph Hellwig wrote:
>additinoal comment is that the code is very messy, very different
>from normal kernel style, full of indirections and thus hard to read.
>
Most of my customers remark that Namesys code is head and shoulders
above the rest of the kernel code. So yes, it is different. In
All objections have now been addressed so far as I can discern.
The VFS layering issue was addressed after 2 months of recoding.
The undesired type safe lists were removed after ~ a man week of coding.
Cosmetic issues regarding line length, etc., were addressed.
Numerous ~ one l
Alexander Zarochentsev wrote:
>Hello,
>
>On Monday 04 April 2005 19:15, Nicolas Smallwood wrote:
>
>
>>reiser4[vianoderepos(1501)]: commit_current_atom
>>(fs/reiser4/txnmgr.c:1206)[niki
>>ta-3176]:
>>WARNING: Flushing like mad: 16384
>>
>>Saw this in dmesg this morning... is it anything to real
Peter Foldiak wrote:
> Hans Reiser wrote:
>
>>> The user (or tools) don't even have to know which is the "real" file,
>>> which are "parts of real files" and which are "concatenations of real
>>> files". This is really good for
Peter Foldiak wrote:
> Hans, in the interview you give the example:
>
> cat /home/reiser/mp3s//childcat > /dev/dsp
>
> to illustrate concatenation.
>
> I sorry for repeating myself, but still think it would be a lot cooler
> to be able to simply do:
>
> cat /home/reiser/mp3s > /dev/dsp
>
> t
Andrew Morton wrote:
>
>
>The type-unsafety of existing list_heads gives me conniptions too. Yes,
>it'd be nice to have a type-safe version available.
>
>That being said, I don't see why such a thing cannot be a wrapper around
>the existing list_head functions. Yes, there will be some ghastly
>C
Andrew Morton wrote:
>
>
>
>>1. pseudo files or "" files
>>
>>
>>
>
>
>
>> disabled. It remains a point of (extraordinary) contention as to
>>whether it can be fixed, we want to keep the code around until we can
>>devote proper resources into proving it can be (or until we fail to pr
Christoph Hellwig wrote:
> 6. remove type safe lists and type safe hash queues.
>
>> not done, it is not clear that the person asking for this represents a
>> unified consensus of lkml. Other persons instead asked that it just be
>> moved out of reiser4 code into the generic kernel code, whic
Chris Shoemaker wrote:
>On Fri, Sep 09, 2005 at 10:36:06AM -0700, Hans Reiser wrote:
>
>
>>If we lose every remaining point of this list, we can generate a patch
>>in a few days, because the VFS work was the only substantive (in coding
>>hours) task, and it is done
We haven't been sending much email out, but we have been working away.
We just finished the VFS work, and will send a patch out on Monday.
akpm asked for a bullet list of things suggested on lkml as issues for
inclusion.
There are some things that I would like akpm to confirm represent the
off
Andrew, we have been working on a big patch that resolves the VFS
layering issues. This patch should be ready to send in any day now, we
are debugging it. We may not have been sending you a lot of emails, but
we have been working away at it. I don't understand why you think the
review feedback w
Guys, I am sorry, but I just don't think this issue is a priority
compared to other issues. Sorry, too much else going on, honestly.
301 - 400 of 1230 matches
Mail list logo
