HDTenEightyP/NetNews huggingface dataset:
From: jkh@whisker.lotus.ie (Jordan K. Hubbard)
Newsgroups: comp.unix.bsd
Subject: Re: ->386bsd! man-pages.Z ?
Date: 16 Nov 92 12:59:45 GMT
Organization: /home/jkh/.organization


	Get Tom Christiansen's perl rewrite of man. ftp to convex.com.

Or, if you don't feel like hassling with perl, grab the BNR2 man port
I posted here a week or so back (I really should put it up on ref.ftp.com)..

					Jordan
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: xdm and login 
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Mon, 23 Nov 1992 17:19:59 GMT

In article <1992Nov23.154921.29674@Urmel.Informatik.RWTH-Aachen.DE> kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes:
   I'm looking for a method to use xdm to come up on my system permanently
   in a fashion similar to the way it's done on most systems, e.g. Ultrix:

   at the end of /etc/ttys:

   :0 "/usr/bin/login -P /usr/bin/Xprompter -C /usr/bin/dxsession" none on secure w
   indow="/usr/bin/Xcfb"
   :1 "/usr/bin/login -P /usr/local/xprompter-ncd -C /usr/local/start-ncd -e" none
   on secure

   What would it require? A special login program? A special init?
   Any clues?

just edit /etc/ttys and /etc/rc.local -- nothing special is needed.

From /usr/X386/lib/X11/etc/README.386BSD in the XFree86 distribution:

If you would rather run xdm on bootup, disable logins on the console
by removing `vga' from /etc/ttys, and add code like the following to
your /etc/rc.local script.

  if [ -x /usr/X386/bin/xdm ]; then
    echo -n ' xdm'; /usr/X386/bin/xdm
  fi

If you have replaced crypt on your system (see Chris Demetriou's
/usr/386bsd.errata/crypt.instructions) and use encrypted passwords,
you cannot use the supplied xdm binary.  The supplied xdm binary uses
the 386BSD 0.1's dummy crypt routine that prints the message 'Crypt
not present in system' in the xdm-errors file each time a user logs
in.  You can ignore this.  It merely tells you that passwords are
unencrypted.  US export restrictions prevent us from providing an xdm
binary with a real crypt.  If you need it, get the xdm sources
(mit/clients/xdm) and recompile it using `xmkmf -a' and `make'.

Rich Murphey 

   --
   --Chris
   Christoph P. U. Kukulies
   kuku@acds.physik.rwth-aachen.de
   *** Error code 1

   Stop.
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] Warnings rebuilding libc.a
Date: 18 Nov 92 19:35:34
Organization: Kernel Hackers 'r' Us
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: david@otago.ac.nz's message of 19 Nov 92 00:48:01 GMT

the errors w/tsort are perfectly normal...

how much RAM do you have in your system?

my system (486DX-50, 16M ram) took about 1/2 hour to compile libc
from scratch, including doing the man pages.

from "time make" in /usr/src/lib/libc:
943.8u 730.1s 31:21.72 88.9% 0+0k 0+0io 0pf+0w

also, re: it being 11k larger:

i could believe it.

the ones i just compiled:
-rw-r--r--    1 root       264602 Nov 18 19:12 obj/libc.a
-rw-r--r--    1 root       323810 Nov 18 19:20 obj/libc_p.a


and i know that these work, because i've compiled libc before, and the
recompiled libc is used in things like, say, login... 8-)


good luck,

Chris
--
Chris G. Demetriou                                    cgd@cs.berkeley.edu

"Sometimes it is better to have twenty million instructions by
        Friday than twenty million instructions per second." -- Wes Clark
Newsgroups: comp.unix.bsd
From: mm@brl.mil (Mike Markowski)
Subject: Re: Help with getting tip to work
Reply-To: mm@brl.mil
Organization: US Army Research Laboratory
Date: Mon, 9 Nov 1992 16:32:13 GMT

In article <1992Nov5.183411.28451@a.cs.okstate.edu>, yeoy@a.cs.okstate.edu (YEO YEK CHONG) writes:

|> "tip com1" didn't work for me.
|> [more tip related stuff]

I've made the tip-related FAQ fixes and also am having no luck using a
modem.  I've also tried kermit from the etc01 distribution with no success.

I have an old but working Racal Vadic VA3451 modem signed out from work.
At 1200 baud, I even tied the handshaking lines together just to see what
I'd get, and I got nothing!

Is it a com1 driver problem or, more likely, an operator problem?
Does anyone have any tip tips?  (By the way, the mouse on the 9-pin com1 port
works just fine under XFree86.)

Thanks.
-- 
Mike Markowski
mm@brl.mil
(410)278-6674
Newsgroups: comp.unix.bsd
From: karl@NeoSoft.com (Karl Lehenbauer)
Subject: Re: [XFree86]  Help needed badly
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Mon, 23 Nov 1992 04:45:32 GMT

In article <1992Nov22.203129.17299@ultb.isc.rit.edu> sxx4519@ultb.isc.rit.edu (S.X. Xue) writes:
>A suggestion I
>would give here is to redirect the errors to a file by
>	xinit >& err;sync

>then you will you some error messages that you don't see on the screen by 
>catting the file "err." In my case, I found out the permission of my mouse 
>port (com1) and the font path were not set properly.

Yes, redirecting xinit is essential to figuring out problems.

I'd like to point out, too, that even if you're not getting your card
switched into graphics code, you won't see xinit's error output unless
you save it off.  

In my case it couldn't find the entry in the modem DB.  Now we're up
with a Farenheit 1280!

-- 
-- Email info@NeoSoft.com for info on getting interactive Internet access.
"Turn on your hot tub by email now.  Ask me how."
From: paul@tvt-k (Paul Pries)
Newsgroups: comp.unix.bsd
Subject: Re: XFREE 86 installation
Date: 23 Nov 92 07:11:54 GMT
Organization: >Televerket Utbildning, Utf

adasal@netcom.com (Salvatore Collora) writes:

>Hi all.

>I got the sources for XFree 86, and I uncopressed it and detarred it
>in accordance with the readme file.  Everything went fine.

>When I went to run x386install   it gave me the following error:

>[:No match

The "[" is used in Bourne shell instead of the word "test".
Try running the X386install through a bash or sh, and make sure there is
a space on each side of the "[" and "]".

>No matter what I do I get this error.  Needless to say I am frustrated.
>It took forever to FTP 20 megs worth of stuff to have it not work.

>Any remedy would be appreciated...

>Salvatore Collora
>LMU Systems Integration
> 

Hope it helps.

Paul Pries
--
email: 5322@msg.abc.se      (Short email only, not more than 500 lines :-))
Newsgroups: comp.unix.bsd
From: genek@mentor.cc.purdue.edu (Gene Kim)
Subject: Screen utilties (blanker, 132 col, etc.) for 386BSD?
Organization: Purdue University
Date: Mon, 16 Nov 1992 03:05:20 GMT

    There sure seems to be a growing wealth of utilities for
386BSD!  However, I can't seem to find any mention of a simple
screen-blanker that blanks the screen after a specified keyboard
idle time is reached.  Does any such beast exist (that doesn't
run under X)?

    Similarly, is there a utility to kick a VGA card into a 132
column mode?

    For those of us who don't have X up and running yet, these
utilities would be invaluable, no?

Thanks in advance!
Gene
Newsgroups: comp.unix.bsd
From: tching@target.uucp (Tracy Ching <SysAdmin>)
Subject: Has anyone loaded 386BSD on a EISA Compaq 486?
Followup-To: poster
Organization: cdwr
Date: Mon, 23 Nov 1992 21:27:59 GMT

	I'm trying to load 386BSD on my 486 EISA Compaq but it loads
