Linux-Development-Sys Digest #742, Volume #7 Wed, 5 Apr 00 06:13:12 EDT
Contents:
Re: To core or not to core - You tell me (Casper H.S. Dik - Network Security
Engineer)
Re: To core or not to core - You tell me (Richard L. Hamilton)
Re: Linking error with thread program (Michael A Uman)
Re: Linking error with thread program
Re: To core or not to core - You tell me (Zoran Cutura)
Re: Free BSD (AD)
Re: MQSerirs Synchronous method (Lew Pitcher)
Re: Time zone botch? (Villy Kruse)
driver using socket ??? (philippe Defert)
Re: Rubini's device driver example (Stephane SARAGAGLIA)
Re: porting WIN32 to UNIX (Linux) (Jussi Jumppanen)
Re: To core or not to core - You tell me
Re: Random system hangs on Compaq P166/2.2.14 (Stephen Marley)
Re: porting WIN32 to UNIX (Linux) (Harald Finster)
Re: Random system hangs on Compaq P166/2.2.14 (Stephen Marley)
Re: How compatible is Linux with .. Linux (Stefaan A Eeckels)
Re: How compatible is Linux with .. Linux (Diego Berge)
Re: How compatible is Linux with .. Linux (Diego Berge)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Casper H.S. Dik - Network Security Engineer)
Crossposted-To: comp.lang.c,comp.unix.solaris,comp.lang.c++,comp.unix.programmer
Subject: Re: To core or not to core - You tell me
Date: 5 Apr 2000 05:04:13 GMT
[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]
David Williams <[EMAIL PROTECTED]> writes:
> This means that
> a) 0 == NULL (an integral constant expression with value 0...
> converted by comparsion...this produces a null pointer..)
> ^^^^^^^^^^^^^^^^^^^^^^^
> ??? are they the same or not?? NB A conversion could be taking
> place implying that they are not.
No, this means they need not be the same. A 0 is converted toa
nULL pointer in the appropriate context; multiple binary representations
of NULL pointers can exist (e.g., one for each type of object)
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
------------------------------
From: [EMAIL PROTECTED] (Richard L. Hamilton)
Crossposted-To: comp.lang.c,comp.unix.solaris,comp.lang.c++,comp.unix.programmer
Subject: Re: To core or not to core - You tell me
Date: 5 Apr 2000 05:41:02 GMT
In article <ortG4.41$cS2.1775@burlma1-snr2>,
Barry Margolin <[EMAIL PROTECTED]> writes:
> In article <8cdmjd$15fv$[EMAIL PROTECTED]>,
> -hs- <[EMAIL PROTECTED]> wrote:
>>Juergen Heinzl a �crit dans le message ...
>>[...] too...
>>>
>>>You should think of what the compiler is, probably, going to
>>>generate:
>>>
>>>ptr is NULL, so the base address is 0x00000000. a is an integer and
>>
>>
>>Wow ! In your machine perhaps, but the C-language does not guarantee a NULL
>>pointer to be at address 0.
>
> He *did* say "probably". The C language doesn't guarantee it, but most
> implementations work that way anyway.
>
> Furthermore, the original poster asked what would happen in specific
> systems. I'll bet that all of them use null pointers with the above
> representation.
On Suns, dereferencing a NULL pointer is normally illegal, and will segv
you.
A trick I saw somewhere is to use an available but apparently undocumented
workaround (and of course fix your code ASAP): set LD_PRELOAD to
[EMAIL PROTECTED], which will provide a zero at address zero to make
clueless programs happy.
--
ftp> get |fortune
377 I/O error: smart remark generator failed
Bogonics: the primary language inside the Beltway
mailto:[EMAIL PROTECTED] http://www.smart.net/~rlhamil
------------------------------
From: Michael A Uman <[EMAIL PROTECTED]>
Subject: Re: Linking error with thread program
Date: Wed, 05 Apr 2000 05:47:04 GMT
==============B0D63CEFC6EC2BE223A179CA
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Chuck Winters wrote:
> Hello All,
> I am trying to create a small program using threads(I'm bored). I was
> wondering how to reconcile this linking error I am getting when I try to
> compile and linke the program. I am sure I will have to use a command line
> option to redirect the compiler to the right library, but which library should
> I point to? Any help would be appreciated.
>
> Chuck Winters
Hi Chuck,
I think I can answer this one... I have been recently using the pthreads
library...
the compile & link is like this
gcc -D_REENTRANT -o myApp myApp.cp -lpthread
The trick is `-lpthread' which tells the linker to link with "libpthread.a" which
should be available in the default lib directory. Note also that I define
preprocessor symbol _REENTRANT which is recommended so that you use the reentrant
versions of certain library routines.
Try that,
Michael Uman
==============B0D63CEFC6EC2BE223A179CA
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Chuck Winters wrote:
<blockquote TYPE=CITE>Hello All,
<br> I am trying to create a
small program using threads(I'm bored). I was
<br>wondering how to reconcile this linking error I am getting when I try
to
<br>compile and linke the program. I am sure I will have to use a
command line
<br>option to redirect the compiler to the right library, but which library
should
<br>I point to? Any help would be appreciated.
<p>Chuck Winters</blockquote>
Hi Chuck,
<p>I think I can answer this one... I have been recently using the
pthreads library...
<p>the compile & link is like this<font face="Courier New,Courier"></font>
<p><font face="Courier New,Courier">gcc -D_REENTRANT -o myApp myApp.cp
-lpthread</font>
<p>The trick is `-lpthread' which tells the linker to link with "libpthread.a"
which should be available in the default lib directory. Note also that
I define preprocessor symbol _REENTRANT which is recommended so that you
use the reentrant versions of certain library routines.
<p>Try that,
<p> Michael Uman
<br> </html>
==============B0D63CEFC6EC2BE223A179CA==
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Re: Linking error with thread program
Date: Wed, 05 Apr 2000 08:00:03 +0100
On Wednesday, April 5, 2000 5:34 AM Chuck Winters
<[EMAIL PROTECTED]> wrote:
If you are using the pthread lib, just pout a -lpthread on gcc's command line
--
BBP
------------------------------
From: Zoran Cutura <[EMAIL PROTECTED]>
Crossposted-To: comp.lang.c,comp.unix.solaris,comp.lang.c++,comp.unix.programmer
Subject: Re: To core or not to core - You tell me
Date: Wed, 05 Apr 2000 08:03:54 +0200
Harish K Chandraia wrote:
>
> Hi All,
>
> I hope that somebody can tell me what is going on here. I
> have the following C program
>
> #include <stdio.h>
>
> int main()
> {
> struct def
> {
> int a;
> };
>
> struct def *ptr;
>
> ptr = NULL;
>
> printf("%d\n", ptr->a);
> }
>
>
> From all that you know about programming what do you think should
> happen when I try to compile and execute the above program. I have executed
> this piece of code on the following four machines(posting about my
> results will follow). I am not trying to be a smart ass here but I am
> only interested in knowing what you people think would happen because
> what I thought would happen didn't happen on two of the four machines.
>
> 1. (samwise)# uname -a
> unix samwise 5.3 1.0 mc68060
>
> 2. # uname -a
> NonStop-UX leonard 4.2MP C51IPM74.puma.0414.01:12 S5000 mips
>
> 3. hercules23> uname -a
> SunOS hercules23 5.5.1 Generic_103640-24 sun4u sparc SUNW,Ultra-60
>
> 4. icarus# uname -a
> SunOS icarus.cc.uic.edu 5.7 Generic_106541-10 sun4u sparc SUNW,
> Ultra-Enterprise
>
> Thank you
> Harish
Now after all where are your results?????
------------------------------
From: AD <[EMAIL PROTECTED]>
Subject: Re: Free BSD
Date: 5 Apr 2000 06:21:33 GMT
Sebastien Dessimoz <[EMAIL PROTECTED]> ����� � �����
comp.os.linux.development.system:
> What is the advantage to use Linux instead of FreeBSD or the opposite???
FreeBSD is alive. It've appeared earlier than Linux, so it is well
distribute in the world (in Russia, e.g.). Many people say, that
FreeBSD is good for to install it and work. Not modify a lot. But
Linux is flexible. And, for the p.s.: Linux and BSD are friends:
look at the history of Linux NET code, for example. Its just like
a people life, life of OS's: everybody learn to live from others.
--
Andrei Uporov aka - AD -
Home page: http://oniltz.da.ru/~ad
ICQ UIN #: 40495187 _Unixes,programming,administry...-simply_i_liKe_it..._
------------------------------
From: Lew Pitcher <[EMAIL PROTECTED]>
Subject: Re: MQSerirs Synchronous method
Date: Wed, 05 Apr 2000 06:31:19 GMT
qsun wrote:
>
> I am using IBM MQSeries under LInux, does anybody knw
> is there any synchronous method of MQSeries to put/get
> messages?
MQSeries implements asynchronous messaging. The closest you can get to
synchronous messaging in MQSeries is to impose an extended timeout on
your MQGET() such that you guarantee that all but the most hopelessly
lost messages are retrieved before the MQGET times out. In other
words, never truely synchronous.
--
Lew Pitcher
Master Codewright and JOAT-in-training
------------------------------
From: [EMAIL PROTECTED] (Villy Kruse)
Subject: Re: Time zone botch?
Date: 5 Apr 2000 06:55:15 GMT
On Tue, 04 Apr 2000 16:55:40 GMT, Jim Haynes <[EMAIL PROTECTED]> wrote:
>This is on a Red Hat 5.2 system. I am in central (U.S.) time zone.
>I ran the following test program. It prints EST as the time zone
>name. If I change the link /etc/localtime to point to other files
>in the zoneinfo/US directory it gives the correct time zone: EST,
>MST, or PST. But in Central it gives EST. I haven't figured out
>what makes those zoneinfo files to know how to look at it.
>
>#include <time.h>
>main()
>{
> time_t t;
> time(&t);
> /* printf("%s\n", ctime(&t)); */
> localtime(&t);
> printf("%s\n", *tzname);
>}
You will need to extract the time zone name from the tm structure
returned from localtime. Or install RH6.1 with the new glibc library
where the problem is fixed.
Villy
------------------------------
From: philippe Defert <[EMAIL PROTECTED]>
Subject: driver using socket ???
Date: Wed, 05 Apr 2000 12:02:13 +0200
Reply-To: [EMAIL PROTECTED]
hi ,
i developpe a character driver using socket
and when i compile i have no warning and no error
but when i load the module ,
the kernel respond :
./driv.o : unresolved symbol socket
./driv.o : unresolved symbol getservname
./driv.o : unresolved symbol getservbyname
./driv.o : unresolved symbol connect
but i need this fonction in my driver, it's more inportante for the
future of my program
do you know a solution for this problem (static link or new code for
using th socket with the kernel, i dont konw)
thanks
philippe Defert
P.S. it's the code of open function :
static int driv_open( struct inode *inode, struct file *file )
{
int retval=0;
MOD_INC_USE_COUNT;
{
int co;
int sock;
sock=socket(AF_INET,SOCK_STREAM,0);
^^^^^^^
if (sock==-1)
{ perror("\n Pb creation SOCKET ");
exit(1);
}
else printf("socket cree : [AF_INET,SOCK_STREAM,0]
%d\n",sock);
getservname(srvname,10);
h=getservbyname(srvname);
if ( h==NULL )
{ printf(" Machine : %s - non identifiable \n",srvname);
exit(1);
}
else printf(" Machine : %s - reconnue \n",h->h_name);
adrsrv.sin_addr.s_addr= *((unsigned long *) h->h_addr);
adrsrv.sin_family=AF_INET; /* h->h_adrtype; AF_INET */
adrsrv.sin_port=PORT ;
co=connect(sock,(struct sockaddr *)
&adrsrv,sizeof(adrsrv));
if ( co==-1 )
{ perror("\n Echec lors de la Connection ");
exit(1);
}
}
return sock;
}
------------------------------
From: Stephane SARAGAGLIA <[EMAIL PROTECTED]>
Subject: Re: Rubini's device driver example
Date: Wed, 05 Apr 2000 11:04:09 +0200
You have to permit syslog to print kernel messages in console by
adding or uncommenting the following line in the /etc/syslog.conf file :
kern.* /dev/console
So, I think "xterm -C" will print your kernel messages.
Stephane SARAGAGLIA
Girish Chandraiah wrote:
>
> I thought this might help some newbie's like myself. As suggested by one of the
>replies
> to the original posting, printk outputs did apprear in the /var/log/messages
> xterm -C didn't seem to help. Thanks to those who responded.
>
> nilesh patel wrote:
>
> > "Roger J. Pryor" wrote:
> >
> > > > Harish K Chandraia schrob:
> > > > > I am trying to run the first example in Rubini's Linux Device
> > > > > Drivers and when I run the insmod command, I don't see "Hello World"
> > > > > from the init_module() being printed and I don't see anything from
> > > > > the cleanup_module() being printed when I run the rmmod command
> > > > > either.
> > > >
> > > > Are you running X? printk's don't appear on an X console.
> > > > Switch to a standard console and try from there.
> > > >
> > > > HTH
> > > > Christian
> > > >
> > >
> > > Or take a look into /var/log/messages, that is the printk daemon's log
> > > file.
> > >
> > > --
> >
> > try xterm -C if you want that on xterm .
------------------------------
From: Jussi Jumppanen <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.development,comp.os.ms-windows.programmer.win32,comp.os.ms-windows.programmer.misc,comp.unix.programmer,comp.programming
Subject: Re: porting WIN32 to UNIX (Linux)
Date: Wed, 05 Apr 2000 19:27:47 +1000
Johannes Hacker wrote:
> I am currently working on a project where I have to port a WinNT
> Application to Linux. I am mainly focused on threads, processes,
> synchronization and messaging between processes.
I would suggest taking a look at Wine web page:
www.winehq.com
This is an Open Source project that is attempting to have windows
programs (and the Win32 API) running on linux and so far they have
done a wonderful job.
Jussi Jumppanen
Author of: Zeus for Windows, Win32 (Brief, WordStar, Emacs) Text Editor
"The C/C++, Java, HTML, Pascal, Cobol, Fortran programmer's text editor"
http://www.zeusedit.com
------------------------------
From: [EMAIL PROTECTED] ()
Crossposted-To: comp.lang.c,comp.unix.solaris,comp.lang.c++,comp.unix.programmer
Subject: Re: To core or not to core - You tell me
Date: 5 Apr 2000 09:24:04 GMT
In article <8cd1d7$vkl$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Harish K Chandraia) writes:
> Hi All,
>
> I hope that somebody can tell me what is going on here. I
> have the following C program
>
> #include <stdio.h>
>
> int main()
> {
> struct def
> {
> int a;
> };
> struct def *ptr;
> ptr = NULL;
> printf("%d\n", ptr->a);
> }
>
>
> From all that you know about programming what do you think should
> happen when I try to compile and execute the above program.
*Anything* might happen, as far as the C standard is concerned, because
you've attempted to dereference a null pointer.
`prt` is a null pointer (you assigned it explicitly), and `ptr->a`
dereferences it. The C standard says that this produces "undefined
behaviour", which means an implementation is allowed to do whatever
it likes.
Plausible results:
* a memory protection fault of some kind.
* access to random garbage that happens to be at address 0.
Less plausible results:
* you crash the machine, because accesses to address 0 are accesses
to I/O space, and you haven't written the command yet.
* the compiler crashes, because the optimiser attempts to dereference
0, because it knows that your program is conforming (and if it
isn't, it can do *anything*)
* the compiler emails a message to your SO with a detailed description
of something you'd rather they didn't know about.
Highly implausible results:
* the generated code factorises large composite numbers, and the
compiler wins a coveted prize.
--
Chris "implausible but nevertheless actual" Dollin
C FAQs at: http://www.faqs.org/faqs/by-newsgroup/comp/comp.lang.c.html
------------------------------
From: [EMAIL PROTECTED] (Stephen Marley)
Crossposted-To: uk.comp.os.linux
Subject: Re: Random system hangs on Compaq P166/2.2.14
Date: 5 Apr 2000 09:37:58 GMT
Tim Haynes <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Stephen Marley) writes:
> > Won't any of the kernel experts out there offer some insight on this?
>
> IANA(expert), exactly, but I swear I've heard of something happening with
> Via support in 2.2.14...
I got to see the box last night and built a kernel with no UDMA support.
Of course, the machine worked perfectly for the duration of my visit.
> > Could it just be overheating? It's only a P166 but there's no fan,
> > only a heatsink.
>
> Aaaaarrrrrgggggggggghhhhhhhhhhhhhhhhhhhhhh. (That expressive enough?
> ;)
>
> If your machine is off during the day but wakes up when you get home
> at 1830 (for example) then you should make notes of when it first
> falls over and then how often thereafter it fails, for about 3 days'
> worth. (This is to guarantee a from-cold start every time.) Then get a
> CPU fan and do the same for another couple of days. Graph it (time to
> initial failover + interval thereafter), if you want. Results should
> be obvious.
>
> (I did this for a notebook - 486DX3/99 that should've been 3/75 - and
> had it absolutely clear which was which. With fan it took longer and
> there was a greater MTBF.)
It's not my machine but immediately after re-building the kernel, I
whipped the cover off couln't detect any signs of overheating.
--
[EMAIL PROTECTED]
------------------------------
From: Harald Finster <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.development,comp.os.ms-windows.programmer.win32,comp.os.ms-windows.programmer.misc,comp.unix.programmer,comp.programming
Subject: Re: porting WIN32 to UNIX (Linux)
Date: Wed, 05 Apr 2000 11:50:37 +0200
Johannes Hacker wrote:
>
> Hello!
>
> I am currently working on a project where I have to port a WinNT
> Application to Linux. I am mainly focused on threads, processes,
> synchronization and messaging between processes. I've heard about the
> POSIX-Standard, but I really don't know where to begin.
> Are there any documents, links, ... available about porting in general?
> This problem sounds not so unusual, I am sure this has been done before!
Not sure, if this is exactly an answer to your question (because
my suggestion is NOT a tool for porting).
But anyways: you might consider using ACE, a toolbox supplying a platform
independent programming environment for things like threads, IPC, RPC ...
And there is even a CORBA implementation based on ACE.
Have a look at:
http://www.cs.wustl.edu/~schmidt/ACE.html
HTH
Harald
--
Harald Finster
-
Windoze can be used on the North-Pole without any problems,
... because a frozen computer can't freeze
------------------------------
From: [EMAIL PROTECTED] (Stephen Marley)
Crossposted-To: uk.comp.os.linux
Subject: Re: Random system hangs on Compaq P166/2.2.14
Date: 5 Apr 2000 09:54:12 GMT
Bill Hayles <[EMAIL PROTECTED]> wrote:
> I'm running the same model (but with 32Mb and no ISDN card) as my server
> here using SuSE 6.3 and it's been up for weeks. I doubt it's
> overheating - that's the way Compaq built the things, and there's a good
> air flow around the processor. As an off-the-wall diagnosis, I'd
> suspect an iffy 64Mb RAM chip.
Now that I've had a chance to visit this box, I tend to agree that the
problem is not overheating.
I thought the RAM was OK - it's decent quality Hyundia PC100 stuff -
unless there are any issues with using PC100 dimms in a 66Mhz board (or
the shop has sold me a return - never)? I'll swap the RAM if the
problem keeps occurring. I've also got an old ISA 3c509 on standby to
replace the ne2000 clone.
Could there be a problem related to pci irq sharing between the isdn
card and the nic, or is that solid in linux 2.2.x? Kinda worries me that
I can't change any PCI irqs on the compaq without changing them all.
I'll find out on Thursday if my udma-less kernel has made any difference.
--
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Stefaan A Eeckels)
Crossposted-To: comp.os.linux.development.apps
Subject: Re: How compatible is Linux with .. Linux
Date: 5 Apr 2000 07:35:43 GMT
In article <8cdk1j$l99$[EMAIL PROTECTED]>,
"Peter T. Breuer" <[EMAIL PROTECTED]> writes:
> Which was that system that insisted on making backups
> of your file every time you edited it? With colons in. I _think_ that
> was MVS. It's been a couple of decades. If so, it's still in use in
> backup-conscious places.
MVS did that, but so did GEORGE, ICL's OS for their 29 series
of mainframes. It was quite hilarious editing on one of these
beasts - the terminal server sucked the file off the mainframe,
and allowed you to page through it, forward only. If you wanted
to add lines to the file, you had to know in advance how many,
so you could tell the editor you only wanted 12 lines instead
of 22 (2 lines spare you always got, IIRC). If you miscalculated,
or got the page wrong, you had to quit the editor, causing an
indentical copy to be saved, and restart it. After a morning's
worth of editing a COBOL program, one usually got anxious phone
calls from the operators, asking "please, please can you delete
all your backup copies, the catalog is getting full".
Compiling was just as enthralling. You had to sit next to the
terminal, to hit "continue" after every 24 lines of output
(no way to switch that off) but unfortunately the "abort" key
sat next to the "continue" key so with the compilation speed
of these machines, one can imagine how often a stream of
invectives flew from the programmer's cubicles; accidentally
hitting abort after babysitting a compilation for 20 minutes
is no-one's idea of fun.
>
> I wonder how compatible VMS is with MVS ... ;)
No compatibility whatsoever.
--
Stefaan
--
--PGP key available from PGP key servers (http://www.pgp.net/pgpnet/)--
Ninety-Ninety Rule of Project Schedules:
The first ninety percent of the task takes ninety percent of
the time, and the last ten percent takes the other ninety percent.
------------------------------
From: [EMAIL PROTECTED] (Diego Berge)
Crossposted-To: comp.os.linux.development.apps
Subject: Re: How compatible is Linux with .. Linux
Date: Mon, 03 Apr 2000 19:50:10 GMT
On 2 Apr 2000 17:39:42 GMT, "Peter T. Breuer" <[EMAIL PROTECTED]>
wrote:
>In comp.os.linux.development.apps q_49@hot###mail.com wrote:
>: Well said Rod. Mr. Breuer also made some unseemly comments in
>: response to a question I asked. His answers are usually condescending
>: and invariably unhelpful. It seems that this is "normal" behavior
>: for him, I pity his co-workers. It is consoling to know that his
>: attitude is in the minority.
>
>What world do you live in? Producing software is a technically
>difficult task. It requires technical expertise, not politeness and
>good manners!
You're not 'producing software' here. You're participating in a
public discussion forum.
Regards,
Diego Berge.
------------------------------
From: [EMAIL PROTECTED] (Diego Berge)
Crossposted-To: comp.os.linux.development.apps
Subject: Re: How compatible is Linux with .. Linux
Date: Tue, 04 Apr 2000 00:25:13 GMT
On 03 Apr 2000 14:08:12 +0200, Moritz Franosch
<[EMAIL PROTECTED]> wrote:
>
>
>[EMAIL PROTECTED] (Peter Mardahl) writes:
>
>> I think the safest/least effort thing to do is simply to generate a static ELF
>binary
>> that works on the 2.2 series of kernels.
>>
>> That should work with every modern distribution. It's possible it may fail on some
>> really, really old installations of Linux.
>>
>> A "better" thing to do might be to dynamically link your executable, BUT also make
>> available ALL the libraries which may be needed dynamically. If the program finds
>> itself being installed on a system without the needed libraries, have your installer
>> put in the needed libraries too.
>
>
>I totally agree.
>If your (dynamically linked) program does not work with the dynamic
>link libraries on the customer's system, this can have several reasons:
>1. The library you linked against is not installed on your customer's
> system.
>2. You get "unresolved symbols" because of an incompatibility.
>3. Your program just crashes randomly because of differences between
> the dynamic link libraries.
>
>You should perhaps first try to link your program dynamically against
>the customer's libraries. If that fails (check the output of 'ldd -r',
>this prevents issues 1. and 2.), your installation routine should
>install your versions of the dynamic libraries.
>Because of 3., advanced customers should also have the choice between
>your and their own versions of dynamic libraries. E.g. an update of
>glibc may be necessary because of a change in the kernel while it's
>necessary for all other libraries to link against the original ones
>because of 1. or 2.
ok, but then doesn't it end up being like w/ windows DLL's, where
new apps upgrade old DLL's and along the way break those old apps
using the old DLL's? Another not-so-good solution could be being able
to access more than one version of the same library, no?
Regards,
Diego Berge.
------------------------------
** 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
******************************