On Fri, 15 Jun 2007, Greg KH wrote:
Usually you don't do that by doing a 'mv' otherwise you are almost
guaranteed stale and mixed up content for some period of time, not to
mention the issues surrounding paths that might be messed up.
on the contrary, useing 'mv' is by far the cleanest way
alan wrote:
On Fri, 15 Jun 2007, H. Peter Anvin wrote:
This is one of those things that seems like a good idea, but frequently
ends up short. Part of the problem is that whenever you modify a file
is ill-defined, or rather, if you were to take the literal meaning of it
you'd end up with an
Chris Snook wrote:
The underlying internal implementation of something like this wouldn't
be all that hard on many filesystems, but it's the interface that's the
problem. The ':' character is a perfectly legal filename character, so
doing it that way would break things.
But to work without
This already exists -- it just not open sourced, and you could spend
years trying to create it. Trust me, once you start dealing with the
distributed issues with this, its gets very complex. I am not meaning
to discourage you, but there are patents already filed on this on
Linux.So you
Jeffrey V. Merkey wrote:
This already exists -- it just not open sourced, and you could spend
years trying to create it. Trust me, once you start dealing with the
distributed issues with this, its gets very complex. I am not meaning
to discourage you, but there are patents already filed
Chris Mason wrote:
Strange, these numbers are not quite what I was expecting ;) Could you
please post your fio job files? Also, how much ram does the machine
have? Only writing doesn't seem like enough to fill the ram.
-chris
Sure:
[global]
directory=/mnt/temp/default
I reviewed your sample implementation, and it appears to infringe 3
patents already.You should do some research on this.
Are you able to tell us which areas of the code infringe existing patents?
Cheers,
Mark
--
Dave: Just a question. What use is a unicyle with no seat? And no
On Fri, 15 June 2007 15:51:07 -0700, alan wrote:
Thus, in the end it turns out that this stuff is better handled by
explicit version-control systems (which require explicit operations to
manage revisions) and atomic snapshots (for backup.)
ZFS is the cool new thing in that space. Too bad
On Thu, 07 Jun 2007 17:40:03 +0100 David Howells [EMAIL PROTECTED] wrote:
Make NFS root work by creating a /root directory to satisfy the mount,
otherwise the path lookup for the mount fails with ENOENT.
Signed-off-by: David Howells [EMAIL PROTECTED]
---
init/do_mounts.c |5 -
On Sat, Jun 16, 2007 at 01:09:06AM -0700, [EMAIL PROTECTED] wrote:
On Fri, 15 Jun 2007, Greg KH wrote:
Usually you don't do that by doing a 'mv' otherwise you are almost
guaranteed stale and mixed up content for some period of time, not to
mention the issues surrounding paths that might
On Sat, 2007-06-16 at 09:15 -0700, Andrew Morton wrote:
On Thu, 07 Jun 2007 17:40:03 +0100 David Howells [EMAIL PROTECTED] wrote:
Make NFS root work by creating a /root directory to satisfy the mount,
otherwise the path lookup for the mount fails with ENOENT.
Signed-off-by: David
Jeffrey V. Merkey wrote:
When you get into the recycling issues with storage, the patents come
into play. Also, using the file name to reference revisions is already
the subject of a patent previously filed (I no longer own the patent, I
sold them to Canopy). There is a third one about to be
http://www.wipo.int/pctdb/en/fetch.jsp?LANG=ENGDBSELECT=PCTSERVER_TYPE=19SORT=1211506-KEYTYPE_FIELD=256IDB=0IDOC=1205953C=10ELEMENT_SET=IA,WO,TTL-ENRESULT=1TOTAL=3START=1DISP=25FORM=SEP-0/HITNUM,B-ENG,DP,MC,PA,ABSUM-ENGSEARCH_IA=US2005045566QUERY=%28IN%2fmerkey%29+
The last one was filed with
Alan Cox wrote:
http://www.wipo.int/pctdb/en/fetch.jsp?LANG=ENGDBSELECT=PCTSERVER_TYPE=19SORT=1211506-KEYTYPE_FIELD=256IDB=0IDOC=1205953C=10ELEMENT_SET=IA,WO,TTL-ENRESULT=1TOTAL=3START=1DISP=25FORM=SEP-0/HITNUM,B-ENG,DP,MC,PA,ABSUM-ENGSEARCH_IA=US2005045566QUERY=%28IN%2fmerkey%29+
The last one
On Sat, Jun 16, 2007 at 02:03:49PM -0600, Jeffrey V. Merkey wrote:
Jan Harkes wrote:
implementation, just a high level description. Finally advising anyone
(who is not an actual patent lawyer that could correctly interpret the
language and scope of a patent) to go search out patents seems
Jan Harkes wrote:
Sites like portal.acm.org and citeseer.ist.psu.edu are good places to
find copies of these papers. They also provide links to other work that
either is cited by, or cites these papers which is a convenient way to
find other papers in this area.
Researching, designing and
DEC had versioning files systems 30 years ago. Any
patents on their style must certainly have expired
long ago.
Look at RSX-11 and other seventies era operating
systems.
This is ancient stuff.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to
(Vax/VMS System Software Handbook)
(TOPS-20 User's Manual)
Also Files/11
Basic versioning goes back to at least ITS
Not sure how old doing file versioning and hiding it away with a tool to
go rescue the stuff you blew away by mistake is, but Novell Netware 3
certainly did a good job on
Alan Cox wrote:
(Vax/VMS System Software Handbook)
(TOPS-20 User's Manual)
Also Files/11
Basic versioning goes back to at least ITS
Not sure how old doing file versioning and hiding it away with a tool to
go rescue the stuff you blew away by mistake is, but Novell Netware 3
certainly
Jeffrey V. Merkey wrote:
The trick in the NetWare 3 model was to segregate the directory
entries onto special reserved
4K directory blocks (128 byte dir records). When it came time to purge
storage after the file system filled, an entire 4K block and all
chains was deleted during block
On Sat, Jun 16, 2007 at 09:15:14AM -0700, Andrew Morton wrote:
On Thu, 07 Jun 2007 17:40:03 +0100 David Howells [EMAIL PROTECTED] wrote:
Make NFS root work by creating a /root directory to satisfy the mount,
otherwise the path lookup for the mount fails with ENOENT.
Am still awaiting a
21 matches
Mail list logo
