Linux-Development-Sys Digest #623, Volume #7 Fri, 25 Feb 00 06:13:09 EST
Contents:
interrupt handler not being called . (Nilesh Patel)
Re: problem with processing speed on i486 (Tim Roberts)
Re: glibc development language ("tye4")
Re: Binary compatibility: what kind of crack are they smoking? (Eric Leblanc)
interrupt handler not called ( continued ) (Nilesh Patel)
Re: Binary compatibility: what kind of crack are they smoking? (Arthur)
Re: Want to work with OSS for a living? (MA) (Greystoke)
Re: (Q) Whatever happened to kerneld? (Villy Kruse)
Re: RedHat 6.0 (Anders Larsen)
Re: Debugging application using pthread (Ralf Render)
Suspicious message from IDE driver (Francesc Oller)
Re: Linux and DVD (Anders Larsen)
Re: System hanging with SMP-Kernel 2.2.13 (SuSE6.3)? ([EMAIL PROTECTED])
Re: Bluetooth (Rolf Magnus)
Re: glibc development language (Anders Larsen)
memory allocation . (nilesh patel)
----------------------------------------------------------------------------
From: Nilesh Patel <[EMAIL PROTECTED]>
Subject: interrupt handler not being called .
Date: Fri, 25 Feb 2000 11:35:00 +0530
hi ,
there is an ISR which is being registered for a specific IRQ .
The interrupt has been registered and a
shared IRQ is being used . however there is no other device using this
irq . The hardware has been properly
initialised , we are getting an irq line , but the interrupt handler is
not being called . The interrupt handler
is to be called when a certain buffer gets full . but once the buffer
gets full , the kernel hangs . Please let know
the cause for this . Again , do we have to call a enable_irq explicitly
..
summing up ,
why is the handler not being called ?
do reply back at the earliest .
thanks,
raj.
------------------------------
From: Tim Roberts <[EMAIL PROTECTED]>
Subject: Re: problem with processing speed on i486
Date: Fri, 25 Feb 2000 06:24:06 GMT
[EMAIL PROTECTED] wrote:
>
>there's no problem ... just don't compare clocks of different architectures
>i think alpha 50MHz is faster than pentium 200 ...
Quite the contrary, actually. Many things which take one instruction on a
Pentium require several on an Alpha. In the comparisons we did, an Alpha
at 100MHz ran algorithms at roughly the same speed as a Pentium at 75MHz.
--
- Tim Roberts, [EMAIL PROTECTED]
Providenza & Boekelheide, Inc.
------------------------------
From: "tye4" <[EMAIL PROTECTED]>
Subject: Re: glibc development language
Date: Thu, 24 Feb 2000 13:25:55 -0800
Christopher Browne <[EMAIL PROTECTED]> wrote in message
news:bM0t4.37328$[EMAIL PROTECTED]...
> Centuries ago, Nostradamus foresaw a time when tye4 would say:
> >The GNU guidelines in http://www.gnu.org/prep/standards.html
> >state that it is better to use only C for glibc development.
> >I've been developing C++ code for glibc. Is this a strict requirement
> >or is it okay to use C++ for glibc
>
> I think you're confused.
>
> Only C is used to develop GLIBC, because GLIBC is a C-oriented
> library. It might be well and nifty to write portions of GLIBC in
> Intercal or Emacs Lisp; that would *not* be a good thing for anyone
> that intends to actually deploy GLIBC.
>
I'm not confused. C++ can indeed be used to develop libraries for C
programmers.
extern "C"
{
void c_func1(int foo, int bar);
}
C++ is a standard for all these years. I don't quite understand the
reluctance in using C++ for system development in Linux.
> The material in the "GNU Coding Standards" doesn't seem to say what
> you claim it says.
>
> Quoting:
> "When you want to use a language that gets compiled and runs at high
> speed, the best language to use is C. Using another language is
> like using a non-standard feature: it will cause trouble for
> users. Even if GCC supports the other language, users may find it
> inconvenient to have to install the compiler for that other
> language in order to build your program. For example, if you write
> your program in C++, people will have to install the GNU C++
> compiler in order to compile your program."
>
> That isn't saying anything about libraries; that's saying something
> about which *LANGUAGE* they suggest using.
>
> The recommendation is to use C, and while there might be disagreement
> on some things, the reading is fairly clear.
According to the "Gnu coding standards", the problem with C++ is that
somebody installing glibc may not have a C++ compiler, thereby making it
"incovenient" for them to install glibc. That's strange because anybody
having the GNU gcc compiler is very likely to have the g++ compiler
installed too.
The "C++ slower than C" argument is quite old - dating back to the early
nineties. This was when most programming shops had switched from assembly to
C. However, C++ is quite ubiquitous now. So why is it not used in Linux? I
think it is easier to use an OO language to develop large complex systems
rather than an old structured prog. lang. like C. The "overhead" of C++ is
in the imagination of the critics and not real.
Most programmers use C++ or Java nowadays.
tye4
------------------------------
From: [EMAIL PROTECTED] (Eric Leblanc)
Crossposted-To: comp.os.linux.advocacy,comp.os.linux.setup
Subject: Re: Binary compatibility: what kind of crack are they smoking?
Date: Fri, 25 Feb 2000 06:56:24 GMT
Donovan Rebbechi <[EMAIL PROTECTED]> wrote:
>On 25 Feb 2000 03:10:34 GMT, Colin Watson wrote:
>
>>Qt and KDE don't ship with all distributions, by the way. In particular,
>>Debian won't include them because of licensing issues (the QPL has fatal
>>incompatibilities with the GPL).
>
>They don't ? Hmmm ...
Debian ship Qt2 but not KDE.
--
Eric Leblanc <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Departement de Mathematique % Univ. du Quebec a Montreal, Montreal, Qc
Anyone who is capable of getting themselves made President should on no
account be allowed to do the job.
-- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"
------------------------------
From: Nilesh Patel <[EMAIL PROTECTED]>
Subject: interrupt handler not called ( continued )
Date: Fri, 25 Feb 2000 12:31:53 +0530
hi,
this is in continuation of the earlier question. does a bottom handler
have to call a disable_irq and a enable_irq
explicitly . We are also using task queues .
thanks,
nilesh.
------------------------------
From: Arthur <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy,comp.os.linux.setup
Subject: Re: Binary compatibility: what kind of crack are they smoking?
Date: Thu, 24 Feb 2000 22:57:56 -0800
Reply-To: [EMAIL PROTECTED]
Albert Ulmer wrote:
> Adam Ierymenko wrote:
> > > There is no such thing as a Linux OS! There is RedHat Linux,
> > > SUSE-Linux, debian Linux, and lots of other. Face it, Linux already
> > > has fragmented.
> > Actually, if all the distros would just standardize on one
> > package manager format, it would be OK. Right now it's
> > RPM and DPKG... or maybe make DPKG and RPM able to
> > install each others' packages?
> But they already are! Search freshmeat.net for alien.
kpackage (in KDE) is also supposed to work with RPM's
DEB's, FreeBSD packages and Slackware packages. I've
only done RPM's, so I can't comment on how well this
works, but I believe it calls the rpm or dpkg utilities
so I'd expect it does OK.
Arthur
------------------------------
From: Greystoke <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy,comp.os.linux.development.apps
Subject: Re: Want to work with OSS for a living? (MA)
Date: Fri, 25 Feb 2000 02:22:04 -0500
On Feb 24, Joseph T. Adams spake the following:
: In comp.os.linux.advocacy mlw <[EMAIL PROTECTED]> wrote:
: : I am currently working at a net service company. We need "web guys" you
: : should know some C/C++, but mostly we need UNUX Admin (Freebsd), Apache,
: ^^^^
:
: Might I suggest the addition of ispell? :)
:
: (Sorry, couldn't resist. I'm the same way when I'm in a major hurry,
: which is most of the time.)
:
:
: : PHP, Perl, and the ability to rip apart poorly written (app generated)
: : customer HTML, and make it pretty, functional, and problem free.
:
: I would love to do something like this if I were just a bit more
: qualified and lived closer.
:
: Unfortunately I spend most of my days fixing NT/VB messes - usually by
: writing more and hopefully better VB code, not by migrating to
: standards-based solutions which are the kind I'd usually prefer - and,
: thus, I don't get a whole lot of time to keep my Unix skills current.
:
: My dream job though would be architecting and designing
: standards-based solutions, and building components to fill voids in
: the large, growing, but still not yet perfect arsenal of tools
: available to Free Software developers for building best-of-breed
: applications.
Sounds like a prospective IEEE employee! ;^)
: : Reply to my e-mail directly.
:
: : Sorry to post this on the discussion groups, but we have been looking
: : for people for months and the normal channels are not working, and this
: : is a form of advocacy, right?
:
: : The company is in Westborough Massachusetts.
:
:
: I know it's tough to find qualified people right now. Hopefully that
: will change some over time.
Already is. (worked for company this summer programming linux drivers)
#!/usr/bin/perl
@a=(Lbzjoftt,Inqbujfodf, Hvcsjt); $b="Lbssz Wbmm" ; $b =~ y/b-z/a-z/ ; $c = " Tif ".
@a ." hsfbu wj" ."suvft pg b qsphsbnnfs" . ":\n"; $c =~y/b-y/a-z/; print"\n\n$c ";
for($i=0; $i<@a; $i++) { $a[$i] =~ y/b-y/a-z/; if($a[$i]eq$a [-1]) {print"and $a[$i]."
; }else{ print"$a[$i], "; }}print"\n\t\t--$b\n\n";
------------------------------
From: [EMAIL PROTECTED] (Villy Kruse)
Subject: Re: (Q) Whatever happened to kerneld?
Date: 25 Feb 2000 08:05:25 GMT
On 24 Feb 2000 18:07:45 -0500, Paul Kimoto <[EMAIL PROTECTED]> wrote:
>In article <893tfg$140u$[EMAIL PROTECTED]>, Timothy Murphy wrote:
>> How are modules loaded automatically in kernel 2.2.14 ?
>> I chose autoloading when compiling the kernel,
>> and expected to find kerneld or kmod running,
>> but neither appear to be, although both are on the system.
>
>kerneld(8) should not be running. kmod is part of the kernel
>and does not appear as a separate process.
>(Cf. /usr/src/linux/Documentation/kmod.txt.)
>
Also check /usr/src/linux/Documentation/Changes for description of this
and other changes. In fact the files in /usr/src/linux/Documentation
will answer questions you didn't even know you had.
Villy
------------------------------
From: Anders Larsen <[EMAIL PROTECTED]>
Subject: Re: RedHat 6.0
Date: Fri, 25 Feb 2000 09:24:40 +0100
Sake wrote:
>
> Hi there,
>
> Given the popularity of RedHat Linux, there probably should be a RedHat
> group.
> Anyway, I'll use this for now.
>
> Problem that I have is that, cat on /proc files and 'dmesg' both show 64MB
> of RAM although
> my machine is equipted with 256MB of RAM. I'm using RedHat 6.0 fresh out of
> box.
>
> Where is my memory ?? :(
>
> Any hints are appreciated.
Your BIOS seems to be broken and only reports 64M of RAM (this is
actually
not uncommon, even today).
Try adding an
append="mem=256M"
line to lilo.conf
--
Anders Larsen
------------------------------
From: Ralf Render <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Debugging application using pthread
Date: Fri, 25 Feb 2000 10:20:25 +0100
Coult you tell me what version of gdb/glib I need and where to find it?
Thanks.
Fabrice Peix <[EMAIL PROTECTED]> schrieb in im Newsbeitrag:
[EMAIL PROTECTED]
> Ralf Render wrote:
> >
> > Hi,
> >
> > does anybody know how to debug applications after calling
> > pthread_create()?
> > My problem is that after calling pthread_create() the debugger (kdebg,
> > gdb) displays the message: "Program received signal ?, Unknown signal".
> > After that no further debugging is possible.
> > Maybe the reasons are the new PIDs created by the pthread library.
> > Who knows can help?
> >
> > Thanks Ralf.
> The problim is that libpthread use SIGUSR1 and SIGUSR2 for internal
> management,
> so without the patch of gdb, when you debug your program and a signal is
> cautch
> gdb stop your program.
> An other solution is to ignore the signal SIGUSR1 and SIGUSR2 but to
> debug new thread
> you must attach gdb to it(in fact thread in linux are "pseudo"
> process.(clone syscall).
------------------------------
From: Francesc Oller <[EMAIL PROTECTED]>
Subject: Suspicious message from IDE driver
Date: Fri, 25 Feb 2000 10:36:14 +0100
Reply-To: [EMAIL PROTECTED]
Hi all!
After installing GNU/Linux Debian 2.1r4 I get the following message very
often:
hda: status timeout: status=0xd0 {Busy}
hda: no DRQ after issuing WRITE
ide0: reset: success
hda is a 13GB UDMA ide HD connected to the master ide0
What is this about?
regards
Francesc Oller
------------------------------
From: Anders Larsen <[EMAIL PROTECTED]>
Subject: Re: Linux and DVD
Date: Fri, 25 Feb 2000 10:20:36 +0100
Shazam wrote:
>
> On Luxsonor's website is the following:
>
> ****************************
> LuxSonor does not have the resources or even the proper people to do a port
> to Windows NT 2000 anymore.
> We have not been in the PC business for about 2 years. We have tried to
> outsource our Windows 2000 driver port to people that did the previous ports
> before. Unfortunately, no reasonable agreement could be arranged.
> The best we can do is release our source code to the public.
> ****************************
>
> This is bad news and great news at the same time! Bad news in that I was
> looking forward to Windows 2000 drivers for our Luxsonor based DVD cards
> (ie. CT7160, Labway, Procomp M410 etc). Great news in that Luxsonor has
> decided to give us users the greatest gift of all: Open Source Drivers.
>
> This means that if someone out there is smart enough (and there are a lot of
> smart coders out there), we can expect to see continued Windows 98 driver
> support for Luxsonor based DVD decoder cards! In addition, we can expect to
> see Linux and Windows 2000 drivers for our cards too.
Don't expect a free Windoze 2000 driver - I quote the following excerpts
from the Risks Digest 20.81 (news:comp.risks):
"Microsoft (hereinafter MS) Windows 2000 has a kind of "immune system"
feature which causes it to reject any driver or DLL update which has not
been digitally signed by Microsoft. The signature system looks to be
similar to Authenticode."
"Well, if you want to supply a new device driver (say, for a variant
peripheral) or library update (adding, say, some spiffy cryptographic
features) for Windows 2000, you must give your code to MS for early review
and pay MS a fee. If you do these things, MS may sign your software. If
you do not, then no Windows 2000 machine will run your code (or at least,
not without big trouble, too big for non-techies).
As with Authenticode, MS' scheme is not unbreakable, nor does it even
attempt to assure the quality (as opposed to the provenance) of signed code.
(Oh, MS says their lab will review 3rd-party code for "compatibility," but
they won't check for malware, and unlike, say, Java's sandbox, MS signature
scheme has no inherent malware-inhibiting qualities).
MS marketing will stop at nothing, Q.E.D..
Mark Seecof"
MS wants to see your source code! Well, with open source, thats a
legitimate request - but do we really expect MS to honour the GPL?
No hint as to how much the fee amounts to, however.
> Let's give Luxsonor a big hand of applause for supporting its customers in
> such a fashion! There are a lot of companies out there who wouldn't do
> this.
Nod.
--
Anders Larsen
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: System hanging with SMP-Kernel 2.2.13 (SuSE6.3)?
Date: Fri, 25 Feb 2000 10:16:09 GMT
> I have SuSE 6.3 running on my PPro SMP system.
Works well and I have had
> not hangup or system related problems at all.
This problem could also happen on your system, if
one tries to run
database searches over NFS-mounted filesystems.
I've got several systems
[2x PII 400] running with SuSE 6.1 or 6.2 or 6.3.
They're usually OK, running
without any sign of problems or hanging. But
sometimes as soon as the database
search is started, the hanging will happen. Do you
happen to know the
BLAST program [see:
ftp://ncbi.nlm.nih.gov/blast/]? This program
is actually the database search program which
searches against a biological
FASTA database and finds out the hits for a query
sequence. The hanging
problem didn't occure if I runs it against a local
copy of the database.
Running against a copy in a NFS-mounted directory
causes the hanging.
The database size in our environment is usually
huge: several hundreds hundreds
of MB. And a search on a 4 x Xeon Linux server
usually takes 10 - 20 sec.
It means these huge amount of data have to be
transfered over NFS. This is the reason why I
think it might be related to NFS.
>> We've got a problem with this kernel on a
Dell's PowerEdge 6350
>> system [4 x PIII Xeon 550MHz, 2GB EDO DIMM RAM,
Intel's Ether DualPort
Pro100+]:
>> it hangs sometimes.
> I suspect its your motherboard, CPU's or memory.
But as I don't have Xeon's
> I can't help you other than run a "top" in a
window with 1 sec slice and
> see if that gives you the cause or the
memory/cpu hog process.
>
> I'd bet is h/w problems.
I doubt this. At first I thought about this too.
Memory checking didn't
show any sign of problems. I've also heard about
this hanging problem
from other sites.
>> The /var/log/messages file didn't show any
hints about what caused the
hanging.
>> Usually the system could only be reusable after
rebooting (press reset-button)
>> again (it didn't respond to pings during the
hanging or anything else,
>> i.e.: no telnet, no ftp-> a total k.o. :-<].
>>
>> At first, I've checked the web site:
www.kernelnotes.org and found that the
>> kernel-developers are quite busy with the
kernel-updatings. The newest stable
>> At first, I've checked the web site:
www.kernelnotes.org and found that the
>> kernel-developers are quite busy with the
kernel-updatings. The newest stable
>> kernel version should be 2.2.14 . But I've
still got some doubts that even
>> this latest kernel version can help us out, as
the problem seems to be related
>> to the NFS behaviour of the kernel and the
NFS-related fixes are still
appearing
>> in the latest development kernels. Can someone
confirm this NFS-related
>> (in-)stability point in regards of
SMP-operations? The hangings appeared freq.
if
>> NFS-filesystems were intensivly used (~ 200MB
data in several sec. over NFS).
>>
> My system is supporting 4 systems which are
masqueraded IP wise on a 100/10
> Base T hub and noone has experienced problems.
> I am aware that the upcoming 2.4 kernel will NFS
performance improvements
> and a little bug fixing but NFS is sound. SMP -
Spinlocks have been an issue
> only in 2.0/2.1 but I haven't experienced any
issues under 2.2.13/14.
> I am aware that others have had issues with Xeon
CPU's and motherboards
> before, see www.progsoc.uts.edu.au/lists/slug
mailinglist archives for
> more on this.
> Cheers, Grahame
> Cheers, Grahame.
> --
> SLUG (Sydney Linux User Group) www.slug.org.au
Thanks for your kind posting anyway.
Your pointed web-site contains certainly a lot of
Linux-related stuff,
but I'm missing a search engine to go through it.
I didn't find Xeon-related
stories there. Sorry.
Cheers,
--
regards,
Yan
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Rolf Magnus <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Bluetooth
Date: Fri, 25 Feb 2000 11:31:33 +0100
Reply-To: "Rolf Magnus" <[EMAIL PROTECTED]>
Oliver Meili schrieb...
>> Do you have any details/URL's ?
>
>Take a look at http://sscwww.epfl.ch/~omeili/bluetooth
or at http://developer.axis.com/software/bluetooth/
Rolf Magnus
------------------------------
From: Anders Larsen <[EMAIL PROTECTED]>
Subject: Re: glibc development language
Date: Fri, 25 Feb 2000 11:38:03 +0100
tye4 wrote:
>
> Christopher Browne <[EMAIL PROTECTED]> wrote in message
> news:bM0t4.37328$[EMAIL PROTECTED]...
> > Centuries ago, Nostradamus foresaw a time when tye4 would say:
> > >The GNU guidelines in http://www.gnu.org/prep/standards.html
> > >state that it is better to use only C for glibc development.
> > >I've been developing C++ code for glibc. Is this a strict requirement
> > >or is it okay to use C++ for glibc
> >
> > I think you're confused.
> >
> > Only C is used to develop GLIBC, because GLIBC is a C-oriented
> > library. It might be well and nifty to write portions of GLIBC in
> > Intercal or Emacs Lisp; that would *not* be a good thing for anyone
> > that intends to actually deploy GLIBC.
> >
> I'm not confused. C++ can indeed be used to develop libraries for C
> programmers.
> extern "C"
> {
> void c_func1(int foo, int bar);
> }
The problem with this is, if your c_funct1 really uses C++, some, if not all,
implementations would require main() to be compiled with C++ in order to properly
initialize the C++ run-time environment.
That is, using C++ within glibc might very well require *all* applications to be
compiled with C++; some are certain to break, but OTOH, C++ barfs at a lot of
programming errors which passes undetected through C
> C++ is a standard for all these years. I don't quite understand the
> reluctance in using C++ for system development in Linux.
[snip]
> According to the "Gnu coding standards", the problem with C++ is that
> somebody installing glibc may not have a C++ compiler, thereby making it
> "incovenient" for them to install glibc. That's strange because anybody
> having the GNU gcc compiler is very likely to have the g++ compiler
> installed too.
We don't all have 10+Gb disc drives...
> The "C++ slower than C" argument is quite old - dating back to the early
> nineties. This was when most programming shops had switched from assembly to
> C. However, C++ is quite ubiquitous now. So why is it not used in Linux? I
> think it is easier to use an OO language to develop large complex systems
> rather than an old structured prog. lang. like C. The "overhead" of C++ is
> in the imagination of the critics and not real.
Oh, the speed difference is real - even if it's quite small.
The difference just might turn out to be significant.
Also, C++ tends to require more code space - tell that to the guys who are trying to
*reduce* the footprint of Linux for small, embedded systems.
> Most programmers use C++ or Java nowadays.
Agree, but that doesn't justify *forcing* the rest to use C++ instead of vanilla C.
--
Anders Larsen
------------------------------
From: nilesh patel <[EMAIL PROTECTED]>
Subject: memory allocation .
Date: Fri, 25 Feb 2000 16:40:32 +0530
hi ,
how do you allocate a 64 K contiguous real memory for PCI
devices ?
do reply fast ,
thanks ,
nilesh .
------------------------------
** 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.development.system) 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-Development-System Digest
******************************
