HDTenEightyP/NetNews huggingface dataset:
From: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: Re: Corrupted directory
Date: 15 Oct 92 13:53:47 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

In article <Bw4Fv7.M4L@unx.sas.com> sastdr@torpid.unx.sas.com (Thomas David Rivers) writes:
|
|Regarding this infinite reboot cycle; I recently applied the entire
|beta patchkit (from a new, clean, installation of 386bsd 0.1) and
|began getting this problem.
|
|I.e. If I have to shut down for some reason, or the power goes out; the
|     machine reboots.  Root gets fsck'd and repaired; and the
|     machine reboots again.  Then there is another problem with the
|     fsck of root, and the machine reboots, etc... encountering the
|     same problem over and over.
|
| I've now seen this happen on two machines to which I applied the beta
| patchkit.  It did *not* happen on these machines using the kernel I 
| had patched together from news articles.   This means (at least to me)
| there is some patch applied by the patchkit which I had not otherwise
| applied in my kernel, that is causing the problem.
|
| I've seen it on a SCSI disk and IDE disk, so I don't think it's in the
| driver... could it be some of the changes to init.c?
|

This is what I've experienced too. On another machine which I patched by
hand I've had no problems. Since this was a new installation I thought
I'd try the patchkit. I installed all the patches on a clean src and all
of a sudden I get these corrupted directory problems. They're easy to
reproduce so there's obviously a bug somewhere. The only other
difference between these two machines is that the older one has "real"
partitioning whereas the new one was set up using install. Since David
now thinks it's the patchkit that probably eliminates the partitioning
difference.

Anyway, thanks to those who pointed out clri to me. I lost a few files
but eventually got a clean filesystem. Thanks.


-- 
  Paul Richards at Cardiff university, UK.

  spedpr@uk.ac.cf.thor	Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk
  UUCP:     spedpr@cf-thor.UUCP or ...!uunet!mcsun!uknet!cf!thor!spedpr
+++
Newsgroups: comp.unix.bsd
From: rodeen@buddha.ncc.umn.edu (Rick Odeen)
Subject: [386BSD] System's not finding/using swap
Organization: Nutrition Coordinating Center, University of Minnesota
Date: Thu, 15 Oct 1992 04:53:24 GMT

I'm currently bringing up a system using Terry's "HP Vectra/starlan" kernel
and am experiencing a problem with the system not finding my swap space.
During the inital boot sequence I get the following message:

Oct 15 00:29:38 manray /386bsd: warning: no swap space present (yet)

After which I tried adding a swap line to my /etc/fstab and ran swapon -a
which produced the following message:

Oct 15 00:33:56 manray /386bsd: adding swap: failed! (unchanged)

I have entries in the /dev directory for wd0b and rwd0b.

Anyone have any suggestions?  Having no swap space (and only 4 meg of ram)
makes things like compiling, etc kind of difficult  :-)

Here is the output of disklabel -r wd0:

# /dev/rwd0d:
type: ESDI
disk: micro
label: pack1
flags:
bytes/sector: 512
sectors/track: 35
tracks/cylinder: 15
sectors/cylinder: 525
cylinders: 1222
.
.
8 partitions:
#        size   offset    fstype   [fsize bsize   cpg]
  a:    21000        0    4.2BSD      512  4096    16 	# (Cyl.    0 - 39)
  b:    21000    21000      swap                    	# (Cyl.   40 - 79)
  c:   641550        0    unused        0     0       	# (Cyl.    0 - 1221)
  d:   641550        0    unused        0     0       	# (Cyl.    0 - 1221)
  h:   596925    42000    4.2BSD      512  4096    16 	# (Cyl.   80 - 1216)


-- 
"MINIX costs $169, but the license allows  | Rick Odeen 
making two backup copies, so the effective | richard.odeen@umn.edu 
price can be under $60."                   | rodeen@buddha.ncc.umn.edu 
         - ast@cs.vu.nl (Andy Tanenbaum)   |
Newsgroups: comp.unix.bsd
From: gtoal@ibmpcug.co.uk (Graham Toal)
Subject: Re: 386BSD + MS-DOS
Organization: The IBM PC User Group, UK.
Date: Sun, 11 Oct 1992 01:41:08 GMT

