HDTenEightyP/NetNews huggingface dataset:
From: rahardj@ccu.umanitoba.ca (Budi Rahardjo)
Subject: Help, the boot disk won't boot on my machine
Followup-To: comp.unix.bsd
Originator: rahardj@antares.cc.umanitoba.ca
Keywords: install
Organization: University of Manitoba, Winnipeg, Manitoba, Canada
Date: Tue, 29 Sep 1992 01:30:22 GMT

I decided to give 386BSD a try.[Currently I am using Linux]
Donwloaded the dist.fs and rawrite it to a disk. 
Boot the machine, the drive keeps on spinning ...
nothing on the screen.
I downloaded the file again 3 times, to make sure I didn't forgot
to use the binary (etc.). It still won't boot...
Help.

Machine: Gateway 2000 386SX/16 Meg.

PS: A friend of mine told me he had similar problem. 
    He 'solved' this by going to the CMOS  setup, do nothing,
    and boot the machine. It works on his machine but not mine.

-- budi
-- 
Budi Rahardjo <rahardj@ccu.umanitoba.ca>
Unix Support - Computer Services - University of Manitoba
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: Where can I find xterm for 386BSD for PC.
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Tue, 6 Oct 1992 02:18:03 GMT

In article 1aqhtdINNb4r@gossip.pyramid.com, dinesh@pyramid.COM (Dinesh Jalisatgi) writes:
> I just downloaded the X386 oftware from agate and I find that there is no xterm included in it.
>
> Where can I find one for the 386BSD based PC.

Huh? I downloaded X386 from agate this afternoon and there is
definitely an xterm in there.  Try downloading core-bin-1.1.tar.Z
again.

	Chris Flatters
	cflatter@nrao.edu
Organization: Penn State University
Date: Sat, 26 Sep 1992 15:18:04 EDT
From: <JDA108@psuvm.psu.edu>
Newsgroups: comp.unix.bsd
Subject: Beginning questions:

Well, I got the bin stuff installed, and I haven't crashed it yet, but there
are some questions/broken things I can't quite figure out on my own.
Some of the stuff might be covered in the /etc distribution, but space is a
little limited, and I don't wanna dump it all to floppies needlessly.  So,
here goes:

1)  When attempting to do a 'w', I get an error about not being able to find
    a certain file.  (I'm not at home, wish I'd have written this stuff down).
    Any idea what might need to be fixed from the default setup in the bin
    distribution?

2)  While attempting to find some help on different things, I did a man -k
    and got a 'apropos: cannot find whatis.db'.  Ok, I have the whatis command
    but not much of a clue how to build the database for this.  (BTW it also
    dumps core.  Happy happy.)

3)  For a lack of being able to fix the above problems, I went and fetched the
    source to tcsh.  I got version 6.00.02.  Anyone know exactly what changes
    need to be made before compiling before I go mucking around myself?

Thanks in advance. :)

-Jeff
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: XFree86 problems on 386BSD
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Tue, 6 Oct 1992 17:49:29 GMT

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.

Does anyone have any ideas about what might be going on?

System configuration:
	CompuAdd 325s with built-in VGA interface
	386BSD 0.1 with kernel patches from XFree86 distribution
	6 Mbytes memory
	12 Mbytes swap

	Chris Flatters
	cflatter@nrao.edu
From: briggs@csugrad.cs.vt.edu (Occasionally Allen)
Newsgroups: comp.unix.bsd
Subject: Re: Question about the OS running progs???
Date: 4 Oct 92 19:55:09 GMT
Organization: Virginia Tech Computer Science Dept, Blacksburg, VA

In article <1992Oct4.174420.7664@news.ysu.edu> ae007@yfn.ysu.edu (Daniel Newcombe) writes:
>If gcc compiles to straight 80x86 code, then how does the OS
>handle running multiple programs?  I guess what I really want
>to know is how the OS knows that after X amount of instructions
>have been run, it is time to give control to another process for
>X amount of instructions?

Since you mention that you are taking OS, I will point you to your
book for a more thorough coverage of "multitasking."  In a nutshell,
basic case, the compiler/assembler/linker creates an executable
program that consists of 80x86 (or whatever processor) non-privileged
instructions.  When the user is running any process, they have full
control of the processor.  In most cases, the processor is in a "user"
state so that privileged instructions will cause some sort of hardware
trap that the kernel can handle.  While the processor is running, a
clock is generating interrupts at specified intervals.  When such an
interrupt occurs, the processor is switched into a supervisory state
and a piece of the kernel takes over to save the current state of the
running process and restore the state of the next process on the queue.
When this is done, the interrupt handler exits and the new process
starts execution again.