a few sectors or tracks and goes into a hard reboot.  Anyone ever heard
of this problem?  Anyone have a solution?  (short of getting a different
PC)  There are no extra cards in the PC... Only the necessities...
VGA, floppy HD cntrl, mem expansion, WD8013 e-net.  That's it.  I used
the dist.fs for the western digital card.

tching@water.ca.gov

Newsgroups: comp.unix.bsd,comp.lang.tcl,alt.sources
From: jkh@esel.lotus.com (Jordan K Hubbard)
Subject: CODRV EXPERIENCES [was Re: XFree86 problems (keyboard hangs overnight)]
Organization: Lotus Ireland
	<veit.721670337@du9ds3>
Distribution: comp
Date: 16 Nov 92 09:57:46


	I am becoming quite tired now to to say that all of this is covered by "codrv". 
	Get the keycap-0.1.1.tar.Z stuff from ftp.uni-duisburg.de (134.91.100.14).
	Read README*, FAQ.ddmmyy, and BUGLIST.ddmmyy there.

Actually, in an attempt to be somewhat fair (after jumping all over
Herr Dr. Veit for suggesting that hacking the pccons driver was a
complete waste of time), I installed the keycap stuff over the
weekend.  This is what I encountered:

The instructions assume you don't have anything at major 0x0F - this
is obviously not going to be the case for everyone, so bias the
instructions accordingly.

codrv, as distributed, does not seem to compile on its own.  You need
to grab pcmmap() from pccons.c in order to get the kernel to link.  I
haven't checked to see if it's ever called, but I doubt it is.

Everything seems to work as far as the console driver is concerned,
but I was unable to get the Xfree86 1.1 driver to work at all.  I
applied all the 1.1 patches (successfully) and recompiled the server
to codrv support enabled, but got 'unable to map /dev/vga' upon
running it (with the server suid root, of course).  I didn't
have time to debug it, so I've switched back to the old pccons
driver (with my hacks) for now.

Perhaps when the X11 support is more functional I'll go back to it.
Has anyone gotten this to work?
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject: xdm and login 
Keywords:  xdm /etc/ttys login
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Mon, 23 Nov 92 15:49:21 GMT


I'm looking for a method to use xdm to come up on my system permanently
in a fashion similar to the way it's done on most systems, e.g. Ultrix:

at the end of /etc/ttys:

:0 "/usr/bin/login -P /usr/bin/Xprompter -C /usr/bin/dxsession" none on secure w
indow="/usr/bin/Xcfb"
:1 "/usr/bin/login -P /usr/local/xprompter-ncd -C /usr/local/start-ncd -e" none
on secure

What would it require? A special login program? A special init?
Any clues?

--
--Chris
Christoph P. U. Kukulies
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.

Newsgroups: comp.unix.bsd
From: burgess@hrd769.brooks.af.mil (Dave Burgess)
Newsgroups: comp.unix.bsd
Subject: The SCSI Controller saga continues...
Date: 17 Nov 1992 10:01:26 -0600
Organization: Armstrong Lab MIS, Brooks AFB TX
Distribution: world
NNTP-Posting-Host: hrd769.brooks.af.mil

OK, here goes.

  Jim Henrickson and I have managed to get 386bsd to recognize the Ultrastor
24F Hard drive controller in our Gateway machines.

  (A cheer rises from the crowd...)

Now for the bad news.  Neither of us can boot from it.  Here are the symptoms:

  1)  Power up tests pass, the SCSI search is completed, and the hard drive is
properly identified.  The controller is also identified as ID 7, and appears
to be correct.

(Here comes the spooky part)

  2)  If a floppy is in the disk drive, the system will boot, and identify the
hard disk controller as IRQ 14, 0x1f0.  Isn't that the combo for the IDE drive?
The hard drive is then mountable, fillable, fsckable, etc01.*-able, etc.  Every
check seems to work, all systems go.  But only as wd0*.  Remember, this is an
SCSI drive.

  3)  If there is no floppy in the disk drive, the system tries (as you would
expect) to boot off the floppy.  Failing that it accesses the hard drive.
The system dies.  Locks up.  Freaks.  Fails.  C-A-Detete has no effect. One 
time, the 'RESET' button didn't even work.

  (A frightened moan rises from the crowd...)

