Date: Fri, 11 May 2001 23:15:09 +0200 From: Roelof Osinga <roelof@eboa.com> To: Rasputin <rara.rasputin@virgin.net> Cc: stable@freebsd.org Subject: Re: What gives? Message-ID: <3AFC565D.AECE9C5F@eboa.com> References: <3AF9F4E8.52A31C48@eboa.com> <20010510050737.A2285@xor.obsecurity.org> <3AFB3C14.A6FB45AA@eboa.com> <20010511094813.A20755@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Rasputin wrote: > > >... > > -rw-r--r-- 1 root wheel 1955761 May 10 00:30 gnome > > -rw-r--r-- 1 root wheel 636835 May 10 02:46 kde2 > > Freaky - those two both work for me. > > Sounds like your ports tree is shafted, because the ports work for others. Interesting suggestion. Never mind the obvious 'how could it have been shafted?', but rather point out how one can verify the state of ones port collection. Please :). Each tarball has an unique MD5 hash. Each port release has the distinfo file with the MD5's it has been based upon. Hence each port can verify if the tarball fetched is the right one. Alternatively it can check if needed needed stuff like libs or execs are present. Yet how can a sysop check the correctness of the collection itself? As well as supporting utilities, of course. Just wipe /usr/ports and refetch the whole shebang? Coupled with a CVSup of the source, is it advisable to also wipe the /usr/src tree? Or are there diagnostic tools? Would be nice since that would be a nice first step in the diagnostic process. Roelof -- _______________________________________________________________________ eBOAź est. 1982 http://eBOA.com/ tel. +31-58-2123014 mailto:info@eBOA.com?subject=Information_request fax. +31-58-2160293 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AFC565D.AECE9C5F>