From: "LiFe" <LiFers@optusnet.com.au>
To: Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: WinFS beta out
Date: Tue, 30 Aug 2005 23:39:39 +1000 [thread overview]
Message-ID: <019d01c5ad68$4d5fdfa0$d60310ac@homedom> (raw)
In-Reply-To: 4313FE21.8080709@namesys.com
Watch the video demos from Ch9. Very geeky, dorky and slow.
From 10 minutes of skipping, they're basically saying they're building a
relational database on NTFS. They're not actually rebuilding NTFS, from the
ground up. So the sum total of the project will be a radically different
system wide service (rich database filing), which will probably be supported
by many applications in hereto unthought of ways.
What Hans has built is a new way of storing bits that increases speed,
reliability and flexability in the use of those bits in hereto unthought of
ways.
What'd be great? WinFS on Reiser4.
What we're gonna get? Windows Vista with a slowwer than ever file system,
based on 20yo technology, and uses a ton of RAM, but where data is self
organising in many fascinating ways. And *nix with a revolutionary fast and
different file system, where every application is going to make different
and incompatible use of the files as directories in order to emulate
WinFS-like features.
http://channel9.msdn.com/ShowPost.aspx?PostID=106356#106356
Dear god I love Firefox snapback tabs. Who invents this stuff? They should
be PAID!
----- Original Message -----
From: "Hans Reiser" <reiser@namesys.com>
To: "Jake Maciejewski" <maciejej@msoe.edu>
Cc: "Reiserfs List" <reiserfs-list@namesys.com>
Sent: Tuesday, August 30, 2005 4:35 PM
Subject: Re: WinFS beta out
> Jake Maciejewski wrote:
>
>>Yeah, if SQL on NTFS counts as a revolutionary filesystem. I wonder what
>>Namesys could do with MS's resources.
>>
>>
> Just a few million would be enough to do a lot.... ;-)
>
>>On Tue, 2005-08-30 at 00:36 -0400, Gregory Maxwell wrote:
>>
>>
>>>http://it.slashdot.org/it/05/08/29/2241243.shtml?tid=109&tid=218
>>>
>>>Looks like MSFT will be beating Linux to the nextgen FS punch after all.
>>>;)
>>>
>>>
>
next prev parent reply other threads:[~2005-08-30 13:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 4:36 WinFS beta out Gregory Maxwell
2005-08-30 5:42 ` Jake Maciejewski
2005-08-30 6:35 ` Hans Reiser
2005-08-30 13:39 ` LiFe [this message]
2005-08-30 15:45 ` Marc Perkel
2005-08-30 22:10 ` Lexington Luthor
2005-08-30 23:00 ` Christian Iversen
2005-08-31 1:06 ` Hans Reiser
2005-08-31 1:18 ` Christian Iversen
2005-08-31 10:44 ` LiFe
2005-08-31 13:45 ` michael chang
2005-09-01 8:24 ` LiFe
[not found] ` <b14e81f0050901070453f4d898@mail.gmail.com>
2005-09-01 14:04 ` michael chang
2005-08-31 0:59 ` Hans Reiser
2005-08-31 4:59 ` Marc Perkel
2005-08-31 5:46 ` David Masover
2005-08-31 7:13 ` Hans Reiser
2005-08-31 13:44 ` michael chang
2005-08-31 14:36 ` Fundind Reiser Development Marc Perkel
2005-08-31 19:54 ` Hans Reiser
2005-08-31 14:38 ` Funding " Marc Perkel
2005-08-31 21:44 ` WinFS beta out Hans Reiser
2005-08-31 14:32 ` Marc Perkel
2005-08-31 16:01 ` Jeff Mahoney
2005-08-31 17:32 ` changing label of disk Bedros Hanounik
2005-08-31 18:15 ` evilninja
2005-08-31 20:05 ` WinFS beta out Hans Reiser
2005-08-31 20:35 ` Marc Perkel
2005-08-31 17:45 ` Adrian Ulrich
[not found] ` <b14e81f00508301124ebf9ab9@mail.gmail.com>
2005-08-31 2:02 ` michael chang
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='019d01c5ad68$4d5fdfa0$d60310ac@homedom' \
--to=lifers@optusnet.com.au \
--cc=reiserfs-list@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.