If the time slices are short enough, it looks like the processes are
running "at the same time."  This is, of course, a very simple case and
I've left out (or glossed over) a lot of details like "what constitutes
the current state of a process?" and "what if I'm waiting for an I/O
operation and don't need my clock cycles?  Can I give up control of the
CPU?"

Do look it up in your book, or if your book doesn't cover it well, check
out books by Tannenbaum or Deitel.

-allen
-- 
Allen Briggs          \ People hurry by so quickly
briggs@csugrad.cs.vt.edu | Don't they hear the melodies
Computer Science      / In the chiming and the clicking
Virginia Tech      / And the laughing harmonies.       (Joni Mitchell)
Newsgroups: comp.unix.bsd
From: nils@merlin.ims.uni-stuttgart.de (Cornelis van der Laan)
Subject: Re: [386BSD] can FIFO support be made to work?
Reply-To: nils@ims.uni-stuttgart.de
Organization: IMS, University of Stuttgart, Germany
Distribution:  world
Date: Mon, 5 Oct 1992 11:49:55 GMT

>>>>> On Tue, 29 Sep 1992 01:55:43 EDT, scott@lopez.marquette.MI.US (Scott Reynolds,Insanity) said:

Scott> I've added the necessary "options FIFO" to my configuration and done the
Scott> config, and I had to modify the .depend file manually to make sure that
Scott> the proper fifo.h file was picked up.  This was no real problem, and I

Be sure to not include an 'pseudo-device fifo' line in the config file
and remove any left over fifo.h in /sys/compile/You-Kernel. It is not
needed and is included before the correct /sys/sys/fifo.h. Then remove
all your kernel .o files and - after a make depend which should rebuild
the dependancy file correctly now - rebuild your kernel.

Scott> rebooted and made a fifo only to discover that opening the fifo for writing
Scott> caused the tty to hang.

Doesn't happen to me on 386BSD; but if someone writes some characters to a
fifo that no one has open for reading, all characters are lost. 
On a sun instead the writing process hangs until a reader opens the fifo;
no input gets lost.
I don't know the semantics of fifos. Which one is correct ? 

-- Nils.
Newsgroups: comp.unix.bsd
From: ujlh@pool.info.sunyit.edu (James Henrickson)
Subject: Re: 386bsd networking -- help needed
Organization: State University of New York -- Institute of Technology
Date: Sat, 26 Sep 1992 22:01:59 GMT


I said:
>
>OK, I have narrowed things down somewhat.
>
>I set up an entry in /etc/hosts for localhost and can now connect with
>rlogin, telnet, and ftp.  What do I do now?  I would like to use a regular
>address (such as 0.0.0.1) for my first system, but can't manage to get
>it to work. 
>

I guess it doesn't take much to figure out I'm new to networking.  :-)

