Linux-Misc Digest #346, Volume #24                Tue, 2 May 00 16:13:03 EDT

Contents:
  Re: Cannot kill a process (Robie Basak)
  Re: tty_io.c used obsolete /dev/cua1... (Robie Basak)
  Re: Linux woes (Compaq for one) on the horizon ("Patrick")
  Re: XFree86 4.0 rpms ([EMAIL PROTECTED])
  Re: KDE vs Gnome? (Harlan Grove)
  Re: Need some help in choice of mail clients : A problem. (Madhusudan Singh)
  Re: X locks up solid, what can I do ?! HELP !!! (Ray)
  PCMCIA modem ([EMAIL PROTECTED])

----------------------------------------------------------------------------

From: [EMAIL PROTECTED] (Robie Basak)
Subject: Re: Cannot kill a process
Reply-To: [EMAIL PROTECTED]
Date: 2 May 2000 19:11:11 GMT

On Tue, 02 May 2000 18:37:25 +0800, Deden Purnamahadi said:
>RedHat 6.0, Kernel 2.2.5-15
>
>When I changed user's password with 'passwd' command, Linux gave me 
>an error message:
>
>New UNIX password: 
>Retype new UNIX password: 
>passwd: Critical error - immediate abort
>
>then the passwd command is hung in the process.
>I've tried to kill it with kill -9 , but it didn't succeed.
>
>Any other way I can kill the process ?

I think it did kill it; did it still have a process number? It may
be zombified, which basically means that it is dead, but it's parent
hasn't mourned/noticed yet.

When passwd expects to receive a password, it changes the terminal
settings so nothing gets echoed.

Type:
  reset
or
  stty sane

to restore to a normal terminal (believe me; passwd did get killed
if you successfully sent it a SIGKILL.

The only time kill -9 won't work is if there was a kernel oops - I've
only seen this in cutting-edge only-works-for-the-developer kernel
modules.

Robie.
-- 

------------------------------

From: [EMAIL PROTECTED] (Robie Basak)
Subject: Re: tty_io.c used obsolete /dev/cua1...
Reply-To: [EMAIL PROTECTED]
Date: 2 May 2000 19:13:33 GMT

On Tue, 02 May 2000 00:15:08 GMT, Chat d'Gouti�re said:
>RedHat 6.0
>Trying to connect to my ISP.
>I have no graphic environment.
>When I execute pppd, the connection goes only so far
>and then I get disconnected AND the root session closes
>on me.
>
>The log file mentions this :
>tty_io.c : used obsolete /dev/cua1 - update software to use /dev/ttyS1

This isn't the problem; give the 'debug' option to pppd and show
us a more verbose log.

[snip]

>I also get the same message when I use setserial on cua1.
>
>Maybe the error message from the /var/log/messages
>file has nothing to do with me losing the connection
>and terminating the Linux session.
>
>But if it did, I guess I need to update something here.
>What? From where? How? are my questions.

Change (wherever the setting is) the device of the modem you
are using from /dev/cua1 to /dev/ttyS1 - /dev/cua1 is now
obsolete. If you tell us which method (linuxconf? pppd directly?)
you are using to connect, someone can give you more info on this.

Robie.
-- 

------------------------------

From: "Patrick" <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,comp.os.linux.hardware,comp.os.linux.setup
Subject: Re: Linux woes (Compaq for one) on the horizon
Date: Tue, 2 May 2000 15:19:38 -0000
Reply-To: "Patrick" <[EMAIL PROTECTED]>

I understand your frustration.  The Compaq comes with a weird
Windows which will not work on another computer.  If I am not
mistaken, the installation of windows is not done in the "normal"
way - it's done using a "refresh" or "restore" disk which adds a
whole lot of other software as well as the drivers for keyboard,
modem ect - usually a huge install (takes FOREVER) because of all
the shit they add.  I have an HP which uses the same OS
installation method.  It says on the "restore" CD that it will
not work on another computer.  I found out (much to my chagrin,
that a format, then install a "normal" Windows, it does not work.
If I partitioned the HD and put the "restore" version of win on
the first part and a regular version on the second (just to test
things) everything works fine.  I believe there is something in
the BIOS which detects the presence of the HP version of Windows.
My roommate is the IT guy for a local company with a bunch of
Compaq's and he told me that the OS is quirky when trying to use
dual boots.



> I urge you to try install RHLinux on a Presario 5834 (or some
thing similar) to
> verify what I'm saying.
>
> Its not so much a conspiracy against Linux. But this is for
their profit, I guess.
>


------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.setup,comp.os.linux.x
Subject: Re: XFree86 4.0 rpms
Date: Tue, 02 May 2000 19:22:13 GMT

I'm certainly not guru, but I could swear I got the 4.0-0.6 rpm from
rawhide to install with an "Installation Complete" message.  My goal
has been to get my nvidia geforce to play quake III linux so I was
folling the nvidia driver faq when I installed it.  Then I ran
xf86config.  I have to manually put in "IMPS/2" for the mouse protocol
no matter what mouse I select during the running of xf86config so that
is kind of weird.  I haven't been able to get quake to go yet so maybe
it still isn't set up 100% correctly.

Kish

In article <[EMAIL PROTECTED]>,
  Martin Sanborn <[EMAIL PROTECTED]> wrote:
> Kerry Cox wrote:
>
> > caused a lot of things to break.  Has anyone had any success in
> > installing XFree86 on their own Linux machine using the RPMs?  And
if
> > so, would they be willing to share their experience?
>
> In my case, all the RPMs from rawhide seem to be ok EXCEPT for
> XFree86-4.0-0.x.i386.rpm. This package is broken. I've tried both the
4.0-0.6
> and 4.0-0.8 versions, and neither work. I think the error is akin to
"cpio:
> error file handle broken" or something of the sort.
>
> I plan on installing the binary packages from xfree86.org that
correspond to
> the files contained in XFree86-4.0-0.x.i386.rpm. Specifically, these
are
> Xman.tgz, Xmod.tgz, Xbin.tgz, Xlib.tgz, and Xetc.tgz. I won't install
the
> others since the rest of the XFree-4.0 RPMs (fonts, board-specific
server,
> docs, devel, extra libs) are all OK.
>
> I'll let you know how it goes.
>
> Marty
> [EMAIL PROTECTED]
>
>


Sent via Deja.com http://www.deja.com/
Before you buy.

------------------------------

From: Harlan Grove <[EMAIL PROTECTED]>
Subject: Re: KDE vs Gnome?
Date: Tue, 02 May 2000 12:21:05 -0700

Not that I'm particularly experienced with Linux, but if
you have experience with either Windows or MacOS, the
clipboard/copy&paste functionality in KDE will be closer to
what you expect than that in Gnome. That's about it aside
from aesthetics.

Well . . . I suppose you could come to rely on applications
that are specific to one or the other (eg, korganizer or
gpim), in which case you'll need KDE or Gnome libraries
even if you decide to use the other. So figure out what
software you want to use. If you don't need KDE- or Gnome-
specific applications, you could use something else with
more modest memory and storage requirements. If you have
sufficient storage, install both and switch back and forth,
maybe trying out something else too.


* Sent from AltaVista http://www.altavista.com Where you can also find related Web 
Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautiful

------------------------------

From: Madhusudan Singh <[EMAIL PROTECTED]>
Subject: Re: Need some help in choice of mail clients : A problem.
Date: Tue, 2 May 2000 15:36:52 -0400


I tried to install kmail. I did the following :
1. Installed qt (needed by kdelibs).
2. Configured kdelibs.

On trying to make it, I got the following error :

 8 ] kdelibs-1.1.2 -: make
make  all-recursive
make[1]: Entering directory `/z/chhabra/kde/kdelibs-1.1.2'
Making all in kdecore
make[2]: Entering directory `/z/chhabra/kde/kdelibs-1.1.2/kdecore'
/n/cello/z/chhabra/kde/qt/bin/moc ./kconfig.h -o kconfig.moc
/bin/sh ../libtool --silent --mode=compile g++ -DHAVE_CONFIG_H -I. -I.
-I.. -I/n/cello/z/chhabra/kde/qt/include     -O2 -Wall -c kconfig.cpp
/n/cello/z/chhabra/kde/qt/bin/moc ./kconfigbase.h -o kconfigbase.moc
/bin/sh ../libtool --silent --mode=compile g++ -DHAVE_CONFIG_H -I. -I.
-I.. -I/n/cello/z/chhabra/kde/qt/include     -O2 -Wall -c kconfigbase.cpp
kconfigbase.cpp: In method `const class QString
KConfigBase::readEntry(const char *, const char * = 0) const':
kconfigbase.cpp:382: no matching function for call to `QString::detach ()'
kconfigbase.cpp:394: `class QCharRef' used where a `int' was expected
kconfigbase.cpp: In method `void KConfigBase::writeEntry(const char *,
QStrList &, char = ',', bool = true, bool = false, bool = false)':
kconfigbase.cpp:894: call of overloaded `writeEntry(const char *&, QString
&, bool &, bool &, bool &)' is ambiguous
kconfigbase.cpp:808: candidates are: const char *
KConfigBase::writeEntry(const char *, const char *, bool = true, bool =
false, bool = false)
kconfigbase.h:543:                 const char *
KConfigBase::writeEntry(const char *, bool, bool = true, bool = false,
bool = false)
kconfigbase.h:561:                 const char *
KConfigBase::writeEntry(const char *, const QFont &, bool = true, bool =
false, bool = false)
kconfigbase.h:579:                 void KConfigBase::writeEntry(const char
*, const QColor &, bool = true, bool = false, bool = false)
kconfigbase.cpp: In method `const char * KConfigBase::writeEntry(const
char *, int, bool = true, bool = false, bool = false)':
kconfigbase.cpp:906: call of overloaded `writeEntry(const char *&, QString
&, bool &, bool &, bool &)' is ambiguous
kconfigbase.cpp:808: candidates are: const char *
KConfigBase::writeEntry(const char *, const char *, bool = true, bool =
false, bool = false)
kconfigbase.h:543:                 const char *
KConfigBase::writeEntry(const char *, bool, bool = true, bool = false,
bool = false)
kconfigbase.h:561:                 const char *
KConfigBase::writeEntry(const char *, const QFont &, bool = true, bool =
false, bool = false)
kconfigbase.h:579:                 void KConfigBase::writeEntry(const char
*, const QColor &, bool = true, bool = false, bool = false)
kconfigbase.cpp:907: warning: control reaches end of non-void function
`KConfigBase::writeEntry(const char *, int, bool, bool, bool)'
kconfigbase.cpp: In method `const char * KConfigBase::writeEntry(const
char *, unsigned int, bool = true, bool = false, bool = false)':
kconfigbase.cpp:918: call of overloaded `writeEntry(const char *&, QString
&, bool &, bool &, bool &)' is ambiguous
kconfigbase.cpp:808: candidates are: const char *
KConfigBase::writeEntry(const char *, const char *, bool = true, bool =
false, bool = false)
kconfigbase.h:543:                 const char *
KConfigBase::writeEntry(const char *, bool, bool = true, bool = false,
bool = false)
kconfigbase.h:561:                 const char *
KConfigBase::writeEntry(const char *, const QFont &, bool = true, bool =
false, bool = false)
kconfigbase.h:579:                 void KConfigBase::writeEntry(const char
*, const QColor &, bool = true, bool = false, bool = false)
kconfigbase.cpp:919: warning: control reaches end of non-void function
`KConfigBase::writeEntry(const char *, unsigned int, bool, bool, bool)'
kconfigbase.cpp: In method `const char * KConfigBase::writeEntry(const
char *, long int, bool = true, bool = false, bool = false)':
kconfigbase.cpp:930: call of overloaded `writeEntry(const char *&, QString
&, bool &, bool &, bool &)' is ambiguous
kconfigbase.cpp:808: candidates are: const char *
KConfigBase::writeEntry(const char *, const char *, bool = true, bool =
false, bool = false)
kconfigbase.h:543:                 const char *
KConfigBase::writeEntry(const char *, bool, bool = true, bool = false,
bool = false)
kconfigbase.h:561:                 const char *
KConfigBase::writeEntry(const char *, const QFont &, bool = true, bool =
false, bool = false)
kconfigbase.h:579:                 void KConfigBase::writeEntry(const char
*, const QColor &, bool = true, bool = false, bool = false)
kconfigbase.cpp:931: warning: control reaches end of non-void function
`KConfigBase::writeEntry(const char *, long int, bool, bool, bool)'
kconfigbase.cpp: In method `const char * KConfigBase::writeEntry(const
char *, long unsigned int, bool = true, bool = false, bool = false)':
kconfigbase.cpp:942: call of overloaded `writeEntry(const char *&, QString
&, bool &, bool &, bool &)' is ambiguous
kconfigbase.cpp:808: candidates are: const char *
KConfigBase::writeEntry(const char *, const char *, bool = true, bool =
false, bool = false)
kconfigbase.h:543:                 const char *
KConfigBase::writeEntry(const char *, bool, bool = true, bool = false,
bool = false)
kconfigbase.h:561:                 const char *
KConfigBase::writeEntry(const char *, const QFont &, bool = true, bool =
false, bool = false)
kconfigbase.h:579:                 void KConfigBase::writeEntry(const char
*, const QColor &, bool = true, bool = false, bool = false)
kconfigbase.cpp:943: warning: control reaches end of non-void function
`KConfigBase::writeEntry(const char *, long unsigned int, bool, bool,
bool)'
kconfigbase.cpp: In method `const char * KConfigBase::writeEntry(const
char *, double, bool = true, bool = false, bool = false)':
kconfigbase.cpp:954: call of overloaded `writeEntry(const char *&, QString
&, bool &, bool &, bool &)' is ambiguous
kconfigbase.cpp:808: candidates are: const char *
KConfigBase::writeEntry(const char *, const char *, bool = true, bool =
false, bool = false)
kconfigbase.h:543:                 const char *
KConfigBase::writeEntry(const char *, bool, bool = true, bool = false,
bool = false)
kconfigbase.h:561:                 const char *
KConfigBase::writeEntry(const char *, const QFont &, bool = true, bool =
false, bool = false)
kconfigbase.h:579:                 void KConfigBase::writeEntry(const char
*, const QColor &, bool = true, bool = false, bool = false)
kconfigbase.cpp:955: warning: control reaches end of non-void function
`KConfigBase::writeEntry(const char *, double, bool, bool, bool)'
kconfigbase.cpp: In method `const char * KConfigBase::writeEntry(const
char *, bool, bool = true, bool = false, bool = false)':
kconfigbase.cpp:970: call of overloaded `writeEntry(const char *&, QString
&, bool &, bool &, bool &)' is ambiguous
kconfigbase.cpp:808: candidates are: const char *
KConfigBase::writeEntry(const char *, const char *, bool = true, bool =
false, bool = false)
kconfigbase.cpp:962:                 const char *
KConfigBase::writeEntry(const char *, bool, bool = true, bool = false,
bool = false)
kconfigbase.h:561:                 const char *
KConfigBase::writeEntry(const char *, const QFont &, bool = true, bool =
false, bool = false)
kconfigbase.h:579:                 void KConfigBase::writeEntry(const char
*, const QColor &, bool = true, bool = false, bool = false)
kconfigbase.cpp:971: warning: control reaches end of non-void function
`KConfigBase::writeEntry(const char *, bool, bool, bool, bool)'
kconfigbase.cpp: In method `const char * KConfigBase::writeEntry(const
char *, const QFont &, bool = true, bool = false, bool = false)':
kconfigbase.cpp:999: warning: cannot pass objects of type `QString'
through `...'
kconfigbase.cpp:999: warning: format argument is not a pointer (arg 3)
kconfigbase.cpp:1001: call of overloaded `writeEntry(const char *&,
QString &, bool &, bool &, bool &)' is ambiguous
kconfigbase.cpp:808: candidates are: const char *
KConfigBase::writeEntry(const char *, const char *, bool = true, bool =
false, bool = false)
kconfigbase.cpp:962:                 const char *
KConfigBase::writeEntry(const char *, bool, bool = true, bool = false,
bool = false)
kconfigbase.cpp:977:                 const char *
KConfigBase::writeEntry(const char *, const QFont &, bool = true, bool =
false, bool = false)
kconfigbase.h:579:                 void KConfigBase::writeEntry(const char
*, const QColor &, bool = true, bool = false, bool = false)
kconfigbase.cpp:1002: warning: control reaches end of non-void function
`KConfigBase::writeEntry(const char *, const QFont &, bool, bool, bool)'
kconfigbase.cpp: In method `void KConfigBase::writeEntry(const char *,
const QColor &, bool = true, bool = false, bool = false)':
kconfigbase.cpp:1054: call of overloaded `writeEntry(const char *&,
QString &, bool &, bool &, bool &)' is ambiguous
kconfigbase.cpp:808: candidates are: const char *
KConfigBase::writeEntry(const char *, const char *, bool = true, bool =
false, bool = false)
kconfigbase.cpp:962:                 const char *
KConfigBase::writeEntry(const char *, bool, bool = true, bool = false,
bool = false)
kconfigbase.cpp:977:                 const char *
KConfigBase::writeEntry(const char *, const QFont &, bool = true, bool =
false, bool = false)
kconfigbase.cpp:1050:                 void KConfigBase::writeEntry(const
char *, const QColor &, bool = true, bool = false, bool = false)
make[2]: *** [kconfigbase.lo] Error 1
make[2]: Leaving directory `/z/chhabra/kde/kdelibs-1.1.2/kdecore'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/z/chhabra/kde/kdelibs-1.1.2'
make: *** [all-recursive-am] Error 2

What's wrong ?


Thanks in advance,

Madhusudan Singh.








On 2 May 2000, Robie Basak wrote:

> On Mon, 1 May 2000 22:27:35 -0400, Madhusudan Singh said:
> >Hi
> >     I have a university account on a Debian (potato) system. I read my
> >email currently using pine. However, for entirely non-technical reasons, I
> >wish to be able to install a GUI based mail client in my own login area. I
> >do not have or can acquire super user privileges for installation /
> >running of the mail client. 
> 
> No, you don't need super-user priviledges to install any program, in
> general (except su or something :-)
> 
> >     My local system is a Solaris machine, and my mail boxes are
> >located on the remote Debian machine. Since I wish to process my mail
> >entirely on the remote server with a setenv DISPLAY kind of procedure on
> >the remote machine, I will have to install the mail client on the remote
> >machine. 
> >     Any ideas about the choice of a mail client ? I want it be
> >functional like kmail (installation of KDE is impossible as parts of it
> >require super user privileges).
> 
> No it doesn't.
> 
> Install from source, configure using:
>   ./configure --prefix=~/kde
> then
>   make && mkdir ~/kde && make install.
> 
> You only need kdelibs and kdenetwork, AFAIK. You don't even need
> kdenetwork if you get kmail from http://devel-home.kde.org/~kmail
> 
> HTH,
> Robie.
> 


------------------------------

From: [EMAIL PROTECTED] (Ray)
Crossposted-To: comp.os.linux.networking
Subject: Re: X locks up solid, what can I do ?! HELP !!!
Date: Tue, 02 May 2000 19:46:34 GMT

On Tue, 02 May 2000 10:28:59 GMT, [EMAIL PROTECTED]
 <[EMAIL PROTECTED]> wrote:
>In article <[EMAIL PROTECTED]>,
>  Dave Phillips <[EMAIL PROTECTED]> wrote:
>> Greetings:
>>
>> Apr 29 15:44:04 localhost pppd[5601]: Connect: ppp0 <--> /dev/ttyS3
>> Apr 29 15:44:13 localhost kernel: PPP BSD Compression module
>registered
>> Apr 29 15:44:13 localhost kernel: PPP Deflate Compression module
>> registered
>> Apr 29 15:44:13 localhost pppd[5601]: local  IP address 209.143.26.110
>> Apr 29 15:44:13 localhost pppd[5601]: remote IP address 209.143.26.103
>> Apr 29 15:44:14 localhost modprobe: no dependency information for
>> module: "/d
>> ev/ttyS3"
>>

Well, somehow Dave has managed to convince his system that /dev/ttyS3 is a
module?!  Time to check /etc/conf.modules (or modules.conf if that's what
it's called on his system).  

-- 
Ray

------------------------------

From: [EMAIL PROTECTED]
Subject: PCMCIA modem
Date: Tue, 02 May 2000 19:41:39 GMT

I have a regular desktop but accidentally bought a pcmcia modem because
I wanted a non-software driven modem. However, I realized that pcmcia
modem is made for labtops. Is it possible that my computer has a PCMCIA
port or something, or, if not, is it possible to get one for a desktop,
not a labtop?


Sent via Deja.com http://www.deja.com/
Before you buy.

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.misc) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Misc Digest
******************************

Reply via email to