Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!news.nsw.CSIRO.AU!mel.dit.csiro.au!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!realtime.net!not-for-mail
From: chip@unicom.com (Chip Rosenthal)
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: Re: Screend problem under BSDI 2.x
Date: 13 Aug 1996 23:39:37 GMT
Organization: Unicom Systems Development, Austin, TX
Lines: 21
Message-ID: <4ur3np$udk@news3.realtime.net>
References: <Pine.BSI.3.93.960813102058.302S-100000@babel.magic.fr>
NNTP-Posting-Host: garcon.unicom.com
X-RTcode: ec18ae32323956b48d11120e
In article <Pine.BSI.3.93.960813102058.302S-100000@babel.magic.fr>,
Edouard CORREIA <ded@magic.fr> wrote:
>screend: ioctl (SIOCSCREEN): Protocol not available
I would suspect you failed to construct a new kernel properly.
Did you:
- Install the kernel files that come with the package into your
kernel source tree?
- Modify your kernel configuration to enable gwscreen?
- Re-run config and re-make your kernel?
- Install the new kernel?
The gwscreen installation is fairly simple -- particularly since
BSDI secured permission to include a few small patchy bits in the
stock distribution. (In the old days, you needed to go patching
certain kernel files.) It is important, however, that you follow
--
Chip Rosenthal * Unicom Systems Development * <chip@unicom.com>
Unix system programming/support * Internet * test/ctrl/comm systems
URL: http://www.unicom.com/ * 48 68 D8 BE 10 C8 6B DE 60 17 00 0B A7 83 99 8E