HDTenEightyP/NetNews huggingface dataset:
From: bde@runx.oz.au (Bruce Evans)
Subject: Re: IDE faster than SCSI-2
Organization: RUNX Un*x Timeshare.  Sydney, Australia.
Date: Sun, 8 Nov 92 07:29:24 GMT

In article <1df7dqINN37o@tartarus.uwa.edu.au> oreillym@tartarus.uwa.edu.au (Michael O'Reilly) writes:
>Othman Ahmad (eoahmad@ntuix.ntu.ac.sg) wrote:
>: [...]
>:  JUlian's machine 
>:  is a 50MHz EISA 486 with a 1.3GB drive attached via a Bustek 742a SCSI2
>:  adapter. It has 16MB of ram. Part of the disk (about 200MB is taken up 
>:  by mach2.6 and is unavailable to 386bsd.
>: 
>: I checked the load on this machine, it is very light. There is only another
>: user apart from I.
>: 
>: iozone 1
>: 
>: Writing the 1 Megabyte file, 'iozone.tmp'...1.766667 seconds
>              ^
>	      ^ This is useless. It tells no-one anything. A one meg
>file should fit entirely in the cache. So unless BSD is braindead, and
>doesn't cache (which I doubt), then you have just measured the cache
>speed. On my 486/33, 8 meg ram, a 1 meg files get 10 megs per second. 

1 MB in 1.76 seconds is way below the cache speed.  In fact it is quite
likely to be a good estimate for actual disk speed.

Disk caching in 386BSD-0.1 is quite broken.  First, only 10% of memory is
used for the disk+swap cache.  This is smaller than I like.  (Comments in
the code say that only 5% of memory after the first 2MB are allocated to
the cache, but due to bugs, 10% of all memory is allocated.  A fix has
been posted.)  Second, only half of the 10% is used for the disk cache.
(Some (usually all) of the other half is reserved for buffers for swapping.)
Third, memory for each buffer is allocated twice, so only 2.5% of memory is
used for the disk cache!  A fix is in Terry's patch kit.  Fourth, bugs
in the caching algorithm caused the cache to thrash.  A fix is in the patch
kit.  Fifth, another kernel limit requires limiting the initial 10%
allocation to 256 buffers to avoid panics (the limit is in the patch kit).
(I actually use a limit of 503 to get 251 disk buffers and 252 swap buffers.
This is fairly safe because the system almost never swaps.)

>I don't know exactly what you measured, but it sure ain't disk speed.

It probably was disk speed!  I don't know exactly what the cache size
is on Julian's system.  If the system has all the standard patches, it
will have 128 disk buffers for a total cache size of about 512K if the
file system has a block size of 4K.  That is consistent with the
benchmark.
-- 
Bruce Evans  (bde@runx.oz.au)
Newsgroups: comp.unix.bsd
From: bad@flatlin.ka.sub.org (Christoph Badura)
Subject: Re: BSD on SUN-3? 
Organization: Guru Systems/Funware Department
Date: Fri, 13 Nov 1992 17:25:39 GMT

In <1992Nov12.104709.11414@csqx.cs.rhbnc.ac.uk> markd@csqx.cs.rhbnc.ac.uk (Mark Damerell) writes:
>Please does anybody know if there are any plans afoot to adapt
>the BSD system to either SUN-3 or HP-9000/800 series machines?

A port for the HP machines has already been done. CSRG works almost
exclusively on HP-86k machines these days. For the Sun-3 a separate
port would have to be done, although one could use large parts of the
HP and upcoming SPARC port.

>I would like to be able to read some of the man pages, but when
>I try to run them through nroff, I get garbage. Please, what 
>would be the way to format these for teletype? or V100? or 
>X terminal?

nroff -mdoc ?

>My colleagues are much concerned
>about the security risk posed by the use of NFS. Would it seem 
>reasonable to use the BSD version of nfsd on a machine running
>sun-OS 3? The idea is that BSD nfsd can be told to accept calls 
>only from specified I-net addresses, but can it interact with
>the Sun kernel? I know that any competent hacker can forge an
>address, but it would seem difficult to do this if you are the
>wrong side of a router, and anyway, the BSD  nfsd  ought to be
>more secure than the existing  nfsd  which (I believe) accepts
>calls from anywhere. 

I haven't looked at the nfsd sources. But, depending on how much work
is done in the user process and how much in the kernel process this
may be easier to accomplish or not.

>We would really like to be able to use the BSD code for secure 
>rpc  but this would seem to require a composite kernel containing
>a mixture of BSD code for rpc and SUN-OS code for everything else.
>Is such a beast possible? Please has anybody any suggestions how 
>one might attempt it?

This may actually be easier, since you have complete control over the
NFS and RPC subsystems. Basically one has to port the BSD sources to
the Sun kernel.

-- 
				Christoph Badura  ---  bad@flatlin.ka.sub.org

AIX is a better... is a better...  is a better... OpenSystem.
					IBM Rep at GUUG Symposium '92
Newsgroups: comp.unix.bsd
From: hildi@opal.cs.tu-berlin.de (Thomas Hildmann)
Subject: Have to start X twice
Organization: Techn. University of Berlin, Germany
Date: Fri, 6 Nov 1992 10:10:04 GMT

Shure my X is working. But I have to exit and start it again before I can
use my keyboard. What goes wrong?

Second problem. The new rs232 driver lets the mouse die. I always have
to strike a key when I moved the mouse. Working is impossible.
From: swaliff@afterlife.ncsc.mil (Steve Aliff)
Newsgroups: comp.unix.bsd
Subject: 2 drive system, installing 386BSD on drive 2?
Summary: Is it possible to have MSDOS on one drive, 386BSD on another?
Keywords: 386BSD, boot, disk
Date: 8 Nov 92 01:52:56 GMT
Organization: The Great Beyond


I have two IDE drives on my system. Presently drive 0 is dedicated
to MSDOS and drive 1 to Linux. As I am experimenting with Linux at
the moment, I have a Linux boot floppy which sets things up to use
drive 1 (yes, there are other ways to do it, let's not get into that
now). I can boot MSDOS in the usual fashion.

I'd like to try 386BSD using a similar setup. Is this possible? If
so, how? When I boot from the "tiny" floppy, it reports finding
drive 0 (my MSDOS drive), but not drive 1 (my Linux drive).

[Is there a 386BSD FAQ? If so, where is it?]

[p.s. I like Linux a lot, but have the time and inclination to try
386bsd. Don't read anything into this that isn't there.]

tia,
-- 
Steve Aliff (swaliff@afterlife.ncsc.mil [144.51.1.1])
Newsgroups: comp.unix.bsd,comp.os.linux
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: IDE faster than SCSI-2
Organization: Nanyang Technological University - Singapore
X-Newsreader: TIN [version 1.1 PL6]
Date: Thu, 5 Nov 1992 08:07:16 GMT

I posted an iozone benchmark using my 386/25Mhz machine which shows that
it is slightly slower than a SCSI-2 hard-disk. Now with a 486/33, IDE is
definitely faster than a EISA SCSI-2 486/50MHZ  hard-disk.
	Iozone uses normal unix system calls for writing to disks, after all,
that is how we write C programs.
	I may try to run a more sophisticated file system tester called
bi? later on.


 JUlian's machine 
 is a 50MHz EISA 486 with a 1.3GB drive attached via a Bustek 742a SCSI2
 adapter. It has 16MB of ram. Part of the disk (about 200MB is taken up 
 by mach2.6 and is unavailable to 386bsd.

I checked the load on this machine, it is very light. There is only another
user apart from I.

iozone 1

Writing the 1 Megabyte file, 'iozone.tmp'...1.766667 seconds
Reading the file...1.983333 seconds

IOZONE performance measurements:
	593534 bytes/second for writing the file
	528694 bytes/second for reading the file

Running on 486/33 with 256Kbyte RAM cache, maxtor 200Mbyte IDE hard-disk,
8Mbyte main RAM.

	Whereas the IDE runs XFree86 and open look window manager.
I only use 1 megabyte for test file size.

  IOZONE performance measurements:
	873813 bytes/second for writing the file
	452623 bytes/second for reading the file

	Both machine uses 386bsd 0.1 heavily patched, so the timing measurements
are consistent with each other.


--
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: mark@student.business.uwo.ca (Mark Bramwell CS STAFF)
Subject: Re: Where do I get dist.fs for 3.5" drives?
Organization: University of Western Ontario
Date: Sat, 7 Nov 1992 06:44:53 GMT

dinn@ug.cs.dal.ca (Michael 'Moose' Dinn) writes:

ftp to agate.berkeley.edu   check out the pub/386bsd-0.1
directory.  Grab alot of files including rawrite.exe

It will take the  dist.fs file and make a bootable floppy 3.5 or 5.25
disk from it.
It only have 3.5 disks here.


> 
> 
> Anyone know where I can get this beastie?
> 
> --
>  Michael Dinn, CS Student  |  dinn@ug.cs.dal.ca, dinn@appliedmicro.ns.ca


mark@student.business.uwo.ca (Mark Bramwell CS STAFF)
Western Business School  --  London, Ontario
From: root@starbase.gun.de (Charlie Root)
Newsgroups: comp.unix.bsd
Subject: [386BSD] + X386-1.2E + CRYPT
Summary: 386BSD X11 CRYPT
Keywords: 386BSD X11 CRYPT
Date: 9 Nov 92 14:45:42 GMT
Organization: experiments in process engineering

Hi Netlers,

I have just one simple question:

where can I ftp a binary of "xdm" the X Display Manager

with incompiled BSD crypt.c ?

Any hints welcome.

Thankx in advance

Grusz,    Guido
Newsgroups: comp.unix.bsd,comp.os.minix,comp.os.linux
From: hallvard@immhp1.marina.unit.no (Hallvard Paulsen)
Subject: Re: Floppy overrun/underrun messages...what does it mean?
Reply-To: hallvard@immhp1.marina.unit.no (Hallvard Paulsen)
Organization: Division of Marine Engineering
Date: Fri, 13 Nov 92 06:45:00 GMT

In article <To25TB2w165w@dogear.spk.wa.us>, bobk@dogear.spk.wa.us (Bob Kirkpatrick) writes:
|> I see it all the time. All it means is that your floppy or your scsi is
|> fast or slow compared to the other. The error message should be more
|> like "I'm a floppy drive and your harddisk is so slow I'M waiting for it."
|> or "As harddisks go, I'm sooooo fast I do waitstates on copy from floppy."
|> 
|> Doesn't mean anything. (-:

	Well, I used to see it a lot to. And in the end it was the only
thing I saw. (Except for HD-reset or something like that.) I've now
ordered a new controller.

	Hallvard Paulsen
From: hlu@eecs.wsu.edu (H.J. Lu)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD or LINUX?
Date: 6 Nov 92 18:45:56 GMT
Article-I.D.: serval.1992Nov6.184556.11843
Organization: School of EECS, Washington State University

In article <1992Nov5.060658.639@ntuix.ntu.ac.sg>, eoahmad@ntuix.ntu.ac.sg (Othman Ahmad) writes:
|> Drew Eckhardt (drew@kinglear.cs.colorado.edu) wrote:
|> : 
|> : Linux +'s : 
|> : 
|> : Shared libraries.  This results in a significant disk space savings,
|> : especially in the case of 'X' applications that can shrink by 
|> : an order of magnitude when compiled with shared libraries.  
|> 
|> Let us compare sizes:
|> 

I have a simple X11 program which just prints out "Hello world!".
It takes about 300K with static libs. With shared libs, it only takes
9K. I can even make it less than 3K.

[...]

|> : 
|> : Many kernel structures, such as pty's, are dynamically allocated.  This
|> : increases the amount of pageable memory that is available.
|> 
|> How do we change its number? CAn we add pty indefinitely`?

You know the answer for `indefinitely'.
 
[...]

|> : 
|> : I'd say that if you want BSD, because it's BSD, or if you want 
|> : stable NFS NOW, and not in two weeks,  that it might be worthwhile.  
|> 
|> Have you forgotten that it has the VFS(?), which is the Posix complient file

VFS? Without it, how can Linux support Minix, Ext, MSDOS, Xenix, NFS ...?

|> system. Or has linux used it already? What it does is to have long file names,
|> faster throughput because of large block sizes(4K),without much fragmentation
|> becaue it can go down to 1K block size as well,or am I mistaken?
|> 
|> 	It also uses standard BSD library, which makes it easy to port
|> software written in BSD systems which is widely used in Academic circles.

I am responsible for the Linux C library. It is not that hard to port code
to Linux since the Linux C library is POSIX compliant with lots of SYSV,
BSD and GNU extentions. For most of PD stuff, you can chose POSIX, which
is the safest, BSD (I did it for compress.) or SYSV. I bet porting code
to Linux is easier than to 386bsd in general.

|> 	This is the other reason why I choose 386bsd over linux. However it is
|> not completely true because 4.3 BSD is slightly different from 4.2 BSD. Use
|> of GNU utilities make it slightly incompatible with full blown mainframe
|> BSD or those used in ultrix and Sun workstations.

You mean GNU utilities have lots of new switches? I just happen to like that.
They can do you want them to do.

|> 	The other reason is that linux is more for hackers. Lynne goes to
|> great lengths to make 386bsd installation easy for "idiots"/beginners.

That is true. Now the FSF is planning distribute Linux. We are trying to
make it idiot-proof. But noone can 100% guarantee it.

|> 
|> How about performance comparisons? I've posted the results of iozone 1 to
|> comp.unix.bsd .
|> 

I think that depends on the applications.


H.J.
From: wutcd@chemnitz.guug.de (Joerg Wunsch)
Subject: Re: Problems with mtools ! Please HELP
Organization: tu-chemnitz
Date: Sat, 7 Nov 1992 14:37:57 GMT

Hi all:

what you complain of ain't gotta problem of MTOOLS. It's the stupid
fd driver. For now, it will only handle HD drives, regardless of
your CMOS (except you'd disable the floppy:-(().
I've dealt with it in making some floppy formatter work, and i decided
to redesign the whole driver. Obviously, this would take some weeks.
The goals are: a format call, automatic format detection, change line
support, quite more reliable. (If you don't believe that the current
driver is unreliable: try operating on two floppies at the same time.
Don't do this with worthful data!)

	Tschuess
	J"org
--
J"org Wunsch, TCD GmbH Dresden, R"ahnitzgasse 18, D-O-8060 Dresden
                                                              \     ~.~. 
	joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de         \   ~  | ~ 
	voice: +49-351-5965 137                                 \    ===
Newsgroups: comp.unix.bsd
From: andrew@megadata.mega.oz.au (Andrew McRae)
Subject: Looking for details on WD8003 configuration bits
Organization: Megadata P/L, North Ryde, Sydney, Aust.
Date: Fri, 6 Nov 1992 06:54:05 GMT

Greetings,
I am looking for details about configuring the WD8003
Ethernet card, specifically enabling access to the boot ROM
socket on the card.

The we driver in 386bsd doesn't know about the ROM socket,
and I have looked at the packet driver for the WD8003 and that
also doesn't do anything with the ROM. When I run the setup/diagnose
program via DOS, I can soft-configure the ROM, or if I fix the
ROM address to 0xD8000/16K, the diagnose program recognises it. I have
fixed the RAM/IRQ to IRQ 3, RAM 0xD0000. One strange thing I have
found is that if I soft configure the board for 64Kb ROM space, and
power cycle the PC, it seems to forget the ROM configuration and
disable the ROM access.

When I put a test 16Kb ROM in the board that contains some easily
recognised pattern data (note this ROM will not have the
0xAA55 stuff that the BIOS recognises), and try to access the
ROM from the kernel, then the ROM doesn't seem to appear in
the address space. To check this, I can run:

 dd if=/dev/mem bs=4k | hexdump | more

And then search for d0000. I can then see the shared RAM area, and
see the net packets in the shared RAM and so forth. But the
area of memory starting at 0xD8000 is still all 0xFF (just like
the rest of the unused I/O memory space).

My thought is that there is some configuration bit that enables
access to the ROM space (just like it does with the RAM), but
there is nothing in any documentation I have found that indicates
how to do this, and the drivers I have looked at do not bother
accessing the ROM, so there are no details about the ROM setup.

Since you can soft-configure the ROM address and ROM size, there
must be some bits within the control I/O address of the card to
control the ROM access. Does anybody have some more complete
documentation about this card that I could use? Has anybody
successfully accessed the ROM on the card?

Thanks for any help.

Andrew McRae			inet:	andrew@megadata.mega.oz.au
Megadata Pty Ltd,		uucp:	..!uunet!megadata.mega.oz.au!andrew
North Ryde  2113		Phone:	+61 2 805 0899
NSW    AUSTRALIA		Fax:	+61 2 887 4847
Newsgroups: comp.unix.bsd
From: uwp@cs.tu-berlin.de (Udo Wolter)
Subject: 386BSD, XFree & SCSI
Organization: Technical University of Berlin, Germany
Date: Tue, 10 Nov 1992 12:59:06 GMT

Hi people !
There's something I forgot to ask in my last posting:
Where can I find the latest SCSI drivers ? My tape device can't use the mt
program...:-(
Another question: I tried to compile xv and it exits with an errormessage:

Virtual memory exhausted

Can anyone tell me what it is and what I can do ? I have a 486/33 clone with
8 MB ram on board. I got some hints but I just wanted more of them...

I also got an example of an XConfig file for XFree with a SIGMA LEGEND video
card so perhaps I can solve the problem how to get 800x600 mode. But can
anyone tell me, how to define the 1024x768 mode ? Please don't tell me I have
to use the xclk program. It works only for 640x480 mode...:-(

Thanx in advance,
		  Udo
-- 
Udo Wolter   
INTERNET:    uwp@cs.tu.berlin.de, wolter@db0tui11.cs.tu-berlin.de	
BITNET/EARN: WOLTER@DB0TUI11
Newsgroups: comp.unix.bsd
From: ggr@nareen.acci.com.au (Greg Rose)
Subject: Re: mktemp - Bus Error.
Organization: Australian Computing and Communications Institute
Date: Thu, 5 Nov 1992 06:49:59 GMT

In article <1992Nov3.174359.19262@Princeton.EDU> jsm@shade.Princeton.EDU (John Scott McCauley Jr.) writes:
>In article <KHERA.92Nov3111245@thneed.cs.duke.edu> khera@cs.duke.edu (Vivek Khera) writes:
>[on mktemp]
>>you don't need something so complicated.  how about this:
>>
>>	char tmpname[] = "/tmp/foo.XXXXXX";
>>	mktemp(tempname);
>[should be tmpname]
>>
>
>Careful -- it doesn't work for some C-compilers:
>"t.c", line 3: no automatic aggregate initialization
>"t.c", line 3: illegal lhs of assignment operator
>
>Program defensively! I'd rather have something complicated that works!
>

I think there is a misunderstanding here. "line 3" is either legal C,
and always has been, or illegal C, and still is, depending on where
the line is.

The word "automatic" in the error message refers to the storage class
of the variable "tmpname". If line 3 appears inside a function, the
storage class assumed is "auto", and no, you can't copy around arrays
like that in C. If line 3 is outside a function, the storage class
assumed is "extern", and the statement becomes an initialisation of
the array (not any sort of assignment), and has been legal C since at
least 1975. No C compiler could refuse it.

--
Greg Rose                 Australian Computing and Communications Institute
ggr@acci.com.au                                              +61 18 174 842
`Use of the standard phrase "HIJACKED" may be inadvisable' -- CAA
From: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: Project lists.
Date: 5 Nov 92 16:07:27 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

It has been suggested to me that a ported software list, like the one
that gets posted for BSDI, would be usefull together with a projects in
progress list, much like the one for Linux. I've therefore volunteered
myself to maintain these lists. If you've ported any software to 386bsd
then let me know what it is, how stable it is and where it's available.

I hope the projects list will help to co-ordinate work on future ports
and other software projects such as library development. If you're
working on a particular area of 386bsd or are porting some software then
let me know the details and I'll put you one the list. Hopefully this
will prevent duplication of work.

I'll forward this mailing and any lists I create to the Jolitz's as well
so they now what's happening.

When I get it sorted out I'll start posting the lists periodically (say
every month).

Do people think these lists would be helpful?
-- 
  Paul Richards at Cardiff university, UK.

  spedpr@uk.ac.cf.thor	Internet: spedpr@thor.cf.ac.uk
  UUCP:     spedpr@cf-thor.UUCP or ...!uunet!mcsun!uknet!cf!thor!spedpr
+++
From: frank@martha.utcc.utk.edu (frank segner (phrank))
Newsgroups: comp.unix.bsd
Subject: Re: Try netHack, was Re: Also a question on rogue*
Date: 12 Nov 92 05:45:26 GMT
Article-I.D.: utkux1.1992Nov12.054526.14472
Organization: University of Tennessee Computing Center
X-Newsreader: Tin 1.1 PL3

bjork@telebit.com (Steven Bjork) writes:
: In article <BxJ9tt.BLz@iat.holonet.net>,
:  richardl@iat.holonet.net (Richard Levenberg) writes:
: 
: >Any ideas or suggestions for debugging this.  Is the source available
: >somewhere?
: Upgrade to NetHack!
: I've made a minor patch that allows nethack to compile.
: If anyone cares, I can put it on ref.tfs.com.
: --Steven

steven is right ! 
bye the way: it's also very easy to compile moria(5.5) ;-)    (a nice game too)
-> try it ! (ask archie or read rec.games.moria to find the sources)

--frank

frank@martha.utk.edu   |       'your theory is crazy, but it's not crazy enough
                       |        to be true.'           niels bohr (who else !?)
Newsgroups: comp.unix.bsd
From: jkh@esel.lotus.com (Jordan K Hubbard)
Subject: Re: ftp inc has bsd on cd-rom
Organization: Lotus Ireland
Date: Thu, 5 Nov 1992 19:59:39 GMT

Yes!!  Address?  We folks overseas need more than just a company name to
go on..

				Jordan
			PCS Computer Systeme GmbH, Munich, West Germany
	UUCP:		pyramid!pcsbst!gj gj@meepmeep.pcs.com
	EUNET:		unido!pcsbst!gj
Newsgroups: comp.unix.bsd
From: bjork@telebit.com (Steven Bjork)
Subject: Try netHack, was Re: Also a question on rogue*
Organization: Telebit Corporation; Sunnyvale, CA, USA
Date: Wed, 11 Nov 1992 15:11:28 GMT

In article <BxJ9tt.BLz@iat.holonet.net>,
 richardl@iat.holonet.net (Richard Levenberg) writes:

>Any ideas or suggestions for debugging this.  Is the source available
>somewhere?

Upgrade to NetHack!

I've made a minor patch that allows nethack to compile.

If anyone cares, I can put it on ref.tfs.com.

--Steven
Newsgroups: comp.unix.bsd
From: raz@socs.uts.edu.au (The Inimitable Raz)
Subject: Re: [386bsd] Colorado Jumbo tape drive device driver.
Organization: Computing Sciences, Uni of Technology, Sydney.
Date: 12 Nov 92 03:33:15 GMT

levinson@vax.sonoma.edu writes:

>In article <raz.720786927@ultima>, raz@socs.uts.edu.au (The Inimitable Raz) writes:
>> Has anyone developed, is anyone working on, has anyone worked on a 
>> 386bsd driver for utilising Colorado Jumbo 250M, floppy controller
>> attached, tape drives?
>> 
>> Does anyone have any info or code at all for driving these items?

>It is amazing, that with all the Jumbo systems sold, only you and I are asking
>about a driver for this tape drive!

>If you happen to find one, let me know.  If I find one, I will let you know.
> 
>I am still waiting for Colorado Memory Systems to respond to a message I sent
>to their Compuserv address.  It has been about 3 weeks.

I've had a little more luck. I faxed their buyer registration department
(no way I'm phoning them from here!) and they faxed back some advice and
a minimal list of QIC standards to implement. I am now trying to get my
hands on the relevant standards - Australian Standards were no help at
all. Their librarian claims that the are no Australian standards (and thus
by implication no ISO standards) for the storage of data on magnetic
tape!

Does anyone have QIC standards available for FTP? 


--
Bye for now.
         - Raz           

raz@socs.uts.edu.au   (Roland Turner)   (OH) 61 2 319 5700
From: knier@miller.cs.uwm.edu (Robert Knier )
Newsgroups: comp.unix.bsd
Subject: XFree86
Date: 5 Nov 1992 06:48:51 GMT
Organization: University of Wisconsin, Milwaukee
NNTP-Posting-Host: 129.89.9.13

   Sorry if this is a dumb question - but I'm new to X installation.
When I run 'xdm -nodaemon' from the prompt, the system sits and writes
errors to the xdm-erorrs file.  The error I'm receiving is : 

Cannot establish tcp listening socket
error (pid 226): Server for display :0 terminated unexpectedly: 1
Binding TCP socket: Can't assign requested address


Any ideas?

Thanks!

Bob Knier
(knier@miller.cs.uwm.edu)
Newsgroups: comp.unix.bsd