From owner-freebsd-hackers Tue May 5 07:51:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27312 for freebsd-hackers-outgoing; Tue, 5 May 1998 07:51:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27299 for ; Tue, 5 May 1998 07:51:43 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id OAA01043; Tue, 5 May 1998 14:51:29 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA00916; Tue, 5 May 1998 16:51:29 +0200 (MET DST) Message-ID: <19980505165123.20240@follo.net> Date: Tue, 5 May 1998 16:51:23 +0200 From: Eivind Eklund To: "Ron G. Minnich" , hackers@FreeBSD.ORG Subject: Re: an interesting problem with pkg_add References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Ron G. Minnich on Tue, May 05, 1998 at 10:13:14AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 05, 1998 at 10:13:14AM -0400, Ron G. Minnich wrote: > Here you go: I ran the following: > pkg_add -f ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz > > Then I ^C because as usual our network connection got awful. > > As i write this, there is an rm -r running on /. I am losing my system. > I'm going to let it go because it got too far before I caught it, the I'm assuming you mean that an 'rm -rf' is going on your system? Otherwise, I can't see anywhere where it could have come from pkg_add. > It will be interesting to see how long this machine lasts with this rm > running :-) > > anyway I think this indicates a bug in pkg_add :-) I'd guess it does. Sounds like the PenLocation variable of pkg_add has been garbled somehow - this can (theoretically) happen if your quit-signal comes while the filename is being copied into that variable. This probably mean we should add some locking here - but I don't know how easy it will be to do. > Eating all of one's hard disk is hardly a good thing. Guess I'll run > linux on this machine for a while, til i get over the shock. Eating filesystems for breakfast is very bad program behaviour. BAAD program. Go sit in the corner the next two hours ;-) Actually, I guess it was lucky you were the one that was caught by this - if I've understood correctly, you have good error-recoverability. It would probably have been more of a disaster for a random user. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message