HDTenEightyP/NetNews huggingface dataset:
From: ccml@hippo.ru.ac.za (Mike Lawrie)
Newsgroups: comp.unix.bsd
Subject: Re: xdm not running because cannot find crypt.
Date: 7 Oct 92 05:23:17 GMT
Article-I.D.: hippo.1992Oct7.052317.8908
Organization: Rhodes University, Grahamstown, South Africa

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

>In article <1aqnsrINNivm@gossip.pyramid.com> dinesh@pyramid.COM (Dinesh Jalisatgi) writes:
>    When I run xdm on X386 it fails saying that crypt not found.  When loaded the system using

>    extract bin01  it didnot load crypt. Does crypt come with the system or.


Some posted this some time back:-


|ftp.cs.tu-berlin.de
|
|Directory:
|
|pub/os/386BSD/386bsd-0.1/unofficial/local/xdm-crypt.engel.Z

This clears the problem, but adds another. This xdm looks for binaries
in /usr/bin/X11, so mkdir /usr/bin/X11 and ln -s everything into
/usr/X386/bin. While you are about it, do likewise for /usr/lib/X11 into
/usr/X386/lib/X11.

However, I cannot get xdm to allow me to login - the ownership of
/dev/vga oscillates between my user-id and root.

Mike
-- 
Mike Lawrie                                    <ccml@hippo.ru.ac.za>
Director, Computing Services                   ph +27 461 22023 x 279
Rhodes University, Drostdy Rd                  fx +27 461 25049
Grahamstown 6140, South Africa
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: [XFree86] crypt how to, new session manager
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Wed, 14 Oct 1992 04:52:07 GMT

In article <1992Oct13.115238.1@max.u.washington.edu> anything@max.u.washington.edu writes:
   I have a couple questions concerning XFree86 on 386bsd-0.1

    1.) I made the necessary changes to run crypt on my machine.
   what changes do I need to  make to XFree86 so that it works with
   crypted passwords?

Unless you insist on running xdm, nothing.

If you need xdm, you will have to recompile it.  Since you already
have the XFree86 binary distribution, you only need the sources in
mit/clients/xdm.  Just run 'xmkmf -a' and 'make' to recompile xdm.

   2.) I need a better session manager, I am not very knowledgeable
   about X but surely there must be a session manager that will allow
   me to start programs and such without having to start them from an
   xterm

You can program twm to use menus bound to mouse buttons in your .twmrc.
The xview binary distribution on nova.cc.purdue.edu might also have
something a little more elegant.  Rich
From: jones@acsu.buffalo.edu (terry a jones)
Newsgroups: comp.unix.bsd
Subject: 386BSD and DOS partitioning help.
Date: 8 Oct 92 15:43:02 GMT
Organization: UB


	I have checked through the FAQ and did not see this type of
thing covered there.  I was hoping someone could outline the steps
required to get DOS 5.0 and 386BSD to co-exist on the same drive
without using the standard install procedure.  The setup works fine
if you want to live with the partitioning scheme established by
install.  I have not been able to manually disklabel a drive that
already has a DOS partition, disklabel tends to wipe out the partition info.
Can this be done?


	Thanks,
	Terry Jones		jones@cs.buffalo.edu
Organization: Stanford Linear Accelerator Center
Date: Tuesday, 13 Oct 1992 11:34:52 PST
From: <CALT@SLACVM.SLAC.STANFORD.EDU>
Newsgroups: comp.unix.bsd
Subject: kermit for 386BSD

I am looking for Kermit for 386BSD. Any suggestions?
Thanks!

Ching Shih
shih@cithex.caltech.edu
Newsgroups: comp.unix.bsd
From: stripes@pix.com (Josh Osborne)
Subject: Re: Sound Blaster Driver for 386BSD
Organization: Pix Technologies -- The company with no adult supervision
Date: Tue, 13 Oct 1992 11:27:32 GMT

In article <1992Oct13.020214.7458@ntuix.ntu.ac.sg> eoahmad@ntuix.ntu.ac.sg (Othman Ahmad) writes:
>Josh Osborne (stripes@pix.com) wrote:
[...]
>And Mediavision of Pro Audio Spectrum will let other OEM manufactures similar
>cards and let people know about its interfaces.