Playing with ifconfig took care of that problem, but I have one more left.
I have my NE2000 clone set for the 386BSD defaults, and my screen gets
bombarded with "startartstartartstartartstart..."  How do I get rid of 
this annoying message?  If I'm not mistaken, it also gets written to
/var/log/messages.  :-(

Thanks in advance,

-- 
Jim H.
*
* James L. Henrickson
* ujlh@sunyit.edu        "Some day I might have a real .signature!"
Newsgroups: comp.unix.bsd
From: wutcd@chemnitz.guug.de (Joerg Wunsch)
Subject: Re: 386BSD's non-standard C library
Organization: tu-chemnitz
Date: Sun, 27 Sep 1992 20:30:52 GMT

...please be patient, the patches necessary to have a more comfortable
ctype(3) are under development. Give me some additional days, and at
least the funtionality of SVR3 is achieved.

	J"org

--
J"org Wunsch, TCD GmbH Dresden, R"ahnitzgasse 18, D-O-8060 Dresden
                                                              \     ~.~. 
	joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de         \   ~  | ~ 
	voice: +49-351-5965 137                                 \    ===
From: ghelmer@dsuvax.dsu.edu (Guy Helmer)
Newsgroups: comp.unix.bsd
Subject: [386bsd] Properly patched init.c wanted
Date: 27 Sep 92 22:03:37 GMT
Organization: Dakota State University

I have tried to run 386bsd 0.1 with /sbin/init compiled from the
sbin/init/init.c at patchlevel 4 from Terry's patch kit, but it fails
strangely -- a little while (10 to 20 seconds) after 386bsd begins
running /etc/rc, the machine reboots (usually while running fsck).  If
someone has an operating, patched init, could you please send it to
me?  Thanks in advance.


-- 
Guy Helmer, Dakota State University Computing Services - ghelmer@dsuvax.dsu.edu
White congressmen can't jump, but they sure can bounce.
Newsgroups: comp.unix.bsd
From: bjork@telebit.com (Steven Bjork)
Subject: Sorry, not "type tenex" was Re: Corruption in BIN01.56?
Organization: Telebit Corporation; Sunnyvale, CA, USA
Date: Mon, 5 Oct 1992 15:52:04 GMT

In article <1992Oct4.082800.7011@pimacc.pima.edu>
jlackey@pimacc.pima.edu writes:

>I even attempted the same solutions, ie I got the files again, I made sure
>I typed 'tenex' (the vax version of binary I guess, can't stand this beast), 

The ftp transfer type of "tenex" should only be
used if you are getting binary files to/from an
old DECsystem10 or DECsystem 20. (such as simtel20).

That is, unless someone wrote some horribly confused software :(.

--Steven
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.rt,comp.unix.large
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: strdup
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Thu, 1 Oct 1992 13:14:33 GMT

In article <lckirmINNosg@spim.mti.sgi.com>, koblas@mips.com (David Koblas) writes:

| Here's a copy (typed in off the cuff, so I won't say it
| is guaranteed to work):

And---It won't.  The malloc size if off by one.  Add one.

-- 
 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: ganter@milton.u.washington.edu (M. Ganter)
Subject: Cross booting DOS <-> BSD
Summary: Summary of info. about cross booting DOS <-> BSD
Keywords: Booting,Disks,Partitions
Organization: University of Washington
Date: Wed, 30 Sep 1992 21:13:07 GMT

First, I'd like to thank everyone who responded to my post on cross booting
from BSD <-> DOS.  I have both DOS and BSD on my 486 (80MB DOS and 120MB BSD).
Several of the suggested programs/solutions require starting from a CLEAN disk
(not fun).  However, pboot (from pboot.zip) works VERY well.  It does NOT
require reinstalling any of your software.  The pboot doc is terse.
Basically for DOS try the following:

install pboot.bin boot.saf 

The install program (with pboot) copies in a new boot record and copies out
you're old (into file boot.saf).  Pboot knows about many OS's (including BSD).
When you reboot, a brief menu 1.,2.,3.,4.  comes up.  Your choose which
partition (ie.e OS) and off you go.  

Again, Thanks to all who helped...Mark

Mark Ganter/Univ of Washington/Dept of Mech Engr/FU-10/Seattle, WA 98195 USA
ganter@u.washington.edu

Newsgroups: comp.unix.bsd
From: ccml@hippo.ru.ac.za (Mike Lawrie)
Subject: Re: [X386] xdm won't start display :0
Organization: Rhodes University, Grahamstown, South Africa
Date: Sat, 3 Oct 1992 16:48:44 GMT

In <1992Oct2.084609.1@max.u.washington.edu> anything@max.u.washington.edu writes:

>when I start xdm from root I get a lot of disk activity and nothing else.
>upon reading my /usr/X386/lib/X11/xdm/xdm-errors I find:

>X386 Version 1.2E 1.0.2a / X Window System
>(protocol Version 11, revision 0, vendor release 5000)

>Fatal server error:
>no screens found
>error (pid 1064): IO Error in XOpenDisplay
>error (pid 1062): Display :0 cannot be opened

I had a problem like this - then x386install appeared on agate. This
traced my problem by doing a grep -s 'pc-xmode' /386bsd and reported
that my kernel did not have X386 support. My slipup was to modify the
Makefile in the .../compile/MY.SYSTEM directory, and not in the
.../conf/MY.SYSTEM file.

There are still many other pitfalls awaiting you, but persist, it is
well worth it.

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: julian@tfs.com (Julian Elischer)
Subject: eisa_configure.c (New file) Ideas?
Organization: TRW Financial Systems
Date: Tue, 29 Sep 1992 03:03:48 GMT

I am today, abiut half way through writing my second EISA
scsi controller driver for 386bsd and MACH.
What is becoming apparent is that there needs to be an EISA
version of the routine isa_configure().

Background:
Each slot in an EISA machine decodes out to different addresses for EISA
Extended Registers,
e.g. 
the EER ID registers will appear at location 0x1C80 for the first slot,
					     0x2C80 for the second
					     0x3C80 for the third
					     0x4C80 for the forth
					     etc.

================The ideal way of configuring the system==========
If I know there are drivers for 3 cards A,B and C in the kernel,
I can step through the slots, reading the ID ports for each slot
and doing an 'attach' on the correct driver. If a slot
has no EISA card, or one I don't recognise, I just move on to the next.
The eisa_config table would appear as:

struct eisa_config{
	(*int)() fn;
	char	manufacturer[4];
	int	productnum;
}eisa_config[] = {	 {ahbattach,"ADP",0} /*adaptec 174[02]*/
			,{ahbattach,"ADP",1} /*adaptec 1744*/
			,{btattach,"BTK",0} /*bustek 742*/ (just a guess)
			,{lneattch,"MLX",0} /*mylex lne enet*/
};

This does not fit in well with the present ISA configuration
methods.

===============What I am implimenting for now=================
What I am going to do for the first version of these cards, is
to allow the isa_configure() to call my probe routines as normal,
and the probe routine will move up through the slots looking
for an instance of the board it knows, and then write the 
port number (0x1000 or 0x2000 etc) to the isa_device
structure along with the interrupt vector and dma info.
This info will then be present when isa_configure() validates it
as not clashing with another device.
If The device has been configured a second time, slot scanning will
resume at the next slot after the last board found.

note that in this method the config file need not specify a dma,vector or port
because the probe routine will find this information and write it into the
isa_device structure at boot time.

The values will be as selected by the user in the EISA CONFIGURE (DOS) program.

While the second method will work, I would prefer the first.
=================The third alternative===================
pretend they are ISA devices and specify the port address fully
in the config, i.e. they will only be found if they are
in the right slot. This sounds like trouble to me.




I would like feedback on this issue, particularly from the likes of
bill and lynne, the crowd at CSRG, or the lynux crowd. But don't feel
shy if you're just joe random-hacker. I'd like to know where we're going
on EISA support.

julian

+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\            
          v


Newsgroups: comp.unix.bsd
From: hitchens@untadh.enet.dec.com (Francis J. Hitchens)
Subject: Help logitech bus mouse, Xconfig
Reply-To: hitchens@untadh.enet.dec.com (Francis J. Hitchens)
Organization: Digital Equipment Corporation
Date: Tue, 6 Oct 1992 14:03:31 GMT


Help, what device should a logitech bus mouse use, and how does one
create it  ?

Xconfig ...

busmouse	"/dev/????"

 regards Francis J. Hitchens
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.unix.bsd
Subject: Lance query 
Distribution: world
Date: Sat, 03 Oct 92 01:17:28 GMT
Organization: Crynwr Software

In article <12764.9210021637@thor.cf.ac.uk> spedpr@thor.cf.ac.uk writes:

   I've been getting a number of is1:reset errors from the isolink driver
   and the cause is due to the lance stopping its transmitter.
   Specifically, in the interrupt routine the transmitter-on (TXON) bit of
   the lance is checked and if it isn't set then a reset occurs.

   What I want to know is: under what circumstances does the lance clear
   this bit, supposedly indicating that the transmitter has been switched
   off?

I don't know, particularly.  However, AMD insists that there are no
bugs in the LANCE, so the answer to your question lies in their
published documentation.  No hidden bug sheet/shit.

-russ <nelson@crynwr.com>  I'm proud to be a humble Quaker!
Crynwr Software            Crynwr Software sells packet driver support.
11 Grant St.               315-268-1925 Voice
Potsdam, NY 13676          315-268-9201 FAX
Newsgroups: comp.unix.bsd
From: alan@ulka.zso.dec.com (F. Alan Jones)
Subject: Re: checksum bad on bin01.56 why?
Reply-To: alan@ulka.zso.dec.com (F. Alan Jones)
Organization: Digital Equipment Corporation
Date: Thu, 1 Oct 1992 20:54:15 GMT


I had a similar problem which turned out to be an extra character at
the end of the file added by ftp.  It might be because of not setting
"image" mode.  Anyway, see if the size on the ftp server matches the
size of the file you have downloaded, and if your downloaded file is
one greater, remove the last byte.  I used emacs for this (ESC > BS).

Alan Jones
BTW: We should start a Seattle users group!
Newsgroups: comp.unix.bsd
From: volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt )
Subject: Re: emacs for bsd386??
Organization: Applied Math, University of Bonn, Germany
Date: Mon, 28 Sep 1992 01:50:43 GMT

In article <veit.716830243@du9ds3> veit@du9ds3.uni-duisburg.de writes:
>In <1992Sep17.233311.26321@olymp.informatik.uni-bonn.de> volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt ) writes:
>>In article <bcrawfor.716490140@sol.UVic.CA>, bcrawfor@sol.UVic.CA (Bryan Crawford) writes:
>>> an anuyone point me in the right direction for acquiring
>>> emacs (preferably GNU) which has been ported to BSD386.
>
>>I'm surprised that nobody mentions the fact that a ready-to-run emacs binary
>>came with the etc.01 distribution.  That saved me since I never got around
>>to learning the key sequences of That Other editor.

