HDTenEightyP/NetNews huggingface dataset:
From: dpn2@po.CWRU.Edu (Damien P. Neil)
Newsgroups: comp.os.linux
Subject: Re: What's happening to my memory?
Date: Sun, 13 Dec 1992 03:40:26 GMT
Organization: Case Western Reserve University
NNTP-Posting-Host: b63519.student.cwru.edu

In article <dpn2.195.724208247@po.CWRU.Edu> dpn2@po.CWRU.Edu (Damien P. Neil) writes:
>So far as I can tell, something is happening to a fair chunk of the memory 
>on my machine when I run under Linux. I just tried to compile NetHack, and 
>get out of memory errors...with a six meg swap partition active! Something 
>is wrong here...

Whoops...never mind! I figured out the problem. I was forgetting to run 
swapon after mkswap... :-/

Thanks again to everyone who helped me!
-----
Damien Neil   dpn2@po.cwru.edu    "Until somebody debugs reality, the best
Case Western Reserve University    I can do is a quick patch here and there."
CMPS/EEAP double majoring masochist               - Erik Green
From: pmcgilla@hp.uwsuper.edu (Patrick L. McGillan)
Newsgroups: comp.os.linux
Subject: arp crash under 0.99
Date: 15 Dec 92 22:13:03 GMT
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu

Hi,
 Just brought 0.99 on a second machine and when I try to telnet to it,
 I get an error on the console like;

 arp.c skb with bad magic - 1B7A46: squashing queue

 Who has some thoghts about what this means and how to correct it. Using
 the latest NE2000 drivers on an AT&T 386 20mhz machine - 4mb.

 Same card and drivers work fine on a clone 486-33.

--
Patrick L. McGillan
Computer Systems Specialist
University Of Wisconsin     Ph:  (715) 394-8191
Superior, Wisconsin         pmcgilla@uwsuper.edu
From: ctne_ltd@uhura.cc.rochester.edu (Chris Newbold)
Newsgroups: comp.os.linux
Subject: Re: HELP X gods! .99 broke my xdm!
Date: 15 Dec 92 15:28:01 GMT
Organization: University of Rochester - Rochester, New York

In <chuck.724403077@perlab.eas.asu.edu> chuck@perlab.eas.asu.edu (Chuck Lunskis) writes:

>operjsl@HYDRA.ROSE-HULMAN.EDU writes:

...

>>However, xdm locks up my machine.  xdm was working fine on 0.98.5, and nothing
>>has changed with the xdm (or X, for that matter) stuff since then.  I can 
>>start X with startx just fine.  But xdm locks it up.  Once I was lucky
>>enough to get some errors in the xdm-errors.  Basically, it said 'hung in
>>XOpenDisplay (:0); aborting' and then 'cannot open display.'  Does anyone
>>know what my problem is here?  This is important to me since I have several
>>users, and xdm is their way to login and X is the environment of choice.  Do
>>I need to recompile the xdm source?  Do I have an old version of xdm?  I am
>>running XFREE86-1.1.

>I too am having problems with 0.99 and xdm.

>xdm starts, and I get the login prompt, but can't log in.  Most of the keys
>work, but a few (like 'r', 'RETURN', and some others) don't function.  I also
>get this incessant beeping with every keystroke.  startx also works okay for
>me, it's just xdm with the problem.

Me too. xdm was find under 0.98-pl5, but broke under pl6 and is still dead
at 0.99. Same symptoms: startx works fine, but xdm hangs with a black
screen. If I hit return, it sort of comes up, but anything I type comes out
as garbage in the colsole log window.

It does produce a core file as well...

I'm running the S3 server, version 0.3.

-Chris
-- 
>>>> Chris Newbold <<<< * "If you fool around with a thing for very long you *
University of Rochester	*  		  will screw it up."		     *
Disclaimer: "All warranties expire upon payment of invoice."                
ctne_ltd@uhura.cc.rochester.edu * uhura.cc.rochester.edu!ctne_ltd@uunet
From: jepstei@afterlife.ncsc.mil (John Epstein)
Newsgroups: comp.os.linux
Subject: [SOLUTION]: booting linux-0.99
Date: 20 Dec 92 17:38:45 GMT
Organization: The Great Beyond

I had success with booting linux-0.99 (in fact running it now).

