Linux-Development-Sys Digest #617, Volume #6 Mon, 12 Apr 99 16:14:14 EDT
Contents:
Re: Linux NFS server, Solaris cient, bad news ... (mlw)
Linux Servers, what to buy? (Scott Mayberry)
Re: ISR: Kernel->User space call (Joe Pfeiffer)
Re: Redhat Linux L10N (Changwoo Ryu)
Re: Linux NFS server, Solaris cient, bad news ... (Manfred Hollstein)
Re: script for .procmailrc (David T. Blake)
Re: MPEG player source code for Linux? (David T. Blake)
Re: What is ia32? (Fergus Henderson)
fbcon/S3 Virge (David L. Bilbey)
Re: What is ia32? (Frank Sweetser)
Re: SIGCHLD and zombie (Villy Kruse)
Re: CodeWarror for Linux (was: Re: Programming tools for ...) (MW Ron)
Re: Compiling for x86 CPUs (Was: ... seperate "i686" tree for Redhat ...) (Urs
Thuermann)
Re: kernel_thread()'s become zombies ("B. James Phillippe")
Re: threads and C++ exceptions (Rimas)
a problem with scanf (Francesc Oller)
Re: meminfo and ps (Nix)
----------------------------------------------------------------------------
From: mlw <[EMAIL PROTECTED]>
Crossposted-To: matrix.lists.linux.kernel
Subject: Re: Linux NFS server, Solaris cient, bad news ...
Date: Mon, 12 Apr 1999 17:03:30 +0000
Leslie Mikesell wrote:
>
> In article <[EMAIL PROTECTED]>,
> mlw <[EMAIL PROTECTED]> wrote:
> >Leslie Mikesell wrote:
> >>
> >> In article <[EMAIL PROTECTED]>,
> >> <[EMAIL PROTECTED]> wrote:
> >> >I've got my home directory on a Linux box, running Redhat 5.2, kernel
> >> >2.2.5, and the appropriate Redhat 2.2 patches. It's mounted on a
> >> >Solaris 2.5.1 box, and I try to configure and compile gcc.
> >> >
> >> >During the configure process, I get write error failures writing to
> >> >files, either creating the spec.h file at the end of configure, or cc
> >> >complains about not being able to create executables during
> >> >configure. A couple of times, ex started up for some reason, and once,
> >> >a .h file in the parent directory got overwritten by an object file.
> >> >
> >> >When it failed on the spec.h file, the file was created with 0 length,
> >> >it was owned by me, mode 644, (ls on server and client) but the client
> >> >system bechaved as if it was owned by some other user.
> >> >
> >> >I tried 2.0.36, 2.2.4-ac1, and 2.2.5 on the server, and two Solaris
> >> >clients running 2.5.1 and 2.6
> >> >
> >> >If no-one's seen (and fixed) this already, I'll turn on NFSD_DEBUG and
> >> >try to get some data next week.
> >>
> >> I think the only thing that even has a chance of interoperating
> >> correctly with non-linux systems is kernel 2.2.3 and patches
> >> included in knfsd-1.2.2. It looks like there may be a new
> >> version just out for 2.2.5 but I haven't tried to install it
> >> yet. See ftp://ftp.varesearch.com/pub/support/hjl/knfsd/.
> >> Also, there are some rpm updates in
> >> ftp://ftp.varesearch.com/pub/support/hjl/linux-2.2/RPMS/i386/
> >> but I'm not sure if they need 2.2.3 or will also work with
> >> the new patches for 2.2.5.
> >>
>
> >Sorry guys, 2.2.5 doesn't work either.
> >I have seen this very problem. It seems as though when a file is
> >created,deleted, then mkdir creates a directory, on NFS fom solaris. The
> >Solaris box refuses to think the directory is a directory.
> >
> >I would love to see this fixed, I got people giving me sh$t about it.
>
> Is this with or without the patches I mentioned?
>
> Les Mikesell
> [EMAIL PROTECTED]
Wouldn't patches for nfsd in the 2.2.3 kernel be in the 2.2.5 kernel?
--
Mohawk Software
Windows 95, Windows NT, UNIX, Linux. Applications, drivers, support.
Take the Mohawk Software Computer Survey at: www.mohawksoft.com
------------------------------
From: Scott Mayberry <[EMAIL PROTECTED]>
Subject: Linux Servers, what to buy?
Date: Mon, 12 Apr 1999 17:20:21 +0000
I've been assigned the task of deciding what hardware to buy
for a Linux server for a small company of 15 people. They
would like a large tape backup, RAID, and capability to add
a second processor if needed. I was looking at the DELL
PowerEdge Servers. Is anyone successfully running Linux
on one of these machines? Specifically, will the RAID
controller that comes in them work under Linux?
If anyone has some other suggestions for an economical
Linux server please respond! =)
--
Scott Mayberry
[EMAIL PROTECTED]
------------------------------
From: Joe Pfeiffer <[EMAIL PROTECTED]>
Subject: Re: ISR: Kernel->User space call
Date: 12 Apr 1999 11:02:41 -0600
Joe Pfeiffer <[EMAIL PROTECTED]> writes:
> Milos Dedecek <[EMAIL PROTECTED]> writes:
>
> > I'm writing a kernel space device driver.
> > In my interrupt service routine (kernel space) I want to notify user's
> > programm, that the data has arrived. How can I do this?
> >
> > I want the user to register a function (in user space), which will be
> > than called from my ISR. Is this possible? Or is there another way?
> > Semaphores etc.?
I was asleep when I wrote at least part of my previous response. No,
your driver can't call a user-level function (that part was right).
But if you open your device asynchronously, a SIGIO signal will get
delivered to your program when data comes available, and you can write
a handler that will get called when that occurs. This sounds like
exactly what you want to do.
--
Joseph J. Pfeiffer, Jr., Ph.D. Phone -- (505) 646-1605
Department of Computer Science FAX -- (505) 646-1002
New Mexico State University http://www.cs.nmsu.edu/~pfeiffer
------------------------------
From: Changwoo Ryu <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.questions
Subject: Re: Redhat Linux L10N
Date: 13 Apr 1999 00:40:04 +0900
Song Yang <[EMAIL PROTECTED]> writes:
> Are there Localized versions/extensions of Redhat distribution in
> Chinese, Korean, German or French?
A Korean localized dist, called `Alzza', is very popular among the
Korean RedHat users.
<ftp://ftp.bora.net/pub/Linux/alzza/>
--
Changwoo Ryu
------------------------------
From: [EMAIL PROTECTED] (Manfred Hollstein)
Crossposted-To: matrix.lists.linux.kernel
Subject: Re: Linux NFS server, Solaris cient, bad news ...
Date: 12 Apr 1999 17:49:11 +0200
Reply-To: Manfred Hollstein <[EMAIL PROTECTED]>
[EMAIL PROTECTED] (Leslie Mikesell) writes:
> In article <[EMAIL PROTECTED]>,
> David T. Blake <[EMAIL PROTECTED]> wrote:
> >mlw <[EMAIL PROTECTED]> writes:
> >
> >>Sorry guys, 2.2.5 doesn't work either.
> >>I have seen this very problem. It seems as though when a file is
> >>created,deleted, then mkdir creates a directory, on NFS fom solaris. The
> >>Solaris box refuses to think the directory is a directory.
> >>
> >>I would love to see this fixed, I got people giving me sh$t about it.
> >
> >
> >http://sunsolve.Sun.COM/pub-cgi/us/pubpatchpage.pl
> >might help. All releases of Solaris have nfs patches
> >available. The standard Solaris release nfs has bugs
> >that make Sun server:linux client not work quite
> >right.
> >
> >Note: This may or may not solve your problem, but it
> >would be the first thing to verify - that the Sun NFS
> >patches are applied.
>
> It isn't just Solaris, though. My problems are with freebsd
> clients and a linux server, and they seem to be fixed with
> the 2.2.3 patches except for the quirk that I get an error
> when trying to mount a remote filesystem in it's relative location
> on another mounted filesystem (i.e. mounting /n/machine, then
> /n/machine/home). Still haven't tried the 2.2.5 version.
I got similar problems with a virgin 2.2.5 kernel based NFS server;
once I activated CONFIG_NFSD_SUN all trouble has gone.
>
> Les Mikesell
> [EMAIL PROTECTED]
Later,
manfred
--
Manfred Hollstein If you have any questions about GNU software:
EMAIL: <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
WWW: <http://home.t-online.de/home/manfred-h/>
PGP: <http://home.t-online.de/home/manfred-h/manfred.hATgmx.net.asc>
------------------------------
From: [EMAIL PROTECTED] (David T. Blake)
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.help,comp.os.linux.misc
Subject: Re: script for .procmailrc
Date: 12 Apr 1999 07:54:10 -0700
"George Macario" <[EMAIL PROTECTED]> writes:
>I have a shell account on the Linux system of my university,
>but I'm not a Linux expert. I'd like to know if procmail can...
>- ...leave, first of all, a local copy of all mail that arrive to my
>address, and...
>- ...using split and formail, divide only messages smaller than
>5 kb into smaller messages of, at most, 160 characters, add
>to each new message "date", "from" and "subject" headers
>of the mail which was divided and forward all messages
>obtained to another address.
>To do this, I need a script for the file .procmailrc; anyone could
>write it for me?
I would suggest that this is a job for Perl, and
would require about 10 lines of code and a proper
entry in the .forward file.
Try man perl.
--
Dave Blake
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (David T. Blake)
Subject: Re: MPEG player source code for Linux?
Date: 12 Apr 1999 07:51:37 -0700
Andrea Borgia <[EMAIL PROTECTED]> writes:
>On 10 Apr 1999 01:54:01 -0400,
>in article <[EMAIL PROTECTED]>,
>[EMAIL PROTECTED] (Adam P. Jenkins) wrote:
>
>
>>mpeg players, and you'll find a bunch. Do a keyword search for
>>"mpeg". xanim is probably the most common mpeg player on Linux. For
>>DVD try MpegTV.
>
>xanim does not work with most of the mpegs I find... be it that
>they're windows-made or just that xanim is lagging behind in
>supporting the newer formats, imho mpegtv is the only viable choice
>for playing mpegs under Linux.
I recently compiled xanim for linux with modules for
Quicktime and other formats, and I have yet to find an mpeg
it will not play. It is a pretty straightforward
compile, too.
--
Dave Blake
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Fergus Henderson)
Subject: Re: What is ia32?
Date: 12 Apr 1999 14:33:20 GMT
Urs Thuermann <[EMAIL PROTECTED]> writes:
>[EMAIL PROTECTED] (Aki M Laukkanen) writes:
>
>> This leads me thinking that they were mostly bug fixing although I
>> didn't follow ia32 kernel development at that time.
>
>That's thwe second time I read this term. What is ia32?
Intel Architecture, 32-bit. In other words Intel 386 and compatibles.
IA64 is Intel's new (as yet unreleased) 64 bit architecture.
--
Fergus Henderson <[EMAIL PROTECTED]> | "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh> | of excellence is a lethal habit"
PGP: finger [EMAIL PROTECTED] | -- the last words of T. S. Garp.
------------------------------
From: David L. Bilbey <[EMAIL PROTECTED]>
Subject: fbcon/S3 Virge
Date: 12 Apr 1999 15:37:14 GMT
Does anyone know where I can find out whether I can get s3 virge support
for fbcon. I have 2.2.2, and S3 virge does not seem to be supported and I
can't get the vesafb to work (maybe my bios doesn't support it). I just
would like to find out if any of the recent kernels support this chipset
before I go and download patches on my s...l...o...w modem connection.
Thanks.
bilbey
--
"One good thing about hell, at least, is you can probably pee wherever you
want to." --Jack Handey
------------------------------
From: Frank Sweetser <[EMAIL PROTECTED]>
Subject: Re: What is ia32?
Date: 12 Apr 1999 11:28:30 -0400
Urs Thuermann <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Aki M Laukkanen) writes:
>
> > This leads me thinking that they were mostly bug fixing although I
> > didn't follow ia32 kernel development at that time.
>
> That's thwe second time I read this term. What is ia32?
intel architecture, 32 bit. ie, x86.
--
Frank Sweetser rasmusin at wpi.edu fsweetser at blee.net | PGP key available
paramount.ind.wpi.edu RedHat 5.2 kernel 2.2.5 i586 | at public servers
Coach: What's shaking, Norm?
Norm: All four cheeks and a couple of chins, Coach.
-- Cheers, Snow Job
------------------------------
From: [EMAIL PROTECTED] (Villy Kruse)
Subject: Re: SIGCHLD and zombie
Date: 12 Apr 1999 17:46:59 +0200
In article <[EMAIL PROTECTED]>,
Jose Santiago <[EMAIL PROTECTED]> wrote:
>
>Yes. If the parent does not catch the SIGCHLD, the child becomes a zombie.
The parent must do a little more than that when it is catching SIGCHLD:
Call waitpid in nonblocking mode repeatedly until there are no more
zombies.
It could also call waitpid without catching SIGCHLD if that fits withind
the program, for example if the parent need to wait for the child to exit.
Villy
------------------------------
From: [EMAIL PROTECTED] (MW Ron)
Crossposted-To:
comp.os.linux.advocacy,comp.os.linux.development.apps,comp.os.linux.help,comp.unix.programmer
Subject: Re: CodeWarror for Linux (was: Re: Programming tools for ...)
Date: Mon, 12 Apr 1999 12:58:55 -0400
In article <[EMAIL PROTECTED]>, Alexander Dymerets
<[EMAIL PROTECTED]> wrote:
>All
>you need is a good text editor, debugger and compiler. I'm a newbie
>in Linux and I tried to use some IDE's (xwpe, code crusader). At last
>I decided to use emacs + make + gdb.
There are some advantages to having makefiles and some advantages to
having an IDE. I work for Metrowerks but I firmly believe that IDE's are
more productive for day to day work. However by buying CodeWarrior you
also get validation of the tools, manuals, and other goodies.
Ron
--
Order CodeWarrior Professional 4 and receive
CodeWarrior for Red Hat Linux GNU Edition for FREE!
Offer expires 31'st of April 1999
www.metrowerks.com/buy for an authorized distributor in your country
--
METROWERKS Ron Liechty
"Software at Work" [EMAIL PROTECTED]
------------------------------
From: Urs Thuermann <[EMAIL PROTECTED]>
Subject: Re: Compiling for x86 CPUs (Was: ... seperate "i686" tree for Redhat ...)
Date: 12 Apr 1999 18:17:46 +0200
"G. Sumner Hayes" <[EMAIL PROTECTED]> writes:
> Note: The 2.0.x kernels should be compiled with gcc 2.7.2.3 rather
> than egcs.
Yes, that's why I kept 2.7.2.3 when I installed gcc-2.8.1 and also
when I replaced 2.8.1 with egcs.
> They'll produce code that will run on a 386 or better (assuming fp
> emulation in-kernel).
>
> > How should I invoke egcs
> > and gcc-2.7.2.3 to compile with maximum performance on i686 but with
> > the constraint that the code should also be executable on i486?
>
> Basic flags:
> gcc:
> -O2 -m486
Is this different from -O2 without -m<anything> on gcc-2.7.2.3 when it
is configured as i686-pc-linux-gnu? Since I asked for max performance
for i686 I interpret your answer to mean gcc only knows 386 and 486
and -m486 doesn't make a diff in my case, since I didn't configure for
386. Is that right?
> egcs:
> -Os -mcpu=pentiumpro
Same question again: is this different from -Os without -m<anything>
when egcs is configured for i686? I thought in that case egcs would
generate for Pentium II/Pro anyway. BTW, are there differences in
instruction set and/or egcs code generation between PII and PPro?
I usually have used -O2 -fomit-frame-pointer for most of my compiles.
-Os is new to me. It's not in the egcs man page, at least. So thanx
for this hint.
> Contrary to Intel docs, egcs developers claim these beat out 2 or 4
> alignments. Generates smaller code. Probably a lose on a 486, you'll
By "lose" you mean performance wise, or do you mean it crashes on 486?
> -fno-exceptions -fno-rtti
> If you're not building libraries that might be called through via C++.
> Might be good to use when building the kernel with egcs??? Shouldn't
> affect run-time too much, but could affect size.
Oops. Do -fno-exceptions and -fno-rtti affect the cc1 compiler? I've
thought it's only for cc1plus. I just checked it: I compiled some C
sources with gcc -v -S and with gcc -v -S -fno-exceptions -fno-rtti.
No difference. Although the gcc front end passes these options
through to cc1.
urs> What target should I specify to the glibc configure script? I guess
urs> i486-pc-linu-gnu does't what I want, right?
Oops. A typo. That should read "I guess ... does what I want".
> Why not? It seems like that ought to tell libc to use 486 asms
> instead of 686 ones. Have you tried:
>
> CFLAGS="-Os -mcpu=pentiumpro" ./configure i486-pc-linux --enable-omitfp
Unfortunately, I guess it won't then use the code from
glibc-2.1/sysdeps/unix/sysv/linux/i386/i686 (and probably other
similar cases), which seems ok for all x86 but faster on i686 (as the
comment states). Anyway, this is what I will try tonight and see if
my diskless i486 machine will work with glibc-2.1 compiled this way.
> Newer features are used, new TSC among them. These features don't
> exist on 386/486. A 486 compile will run on a PPro, of course.
> 2.2.x uses a lot more of these features, especially with SMP.
I've last read the code using TSC in do_fast_gettimeoffset() a few
month ago in 2.0.35 or 36. IIRC, there is a check if the CPU has the
needed capability. But maybe, there are places in 2.2.x where
PII/PPro features are used without such checks.
> > But what sense does the -m486 make, if the code does not necessarily
> > run on an i486 anyway?
>
> gcc doesn't have -m586 or -m686 or anything like that. gcc 2.7.2 is
> still the standard compiler for building the kernel (especially since
> it is the one that Linus uses). So -m486 is the best you can do.
Hm. Again the question: If I get you right, -m486 is the best since
gcc doesn't know code generation for 586 and 686 anyway. But it is
the same as without -m486 unless gcc is configured for 386. That is,
gcc knows only -m486 and -mno-486 (meaning 386), as the man page says?
urs
------------------------------
From: "B. James Phillippe" <[EMAIL PROTECTED]>
Subject: Re: kernel_thread()'s become zombies
Date: Mon, 12 Apr 1999 09:26:47 -0700
On 11 Apr 1999, Andi Kleen wrote:
> "B. James Phillippe" <[EMAIL PROTECTED]> writes:
> > I am starting this
> > thread from a kernel timer; is there any way for this to work?
>
> No. You cannot start threads from interrupts.
Hi Andi,
Correction, you can start them! I just can't seem to stop them. :( I have
a small module which does a kernel_thread from the function of a kernel
timer, and it works no problem. But when the thread dies/returns, it
becomes a zombie.
Any ideas?
thanks,
-bp
--
B. James Phillippe . [EMAIL PROTECTED]
Software Engineer, WGT Inc. . http://www.terran.org/~bryan
------------------------------
From: Rimas <[EMAIL PROTECTED]>
Subject: Re: threads and C++ exceptions
Date: Mon, 12 Apr 1999 17:43:34 +0200
Rich wrote:
>
> I keep getting SIGSEGV errors when my code executing in a
> pthread_create() created thread tries throws an exception. The class
> that I'm throwing for the exception is a very simple exception derived
> class and after some debugging I'm convinced that the class being thrown
> has nothing to do with the problem.
>
> Is there some sort of no-no about threads throwing exceptions in Linux?
> Are there special attributes that need to be set for threads when
> exceptions will be thrown by the code they execute?
>
> -Rich
> [EMAIL PROTECTED]
[sorry for my bad English]
You have to use egcs-1.1 (or higher) configured and made with the option
--enable-threads=posix
Unfortunately precompiled egcs binaries in current Linux distributions
are not made with this option and therefore you have to use egcs
compiled by yourself.
Don't get fooled by the configuration option --enable-threads (without
providing thread-support libarary). I don't know what it enables but I
guess (from egcs documentation) that it affects Objective-C compiler
only. What actualy matters for thread-safe C++ exceptions is not the
compiler executable but the runtime library and such a libarary can be
made only by using certain functions from some thread-support library
(libpthread for example).
In the case of egcs the exception handling code happens to be in
libgcc.a (the section _eh.o with symbols eh_context_initialize,
eh_context_specific, _throw etc.
This library always is linked by default by egcs.
Now some nasty subtleties if you are going to share your program with
other people.
Egcs links libgcc.a by default also when a shared library is being made.
Therefore libstdc++.so.2.9 which you obtain when you compile egcs has
all exception handling routines inside. If your executable uses
libstdc++ routines (e.g. iosteams) and is linked dynamically to
libstdc++.so.2.9 (as nearly all programs written in C++) it will use the
exception handling code imported dynamicaly from lbstdc++.so. This is
generaly a good thing because it minimizes the size of the executable.
But it also means that thread-safety of your exceptions will depend
solely on the libstdc++.so.2.9 in the computer where your program will
be run.
Currently the libstdc++.so.2.9 binaries provided by Linux distributions
are not thread-enabled.
Therefore you will have to include libstdc++.so.2.9 if you would like to
distribute the binaries of your program.
I believe that it must be possible to force linking of the
exception-handling
routines from libgcc.a staticaly while still linking dynamicaly to
libstdc++ for the rest of the stuff but I don't know how to achieve
this.
The other alternatives are:
to distribute only the source and tell the users to compile the
thread-enabled egcs first (nice exercise for the beginers, takes only
~1 hour of CPU and ~ 100 MB of HD space).
to link libstdc++ staticaly (the executable will be really big).
to wait until the Linux people will become more thread-aware and the
thread-enabled egcs and libstdc++ binaries will become the default.
There may be some problems with glibc too.
When glibc is compiled by egcs it puts some stuff from libgcc.a into
libc.so too - the infamous symbols _register_frame... and
_deregister_frame.... These functions (also exception handling related)
also needs 'thread-support' and are affected by the option
--enable-threads=...
It is widely believed that glibc2 is thread-safe but when compiled with
egcs it is bona-fide reentrant only if compiled with thread-enabled
egcs.
For the most of programs it is not a problem because they call these
functions only on startup and on exit from the main thread. The problems
may happen only if the program uses dlopen/dlclose from multiple
threads.
===============
Rimantas Plaipa,
Department of Biochemistry and Biophysics,
Vilnius University, Ciurlionio 21/27, Vilnius 2009, Lithuania.
E-mail: [EMAIL PROTECTED]
------------------------------
From: Francesc Oller <[EMAIL PROTECTED]>
Crossposted-To: comp.lang.c
Subject: a problem with scanf
Date: Mon, 12 Apr 1999 21:30:40 +0200
Reply-To: [EMAIL PROTECTED]
executing the following code in LINUX:
...
void main(void)
{
char c;
setvbuf(stdin,NULL,_IONBF,0);
tty_raw(0);
scanf("%c",&c);/*c=getchar();*/
tty_reset(0);
printf("c='%c'\n",c);
}
where tty_raw puts the terminal in RAW mode and tty_reset
returns it to COOKED mode, makes me to have to press two chars
in order for scanf to get the first (i.e printf doesn't
execute until I press twice).
However getchar works as expected (only one keyb press)
WHY?
Francesc Oller
------------------------------
From: Nix <$}xinix{[email protected]>
Subject: Re: meminfo and ps
Date: 12 Apr 1999 08:09:54 +0100
[EMAIL PROTECTED] (Phil Howard) writes:
> What I find to be a real problem in Linux is the WRITE data. Linux defers
> writing to disk until the memory is full. This means that LOTS of memory
> is used that cannot simply be taken freely for other purposes. I have a
This is what update(8) is for.
--
`The purpose of a windowing system is to put some amusing
fluff around your one almighty emacs window.' -- Mark on gnu.emacs.help
------------------------------
** 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
******************************
