From owner-freebsd-hackers Mon Jan 8 16:46:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA23019 for hackers-outgoing; Mon, 8 Jan 1996 16:46:08 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA23004 for ; Mon, 8 Jan 1996 16:46:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id QAA26150; Mon, 8 Jan 1996 16:45:19 -0800 To: dennis@etinc.com (dennis) cc: hackers@freebsd.org Subject: Re: Using `ping' to diagnose network connections reasonable? In-reply-to: Your message of "Mon, 08 Jan 1996 11:57:03 EST." <199601081657.LAA18245@etinc.com> Date: Mon, 08 Jan 1996 16:45:19 -0800 Message-ID: <26148.821148319@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org Precedence: bulk > Something that i would like (and if its in there please tell > me!). is the ability to escape to a shell to do manual network > diagnostics. I've had nfs fail due to minor details and it a real About the closest I get is the fixit floppy, but that doesn't let you come back so you'd need to do *all* of it manually. Probably not what you're looking for. I have some improvements planned here, one of which may involve Joerg helping me figure out how to get the floppy back from the death-grip the system has on it in certain circumstances.. :-) > Dennis PS: got 2 more BSDI defectors last week....general comments > are "BSDI has pissed me off for the last time". :-) Jordan