I had to do make clean; make config; make dep; make disk MORE THAN ONCE
to get it to work.  Michael Johnson said the problem is with FPU
emulations.  I "know" I answered yes every time I did a make config!!!

BTW: The default in the configure script SHOULD BE y vice n for
FPU emulation.  My reasoning: if you have a 486 or 386/387 no harm is done.
If you have a 386 without a 387 then the present default will not build
a working system.

Have a safe and happy holidays --- back-up your systems!!!

John
From: sadkins@bigbird.cs.ohiou.edu (Scott W. Adkins)
Newsgroups: comp.os.linux
Subject: Intel Ethernet Board
Date: 17 Dec 92 14:17:00 GMT
Organization: Ohio University CS Dept., Athens

If anybody has gotten an Intel EtherExpress16 board to work with Linux, 
please let me know! :-)  Likewise, if anybody knows that they have gotten
Linux to run with an 82586 Chip (!), let me know... The board above uses
the chip, and I am in need getting this all to work...

Thanks,
Scott

-- 
         Scott W. Adkins           Internet: sadkins@ohiou.edu
         ~~~~~~~~~~~~~~~                     ak323@cleveland.freenet.edu
    Ohio University of Athens        Bitnet: adkins@ouaccvma.bitnet
Newsgroups: comp.os.linux
From: eric@tantalus.nrl.navy.mil (Eric Youngdale)
Subject: Re: Dying IDE disk drive.
Organization: Naval Research Laboratory
Date: Tue, 15 Dec 1992 04:11:16 GMT

In article <92121423631@vtrx33.uucp> don@vtrx33.uucp (Donald E. Cope) writes:
>Eric Youngdale (ericy@hal.gnu.ai.mit.edu) wrote:
>: 	It seems that I am usually answering questions, but now the tables are
>: turned.  This morning my IDE disk died.  Not completely, but I get all kinds of
>:    The HD error message says that
>: the error code is 0x10, the status is 0x59.  The file hdreg.h says that 0x10
>: means ID_ERR, whatever that is.

>When each hard disk is low level formatted an ID is included into each and
>every sector so that when the disk is read or written, it can ensure that
>the head is at the right spot on the disk.  The ID part is read and checked
>before a read or write can be performed.  If you give the drive parameters
>of say cyl 75 head 2 sector 34 and you only have 17 sectors per track you
>will get a status of 0x59 or 0x51 and a error code of 0x10 saying the ID
>has not been found at this disk location.

	I came to the conclusion that I had a head crash.  The dealer replaced
the drive, and for 150$ let me upgrade from 125Mb to 210Mb.  I have most of the
stuff restored from tape, but I still have some minor details to clean up.

Thanks.

-Eric




-- 
Eric Youngdale
From: kbj@po.CWRU.Edu (Kevin B. Jacobs)
Newsgroups: comp.os.linux
Subject: HELP!!!!  SCSI problem!
Date: 12 Dec 92 00:44:24 GMT
Reply-To: kbj@po.CWRU.Edu (Kevin B. Jacobs)
Organization: Case Western Reserve University, Cleveland, OH (USA)
NNTP-Posting-Host: thor.ins.cwru.edu


I'm really not at all happy with linux so far.  Its nuked my harddrive and
caused me hours of untold grief.  I've asked all the IRC #linux gurus I
couldhunt down for help and they don't seem to have a clue... so here
goes:
  I have a Western Digital 7000FASST SCSI controller, and a Maxtor 338meg
hard drive.  Its physical characteristics are:

  Cylinders            = 1632    !!!!  They say this is a problem !!!!
  Tracks/sector        = 54
  Heads                = 8
  Tracks/Zone          = 8
  Alt. Sectors/zone    = 5
  Alt. Tracks/zone     = 0
  Bytes/Pysical sector = 512
  Interleave           = 1
  Track Skew           = 0
  Cylinder Skew        = 16

I boot up, it recognizes my controller, it says

"bad paritiion table for dev 0800
 partition table ok."

When I boot.

I then run "fdisk /dev/sda" and I enter the extended options menu and
enter the tracks, cylinders and heads and it ends up nuking my hard drive
without fail.

To put my request simply:  HELP!!!!!!!!!!!!!!!

Many thanks,
Kevin Jacobs   --- programmer seeking to become one with the wall. 
                   At high speed

