From owner-freebsd-arch Thu May 2 16:23:30 2002 Delivered-To: freebsd-arch@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 10D1337B417; Thu, 2 May 2002 16:23:24 -0700 (PDT) Received: from pool0524.cvx21-bradley.dialup.earthlink.net ([209.179.194.14] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 173Pv1-0001gE-00; Thu, 02 May 2002 16:23:23 -0700 Message-ID: <3CD1CA4D.31AE5135@mindspring.com> Date: Thu, 02 May 2002 16:22:53 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Andrew R. Reiter" Cc: John Baldwin , arch@FreeBSD.org Subject: Re: savcore dump names? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Andrew R. Reiter" wrote: > On Thu, 2 May 2002, Terry Lambert wrote: > :This was really meant for someone who was upset enough that > :they were willing to revert the dump format changes at the > :same time... > : > :I was doing this: 8^p. > > Damn, then why post at all? That's crap. If you want, I can find the URL references to back out all the corresponding changes; I think it would piss Marcel off, if anyone committed them, though. If anyone is the current maitainer, it's Marcel. My personal take on "the MD5 naming problem" is: ls -lt | more You only ever really care about the datestamp, anyway, and anyone who keeps more than one dump around is either crazy, or has too many things going on at once. Obviously, there are people who disagree with this strongly enough that they're willing to flame -arch about it (and have). So: What does everyone want done so badly that they are willing to break off Poul's arm and try to beat him to death with the wet end? "Put it back" is not an acceptable answer, since it doesn't provide a forward path by describing the "correct behavior" ("the way it was" is not an adequate behavioural specification). If you want "put it back", then you can easily do that yourself with the resources I pointed at. If people could say what they want, rather than bitching about what they don't want, it'd be a heck of a lot more likely to result in patches (IMO). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message