HDTenEightyP/NetNews huggingface dataset:
From: ABS1 <ABS1@musica.macarthur.uws.EDU.AU>
Subject: 386BSD & WD7000 Fasst SCSI
Organization: University of Western Sydney, Macarthur
Date: Mon, 16 Nov 1992 22:33:00 GMT

Has anybody got any ideas on running 386BSD on a 386 with
WD 7000 SCSI controller.

Joseph Chillari
UWS Macarthur.

Newsgroups: comp.unix.bsd
From: az7141633@v9001 (AZ7141633)
Subject: [XFree86]  Help needed badly
News-Software: VAX/VMS VNEWS 1.41    
Keywords: Help, XFree86, 386BSD 
Organization: Nanyang Technological University - Singapore
Date: Fri, 20 Nov 1992 12:25:00 GMT

I am facing the same problem as what both Thanh Luu and S.X. Xue faced;  but I
could not find any replies to their queries in comp.unix.bsd.
I would appreciate if anyone could help us get started with XFree86 and 386BSD.
Thanks in advance.

Sok
Internet addr:  az7141633@ntuvax.ntu.ac.sg
With Love from Nanyang Technological Univ of Singapore


>X-NEWS: ntuvax.ntu.ac.sg comp.unix.bsd: 7901
>From: tpl20@pswd.amdahl.com (Thanh Luu)
>Subject: Problem starting up X
>Date: 13 Nov 92 17:46:56 GMT
>
>I installed XFree86 and the kernel patch.  When I tried to bring up X, using
>xinit, I got the following message:
>
>   XIO: fatal IO error 32 (broken pipe) on X server ":0.0"
>   after 0 requests (0 known processed) with 0 events remaining
>   The connection was probably broken by a server shutdown or KillClient
>
>What did I miss to do?  Thanks in advance.


>X-NEWS: ntuvax.ntu.ac.sg comp.unix.bsd: 7953
>From: sxx4519@ultb.isc.rit.edu (S.X. Xue)
>Subject: Starter needs help!
>Date: Mon, 16 Nov 1992 08:20:39 GMT
>
>I recently installed a copy XFree86 on my newly installed 386BSD. I am
>experiencing many problems. Hope experts out there would help me out.
>
>OS:
>   386BSD binary distribution from agate.berkeley.edu
>   No source distribution, no etc dirstribution
>   Updated kernel for XFree86
>   XFree86 bininary distribution from the same ftp host
>   X server is set to X386mono (trying to start generic VGA mode)
>
>Problems:
>   Printer driver missing (/dev/lp)
>   C compiler does not work with floating point numbers
>       -- all numbers are rounded off to intgers
>   Mtools does not work,
>       message-- init: open: No such a file or dirctory
>   X server will not start,
>       message-- Fatal I/O error 32. Broken pipe on X server...
From: julian@tfs.com (Julian Elischer)
Newsgroups: comp.unix.bsd
Subject: Re: At boot: file too big to load
Date: 23 Nov 92 07:02:12 GMT
Organization: TRW Financial Systems

In article <1992Nov22.225044.1344@ghost.dsi.unimi.it> serini@ghost.dsi.unimi.it (Piero Serini) writes:
>Hi.
>At the end I succeeded recompiling that damn kernel.
>A little problem still keeps me unhappy: if I install the new
>kernel in /386bsd, at boot time bootas tells me: file too big to load.
>
>I 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.

I'll bet that if yu do a 'size' on the kernel,
it shows that the sum of the partitions in the file are bigger than that.
don't forget the zero filled section is not in the file, it just bzeros it.



>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.
I frequently have to decide what to leave out of the kernel
to add some other feature.
Newsgroups: comp.unix.bsd
From: gtoal@nyx.cs.du.edu (Graham Toal)
Subject: [386BSD] Has anyone ported pgp20?
X-Disclaimer: Nyx is a public access Unix system run by the University
	of Denver for the Denver community.  The University has neither
	control over nor responsibility for the opinions of users.
Organization: Nyx, Public Access Unix at U. of Denver Math/CS dept.
Date: Sun, 22 Nov 92 23:56:56 GMT

I tried compiling pgp20 today - found one major problem: it uses toupper
and tolower but doesn't check their args are in range first with isalpha
and islower/isupper.  Actually I was amazed that gcc on 386bsd supported
that bogus old definition of toupper/tolower, but I guess there's a
reason for it somewhere.

Anyway, after that I was able to read the config file, and decode command-line
options OK.  But I still can't encrypt anything.  Following the instructions
to the letter, and doing all the tests, it seems not to find my encoding
key in my keyring.

If anyone has ported pgp20 please give me some hints!  And if you think it's
possible that what I've compiled *is* working, but it's common to misunderstand
the instructions... tell me that too.  I'm baffled at this stage.

Thanks.

G
From: james@raid.dell.com (James Van Artsdalen)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] A caution on using new man & gcc 2.3.1 notes.
Date: 15 Nov 92 23:29:02 GMT
Reply-To: james@raid.cactus.org (James Van Artsdalen)
Distribution: comp
Organization: Dell Computer Co

In <JKH.92Nov9195806@esel.lotus.com>, jkh@esel.lotus.com (Jordan K Hubbard) wrote:

> On a positive note, I compiled all of XFree86 1.1 with gcc 2.3.1 and
> it works great (with -O2 -m486).  2.3.1 obviously isn't as buggy
> as some people are claiming.

gcc 2.3.1 is quite reliable.

> Of course, when I tried to compile libc with it, it coredumped on
> ldexp.c, so it's not *that* robust either!

I would bet that there is an asm statement in ldexp.c that tries to
use 387 registers.  gcc 2.3.1 uses a different syntax for such
expressions than gcc 1.39, and it's unlikely that any asm statement
involving 387 regs will work without being rewritten.

That being said, an error message would have been more graceful than a
core dump.  I don't have access to 386bsd right now: please send a bug
report.
-- 
-- 
James R. Van Artsdalen          james@bigtex.cactus.org   "Live Free or Die"
Dell Computer Co    9505 Arboretum Blvd Austin TX 78759         512-338-8789
Newsgroups: comp.unix.bsd
From: venkat@uxh.cso.uiuc.edu (Venkat)
Subject: [BSD386] 'make' seems to take a long time - elm2.4
Followup-To: venkat@uiuc.edu
Organization: University of Illinois at Urbana
Date: Wed, 18 Nov 1992 16:25:57 GMT

I have been trying to install elm2.4 on my 386 running Bsd/386. After I answer
all the config questions and elm instructs me to run make, when I do so it
seems to take a long time. I have waited for about 4-5 mins and all the while
there is no disk activity. Is this normal ? Does 'make' take this long ?

Venkat
[venkat@uiuc.edu]
Newsgroups: comp.unix.bsd
From: torre@mom (Pat Torre)
Subject: sdboot
Summary: [386BSD] Where to get a copy of sdboot?
Organization: Computone, Corp.
Distribution: usa
Date: Fri, 20 Nov 92 00:28:09 GMT

Is there a copy of sdboot, bootsd  source somewere?
I dont have ftp so it needs to be available via mail server.
Any help would be appreciated.

It should not be very big, If someone could mail it
to me I would appreciate it.

thanks,
pat
From: chk@mcshh.Hanse.DE (Christian Kuhtz)
Newsgroups: comp.unix.bsd
Subject: [386BSD] configuring serial to 8n1, multiport serials.
Keywords: bsd, 386bsd, unix, 386BSD, serial, device, help, faq, question
Date: 15 Nov 92 13:32:00 GMT
Organization: Point of Presence & MCS Hamburg

Hi,

I know that this questions are possibly FAQ Questions, but I did not
found an answer in the FAQs. Please help me cause the elder news about
this topic are all expired... :(

1.) How can I configure the serials to 8N1, 8 bit, no parity, 1 stopbit ?
    I need this setting for an dialin port. This port has to be locked
    to 19200, 8N1.
    It's no problem to do stty cs -parenb -clocal </dev/com{1,2,3,4}
    but that does only work after login, cause it's no gettyredefinition.
    Please tell me how to configure /etc/gettytab for such purposes.
    Sorry, but it's urgent, I have to get this machine up with this
    setting. Hope you can help me. Thx for reading and probably you
    can mail an answer.

2.) Does 386BSD support AST-Research compatible (or XENIX-compatible :)
   4 Port cards that use only one Interrupt ? If not is there any
    chance to patch it ?


Thx in advance for all help.
		Regards,    Christian
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: [386BSD] SCSI Bootstrap Method?
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
	<1c6BuB4w165w@student.business.uwo.ca>
Date: Mon, 16 Nov 1992 17:58:57 GMT

In article <1c6BuB4w165w@student.business.uwo.ca> mark@student.business.uwo.ca (Mark Bramwell CS STAFF) writes:
   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.


Enabling the scsi adapter's bios also has beneficial effects even if
you don't boot from the scsi drive.

I've got an identical setup -- adaptec 1542 with a 1.2gig fujitsui
scsi drive -- but boot from an ide.  The bios on the adaptec 1542B
seems to initialze the drive into a state which prevents error which
occur otherwise when cold booting.  Rich
Newsgroups: comp.unix.bsd
From: pingo@guug.de (Thomas Meidinger)
Subject: Re: [386bsd/X] XDM with DES...
Organization: Technical University of Munich, Germany
Date: Fri, 20 Nov 1992 14:07:36 GMT

rkb55989@dcl-nxt50 (Rafal Krzysztof Boni) writes:

>	Yet another question... I have the X386/XS3 bin distribution, and
>	definitely do not have room for X11R5 sources on my machine...

>	So my question is this... 
>		What are the mininal sources I need to recompile XDM
>		with crypt support? What subset of X11R5 sources do I
>		need, and what else do I have to do before I can make
>		away happily?? Seeing as EXPORT.LCS.MIT.EDU has an
>		un-packed R5 source tree, I can grab files off there...

>		Alternately, is there anyone out there who has a working
>		XDM with crypt installed that would want to put it up
>		somewhere [discreetly] and let me know???

>				Thanks once again,
>						Rafal
You can grab the sources and the binary from
cony.gsf.de [146.107.1.2] : ~ftp/pub/xdm

cu,
 Pingo

--------------------------------------------------------------------------------
 Thomas "Pingo" Meidinger               GSF - National Center for Environmental
                                        Sciences GmbH Munich (Germany)
                                        e-mail: pingo@gsf.de
                                        pingo@guug.de
--------------------------------------------------------------------------------
--
--------------------------------------------------------------------------------
 Thomas "Pingo" Meidinger               GSF - National Centre for Environmental
                                        Sciences GmbH Muenchen
                                e-mail: pingo@gsf.de
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: [BSD386] 'make' seems to take a long time - elm2.4
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
	<1992Nov19.035447.29105@moxie.hou.tx.us>
Date: Sat, 21 Nov 1992 17:59:38 GMT

In article <1992Nov19.035447.29105@moxie.hou.tx.us> hackney@moxie.hou.tx.us (Greg Hackney) writes:
   venkat@uxh.cso.uiuc.edu (Venkat) writes:

   >I have been trying to install elm2.4 on my 386 running Bsd/386. After I answer
   >all the config questions and elm instructs me to run make, when I do so it
   >seems to take a long time. I have waited for about 4-5 mins and all the while
   >there is no disk activity. Is this normal ? Does 'make' take this long ?

   It won't compile right with the existing version of /bin/sh. You
   need to copy 386BSD's bash onto /bin/sh.

This may cause you problems when booting.  It's also going to expose
all the sh dependent code in system shell scripts.  Rich
Newsgroups: comp.unix.bsd
From: meissner@osf.org (Michael Meissner)
Subject: Re: [386BSD] Gcc 2.3.1 & kernel -> SUCCESS/2
Organization: Open Software Foundation
Date: 18 Nov 92 17:48:44

In article <1992Nov16.134717.22679@dde.dk> kim@dde.dk (Kim Andersen) writes:

| I would like to report a partial success with using gcc-2.3.1 for kernel
| compiling.
| 
| I had to do the following in order to be able to link/boot this new kernel:
| 
| compile init_main.c with gcc-1.39, otherwise the link stage would fail with
| symbol error for "___main".

Since the kernel doesn't have any C++ files compiled in, you can just add:

	/* NOP the call to set up G++ static constructors and destructors
	   with GCC 2+, since we don't link with libgcc.a.  */

	__main(){}

(I had to do the same thing for the OSF/1 kernel).

--
Michael Meissner	email: meissner@osf.org		phone: 617-621-8861
Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142

You are in a twisty little passage of standards, all conflicting.
Newsgroups: comp.unix.bsd
From: "Michael Squires" <mikes@moose.cs.indiana.edu>
Subject: [386BSD] Checking disk for bad blocks
Organization: Indiana University, Bloomington
Date: Tue, 17 Nov 1992 23:50:17 -0500

I'm trying to use an older drive with a fair number of bad sectors on it,
a Miniscribe 660MB ESDI drive.  Running Spinrite under DOS I can lock out
all of the bad/questionable sectors.  I've also been able to write a
disktab entry which is accepted by disklabel/newfs.  Is there some standard
method of writing data to a partition block by block and then reading it
back to look for the really awful problems?  The Adaptec drivers will
output the block number when there is a disk error, but the WD drivers
on the dist.fs disk will only indicate that there is an error.

I can use the information from Spinrite to input to bad144, but that will
lose 140MB as DOS can't handle the real drive parameters (over 1024 cylinders).

Doing something like "cat /dev/wd0a > /dev/null" does not seem to find the
problem blocks, although they show up quickly when trying to extract files.

-- 

Mike Squires (mikes@iuvax.cs.indiana.edu)     812 855 3974 (w) 812 333 6564 (h)
mikes@iuvax.cs.indiana.edu          546 N Park Ridge Rd., Bloomington, IN 47408
Newsgroups: comp.unix.bsd
From: shipley@merde.tfs.com (Pete Shipley)
Subject: Re: ref.tfs.com frequently unrecognized by DNS
Organization: Processed People for a Processed America
	<CGD.92Nov22190604@eden.CS.Berkeley.EDU>
Date: Mon, 23 Nov 1992 09:24:26 GMT


In article <CGD.92Nov22190604@eden.CS.Berkeley.EDU> cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes:
>   UCB is a secondary for TFS, and doesn't have the correct info.

I *just* increment the serial (now set to 901205) and SIGHUP'ed named
and the named does have the right infomation it is that the secondary servers
   NS.CC.Berkeley.EDU           128.32.206.12, 128.32.206.9
   JADE.Berkeley.EDU            128.32.136.9
do not have the new info.  I will call berkeley and  see if I can get
them to manualy force the update. There is nothing I can do
from here to fix the problem.

--
---------------
Pete Shipley:
email: shipley@berkeley.edu             Flames:  cimarron@postgres.berkeley.edu
Spelling corections: /dev/null          Quote: "Anger is an energy"
Newsgroups: comp.unix.bsd
From: ljg@space.physics.uiowa.edu (Larry Granroth)
Subject: [386BSD] XFree86/ATI Ultra Pro/Gateway2000 1572FS
Summary: Want Xconfig info
Organization: The University of Iowa, Department of Physics and Astronomy
X-Newsreader: TIN [version 1.1 PL6]
Date: Mon, 16 Nov 1992 20:48:41 GMT

I'm trying to install XFree86 on a Gateway 2000 4DX2-66V with an ATI
Ultra Pro and 1572FS monitor.  Using the distribution from agate, I
have it working at 640x480, but would either like better clock information
for higher resolutions (and refresh rates around 70Hz) or, better yet,
I'd like to get my hands on an X386 with support for the Ultra Pro or
8514/a.  Amancio Hasty has an (alpha test?) XBSD8514 up on his ftp
server, but it doesn't like my Xconfig.

If you have X running on similar hardware at 1024x768 (1024x1024 virtual)
at refresh rates around 70Hz (under 386BSD), please send me a copy of your
Xconfig.  If I get anything useful, I'll post a summary.

Thanks in advance.

larry-granroth@uiowa.edu
From: deraadt@newt.cuc.ab.ca (Theo de Raadt)
Newsgroups: comp.unix.bsd
Subject: 4.4/4.3Reno style SIOCGIFCONF
Date: 18 Nov 92 11:53:05 GMT
Organization: little lizard city

I don't understand fully what is going on with SIOCGIFCONF, at least as
it is implimented under 386BSD. I suspect this is the way it is implimented
in 4.4. The calls support sockaddr's with sa_len fields.

I finally figured out how it works. It differs quite a bit from the old
system. I can understand that this is to support multiple address families
and interface addresses on one interface. But, what is the AF_LINK entry
for?
 <tdr.
--

This space not left unintentionally unblank.		deraadt@newt.cuc.ab.ca
Xref: sparky comp.unix.bsd:9002 alt.sources:2538
From: paulp@uts.amdahl.com (Paul Popelka)
Newsgroups: comp.unix.bsd,alt.sources
Subject: [386bsd] mountable DOS filesystem code, Part 0/5
Date: 17 Nov 92 17:24:24 GMT
Followup-To: comp.unix.bsd
Organization: Amdahl Corporation, Sunnyvale CA


This is version 0.0 of the code to allow mountable DOS filesystems
under 386bsd 0.1.  It is refered to as pcfs from now on.  No, this is
not related to sun's pcfs, although they essentially do the same
thing.

This package has been installed on a 386bsd 0.1 system that has NOT
had the patchkit installed.  But, pcfs only changes a few files in
the base system so if pcfs changes collide with the patchkit they will
be small and localized.

Unshar each of the following 4 shar files.  They create files in
/sys/pcfs and /usr/src/sbin/mount_pcfs.  They do not overwrite any
existing files.  Once you have them unshared read the /sys/pcfs/INSTALL
file to find out how to install it and mount pc filesystems.  Then look
at the /sys/pcfs/pcfs.8 file for a list of the filesystem's quirks.

If you have problems send me some email and I'll see what I can do.
If you add things please send me the mods and I will try to incorporate
them for the next release.

Have fun,
Paul
paulp@sde.uts.amdahl.com
From: augustss@cs.chalmers.se (Lennart Augustsson)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD or LINUX?
Keywords: n
Date: 17 Nov 92 04:54:43 GMT
Organization: Chalmers University of Technology

In article <1992Nov4.131541.15661@prism.poly.edu> kapela@prism.poly.edu (Theodore S. Kapela) writes:
>Yes.  I had the problem with the fsck also.  It looks like fsck exits
>before the system is rebooted (after fsck modifies the root fs).  This
>allows the rc scripts to continue, and a sync ends up being done. This flushes
>the bad buffers back to disk, writing over the fixes made by fsck (using the
>raw partition).  I haven't really had a chance to check this out yet.
Add the line
	trap : 15
at the start of /etc/rc to fix the problem.  reboot send SIGTERM to all
processes and it is not ignored by default by the shell.  (One one the 58
patches caused this behaviour.)

-- 

	-- Lennart Augustsson
[This signature is intentionally left blank.]
From: forsyth@minster.york.ac.uk
Newsgroups: comp.unix.bsd
Subject: multibyte character representations and Unicode
Date: 17 Nov 92 09:50:36 GMT
Organization: Department of Computer Science, University of York, England

Terry Weber suggests that half one's disc space will vanish
on adopting Unicode.  Not so: I draw your attention to Plan 9,
which uses Unicode very successfully.  See the Plan 9 documentation
on research.att.com (dist/plan9doc, I think).

Basically, there is a multibyte encoding for Unicode that works well.
Inside relatively FEW programs the multibyte encoding is converted
to an integer representation (the type `Rune') to simplify manipulation.
For instance, the text displayed in a text frame by sam or the window
manager is kept as Runes, but ONLY the text displayed.  Any hidden
text -- and text in disc files -- is kept in the multibyte encoding.

Some care is required in specifying the multibyte encoding.
It seems that Plan 9 originally followed the encoding specified in
the Unicode standard, but it has some messy consequences in practice:
not least that the 2nd and 3rd bytes can appear to be valid
ASCII.  (Why anyone would design an encoding that does this is beyond
me, since the problems are fairly obvious, but that's what Unicode did.)
Eventually Plan 9 switched to a new encoding -- which apparently has now been
proposed for use in ISO 10646 -- that lacks all the unfortunate features.
The second and third bytes of the encoding do not look like ASCII characters.
(All bytes of an encoded character have the 0x80 bit set.)
The consequence is that even fewer programs are affected:
most pass Unicode encodings straight through.

In particular, the `normal' file system names can hold Unicode
characters without fuss.  There is certainly no need to switch to 16-bit
representations for them, with all that that entails.

Actually, on Plan 9 you cannot even run the window manager without using
Unicode: it's name is `eight and a half' (ie, 8 followed by a 1/2 symbol!),
entered as `8 ALT 1 2' (on my keyboard, anyhow).

You can find much of the Plan 9 Rune support in
the source for Pike's editor `sam', also on research.att.com
(dist/sam, i think).
(You also get a very decent editor, a library that gives you a sane
interface to X11, and a library for managing text on a bitmap display.)

Obviously programs can store Runes in disc files if that's really what
they need, or if their authors work for disc manufacturers, but it
isn't necessary.
Newsgroups: comp.unix.bsd