-- 
---  Camber - Kevin  ---             | If the red slayer think he slays,
E-Mail:  kbj@po.CWRU.edu             |   Or if the slain think he is slain,
                                     | They know not what the subtle ways
quote by:  Ralf Waldo Emerson        |   I keep, and pass, and turn again.
Newsgroups: comp.os.linux
From: asimard@emr1.emr.ca (Andre Simard)
Subject: 1542B setup with 0.98 question
Organization: MPS, Energy Mines & Resources, Canada
Date: Fri, 18 Dec 1992 13:54:57 GMT

I decided to give a try at linux and got the boot and root images of 0.98.

I did the installation and things are ok so far (had to look at the INSTALL 
series of commands since the automatic installation doesn't seem to work 
with the Adaptec).

My problem arrives with pboot so here are my questions.

1) Can someone tell me the numbers to enter (I tried 0303 -- third primary 
partition on the disk)?  I.E.: is there a different number for sda (03)?

2) Do I have any other surprises waiting for me because of the 1542B?

3) I saw in the news that 0.99 is out, where can I get it from?

4) What else

Please email me and I will post a summary to save bandwidth.
-- 
Andre Simard
asimard@emr1.emr.ca
----------------------------
Newsgroups: comp.os.linux
From: bkuhn@cs.loyola.edu (Bradley " b " Kuhn)
Subject: Problem w/ .99 boot disk created by SLS
Organization: Loyola College in Maryland
Distribution: comp
Date: 20 Dec 92 22:34:46


I recently attempted to install the latest SLS distribution.  Things seemed
to go fine.  a1 booted ok; I mounted a2, created a file system, rebooted and
installed the whole thing (a, b, c, and x).

Then, when I asked to created a boot disk, I put the formatted disk in as
requested.

When I boot from that disk, I get the following messages:
.
.
.
.
floppy drive(s): fd0 is 1.44M
floppy: IPC region 0X90
sock_init: initialized family 1 (AE_UNIX)
sock_init: initialized family 2 (AE_NET)
Loopback device init
Warning: WD8013 board not found at i/0 = 280
hda:

At this point, the boot hangs...C-ALT-DEL does nothing....I have to turn off
the power.
My system configuration is the following:
Notebook 486DX Proffesional
486DX @ 33 MhZ
16 MB RAM
212 MB IDE HD
  /dev/hda1 is a 106 MB DOS partition
  /dev/hda2 is a maximum sized Linux/Minux partition

Circus VGA BIOS V 3.63
486DX Modular BIOS V3.20-B from Award Software

Any help would be appreciated.  I am excited about getting Linux up and 
running and possibly ditching Coherent as my PC Unix system of choice.
Thanks.  Respond via email, or to the group if you enjoy increasing the ever-
increasing volume of comp.os.linux.



--

 -- Bradley M. Kuhn    Computer Systems Development, Inc.

     INTERNET: bkuhn@cs.loyola.edu, bkuhn@loyola.edu, kuhn@cpwsca.psc.edu,
               rhlab!bkuhn@uunet.uu.net (take your pick :-)
     BITNET:   bkuhn@loyvax.BITNET
     UUCP:     ...uunet!rhlab!bkuhn
     SNAIL:    100 W. Cold Spring Lane, Box: 141, Baltimore, MD   21210
     VOICE:    (410) 617-(4343 || 4497), (x4343 || x4497 on Loyola Campus)

Newsgroups: comp.os.linux
From: shanea@extro.ucc.su.OZ.AU (Shane Alderton)
Subject: Re: PATCH: (0.98.6) allow root to link/unlink directories
Keywords: kernel,patch,0.98.6,fs,link,unlink,root,directory,namei,standard,fix
Organization: Sydney University Computing Service, Sydney, NSW, Australia
Date: Sun, 20 Dec 1992 00:44:19 GMT

torvalds@klaava.Helsinki.FI (Linus Torvalds) writes:

>I just wanted to say that while the patch may work (I didn't look at it
>closer, but it should be simple enough), this is a feature that the
>current kernel forbids for a very good reason: linking/unlinking
>directories is generally a very bad idea, even if it's restricted to
>root.  It's available in some unixes due to the way they implement
>moving of directories, but it's unsafe.  All versions of linux have
>explicitly checked for directories, and not allowed links/unlinks to
>them. 

>Is there anybody out there that actually needs this? I'm just warning
>you that this patch won't get into the standard kernel unless somebody
>can come up with a truly good reason for it (I doubt there is any). 

Well, I don't know whether or not you would consider it a good reason,
but it is something I have needed to do in the past when file system
corruption caused a directory with an entry that I couldn't delete and
that the efsck of the time could not handle.  This of course meant that
I could not rmdir the directory in question, as it appeared to contain
a file.  Perhaps being able to unlink the directory would have solved
the problem, albeit in a messy fashion.

I agree that it is a very dangerous thing to do, but one of the things
I like about Unix in general is its power and the small number of
assumptions it makes.  GNU's rm does protect you from accidentally
unlinking a directory  - and even if I could not think of a reason for
being able to do this, that just means that my imagination is limited,
not that it could never be necessary.

Incidentally, I will add my voice to all those others who have said:
THANK YOU!  for the best thing to hit PCs - Linux.

Regards,
Shane Alderton
shanea@extro.ucc.su.oz.au
From: ericy@hal.gnu.ai.mit.edu (Eric Youngdale)
Newsgroups: comp.os.linux
Subject: Dying IDE disk drive.
Date: 12 Dec 1992 20:47:07 GMT
Organization: /etc/organization
NNTP-Posting-Host: hal.gnu.ai.mit.edu


	It seems that I am usually answering questions, but now the tables are
turned.  This morning my IDE disk died.  Not completely, but I get all kinds of
HD errors, and an occasional HD reset, followed by a kernel panic because it is
unable to read the inode table.  All of this came about unexpectedly with no
warning while I was in the middle of using the system.  The thing that is
really queer is that two of the partitions on the disk are just fine.
Unfortunately these are my DOS and my swap partitions - my root and home
partitions are the two that seem to be afflicted.  I can do an od on both the
dos and swap partitions and I get no errors.  The HD error message says that
the error code is 0x10, the status is 0x59.  The file hdreg.h says that 0x10
means ID_ERR, whatever that is.

	Anyway, this is one of those 125 Mb Seagate half-height 3-1/2" disks,
IDE interface, about 7 months old.  I have tried the usual sorts of tricks with
reseating the controller board and cable and that does not help.  Does anyone
have any suggestions for something else to try this weekend, or should I go the
replacement disk drive route on Monday?  I am not terribly concerned about the
data on the disk, because I have a scsi tape drive and I use it regularly :-).

-Eric
From: rick@ee.uwm.edu (Rick Miller, Linux Device Registrar)
Newsgroups: comp.os.linux
Subject: Re: Boot problems with 0.99 (& LILO)
Date: 16 Dec 1992 17:15:16 GMT
Organization: Just me.
NNTP-Posting-Host: 129.89.2.33
Summary: LILO BETA.7 works *fine* for me...

pmcgilla@hp.uwsuper.edu (Patrick L. McGillan) writes:
>Hi,
>I see many of you are have boot problems after compiling the new 0.99
>kernel. I did to, until I hand patched the files that Linus said should
>be fixed. DID YOU? Best I can recall there are either two or three patches.
>My 0.99 works great, sort of. Lilo is dead and I have to boot from floppy.

I compiled LILO BETA.7 under Linux 0.98.6 w/ GCC 2.2.2d7 and it worked just
fine booting Linux 0.99 (which I also compiled under the same conditions).

BTW: I *really* like the "make config" routine... it's a *lot* nicer than
	trying to find my way through editing two dozen files going by
	directions from half a dozen README's.

Rick Miller   <rick@ee.uwm.edu> | <rick@discus.mil.wi.us>   Ricxjo Muelisto
Occupation:  Husband, Father, WEPCo. WAN Mgr., Discus Sys0p, and  Linux fan
Newsgroups: comp.os.linux
From: mdw@db.TC.Cornell.EDU (Matt Welsh)
Subject: Re: Loopback Network question
Organization: The Linux Inquisition, Propaganda Division
Date: Sun, 13 Dec 1992 00:03:39 GMT

In article <1992Dec12.230105.3948@pasteur.Berkeley.EDU> c60c-2gf@web-2d.berkeley.edu () writes:
>Problem 1:
>I can telnet, ftp, and ping myself using either my hostname or full
>address.  However, if I try to ftp or telnet to 0, the system crashes
>and reboots.

"Don't do that, then!" :)