While I think the people at Creatave Labs do some scummy things, they *DO*
make most of the interface to their cards public (only stereo recording
has been omitted from their docs, and I think it may have just been omitted
from the hardware...).

>	Anyone want to develop a SCSI driver for it as well so that we can
>use its fast CDROM as well. I wonder what sort of SCSI chip does it use?

Zilog Z5380.  Anyone have docs on the chip?
-- 
           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
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: 386BSD gethostbyname change
Organization: Weber State University  (Ogden, UT)
Date: Tue, 13 Oct 92 17:58:12 GMT

In article <SIMON.92Oct13143208@liasg2.epfl.ch> simon@lia.di.epfl.ch (Simon Leinen) writes:
>In article <16807@ksr.com> dean@ksr.com (Dean Anderson) writes:
>
>   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.
>
>If you want to avoid the additional file access, you can define a new
>/etc/resolv.conf option (this is what SGI did in IRIX 4.0).

This seems to me to be the most reasonable... I liked the idea of it being
configurable, but hated the idea of an additional file open/read/close on
a failure to resolve.  I distinctly liked the idea of searching the local
/etc/hosts first, since Sun seems to do this and I'm happy with my Sun
machines, but I understand the argument for configurability.  This seems
to adequately address all the issues.  If there are no objections, I'll
code it up and set it loose on an unsuspecting world. 8-).


					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
-------------------------------------------------------------------------------
Xref: sparky comp.unix.bsd:7557 comp.unix.ultrix:7669 comp.unix.solaris:256
From: braham@csc.umist.ac.uk (j braham levy)
Newsgroups: comp.unix.bsd,comp.unix.ultrix,comp.unix.solaris
Subject: Re: Unix with real time performance ?
Date: 16 Oct 92 15:50:52 GMT
Organization: Manchester Computing Centre
Originator: braham@horatio.csc.umist.ac.uk

From article <1992Oct14.003850.10076@pt.com>, by jjg@pt.com (John Grana):
> In article <1992Oct10.211721.5925@decuac.dec.com> mjr@hussar.dco.dec.com (Marcus J. "Buddy can you spare a clue?" Ranum) writes:

can anyone post some adresses and emails of the various companies that
produce an RT-UNIX ? failing that send em to me and i'll summarize.

also for people that have used these could you extract salient features,
both pro and con, once again if you mail me i'll summarize


thanx

braham
-- 
j braham levy				| Control Systems Centre,
email: braham@csc.umist.ac.uk		| UMIST, PO Box 88,
Tel: +44-61-200-4672			| Manchester, M60 1QD, UK.
Fax: +44-61-200-4647			|
Newsgroups: comp.unix.bsd
From: scotty@gagetalker.com (Scott Turner)
Subject: Problems with beta patched wd.c
Organization: L5 Computing
Date: Tue, 13 Oct 1992 03:03:40 GMT

My kernel stopped working after applying the beta patch kit.
The system couldn't mount root.

The problem was that patch00021 changed the behaviour of
wd.c regarding controllers that didn't grok what
wdgetctlr() did. My Adaptec 2322B ESDI adaptor doesn't
seem to understand this command and patch00021 would
then decide there was no drive attached. This resulted in
my system having no hard disks, hence no ability to
mount root. :)

The following patch puts things back the way they
were:
*** wd.c.pl3    Mon Oct 12 19:53:40 1992
--- wd.c        Mon Oct 12 19:55:56 1992
***************
*** 236,244 ****
                        du->dk_unit = unit;
                }
                else {
!                       free(du, M_TEMP);
                        wddrives[unit] = 0;
!               }
        }
        return(1);
  }
--- 237,246 ----
                        du->dk_unit = unit;
                }
                else {
!                       du->dk_unit = unit;
! /*                    free(du, M_TEMP);
                        wddrives[unit] = 0;
! */            }
        }
        return(1);
  }

Scotty
Organization: Stanford Linear Accelerator Center
Date: Tuesday, 13 Oct 1992 23:54:50 PST
From: <CALT@SLACVM.SLAC.STANFORD.EDU>
Newsgroups: comp.unix.bsd
Subject: missing include files!?