In article <1992Oct11.002954.29581@mccc.edu> pjh@mccc.edu (P. J. Holsberg) writes:
>I have access to a lab full of 386 PCs running MS-DOS and a Novell
>network. Would it be feasible to partition their HDs and install 386BSD?
>Would that require reformatting and re-installing all the MS-DOS
>software? Would 386BSD's networking work over Novell network hardware?

The easiest thing is to have novel/dos on a boot floppy and 386 bsd on the
hard disk.  Unless you've bought nfs for novell, the only useful thing
you'll be able to do from bsd to novell is ftp, which you can set up
on a spare dos machine with either ka9q or ncsa telnet.  (I prefer
ka9q because ncsa telnet has a bug - all directories get weird
names, eg system becomes .ystem - if there's a fixed ncsa someone
please tell me)

G
-- 
Xref: sparky comp.unix.bsd:7266 comp.windows.x:17749
From: at626@cleveland.Freenet.Edu (Dave Strout)
Newsgroups: comp.unix.bsd,comp.windows.x
Subject: List of XFree86 Video Boards
Date: 12 Oct 1992 13:20:10 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Reply-To: at626@cleveland.Freenet.Edu (Dave Strout)
NNTP-Posting-Host: hela.ins.cwru.edu


All--

I was shopping for a video board to run XFree86 on, but didn't have a list
of what boards worked w/ it (I hesitate to say "supported").  Anyway, I
made a list out of modeDB.txt and an emacs macro.  Here it is, hope it's
useful. 

dave.

SuperVGA Card			Chip Set 	Resolution
-------------------------	--------	----------
2-the-MAX VGA 4000		ET4000		800x600
ATI VGA-Wondercard		ATI		640x480
BOCA Research
w/ 1M				ET4000		1024x768i
w/ 512K				ET4000		840x624
Cardinal 700, 1M		ET4000		1024x768
Cardinal ET4000, 1M		ET4000		1024x768
CompuAdd HiRez, 1 Meg		ET4000		1024x768i
Diamond Spdstar w/ HIcolor	ET4000		1024x768
Diamond Spdstar II+
(Direct from Gateway 2000)	ET4000		1152x900
Diamond SpdStar Plus w/ 1M	ET4000		1024x768
Diamond SpdStar Plus
 High Color			ET4000		1024x768
Diamond SpdStar Plus
 High Color (1M)		ET4000		1024x768
EIZO VA41 1Mb			ET4000		1024x768
Everex Viewpoint NI w/ 512K	ET4000		832x624
GA-200 Local Bus Card		ET4000		1152x900
Micro-Labs Ultimate
 VGA/HiColor 2.0		ET4000		1152x910
Optima VGA			ET3000		800x600
Optima MEGA VGA-Sync 
(H3Z 3081)			ET4000		1040x772
Orchid Prodesigner II		ET4000		800x600
Orchid ProDesigner IIs		ET4000		1024x768
Orchid ProDesigner IIs
 board date code 12/91		ET4000		1024x768
Rainbow SVGA w/ 1M		ET4000		1024x768i
STB Powergraph, 1 Meg		ET4000		1024x768i
STB Powergraph ERGO, 1 Meg	ET4000		1024x768
Swan SVGA Adapter, 
 Model VGA/16, 1 Meg		ET4000 		1024x768i
SWAN sVGA (with VCO chip)	ET4000		1024x768
Trident JAX-8214		TVGA8900	1024x768
Tseng et4000 UN-4010		ET4000		1024x768
Tseng Highcolor 72Mhz		ET4000		1024x768
Tseng Intl MegaEva/1024		ET4000		1144x858
Tseng Intl VGA ultra		ET4000		1120x840
VGA4031				ET4000		1120x840
VGA4031				ET4000		1024x768
-------------------------	--------	----------

An 'i' at the end (e.g 1024x768i means "interlaced").

I take no responsibility for the completeness of this, no endorsement or
lack of endorsement is intended by inclusion or omission, I don't speak for
the authors of xFree86 or any derivative works, no ozone-depleting CFCs
were used in the preparation of this, your mileage may vary, etc.
-- 
Dave Strout          <at626@cleveland.freenet.edu>
"Thompson's Rule for First Time Telescope Makers:
It is faster to make a four-inch mirror then a six-inch
mirror than to make a six-inch mirror."
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: software ported to 386bsd
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Wed, 14 Oct 92 18:54:12 GMT

I just saw the list of software ported to BSD/386 go by in this newsgroup.
Is anyone maintaining a similar list for 386BSD?  It seems to me that this
would be pretty useful thing to have.

	Chris Flatters
	cflatter@nrao.edu

Newsgroups: comp.unix.bsd
From: hlu@eecs.wsu.edu (H.J. Lu)
Newsgroups: comp.unix.bsd
Subject: Re: Sun/386BSD Cross Compiler?
Date: 7 Oct 92 17:52:56 GMT
Article-I.D.: serval.1992Oct7.175256.13113
Organization: School of EECS, Washington State University

In article <7636@skye.ed.ac.uk>, richard@aiai.ed.ac.uk (Richard Tobin) writes:
|> In article <1992Oct5.204631.8172@tinman.mke.ab.com> tdphette@mke.ab.com (Thad Phetteplace x4461) writes:
|> >I've been thinking it would be really handy if I could use one of my
|> >SPARCstations to compile 386BSD code (in particular X386).
|> 
|> Cross-compiling isn't too difficult a problem - gcc2 can be configured
|> as one.  I believe I sent out some patches to BSD's ld to use it as a
|> cross-linker (it doesn't handle byte-order differences correctly)
|> about 6 months ago, but I no can no longer find them.
|> 
|> However, cross-building X looks rather tricky, due to the complicated
|> configuration process.  For example, it builds and then runs imake 
|> so you have to arrange for that to be compiled for the host machine,
|> rather than the target.
|> 

I cross-compiled X11R5 for Linux. It is kind of tricky. X11R5 was not designed
with cross-compiling in mind. You have to be very careful about a few details.
Finally, I managed to make X11R5 for Linux.

|> If your problem is disk space, you might find it easier to put your
|> 386BSD machine on the net and nfs-mount a filesystem from the Sun.
|> 
|> -- Richard
|> -- 
|> Richard Tobin,
|> AI Applications Institute,                                R.Tobin@ed.ac.uk
|> Edinburgh University.


H.J.
From: richard@aiai.ed.ac.uk (Richard Tobin)
Newsgroups: comp.unix.bsd
Subject: Re: Sun/386BSD Cross Compiler?
Date: 7 Oct 92 11:43:47 GMT
Organization: AIAI, University of Edinburgh, Scotland

In article <1992Oct5.204631.8172@tinman.mke.ab.com> tdphette@mke.ab.com (Thad Phetteplace x4461) writes:
>I've been thinking it would be really handy if I could use one of my
>SPARCstations to compile 386BSD code (in particular X386).

Cross-compiling isn't too difficult a problem - gcc2 can be configured
as one.  I believe I sent out some patches to BSD's ld to use it as a
cross-linker (it doesn't handle byte-order differences correctly)
about 6 months ago, but I no can no longer find them.

However, cross-building X looks rather tricky, due to the complicated
configuration process.  For example, it builds and then runs imake 
so you have to arrange for that to be compiled for the host machine,
rather than the target.

If your problem is disk space, you might find it easier to put your
386BSD machine on the net and nfs-mount a filesystem from the Sun.

-- Richard
-- 
Richard Tobin,
AI Applications Institute,                                R.Tobin@ed.ac.uk
Edinburgh University.
Newsgroups: comp.unix.bsd
From: Matt Mannhardt <lasmtm@Arco.COM>
Subject: nfs:  'mountd' hangs, must ^c...
Organization: ARCO Alaska, Inc.
X-Useragent: Nuntius v1.1a2
Date: Wed, 7 Oct 1992 23:17:18 GMT

Well I've finally got 386BSD installed and working, including X386 and
just
started the last test on my list, nfs.  I uncommented the line in
/etc/netstart
and rebooted,  'init' gets to 'mountd' and hangs till I '^c'.   Same
symptoms 
when I login as 'root' and issue the /sbin/mountd command.  Found the
mountd.c 
src and did a 'make' on it and tried the new executable, same....  

I'm not an NFS guru (Apollo sys Admin, don't use NFS much at all) so I'm
running
out of idea.  Any help would be appreciated...

-Matt Mannhardt    - WL7CDE
lasmtm@arco.com

- Any opinions in this posting are my own and not those of my employer.
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: XFree86 problems on 386BSD
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Wed, 7 Oct 1992 15:59:07 GMT

In article 12104@nrao.edu, cflatter@nrao.edu (Chris Flatters) writes:
>I'm having some problems with the monochrome X server from XFree86 1.1 (downloaded
>from agate).  Specifically, X386mono will display its startup messages, switch
>the vga to graphics mode (displaying a few random dots) and then terminate after
>about one second.  No core dump appears to have been generated.

Boy, do I feel stupid!

I had used the default font path for Xconfig.sample which references a
font directory that doesn't exist in the binary distribution for 386BSD
(/usr/X386/lib/fonts/Speedo).  The X server won't set the font path if
the default font path contains a directory that doesn't exist.  If it
doesn't set an initial font path it can't find any fonts and refuses to
work.

	Chris Flatters
	cflatter@nrao.edu

Newsgroups: comp.unix.bsd
From: stark@cs.sunysb.edu (Gene Stark)
Subject: Bell on XFree86
Organization: SUNY at Stony Brook Computer Science Dept.
Distribution: comp
Date: Wed, 14 Oct 1992 18:06:14 GMT

I got XFree86 running with no more than the usual number of hassles, but
there is one thing I haven't figured out, and that is that clients seem
unable to sound the console bell.  For example, I can get xterm to produce
a visual bell (too slow to be useful), but no audible "feep".

Has anyone else had this problem?  What did I miss?

							- Gene Stark
From: pdac@quantime.co.uk (Peter Da'Costa)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD won't boot with AMI BIOS/Gateway 2000
Keywords: AMI Gateway 2000
Date: 15 Oct 92 18:05:16 GMT
Organization: Quantime Ltd, London

In article <1992Oct14.225619.26784@ccu.umanitoba.ca> rahardj@ccu.umanitoba.ca (Budi Rahardjo) writes:
>boehme@unvax.union.edu (Eric M. Boehm) writes:
>
>>I have seen oblique references to a problem with AMI BIOS in other
>>messages. I recently upgraded my BIOS from 030389 to 050591. 386BSD
>>still won't boot. The drive light comes on and stays on. Ctrl-Alt-Del
>>won't regain control -- time for the red button.
>
>I haven't seen (heard) anybody can get 386bsd up and running on a
>Gateway machine. I have posted twice, but the only responses I have
>were me too mails.
>I phoned Gateway tech. rep. and he knows nothing of 386BSD.
>I guess we (gateway owner) are stuck. I guess I should stick with Linux then.
>
>-- budi
>-- 
>Budi Rahardjo <rahardj@ccu.umanitoba.ca>
>Unix Support - Computer Services - University of Manitoba

  I have a Gateway 2000 25MHz 386 at home. It has an AMI BIOS (I don't
know the revision date, but I bought the machine about 2 years ago).
I have been running 386BSD 0.1 fine for quite some time. The only
problems I've had with it are due to the bad sectors on my EDSI drive.

  If anyone could point me to some patches to enable bad144 to work
(especially for swap partitions) I'd be most grateful (Oh, I'd like
to have  support for two controllers too).
-- 
--------------------------------------------------------------
Peter Da'Costa					Quantime Ltd
EMAIL: pdac@quantime.co.uk			67 Maygrove Rd
PHONE: +44 71 625 7222				London NW6 2EG
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.unix.bsd
Subject: Re: Ethernet Western Digital Troubles
Date: 8 Oct 92 21:06:19 GMT
Article-I.D.: fcom.1992Oct8.210619.2718
Distribution: usa
Organization: Weber State University  (Ogden, UT)

In article <1992Oct8.132736.22989@rwwa.COM> witr@rwwa.com writes:
>In article <1992Oct7.221654.21141@Arco.COM>,
>   Matt Mannhardt <lasmtm@Arco.COM> writes:
>
>| I've used both WD and SMC  "elite 16" NIC's and the both work great;
>| as long as you don't soft boot.
>
>Incidentally, there was discussion some time ago about the failure of
>ethernet *after* a warm reboot.  I think someone (Terry?) identified the
>problem, but I don't remember a solution...  I don't see it mentioned in the
>patchkit listing either...
>
>Is there a fix for this?

No, but the method to go about fixing it (at least the one I prefer) was
suggested by Holger, and replied to as being suitable for this purpose
by me earlier today.

I can't take credit for identifying the problem, but the gist of it is that
the card isn't told to shut up when the system is shut down, so it fails
probe on startup.

If the problem is that it is checksumming card memory as well as ROMs, then
adding "option WDCOMPAT" and rebuilding the kernel *might* fix it as a side
effect.

The real fix is to have the "halt" mechanism prior to reboot shutdown the
card, which would require the addition of a "shutdown" or "haltio" routine
for each device driver, and then leave it NULL for most devices.  This
would be a change away from standard BSD, and may not be a good thing
because of that.

The need to do this is an artifact of having to do "pretend" probe routines
for the device due to the nature of the ISA bus; otherwise a forcible reset
in the "attach" on "probe" success would work.  The problem is the "probe"
is dependant on the current device state.  An "EISA only" 386BSD wouldn't
have to have this drwback if the use of ISA cards were diallowed.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: alan@ulka.zso.dec.com (F. Alan Jones)
Subject: Re: Adding Swapspace ??
Reply-To: alan@ulka.zso.dec.com (F. Alan Jones)
Organization: Digital Equipment Corporation
Date: Fri, 16 Oct 1992 16:27:29 GMT


>Is there a way to add that much swap-space without making a new filesystem
>i.e. just recompile the kernel ?

I believe the answer is no.  There may be a way to figure out how much
swap space you have configured.  Look for the file swapvmunix.c in your
kernel object files directory.  That will tell you which device swap
is configured to run on.  Then do something like chpt -q on ULTRIX.  I
think I have tried this command and had it not work.   In any case try
to read what the current partition table is and see how much space is
allocated to the device on which your swap is configured.  If it is
smaller than you want, and the rest of the disk is taken up with the
root and/or /usr filesystem,  I'm afraid you will have to rebuild from
scratch.

Alan
From: pbd@runyon.cim.cdc.com (Paul Dokas)
Newsgroups: comp.unix.bsd
Subject: It actually works (almost 8-)
Date: 8 Oct 92 18:45:23 GMT
Organization: ICEM Systems, Inc.

Well, I've compiled X11R5 (pl17 with XFree1.1) and it actually works
on my machine (386-40, Diamond SpeedStar+, 8MB 1542B, 1.5GB of disk)
I'm quite impressed (although now I need a monitor greater than 14")