>Problem 2:
>If I just finger, or finger <username>, it works fine.  But if I
>finger <user>@<my-hostname> or just @<my-hostname> it just prints out 
>my hostname in brackets and displays no information.

Make sure your finger is in the right place. When you run finger @hostname,
it has to start up fingerd to do the net_finger() stuff. Fingerd has to
run finger to get the information, and fingerd expects finger to be in
a certain place (/usr/local/bin/finger on my setup). Just do a 
'strings fingerd | grep finger' to see where fingerd expects it to be.

Good luck!

mdw
-- 
Matt Welsh     mdw@tc.cornell.edu     Cornell Theory Center
  "Go on, emote! I was raised on thought balloons!"
Newsgroups: comp.os.linux
From: tjrc1@cus.cam.ac.uk (T.J.R. Cutts)
Subject: Re: YANUI (Yet another new user inquiry!)?
Organization: U of Cambridge, England
Date: Mon, 14 Dec 1992 12:28:21 GMT

In article <GHENNIGA.92Dec12000414@ampere.ampere>, ghenniga@NMSU.Edu writes:

|> 	My second question is, is there any SVGA support for my video card,
|> F1280 (S3 based)? I can't even get mono X support to work on my card. A
|> 'startx', with X being configured for mono, appears to put my card in
|> graphics mode but then just locks up my machine, and this IS for mono
|> support since the color configuration gives me definate error messages and
|> exits X without locking up.

You need the S3 server.  This is available at various sites; I got my copy from
robots.ox.ac.uk (or maybe it was ftp.robots.ac.uk, I can't remember).  Once
you've got that, I will pre-empt some other problems you will have:

1) Uncompress all your font files
2) Run mkfontdir
3) Replace your Xconfig fontpath line with that from the supplied Xconfig.mono

This is what I did, and now have X speeding along at 1024x768 in glorious
technicolour...


-- 
-- Tim Cutts                             /~\     ----
                                        (   )  /     \
Sugarmice on a skateboard               /   \/        \
                                      /  O             \
                                    /                   \
                                    \____________________================
                                 -===========================-
                                   O                       O
From: root@slave.uwe.ac.uk (Operator (Phil/Dylan))
Newsgroups: comp.os.linux
Subject: Re: SLS98p1-TCPIP
Date: 17 Dec 92 04:38:31 GMT
Reply-To: p_copela@csd.uwe.ac.uk
Organization: The New University in the West of England, Bristol (WEB)

In article <1992Dec11.221047.22954@sun1.ruf.uni-freiburg.de>,
hartnegg@sun1.ruf.uni-freiburg.de (Klaus Hartnegg) writes:
|> Michael_Kraehe@hb.maus.de (Michael Kraehe) writes:
|> 
|> >   socket: Protocol not supported
|> 
|> ftp ftp.ruf.uni-freiburg.de
|> cd pc/linux/packages/tcpip
|> get config.c
|> quit
|> cc -o config config.c

alternively, another mishap that will cause this is the absence of a
'protocols'
file... absolutely devestating if you are mounting NFS systems in your rc 8-)

/etc/protocols (linked to /usr/etc/inet/protocols should have the following
/etc/protocols
        # protocols - standard well defined IP protocols
        ip      0       # internet protcol, pseudo protocol number
        icmp    1       # internet control message protocol
        igmp    2       # internet group multicast protocol
        ggp     3       # gateway -> gateway protocol
        tcp     6       # transmission control protocol
        egp     8	# (forgotten but it's on our sun's)
        pup     12      # PARC universal packet protocol
        udp     17      # user datagram protocol
        idp     22	# Think this is internet datagram protocol?
        raw     255     # raw

I beg to differ with the 0.8.0 distribution's line which says
	ggp     2
but this isn't used yet (I think) so it shouldn't matter (just being purist)

Phil
=--=
Newsgroups: comp.os.linux
From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger)
Subject: Re: lilo boot problem with 0.98p5 SLS
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Date: Mon, 14 Dec 1992 01:35:41 GMT

In article <Bz6KK3.Jps@acsu.buffalo.edu> jchen@acsu.buffalo.edu (Jonathan Chen) writes:
>	partition table ok
>	MINIX-fs: unable to read superblock
>	EXT-fs: unable to read superblock
>	MSDOS bread failed
>	kernel panic: Unable to mount root