Hello,
I have 386bsd (bin01 and src01) and XFree86 installed.
They are "running". I now try to use them. I wrote some
VERY simply C programs and tried to compile them.
I found I don't have all the include files of
/usr/include/sys/*.h, such as /usr/include/sys/cdefs.h
../sys/types.h, ../sys/unistd.h, ../sys/time.h, and more...
I looked at /usr/include/sys. It's a link to /sys/sys,
and /sys is a link to /usr/src/i386, and under /usr/src/i386
there is no the sys directory. Thus /usr/include/sys does not
exist, and therefore all the /usr/include/sys include files
do not exist. I am really confused! How does it happen?
Did I miss anything? Thanks in advance for any information!
Ching Shih
shih@cithex.caltech.edu
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: [XFree86] crypt how to, new session manager
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Wed, 14 Oct 1992 05:27:47 GMT

In article <1992Oct13.115238.1@max.u.washington.edu> anything@max.u.washington.edu writes:
    1.) I made the necessary changes to run crypt on my machine.
   what changes do I need to  make to XFree86 so that it works with
   crypted passwords?

I put the XFree86 1.1 sources for mit/clients/xdm on
nova.cc.purdue.edu in pub/386bsd/submissions/XFree86/xdm-src-1.1.tar.Z.

tar xzf xdm-src-1.1.tar.Z.
xmkmf -a
make

should create xdm.  Rich
Newsgroups: comp.unix.bsd
From: adrian@ibmpcug.co.uk (Superuser)
Subject: Re: Could the passwd/crypt changes be included in the patch kit?
Organization: The IBM PC User Group, UK.
Distribution: usa
Date: Thu, 8 Oct 1992 10:08:42 GMT

In article <veit.718535584@du9ds3> veit@du9ds3.uni-duisburg.de writes:
>
>Just curious, there was once a pointer by cgd to extract this crypt from some
>package publicly available from uunet. Has it been removed? If so,
>there is a copy of this file available at ftp.uni-duisburg.de in
>/pub/unix/386bsd-0.1/unofficial, if anyone is in need for encryption.
>The algorithm is basically PD, since the scheme and the sboxes have been
>published in Scientific American, so I don't understand this paranoic
>behavior of the US government (I believe nobody does). The above site is
>outside the US, and I won't accept any request of anybody to remove this
>file from there, since I have not stolen it anywhere but obtained from a
>legal and official site.
>

The instructions for installing crypt into the libraries and various
routines that need it are in /usr/386bsd.errata/crypt.instructions

As usual (for those that can get to it :), the patched sources
(including /usr/src/lib/libc/gen/crypt.*) are on rachel.ibmpcug.co.uk.
Would it help for me to put up my compiled libraries and binaries
as well?

The kernel file available for ftp is now to beta.patch.kit level.

Terry: Want to send me the patchkit maker and a number so I can
       produce a crypt patch?

Adrian


-- 
--------------------------------------------------------------------------
Adrian Hall					Connect Systems Manager
A.Hall@ibmpcug.co.uk				The IBM PC User Group
Tel: +44 81 863 1191				Harrow, London, UK
Newsgroups: comp.unix.bsd
From: st923150@pip.cc.brandeis.edu (Benjamin A. Tober)
Subject: Re: 386BSD gethostname() problems
Reply-To: st923150@pip.cc.brandeis.edu
Organization: Brandeis University
Date: Thu, 8 Oct 1992 23:54:47 GMT

Yes, agreed, the way DEC does service database resolution _is_ better than
the second best thing (probably the way Sun does it).  I might be interested
in coding up such an extension.  It's reasonably trivial.
-ben
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: Configuring X386 & etc
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Fri, 9 Oct 92 17:13:06 GMT

In article 16385@u.washington.edu, ganter@carson.u.washington.edu (Mark Ganter) writes:
>Hi gang,  I have X386 up and running! I don't have video problems THANKS
>to many posts, the FAQ for X, xclk, etc.  However, I'm having mouse problems.
>In the Xconfig file theres a line:
>(from my human memory)
>Logitech  /dev/tty00
>
>I have a couple of questions.  I didn't have a tty00.  So I generated one
>with mknod tty00 c 8 1 (just like com1 where my mouse was attached).  IS
>this correct?

Actually, you could just havbe replaced /dev/tty00 with /dev/com1 in the
Xconfig file.

>Also, what are other valid names to replace "Logitech"?
>And how would I know?  Am I missing docs somewhere?  I checked FAQ-X.  Did
>I miss something?

The options for Xconfig are documented in the X386 man page.

>I start X using xinit.  Lastly, I keep seeing Xfree86 with references to
>agate.berkeley.edu in pub/incoming/X386.  Is that the correct place?  I download
>last week and I got core.bin.1.02 files.  Yet, I see references to higher
>versions.  Has there been an update within the last week?

The most recent copy is in /pub/386BSD/ports-0.1/XFree86.  The version number
on the archive files is now 1.1.

	Chris Flatters
	cflatter@nrao.edu
Newsgroups: comp.unix.bsd
From: barnesdo@CS.ColoState.EDU (douglas barnes)
Subject: Some questions about 386BSD
Date: Fri, 16 Oct 1992 22:46:08 GMT
Organization: Colorado State University, Computer Science Department

I have been following the discussions on this newsgroup very closely
but I remain somewhat confused on a couple of topics because conflicting
posts were made and no clear victor emerged (or I missed the article
where one was declared).

Here goes:

1) Various posts have been made to the effect that using more than 
   16MB to run 386BSD is a *bad thing*. I also remember similar 
   problems with earlier versions of Interactive. In both cases the
   difficulty was attributed to the limited address space for devices
   (say SCSI controllers) to DMA into. Is this a real problem for 
   386BSD? Is anyone successfully running with >16MB of memory?

2) Several approaches have been outlined for causing DOS and 386BSD
   to coexist. Some apparently do not work for IDE drives. Could 
   someone mail me or repost the canonical method for installing
   multiple OSs on a *SCSI* drive? Also, I appreciate the ongoing
   efforts to discern exactly what the deal is with IDE, as the
   next available platform available to me has IDE drives.

3) That handy little program "os-bs" does not permit booting from 
   other hard drives. Is there a fundamental reason for this, or
   could such a utility theoretically boot from another drive? Is
   there a utility that does this?

Thank you for whatever help you can provide on the topic.

doug


-- 
-----------                                                   -----------
douglas barnes                               Calgon can't take me away...
barnesdo@CS.ColoState.EDU                 From the things I did today -L7
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: Could the passwd/crypt changes be included in the patch kit?
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Thu, 8 Oct 1992 13:43:41 GMT

In article <1992Oct8.014729.17211@fcom.cc.utah.edu>,
   terry@cs.weber.edu (A Wizard of Earth C) writes:
| In article <1992Oct7.161805.21244@rwwa.COM> witr@rwwa.com writes:
| >So then, if there were a patch that included a dummy module with comments
| >pointing to such a place, a patch could be distributed, right?
| >
| >So, Terry?  Want to include this in the next Patchkit Beta?
| 
| Can't.  Someone might ftp it from outside the US.

Uhh...???  What's wrong with them ftping it with a *DUMMY MODULE*?

| Tell you what, Robert:  You get a license and find the sources somewhere,
| and I'll email you the patch production software and get a number and an
| application ordering worked out with Nathan and send you a patch number
| to use.  8-).

I sent you mail offering to do just that... But I forgot to fix your
friggin address and it bounced... Can you post, for us, the address of
the administrator who has yet to fix the routing tables at weber.edu?  

GRR.....GRR....GRR...   OK, so I had too much coffee this morning!!!!   ;-)

| I don't think crypt is that big an issue; the way passwording is currently
| done, the machine is basically at the same security state for it's users
| as it would be in a vouchsafe environment:

It's not the security that I want, it's the standardization...  For example,
currently when I do:

	bash$ telnet meatball
	Trying 192.124.97.11 ...
	Connected to meatball.
	Escape character is '^]'.
	
	   386BSD (meatball.rwwa.com) (ttyp0)

	login: witr
	386BSD Release 0.1 by William and Lynne Jolitz. 
	[...]

But when I do:

	bash$ ftp meatball
	Connected to meatball.
	220 meatball.rwwa.com FTP server (Version 5.60) ready.
	Name (meatball:witr): witr
	331 Password required for witr.
	Password:
	530 Login incorrect.
	Login failed.

This probably *could* be fixed without the passwd/crypt system stuff, but
I don't see any good reason why it *should* be fixed without them.  

I'd be happy with a crypt that *didn't* crypt and kept the passwords in
plaintext, as long as the rest of 386BSD didn't know the difference.  And
if the dummy crypt has a comment directing you to a method to get the
*real* crypt, so much the better...

-- 
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA
Newsgroups: comp.unix.bsd
From: scs@iti.org (Steve Simmons)
Subject: BSDI, portables, and overhead projectors
Organization: Industrial Technology Institute
Date: Thu, 8 Oct 1992 21:03:21 GMT


Please forgive my depth of ignorance about PCs here . . .

I will shortly be recieving a portable for the purpose of giving
demos for a class.  My original plan was to put BSDI on it (go with
what you know, right?) but there is a potential fly in the ointment.

As part of the demo, they are currently connecting a device to the
VGA output port of the portable.  This device can be placed on an
overhead projector, and the entire class can see the result.  It
turns out that one toggles the screen display between the lcd and
the display unit by doing a magic key sequence on the keyboard.

If this key sequence won't work for BSDI, I'll have to drop back to
DOS instead.  Anybody got a portable that they're doing this sort
of thing with?  If so, let me know brand and sequence.

Will summarize.
-- 
scs:  Tied for last on the Zwicky list with `zwicky'.
From: goran@astro.uu.se (Goran Hammarback)
Newsgroups: comp.unix.bsd
Subject: Re: Memory problem
Date: 16 Oct 1992 12:36:03 GMT
Organization: Uppsala University
Distribution: world
NNTP-Posting-Host: solaris.astro.uu.se
Keywords: memory

In article <wmbfmk.719081295@rwb.urc.tue.nl>, wmbfmk@rwb.urc.tue.nl (Marc van Kempen) writes:
|> Hi, I seem to have a memory related problem with 386bsd.
|> 
|> Whenever I start xlyap a few times (consumes approx. 4 MB each time) and
|> then start a make on some big program, my system will eventually hang,
|> and even reboot. I have read the thread about make having a memory leak,
|> so I guess the system just runs out of memory, which should be correct
|> since I had started xlyap enough times to use up to 34 MB or so. What
|> bothers me is that the system does not complain about running out of
|> memory in a somewhat more communicative manner than it does right now.
|> Is there a bug somewhere or am I just stupid and misconfigured the
|> system?
|> 

It's a known problem that 386BSD just hangs if you fill the swap.
I call it a bug (I doubt you will find anyone saying it's feature 8-) ).

-- 

Goran

------------------------------+---------------------------------
Goran Hammarback              |     goran@astro.uu.se
Astronomiska Observatoriet    |
Uppsala Universitet           |
S-751 20 SWEDEN               |
------------------------------+---------------------------------
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD and manual pages
Date: 12 Oct 92 08:22:39 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Distribution: global
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de

In <1992Oct10.170713.12180@hippo.ru.ac.za> g89s9112@hippo.ru.ac.za (Dirk Sturzebecher) writes:

>Hi all,
>just a short question. how do manual pages work with 386bsd ?

>they are not in the normal format but rather as some form of text
>file (with special char's to do the high lighting of keywords).
>How do I get normat manual pages to 386bsd manual pages? I tried
>troff,.. , but the results where not more or less unsatisfactory !

>Cheers, Dirk

>-- 
>-----------------------------------------------------------------------
>Dirk Sturzebecher				g89s9112@alpha.ru.ac.za
>Rhodes University Grahamstown			South Africa

Something like

nroff -mandoc manpage.1 >manpage.0

Holger

-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|  | /   Dept. of Electr. Eng.   |   Sorry, the above really good fortune has
|  |/    Inst. f. Dataprocessing |      been CENSORED because of obscenity"
Newsgroups: comp.unix.bsd