HDTenEightyP/NetNews huggingface dataset:
From: serini@ghost.dsi.unimi.it (Piero Serini)
Subject: Re: At boot: file too big to load
Organization: Computer Science Dep. - Milan University
Date: Mon, 23 Nov 1992 16:03:17 GMT

julian@tfs.com (Julian Elischer) writes:

>In article <1992Nov22.225044.1344@ghost.dsi.unimi.it> serini@ghost.dsi.unimi.it (Piero Serini) writes:
>>Hi.
...
>>if(roundup(x.a_text, 4096) + x.a_data + x.a_bss > (unsigned)&fil) {
>>	printf("File too big to load");
>>	return;
>>}
>>The meaning of the code is clear, but I can't figure out why
>>a kernel which size is 466730 is 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.

yes, you're right. The "large" kernel will use 724848 bytes, and 
the start address of the struct "fil" varies from 621736 to 622376.
The distribution stripped kernel reaches 526144.
My kernel wants 668580, still too much.
I put a printf in bootas code to know this. (start addr of the struct "fil")
>>What do you (all) think about casting fil address a bit higher ?

>no

>>I'm waiting for your suggestions ...

>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.

Whe have to wait for it, then :)

>I frequently have to decide what to leave out of the kernel
>to add some other feature.

Bye

------------------------------------------ Piero Serini -----------------
                               E-mail: serini@ghost.dsi.unimi.it   
Piero Serini	               or: piero@strider.st.dsi.unimi.it
Via Giambologna, 1
I  20136  MILANO  MI                Computer Science Dept.
ITALY                        Universita' Statale - Milano - ITALY
-------------------------------------------------------------------------
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.unix.bsd
Subject: Re: The SCSI Controller saga continues...
Date: 18 Nov 92 03:43:51 GMT
Article-I.D.: spcvxb.1992Nov17.224351.4470
Organization: St. Peter's College, US

In article <1eb50mINNoc@hrd769.brooks.af.mil>, burgess@hrd769.brooks.af.mil (Dave Burgess) writes:
>   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.
> 
> Huh? 

  It looks your hard disk controller provides emulation registers for the AT-
type controller. That means that it can be used without special drivers for
things like DOS, Novell Netware, etc.

  However, depending on what the OS does to poke the registers on a boot, the
controller may change the drive's reported geometry. That would cause all sorts
of odd behavior on booting.

  I'd try sticking the wdboot out there and see if that makes it bootable. Of
course, you're liable to get better performance if you can run the controller
in native (SCSI) mode, rather than relying on the emulation registers.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
Newsgroups: comp.unix.bsd
From: sharmila@Tandem.com (Sharmila Podury)
Subject: HELP: Beginner's question on installing 386BSD 
Organization: Tandem Computers
Date: Sat, 21 Nov 1992 02:57:19 GMT


Hi:

I am trying to install 386BSD Unix on my 486 pc with 200MB disk space. I have
managed to create a partition for DOS/WIndows etc. (about 80 MB) using the fdisk
program.  However, I am unable to set second partition as active so that I can load
UNIX.  I am not sure that I am doing the right steps in installing 386BSD 
(IMO, the installation notes are rather cryptic for me to understand)

I would very much appreciate any help from people who have successfully managed
to install 386BSD on their PCs.

Newsgroups: comp.unix.bsd
From: cgt@gargoyle.uchicago.edu (Carlos Talbot)
Subject: [386bsd]: rarpd and bootpd
Keywords: rarpd bootpd
Organization: University of Chicago Computing Organizations
Date: Mon, 16 Nov 1992 20:32:09 GMT

Does anyone know if they are supplied with 386bsd? I've checked the net2
sources at ftp.uu.net but couldn't find it. Is this code publicly
available? Any help would be appreciated. Thanks.


Carlos Talbot                     | E-Mail: ctalbot@lucpul.it.luc.edu
Office of Fiscal Affaris          |         ctalbot@mica.meddean.luc.edu
Stritch School Of Medicine        |         cgt@gargoyle.uchicago.edu
Loyola University Medical Center  | Tel. 708-216-6347
Carlos Talbot                     | E-Mail: ctalbot@lucpul.it.luc.edu
Office of Fiscal Affaris          |         ctalbot@mica.meddean.luc.edu
Stritch School Of Medicine        |         cgt@gargoyle.uchicago.edu
Loyola University Medical Center  | Tel. 708-216-6347
Newsgroups: comp.unix.bsd
From: watpod77@alfred.carleton.ca (Andrew Cornwall)
Subject: [386BSD] Newbie SCSI question
Keywords: SCSI,Adaptec,386
Organization: Carleton University
Date: Sat, 21 Nov 1992 04:02:39 GMT

 I've been trying to set up a 386BSD system on my machine, but I can't