*Sniff,sniff* ... I smell a new FAQ.

This happens if a) your kernel has no or the wrong boot device set and
b) you didn't tell LILO to override the boot device setting of the kernel.

To fix a) use rdev aka setroot, e.g. rdev /linux /dev/hda1
(or change the value of ROOT_DEV in the top-level kernel Makefile,
rebuild the kernel and - of course - run /etc/lilo/install.)

To fix b) (the preferred solution):

   If you're using old-style configuration, append ,<rootdev> to the
   descriptor of your kernel, e.g. /linux,/dev/hda1

   If you're using new-style configuration, add the variable
     root = <rootdev>
   after the  image = ... variable in your /etc/lilo/config, e.g.

   image = /linux
     root = /dev/hda1

   Then run /etc/lilo/install to copy the settings into the map file.

- Werner
-- 
   _________________________________________________________________________
  / Werner Almesberger, ETH Zuerich, CH      almesber@nessie.cs.id.ethz.ch /
 / IFW A44  Tel. +41 1 254 7213                 almesberger@rzvax.ethz.ch /
/_BITNET:_ALMESBER@CZHETH5A__HEPNET/CHADNET:_[20579::]57414::ALMESBERGER_/
Newsgroups: comp.os.linux,comp.unix.bsd
From: jochen@busybit.mrz.sub.org (Jochen Fahrner)
Subject: Re: [386bsd]  cp something to /bin/cp and cp core dumps; bug or feature?
X-Md4-Signature: 5629c2ad0e0f4736342a3bf6f68a4646
Organization: Busybit's Software Labor, D-8068 Pfaffenhofen
Distribution: comp
Date: 8 Dec 92 18:56:02
	<1fjcsuINN2vf@hrd769.brooks.af.mil>

In article <1fjcsuINN2vf@hrd769.brooks.af.mil> burgess@hrd769.brooks.af.mil (Dave Burgess) writes:

     I have also noticed something that bothers me a little bit.  I was ftping
   a bunch of files from point A to point B and managed to ftp /usr/bin/ftp.
   The execed ftp core dumped.

     Why?

   I have seen the same thing with several other programs (cp, for example).
   What umbilical link is there between a running program and its image on
   disk?

Why is it possible to overwrite a program which is currently executing
in memory ? I don't know BSD, but in SYSV this is impossible.

Jochen
-- 
Jochen Fahrner, D-8068 Pfaffenhofen, jochen@busybit.mrz.sub.org
From: S_ESPENLAUB@rzmain.rz.uni-ulm.de (Klaus Espenlaub)
Newsgroups: comp.os.linux
Subject: X and Speedstar (don't kill me too)
Date: 14 Dec 92 16:09:51 GMT
Organization: University of Ulm, Germany
X-News-Reader: VMS NEWS 1.24

I'm interested in the Xconfig for a Diamond SpeedStar HiColor, too.

I've figured out how to make 640x480 and 800x600 but not 1024x768 at 70Hz.
This is not acceptable with a 17" monitor.

please post it because there are many users with this card.

Thanks
From: iarit@slate.mines.colorado.edu (ARIT ISMAIL)
Newsgroups: comp.os.linux
Subject: UUCP strange problem..
Date: 15 Dec 92 02:51:06 GMT
Organization: Colorado School of Mines

Hi there,

First, thanks to Ian Justman's tip, UUCP is not giving me
'segmentation fault' anymore.
Here is my /usr/lib/uucp dir;

Devices      Permissions  paths        uucico       uuxqt
Dialers      Systems      uuchk        uucico.old   uuxqt.old

I was having problems sending stuff over UUCP, and just remembered
to run uulog -s sytemName, and got this;

$ uulog -s tara
uucp tara (12/13-17:38:32,1417,0) Calling system tara (port ttys1)
uucp tara (12/13-17:38:32,1417,0) ERROR: fopen (/usr/lib/uucp/Dialers): No
such
 file or directory
uucp tara (12/13-17:38:32,1417,0) ERROR: hayes: No such dialer
uucp tara (12/13-17:38:32,1417,0) ERROR: fopen (/usr/lib/uucp/Dialers): No
such
 file or directory

what is going on??

If I run uuchk, it sees everthing correctly.

It looks like uucp can't read Dialers file, why?
any help would be appreciated.
thanks...(:-)
iarit@slate.mines.colorado.edu