*BSD News Article 63318


Return to BSD News archive

Newsgroups: comp.unix.bsd.bsdi.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!psgrain!newsfeed.internetmci.com!in2.uu.net!news.new-york.net!spcuna!spcvxb!terry
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Subject: Re: BSDI and SLiRP
X-Nntp-Posting-Host: spcvxa.spc.edu
References: <Do35r9.EHH@eskimo.com>
Sender: news@spcuna.spc.edu (Network News)
X-Nntp-Posting-User: TERRY
Organization: St. Peter's College, US
Date: Mon, 11 Mar 1996 08:38:54 GMT
Message-ID: <1996Mar11.033854.1@spcvxb.spc.edu>
Lines: 19

In article <Do35r9.EHH@eskimo.com>, starcrow@eskimo.com (Mark Dreyer) writes:
>   Is there a port of SLiRP for BSDI 2.x?  I looked at ftp.bsdi.com and 
> cdrom.com to no avail.  Is someone working on this?

  I don't recall any problems getting it to compile out-of-the-box. The
only issue is that there is a bug in 2.0/2.0.1 (supposedly fixed in 2.1,
I haven't checked) that can panic the system with a "trap type 12".

  On a completely different note, does anybody have any ideas on how to
"break" a BSD/OS 2.x system so that SLiRP (and TIA, and MLINK, etc.)
won't do anything useful, while the rest of the system functions nor-
mally? I have a student system and modem pool that's being tied up by
people dialing in and running these utilities. We're not an ISP and we
don't want to have to buy more modems or restrict shell access to the
BSDI boxes.

	Terry Kennedy		  Operations Manager, Academic Computing
	terry@spcvxa.spc.edu	  St. Peter's College, Jersey City, NJ USA
        +1 201 915 9381 (voice)   +1 201 435-3662 (FAX)