get the 0.1 boot disk to boot. I've got an Adaptec 1542B, and when I
installed it in the default configuration and booted the 0.1 bootable,
it didn't recognize the controller. I know the controller works,
'cause I was able to go into DOS and use the HD... but I can't seem to
get 386BSD to talk to it.

 The weird thing is that when 0.1 boots, I don't get any controller
messages at all! I can talk to the floppy OK (it's on the same card),
but after the fd is recognized, the as isn't. According to the FAQ,
this means that something is incorrectly-configured on the card. The
default on the card is IRQ 11, DMA 5, BIOS enabled at DC000. I changed
the BIOS to be at C8000, still no dice. Then I changed the IRQ to 14,
and still nothing happens.

 Unfortunately, I'm a SCSI neophyte, so the one-page manual that came
with the 1542B isn't much help. It's got lots of options that I can
change, but doesn't tell me anything about what they are. If anyone
can tell me what I'm doing wrong, please do so. Also, if you could
point me to a good SCSI book, I'd love to read it :-)

          Andrew Jr.
---
Andrew Cornwall
watpod77@alfred.ccs.carleton.ca

Newsgroups: comp.unix.bsd
From: tcombs@dacapo.urbana.mcd.mot.com (Tim Combs)
Subject: Micro-channel
Organization: Motorola Computer Group, Urbana Design Center
Date: Fri, 20 Nov 1992 22:57:00 GMT

This may be a dumb question considering the cost but is anyone working
on a micro-channel version?








________________________________________________________________________________
Tim Combs
tcombs@urbana.mcd.mot.com

Newsgroups: comp.unix.bsd
From: mark@student.business.uwo.ca (Mark Bramwell CS STAFF)
Subject: Re: [386BSD] SCSI Bootstrap Method?
Organization: University of Western Ontario
Date: Mon, 16 Nov 1992 14:13:23 GMT

tweten@wilbur.nas.nasa.gov (Dave Tweten) writes:

> I need to find out how to bootstrap 386bsd, given a machine which only
> has a SCSI hard disk.  When Julian Elischer posted his SCSI driver
> code, I thought I had it made, but I haven't been able to get past the
> need for a SCSI capable bootable filesystem diskette.  I've searched
> agate.berkeley.edu and ref.tfs.com, and haven't found a suitable *.fs
> file on either.  I need help!


I have 386bsd running with no problems as far as booting is concerned.

I am running an adaptec 1542 with a 1.2gig fujitsui scsi drive.
I set the cmos drive to 0 'no drives' and let the scsi board boot the
machine.  All seems to be ok.  I am running the stock kernel.


> 
> In addition to its SCSI hard disk, my machine also has the usual
> diskettes (1.44 MB and 1.2 MB), a tape, COM ports and LPT ports, but
> the only kind of hard disk it has is SCSI.  It is an EISA bus machine,
> and the SCSI host bus adapter is an Adaptec 1740.
> 
> Am I missing an obvious bootstrap method?  Does my desired *.fs file
> already exist anywhere?  Come to think of it, is there a BIOS ROM *.fs
> file anywhere?  It would be absurd as a running system, but potentially
> useful for bootstrapping.  How has 386bsd been brought up on other SCSI
> machines?  Any advice will be greatly appreciated.
> 
> -- 
> ---------------------------------------------------------------------------
> Dave Tweten						tweten@nas.nasa.gov
> NASA Ames Research Center, M/S 258-5			     (415) 604-4416
> Moffett Field, CA  94035-1000				FAX: (415) 604-4377


mark@student.business.uwo.ca (Mark Bramwell CS STAFF)
Western Business School  --  London, Ontario
Newsgroups: comp.unix.bsd
From: serini@ghost.dsi.unimi.it (Piero Serini)
Subject: At boot: file too big to load
Organization: Computer Science Dep. - Milan University
Date: Sun, 22 Nov 1992 22:50:44 GMT

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 gave a look into boot.c code, and found the following lines:

if(roundup(x.a_text, 4096) + x.a_data + x.a_bss > (unsigned)&fil) {
	printf("File too big to load");
	return;
}

now, x is declared struct exec x   , and fil struct dinode fil;

The meaning of the code is clear, but I can't figure out why
a kernel which size is 466730 is too big to load.
What do you (all) think about casting fil address a bit higher ?

I'm waiting for your suggestions ...

Bye



------------------------------------------ Piero Serini -----------------
                               E-mail: serini@ghost.dsi.unimi.it   
Piero Serini	               or: piero@strider.st.dsi.unimi.it
Via Giambologna, 1
I  20136  MILANO  MI                Computer Science Dept.
ITALY                        Universita' Statale - Milano - ITALY
-------------------------------------------------------------------------
From: fmayhar@altair.mpd.tandem.com (Frank Mayhar)
Newsgroups: comp.unix.bsd
Subject: Disk statistics on 386bsd, and porting vmstat.
Date: 17 Nov 92 23:14:35 GMT
Reply-To: fmayhar@mpd.tandem.com
Organization: Tandem Computers (MPD) Austin, TX

I've finally gotten 386bsd up and running on my 486 at home, with all patches
installed, and things appear to be working great.

So, I noticed that the distribution didn't include a 'vmstat' command, so I
can't see all those fancy statistics that I'm used to seeing on my Sun at work.
Hmm, OK, I'll get the BSD one on ftp.uu.net, and port it.  Early on I notice
that there are little or no disk statistics being kept!  I'm specifically
referring to the statistics in <sys/dkstat.h>, more specifically things like
dk_xfer and dk_busy (which lets kern_clock keep dk_time), et al.

Actually, the statistics in the generic kernel (what there are of them) all
appear to be there, but nothing is kept in the i386 device drivers.  I grabbed
the tahoe stuff from ftp.uu.net for a reference, and it's all there, so I'm a
tad confused.

So my first question is, why is this?  Secondly, is anyone working on instru-
menting wd.c, as.c, fd.c, etc. (is that all of them?) for this capability? I
can see that it will take changes to the isa_device and isa_driver structures,
as well as changes to isa_configure() and the device drivers themselves.

As you can see, I've actually already started looking into it, but I want to
know if anyone else is doing work here before I get too committed.  Perhaps we
can share expertise and split up the work.  I'm also investigating Tom Ivar
Helbekkmo's wd driver, and may use that as a starting point, rather than the
distributed one.

Any suggestions, information, advice would be appreciated.  Thanks.
-- 
Frank Mayhar  fmayhar@mpd.tandem.com
              Tandem Computers, Inc.  Micro Products Division
              14231 Tandem Blvd., Austin, TX  78728    Phone:  (512) 244-8969
Organization: Stanford Linear Accelerator Center
Date: Monday, 23 Nov 1992 10:20:19 PST
From: <CALT@SLACVM.SLAC.STANFORD.EDU>
Newsgroups: comp.unix.bsd
Subject: ALWAYS 2000 SCSI controller

Hello -- Does an ALWAYS 2000 16-Bit SCSI controller work with
bsd386 and XFree86?
Thanks!
Ching Shih
shih@cithex.bitnet
shih@cithex.caltech.edu
Newsgroups: comp.unix.bsd
From: mc499424@longs.LANCE.ColoState.Edu (amine chouicha)
Subject: FAQ site for comp.unix.bsd 
Date: Wed, 18 Nov 1992 03:51:44 GMT
Organization: Colorado State U. Engineering College

 Hi,
 Where can I find FAQ for this news group
From: david@otago.ac.nz (David Harris)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Warnings rebuilding libc.a
Date: 19 Nov 92 13:48:01 +1300
Organization: University of Otago, Dunedin, New Zealand

Maybe I'm just paranoid, but...

In the process of installing the crypt security support, I made the mistake
of rebuilding libc.a instead of simply replacing crypt_dummy.o with crypt.o
- for anyone out there contemplating this, it took nearly three hours and
2 crashes on a 486/50 to rebuild the libs - I don't recommend it unless you
have to do it.

However, in the process of rebuilding both the standard and profiled libs,
I noticed a number of warnings or perhaps errors from ar, of the general
form "cyclic data" - there were about 20 of them all at once, but they
scrolled past too fast for me to note down. As well, the resulting libc.a
was about 11KB larger than the bindist version.

Because of these warnings, I didn't want to risk installing the rebuilt
libc.a, so I simply patched the old one. Am I being paranoid? Are these
warnings in fact benign?

PS: Anyone know why all the ethernet cards are defaulted to IRQ2? On other
systems (NetWare and DOS) they warn you not to select IRQ2 for ethernet
cards in VGA systems because of possible conflicts with the VBL interrupt.
What's more, I don't think any of the supported cards uses IRQ2 as a
default out of the box (usually IRQ5 is safest, although most default to
IRQ3 which conflicts with COM2).

Cheers!

-- David --

=-=-=-=-=-=-=-=-=-=-=-=-=-=|  David Harris  |=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Consultant, Computing Services Centre,              phone: (+64) 3-4536889
University of Otago, Dunedin, New Zealand.          fax:   (+64) 3-4536612
   Internet email: david@pmail.gen.nz (preferred), or david@otago.ac.nz
From: wjin@cs.uh.edu (W. Woody Jin)
Newsgroups: comp.unix.bsd
Subject: Re: dist.fs boot infinity-loop
Date: 21 Nov 1992 07:22:14 GMT
Organization: University of Houston
NNTP-Posting-Host: modigliani.cs.uh.edu
Keywords: boot loop

In article <BxxHtz.2sz@encore.com> idequesa@encore.com (Ivan Dequesada) writes:
>
>Does anyone know the difference between BSD's dist.fs and
>LINUX's dist.fs??
>
>It seems that some PCs (Including (but not limited to) Compaq
>Systems and TI's) hang in an infinite loop when booting from
>the dist.fs diskette (3 1/2", 1.44 Mbytes).

I had a similar problem with fixit.fs.  Someone hinted to me that 
it might be because of fixit.fs corruption.  So, I freshly formatted
a diskette, re-ftp'ed and re-download it.  Then the problem was gone.

Just a possibility.

-- 
____   ____  ____ ____________________________________ (___) _________________
|  |   |  |  |  |  W. Woody Jin (wjin@cs.uh.edu)       (o o)      Moo.... 
|  |   |  |__|  |  PhD Student. Research Asst.  o=======\ /  I'm  a Cow Lover.
|  |   |        |  Dept. of Computer Science   / |     ||O   My wife  was born
\  |---|  |--|  |  University of Houston      `  ||'---||    in Cow year. Mooo
 \____/|__|  |__| _______________________________^^    ^^_____________________

Newsgroups: comp.unix.bsd
From: stripes@pix.com (Josh Osborne)
Subject: Re: ->386bsd! man-pages.Z ?
Organization: Pix Technologies -- The company with no adult supervision
Date: Wed, 18 Nov 1992 03:16:57 GMT

In article <JKH.92Nov16125945@whisker.lotus.ie> jkh@whisker.lotus.ie (Jordan K. Hubbard) writes:
>	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)..

Unless the BNR2 man is unlike it's ancesters it will be far slower then
the Perl man, and have far fewer fetures (and yes, many of the fetures
are useful, many are useless).  Of corse I don't know which is larger (including
the perl executable, excluuding it, the perl man is smaller)...
-- 
           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
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: ref.tfs.com frequently unrecognized by DNS
Date: 22 Nov 92 19:06:04
Organization: Kernel Hackers 'r' Us
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: mark@student.business.uwo.ca's message of Mon, 23 Nov 1992 02:00:55 GMT

i tracked it down, too, a few days ago...

UCB is a secondary for TFS, and doesn't have the correct info.

I asked Julian if he had updated the serial number when he
added ref, and he had, so i have no idea why the UCB nameservers
didn't get the correct info.

Unfortunately, i don't have time to beat the people who manage the nameservers
around here to "get it right" right now...

it bites me really hard, because around here, ref is *never* known,
even tho it's only a few blocks away... 8-)

<sigh>

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
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: 928 chipset?  was Re: What is the best VGA card for 386BSD???
Date: 20 Nov 92 07:24:06 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <1992Nov19.093138.14545@netcom.com>, hasty@netcom.com
(Amancio Hasty Jr) writes:

[ deleted ]
 
> S3 chipsets  come  basically in three flavors:
> (1) 911 slowest chipset
> (2) 924
> (3) 801 fastest chipset

Was there supposed to be a 928 model? or is this the 801 chipset mentioned
above?

-- 
Gary Browning        | Exhilaration is that feeling you get just after a
		     | great idea hits you, and just before you realize
                     | what is wrong with it.
Newsgroups: comp.unix.bsd
From: russo@cucbs.chem.columbia.edu (Thomas Russo)
Subject: [386BSD] Disklabeling a DOS formatted floppy
Organization: Center for Biomolecular Simulation, Department of Chemistry,
	Columbia University
Date: Sun, 22 Nov 1992 19:59:45 GMT

No, I don't want to know how to low-level format a floppy -- I know I
need to do that from DOS.

What I WANT to do now is to make a filesystem on a floppy (either 5.25
or 3.5in), just like the dist.fs and fixit.fs floppies have
filesystems, but for the life of me I can't figure out how to do it.
This is what I've tried (some of them based on things I remember
reading here on how to make bootable floppies, which isn't what I
really want to do but hey, I just want to be able to mount a freaking
floppy!):

DOS
format a: (that's the 5.25, or b:, the 3.5)

386BSD:

1) newfs /dev/fd0a

or

2) disklabel -w fd0a floppy5 

or

3) disklabel fd0a > junk -- this once gave me a skeletal disklabel in
junk, but only once.
   disklabel -R fd0a junk /usr/mdec/fdboot /usr/mdec/bootfd

or

4) cat /usr/mdec/fdboot /usr/mdec/bootfd > /dev/rfd0a

But none of these things do ANYTHING other than give me an error of
the sort "ioctl: TIOCFOOBARBLETCH: device not configured", or "can't
read disk label"

I'm confused.

I have tried this using DOS formatted diskettes and unformatted
diskettes (even though I knew that wasn't supposed to work), and I
cannot get the damned thing labeled, much less newfs it.

What precise steps do I need to take to get a floppy disk to have a
bsd filesystem on it?

On another front, I seem to recall someone saying something about how
to get mdir to stop saying "file not found" and to produce a real
directory of the dos floppy, but I didn't save it.  Could someone tell
me why mdir (and mformat) is doing this and what I have to do to stop
it.

-- 
Thomas Russo			russo@nile.chem.columbia.edu
Department of Chemistry and Center for Biomolecular Simulation
Columbia University
Newsgroups: comp.unix.bsd
From: jkh@esel.lotus.com (Jordan K Hubbard)
Subject: PCFS driver posted
Organization: Lotus Ireland
Distribution: comp
Date: 18 Nov 92 10:42:51

Seems to work great, except it doesn't seem to distinguish between files with
identical names but differing extents.  If you have, for example:

drosfile.foo
drosfile.bar

You can look at each one, but doing a directory listing will only
show you one of them.

Anyone else seen this?

						Jordan
Newsgroups: comp.unix.bsd
From: colin@cs.curtin.edu.au (Colin Manning)
Subject: What is the best VGA card for 386BSD???
Organization: Curtin University of Technology
Date: Wed, 18 Nov 1992 02:38:45 GMT

Hi,
	My TVGA card neads replacing, and as I plan an running 386BSD most of
the time (with X) I was wondering which is the best card I could replace it 
with.

	What is "the best" card, and what is "the best value for money" card?
Unfortunatly I don't have an unlimited money supply, and worst of all it will
be my money that I will be spending :-)

Colin.
--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
Newsgroups: comp.unix.bsd
From: tom@izf.tno.nl (Tom Vijlbrief)
Subject: Re: dist.fs boot infinity-loop
Keywords: boot loop
Organization: TNO Institute for Perception
Date: Mon, 23 Nov 1992 16:34:12 GMT

wjin@cs.uh.edu (W. Woody Jin) writes:

>>It seems that some PCs (Including (but not limited to) Compaq
>>Systems and TI's) hang in an infinite loop when booting from
>>the dist.fs diskette (3 1/2", 1.44 Mbytes).

Yep,

The Compaq reboot from floppy problem was fixed a few months ago
by someone from Japan (Sorry, I forgot your name).

I have distributed a new bootblock for the floppies and someone
(Sorry forgot his name too and I last my mailrecord:-( )
placed it on an archive (can you please repost the archive name).

If you get no response than I'll repost it or place it
on our own archive. (we just got internet :-)

Tom
From: ifbb657@ccwf.cc.utexas.edu (Douglas Floyd)
Newsgroups: comp.unix.bsd
Subject: Thanks, and a question
Date: 16 Nov 92 21:45:26 GMT
Reply-To: ifbb657@ccwf.cc.utexas.edu (Douglas Floyd)
Organization: The University of Texas at Austin, Austin TX
Originator: ifbb657@donald.cc.utexas.edu


Thanks for your help with the floppy drive.

Here is another question:

Sometimes when 386bsd boots up, the keyboard locks up,
the only way to get out of it is to turn off the computer
and back on again.  This happens randomly about 1 in 3
times.

I am using a Dell 386/33 with 4 MB RAM, VGA monitor, and
a 80 MB Quantum IDE hard disk.  There is a MS-Mouse attached,
also.  There is also a COM1 connection between the Dell and
a Mac SE via a null modem cable.

ad THANKS vance,


-- 
********** ifbb657@ccwf.cc.utexas.edu (Douglas Floyd) **********
Windows NT:                  * Disclaimer:  I speak for myself *
                             ***********************************
You WANT your hard drive trashed now.