I have been wondering about this, but I figured I would have to put it together myself: Are there any checksum programs that integrate with package managers?
Specifically, I am thinking about Debian packages with md5sums. Separating the files verifiably changed by package would be helpful in tracking unexpected file modifications (due to lower volume) and for noting unsigned packages (not everything in Debian is signed yet).
Yup, it's worked for me. Checking my notes, I compared aide to tripwire 1.2 last September; I was annoyed by tripwire filling out unrequested fields. Going from memory: I think tripwire was _much_ slower than aide with similar options chosen (multiple checksums).
This was before version 2 came out; I never got around to checking that out. Aide is up from 0.7 to 0.9, at least. 0.9 seemed a little faster than 0.7.
As a disclaimer: I'm not sending the output of Aide to a database, or to another machine, or anything very fancy; I'm just getting a flat text file and running version tracking on that.
The only downside is that the filesystem will sync every 5 seconds or so, which completely destroys any possibility of ever letting the disks spin down for power saving, but that's more of a laptop issue than a server issue.
If you mount it with the noatime option, then it won't constantly rewrite the last access time for files; this means that your disks can spin down again. It's worked for me.
Look, when this website goes all crazy and destroys your computer, kills your pet, sleeps with your significant other, digs up all your old poetry and laughs and laughs, then calls up your friends and reads them all those really embarrassing parts out of your journal, like when you said you were "destined for beauty" or some shit like that, we make no guarantees and will simply join with everyone and laugh at your sorry ass, because damn, there's no freaking warranty here. Get it? No warranty. None. At all.
Yup. I went back to the version of eLinks that was in Debian stable because the new Links version lacked persistent cookies & it couldn't work with my bookmarks.
I forgot about this comment for a while...
Re: Seems like a good idea.
on
Ghost for Unix
·
· Score: 2, Informative
They can use different compression schemes to trade off space vs the size of backups. They already offer gzip and bzip2, I think, so lzop should be easily added - that is very quickly compressible and decompresses obscenely fast, several megabytes per second on a P133.
It isn't a federal matter, it's a state matter. Check out ageofconsent.com . In California, it's 18; in lots of states, it's 16, and a couple of states have 14 as the age of consent of a partner if you're young enough.
There are places that donate computers; one I'm familiar with is at accrc.org. I know that they have Pentium-level machines at hand, and they have passed along many donated computers.
The mplayer suite includes mencoder. Check the docs. The MPEG4 stuff uses the libavcodec library from the FFMPEG project; I've heard that it compares favorably to DIVX 5 & Xvid.
The same site has some technical papers up. From skimming them, it looks like they take the least audible bit of digital audio at set times for set durations, and encode suggested filters. The filters are most useful at times of extreme volume - loud or quiet. Even if you have to output to 16-bit depth, you might have a choice on dithering type, producing specific acoustic effects.
Like albums and Dolby noise reduction cassettes, there are complementary filters for encoding or decoding; it's just more complex than an equalization.
Update to self: Thanks to the new Package Tracking system, I read a better info page on libsafe and re-read a policy problem: libsafe isn't building on Alpha.
I'm surprised; I checked libsafe's availability under Debian, and although it's in my local package list, it's not downloadable for testing or stable, but it does have an version in unstable. It currently breaks scrollkeeper.
It was in Mort, which I have handy, just having read it again a couple of days ago:
"Practically anything can go faster than Disc light, awhich is lazy and tame, unlike ordinary light. The only thing known to go faster than ordinary light is monarchy, according to the philosopher Ly Tin Wheedle. He reasoned like this: you can't have more than one king, and tradition demands that there is no gap between kings, so when a king dies the succession must therefore pass to the heir instantaneously. Presumably, he said, there must be some elementary particales - kingons, or possibly queons - that do this job, but of source succession sometimes fails if, in mid-flight, they strike an anti-particle, or republicon. His ambitious plans to use this discovery to send messages, involving the careful torturing of a small king in order to modulate tthe signal, were never fully expounded because, at that point, the bar closed." (p. 16 of the HarperTorch paperback, by the way)
He strikes me as cool. He broke into Yahoo News last year (Google cache) and wrote some great quotes from Attorney General Ashcroft, about "the haunting specter of inner-city minorities with unrestricted access to literature, and through literature, hope" and "They shall not overcome. Whoever told them that the truth shall set them free was obviously and grossly unfamiliar with federal law."
If you're not convinced he's not a stereotypical l337ist, check out some picturesofhim. He's cool.
Ext3 in ordered mode was my first thought. I'm comfortable with the stock kernel - after crashes (and on regular intervals), I don't think I've had to intervene with the fsck at bootup. If you'd prefer more QA, then you might examine the patches that, say, RedHat and Debian provide in their kernels, and stick with one.
Well, I use a SUSE version of LILO for cool animations at bootup. I have a few kernels in the startup menu - the version installed by Debian, and various versions of 2.2 & 2.4 (in case the new one, say, doesn't properly load sound, apm, or pcmcia drivers). But I do tend to keep a rescuecd or two around anyway.
I'd like to add two things: You can backup the drive image too, so if the file is irreplaceable and corrupted, you can try more than one recovery method safely. Also, to fsck/, "touch/forcefsck" and reboot.
Each node would store encrypted chunks of data; without a map of the chunks that make up a file, it wouldn't be able to reconstruct the original file. So a node could get infected by a virus, but the virus couldn't infect the chunks. If you put a file together from chunks from nodes that are infected, the reassembled file is not infected (unless you backed up an infected file).
>> My point there being that we (in this case Debian users) are pretty much being forced for either jump ship or *trust* a fix...
Not to repeat myself, but: If you're using woody - debian testing - add this to your/etc/apt/sources.list: deb http://security.debian.org woody/updates main contrib non-free and you can get OpenSSH 3.3.
This doesn't really help with Potato. Um. Hey, you can get Mozilla 1.0 there too!
If you're using woody - debian testing - add this to your/etc/apt/sources.list: deb http://security.debian.org woody/updates main contrib non-free then the usual apt-get update; apt-get upgrade.
Slashdot Mirror
I have been wondering about this, but I figured I would have to put it together myself: Are there any checksum programs that integrate with package managers?
Specifically, I am thinking about Debian packages with md5sums. Separating the files verifiably changed by package would be helpful in tracking unexpected file modifications (due to lower volume) and for noting unsigned packages (not everything in Debian is signed yet).
Yup, it's worked for me. Checking my notes, I compared aide to tripwire 1.2 last September; I was annoyed by tripwire filling out unrequested fields. Going from memory: I think tripwire was _much_ slower than aide with similar options chosen (multiple checksums).
This was before version 2 came out; I never got around to checking that out. Aide is up from 0.7 to 0.9, at least. 0.9 seemed a little faster than 0.7.
As a disclaimer: I'm not sending the output of Aide to a database, or to another machine, or anything very fancy; I'm just getting a flat text file and running version tracking on that.
Ooooh.
Am I missing the importance of safety scissors & Elmer's glue? Or are the links on the parentheses around linkcat just for kicks?
If you mount it with the noatime option, then it won't constantly rewrite the last access time for files; this means that your disks can spin down again. It's worked for me.
Yup. I went back to the version of eLinks that was in Debian stable because the new Links version lacked persistent cookies & it couldn't work with my bookmarks.
I forgot about this comment for a while...
They can use different compression schemes to trade off space vs the size of backups. They already offer gzip and bzip2, I think, so lzop should be easily added - that is very quickly compressible and decompresses obscenely fast, several megabytes per second on a P133.
> You mean there's another 3 lynx users out there? I'm not alone!
Heh. I'm using links right now; it does tables, frames, and mouse clicks.
It isn't a federal matter, it's a state matter. Check out ageofconsent.com . In California, it's 18; in lots of states, it's 16, and a couple of states have 14 as the age of consent of a partner if you're young enough.
There are places that donate computers; one I'm familiar with is at accrc.org. I know that they have Pentium-level machines at hand, and they have passed along many donated computers.
1.) Microsoft has already filed patent applications for this process (pretty likely, I think), in which case Lucky Green will be too late.
FYI: He has spoken with the people at Microsoft who should know about that sort of thing. (Google cache) They claimed no knowledge of related work.
The mplayer suite includes mencoder. Check the docs. The MPEG4 stuff uses the libavcodec library from the FFMPEG project; I've heard that it compares favorably to DIVX 5 & Xvid.
Like albums and Dolby noise reduction cassettes, there are complementary filters for encoding or decoding; it's just more complex than an equalization.
Update to self: Thanks to the new Package Tracking system, I read a better info page on libsafe and re-read a policy problem: libsafe isn't building on Alpha.
I'm surprised; I checked libsafe's availability under Debian, and although it's in my local package list, it's not downloadable for testing or stable, but it does have an version in unstable. It currently breaks scrollkeeper.
"Practically anything can go faster than Disc light, awhich is lazy and tame, unlike ordinary light. The only thing known to go faster than ordinary light is monarchy, according to the philosopher Ly Tin Wheedle. He reasoned like this: you can't have more than one king, and tradition demands that there is no gap between kings, so when a king dies the succession must therefore pass to the heir instantaneously. Presumably, he said, there must be some elementary particales - kingons, or possibly queons - that do this job, but of source succession sometimes fails if, in mid-flight, they strike an anti-particle, or republicon. His ambitious plans to use this discovery to send messages, involving the careful torturing of a small king in order to modulate tthe signal, were never fully expounded because, at that point, the bar closed." (p. 16 of the HarperTorch paperback, by the way)
If you're not convinced he's not a stereotypical l337ist, check out some pictures of him. He's cool.
Ext3 in ordered mode was my first thought. I'm comfortable with the stock kernel - after crashes (and on regular intervals), I don't think I've had to intervene with the fsck at bootup. If you'd prefer more QA, then you might examine the patches that, say, RedHat and Debian provide in their kernels, and stick with one.
Well, I use a SUSE version of LILO for cool animations at bootup. I have a few kernels in the startup menu - the version installed by Debian, and various versions of 2.2 & 2.4 (in case the new one, say, doesn't properly load sound, apm, or pcmcia drivers). But I do tend to keep a rescue cd or two around anyway.
Um, unless of course this is a collection & obituary sent back in time...
I'd like to add two things: /, "touch /forcefsck" and reboot.
You can backup the drive image too, so if the file is irreplaceable and corrupted, you can try more than one recovery method safely.
Also, to fsck
From what I remember about Mojo Nation:
Each node would store encrypted chunks of data; without a map of the chunks that make up a file, it wouldn't be able to reconstruct the original file. So a node could get infected by a virus, but the virus couldn't infect the chunks. If you put a file together from chunks from nodes that are infected, the reassembled file is not infected (unless you backed up an infected file).
>> My point there being that we (in this case Debian users) are pretty much being forced for either jump ship or *trust* a fix ...
/etc/apt/sources.list:
Not to repeat myself, but:
If you're using woody - debian testing - add this to your
deb http://security.debian.org woody/updates main contrib non-free
and you can get OpenSSH 3.3.
This doesn't really help with Potato. Um. Hey, you can get Mozilla 1.0 there too!
If you're using woody - debian testing - add this to your /etc/apt/sources.list:
deb http://security.debian.org woody/updates main contrib non-free
then the usual apt-get update; apt-get upgrade.