decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Federation..... | 81 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Same Guy - Google Reader and other customer tragedies
Authored by: SilverWave on Monday, April 01 2013 @ 09:44 PM EDT
Google Reader and other customer tragedies Interesting once you filter out the anti google stuff.

---
RMS: The 4 Freedoms
0 run the program for any purpose
1 study the source code and change it
2 make copies and distribute them
3 publish modified versions

[ Reply to This | Parent | # ]

WinFS, Integrated/Unified Storage, and Microsoft – Part 4
Authored by: Ian Al on Tuesday, April 02 2013 @ 07:59 AM EDT
I think this is related to something in Windows 7 I hate with a passion. I think
that an object file store is a terrific idea. I am fed up with asking people I
help with computers 'and which directory do you store that sort of stuff?'.

So many Windows programs default to saving files in the C:Program Files
directory. I have spent many unhappy hours rounding up the creative content and
putting it into the correct directory. The reason for all that effort is that I
don't want all their creative stuff to be lost whenever Windows needs
reinstallation. I back up the Windows partition as a compressed image and the
creative stuff as uncompressed files.

Windows 7 uses what I take to be a Federation approach to presenting files in
virtual folders. Each virtual folder can contain standard stuff from the C:
drive and the contents of any user directories. This is a wonderful concept
destroyed by the Windows 7 implementation. As I say, I backup all the creative
stuff separately from the C: drive.

Windows 7 prevents me (even as administrator) from moving creative stuff from
the C: partition to a user directory for backing up. The OS makes it as hard as
possible to backup and restore except for the whole of the Windows installation.
It does allow incremental backup, but Windows can get compromised somewhere in
the incremental chain and it is tedious to keep working back down the chain to
find a non-compromised image.

Actually, I think that the object file store is an illusory goal. The article
mentions the interim Exchange object file store image. This is a simple string
of bytes in a file and the application presents this as individual file objects
inside virtual folder objects. Objects can be added or deleted and saved as an
object file store image. Unfortunately, the storage of the image file requires
an underlying non-object file store.

There is no real difference between the string of bytes on a hard drive with its
associated virtual file and directory table and the same thing inside an image
file, except that additions and deletions cannot be made in memory and saved out
to the hard drive.

The computer has to deal with the underlying file system if it has inadequate
RAM to hold the entire object file store image. In other words, RAM must be
larger than all the fixed storage media put together.

Still, the Windows 7 model together with file system scanning tools that can put
virtual file objects in specified virtual folders would be terrific as long as
the underlying disk file system can be transparently administered. Most media
players in all OSs will do this. Lets have a proper system-wide version. Then we
can have individual email files brought together and a virtual compression
system for email archiving.

---
Regards
Ian Al
Software Patents: It's the disclosed functions in the patent, stupid!

[ Reply to This | Parent | # ]

Federation.....
Authored by: tiger99 on Tuesday, April 02 2013 @ 01:11 PM EDT
It seems to me that this, as described, is just a Union Mount, which your favourite OS (Linux and probably xBSD) has supported for ages.

Or, the Apache Foundation has Hadoop, which also seems to work, and is rather more sophisticated.

Once again, Bill's incompetence is showing, and M$ are at the trailing edge of technology.

[ Reply to This | Parent | # ]

WinFS, Integrated/Unified Storage, and Microsoft – Part 4
Authored by: albert on Tuesday, April 02 2013 @ 05:12 PM EDT
Wow! So this is MS 'management'? It's organized like the traffic patterns in
Mumbai or Saigon. Looks there's mature, politically-entrenched bureaucracy at
'work' there.

I pictured Jobs (at Apple):

Jobs:"You're going to do this like this, that like that, and I want a
progress report by Friday!"

Team: OK

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )