Linux-Development-Sys Digest #723, Volume #8 Wed, 16 May 01 10:13:16 EDT
Contents:
Re: Path to kernel include directory? (Kasper Dupont)
Re: Generic SCSI driver (Kasper Dupont)
Re: Generic SCSI driver (Josef Moellers)
Re: passing messages to a forked thread ([EMAIL PROTECTED])
Re: make dep clean zImage (Lew Pitcher)
Newbie programmer ("Paul Jones")
Re: Path to kernel include directory? (Rene Herman)
Re: Generic SCSI driver (Andrzej Stypula)
Re: Newbie programmer ("William Dandreta")
Formulating Compatibility Signature: (Adam Shapira)
Re: Newbie programmer (Lars Luthman)
Re: malloc returns NULL! (Wolfram Gloger)
Re: Path to kernel include directory? (Grant Edwards)
Re: Path to kernel include directory? (Grant Edwards)
Re: Newbie programmer ("Thorsten Roggendorf")
Re: Path to kernel include directory? (Grant Edwards)
Re: Formulating Compatibility Signature: (Rene Herman)
Re: Understanding module initialization (Derek Viljoen)
----------------------------------------------------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: Path to kernel include directory?
Date: Wed, 16 May 2001 10:12:08 +0000
Jim Cochrane wrote:
>
> In article <NLhM6.997$[EMAIL PROTECTED]>,
> Grant Edwards <[EMAIL PROTECTED]> wrote:
> >One of the drivers I maintain has always used
> >/usr/src/linux/include as the path to the kernel include
> >directory.
> >
> >This seemed to work well until RH7.1 (we refused to attempt
> >supporting RH7.0). Now there is no /usr/src/linux symbolic
> >link installed by the kernel-sources package in RH7.1, and our
> >driver won't compile (the first of many problems, I'm sure).
> >
> >Anyway, if you can't depend on /usr/src/linux/include being
> >there anymore, what mechanism do people use to find kernel
> >include files?
>
> I think (and I hope someone more knowledgeable will correct me if I'm
> wrong) that it's standard for linux distributions to have a symbolic link
> from the linux include directory to /usr/include/linux.
I don't know if there is any standard, but even if
there was a standard there would be distributions
not following it. In RH7.0 /usr/src/linux/include
and /usr/include contained two different versions
of the header files.
I think you have to rely on either /usr/include or
/usr/src/linux/include and tell people what to do
if they have a version where it doesn't work like
adding a new symlink. Perhaps generating a symlink
in your own modules source directory to an
appropriate include directory would be the most
reliable version.
In RH6.0 both /usr/src/linux/include and
/usr/include works. In RH7.0 only
/usr/src/linux/include works.
>
> >
> >Does /usr/src/linux-<version>/include work in enough distros
> >to be worthwhile?
> >
> >--
> >Grant Edwards grante Yow! Let's climb to the
> > at TOP of that MOUNTAIN and
> > visi.com think about STRIP MINING!!
>
> --
> Jim Cochrane
> [EMAIL PROTECTED]
--
Kasper Dupont
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: Generic SCSI driver
Date: Wed, 16 May 2001 10:47:01 +0000
Andrzej Stypula wrote:
>
> Kasper Dupont wrote:
> > The generic scsi devices is used to send commands
> > directly to the devices. This interface can be used
> > to control all different types of scsi devices not
> > just block devices.
> >
> > If you need to mount a block device you should not
> > use the generic driver but the driver specialized
> > to the type of block device being used. If it is a
> > CD drive the name is typically /dev/scd0. If it is
> > a harddisk I think the name is /dev/sda.
>
> OK.I know, when I need to mount device I have to use the specialized
> driver like /dev/sd? or /dev/hd? But how I can bind/remove the generic
> driver outside the lilo.conf?
> If generic is binding I can not use specialized driver
>
> Thanks,
> --
> Andrzej Stypula @Home: altair.krakow.pl
> [EMAIL PROTECTED] Private Home Domain, Poland
> PGP2.x id: 9AB243A5 ####################################################
I don't think it is posible to use /dev/hd?
and /dev/sg? simultaneously on the same drive.
But it is posible to use /dev/sg? and /dev/sd?
simultaneously on the same drive.
Is it a CD or a harddisk you want to use?
--
Kasper Dupont
------------------------------
From: Josef Moellers <[EMAIL PROTECTED]>
Subject: Re: Generic SCSI driver
Date: Wed, 16 May 2001 13:07:20 +0200
Andrzej Stypula wrote:
> =
> Kasper Dupont wrote:
> > The generic scsi devices is used to send commands
> > directly to the devices. This interface can be used
> > to control all different types of scsi devices not
> > just block devices.
> >
> > If you need to mount a block device you should not
> > use the generic driver but the driver specialized
> > to the type of block device being used. If it is a
> > CD drive the name is typically /dev/scd0. If it is
> > a harddisk I think the name is /dev/sda.
> =
> OK.I know, when I need to mount device I have to use the specialized
> driver like /dev/sd? or /dev/hd? But how I can bind/remove the generic
> driver outside the lilo.conf?
> If generic is binding I can not use specialized driver simultaneously.
The generic driver is an additional interface, next to the proper device
drivers like /dev/st* and /dev/sd*. As long as you don't use it, it just
sits there and does nothing. No need to bind/unbind the generic driver.
Evene when a partition on a scsi disk is mounted, you can use the
generic scsi driver e.g. to read some status from the drive.
BTW. As the name /dev/_s_g implies, this is a generic SCSI driver (I
know, not all /dev/s* are SCSI devices), it won't work on /dec/hd*.
-- =
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: passing messages to a forked thread
Date: 16 May 2001 10:31:36 GMT
On Tue, 15 May 2001 23:35:32 +0100 Darren LS <[EMAIL PROTECTED]> wrote:
| Hello all. I have a nice little socket programmed than runs transparently
| due to the fork command thanks to the advice of many wonderful people on
| these newsgroups. However now I need to do some manipulation to the
| currently running process. I appreciate any advice on the following
|
| 1. this thread must be able to detect if it is the only instance running and
| if not then it needs to be able to get the process handle of other instances
| so it can communicate with them
Only instance of what? Of a particular executed program file? Of being
forked from the same parent?
| 2. Active instances must be able to take signals of other threads, processes
| or even programs
Depending on what you are expecting, this may or may not be possible.
| 3. must be able to send signals to other processes both local and remote
What do you mean by remote? On a different computer?
| 4. must be able to ignore SIGTERM and should SIGKILL be thrown at it then it
| needs to survive long enough to fill in a log entry before it goes down. I
| appreciate any ideas.
SIGKILL is defined as not being interceptable. The only way to detect such
a signal is to have a parent waiting for it and have that parent enter the
log entry (if it is also not killed).
It is possible for an errant process to go into a loop when it's handling a
signal. How would you kill such a process if you didn't have a SIGKILL that
was not interceptable?
--
=================================================================
| Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ |
| [EMAIL PROTECTED] | Texas, USA | http://phil.ipal.org/ |
=================================================================
------------------------------
From: [EMAIL PROTECTED] (Lew Pitcher)
Subject: Re: make dep clean zImage
Reply-To: [EMAIL PROTECTED]
Date: Wed, 16 May 2001 12:08:10 GMT
On Tue, 15 May 2001 20:17:26 -0700, <[EMAIL PROTECTED]> wrote:
>Well Gentlemen, I would be interested in your take on the file
>linux/Documentation/modules.txt as I am trying to understand module
>compilation and I found in that file a reference to doing the make dep clean
>zImage in that order (as opposed to make clean dep zImage). I also see here
>a note that says, to enable CONFIG_MODVERSIONS (instead of disable same) to
>make the compilation more independent of versioning information.
>
>Basically, I have been told by others (and found in reference books) the
>exact opposite of what this file says. Some references say to 'make dep
>clean bzImage' in that order and others say do 'make clean dep bzImage' in
>that order. Additionally, some references say disable CONFIG_MODVERSIONS for
>module independent versioning and others say enable CONFIG_MODVERSIONS for
>independent versioning.
>
>So... I don't know what to believe or not believe. If it is described in the
>*official* Linux documentation, do we take it as gospel, with a grain of
>salt, or only on Sunday?
'make dep' builds the compilation dependancy lists that are necessary
before the 'make bzImage' can be performed
'make clean' deletes any old intemediary and object files, so that
there's no compile results left around from previous compiles
'make bzImage' compiles the kernel (using the dependancy lists to
determine what gets compiled first), and then copies/links all the
compile results to a big kernel file
'make dep' and 'make clean' have to preceed 'make bzImage', but the
order in which you run 'make dep' and 'make clean' (IIRC) doesn't
matter. This means that 'make dep clean' is just as good as 'make
clean dep'.
But, you missed two more 'make' steps when compiling a modularized
kernel: 'make modules' and 'make modules_install'
'make modules' compiles the modules
'make modules_install' copies the modules into the
/lib/modules/$KERNEL_VERSION directory tree.
These two commands have to be performed in that order, and must be
performed after the 'make dep clean'; they may either preceed, follow,
or surround the 'make bzImage'.
Lew Pitcher, Information Technology Consultant, Toronto Dominion Bank Financial Group
([EMAIL PROTECTED])
(Opinions expressed are my own, not my employer's.)
------------------------------
From: "Paul Jones" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.mandrake,comp.os.linux.development.apps
Subject: Newbie programmer
Date: Wed, 16 May 2001 21:50:47 +1000
I was wondering if anyone could point me in the direction of some help for
people moving from windows to Linux development. I can't seem to find
anything on the subject. I'm ok at windows programming, but I'm assuming
that linux has totally different libraries and stuff. Also I'm still
learning Linux which makes it a bit hard :)
All help appreciated!
Paul Jones.
------------------------------
From: Rene Herman <[EMAIL PROTECTED]>
Subject: Re: Path to kernel include directory?
Date: Wed, 16 May 2001 15:20:48 +0200
Jim Cochrane wrote:
> I think (and I hope someone more knowledgeable will correct me if I'm
> wrong) that it's standard for linux distributions to have a symbolic
> link from the linux include directory to /usr/include/linux.
It's not only standard, it's pretty much *required* to have a set of
kernel headers in /usr/include/{linux,asm}. Sometimes these directories
will be just symlinks to /usr/src/linux/include/{linux,asm}, sometimes
they will be real directories containing the headers from some fixed
kernel version that the rest of the system was compiled against.
I'm not a kernel and/or driver developper, so somebody please correct
if *I* am wrong, but I believe that driver code should just rely on
#include <linux/...>
#include <asm/...>
The kernel supplied drivers do. If 3rd party code relies on a very
specific kernel version (and/or kernel headers from, say, net or scsi),
I guess it should tell the the person that's building it to dump the
driver source into that specific tree and use the master kernel
Makefile to build. The kernel build process will make sure that the
#include will pick up the version specific headers before looking
through /usr/include/{linux,asm}
Rene.
------------------------------
From: Andrzej Stypula <[EMAIL PROTECTED]>
Subject: Re: Generic SCSI driver
Date: Wed, 16 May 2001 15:33:19 +0200
Kasper Dupont wrote:
> Andrzej Stypula wrote:
> > OK.I know, when I need to mount device I have to use the specialized
> > driver like /dev/sd? or /dev/hd? But how I can bind/remove the generic
> > driver outside the lilo.conf?
> > If generic is binding I can not use specialized driver
>
> I don't think it is posible to use /dev/hd?
> and /dev/sg? simultaneously on the same drive.
> But it is posible to use /dev/sg? and /dev/sd?
> simultaneously on the same drive.
>
> Is it a CD or a harddisk you want to use?
I have the atapi CD (at /dev/hdd) so, some times I want to read this
as scsi device (for ex. readcd requires the scsci device).
If I add the line 'append hdd=ide-scsi' in my lilo.conf, when
I have info in /proc about this binding, and until now all is OK.
But I can not to mount any fs by /dev/hdd - this is my problem.
All is OK if generic is unloaded but in this case I can not to
use /dev/sg?.
up to now I do not find any solution for this problem.
Maby magic line in conf.modules?
--
Andrzej Stypula @Home: altair.krakow.pl
[EMAIL PROTECTED] Private Home Domain, Poland
PGP2.x id: 9AB243A5 ####################################################
------------------------------
From: "William Dandreta" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.mandrake,comp.os.linux.development.apps
Subject: Re: Newbie programmer
Date: Wed, 16 May 2001 13:38:28 GMT
Hi Paul,
>I was wondering if anyone could point me in the direction of some help for
>people moving from windows to Linux development.
>
You might want to give Kylix a try, especially if you know some Pascal. It
is Borland's port of Delphi to Linux. Delphi takes the pain out of writing
Windows programs because you don't need to know Windows API's to write
effective programs. Kylix should do the same for Linux. I haven't tried it
yet. The first release costs $1000 but a GPL version should be available via
download this summer. You might want to checkout the Kylix info on Borland's
website and the Kylix newsgroup as well.
Python is another good choice. It is the easiest language I have ever
learned and runs on most platforms including both Windows and Linux. If I
had to learn programming from scratch I would start with Python than learn
Delphi. Knowing both would allow you to easily accomplish most programmming
tasks.
Bill
------------------------------
Date: Wed, 16 May 2001 09:46:24 -0400
From: Adam Shapira <[EMAIL PROTECTED]>
Subject: Formulating Compatibility Signature:
Generally, with my programs, the installer uses two variables,
OS_TYPE and HOSTTYPE, to determine if the pre-compiled object
files are compatible with the current machine that I'm trying
to install a program on.
Only one problem with this: the OS_TYPE variable is not
constant in the Linux world. I've seen cases of it taking
a number of different values. For example, on RedHat 6.x,
OS_TYPE has a value of "Linux", and on RedHat 7, the same
environment variable has a value of "linux-gnu".
This is a problem because I have two machines that run
RHLinux, one running 6.x and one running 7. Stuff that I
write and compile on one won't install on the other. I
have to install from the source-code again. This will
also be a problem when I try to distribute my software,
or to install it on systems (which do exist) where
the "compile" feature of -gcc- has been disabled.
Is there any more official way of determining a compatibility
signature other than using the OS_TYPE and HOSTTYPE environment
variables?
I know some of you might tell me to upgrade the 6.x machine
to 7, but there are two problems to this. First of all, our
SysAdmin is Part Time. Second of all (and more importantly)
to do that would be evading (rather than solving) the
problem.
Thanks,
Adam
------------------------------
From: Lars Luthman <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.mandrake,comp.os.linux.development.apps
Subject: Re: Newbie programmer
Date: Wed, 16 May 2001 15:35:08 +0200
Paul Jones wrote:
>
> I was wondering if anyone could point me in the direction of some help for
> people moving from windows to Linux development. I can't seem to find
> anything on the subject. I'm ok at windows programming, but I'm assuming
> that linux has totally different libraries and stuff. Also I'm still
> learning Linux which makes it a bit hard :)
It depends on what language you are using, and what you want to do. If
you want to write text-based programs in ANSI C++ without any
OS-specific stuff like playing sounds and opening network connections,
it's exactly the same. If you want to write GUI apps, you should learn a
widget library, like Qt (http://www.trolltech.com) or
GTK+(http://www.gtk.org). There are widget libraries that claim to work
on lots of platforms, wxWindows (http://www.wxwindows.org), for example,
have libraries for UNIX systems, Windows and Mac. I haven't tried it
myself, but it looks interesting.
All Linux system calls and standard C functions have man pages, so you
could type 'man bind' or 'man strcspn' to get information about the bind
function or the strcspn function. Or you could use the help browsers in
KDE or Gnome.
If you want a nice graphical IDE, you should take a look at KDevelop
(http://www.kdevelop.org). I haven't used it in a while, but the last
time I checked it had frameworks for Qt/KDE/GTK+/console applications,
and it sets up your project for you using 'automake' and 'autoconf', all
you have to do is write the code. If you want more control you could use
XEmacs (http://www.xemacs.org) or another editor to write your own
Makefile.am and configure.in. Take a look at the info pages for automake
and autoconf.
Have fun.
--ll
------------------------------
From: Wolfram Gloger <[EMAIL PROTECTED]>
Subject: Re: malloc returns NULL!
Date: 16 May 2001 15:49:16 +0200
"Karl Heyes" <[EMAIL PROTECTED]> writes:
> I don't know what the implementation of glibc malloc is like
I do :-)
> but if two
> pointers are used and 10 bytes requested then that a minimum of 18 bytes
> for each allocation (not counting alignment, size field and chunk usage).
The pointers are used by the malloc implementation _only_ when the
chunk is `not in use', therefore they don't contribute to `overhead'
but just to the minimum chunk size of 16bytes. Only the 4byte `size'
field is truly overhead. This is one of the good features of glibc's
malloc.
This is all on 32bit architectures only, though, I forgot that in my
previous post.
Regards,
Wolfram.
------------------------------
From: [EMAIL PROTECTED] (Grant Edwards)
Subject: Re: Path to kernel include directory?
Date: Wed, 16 May 2001 13:55:52 GMT
In article <9dtuso$fes$[EMAIL PROTECTED]>, Rene Herman wrote:
>Jim Cochrane wrote:
>
>> I think (and I hope someone more knowledgeable will correct me if I'm
>> wrong) that it's standard for linux distributions to have a symbolic
>> link from the linux include directory to /usr/include/linux.
>
>It's not only standard, it's pretty much *required* to have a set of
>kernel headers in /usr/include/{linux,asm}.
It does have some of them. There is a set of header files in
/usr/include/linux. It appears to be the same files that are in
/usr/src/linux/include.
However my driver includes /usr/src/linux/net/tcp.h. The files under
/usr/src/linux/net are not available via links from /usr/include/whatever.
>Sometimes these directories will be just symlinks to
>/usr/src/linux/include/{linux,asm}, sometimes they will be real directories
>containing the headers from some fixed kernel version that the rest of the
>system was compiled against.
Right, but it's the /usr/src/linux/net directory I'm trying to get to. The
usr/src/linux/include directory isn't a problem since those files are
present in /usr/include/linux.
>I'm not a kernel and/or driver developper, so somebody please correct
>if *I* am wrong, but I believe that driver code should just rely on
>
>#include <linux/...>
>#include <asm/...>
>
>The kernel supplied drivers do. If 3rd party code relies on a very
>specific kernel version (and/or kernel headers from, say, net or scsi),
Why are the kernel header files from net/scsi not made visible in a standard
way?
>I guess it should tell the the person that's building it to dump the
>driver source into that specific tree and use the master kernel
>Makefile to build. The kernel build process will make sure that the
>#include will pick up the version specific headers before looking
>through /usr/include/{linux,asm}
--
Grant Edwards grante Yow! My BIOLOGICAL ALARM
at CLOCK just went off... It
visi.com has noiseless DOZE FUNCTION
and full kitchen!!
------------------------------
From: [EMAIL PROTECTED] (Grant Edwards)
Subject: Re: Path to kernel include directory?
Date: Wed, 16 May 2001 13:59:05 GMT
In article <[EMAIL PROTECTED]>, Kasper Dupont wrote:
>I don't know if there is any standard, but even if there was a standard
>there would be distributions not following it. In RH7.0
>/usr/src/linux/include and /usr/include contained two different versions of
>the header files.
>
>I think you have to rely on either /usr/include or /usr/src/linux/include
>and tell people what to do if they have a version where it doesn't work like
>adding a new symlink.
That's not an option. The driver must compile cleanly and install under
RH7.1 with a simple "make install". That decision's been made by
management. I don't get to tell my customers with RH7.1 to rearrange their
systems.
>Perhaps generating a symlink in your own modules source directory to an
>appropriate include directory would be the most reliable version.
>
>In RH6.0 both /usr/src/linux/include and
>/usr/include works. In RH7.0 only
>/usr/src/linux/include works.
In 7.1 there is no link from /usr/src/linux to /usr/src/linux-<version> That
means my makefile has to work without it.
--
Grant Edwards grante Yow! World War III? No
at thanks!
visi.com
------------------------------
From: "Thorsten Roggendorf" <[EMAIL PROTECTED]>
Subject: Re: Newbie programmer
Date: Wed, 16 May 2001 15:56:45 +0200
Crossposted-To: alt.os.linux.mandrake,comp.os.linux.development.apps
Hi,
what do you want, man?
Write C? C++? Java? Pascal? Tcl/Tk? Python?
If it's C/C++ you have a couple of choices. Do you want an IDE? If so,
you may have to purchase one (borland has one for linux I think).
Tho open source IDEs are being developed but I know of none that
works fine ... yet.
Otherwise you have to start by digging into the seperate tools.
The standard editor for any language is emacs. Well actually it's
vi, but vi is plainly a pain in the ass. With emacs you got a safe bet
and an editor on almost every linux machine. If you wan't more grafic
I'd recommend glimmer. That's an editor for gnome and a nice one at
that. Speaking of gnome - imho a good choice for a desktop. I like it
more than kde (and many developers seem to think likewise, but don't
flame me on that and don't start fighting over it ... ;->).
Then you need a build tool. Read into make but don't go too deep.
After you got some faint ideas about make, read into automake/autoconfig
and libtool. With these three you can build anything (and spend quite some
time reading ...).
If it is to be C/C++ your compiler will be gcc (yaeh, you guessed it -
prepare to read ;->) and you debugger gdb. Except for glimmer all that
stuff is command line and config file driven. ddd is a grafical frontend
for gdb and worth a try (there are others, ddd is just pretty popular).
xemacs is a frontend for emacs (but emacs itself is ok).
I guess with these tools you'll be busy for some time...
Regards
Thorsten
------------------------------
From: [EMAIL PROTECTED] (Grant Edwards)
Subject: Re: Path to kernel include directory?
Date: Wed, 16 May 2001 14:00:35 GMT
In article <NLhM6.997$[EMAIL PROTECTED]>, Grant Edwards wrote:
>One of the drivers I maintain has always used
>/usr/src/linux/include as the path to the kernel include
>directory.
>
>This seemed to work well until RH7.1 (we refused to attempt
>supporting RH7.0). Now there is no /usr/src/linux symbolic
>link installed by the kernel-sources package in RH7.1, and our
>driver won't compile (the first of many problems, I'm sure).
>
>Anyway, if you can't depend on /usr/src/linux/include being
>there anymore, what mechanism do people use to find kernel
>include files?
My original post was slightly incorrect: it's not /usr/src/linux/include I'm
having problems with (that's covered by /usr/include/linux). It's
/usr/src/linux/net/tcp.h that I'm trying to figure out how to find
automagically.
--
Grant Edwards grante Yow! Yow! Is this sexual
at intercourse yet?? Is it,
visi.com huh, is it??
------------------------------
From: Rene Herman <[EMAIL PROTECTED]>
Subject: Re: Formulating Compatibility Signature:
Date: Wed, 16 May 2001 16:02:00 +0200
Adam Shapira wrote:
> Is there any more official way of determining a compatibility
> signature other than using the OS_TYPE and HOSTTYPE environment
> variables?
Parsing the ouput from "uname" I guess. Do a "uname --help", "man
uname" or "info uname" for more information.
Hope this helps.
Rene Herman
------------------------------
From: Derek Viljoen <[EMAIL PROTECTED]>
Subject: Re: Understanding module initialization
Date: Wed, 16 May 2001 09:45:41 -0400
Reply-To: [EMAIL PROTECTED]
I'm not sure about the __initcall_start but my guess is it has to do
with the new macro used to define your module_init/cleanup functions.
Instead of every module defining the same-named function init_module(),
you can now define any named function to be your init:
module_init( my_module_init );
... and its corollary ...
module_exit( my_module_exit );
As for how they are initialized into the kernel, all you really need to
know is these functions are called in response to the modutils package
interactions (insmod, modprobe, rmmod, etc). The .o of your module is
mmap'ed into the kernel's address space, and your init function is
invoked, your symbols are exported and put into the kernel symbol table,
dependent modules are loaded, etc. (Not in this order of course...)
That's really all that you need to know about for most instances.
[EMAIL PROTECTED] wrote:
> I am trying to understand how modules are initialized in the kernel. I can
> see in ../init/main where do_basic_set for things like CONFIG_PCI and other
> constants. After that I see a call to do_initcalls() where I then presume
> the various init_module() routines of all of the modules that are compiled
> into the kernel are called. I can see it calling something called
> __initcall_start which appears defined in vmlinux.lds and appears to be a
> linker control script of some sort. The problem is I don't understand what
> is going on. Perhaps someone might help me out by expressing how this works.
> (And if the answer is 'man xxx', so be it, but I did try).
>
> By extension, the next question relates to modules loaded after the kernel
> boots. Is this the same, or is there some other mechanism at work.
>
> Charles
--
___ __ _ * [EMAIL PROTECTED]
/ ) _ _ _ / / / . / . _ _ _ * (609) 734-3061 (W)
(_/__/ (/_/__(/__/< (_/ /_/_/_(_)_(/_( )__ * ICBM Addr: 39N 58' 21"
_/ * 74W 47' 49"
------------------------------
** 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 by posting to the
comp.os.linux.development.system newsgroup.
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
******************************