Here comes the question.  

Huh? 

  I have tried every boot block set I can find, including the fs{boot}fs, just
for grins.  None of them seem to help.  What I think I need is an {as,sd}boot
set that thinks it's an IDE drive (or a wdboot that works like a SCSI)?  
Any good suggestions at this point would be really appreciated.  

  Failing that, is there a way to boot from floppy and set the root device to
the hard drive?  There sits, in the back of my mind, a nagging thought that
says 'Yes, you could do it on the Cromemco'.  Surely, 386bsd is better than
Cromix :-).


TSgt Dave Burgess

Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: At boot: file too big to load
Organization: Weber State University  (Ogden, UT)
Date: Mon, 23 Nov 92 22:09:35 GMT

In article <1992Nov23.070212.9393@tfs.com> julian@tfs.com (Julian Elischer) writes:
>In article <1992Nov22.225044.1344@ghost.dsi.unimi.it> serini@ghost.dsi.unimi.it (Piero Serini) writes:
>>Hi.
>>At the end I succeeded recompiling that damn kernel.
>>A little problem still keeps me unhappy: if I install the new
>>kernel in /386bsd, at boot time bootas tells me: file too big to load.
>>
[ ... ]
>I'll bet that if yu do a 'size' on the kernel,
>it shows that the sum of the partitions in the file are bigger than that.
>don't forget the zero filled section is not in the file, it just bzeros it.
>
[ ... ]
>The only answer is to have a kernel that can load above 1MB
>otherwise it and the loader have to fit in the 640k window.
>bill jolitz says 0.2 will be able to do this.
>I frequently have to decide what to leave out of the kernel
>to add some other feature.

You can load larger than 1 Meg kernels by loading above 1 Meg with Julians
boot code.  You lose the memory below 1 Meg unless you hack to add it back
into the free pool.

The main "gotcha" is giving a "link-to" address when building the kernel,
since this isn't automatic.

This works just fine for me with 1.0.

Julian's boot code also has the advantage of allowing you multiple load
devices (like other SCSI disks) without changing anything else... although
this won't make things like ISC UNIX (which requires the boot partition be
the active one so it can find itself) happy.


					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: hado@leland.Stanford.EDU (Ha Do)
Subject: Re: [XFree86]: Performance Problems
Keywords: XFree86 X11 X-windows X386
Organization: DSG, Stanford University, CA 94305, USA
Date: Fri, 20 Nov 92 01:28:24 GMT


Farenheit 1280 card:
Orchid tech. has several graphic cards such as F1280, Prodesigner II and
a new one F1280-SA (?). Which card has which kind of S8 chips on it, could
somebody tell me ? and will Amacio's XS3 support current as well as new
S3 chips ? (The 1280-SA is the one with "voice" feature).
What is the new S3 chip coming in a month  that has several times the 
performance of current S3 chip ?
I need to know since I am about to buy one of the Orchid card and want
to pick the best one.
Thank you

Newsgroups: comp.unix.bsd
From: frank@martha.utcc.utk.edu (frank segner (phrank))
Subject: Re: [386BSB] All network ports in use.
Organization: University of Tennessee Computing Center
X-Newsreader: Tin 1.1 PL3
Date: Mon, 16 Nov 1992 03:12:42 GMT

c.kuhtz@data-hh.comlink.de (Christian Kuhtz) writes:
: Hi,
: 
: I can only log in on three ttyp's. screen says no more PTYs and
: telnetd: All network ports in use. But I need a few more, at least 10
: ports. Please help me! I had to get rid of this problem !
: 
: How should I creat more ports ? by MAKEDEV ? how ?

try to replace 'pseudo-device pty 4' by 'pseudo-device pty 16'
in /sys/i386/conf/YOURCONFIGFILE     ;-}
and, of course, recompile the kernel...

so long
          frank
From: cssjs2@ufhx1.ufh.ac.za (Mr I Scheepers)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd list of bad patches: patch00019 -> SC_ERROR?
Date: 17 Nov 92 07:48:53 GMT
Article-I.D.: ufhx1.1992Nov17.074853.2556
Organization: University of Fort Hare, Alice, Ciskei

In <RICH.92Nov15135940@omicron.Rice.edu> rich@Rice.edu (Richard Murphey) writes:

>In article <1992Nov14.223035.14857@jpusa1.chi.il.us> stu@jpusa1.chi.il.us (Stu Heiss) writes:

>   Which patches are bad and why...


>patch00019 slip

I'm getting a compile error on patch00019: 
	in ../../net/if_sl.c: In function slinput:
	Line 634: `SC_ERROR' undeclared
The offending line is
		
		sc->sc_flags |= SC_ERROR;

Any clues?
Newsgroups: comp.unix.bsd
From: kapela@prism.poly.edu (Theodore S. Kapela)
Subject: Broken patched init (Was Re: 386BSD or LINUX?)
Organization: Polytechnic University, New York
Date: Fri, 20 Nov 92 14:10:26 GMT

In article <1992Nov17.045443.20013@cs.chalmers.se> augustss@cs.chalmers.se (Lennart Augustsson) writes:
>In article <1992Nov4.131541.15661@prism.poly.edu> kapela@prism.poly.edu (Theodore S. Kapela) writes:
>>the bad buffers back to disk, writing over the fixes made by fsck (using the
>>raw partition).  I haven't really had a chance to check this out yet.
>Add the line
>	trap : 15
>at the start of /etc/rc to fix the problem.  reboot send SIGTERM to all
>processes and it is not ignored by default by the shell.  (One one the 58
>patches caused this behaviour.)

I came across a note about one of the patches in the patchkit, which also fixed
my problem.  There is a missing semicolon as part of the 
"send SIGTERM, sleep, send SIGKILL" patch to init.  Replacing the 
semicolon fixed this problem. (Near line 234 in init.c, I beleive).


-- 
..............................................................................
 Theodore S. Kapela				kapela@poly.edu
 Center for Applied Large-Scale Computing	
 Polytechnic University
Newsgroups: comp.unix.bsd
From: richardl@iat.holonet.net (Richard Levenberg)
Subject: m* and docs
Organization: HoloNet (BBS: 510-704-1058)
Date: Fri, 20 Nov 1992 04:58:32 GMT

Are there docs or mans on the m group of executables (i.e. mread, 
mwrite, mdir) I have used them successfully but it is a shot in the
dark?

richardl@holonet.net

Newsgroups: comp.unix.bsd
From: karl@NeoSoft.com (Karl Lehenbauer)
Subject: Re: XFREE 86 installation
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Mon, 23 Nov 1992 04:01:03 GMT

In article <1992Nov22.233347.2343@netcom.com> adasal@netcom.com (Salvatore Collora) writes:
>I got the sources for XFree 86, and I uncopressed it and detarred it
>in accordance with the readme file.  Everything went fine.

>When I went to run x386install   it gave me the following error:
>[:No match
>
>No matter what I do I get this error.  Needless to say I am frustrated.

cd /bin
ln test '['

Did you get 386BSD 0.1?  I remember having to do that back on 0.0, but not 0.1.
-- 
-- Email info@NeoSoft.com for info on getting interactive Internet access.
"Turn on your hot tub by email now.  Ask me how."
Newsgroups: comp.unix.bsd
From: sbartram@xzaphod.com (Scott Bartram)
Subject: looking for port of PPP to 386BSD
Organization: XZaphod in Rockville, MD
Date: Thu, 19 Nov 1992 22:54:57 GMT

Has anybody done the port? If so, where can I find it?

scott

-- 
=======================================================================
Scott Bartram
sbartram@xzaphod.com
uunet!xzaphod!sbartram
From: deraadt@newt.cuc.ab.ca (Theo de Raadt)
Newsgroups: comp.unix.bsd
Subject: 386BSD: fstat bug?
Date: 18 Nov 92 13:14:16 GMT
Organization: little lizard city

I think fstat has a bug.

[gecko yp 4 ]# ps agux
ps agux | grep bind
root       710  0.0  0.0   172    0 p1  S+    6:58AM    0:00.11 grep bind
root       689  0.0  0.0   200    0 p0  S+    6:55AM    0:00.17 ./ypbind
[gecko yp 5 ]# fstat -np 689
USER     CMD          PID   FD  DEV    INUM       MODE SZ|DV
root     ypbind       689   wd  5,1   81729      40700    512
root     ypbind       689    0  0,0    3113      20620   5,0
root     ypbind       689    1  0,0    3113      20620   5,0
root     ypbind       689    2  0,0    3113      20620   5,0
root     ypbind       689    3* internet dgram udp fe30b414
root     ypbind       689    4* internet stream tcp fe322414
root     ypbind       689    5* internet dgram udp fe30b394
[gecko yp 6 ]# l /var/yp/binding/cuc.ab.ca.2
-rw-r--r--    1 root           16 Nov 18 06:55 /var/yp/binding/cuc.ab.ca.2
[gecko yp 7 ]# ./testlock /var/yp/binding/cuc.ab.ca.2
-1 35
[gecko yp 8 ]# ./testlock /etc/passwd
0 0

I know for a FACT that this process has file descriptor 7 open. (fd 7
is being used to keep a shared-lock on /var/yp/binding/domainname.2 so
that user level processes can access YP fast. It's a Sun hack.)

See how fd 6 is not open? I think fstat has a bug. Someone else want to
deal with this one? I'll go roll in the snow (yes, there's snow outside)
if there's no bug!

Those of you who are excited by the word "ypbind", just hold onta yer
herses fer a little mer time, eh feller? Sooon...

Those who would flame me because "YP is such a terrible system", need
not bother sending flames. (I'm writing it from scratch, I know how bad
it is.) For those who care, I'm trying to make YP perform better than it
does on any other machine (except perhaps Solaris.)
 <tdr.
--

This space not left unintentionally unblank.		deraadt@newt.cuc.ab.ca
Newsgroups: comp.unix.bsd
From: vixie@pa.dec.com (Paul A Vixie)
Subject: Re: [386bsd] NNTP or INN
Organization: DEC Network Software Lab
Distribution: comp.unix.bsd
Date: 19 Nov 92 10:23:43

> not too long ago someone posted that INN was a better news server than
> NNTP as far as 386bsd is concerned, where do I find this program?

that was me.  get it from gatekeeper.dec.com:~ftp/pub/news/inn.
--
Paul Vixie, DEC Network Systems Lab	
Palo Alto, California, USA         	"Don't be a rebel, or a conformist;
<vixie@pa.dec.com> decwrl!vixie		they're the same thing, anyway.  Find
<paul@vix.com>     vixie!paul		your own path, and stay on it."  -me
From: babraham@unpcs1.cs.unp.ac.za (Bobby Abraham)
Newsgroups: comp.unix.bsd
Subject: 386bsd at missing
Keywords: at 386bsd
Date: 20 Nov 92 07:42:43 GMT
Organization: Dept. Computer Science, UNP
NNTP-Posting-Host: pc030.cc.unp.ac.za


I don't have the binary or source code for "at" on my 386bsd.
Can this be true ?  Are they available ?

-------------------------------------------------------------------
Bobby Abraham
Dept. of Computer Science
University of Natal, Pietermaritzburg
email - babraham@unpcs1.cs.unp.ac.za
        abraham@unpsun1.cc.unp.ac.za
-------------------------------------------------------------------
Newsgroups: comp.unix.bsd