HDTenEightyP/NetNews huggingface dataset:
From: solsman@ra.nrl.navy.mil (Mark Solsman)
Newsgroups: comp.unix.bsd
Subject: extract says its corrupt, damit!
Date: 9 Sep 92 05:51:02 GMT
Distribution: world
Organization: Naval Research Lab, Washington, DC


Hello,

I am having trouble installing 306bsd.  This morning, I mread the bin dist
into /tmp and then extracted them fine.  However, when the system accidently
rebooted, I decided that I should start over from scratch rather than invest
more time and kill myself later.

So I did just that, and now no matter what the hell I do, extract tells me
that etc01.71 and bin01.46 are corrupt.  Now, I am using the same disks
are I did before, and I even re-ftp-ed them from my workstation to my PC,
when that didn't work, I even re-ftp-ed them from agate.berkeley to my PC,
When that didn't work, I even ftp-ed them from agate.berkeley to my 386bsd
setup using slip.  No matter what I do, these two files etc01.71 & bin01.46
are corrupt.

Does anyone have any ideas of what I am doing wrong?  I have re-installed
tiny-bsd many times and started over and over from scratch.  Does anyone
have an idea of how to fix my situation.

thanks in advance

-Mark

Gateway 386/25 w/ 8megs, 105meg bsd partition active on drive 0, ati vga,
esdi, mread b:*.* /tmp - from 3.5"                    


-- 
Mark Solsman                                 Building 1, Code 5160
United States Naval Research Laboratory      solsman@ra.nrl.navy.mil
Washington, DC                               (202) 767-5769
From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
Newsgroups: comp.unix.bsd
Subject: Less than 8 planes in X?
Date: 6 Sep 92 15:00:49
Organization: Kansas State University
NNTP-Posting-Host: maverick.ksu.ksu.edu

Due to limitatinos in processor speed I'm wondering if there is any
way to make X386 to use less than 8 planes.  Something like 2 or 4
planes would be great.  Even 1 plane would be preferable at times.
Is there a way to specify the number of planes to use in Xconfig?

++Brett;
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: Argh! 386BSD dies after a dozen or so commands!
Date: 9 Sep 92 14:06:28 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de
Keywords: 386bsd Memory Fault

In <1992Sep09.023506.16724@ecst.csuchico.edu> cyber@ecst.csuchico.edu (Erik Berls) writes:

>Im having a little problem with 386BSD,
>after booting off of either the dist.fs or the fixit.fs it only allows
>me so many commands before it starts spitting back in my face.
>The easiest way to replicate the situation is to do a ls -al.
>That works for about 13 times, after that it Memory Faults.
>The computer science part of me says that something is not getting cleaned up.
>But it works fine on my roomates system (booting up, can do the ls -al 15-20
>times without a problem, didnt try anymore after that.)

>My system:
>Adaptec 1542B SCSI Controller.
>Orchid Prodesigner II
>Sound Blaster Pro
>Compudyne Internal 2400 baud modem
>a no-name multi-io card (2s1p1g)
>a no-name monocrome card
>and the motherboard is a 386DX-33 (Intel) 8 megs of RAM
>as for brand name, it has a chip on the motherboard that says "CHIPS"
>but i seem to remember a manual that had the correct jumper configs that said
>"Star" on it,
>The motherboard can hold 16Megs, 8 on board, another 8 on an memory expansion
>board.
>(The abundance of motherboard info is to aid anyone in identifieing it.)
>AMI Bios.

>thanks,
>-=erik.

General hint: remove all the unnecessary or unsupported cards, i.e.
sound blaster (might conflict with multi-I/O, although mine does not afflict
operation, might also conflict with Adaptec DMA)
internal modem card (might conflict with IRQ's from serial I/O)
monochrome card (might conflict with orchid)
and try again.

Since DOS handles the hardware in a different way (does not rely on IRQ and
DMA for many of the cards), the present configuration might work well here,
but fails with 386bsd).

Holger

-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
From: smg@oxphys.physiol (Steve Gough)
Newsgroups: comp.unix.bsd
Subject: Re: getting mtools working (again) ?
Date: 15 Sep 92 15:38:30 GMT
Organization: Physiology Department, Oxford University, Oxford, UK.
Originator: smg@oxphys.physiol

In article <veit.716109291@du9ds3> veit@du9ds3.uni-duisburg.de writes:
> In <1992Sep9.071926.6592@msuinfo.cl.msu.edu> paoletti@cps.msu.edu (David R. Paoletti) writes:
>
> >I've got 386BSD up and running, and installed the binaries
> >using the loadfd command when I started.  My problem is that
> >now none of the mtools (mdir, mread, etc) will work.  If I do
> >something like mdir a: or mdir "a:" or mdir "a:*.*", it just
> >aborts with the error:
>
> >  init: open: No such file or directory
>
>This should get into the FAQ:
>
>A non-root user has no R/W access to the floppies. Set the 
>permissions to 666 for /dev/fd?[a-h]. This, however, introduces 
>all dirty tricks that undermine security, so a probably better
>idea could be 644.

I had the same problem after I installed 386bsd.  It's not the permissions.
The mtools in the binary distribution appear to be broken.  mread works
fine, but mdir/mwrite/mattrib etc. abort with the above error message.

I grabbed the binaries for mtools from the file
/386BSD/nova.cc.purdue.edu/mtools-2.0.5.tar.Z on src.doc.ic.ac.uk ftp
server and these work fine.

As mread works, you should be able get the new mtools loaded if you don't
have internet access from the 386BSD computer.

The nova.cc.purdue.edu directory is not in the ROADMAP, so this 
directory might not exist at all the 386BSD ftp sites, but presumably
it *IS* available at nova.cc.purdue.edu!

Of course, I might be wrong about the mtools in the binary distribution.

Steve.
-- 
 Stephen Gough               McDonnell-Pew Centre For Cognitive Neuroscience
 smg@physiol.ox.ac.uk        University Laboratory Of Physiology
 tel: +44 865 272514         Parks Road
 fax: +44 865 272469         Oxford OX1 3PT
Newsgroups: comp.unix.bsd
From: stritzi@Physik.TU-Muenchen.DE (Peer Stritzinger)
Subject: Ethernet cards and BSD/386
Keywords: ehternet card
Organization: Leibniz-Rechenzentrum, Muenchen (Germany)
Date: Fri, 11 Sep 1992 17:22:32 GMT

I asked this before but got no answer:

Which ethernet cards are supported in BSD/386?

Is the INTEL Etherexpress supported?

Where can I get additional drivers?

--
Peer Stritzinger
Phone: +(49)8141-90613
Fax: +(49)8141-95235
Internet: stritzi@physik.tu-muenchen.de
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: LPT problems in 386BSD - HELP!
Date: 12 Sep 92 10:20:59 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de

In <abeech.716211632@kraken> abeech@kraken.itc.gu.edu.au (Adrian Beech) writes:

>Greetings!

