Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!think.com!ames!haven.umd.edu!wam.umd.edu!ima
From: ima@wam.umd.edu (Linda Tamara Bresler)
Subject: 386BSD as cores and more
Message-ID: <1992Oct29.151233.13494@wam.umd.edu>
Keywords: 386BSD, as , rm
Sender: usenet@wam.umd.edu (USENET News system)
Nntp-Posting-Host: rac1.wam.umd.edu
Organization: Workstations at Maryland, University of Maryland, College Park
Date: Thu, 29 Oct 1992 15:12:33 GMT
Lines: 69
First of all thank you to Bill and Lynne Jolitz for 386BSD.
Next, thank you to everyone who has contributed to the FAQ and bug list.
I've got 386bsd up and running!
But, there are a couple of problems:
1. as cores! trap 10.
tried the hello world program:
#include <stdio.h>
main ()
{
printf("\n Hello, World.");
}
this one is desparate! without the compiler, other fixes are by
binary patch only.
2. rm cores!. the rm that came with the distribution diskette works fine.
3. ps cores! segmentation fault.
4. lpd is missing. ( this must be a faq.)
5. netstat binary from ugle.unit.no results in a Bus Error.
- cant compile the source.
6. csh $cwd doesn't work. the original directory remains in the prompt.
7. sh MAKEDEV uses awk. awk complains that its out of memory
system comfiguration:
we0: western digital WD8013EW
wd0: seagate ST-251 with western digital hd/fd cntlr
bios: AMI 1990, displays at boot:
30-0100-ZZ1277-00101111-050591-SCAMPSX-8
cpu: intel 386 sx
mem: 8 MB
pc0: ega with irq2 taped ( insulated from slot connector)
motherboard uses VLSI VL82C311 system controller in place of
the usual assortment of intel chips.
pc<color> @ 0x60 irq 1 on isa
com1 @ 0x3f8 irq 4
wd0 @ 0x1f0 irq 14
fd0 drives 0: 1.44M, 1: 1.2M @ 0x3f0 irq 6 drq 2 on isa
we0 ethernet address xx.xx.xx.xx.xx.xx @ 0x280 irq 9
386BSD 0.1.24 07/12/92 22:20
the dist.fs is dist.fs-noIS available from agate.berkeley.edu
swap is set for a little over 5MB on disk, due to cylinder alignment
on the disk.
Good News:
1. find works well.
2. the network software is up and running (ping, ftp, telnet) except for
NFS. if someone has the actual article number that would help, the
faq refers to an article between 1600 and 2100. (terry, i have found
the faq you edited to be very useful. thank you. is a new one in the
works?)
3. bad144 seems to work fine.
4. no problems with the western digital ethernet card, even though many
reported problems with the WD8013 in news articles.
all suggestions are appreciated.
thank you,
ima@wam.umd.edu