HDTenEightyP/NetNews huggingface dataset:
From: ant@brolga.cc.uq.oz.au (Anthony Murdoch)
Subject: PCNFS and 386BSD - so close, but....
Summary: mountd returns 1007
Organization: Prentice Centre, University of Queensland
Date: Thu, 3 Sep 1992 06:09:13 GMT


Hi guys 'n gals,

I've been trying to get pcnfs to work with 386bsd in the last couple of
weeks (as some out there would already know :).  Well, I've reached a
pinicle point (ie I've hit a brick wall).

PCNFSD appears to work - the authentication process goes ahead and I am
able to mount drives on other servers (eg a SUN 670) with the same
permissions as the user I authenticated to on the 386bsd server.

BUT, I am unable to mount directories on the 386bsd server.  I know the
386bsd servers mountd works, I am able to mount its directories from the
afore mentioned SUN 670.  I have added the patches suggested for getting
nfs mounting working, so mountd doesn't freeze anymore.

When I try to connect a drive using the "net use" command, I get a NFS039F
error with a return code of 1007 (ie the mountd on the 386bsd server
refused the request with an error code of 1007).  I have been unable to
find the meaning of a return code of 1007.  I've searched the source code
of mountd and all the include files.

I've tried all sorts of variations of the exports file.  Right down to
exporting / to all (which did work before I made the fixes to mountd).
Can someone tell me what 1007 is or give me some pointers here.

Thanx in advance
ant
Newsgroups: comp.unix.bsd
Subject: Using the Source (Luke :)
From: <AI4CPHYW@MIAMIU.BITNET>
Date: Monday, 31 Aug 1992 00:21:40 EDT
Organization: Miami University - Academic Computer Service

I have a couple of kinda newbie questions about the source distribution of
386bsd 0.1, so please bear with me and don't roll your eyes _too_ much :)
 
I can make the binary distribution fly with no problems, but I haven't had
too much experience with source distributions of any OS, let alone Unix . .
 
I can get the source distribution unpacked fine (except I got an error along
the lines of "can't find script source.install, install failed" or something
like that) and I carefully read the file /usr/src/ROADMAP but when I try to
run config or make all I get is command not found errors.  Does this mean
that I have to first install the binary distribution? (i.e. the source distrib
doesn't come with the executables I need to compile the OS). If I don't need
to first install the binary distrib, then what am I doing wrong.
(For that matter, where can I get a good discussion of make, other than the
man pages, I'm not that much of a tyro :) :)
 
If I need both distributions installed, is there any way I can do it on an
80MB hard drive. I tried installing first the binary and rebooting to delete
the bin01.* files, then installing the source distribution, but the filesystem
got full.
 
In another vein, where should I look for more instructions on how to enable
incomming telnet and ftp connections.  The boot sequence "sees" my 3c503 and
ifconfig makes the thing work (I can ping, ftp, and telnet other hosts) but
if I try to ping, ftp or telnet my 386BSD machine from another machine,
I get no response.
 
Thanks for you help in advance, and thanks to Bill and Lynne and everyone
else who made this wonderful OS.
 
                      -Alec D. Isaacson
                       AI4CPHYW @ miamiu.acs.muohio.edu
                       isaacson @ rogue.acs.muohio.edu (NeXt Mail)
                       Miami University, Oxford, OH
-------------------------------------------------------------------------
Only a barbarian would eat chive cream cheese and blackberry jam on the
same bagel.                          -Spenser
Newsgroups: comp.unix.bsd
From: colin@marsh.cs.curtin.edu.au (Colin Manning)
Subject: Extracted {bin,src,etc}dist and X386?
Organization: Curtin University of Technology
Date: Wed, 26 Aug 1992 04:12:57 GMT

Hi,
	Is there anywhere that individual files from the {bin,src,etc}dist's
can be got from (anon ftp?)?

	What I am after specifiaclly is X386, xinit and xterm.  I would also 
like to see what's in the etcdist, - but I don't have the room ('cept on this
machine - but I would make my self *VERY* unpopular if I extracted 30+ Meg of
files and left them here).

	Does anyone have there 386bsd distributions extracted so that people 
who want a few files from the dist can get the files they want without needing
a spare 30+Meg of disk space?
--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
Newsgroups: comp.unix.bsd
From: fridlund@mermaid.micro.umn.edu (Jim Fridlund)
Subject: Re: Incorrect Install Procedure in FAQ
Followup-To: comp.unix.bsd
Organization: Minnesota Automated Plate Scanner Lab
Date: Mon, 31 Aug 1992 15:21:18 GMT

In article <sxjcb-300892172124@sxjcb.uacn.alaska.edu> sxjcb@orca.alaska.edu (Jay C. Beavers) writes:

> Path: news.cis.umn.edu!umn.edu!csus.edu!wupost!cs.utexas.edu!sun-barr!ames!ig!bionet!raven.alaska.edu!sxjcb.uacn.alaska.edu!user
> From: sxjcb@orca.alaska.edu (Jay C. Beavers)
>  Newsgroups: comp.unix.bsd
>  Date: 31 Aug 92 01:33:10 GMT
>  Sender: news@raven.alaska.edu (USENET News System)
>  Followup-To: comp.unix.bsd
>  Organization: University of Alaska Computer Network
>  Lines: 34
>  Nntp-Posting-Host: sxjcb.uacn.alaska.edu
>

   [other stuff deleted...]

>  In the 386BSD 0.1 FAQ revision date 09 Aug 92 there is an error in one of
>  the installation procedures.  In section 2.04, 'How do I get 0.1 installed
>  with "real" partitionning?', there is a description of how to install BIN01
>  without using the happy fun EXTRACT program.  The procedure neglects to
>  mention that you have to run a device install script after step 21, the
>  decompression of the bin01.* files.  The result of this is that /dev/kmem
>  doesn't get created, the rc script complains of its absence, and telnetd
>  refuses to allow incoming telnet sessions.

If I remember correctly, I had to run MAKEDEV.

>  The original discussion on installing 386BSD 0.1 on a 40 mb hard drive by
>  using the script:
>  # (for i in /tmp/bin01.*; do
>  > cat $i && rm $1
>  > done
>  > ) | uncompress | cpio -iadm
>  also negelcts to mention this.

I remember posting something like this back in July.

Here's how I did it:

My solution after reading the cpio (yuk) man page and getting some
help with my Bourne Shell from my friend David Zuhn was:

- Install Tiny 386BSD on the hard drive.
- Boot from the hard drive
- The extraction procedure:
        % cd /tmp
        % loadfd        # copy all the bin01.* to /tmp.  Ctrl-C when done.
        % cd /
        % (for i in /tmp/bin01.*; do
        > cat $i && rm $i
        > done
        > ) | uncompress | cpio -iadm

That should extract each bin01.?? file and remove it.  The '%' and '>'
are shell prompts.  Note:  the $i instead of $1.  Try this again.
This is how I unpacked 386BSD bindist on a 40 meg Seagate ST-251 MFM
drive.  Hope this helps.
--
Jim Fridlund                                     U of MN - Computer Science
fridlund@mermaid.micro.umn.edu                   Institute of Technology
Newsgroups: comp.unix.bsd
From: "Andrew A. Chernov, Black Mage" <ache@astral.msk.su>
Subject: Re: HELP: Can't install 386bsd-0.1 into own partition!
Keywords: 386BSD
Organization: Kurchatov Institute of Atomic Energy, Moscow
X-Natal-Chart: Sun/Virgo, Moon/Capricorn, Asc/Saggitarius
X-Tarot-Aim: Curriculum Hermetis
Date: 27 Aug 92 12:08:10 GMT

In <ache.714840717@cpuv1> I writes:

>Problem description:
>Can't install 386BSD into 0xa5 partition, but installation on whole
>disk is sucessfull.
>This bug is independent of partition size and order.

>'install' diagnostics:
>"High level... disk storage:"
>Disk parameters and partition size are correct.
>After "super-block backups ..." and its numbers 'install' says:
>newfs: ioctl (WDINFO): No such process
>newfs: /dev/rwd0a: can't rewrite disk label

I found some solution of this problem, but not a _real_ solution:

You must allow 'install' to _create_ BSD partition, don't create this
partion by hand or by "diskmanager" or by something else.
'install' can't work only when BSD partition already exist, but can
create it himself!

Very strange...

-- 
In-This-Life:  Andrew A. Chernov    |  "Hay mas dicha, mas contento
Internet:      ache@astral.msk.su   |  "Que adorar una hermosura
Organization:  The RELCOM Corp.,    |  "Brujuleada entre los lejos
	       Moscow, Russia       |  "De lo imposible?!"  (Calderon)
Newsgroups: comp.unix.bsd
From: nickel@cs.tu-berlin.de (Juergen Nickelsen)
Subject: Re: virtual tty's for 386bsd ?
Reply-To: nickel@cs.tu-berlin.de
Organization: STONE Project, Technical University of Berlin, Germany
Date: Wed, 26 Aug 1992 18:52:34 GMT

In article <colin.714801124@marsh> colin@marsh.cs.curtin.edu.au (Colin
Manning) writes:

> ado@bigcomm.gun.de (Christoph Adomeit) writes:
[...]
> >But there is one thing I really miss: Virtual consoles.
[...]
> There is iScreen.  I believe it is in the etcdist, but I got it from elsewhere.
> I can't remember where.  Try an archie search for screen.
[...]

Since you are in Germany, the best place for getting iScreen should be
its "home" server, ftp.informatik.uni-erlangen.de. It requires some
searching though, the directory structure on this server is like they
want to hide their software. :-)

Be sure to get the latest version (3.2, if I didn't miss one), since
scrollback buffers are not in 3.1. (Cut & paste is, but scrollback is
nice!)  Juergen Weiger seems to put one new feature into each version.
I like it very much, though I use it only with SunOS and 4.3 BSD, not
with 386bsd.

--
Juergen Nickelsen
Newsgroups: comp.unix.bsd
From: kilroy@mik.uky.edu (Paul S. Kilroy)
Subject: Re: [386bsd] namelist hassles
    <1992Sep2.150438.23098@nrao.edu>
Organization: University Of Kentucky, Dept. of Math Sciences
Date: Wed, 2 Sep 1992 18:17:41 GMT

In <1992Sep2.150438.23098@nrao.edu> cflatter@nrao.edu (Chris Flatters) writes:

|In article 17592@hippo.ru.ac.za, ccml@hippo.ru.ac.za (Mike Lawrie) writes:
|>Several programs on 386bsd-0.1 produce namelist error messages - what
|>does one do to fix this? I've done a pretty vanilla install of
|>{bin,src,etc}dist on a 560 Mb SCSI, 8 Mb RAM 386, and am far from being
|>a bsd expert.
|>
|>For example:
|>
|>netstat (the one referred to in the FAQ) produces "filehead or nfiles
|>not in namelist"
|>
|>netstat -r produces "rthashsize: symbol not in namelist"
|>
|>ps -aux produces "ps: nlist: can't find the following symbols: _fscale
|>_avail_start _avail_end:

|If you haven't done it already, you should rebuild the kernel.  The version
|on the distribution floppy has been stripped (so it doesn't have any symbols
|in it at all).

|	Chris Flatters
|	cflatter@nrao.edu

is there a pre-compiled kernel that i can get that is not stripped..
I am going to install bsd as soon as i get my new machine (486/33)

thanks


paul

--
                       -Paul   (kilroy@mik.uky.edu)
Newsgroups: comp.unix.bsd
From: jaak@stacken.kth.se (Jaak Lippmaa)
Subject: sysv semaphores on bsd
Organization: Royal Institute of Technology, NADA
Date: Sun, 30 Aug 1992 08:51:51 GMT

  Is there any public implementations of SYSV semaphores on BSD unix?
This semaphore stuff is quite a mess, but lot of programs are
already using them and they are needed for compatibility.

Please replay via e-mail to taavi@pm.postimees.ee

Taavi Talvik
Newsgroups: comp.unix.bsd
From: juengst@boss1.physik.uni-bonn.de (Henry G. Juengst)
Subject: Re: [386bsd] Virtual memory exhausted. Do I need more swap?
Organization: Universit"at Bonn, Informatikinstitut, R"omerstr 154, W-5300 Bonn 1
Date: Fri, 28 Aug 1992 19:07:48 GMT

In article <david.714981284@mlb.geomechanics.csiro.au>, david@mlb.geomechanics.csiro.au (David Le Blanc) writes:
> When compiling some programs with GCC, I get the message 'virtual memory
> exhausted'. I have 40Meg virtual memory, so I am sure that is not the problem.
> 
> Is there a setting with GCC which I should raise or what??
> 
> Thanks.
> 
> --
> David Le Blanc                         :
> Email: david@mlb.geomechanics.csiro.au : `Sort of a cross between a Jaguar
> CSIRO Division of Geomechanics,	       :  and a freight train.' the Alien
> P.O. Box 54 Mt Waverley 3149	       : in Alien^3.

I'm sure it's a limit problem. Use csh to set 'ulimit -h' (as root) and
'ulimit' or 'limit -h' / 'limit' to set a acceptable limit. Then start your
make again (as child process of the csh process).

This is a problem you will also find, if you try to start a XWindows program
which needs large resources. Your application fails, but the reason is
because your X (X386) was started with small limits.

Henry

-- 
juengst@boss1.physik.uni-bonn.de [131.220.221.30]
juengst@saph2.physik.uni-bonn.de [131.220.221.12]
juengst@pib1.physik.uni-bonn.de  [131.220.221.2] (strange particle)

I'm only speaking for myself, but not for anybody else !
Newsgroups: comp.unix.bsd
From: karl@NeoSoft.com (Karl Lehenbauer)
Subject: Re: An overview of 17" monitors
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Wed, 02 Sep 1992 20:07:05 GMT

Correct me if I'm wrong, but all the current HDTV proposals except for MIT's
are lower resolution than 1280x1024.

MIT's proposal looks the most interesting, in my opinion, because it is 
display-resolution independent -- it can scale compatibly, apparently, to
ever higher resolutions.
-- 
-- Email info@NeoSoft.com for info on getting interactive Internet access.
You will now awaken feeling relaxed and refreshed, remembering everything 
you've read except the details of the Omega contingency plan.
Newsgroups: comp.unix.bsd
From: rpw3@rigden.wpd.sgi.com (Rob Warnock)
Subject: Re: [386BSD]
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Sat, 29 Aug 1992 07:37:14 GMT

tj2n+@andrew.cmu.edu (Tao Jiang) writes:
+---------------
| Hi, is ka9q or related software available in 386BSD?
+---------------

Although an excellent work, KA9Q's "NOS" is not needed in 386bsd, which
already has full Berkeley networking built in. See the man pages for
rlogin, rsh, rcp, ftp, telnet, socket, etc.


-Rob

-----
Rob Warnock, MS-9U/510		rpw3@sgi.com
Silicon Graphics, Inc.		(415)390-1673
2011 N. Shoreline Blvd.
Mountain View, CA  94043
From: kapela@prism.poly.edu (Theodore S. Kapela)
Newsgroups: comp.unix.bsd
Subject: Re: time for comp.unix.bsd.386
Date: 27 Aug 92 12:22:44 GMT
Organization: Polytechnic University, New York

In article <1992Aug27.093740.29039@uniwa.uwa.edu.au> craig@ec.uwa.oz.au (Craig Richmond - division) writes:
>peter@taronga.com (Peter da Silva) writes:
>
>>FWIW, if we're going to have a bunch of comp.os.unix-alike groups, then
>>this should be comp.os.386bsd. I think it would be better to put the
>
>comp.os.UNIX.386bsd
>
>*craig screams loudly*
>

Read the INSTALL.NOTES with the 386bsd 0.1 distribution.  It reads:

	On the INTERNET/USENET, we are hoping to establish our
	own  newsgroup called "comp.os.386bsd". This newsgroup would
	reside  alongside  the  "comp.os.mach"  and  "comp.os.linux"
	newsgroups. Already there are over 100,000 copies of Release

and further down:

	by  asking  your  news coordinator to subscribe to it. We do
	not recommend using comp.unix.bsd, since 386BSD, like  linux
	and mach, is not a "comp.unix" system.


I agree with Peter.  "comp.os.386bsd"

-- 
..............................................................................
 Theodore S. Kapela				kapela@poly.edu
 Center for Applied Large-Scale Computing	
 Polytechnic University
From: michael@resonex.com (Michael Bryan)
Newsgroups: comp.unix.bsd
Subject: Re: time for comp.unix.bsd.386
Date: 27 Aug 92 09:52:50 GMT
Organization: Resonex Inc., Sunnyvale CA

In article <1992Aug27.091607.12110@resonex.com> michael@resonex.com (Michael Bryan) writes:
>Personally, I rather like Peter's recent suggestion of comp.os.posix.*

Oops!  I just noticed that Peter suggested comp.posix, and not
comp.os.posix.  Hmmm.  I could probably go either way on that one.
The comp.posix would more closely mirror the existing comp.unix
heirarchy for OS versions contained therein, where comp.os.posix would
put groups under comp.os with all other operating systems.  I'd
probably prefer comp.os.posix, but either one would be acceptable as
parents for a new 386bsd group.

-- 
Michael Bryan        michael@resonex.com                     |     ,_,
Milk and Cheese in '92!!!                                    |    /oo \
"What the world needs now are some true words of wisdom,     |    <>__|
like 'La-la-la-la-la-la-la-la-la-la'."  -- Cracker           |    |  U|
Organization: Sophomore, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA
Newsgroups: comp.unix.bsd
Date: Wed,  2 Sep 1992 09:04:24 -0400 
From: "Alex R.N. Wetmore" <aw2t+@andrew.cmu.edu>
Subject: mgr?

has anyone ported mgr to 386bsd?  Moreover, did they compile it with ega
drivers?

alex
From: rich@Rice.edu (Richard Murphey)
Newsgroups: comp.unix.bsd
Subject: Re: et4000 chipset setup for X386...
Date: 3 Sep 1992 06:47:28 GMT
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University

Here's what I use... Rich

vga256
  Chipset"et4000"
  Vendor"Orchid"
  Clocks 25 28 33 37 40 45 74 65 #Rich's Orchid ProDesigner IIs
  ViewPort      0 0
# Uncomment the next two lines to use the faster `speedup' mode.
#  Virtual1024 1024
#  Modes "1024x768i" "1024x768"
# Uncomment the next two lines to use a screen size similar to the
suns.
  Virtual1152 900
  Modes "1152x900i" "1024x768i" "1024x768" "1152x900"

ModeDB
#            clock  horzontal timing      vertical timing
"1024x768"  65    1024 1032 1176 1344    768  771  777  806
"1024x768i" 45    1024Y
064 1224 1264    768  777  785  817 Interlace
"1152x900i" 65    1152 1184 1304 1424    900  905  923  955 Interlace
"1152x900"  74    1152 1168 1464 1496    900  900  908  920
"640x480"   28     640  672  768  800    480  490  492  525
"640x480"   25     640  672  768  800    480  490  492  525
"800x600"   37     800  816  952 1056    600  608  610  633
--
From: eld@chiton.ucsd.edu (Eric Dorman)
Newsgroups: comp.unix.bsd
Subject: Quantum LP105AT IDE: Geometry change on boot?
Keywords: Quantum-105 boot-problems
Date: 26 Aug 92 01:16:09 GMT
Distribution: na
Organization: MPL of SIO at UCSD

I have followed the "won't boot from HD after installo
 because of geometry change" thread with interest, as I have 
a disk that fails boot from HD in a similar fashion.  I know 
the hardware mostly works, since I tried a build on
a Conner CP3544 (before it went and died, boo!) and it would boot fine.

I'm not even sure what this things actual geometry is!  Perhaps this
info needs to get stuffed into the BIOS user-defined disk?

Is anyone else running this disk?
Config:	ALR Business VEISA (386-33+cachepack)
	17Mb ram, WD8003E, other junk.
Help!
-- 

Eric Dorman                                          eld@mpl.ucsd.edu
Scripps Institution of Oceanography             -or- eric@siodept.ucsd.edu
University of California, at San Diego         
#include <std.disclaimer.h>
From: eje@irenaeus.mlo.dec.com (Eric James Ewanco)
Newsgroups: comp.unix.bsd
Subject: 386bsd: Doesn't use BIOS?
Date: 3 Sep 92 19:44:27 GMT
Reply-To: ewanco@kalvin.enet.dec.com
Organization: Digital Equipment Corporation


I saw mentioned in the thread on the Diamond Speedstar 24[X] interface problems
that said that 386bsd does not use BIOS and hence needs the code for the
Speedstar.  This struck me as odd; I can understand skipping the BIOS for the
sake of speed on certain devices, but why can't 386bsd use BIOS for proprietary
devices like the Speedstar?  Is it an all-or-nothing thing, that is, either we
forgo using BIOS at all or incur horrible disadvantages?  I'd like to
understand why exactly 386bsd cannot use the BIOS at all.  I guess I could
understand Diamond's hesitance to give us direct access to their hardware,
especially when everyone else probably goes the standard way and uses the BIOS
to access it.  (Then again, it is news to me that you could take advantage of
hi-res accelerated boards through the BIOS, but that's another issue.)

Eric
--
/=============================================================================\
| Eric Ewanco - Software Engineer     For the rash and outrageous opinions ex-|
| Digital Equipment Corp, Maynard MA  pressed herein I alone am responsible;  |
| ewanco@kalvin.enet.dec.com          they do not belong to DIGITAL(TM).      |
\==============================- 2 Th 2:15 -==================================/
    "...[T]he greatest and most ancient Church known to all, founded and
    organized at Rome by [] Peter and Paul, [is] that Church which has the
    tradition and faith which comes down to us after having been announced
    to men by the Apostles.  For with this Church, because of its superior
    origin, all Churches must agree ...  and it is in her that the
    faithful everywhere have maintained the Apostolic tradition."
       -- St. Irenaeus, Against Heresies, c. 180 A.D., 3,3,3.
From: pschneider@espel.picker.de
Newsgroups: comp.unix.bsd
Subject: date is 21 days ahead
Date: 29 Aug 92 12:21:19 MET
Organization: Picker International GmbH, Espelkamp

I have a strange behaviour of the date on my machine. The date is always
21 days ahead if I boot 386bsd. Under MS-DOS, the date is correct. I have
already tried different localtime links, but no difference. Has anybody
else seen this behaviour ?

Paul Schneider
----
pschneider@picker.de
From: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: install problems
Date: 25 Aug 92 20:30:07 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

I've been out of things for the last couple of months with first
illness, then a holiday then a departmental move so after finally
getting my machines on the net I thought I'd update my 0.0 to 0.1.

I get the dist.fs onto a floppy and it boots fine, recognises all my
devices and everything looks good until I type install. Bingo - Floating
point exception.

At this point there's not a lot I can do since there's no source for
install. I'll spend the rest of this night loading the 0.0 way using the
fixit.fs disk but I thought I'd better report my problem.

My machine is a noname with

	25Mhz OCTEK Hippo-486 motherboard
	ACE IDE-I/O card
	ST1144A IDE disk
	AMI Bios
	4M memory
	Trident 1M 8900 video card
	
It's going to be difficult to track down this problem since I'm not
going to use install again so does anyone have any ideas??

If there's a difference with my motherboard then I'm going to get these
exceptions again so I'd like to find out what's causing them.
-- 
  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