From owner-freebsd-current Mon Mar 16 22:06:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03405 for freebsd-current-outgoing; Mon, 16 Mar 1998 22:06:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03393; Mon, 16 Mar 1998 22:06:38 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id BAA00352; Tue, 17 Mar 1998 01:02:01 -0500 (EST) (envelope-from root@danberlin.resnet.rochester.edu) Date: Tue, 17 Mar 1998 01:02:01 -0500 (EST) From: Daniel Berlin To: Michael Hancock cc: Karl Denninger , current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No no no, haven't you been watching those IBM commercials? It was probably the malicious hackers who can break through routers blocking their packets, cover their tracks and unleash viruses all over your computer in a matter of seconds, unless you are using IBM certified solutions. I bet it was them. Damn hax0rs. But seriously, i have just started to see a couple weird filesystem related things since building a kernel a couple hours ago and rebooting a couple times that weren't happening yesterday. arghghghgh --Dan On Tue, 17 Mar 1998, Michael Hancock wrote: > Is it possible that the previous kernel quietly trashed your disks and it > didn't manifest itself until after the last vm fix commit? > > Regards, > > Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message