Read Linus's explanation of why this isn't viable- basically paraphrasing, the kernel (specifically vfs) tries to cache as much inode information in memory as possible to improve performance.
This isn't a bug on ext2 (or ext3 or all other supported fs's), this is a failing of how dump works.
Kludging the vfs to enable this older method of backup doesn't seem quite viable considering the performance benefits you get from the caching.
seriously? I go to UW-madison, and at least in the earlier course's (upto 400 level), they're practically documentation natzi's...
Don't get me wrong, I agree... I've delt with entirely too much code that's become my responsibility that has crap for documentation, but the documentation we're required to do on our submitted code is a little bit anal...
Somebody please explain to me, how I can hit the frigging lameness filter and every other damned filter known to man, yet AC fools can hop on and spout some of the most amazing trolling I've ever seen.
Lets face it, fusion power took a bit of a hit in it's credibility w/ the whole cold fussion thing...
Just curious, reading through the article, and it really doesn't describe much... just states that they're making progress and this leaner solution has solved technical problems- anybody got any info on what tech problems?
After reading the article, I interpreted it as that cd player's use error correction to average/interpolate it to or at least close to its original value;
the thing to consider though, is from the sounds of the article it might be that when trying to rip the cd, no error correction, and it either reads the data, or craps out for that section.
good idea if the cd-rom is able to read it, screwed if it craps out.
the problem with this is fairly simply though, consider if they're using a list of auroral finger prints for the songs and only allowing those through that match, what if I, a DJ hobbyist wanted to share my music? I'd be screwed royally because it'd only be allowing a small portion through, and only that which it knows is alright.
true, it beautifully takes care of being sued (only thing they're allowing is stuff they've checked already), but that'd serve as a sort of additional death for napster, because napster has always had that element of finding something new, something few or nobody knows about.
Slashdot Mirror
I hate that snippet of error msgs. Totally unusable without compilation failures proceeding it.
You're going to file that at bugs.gentoo.org, right?
install libvorbis, or compile from source...
Nice Lewis Black reference in the sig...
Alternatively, just use a different syslogger- say metalog for instance, which writes in blocks rather then 'each and every.'
Read Linus's explanation of why this isn't viable- basically paraphrasing, the kernel (specifically vfs) tries to cache as much inode information in memory as possible to improve performance.
This isn't a bug on ext2 (or ext3 or all other supported fs's), this is a failing of how dump works.
Kludging the vfs to enable this older method of backup doesn't seem quite viable considering the performance benefits you get from the caching.
seriously? I go to UW-madison, and at least in the earlier course's (upto 400 level), they're practically documentation natzi's...
Don't get me wrong, I agree... I've delt with entirely too much code that's become my responsibility that has crap for documentation, but the documentation we're required to do on our submitted code is a little bit anal...
Somebody please explain to me, how I can hit the frigging lameness filter and every other damned filter known to man, yet AC fools can hop on and spout some of the most amazing trolling I've ever seen.
Lets face it, fusion power took a bit of a hit in it's credibility w/ the whole cold fussion thing...
Just curious, reading through the article, and it really doesn't describe much... just states that they're making progress and this leaner solution has solved technical problems- anybody got any info on what tech problems?
bad news... last I knew, Looking Glass had gone out of business...
After reading the article, I interpreted it as that cd player's use error correction to average/interpolate it to or at least close to its original value; the thing to consider though, is from the sounds of the article it might be that when trying to rip the cd, no error correction, and it either reads the data, or craps out for that section. good idea if the cd-rom is able to read it, screwed if it craps out.
the problem with this is fairly simply though, consider if they're using a list of auroral finger prints for the songs and only allowing those through that match, what if I, a DJ hobbyist wanted to share my music? I'd be screwed royally because it'd only be allowing a small portion through, and only that which it knows is alright. true, it beautifully takes care of being sued (only thing they're allowing is stuff they've checked already), but that'd serve as a sort of additional death for napster, because napster has always had that element of finding something new, something few or nobody knows about.