Date: Tue, 6 Feb 1996 20:36:50 -0800 (PST) From: invalid opcode <coredump@nervosa.com> To: Frank Durda IV <uhclem@nemesis.lonestar.org> Cc: hackers@freebsd.org, current@freebsd.org Subject: Re: sup%d is broken - I agree Message-ID: <Pine.BSF.3.91.960206203402.3773B-100000@nervosa.com> In-Reply-To: <m0tjzAx-000CCzC@nemesis.lonestar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I agree, a method of checksums (filesize, crc, etc.) should be used in order to find the latest copy. I thought sup already did this? Or does it only check dates? Chris Layne, coredump@nervosa.com. > As I understand sup, it doesn't look for changes the instant you pull > stuff down, but does a scan at regular intervals. If that is true, > read on. > > I remember a tool that would cut a snapshot of a directory structure and > a file of checksums that could be used to make sure the tree is intact. > (It may have been an alias for a "find | sum" combination, I don't recall.) > > Why not have some other app generate a sanity file just prior to sup > synchronizing itself? The file would contain the "correct" tree > structure, along with checksums of the files. Then the file would be > available to both the mirrors (and mortals), would get sup'ed down as > any other file, and could be used for detecting incomplete, corrupted, > absent and extra files in their local trees by running a similar > scan locally. > > > Frank Durda IV <uhclem@nemesis.lonestar.org>|"The Knights who say "LETNi" > or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" > ^------(this is the fastest route)|"A what?" > or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960206203402.3773B-100000>