From: Martin Dalecki <dalecki@evision-ventures.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>, linux-kernel@vger.kernel.org
Subject: Re: kbuild 2.5 is ready for inclusion in the 2.5 kernel
Date: Thu, 02 May 2002 18:53:23 +0200 [thread overview]
Message-ID: <3CD16F03.9090900@evision-ventures.com> (raw)
In-Reply-To: <E173HX6-00041D-00@the-village.bc.nu> <3CD13FF3.5020406@evision-ventures.com> <3CD15996.8EB1699F@redhat.com> <200205021559.g42Fxud19755@vindaloo.ras.ucalgary.ca> <3CD15CFA.1090208@evision-ventures.com> <20020502132552.G8073@devserv.devel.redhat.com>
Uz.ytkownik Arjan van de Ven napisa?:
>
>>It just DOES NOT BELONG in to the kernel-space.
>
>
> That's why it's done by modutils.
>
Last time I checked on Linux:
[root@kozaczek j2me]# ls -l /proc/ksyms
-r--r--r-- 1 root root 0 Mai 2 19:42 /proc/ksyms
Compare this with the following on Solaris:
www01:/kernel/drv# ls sy sy.conf
sy sy.conf
www01:/kernel/drv# file sy
sy: ELF 32-bit MSB relocatable SPARC Version 1
www01:/kernel/drv# cat sy.conf
#
# Copyright (c) 1992, by Sun Microsystems, Inc.
#
#ident "@(#)sy.conf 1.4 93/06/03 SMI"
name="sy" parent="pseudo" instance=0;
www01:/kernel/drv#
www01:/kernel/drv# nm sy
0000000000000014 T _fini
0000000000000028 T _info
0000000000000000 T _init
U cdev_ioctl
U cdev_poll
U cdev_read
U cdev_write
....
0000000000000278 T syclose
0000000000000488 T syioctl
0000000000000140 T syopen
00000000000005b0 T sypoll
0000000000000280 T syread
0000000000000384 T sywrite
www01:/kernel/drv# strings sy
Indirect driver for tty 'sy'
www01:/kernel/drv#
And then think about the fact that they are able to even *patch*
running kernels. There is no way I can be convinced that the whole
versioning stuff is neccessary or a good design for any purpose.
next prev parent reply other threads:[~2002-05-02 17:56 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 14:23 kbuild 2.5 is ready for inclusion in the 2.5 kernel Keith Owens
2002-05-02 15:17 ` Denis Vlasenko
2002-05-02 10:38 ` tomas szepe
2002-05-02 12:21 ` Keith Owens
2002-05-02 12:49 ` Martin Dalecki
2002-05-02 14:26 ` Alan Cox
2002-05-02 13:32 ` Martin Dalecki
2002-05-02 14:54 ` Kai Germaschewski
2002-05-02 15:17 ` Alan Cox
2002-05-05 9:43 ` Mike Fedyk
2002-05-05 10:16 ` Keith Owens
2002-05-02 15:21 ` Arjan van de Ven
2002-05-02 15:59 ` Richard Gooch
2002-05-02 15:36 ` Martin Dalecki
2002-05-02 17:15 ` Alan Cox
2002-05-02 16:30 ` Martin Dalecki
2002-05-02 18:20 ` Alan Cox
2002-05-02 17:25 ` Arjan van de Ven
2002-05-02 16:53 ` Martin Dalecki [this message]
2002-05-02 17:48 ` David S. Miller
2002-05-02 17:42 ` Martin Dalecki
2002-05-02 19:11 ` Alan Cox
2002-05-02 18:22 ` Martin Dalecki
2002-05-02 18:49 ` David S. Miller
2002-05-02 18:33 ` Alan Cox
2002-05-02 14:24 ` Kai Germaschewski
2002-05-02 15:18 ` David Woodhouse
2002-05-02 15:40 ` Kai Germaschewski
2002-05-02 23:40 ` Keith Owens
2002-05-02 23:25 ` Martin Dalecki
2002-05-03 14:48 ` Kai Germaschewski
2002-05-03 15:45 ` Keith Owens
2002-05-02 15:19 ` Alan Cox
2002-05-02 22:57 ` Pavel Machek
2002-05-03 8:33 ` Vikram
2002-05-03 12:07 ` Keith Owens
2002-05-18 1:14 ` Andrea Arcangeli
2002-05-18 1:33 ` Dave Jones
2002-05-18 3:06 ` Oliver Xymoron
2002-05-18 12:28 ` [PATCH] move jiffies from sched.h to it's own jiffies.h Tim Schmielau
2002-05-19 22:33 ` Tim Schmielau
2002-05-20 2:32 ` Rusty Russell
2002-05-18 2:12 ` kbuild 2.5 is ready for inclusion in the 2.5 kernel Gerhard Mack
2002-05-18 2:13 ` Keith Owens
2002-05-18 2:30 ` Andrea Arcangeli
2002-05-20 2:38 ` Miles Bader
2002-05-02 21:34 ` tomas szepe
2002-05-02 21:42 ` Dave Jones
2002-05-03 1:19 ` John Covici
2002-05-03 1:33 ` Keith Owens
2002-05-03 1:39 ` tomas szepe
2002-05-03 2:31 ` Alexander Viro
2002-05-03 3:21 ` Davide Libenzi
2002-05-02 21:42 ` Alexander Viro
2002-05-02 23:25 ` tomas szepe
2002-05-03 21:05 ` Mark H. Wood
2002-05-04 13:58 ` Kurt Wall
2002-05-06 1:54 ` Mike Fedyk
2002-05-02 22:54 ` Pavel Machek
2002-05-03 9:00 ` Keith Owens
2002-05-03 4:17 ` Randy.Dunlap
2002-05-03 5:02 ` Keith Owens
2002-05-03 6:32 ` Randy.Dunlap
2002-05-03 10:06 ` Gerd Knorr
2002-05-03 10:42 ` Keith Owens
2002-05-03 12:05 ` Gerd Knorr
2002-05-03 13:31 ` Keith Owens
2002-05-04 6:44 ` Paul Mackerras
2002-05-04 8:03 ` Paul Mackerras
2002-05-06 0:42 ` Mike Fedyk
2002-05-06 4:07 ` Paul Mackerras
2002-05-04 9:03 ` Keith Owens
2002-05-04 9:38 ` Russell King
2002-05-04 10:33 ` Paul Mackerras
2002-05-04 11:49 ` Keith Owens
2002-05-06 8:40 ` Gerd Knorr
2002-05-07 4:14 ` Keith Owens
2002-05-04 15:30 ` Richard Gooch
2002-05-05 17:23 ` Urban Widmark
2002-05-05 23:36 ` Keith Owens
2002-05-06 11:33 ` Urban Widmark
2002-05-06 23:54 ` Keith Owens
2002-05-06 10:54 ` Alex Riesen
2002-05-08 2:54 ` Keith Owens
2002-05-08 17:25 ` Alex Riesen
2002-05-09 0:10 ` Keith Owens
2002-05-09 0:55 ` Daniel Jacobowitz
2002-05-09 1:44 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2002-05-05 16:42 Dan Kegel
2002-05-05 23:44 ` Keith Owens
2002-05-06 0:02 ` Dan Kegel
2002-05-06 0:40 ` Keith Owens
2002-05-06 15:38 ` Alan Cox
2002-05-06 15:33 ` Tomas Szepe
[not found] <cs.lists.linux-kernel/18740.1020729269@ocs3.intra.ocs.com.au>
2002-05-07 23:48 ` Ion Badulescu
2002-05-08 0:10 ` Keith Owens
2002-05-08 0:37 ` Alan Cox
2002-05-08 0:34 ` Keith Owens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CD16F03.9090900@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox