HDTenEightyP/NetNews huggingface dataset:
From: adam@micromuse.co.uk (Adam Kerrison)
Newsgroups: comp.unix.bsd
Subject: XView 3.0 for XFree86
Date: 9 Oct 92 09:13:09 GMT
Reply-To: adam@micromuse.co.uk
Organization: MicroMuse Ltd, London, Uk

Hi,

I have recently got thr source for XView 3.0 onto my BSD system and I am
about to start compiling it ... but a thought occured to me - has this been
done before ?? Is there a ready patched distribution out there (as I dont 
think it will compile first time :-) ???

Is they a ready compiled version available - as I also think that my little
386 chip is going to have its work cut out trying to compile it.

I anyone knows, can you let me know ??? If there isn't anyone think of any
potential problems (shared libs and paths are two possiblilities)

Ad (thanks) vance

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 
===========================================================================
From: chr@bio128.uni-bielefeld.de (Christian Bartling)
Newsgroups: comp.unix.bsd
Subject: BSD boot problems
Keywords: BSD, boot
Date: 14 Oct 92 07:25:48 GMT
Organization: Universitaet Bielefeld

I have installed BSD 0.1 on my computer and got the same boot problems,  
which were mentioned in this group before. I tried to solve the problem by  
installing the recommended patch, but it does not work.

Could the installation of a boot manager be a solution of this problems,  
or would this be a useless trial??

---
Christian Bartling
chr@bio128.uni-bielefeld.de 
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: .xinitrc&window manager for XFree86
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Tue, 13 Oct 92 19:08:25 GMT

In article Bqo@pix.com, stripes@pix.com (Josh Osborne) writes:
>In article <1992Oct13.113607.15615@ntuix.ntu.ac.sg> eoahmad@ntuix.ntu.ac.sg (Othman Ahmad) writes:
>[...]
>>Any other window managers?
>
>tvtwm, and gwm are the only (free) ones of note...

Ahem... there are also the OPEN LOOK window manager (olwm) and its virtual
equivalent olvwm.  olwm is included in the binary distribution of XView for
386bsd at nova.cc.perdue.edu.

	Chris Flatters
	cflatter@nrao.edu
Newsgroups: comp.unix.bsd
From: chrisc@ramrod.lmt.mn.org (Chris Cox)
Subject: patched dist.fs or /386bsd available?
Organization: LaserMaster Technologies, Minneapolis, MN  USA
Date: Tue, 6 Oct 1992 16:54:16 GMT

Does anyone have either a complete dist.fs(.Z) or just the /386bsd kernel 
binary available somewhere which has all of Terry's patchkit installed 
within it?

Chris

   Chris Cox  W0/G4JEC                               chrisc@ramrod.lmt.mn.org
   LaserMaster Technologies                          Tel: (612) 944-6069
   7156 Shady Oak Road                               Fax: (612) 944-5544
   Eden Prairie, MN  55344

           ----- For mail of a more social nature, please use -----

     chrisc@moron.vware.mn.org  -or- chrisc@biggus.g4jec.tcman.ampr.org
From: tholo@amanda.bbb.no (Thorsten Lockert)
Newsgroups: comp.unix.bsd
Subject: GCC 2.2.2 with 386BSD?
Date: 9 Oct 1992 17:07:40 +0100
Organization: Bergen By Byte A/S
NNTP-Posting-Host: amanda.bbb.no
Summary: Using GCC 2.2.2 with 386BSD possible?
Keywords: gcc 386bsd

Is it possible to use GCC 2.2.2 with 386BSD 0.1?  Will the kernel etc.
compile cleanly with this setup?  If not, are there patches available to
make this possible?

Thorsten
-- 
Thorsten Lockert       |  postmaster@bbb.no  |
Ibsensgate 122         |  hostmaster@bbb.no  |  Universe, n.:
N-5037 Solheimsviken   |  tholo@bbb.no       |          The problem.
Norway                 |                     |
Newsgroups: comp.unix.bsd
From: sastdr@torpid.unx.sas.com (Thomas David Rivers)
Subject: Re: Corrupted directory
Date: Fri, 16 Oct 1992 18:17:27 GMT
Organization: SAS Institute Inc.

In article <1992Oct16.033843.9805@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>In article <5232.9210151353@thor.cf.ac.uk> spedpr@thor.cf.ac.uk (Paul Richards) writes:
>>In article <Bw4Fv7.M4L@unx.sas.com> sastdr@torpid.unx.sas.com (Thomas David Rivers) writes:
>>|
>>|Regarding this infinite reboot cycle; I recently applied the entire

	A lot of stuff deleted... (about how I noticed the infinite
 fsck/reboot problem on two disks at home after I applied the patchkit)

>I -think- the offending patch is patch00038, which updates the error
>reporting mechanism for bad sector reporting for read errors being reported
>to user programs (with this patch in place, trying to install the bin01
>distribution from files located on a bad sector actually fails where you
>would want it to, rather than in the decompression some time later).
>
>Backing out this patch does not require deinstallation of other patches.  It
>should be noted that the correct fix is to adjust the fsck code (or to return
>the expected value to the fsck code) so that the checking is not aborted by
>the error.
>
>Generally, this error will not occur on disks installed with a dist.fs with
>the patches applied; instead, it will occur on disks installed on top of
>bad sectors (without the error being caught) and to which the patches are
>later applied.
>
>I don't know how the author of the patch (Frank Maclachlan) handles this on
>his drives, but I suspect that he does one of the two approaches above.
>

  Well, one of my machines is a SCSI, which should have no bad sectors reported
by the controller  and the other is an IDE  which, according to the 
INSTALLATION document should have no bad sectors either - although I'm
skeptical/confused about that one.

  So, while patch0038 could be the problem; I don't think it's because
fsck is actually running into read errors.  Could it be that the mechanism
is incorrectly reporting such errors?

	- Dave Rivers -
	(rivers@ponds.uucp (home))
	(sastdr@unx.sas.com (work))
-- 
UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express
Newsgroups: comp.unix.bsd,comp.unix.ultrix,comp.unix.solaris
From: jamesd@lna.oz.au (James D)
Subject: Unix with real time performance ?
Organization: Leeds & Northrup Australia, Sydney
Date: Fri, 9 Oct 1992 02:48:16 GMT

	I'm looking (very hard) for possible mechanisms of process
communication that could satisfy some fairly tight real-time constraints.

We are considering porting our Versados products to Unix or to some such 
Unix variant. We currently have Ultrix-32 and SunOS 4.1, and I have some
timing results for them. We will also have Solaris and OSF soon. Many 
OS vendors claim their product will have "increased real-time support"
in their next release, but we need to know what is currently available 
to make desisions now. 

BSD 4.2 sockets and System V messages are all we have tested, so we would
like to know if anyone else has done any studies on "real-time" Unix.

						Thanks -- James Duff

-- My views may reflect the views of my employer,
-- but only while he's listening :-)
Newsgroups: comp.unix.bsd
From: mark@labtam.labtam.oz.au (Mark Treacy)
Subject: Re: getting net config with SIOCGIFCONF ioctl call
Organization: Labtam Australia Pty. Ltd., Melbourne, Australia
Date: Thu, 8 Oct 1992 11:20:44 GMT
Keywords: ioctl ifconf ifreq

linkt@GroupW.cns.vt.edu (Tim Link) writes:
>I'm working on a program that needs to determine the network
>configuration under 386BSD.  I'm using the SIOCGIFCONF IOCTL function
>which *I THINK* should return to me an array of ifreq structures which
>have the name of the interface and it's ip address.  This ain't what I'm
>gettin'.  I've poked and prodded and looked at if.c to try to figure out
>what's going on, but I can't see where the problem is.  Just as a test I
>compiled the program on an Ultrix machine and the results were close to
>what I expected, but still not exact.  Can anybody look at this and tell
>me if I'm completely wrong in what I'm doing of if SIOCGIFCONF isn't
>returning what it should be???

I haven't seen any replies to this, so either you're still in the dark
or our news feed is dropping articles.

In the 4.3bsd-reno and net2 release the ifreq's returned by SIOCGIFCONF
are not fixed length.  See ifconf() in usr/src/sys/net/if.c .

You need something similar to the code in inet.c in tcpdump.
i.e. (fragment taken from tcpdump)

	ifc.ifc_len = sizeof ibuf;
	ifc.ifc_buf = (caddr_t)ibuf;

	if (ioctl(fd, SIOCGIFCONF, (char *)&ifc) < 0 ||
	    ifc.ifc_len < sizeof(struct ifreq)) {
		perror("tcpdump: SIOCGIFCONF: ");
		exit(1);
	}
	...

	ifrp = ibuf;
	ifend = (struct ifreq *)((char *)ibuf + ifc.ifc_len);
	
	while (ifrp < ifend) {
		....
#if BSD >= 199006
		n = ifrp->ifr_addr.sa_len + sizeof(ifrp->ifr_name);
		if (n < sizeof(*ifrp))
			++ifrp;
		else
			ifrp = (struct ifreq *)((char *)ifrp + n);
#else
		++ifrp;
#endif
	}
	...


You're probably only interested in AF_INET addresses, so skip
over the ones that aren't.  if_attach() creates an AF_LINK
address for an interface which isn't terribly usefull
since it only gets filled in with the interface name.
The function in libc to handle AF_LINK addresses wouldn't
display the address correctly anyway.

>As always, any and all help appreciated.  
>  Tim

 - Mark.
Newsgroups: comp.unix.bsd
From: hitchens@untadh.enet.dec.com (Francis J. Hitchens)
Subject: Help logitech busmouse. missing device.h
Reply-To: hitchens@untadh.enet.dec.com (Francis J. Hitchens)
Organization: Digital Equipment Corporation
Date: Wed, 7 Oct 1992 13:24:28 GMT

Hi,

I have found the busmouse.v3 kit patch and  tried to add it to my kernel.

The header file device.h seems to be missing. Can any body point me to
it please.

Do you know what its like having an Xserver without a mouse !

regards Francis J. Hitchens.
From: rich@Rice.edu (Richard Murphey)
Newsgroups: comp.unix.bsd
Subject: Re: Floating point ops don't work
Date: 16 Oct 92 16:56:07 GMT
Article-I.D.: kappa.RICH.92Oct16105607
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University

In article <1992Oct16.144328.1391@cs.brown.edu> ac@cs.brown.edu (Arthur!! Chai) writes:
   I have the patched 1.0.3 kernel and XFree86 mono working. However, I just
   realized that floating point ops no longer work while trying to get
   ghostscript to work.  Hmmm ... is it because the kernel supplied with
   the X distribution is for a machine with a 387 installed ? If so, does 
   anyone have one without that ? Or am I just confused ? I have a plain 386SX-25
   without a 387 installed.  I would like to be able to have both X and floating
   point ops ;^) Any pointers would be appreciated.
   Arthur!!

The 1.0.3 kernel binary is the same as the GENERICISA except for the
XFree86 related patches.  So, it should have the same floating point
emulation codes as the kernel in the dist.fs floppy.  Rich
Newsgroups: comp.unix.bsd
From: g89s9112@hippo.ru.ac.za (Dirk Sturzebecher)
Subject: UUCP and 386BSD, HELP !!
Organization: Rhodes University, Grahamstown, South Africa
Distribution: global
Date: Sat, 10 Oct 1992 17:27:21 GMT

Hi all,
I am still struggeling with UUCP, maybe someone out there knows the
answer. Here it goes,

I am running 386bsd on a 386 and I got a modem on COM2. the modem can do
2400. I have tried to change the files in "/etc/uucp" to work for my
system, but not with much success (I think). Now if I do the following:

uucico
uucp host\!file /tmp
uustat -a

I will see file being in the spool (or I at least think that's it).
Some entry with host,file,filesize,date,time.
Now nothing happens. Should the system not try to send the file ?

uucico -Shost

does not change the situation ?


Is anything of the above incorrect ? Is there anything I do not know and
need to know to make it work ? It looks like the computer never actually
speaks to the modem ! Is there anyone out there who has a system like
this working ? If so could I maybe get a copy of his setup files (after
the removal of the sensitve info) ?

Cheers, Dirk

-- 
-----------------------------------------------------------------------
Dirk Sturzebecher				g89s9112@alpha.ru.ac.za
Rhodes University Grahamstown			South Africa
From: wkt@csadfa.cs.adfa.oz.au (Warren Toomey)
Newsgroups: comp.unix.bsd
Subject: Isolan driver fixed yet? [386BSD]
Date: 16 Oct 92 01:34:53 GMT
Organization: Australian Defence Force Academy, Canberra, Australia

Has the Isolan driver for 386bsd 0.1 been fixed yet? If so, where can I
get the patches from? I've check thru all the old postings and have seen
no mention of a new Isolan driver.

Thanks in advance,

	Warren Toomey wkt@csadfa.cs.adfa.oz.au
Newsgroups: comp.unix.bsd
From: scotty@gagetalker.com (Scott Turner)
Subject: Re: Question on Diamond Clock Synthesizer
Organization: L5 Computing
Date: Thu, 15 Oct 1992 01:03:34 GMT

In article <1992Oct13.175214.19534@fcom.cc.utah.edu> terry@cs.weber.edu (A  
Wizard of Earth C) writes:
|> In article <1992Oct13.050754.4113@sinkhole.unf.edu> shite@sinkhole.unf.edu  
(Stephen Hite) writes:
|> >
|> >   I read a message that David Wexelblat posted recommending
|> >for people to not use the "Batman" Diamond clock code (David got this 
|> >advice from Thomas Roell).  I believe the reason was that it could
|> >cause some kind of physical damage to either your monitor or card
|> >(forgot which).  I'll take Thomas's word for it...
|> 
|> Wrong reason.  The reason was legal.  There would be no more danger in a
|> piece of code dealing with the video card than any other code dealing with
|> a video card.  The warnings you remember were from another post for some
|> alpha VGA code (not the "Batman" code).  Unfortunately, no one who has
|> used the "Batman" code can sy whether or not there was a problem, since
|> doing so could be admitting a violation of the trade secrets act if Diamond
|> wanted to prosecute.
Forget these Diamond turkey's. The STB Evolution card uses the Cirrus Logic
CL-GD5422 chip which has onboard clock generation and is FULLY documented
with no trade secret restrictions by Cirrus Logic.

As for reverse engineering the Diamond I thought they had one of those
annoying "by using this product you agree to the following..." thingies
that basically says you won't reverse engineer the card because it has
trade secrets inside it and that I agree to protect it from all un-american
influences like Clinton and Gore. :)

Scotty
From: dittman@skitzo.dseg.ti.com (Eric Dittman)
Newsgroups: comp.unix.bsd
Subject: Re: Speedstar 24X with XFree86 in 640x480x256 mode?
Date: 15 Oct 92 06:35:24 GMT
Article-I.D.: skitzo.1992Oct15.013524.727
Organization: Texas Instruments Component Test Facility

In article <1992Oct14.021655.721@skitzo.dseg.ti.com>, dittman@skitzo.dseg.ti.com (Eric Dittman) writes:
> Has anyone been able to get XFree86 to work with the Diamond
> Speedstar 24X in ANY mode?  I've been following the discussion
> on this video card, and I know there's no config available for
> the higher resolution modes.  I thought I read a post earlier
> that said 640x480x256 would work, but it doesn't work for me.

Well, I have 640x480x256 working.  The problem was my mouse was
set to /dev/tty0 instead of /dev/com1.  I changed this, changed
the mouse type from logitech to microsoft (it's a Dexxa+ mouse
and is supposed to act like a Logitech, but it didn't work right),
and removed all modes except "640x480".  It works, but of course
I'd rather have 1024x769 available.
-- 
Eric Dittman                  Texas Instruments - Component Test Facility
dittman@skitzo.dseg.ti.com    (214) 578-3575
Disclaimer:  Not even my opinions.  I found them by the side of the road.
From: felawka@sitka.triumf.ca (Larry Felawka)
Newsgroups: comp.unix.bsd
Subject: Re: Corrupted directory
Date: 14 Oct 1992 22:27:36 GMT
Organization: TRIUMF, Vancouver BC
Distribution: world
NNTP-Posting-Host: sitka.triumf.ca

In article <Bw4Fv7.M4L@unx.sas.com>, sastdr@torpid.unx.sas.com (Thomas David Rivers) writes:
|> 
|> Regarding this infinite reboot cycle; I recently applied the entire
|> beta patchkit (from a new, clean, installation of 386bsd 0.1) and
|> began getting this problem.
|> 
|> I.e. If I have to shut down for some reason, or the power goes out; the
|>      machine reboots.  Root gets fsck'd and repaired; and the
|>      machine reboots again.  Then there is another problem with the
|>      fsck of root, and the machine reboots, etc... encountering the
|>      same problem over and over.
|> 
|>  I've now seen this happen on two machines to which I applied the beta
|>  patchkit.  It did *not* happen on these machines using the kernel I 
|>  had patched together from news articles.   This means (at least to me)
|>  there is some patch applied by the patchkit which I had not otherwise
|>  applied in my kernel, that is causing the problem.
|> 
|>  I've seen it on a SCSI disk and IDE disk, so I don't think it's in the
|>  driver... could it be some of the changes to init.c?
|> 

Only indirectly ... the problem comes when you do the "make install" for
"init".  It appears that at this point the file system has become corrupted
and if you reboot you get the behaviour you have described.  One can recover
by inserting the fixit disk, rebooting from the floppy and doing
"fsck /dev/rwd0a".  The clean way to do the patch installation for init (and
other programs that are running while you are patching them) is probably to
do the "make", shut down and do the installation using the fixit disk.

-- 
Larry Felawka
Newsgroups: comp.unix.bsd,comp.windows.x
From: rivers@ponds.uucp (Thomas David Rivers)
Subject: XFree86 dumping core on 386BSD...
Summary: ico crashes server
Date: Tue, 13 Oct 1992 23:23:23 GMT

Well, I finally got some time to get XFree86 going on one of my 386BSD
boxes.

After what seems to be the standard frustration with the font path, and
mice, etc... (I think the setup has improved, by the way, from the
old X11R4 version.) I was able to get things going.

The first thing I did was run ico; which crashed the server rather
quickly.   I have determined that running ico on another host; displaying
on mine seems to crash the server regularly; but running it locally can
get a crash as well.  I've run it with and without colors, faces, etc...
that doesn't seem to be a problem.

I don't think it would be wise to ship someone a core file; it's rather
large:

-rw-r--r--    1 root      1093632 Oct 13 19:11 core.X386

I'm running this on a 33mhz 386DX, with a Cyrix '387, 12 meg of main
memory, and an Adaptec 1542b and the released SCSI driver.  I've applied
all the patches in Terry's beta patch kit; and am using Chris D.'s
serial driver.  I'm using the latest XFree86 found in ports-0.1 on 
agate.berkley.edu.


I would give someone a traceback, etc... but the server was stripped...
I'm not suggesting putting the debugging information in there; it's much
too large to download that way, it's just a shame.

Also; I noticed that the PEX*.h files were missing from 
/usr/X386/include/extensions.


I've noticed no other problems, so as long as I don't run ico - it's
great!

	- Dave Rivers -
	(rivers@ponds.uucp)
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: nfs:  'mountd' hangs, must ^c...
Organization: Weber State University  (Ogden, UT)
Date: Thu, 8 Oct 92 02:33:31 GMT

In article <1992Oct7.231718.22241@Arco.COM> Matt Mannhardt <lasmtm@Arco.COM> writes:
[ ... mountd hangs ... ]

Install the patches to NFS and recompile mountd and rebuild the kernel.

There was a bug where if you exported "/" and "/usr" and they were on the
same disk, mountd hung.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
From: rcisnet2!color_galaxy_mw!eric_levinson
Newsgroups: comp.unix.bsd
Subject: network config
Keywords: (none)
Date: Fri, 9 Oct 92 02:20:50 PST
Summary: (none)
Organization: The Rainbow Connection Information Service

I seem to have my network configuration files set up wrong.  When I boot
386BSD, I see the following:
 
writing to routing socket: File exists
add host pepper: gateway localhost: File exists

and then the usual rest of the stuff.
 
My question is, which files do I have to modify and how do I modify them to
reflect my host 'pepper'?
 
Any help would be greatly appreciated.  Please respond vioia private e-mail if
possible:  moon.nbn.com!rcisnet2!root
 
Thanks
 
Eric
Newsgroups: comp.unix.bsd
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: Re: DOS and 386BSD
Organization: Nanyang Technological University - Singapore
X-Newsreader: TIN [version 1.1 PL6]
Date: Tue, 13 Oct 1992 02:19:42 GMT

 (K390670@ALIJKU11.BITNET) wrote:
: My machine is a 486-50 with 212MB Conner CP3204F (IDE) and 543MB Conner

Probably the same IDE as mine.

: CP3540 (SCSI-2), the latter of which is connected to an Adaptec 1542B.
: 
: 
: 
: 
: 
: I have painstakingly followed Terry Lambert's advice about setting the
: IDE drive to its "native" parameters and about putting 386BSD (ptntype A5)
: *first* on the disk, DOS second.
I do not need to do this. Just install DOS first and leave some for 386bsd
at the last partition, then use nu to lavel the 386bsd partition a5. Linux
archive has pdisk(?) or something, which may be used in lie of nu.
	If there is a crash, use ndd to restore the boot sector.

: 

--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet

Newsgroups: comp.unix.bsd
From: song@iastate.edu (Chang-Hyeon Song)
Subject: Help!  Installation.
Organization: Iowa State University, Ames, IA
Date: Fri, 9 Oct 1992 05:46:36 GMT

Hello, can somebosy help me with installing 386BSD?  I have following problems.

1. bin01.52 file:  The other file seems OK, but when I do "loadfd" ,this gives me an error on I/O.  I have downloaded it again, but filed for the reason.

2. etc01 unpacking.  After packing etc01.59, "too many file opened" error 
occurs from etc01.60, 61, .... .

Thanks.

Xref: sparky comp.unix.bsd:7467 comp.os.linux:13467
From: torvalds@klaava.Helsinki.FI (Linus Torvalds)
Newsgroups: comp.unix.bsd,comp.os.linux
Subject: Re: Binary compatibility question... [Summary]
Date: 15 Oct 92 09:22:05 GMT
Organization: University of Helsinki

In article <1992Oct14.193014.537@ucsu.Colorado.EDU> ngoh@rintintin.Colorado.EDU (NGO HIEN D) writes:
>
>From: Cameron Spitzer 764-6339 <camerons@nad.3com.com>
>
>There *is* an "Application Binary Interface" for System V on the [34]86.
>I was real disappointed to find out Linux doesn't use it.  Don't know why he 
>doesn't either.

The simple reason linux isn't even close the the intel ABI is that I
simply hadn't got a clue about how it looked - intel never contacted me
about it :-) and I certainly didn't want to go to any unnecessary
trouble over it. 

As it turns out, the linux-ss project might be helped by linux following
the intel ABI or at least being a bit closer (ie lcall 7,$0 for system
calls), so I might put in some hooks for it - I'll take a look at the
xenix emulator when I get some time. 

Making linux run most normal i386 ABI binaries would probably be pretty
simple: you'd just need a simple wrapper around the system calls
mechanism.  To get more complete support, the signal handler stack frame
would have to be changed etc, but very few programs care about that
anyway. 

		Linus