Journal AKAImBatman's Journal: Spread the word! 7
A follow up to last week's four part series is now online. Call all your friends, neighbors, relatives, blogging buddies, and Linus Torvalds to let them know!
A follow up to last week's four part series is now online. Call all your friends, neighbors, relatives, blogging buddies, and Linus Torvalds to let them know!
Always look over your shoulder because everyone is watching and plotting against you.
Slashback (Score:1)
Re:Slashback (Score:2)
I'll probably try submitting one after I get the second part of the series out. As for the second part, I'm going to attempt to accelerate the "once per week" schedule that I've been keeping. Just this once.
I was going to post this over there (Score:2)
A DBFS is not an SQL Server!
The shapes of the data differ drastically between a DBFS and an RDBMS.
DBFS ==tree
RDBMS==arbitrary 2D tuples
There is a huge impedence mis-match between the two. Not that you can't code around it.
See Celko [amazon.com]
Installation != Ease of Use
"Flexibility is the key to indecision"
It's an iceberg. Even the most advanced users want to manage things in a declarative fashion, and leave the messy imperative detail below the waterline.
In a proprietary OS, that
Re:I was going to post this over there (Score:2)
I'm surprised that you weren't able to post over there. The comments allows for most basic HTML. Where you trying to do anything odd?
The shapes of the data differ drastically between a DBFS and an RDBMS.
DBFS ==tree
RDBMS==arbitrary 2D tuples
That's not true in the case I've presented. The file system model I suggested in the articles used table-like structures instead of INode structures. There is nothing inherently heirarchical about this, thus the heirarchy must be simulated to provide the ty
Re:I was going to post this over there (Score:2)
IIUC, Reiser4's metadata will support that kind of approach. IANAKH (Kernel Hacker or Kroah-Hartman), but seriously pursuing a non-Inode hierarchical affair is going to take you into major kernel patching territory, if I got anything out of Love's book.
My (admittedly poorly c
Re:I was going to post this over there (Score:2)
, and blogspot doesn't like it.
Blogspot handles whitespace automatically. Although its handling of < and > can be a bit annoying. (They're automatically converted back to the original characters during preview.)
seriously pursuing a non-Inode hierarchical affair is going to take you into major kernel patching territory, if I got anything out of Love's book.
I've been into the kernel quite a bit as of late, and I don't think it's an issu
libferris (Score:2)
1. file changed since last scan,
2. infection most commonly found in the wild,
3. vulerabilites discover, but not yet patched,
4. seriousness of known exploits
5. ev