But there only two catches.  I can't get PEX or the shape extentions
to work properly.  PEX gobbles up lots of memory and starts the machine
to swapping so badly that nothing responds.  Even after 10 minutes of
waiting I was not able to reclaim my Xserver.  I guess that PEX just
requires a lot of memory (more than I've got anyway).

Shape extentions almost works.  oclock for example, comes up with the
window manager title bar and a white circle.  Then it just sits there,
nothing is ever drawn onto the white circle.  It also slows down my
Xserver quite a bit while it is running.

Anyone have any suggestions about fixing these things?

BTW, for those of you who asked me, here is the disk space requirements
for X11R5.  All results are in 512Kb blocks as given by 'du':

  170151   ftped MIT distribution (mit-[1234].*, contrib-[123].* and fixes)
  265396   mit directory:  source, objects and executables (created with 'make World')
   41769   /usr/bin/X11
   40897   /usr/lib/X11 (around 43000 with the X libraries in /usr/lib/lib*.a)
    5074   /usr/man (only expanded X libraries)
  ------
  523287   total (around 260MB for me, your mileage may vary)

-- 
#include <std.disclaimer>
#define FULL_NAME                          "Paul Dokas"
#define EMAIL                              "pbd@runyon.cim.cdc.com"
/* we are realizing infinite possibilities in exchange for our soul */
From: dean@ksr.com (Dean Anderson)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD gethostbyname change
Date: 12 Oct 92 19:12:44 EDT
Organization: Kendall Square Research

In article <1992Oct5.125237.5267@slustl.slu.edu> ejh@slustl.slu.edu (Eric J. Haug) writes:
>I became tired of not being able to boot 386bsd and mount the two
>NFS partitions because the ethernet bridge was down, or the name server
>was not up to date, so i changed the way hostname lookup fails.
>Any comments?
>eric
>In the file gethostnamadr.c in src/lib/libc/net at around line 281
>#if	0	/* get rid of this, in favor of ...   ejh@slustl.slu.edu */
>		if (errno == ECONNREFUSED)
>			return (_gethtbyname(name));
>		else
>			return ((struct hostent *) NULL);
>#else
>			/* always check the local host table */
>		return (_gethtbyname(name));
>#endif

I think the best solution is to have a configuration file ala
Dec's /etc/svcorder file, to determine in which order
databases should be checked.  This gives the administrator control
over what happens, but has the disadvantage of requiring a file access.

		--Dean
--
Dean Anderson			dean@ksr.com  |  I'm not voting because the
KSR Computing Facilities                      |  lack of a candidate has
Kendall Square Research                       |  co-opted me out of the process
From: stripes@pix.com (Josh Osborne)
Newsgroups: comp.unix.bsd
Subject: Re: Sound Blaster Pro driver (re-post)
Date: 12 Oct 92 16:59:29 GMT
Organization: Pix Technologies -- The company with no adult supervision

In article <BvzMx7.95B@pix.com> lidl@pix.com (Kurt J. Lidl) writes:
>A word of warning.  Josh didn't finish whacking together a
>"play" command (I just hack on things, Josh *programs* :-)  We also

Don't let him fool you, he isn't a bad programmer, he just doesn't
enjoy it enough.  The "play" program _should_ convert Sun/NeXT audio
files to SB Pro 8bit linear samples and send them to /dev/dsp.  If
you can't wait for me to finsh it (I won't be able to hack on it
until about the same time Kurt gets back). but want to play Sun/NeXT
audio samples get "SPARCstation Sound Tools" written by Jef Poskanzer
(jef@well.sf.ca.us) abd use the ulawtolinear program to convert to
16bit ASCII format, then just read each value, shift out the low byte and 
add 128, send that to /dev/sb_dsp (or modify the ulawtolinear code to
do it dirrectly).  That will play the samples just fine, but will convert the
file header to an anoying crakle.  Oh yeag, you will have to set the sample
rate to 8000 using the supplyed cdsp program.

The play program I was working on apparenytly was revealing bugs in the 
sound blaster driver's ioctl handling.

[...]
>Also, the port of the driver, or something that it interfaces to in the 386BSD
>system, seems to be pretty unstable.  Both playback of FM voices and
>digitized sounds seem to work pretty good.  Recording frequently
>crashes the system.  You gets what you pays for.

Also using anythign other then the supplyed programs to do ioctl's results
in a panic next time you do heavy disk I/O (like a make), that's what was
preventing me from finshing the play code...
-- 
           stripes@pix.com              "Security for Unix is like
      Josh_Osborne@Real_World,The          Multitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
We all agree on the necessity of compromise.  We just can't agree on
when it's necessary to compromise.       - Larry Wall
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Newsgroups: comp.unix.bsd
Subject: Re: Problems with Kermit 5a
Date: 9 Oct 92 13:45:10 GMT
Organization: Nanyang Technological University - Singapore
X-Newsreader: TIN [version 1.1 PL6]

I have almost solved the problem by using the pc entry in the TERMCAP.
THE problem is due to wrong termcap entry.
	The termcap for our ultrix machine comes with pc entry which 
does not work when I delete lines. It is left with @.
	I was trying to transfer pc3 into my TERMCAP variable in .profile. 

Will it work?

--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet
Newsgroups: comp.unix.bsd