>I've installed the lpt patch as suggested by many readers of this group.  I
>now cat print using the `cat <file> >/dev/lpt' command with no problems.
>However when I use the lpr command all I get is the banner page and then the
>system falls over.  Has anyone else had the same trouble?


>-- 
>Adrian V. Beech                              E-MAIL: A.Beech@ext.gu.edu.au

Recompile lpd/lpr. In particular, if you also have done the kvm.c patches
to make ps running, it is recommended to rebuild all applications that use
libutil.a (A dozen or so, lpd is one of them).

Holger
-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
Newsgroups: comp.unix.bsd
From: pham@ucselx.sdsu.edu (Peter Pham)
Subject: How md_space in struct mb_device defined?
Keywords: [SunOS4.1.1]
Organization: San Diego State University Computing Services
Date: Wed, 9 Sep 1992 23:14:38 GMT


I am trying to make a device driver loadable on SunOS 4.1.1
(on a Sun4/330).  There is a structure 'mb_device' that I need
to initialize.  Under this structure, there is a field called
'u_int  md_space'.  The comment for this field (structure 
defined in <sundev/mbvar.h>) says this is a field for "encoded
address space".  Suppose I want the VME address space of 32D32,
what should I put in this field?  Does anyone know the "encoded
address space" is pre-defined some where?

Thanks in advance.

Peter Pham
Newsgroups: comp.unix.bsd
From: goran@astro.uu.se (Goran Hammarback)
Subject: Re: how do I put 386bsd on drive 2
Organization: UDAC, Uppsala, Sweden
Date: Tue, 8 Sep 1992 13:51:24 GMT

In article <92252.033510MHS108@psuvm.psu.edu>, Mark Solsman <MHS108@psuvm.psu.edu> writes:

|> I have two esdi drives, I would like to make the first drive msdos, and
|> the second drive 386bsd.  Can I do this, and how?  I am not sure, because
|> 386bsd install only seems to look at drive one, and doesn't notice the big
|> vacient sign on the partition table for drive two...

There are two possibilites:

* Open your PC and change cables and settings so the second disk
  is the first disk, boot from the tinyBSD disk and let install do
  it's stuff (or use the fixit disk and makeo a custom disklabel and
  install so you get a decently sized swap partition).

* Get a kernel that supports two disks, strip it and replace the kernel
  on the fixit disk, boot from fixit, disklabel the second disk, mount
  it and custom install.

Either way, you now have a DOS disk, and a 386BSD disk.  The problem is
that the PC ROM only allows you to boot from the first (DOS) disk, so to
boot from the other disk you have to physically make it that disk the first
one.
This is not very practical (although I use that myself now, but that's
because my stupid diskcontroller won't realize I have two disks on it 8-(.
I bought a new one today, I hope that one works 8-) ).

To have a workable system you have to have both systems on the first
disk.  Either have a small DOS partition + all BSD on the first, with
the rest of your DOS stuff on the second disk, or all of DOS + a small
(5-10MB depending on how you treat /tmp) BSD root partition + some swap
for BSD on the first, with /usr and more swap for BSD on the second.

In either case you need to handle the BSD installation yourself,
in the first case to get a decent swap area, and in the second case
to install /usr (and swap) on the second disk.

Which to choose depends on the size of your disks, and how much space
you need for the two systems.  The main factor is how much DOS space
you need, BSD (and you) will be happier the more diskspace it gets.

-- 

Goran

------------------------------+---------------------------------
Goran Hammarback              |     goran@astro.uu.se
Astronomiska Observatoriet    |
Uppsala Universitet           |
S-751 20 SWEDEN               |
------------------------------+---------------------------------
Newsgroups: comp.unix.bsd
From: john@socrates.umd.edu (John VanAntwerp)
Subject: Re: 386bsd -- The New Newsgroup
Keywords: newsgroup 386bsd news group
Organization: University of Maryland University College
Date: Tue, 8 Sep 1992 20:06:25 GMT

In article <18iprpINNg6e@agate.berkeley.edu> wjolitz@soda.berkeley.edu (William F. Jolitz) writes:
>
>As per Bill's suggestion, here's a breakdown of some of the suggested 
>topics and groups:
>
>	comp.os.386bsd		(general questions and trivia)
>	comp.os.386bsd.kernel	(discussion on kernel content/structure)
>	comp.os.386bsd.windows	(ditto, on windowing systems like X)
>	comp.os.386bsd.sharedlib (shared library and programming environment)
>	comp.os.386bsd.net	(networking topics)
>	comp.os.386bsd.bugs	(new bugs)
>	comp.os.386bsd.ann	(announcements, fixes, additions)

I think that this is a fine set of newsgroups...

						John
From: ws@tools.de (Wolfgang Solfrank)
Newsgroups: comp.unix.bsd
Subject: Re: GDB under 386bsd 0.1
Date: 5 Sep 92 19:28:07
Organization: TooLs GmbH, Bonn, Germany
	<1992Sep4.153554.4387@cs.few.eur.nl>
NNTP-Posting-Host: kurt.tools.de
In-reply-to: pk@cs.few.eur.nl's message of Fri, 4 Sep 1992 15:35:54 GMT

While your fix probably solves this particular problem, the real
fix is to modify the copyout routine to explicitly check for a
write to a write-protected page. Without this the copy-on-write
handling never takes place when the kernel writes data to the user.
E.g. in the following program the data read by the child can be seen
in the parent's data space:

char buf[512];

main()
{
	switch (fork()) {
	case -1:
		perror("fork");
		exit(1);
	case 0:
		buf[0] = 0;
		if (read(0,buf,sizeof(buf)) < 0) {
			perror("read");
			exit(1);
		}
		return 0;
	default:
		if (wait(0) < 0) {
			perror("wait");
			exit(1);
		}
		write(1,buf,strlen(buf));
		return 0;
	}
}

Bill Jolitz included an obviously first try in locore.s, but this
is disabled by a #ifdef notdef (don't know the reasons for this).

While I read this code another bug came to my mind. In the
copy{in,out} routines the kernel uses the kernel data segment to
access the user data. This means the user program can e.g. give
the address of some kernel data structure to the read system call
and thus destroy (or otherwise modify :-() its contents.

When I'm done testing this I will post a fix. But don't hold
your breath as I'm a little short on time currently.
--
ws@tools.de     (Wolfgang Solfrank, TooLs GmbH) +49-228-985800
Newsgroups: comp.unix.bsd
From: tim@kimba.catt.citri.edu.au (Tim Liddelow)
Subject: Setting up NE2000 card for easy ftp 
Organization: CATT Centre at CITRI, Melbourne, Australia
Date: Thu, 10 Sep 92 23:31:59 GMT

Ok, can someone who has succesfully installed the tiny distribution on their
hard disk tell me the correct ifconfig and route commands for setting up
an NE2000 card for an ftp session so I can get the bin and src quickly off
a local SUN ?  I followed the directions in the installation notes, but all
I got was "st" when trying to ftp (this is after a

ifconfig ne0 <386bsd box ip> netmask <netmask> etc...
route add default <local gateway ip>

)

No luck.  Any ideas ?

-- 
________________________________________________________________________________
  Tim Liddelow                                          for(;;) fork();
  Systems Programmer
  Centre of Advanced Technology in Telecommunications   My brain on a bad day.
  CITRI, Melbourne, Australia                           
  internet : tim@kimba.catt.citri.edu.au                
  Phone : +61 3 282 2455   Fax : +61 3 282 2444	        
________________________________________________________________________________
Newsgroups: comp.unix.bsd
From: rminnich@super.org (Ronald G Minnich)
Subject: Re: 386BSD & COMPAQ 486/33
Organization: Supercomputing Research Center (Bowie, MD)
Date: Tue, 8 Sep 1992 02:31:38 GMT

In article <1992Sep7.112452.5403@csd.uch.gr> kanagn@ikaros.cc.uch.gr (Kostas Anagnostakis) writes:
>I tried to boot 386BSD on a COMPAQ 486/33 / 4 MB RAM but it didn't work.
>It didn't even get to the "386BSD etc" notice. Has anybody out there gone
>into the same problem ? 

as things currently stand compaq's won't boot it at all. any compaq. 
I only have talked to one person who has gotten it to go, one compaq
in a room full of compaqs. nobody knows why. I looked into it but don't 
have time to fool with it; I have no documentation on the machine 
and hate debugging in that mode when I know it is unnecessary. 
I am going to drop a Kbuck on bsdi and hope they have something that works. 

One thing you could try that has been recommended to me is to 
junk the COMPAQ ROMS and replace them with AMI roms. 

If the bsdi path doesn't work I am going to rip the compaq motherboards out
of the 3 deskpro/25 machines I have, 
replace them with cheap clone motherboards that
work, and take the compaq motherboards out for a little target practice. 
Should be fun. Should cost < $1500. 

Cheap advice: if you are looking for a machine to run 386bsd, don't get a 
compaq of any stripe.
ron

-- 
--------------------------------------------------------------------------------
satisfaction: the feeling you get when you        | rminnich@super.org
run newfs on a DOS disk so you can install 386BSD.| (301)-805-7451
Now if only I could do this to AIX on the RS/6k ...|
From: adam@micromuse.co.uk (Adam Kerrison)
Newsgroups: comp.unix.bsd
Subject: 386BSD Filesystem bug ?
Date: 10 Sep 92 17:00:25 GMT
Reply-To: adam@micromuse.co.uk
Organization: MicroMuse Ltd, London, Uk

As I reported in a previous posting, I am having trouble with my filesystem
under 386BSD. I have an IDE disk (Seagate ST1239A) which is all BSD (no DOS)
in 3 partitions.

Having got X386 running successfully I am now trying to compile XFig on my
system. As the make reached the third file I recieved the following message:

/: bad dir ino 2 offset 512: mangled entry
panic: bad dir
updating disks before reboting ...

after a long wait the machine showed no signs of rebooting so I hit the 
reset switch. Once the machine had powered up again it refused to read
the BSD disk (insisting that the absent disk in drive a: was a non-system
disk - surprise, surprise) - This is a problem I have reported before.

So I powered off and on and the machine booted fine - fsck reported NO problems.

Help me please !! Have I found a bug in the filesystem - does anybody else have
this problem - do I need a patch ...

There could be a lot of reasons for this. I'd like to get some feedback before
I go poking around in the Kernel sources .....

Thanks for any advice/opinions/flames etc etc

Adam

---
===========================================================================
Adam Kerrison                  | Phone : +44 71 352 7774
Technical Support              | Fax   : +44 71 351 7834
MicroMuse Ltd                  | Personal E-mail: adam@micromuse.co.uk 
London SW10 0RN                | Support E-mail : support@micromuse.co.uk 
===========================================================================
Newsgroups: comp.unix.bsd
From: rkrouse@netcom.com (Robert K. Rouse)
Subject: How to setup modem?
Date: Sun, 13 Sep 92 17:16:34 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Keywords: modem,tip,cu



Experts,
	I have a 2400 baud hayes compatible modem connect to
com2.  What do i do the call out using "tip" or "cu".

-- 
==========================================================================
            Robert K. Rouse		rkrouse@netcom.com
--------------------------------------------------------------------------
 "VOTE! - use it or lose it" 
--------------------------------------------------------------------------
From: eddy@aludra.usc.edu (George Edmond Eddy)
Newsgroups: comp.unix.bsd
Subject: IDE and bad sectors.
Date: 11 Sep 1992 16:25:10 -0700
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: aludra.usc.edu

How does one deal with bad sectors on an IDE hardrive?  

After I had done the disklabel and newfs on a conners 3204, the 
disklabel showed a bad sector map (paraphrase) in the flags field
and went into the endless reboot cycle.  i used disklabel -e to
clear the flags field, and everything proceeded fine, (this,
however is wrong!).  It was suggested that i run bad144, however
i read the INSTALL.NOTES and know not to do this!  

Now i suffer from magically corrupting cp, rm and mv commands.
I will rebuild the commands mv 'em into bin, everything is fine
for a while, then WHAM! they start core dumping, (in the call to
rindex).  i'll do a diff on the versions in the build directory
vs. those in /bin, and diff claims there are differences????

So will some kind soul illuminate me as to how to handle bad sectors
on an IDE drive?  or should that flag be showing up at all???

thank you!

- rusty


eddy@usc.edu
rusty@kirra.ema.rockwell.com

Newsgroups: comp.unix.bsd
From: umrose05@ccu.umanitoba.ca (Dave Rose)
Subject: 386BSD: news stuff
Organization: University of Manitoba, Winnipeg, Canada
Date: Wed, 9 Sep 1992 21:42:31 GMT

Hello,

	Has anyone gotten cnews to successfully compile on 386bsd? If so, 
could you post what version of cnews and the fixes needed to get it to
run? Also, what about nn6.14?

Newsgroups: comp.unix.bsd
From: david@mlb.geomechanics.csiro.au (David Le Blanc)
Subject: Re: Problem with 386BSD and Network
Organization: CSIRO DIT (Melb.)
Date:  7 Sep 92 00:16:43 GMT

>> ne0 ethernet address 00:00:4d:21:65:97 at 0x300 irq9 on isa
>I have a wd elite 16 on irq 2, and the machine comes back as irq 9 also.

Just a point to you all. Due to the utter rubbish that the PC motherboard
must conform to (you know, the IBM original :-)) It is forced to act like
an original AT.

AT architecture has a problem with the interrupt hardware (a conflict
somewhere but I cannot remember the specifics) and the hardware automatically
takes interrupt 2, and cascades it so that it is now in the SECOND interrupt
controller. This 'cascading' of interrupts is done mostly invisibly, but
you must remember that interrupts on a pc go
1 9 3 4 5 6 7 8.
Then you directly program the second controller.

Its stupid, but its backward compatible with the XT (as if anybody cares!)

>mark@student.business.uwo.ca (Mark Bramwell CS Staff)
>Western Business School  --  London, Ontario
--
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.
Organization: Penn State University
Date: Tue, 8 Sep 1992 03:35:10 EDT
From: Mark Solsman <MHS108@psuvm.psu.edu>
Newsgroups: comp.unix.bsd
Subject: how do I put 386bsd on drive 2

Hello -

I have a question that I cant seem to find an answer to in the docs-

I have two esdi drives, I would like to make the first drive msdos, and
the second drive 386bsd.  Can I do this, and how?  I am not sure, because
386bsd install only seems to look at drive one, and doesn't notice the big
vacient sign on the partition table for drive two...

any/all help would be greatly appreciated!

-----
Mark Solsman

The Pennsylvania State University  -  University Park, Pennsylvania
                "My opinions are not that of my own"
From: mfg@castle.ed.ac.uk (M Gordon)
Newsgroups: comp.unix.bsd
Subject: Setting up 386BSD to use a UK keyboard
Date: 6 Sep 92 14:47:49 GMT
Organization: Edinburgh University

Has anyone set 386BSD up to use other than a US keyboard layout?
Looking through the source it seems that I have to change the
tables that map scan codes to characters in pccons.c (does anything
else need changing?), but I thought I'd check to see if anyone else
has already done this before I start.

Thanks

-- 
                                                         _   _   _    _   _	
Michael Gordon - mfg@castle.ed.ac.uk OR ee.ed.ac.uk     | |_| |_| |__| |_| |   
EE Dept, Edinburgh University                           | . . . .      . . |    
It's not an optical illusion, it just looks like one    |_________|~~|_____|    
Newsgroups: comp.unix.bsd
From: watkins@garnet.idbsu.edu (Chris Watkins)
Subject: X386 - no screens found XIO: fatal IO error 32
Organization: Computer Exchange & Leasing
Date: Sat, 5 Sep 1992 07:10:44 GMT



I have recently just installed 386BSD. I love it.
But I am having a problem with the X 1.2E 1.0.1 port

I made /dev/vga

then I got
Fatal server error:
no screens found
so I looked over my Xconfig file..
I set the chipset for "pvga"
my card is a Paradise prof vga compatible card.

I have a feeling it's the video card.
But, I looked in modeDB.txt and found that someone had tried an ATI
wonder. Now I wasn't sure if the 386BSD port supported that chipset or
not, but I tried the card anyway.  same results.
Is the answer a cheap ET4000?

Thanks,
chris
Newsgroups: comp.unix.bsd