From owner-freebsd-current Thu Jul 23 12:53:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19699 for freebsd-current-outgoing; Thu, 23 Jul 1998 12:53:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (green@zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19694 for ; Thu, 23 Jul 1998 12:53:43 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id PAA01980; Thu, 23 Jul 1998 15:53:04 -0400 (EDT) Date: Thu, 23 Jul 1998 15:53:04 -0400 (EDT) From: Brian Feldman To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: More doscmd adventures/lockups In-Reply-To: <199807231834.LAA00344@dingo.cdrom.com> 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 Alright, sorry about that. The CURRENTness is a world from a few days ago, and a kernel from 7/22/98; I don't know exactly what "options" you're referring to, but the only non-normal-and-possibly-unstable things in my kernel are: options "VM86" options SOFTUPDATES I'm pretty sure the problem wasn't with SoftUpdates... the specific conditions were bochs, an i386 emulator, installing DOS on the drive (/home/green/msdos.drv), which uses nothing special, system-wise, and doscmd, trying to boot the drive at the same time, which uses the VM86 system to run. Let me know what else you want to know. Cheers, Brian Feldman green@unixhelp.org On Thu, 23 Jul 1998, Mike Smith wrote: > > Yessiree, doscmd has ways of locking me up without a panic. I'll explore > > what happened this time: I was using my 5[0-2][0-8]mb dos drive in bochs, > > installing MS-DOS 6.22. I tried using doscmd to boot it, doscmd -bx... > > after Starting msdos... the whole computer froze, I waited a few minutes, > > and hit reset when I was sure it was locked up solid. To recap: bochs was > > loading dos on the drive, on disk 2 by now, and doscmd -bx tried to boot > > the drive; this was standard access, no vn(4) problems. > > Please, if you're going to report problems, try doing it in a fashion > that gives us something to work with. > > For example, here you haven't mentioned what level of -currentness your > system is at, or what other options you've got enabled. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message