>You seem to have a different "etc01" than the rest of the world. From the
>cpio directory listing the only thing that has "emacs" in its path is
>the emacs.el mode for perl-4.019. Another check for finding the numerous
>".el" and ".elc" files only find few additional ones in perl and cvs 
>directories. Where did you get your "etc.01"? Seems that someone has 
>mixed together "official" and "unofficial" stuff. No such addition has
>been posted to c.u.b yet.

Sorry. You're right.  I got the emacs binary off some ftp server (forget
which one) but it didn't come from the etc distribution.  The port was done by
Shannon Appel (appel@erzo.Berkeley.EDU) and works just fine.  I'm very glad to
have it.

-- Volker

-- 
----------------------------------------------------------------------------
Bitnet:   UNM409@DBNRHRZ1                              Volker A. Brandt
UUCP:     ...!unido!DBNRHRZ1.bitnet!unm409             Angewandte Mathematik
Internet: volker@sfb256.iam.uni-bonn.de                (Bonn, Germany)
From: dean@ksr.com (Dean Anderson)
Newsgroups: comp.unix.bsd
Subject: Re: Catch What They're Saying About Us...
Date: 28 Sep 92 18:53:31 EDT
Organization: Kendall Square Research

I'm sorry.  I have been listening to this for *too* long.  Personal
Diatribes can be taken to alt.flame.whatever.   

