| Time |
Nickname |
Message |
|
09:17
🔗
|
Schbirid |
nice, mounting the tar.bz2 in avfs took ages (>12 hours i think) but now it looks like accessing files in it is not making any noticable cpu load |
|
09:22
🔗
|
Schbirid |
and with that http://gamespy-archives.quaddicted.com/forums/ is back (still no nice frontend) |
|
11:55
🔗
|
SmileyG |
BlueMax: :D |
|
11:55
🔗
|
BlueMax |
wut |
|
11:56
🔗
|
SmileyG |
irony. |
|
11:58
🔗
|
SmileyG |
also that song is ironic. |
|
12:06
🔗
|
Coderjoe |
Schbirid: well, unfortunately, it would have needed to completely decompress the bz2, both to determine length and to parse the tar file. It might not have been using an optimal blocksort algorithm (the most compute-expensive part of the bzip2 algorithm) |
|
12:08
🔗
|
SmileyG |
o_O How much ram is it using Schbirid ? |
|
12:13
🔗
|
Coderjoe |
once it has indexed the bz2 blocks and the tar file, cpu usage would be much, much better |
|
12:15
🔗
|
Coderjoe |
Schbirid: is avfs smart enough to keep the indexing info in a file, so you can remount without the long wait? |
|
12:32
🔗
|
Schbirid |
Coderjoe: SmileyG: it wrote some 1G file to /tmp/, pretty sure it does use that only while mounted though. uses about that much ram too. oh look, it is at 100% cpu again :( |
|
12:32
🔗
|
Schbirid |
shit |
|
12:33
🔗
|
Schbirid |
oh well, as long as the rest of the server does not suffer |
|
12:34
🔗
|
Coderjoe |
the only way to avoid the massive cpu hit is to cache the decompressed results for a period of time |
|
12:35
🔗
|
Schbirid |
there are at least 3 projects named "avfs", ugh |
|
12:35
🔗
|
Coderjoe |
i noticed |
|
12:35
🔗
|
Schbirid |
yeah, that's the thing i try to avoid since hdd is very limited |
|
12:35
🔗
|
Schbirid |
http://avf.sourceforge.net/ |
|
12:36
🔗
|
Coderjoe |
the other day I went looking for it, since you mentioned the bz2 random access support and gave up with the dozens of results I found |
|
12:38
🔗
|
Schbirid |
heh |
|
13:20
🔗
|
Schbirid |
yay, googlebot is doing ~2 pages per minute |
|
13:33
🔗
|
Coderjoe |
I think you can give it a crawl delay via robots.txt |
|
13:34
🔗
|
Coderjoe |
balrog, chronomex, ersi: spread the @? |
|
13:36
🔗
|
balrog |
better? |
|
13:41
🔗
|
SmileyG |
no :( |
|
13:41
🔗
|
SmileyG |
:D |
|
13:53
🔗
|
Schbirid |
Coderjoe: no, i honestly am happy that it is going remotely quick :) |
|
13:58
🔗
|
godane |
i found a video called birth of biohazard |
|
18:24
🔗
|
Schbirid |
rdiff-backup really sucks if you move directories around |
|
23:29
🔗
|
arkhive |
I have 79 3 1/2" floppy disks of various software of the time and am wondering what is the best way to rip/backup/recover/archive them to my computer? |
|
23:34
🔗
|
winr4r |
good question |
|
23:34
🔗
|
winr4r |
that can go into sub-questions, like whether they will be readable at all, and whether there's a reason to not just get a 3.5" USB floppy drive and "dd" that motherfucker |
|
23:35
🔗
|
winr4r |
i don't have the answers to those, but they're points of discussion/research |
|
23:36
🔗
|
winr4r |
what are they? FAT disks? |
|
23:38
🔗
|
winr4r |
also, in the case that "dd that motherfucker" looks like a good option, http://www.gnu.org/software/ddrescue/ddrescue.html |
|
23:42
🔗
|
DrainLbry |
i'd buy a "dd that motherfucker" shirt |
|
23:43
🔗
|
winr4r |
with a little picture of a floppy disk above it |
|
23:43
🔗
|
winr4r |
i think i would too! |
|
23:45
🔗
|
DFJustin |
http://archiveteam.org/index.php?title=Rescuing_Floppy_Disks |
|
23:51
🔗
|
winr4r |
if it's just like, plain MS-DOS floppies though (and i do have some kicking around i've been meaning to do stuff with) |
|
23:51
🔗
|
winr4r |
is any of the advanced stuff mentioned there, vs getting a USB floppy and doing a 'ddrescue', overkill? |
|
23:55
🔗
|
chronomex |
why hello gentlemen |
|
23:55
🔗
|
arkhive |
sorry was away.. now reading messages |
|
23:55
🔗
|
chronomex |
no worries, friend |
|
23:56
🔗
|
winr4r |
good evening chronomex |
|
23:56
🔗
|
chronomex |
arkhive: a year or two ago I did a massive copy-that-floppy run |
|
23:56
🔗
|
chronomex |
I had a shellscript that ran dd and asked me what the disk said on the label, putting that in a .txt file next to the image |
|
23:56
🔗
|
chronomex |
also turned the disk image into a .zip |
|
23:57
🔗
|
chronomex |
I don't have the script still, unfortunately ... |
|
23:57
🔗
|
arkhive |
alright |
|
23:57
🔗
|
arkhive |
oh |
|
23:57
🔗
|
chronomex |
if you want to do something similar, I can provide guidance |
|
23:58
🔗
|
arkhive |
sure. |
|
23:58
🔗
|
arkhive |
I am not sure on the condition of the floppy disks |
|
23:58
🔗
|
chronomex |
aye |
|
23:59
🔗
|
DrainLib |
you'll soon find out |
|
23:59
🔗
|
chronomex |
heh, pretty much |
|
23:59
🔗
|
winr4r |
chronomex: is dust getting into the disks an issue? and can anything be done about it? |
|
23:59
🔗
|
arkhive |
and I would like to extract all the data from them.. probably both a image copy and a copy of its files |