Re: Repeated messages?

1998-07-09 Thread Chea Prince

its not just you.  something's hosed somewhere. 

On Wed, 8 Jul 1998, Evan
Van Dyke wrote:

> Is it just me, or am I getting messages from two or three days ago again?
> 
> --Evan, who swears he's seed the dir *. /s msg before...
> ---And the Gateway message... and others...
> 
> 
> --  
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
> 
> 

==
  The man
PUBLIC DOMAIN, INC.  Of virtuous soul commands not, nor obeys:
P.O. Box 8899-0899   Power, like a desolating pestilence,
Atlanta, GA  30306   Pollutes whate'er it touches, and obedience,
VOX: 404.373.0980Bane of all genius, virtue, freedom, truth,
FAX: 404.378.3607Makes slaves of men, and, of the human frame,
[EMAIL PROTECTED]   A mechanised automaton. 

 --Percy Bysshe Shelley
=


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null


Re: bo-->hamm: 'iso9660 not supported'

1998-07-09 Thread Chea Prince

john, thanks for your patience and your help.  purged ppp-2.3.5 and
downgraded to ppp-2.2.0f...so i'm once again happily SLiRPing along.  i
had tried just downgrading without purging the newer version but got the
same behavior from 2.2 as 2.3 as long as 2.3 was on the system. 

--c


[EMAIL PROTECTED] wrote:

> > SIOCADDRT: Operation not supported by device
> 
> > why would i get this?  can add/del default route for ppp0 fine on machine
> > running an older version of linux and ppp
> 
> pppd creates the interface when it starts ppp and deletes it when it exits.
> What you need to do is put a route command in ip-up delete the default
> route to your ethernet and one to restore it in ip-down, or, if you don't
> need a default route to the ethernet (you probably don't), edit the
> appropriate init script so it never gets created.
> 
> > i'll check into it.
> 
> Perhaps you could try downgrading to pppd-2.2?
> -- 
> John Hasler
> [EMAIL PROTECTED] (John Hasler)
> Dancing Horse Hill
> Elmwood, WI


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null


Re: autoup.sh + deselect broke emacs

1998-07-08 Thread Chea Prince

i had the same thing happen and i had selected to upgrade emacs to
20.xx...made a mess.  it was the only really broken package.
had been wanting to check out xemacs so ended up purging emacs and
installing xemacs-20.whatever and like it.  anyway, suspect you will need
to purge emacs and do a clean install.  i had to abandon dselect and use
dpkg to remove emacs, then ftp'd xemacs packages and used dpkg to
install them. 

best--c
  
On Wed, 8 Jul 1998, Edward J. Young wrote:

> 
> 
> I should mention that in the deselect screen, there are headings for
> packages that are headed as "obsolete", one being emacs. Does this mean
> what I think: that emacs 19.34.? is now obsolete because I've upgraded
> around it and now it needs upgrading too? Probobly. 
> 
> There are some other packages labeled "obsolete" as well. 
> 
> How should this be handled? 
> 
> 
> One other question:
> Where can I get a CD in the Denver area? I would order a CD of 2.0 but it
> seems to still be in a state of flux and I don't want to have a CD which
> may or may not have a fully stable Debian system. 
> 
> Thanx, 
> 
> Ed
> 
> On Wed, 8 Jul 1998, Edward J. Young wrote:
> 
> > 
> > 
> > I have upgraded from 1.3.1 to hamm with some difficulty, but feel like
> > I'm getting there. My latest problem is that when invoking emacs from a
> > console, I get "segmentation fault", and no emacs. 
> > 
> > I don't believe that emacs was upgraded during the deselect process so I
> > suspect that the version I had (v19.34.?) requires the old libc, though I
> > realy don't understand the issues here.
> > 
> > How do I rectify this?  By running deselect and upgrading Emacs. I'm loath
> > to try that since emacs is huge and a download would be epic, but if
> > absolutely necessary I will. 
> > 
> > If it matters, My upgrade went like this: 
> > -autoup.sh
> > -deselect with ACCESS UPDATE, INSTALL (No SELECT)
> > -several more iterations of INSTALL since the first ones resulted in
> >  brokenly uninstalled packages. 
> > -dselect and running SELECT to get X running (but that's another
> >  posting...)
> > 
> > Now deselect reports no brokenly installed packages and I believe that all
> > the necessary packages are now installed. 
> > 
> > So again, how do I fix emacs? 
> > 
> > Thanx in advance. 
> > 
> > Ed
> > NL7FU
> > [EMAIL PROTECTED]
> > [EMAIL PROTECTED]
> > 
> > 
> > 
> > 
> 
> 
> --  
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
> 
> 

==
  The man
PUBLIC DOMAIN, INC.  Of virtuous soul commands not, nor obeys:
P.O. Box 8899-0899   Power, like a desolating pestilence,
Atlanta, GA  30306   Pollutes whate'er it touches, and obedience,
VOX: 404.373.0980Bane of all genius, virtue, freedom, truth,
FAX: 404.378.3607Makes slaves of men, and, of the human frame,
[EMAIL PROTECTED]   A mechanised automaton. 

 --Percy Bysshe Shelley
=


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null


Re: REPOST: Diald routing (Help!)

1998-07-08 Thread Chea Prince

i'm having the same problem with slirp/ppp connection (connection gets
dropped).  pon scripts log in OK and slirp starts up but LCP negotiation
fails with error message "No Network Protocols Running"

tried disabling 'defaultroute' and adding the default route myself before
running pon, but doing 'route add default ppp0' results in message: 

SIOCADDRT:  Operation not supported by device

on another machine running an older version of linux (1.2/2.0.27) and
older version of ppp (2.2.0f) adding and deleting the default route
with 'route add/del default ppp0' works as it should and updates the
routing table.  any ideas about what's causing the error message above?

TIA--chea

> > Diald is already dialing when it should but the routing table is not
> > > being updated.
> 
>I've had the same problem.  Somewhere (either a HOWTO or a Linux Journal 
> article) I
> found advice about setting the routing manually.  This is what I'm doing now.
> 
>In /etc/ppp/ip-up (the script) I put a
> route del default
> route add default $1
>in just above the run-parts line.  This forces the default route to be 
> made.
> 
>Similarly, in /etc/ppp/ip-down I do a
> route del default
> route add default gw 207.140.8.1 metric 1
>also just before the run-parts command (perhaps that should be below it).
> 207.140.8.1 is just my ISP's gateway IP number.
> 
>Once doing this, this cleared up all of my diald routing problems.
> 
> > > Is there any problem with diald that prevents it from working out of the
> > > box with Debian? Im using the "pon" command as the dialer in
> > > diald.options.
> 
>I found that using "pon" in /etc/diald/diald.options caused the link to 
> disconnect
> after 30-60 seconds or so.  I had to adopt a more conventional script which 
> uses just
> chat and which doesn't call pppd.
> 
>But I agree.  So many people rely on diald it should work more seamlessly 
> with
> pppd.  This is an area which many people want to use, but one which is 
> frustrating for
> newbies (and even semi-newbies like myself;-).
> 
> --
>  Regards,  |Debian GNU/__ o http://www.debian.org
>  . |  / /__  _  _  _  _ __  __
>  Randy | / /__  / / / \// //_// \ \/ /
>  ([EMAIL PROTECTED])   |// /_/ /_/\/ /___/  /_/\_\
>  Tech. Coord./Teacher  |...because lockups are for convicts...
>|What is or why Linux?  Click on the below:
>  http://www8.zdnet.com/pcmag/pctech/content/16/13/os1613.001.html
> 
> 
> 
> --  
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
> 
> 

==
  The man
PUBLIC DOMAIN, INC.  Of virtuous soul commands not, nor obeys:
P.O. Box 8899-0899   Power, like a desolating pestilence,
Atlanta, GA  30306   Pollutes whate'er it touches, and obedience,
VOX: 404.373.0980Bane of all genius, virtue, freedom, truth,
FAX: 404.378.3607Makes slaves of men, and, of the human frame,
[EMAIL PROTECTED]   A mechanised automaton. 

 --Percy Bysshe Shelley
=


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null


bo-->hamm: 'iso9660 not supported'

1998-07-07 Thread Chea Prince

upgraded from bo to hamm on a pentium/166, no problem.  compiled kernel
2.0.34 + modules...everything installed OK.  but now can't mount cdrom
even though cdrom support is built into the kernel and bios identifies
cdrom as /dev/hdc during boot (worked fine under bo)...get following error
message:

mount:  fs type iso9660 not supported by kernel

while configuring the kernel i saw no option to choose iso9660 support
...did i miss something?  [menuconfig came up in b&w instead of color (not
that i care)...just weird.] also, ps2 mouse doesn't work as a module, only
if it is built into the kernel...is this peculiar to my system or
generally the case...just curious...related to this...why do i get the
following during boot regardless of whether device support is built-in or
selected as module:

cdrom: can't locate module cdrom
psaux: can't locate module psaux
serial: can't locate module serial

in the case of the mouse and serial ports doesn't seem to affect function
and they are correctly configured during boot process later on

also, ppp is broken again.  every time i upgrade it breaks existing
scripts.  EXTREMELY aggravating.  is there good reason why this happens? 
tried both old ppp-on script and new scripts configured with
pppconfig...get the same results.  what was a perfectly healthy
slirp/ppp connection now fails during LCP negotiations.  plog reports: 

send (slirp -P -b 115200^M) 
serial connection established
using interface ppp0
pppd[230]: Connect: ppp0 <--> /dev/ttyS1

begins LCP process, then fails about halfway through with:

sent [LCP TermReq id=0x2 "No Network protocols running"]
rcvd [IPCP ConfReq id=0x1  ] # 170.140.110.193 is the correct remote IP address #
pppd[230]: rcvd [CCP ConfReq id=0x1]
pppd[230]: rcvd [LCP TermAck id=0x2]
pppd[230]: Connection terminated.
pppd[230]: Hangup (SIGHUP)
pppd[230]: Exit. 

i obviously need a ppp/chatscript tutor.  RTFM doesn't seem to help.
all assistance appreciated.

TIA--chea



--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null


Re: serial troubles

1998-07-04 Thread Chea Prince
>   I remember some PCI errors showing up during boot with older kernels
> that were eliminated in later kernel versions(2.0.32+ ?), but, of
> course, I can't tell whether this applies to your situation.

yep.  upgrading removed (PCI-related) warnings during boot and now
XF86Config, e.g., recognizes the diamond s3-virge which it wasn't doing
before

> What exacly does 'can't initialize the modem' mean?  

the ppp-on-dialer script was unable to pass the 'AT' command to the modem.
there was txd/rxd activity but the modem was not receiving the command.

> I had a file
> permission problem with the /etc/chatscript/provider script that caused
> pppd to freeze when it tried to use the chatscript.  What does the end
> of the ppp.log look like?  Use plog to see this.

the string being passed by the script (which i borrowed from the PPP-HOWTO
included a /r -- '/rAT' -- the modem in the 486 had no problem with the
return.  but, both the gdc and the us robotics (on the pentium)
did. i removed the 'r' and...  voila.  funny.  had ruled out the script
because it "worked" and had been "tested."  duh. 

thanks, ed--c


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null


Re: serial troubles

1998-07-02 Thread Chea Prince

i suspected the modem too so tried a us robotics (usually have a gdc
connected)...both behave the same.  seems to be related to warnings at
bootup re: PCI ... there is a serial USB controller on IRQ 10 that is one
of the PCI devices that isn't recognized (identified by number)... i tried
disabling it and manually configuring /etc/rc.boot/0setserial but still
get the same behavior.  i need info on this PCI bizness.  i read the
PCI-HowTo but found nothing there of any use

the only debian cd i have is 2.0.27 (kernel)  think i'll try hamm
if i can find a cd...maybe PCI problems have been eliminated

best--c

On 2 Jul
1998, Miquel van Smoorenburg wrote:

> In article <[EMAIL PROTECTED]>,
> Chea Prince <[EMAIL PROTECTED]> wrote:
> >
> >have included serial support in the kernel and on bootup shows serial
> >devices being assigned to /dev/cua0 /dev/cua1 and /dev/ttyS0
> >/dev/ttyS1 but 'cat /proc/interrupts' shows no serial devices at
> >IRQ 3 & 4.
> 
> That's OK; the interrupts are only allocated when the port is actually
> opened. You see, you can't share interrupts at the same time between
> devices but 2 devices can use the same interrupt if they are not used
> at the same time. That's why IRQs are only allocated when used.
> 
> >can dialout fine from minicom but ppp script fails
> >(can't initialize the modem).
> 
> Smells like a modem problem. Maybe the modem is set to non-echo? Try using
> the init string from minicom in the ppp script.
> 
> Mike.
> -- 
>  Miquel van Smoorenburg | Our vision is to speed up time,
> [EMAIL PROTECTED]  |   eventually eliminating it.
> 
> 
> --  
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
> 
> 


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null


serial troubles

1998-07-02 Thread Chea Prince

have included serial support in the kernel and on bootup shows serial
devices being assigned to /dev/cua0 /dev/cua1 and /dev/ttyS0
/dev/ttyS1 but 'cat /proc/interrupts' shows no serial devices at
IRQ 3 & 4.  can dialout fine from minicom but ppp script fails
(can't initialize the modem).  same scripts run fine on a 486
which reports serial devices appropriately on reading /proc/interrupts.
system with the problem is a pentium 166mhz; (asus txp4 MB). 

thanks in advance for any assistance
best--c



--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null


Re: Linux & Compaq servers?

1998-06-25 Thread Chea Prince

don't have a server model in mind.  situation is this.  we (public domain,
inc. --pd) have been providing internet access to other nonprofits and
individual artists for the past seven years on a sun 4/280 running sun OS
4.1.1.  we now need to replace the sun -- which btw has run reliably 24/7
for all these years and only rarely required a reboot -- can't imagine
running anything but a 'unix' OS.  anyway, we have long been supporters of
free software/gnu/open source.  having looked over all the options we find
we are most closely aligned philosophically with debian/GNU.  i've already
installed debian on a 486 and pentium/166 and with the exception of some
choking on an onboard aic6160 scsi chip (append statements in LILO brought
no joy) all's well and i'm looking forward to upgrading to the 2.0beta. 
my interest in compaq is in trying to find a hardware DONOR.  i'm looking
for a company with a corporate giving program that will understand the
proposal i'm writing explaining our decision to go with Linux.  someone
mentioned to me (off this group) that compaq might be approachable. 
suggestion was that they were either shipping boxes with linux
pre-installed or shipping boxes without an OS on which unix/linux could be
installed.  i am looking for clarification on compatibility between debian
linux and compaq servers and on compaq's attitude toward linux in general
so i'll know what kind of spin to put in the proposal, or whether its even
worthwhile putting something in front of them at all.  if anyone happens
to know of a company thats particularly linux friendly, please let me
know. 

pd is a 501-(c)-3 so all donations are, of course, tax deductible.
please visit us at www.pd.org.  thanks for the response, OK.  

-c-



On Thu, 25 Jun 1998 [EMAIL PROTECTED] wrote:

> 
> Hi, Chea
> 
> On Wed, 24 Jun 1998, Chea Prince wrote:
> 
> > 
> > is Compaq shipping servers with Linux installed?  is there an article
> > somewhere outlining Compaq + Linux?
> > 
> 
> what kind of server(s) are you interesting in?
> 
> we just installed rh 5.1 (sorry, debian) on 2CPU
> Compaq Proliant 2500. I have some docs and
> howtos. Feel free to ask
> 
> regards
> 
> OK
> 
> 
> --  
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
> 

==
  The man
PUBLIC DOMAIN, INC.  Of virtuous soul commands not, nor obeys:
P.O. Box 8899-0899   Power, like a desolating pestilence,
Atlanta, GA  30306   Pollutes whate'er it touches, and obedience,
VOX: 404.373.0980Bane of all genius, virtue, freedom, truth,
FAX: 404.378.3607Makes slaves of men, and, of the human frame,
[EMAIL PROTECTED]   A mechanised automaton. 

 --Percy Bysshe Shelley
=


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Linux & Compaq servers?

1998-06-24 Thread Chea Prince

is Compaq shipping servers with Linux installed?  is there an article
somewhere outlining Compaq + Linux?




--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: aic6260, cdrom & linux

1998-06-11 Thread Chea Prince

thanks hamish.  tried your settings and still no joy.  this one's got me
stumped.  anybody else have a suggestion?  is there an optimal place to
put 'append' lines in lilo.conf?  

-c-


On Thu, 11 Jun 1998, Hamish Moffatt wrote:

> On Wed, Jun 10, 1998 at 12:59:28PM -0400, Chea Prince wrote:
> > did you ever get linux to see your cdrom?  i have an onboard aic 6260
> > scsi chip on an old zeos
> > gosling motherboard that linux refuses to recognize.  the bios can be
> > set to autodetect scsi and i'ved tried bios SCSI ENABLED--no suucess
> > with sutoprobe.  disabled bios and forced detection using
> > append="aha152x=0x340,11,7,1,0" & append="aic6260=0x340,11,7,1,0".  no
> > joy.  win95 has no problem
> > accessing the drive with SCSI ENABLED via bios.  seems to be a linux
> > thing.  trying desperately
> > to dump microsoft but snags like this are slowing me down.
> > 
> > any ideas?  anybody?  btw, cdrom is a NEC.
> 
> Hmmm, I think this is the same as card I have (VLB, with floppy, IDE,
> parallel/serial & SCSI all on board). To get it running with Linux,
> I used
> 
> aha152x=0x340,11,7,0,0
> 
> I think the 1->0 disables disconnect or similar. I used an NEC CD-ROM
> drive too and it worked.
> 
> 
> Hamish
> -- 
> Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
> Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5
> CCs of replies from mailing lists are welcome.   http://hamish.home.ml.org
> 

==
  The man
PUBLIC DOMAIN, INC.  Of virtuous soul commands not, nor obeys:
P.O. Box 8899-0899   Power, like a desolating pestilence,
Atlanta, GA  30306   Pollutes whate'er it touches, and obedience,
VOX: 404.373.0980Bane of all genius, virtue, freedom, truth,
FAX: 404.378.3607Makes slaves of men, and, of the human frame,
[EMAIL PROTECTED]   A mechanised automaton. 

 --Percy Bysshe Shelley
=


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


aic6260, cdrom & linux

1998-06-10 Thread Chea Prince
hi ralph

did you ever get linux to see your cdrom?  i have an onboard aic 6260
scsi chip on an old zeos
gosling motherboard that linux refuses to recognize.  the bios can be
set to autodetect scsi and i'ved tried bios SCSI ENABLED--no suucess
with sutoprobe.  disabled bios and forced detection using
append="aha152x=0x340,11,7,1,0" & append="aic6260=0x340,11,7,1,0".  no
joy.  win95 has no problem
accessing the drive with SCSI ENABLED via bios.  seems to be a linux
thing.  trying desperately
to dump microsoft but snags like this are slowing me down.

any ideas?  anybody?  btw, cdrom is a NEC.

best--chea


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]