I don't know anybody (major players) in this forum.  So I think I am
an objective observer.

That being said, it would appear to me that there are a lot of 
egotistical, perhaps megalomanical people who cannot take criticism 
or any sort.  Not that that really bothers me, but 100k byte messages
cost me (and a lot of other people) money.  Ok, its not my money, but
it costs just the same.

Please do not make this my problem. I just want to read about BSD systems
and unix systems in general.  If we cannot behave with a little aplomb, 
perhaps this news group should be moderated.  Then the moderator can filter 
out the undignified and inappropriate messages.  

I hate adding administrativia, but if people continue to have like two year
olds, I don't see what else can be done.


--
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
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.rt,comp.unix.large
From: wheeler@heckle.mitre.org (Brien L. Wheeler)
Subject: Re: strdup
Organization: The MITRE Corporation, Bedford, MA
Date: Thu, 1 Oct 1992 12:27:48 GMT

In article <lckirmINNosg@spim.mti.sgi.com>, koblas@mips.com (David Koblas) writes:
> Here's a copy (typed in off the cuff, so I won't say it is guaranteed to work):
> 
> 	char *strdup(char *str)
> 	{
> 		char	*cp = (char *)malloc(strlen(str));
> 		return cp ? strcpy(cp, str), cp : NULL;
> 	}

Try this instead -- it mallocs a byte for the NULL terminating character.
(There is no need for "strcpy(cp,str),cp" as strcpy always returns its
first argument.)

char *strdup(char *str)
{
        char *cp = (char *)malloc(strlen(str)+1);
        return cp ? strcpy(cp,str) : NULL;
}
 
-----
     Brien L. Wheeler  |  I don't speak for MITRE, and they
     blw@mitre.org     |  don't speak for me.

"When I think back on all the crap I learned in high school..."
Newsgroups: comp.unix.bsd
From: cs120323@rucs2.sunlab.cs.runet.edu (David A. Scardina)
Subject: pascal compiler wanted
Organization: Radford University
Date: Thu, 1 Oct 92 22:01:57 GMT

Iam looking for a pascal compiler for 386bsd that is written in C because I 
need to compile it and the only compiler I currently have is C. 

If anyone has one or knows where to find one, PLEASE send me mail rather than
post to this news group.

thanks in advance.
dave scardina
E-mail cs120323@rucs2.sunlab.cs.runet.edu 
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=|
|\/\/\/|                                __&__   * ######Dave Scardina###### |
|      |        __________________     /     \  * Computer Science Dept.    |
|      |       / Why you little!! \   |       | * Radford University        |