On Mon, 2007-12-03 at 23:45 +0100, Bodo Eggert wrote:
> Jon Masters <[EMAIL PROTECTED]> wrote:
> > On Thu, 2007-11-29 at 11:11 -0800, Ray Lee wrote:
> >> On Nov 29, 2007 10:56 AM, Jon Masters <[EMAIL PROTECTED]> wrote:
> >> > On Thu, 2007-11-29 at 10:4
On Mon, 2007-12-03 at 23:45 +0100, Bodo Eggert wrote:
Jon Masters [EMAIL PROTECTED] wrote:
On Thu, 2007-11-29 at 11:11 -0800, Ray Lee wrote:
On Nov 29, 2007 10:56 AM, Jon Masters [EMAIL PROTECTED] wrote:
On Thu, 2007-11-29 at 10:40 -0800, Ray Lee wrote:
On Nov 29, 2007 9:36 AM, Alan
On Thu, 2007-11-29 at 21:45 +, Alan Cox wrote:
> > Jargon File in all its glory. And if you still think you could look for
> > patterns, how about executable code that self-modifies in random ways
> > but when executed as a whole actually has the functionality of fetchmail
> > embedded within
On Thu, 2007-11-29 at 15:56 -0500, [EMAIL PROTECTED] wrote:
> On Thu, 29 Nov 2007 14:45:51 EST, Jon Masters said:
> > Ah, but I could write a sequence of pages that on their own looked
> > garbage, but in reality, when executed would print out a copy of the
> > Jargon
On Thu, 2007-11-29 at 19:37 +, Nick Warne wrote:
> Hi all,
>
> 2.6.23.9
>
> I have noticed after applying Bart's patch to word93 blacklist my new
> DVD drive:
>
> http://lkml.org/lkml/2007/10/23/475
>
> I see now in logs (look at the hdd line:
>
> [dmesg]
> hdc: 39876480 sectors (20416
On Thu, 2007-11-29 at 11:11 -0800, Ray Lee wrote:
> On Nov 29, 2007 10:56 AM, Jon Masters <[EMAIL PROTECTED]> wrote:
> > On Thu, 2007-11-29 at 10:40 -0800, Ray Lee wrote:
> > > On Nov 29, 2007 9:36 AM, Alan Cox <[EMAIL PROTECTED]> wrote:
> > > > >
On Thu, 2007-11-29 at 10:40 -0800, Ray Lee wrote:
> On Nov 29, 2007 9:36 AM, Alan Cox <[EMAIL PROTECTED]> wrote:
> > > closed. But more importantly further access to it can be blocked until
> > > appropriate actions are taken which also applies with your example, no? Is
> >
> > That bit is hard-
On Thu, 2007-11-29 at 11:19 -0700, Justin Banks wrote:
> Ray Lee wrote
> > On Nov 29, 2007 9:45 AM, Greg KH <[EMAIL PROTECTED]> wrote:
> > > > Perhaps if you looked at this outside of a file-server scenario, the
> > > > problem would be clearer? Anti-malware companies want to check
> > > >
On Thu, 2007-11-29 at 08:47 -0800, Greg KH wrote:
> On Thu, Nov 29, 2007 at 11:36:12AM -0500, Jon Masters wrote:
> > On Wed, 2007-11-28 at 17:07 -0800, Greg KH wrote:
> >
> > > The easiest way is as Al described above, just have the userspace
> > > program t
On Wed, 2007-11-28 at 17:07 -0800, Greg KH wrote:
> The easiest way is as Al described above, just have the userspace
> program that wrote the file to disk, check it then.
But the problem is that this isn't just Samba, this is a countless
myriad of different applications. And if one of them
On Thu, 2007-11-29 at 11:12 +1100, James Morris wrote:
> On Wed, 28 Nov 2007, [EMAIL PROTECTED] wrote:
>
> > So as there is no question the current code does some ugly things it is
> > even more true that we would be even more happy to use an official API.
>
> How about becoming involved in
On Thu, 2007-11-29 at 11:12 +1100, James Morris wrote:
On Wed, 28 Nov 2007, [EMAIL PROTECTED] wrote:
So as there is no question the current code does some ugly things it is
even more true that we would be even more happy to use an official API.
How about becoming involved in creating
On Wed, 2007-11-28 at 17:07 -0800, Greg KH wrote:
The easiest way is as Al described above, just have the userspace
program that wrote the file to disk, check it then.
But the problem is that this isn't just Samba, this is a countless
myriad of different applications. And if one of them
On Thu, 2007-11-29 at 08:47 -0800, Greg KH wrote:
On Thu, Nov 29, 2007 at 11:36:12AM -0500, Jon Masters wrote:
On Wed, 2007-11-28 at 17:07 -0800, Greg KH wrote:
The easiest way is as Al described above, just have the userspace
program that wrote the file to disk, check
On Thu, 2007-11-29 at 11:19 -0700, Justin Banks wrote:
Ray Lee wrote
On Nov 29, 2007 9:45 AM, Greg KH [EMAIL PROTECTED] wrote:
Perhaps if you looked at this outside of a file-server scenario, the
problem would be clearer? Anti-malware companies want to check
anything written to
On Thu, 2007-11-29 at 10:40 -0800, Ray Lee wrote:
On Nov 29, 2007 9:36 AM, Alan Cox [EMAIL PROTECTED] wrote:
closed. But more importantly further access to it can be blocked until
appropriate actions are taken which also applies with your example, no? Is
That bit is hard- very hard.
On Thu, 2007-11-29 at 11:11 -0800, Ray Lee wrote:
On Nov 29, 2007 10:56 AM, Jon Masters [EMAIL PROTECTED] wrote:
On Thu, 2007-11-29 at 10:40 -0800, Ray Lee wrote:
On Nov 29, 2007 9:36 AM, Alan Cox [EMAIL PROTECTED] wrote:
closed. But more importantly further access to it can be blocked
On Thu, 2007-11-29 at 19:37 +, Nick Warne wrote:
Hi all,
2.6.23.9
I have noticed after applying Bart's patch to word93 blacklist my new
DVD drive:
http://lkml.org/lkml/2007/10/23/475
I see now in logs (look at the hdd line:
[dmesg]
hdc: 39876480 sectors (20416 MB) w/2048KiB
On Thu, 2007-11-29 at 15:56 -0500, [EMAIL PROTECTED] wrote:
On Thu, 29 Nov 2007 14:45:51 EST, Jon Masters said:
Ah, but I could write a sequence of pages that on their own looked
garbage, but in reality, when executed would print out a copy of the
Jargon File in all its glory. And if you
On Thu, 2007-11-29 at 21:45 +, Alan Cox wrote:
Jargon File in all its glory. And if you still think you could look for
patterns, how about executable code that self-modifies in random ways
but when executed as a whole actually has the functionality of fetchmail
embedded within it? How
On Tue, 2007-11-27 at 15:49 +1100, Rusty Russell wrote:
> On Monday 26 November 2007 17:15:44 Roland Dreier wrote:
> > It seems pretty
> > clear to me that having a mechanism that requires modules to make
> > explicit which (semi-)internal APIs makes reviewing easier
>
> Perhaps you've got
On Tue, 2007-11-27 at 15:49 +1100, Rusty Russell wrote:
On Monday 26 November 2007 17:15:44 Roland Dreier wrote:
It seems pretty
clear to me that having a mechanism that requires modules to make
explicit which (semi-)internal APIs makes reviewing easier
Perhaps you've got lots of
On Sat, 2007-11-17 at 09:55 -0800, Daniel Walker wrote:
> Sure, you want to split the list?
I'm happy to grab a few of these too. Let me know if either of you or
Ingo is working on the whole lot and about to dump it on us ;-)
Jon.
-
To unsubscribe from this list: send the line "unsubscribe
On Sat, 2007-11-17 at 09:55 -0800, Daniel Walker wrote:
Sure, you want to split the list?
I'm happy to grab a few of these too. Let me know if either of you or
Ingo is working on the whole lot and about to dump it on us ;-)
Jon.
-
To unsubscribe from this list: send the line unsubscribe
On Sat, 2007-11-17 at 01:21 -0500, Steven Rostedt wrote:
> Comments welcomed!
Looks very cool. I was a little apprehensive about the active
synchronous migration/moving runqueues but you seem to have more than
proved your point :-)
Jon.
-
To unsubscribe from this list: send the line
On Sat, 2007-11-17 at 01:21 -0500, Steven Rostedt wrote:
Comments welcomed!
Looks very cool. I was a little apprehensive about the active
synchronous migration/moving runqueues but you seem to have more than
proved your point :-)
Jon.
-
To unsubscribe from this list: send the line
Rusty,
I read your previous email and thought I'd play with it...and then by
the time I got around to having some time tonight you'd already done it.
You're a machine :-) We actually have some other stuff failing at work
due to this exact bug so I will test against RHEL5 tomorrow also.
Jon.
-
On Mon, 2007-11-12 at 03:17 -0500, Jon Masters wrote:
> On Mon, 2007-11-12 at 02:56 +0100, Nick Piggin wrote:
>
> > This is a patch to remove 'nopage' from the tree.
>
> Interesting, but why now? What precipitated this?
Actually reading said patch and thinking helps. I'll go
On Mon, 2007-11-12 at 02:56 +0100, Nick Piggin wrote:
> This is a patch to remove 'nopage' from the tree.
Interesting, but why now? What precipitated this?
Jon.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
On Mon, 2007-11-12 at 02:56 +0100, Nick Piggin wrote:
This is a patch to remove 'nopage' from the tree.
Interesting, but why now? What precipitated this?
Jon.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
On Mon, 2007-11-12 at 03:17 -0500, Jon Masters wrote:
On Mon, 2007-11-12 at 02:56 +0100, Nick Piggin wrote:
This is a patch to remove 'nopage' from the tree.
Interesting, but why now? What precipitated this?
Actually reading said patch and thinking helps. I'll go hide back under
my rock
Rusty,
I read your previous email and thought I'd play with it...and then by
the time I got around to having some time tonight you'd already done it.
You're a machine :-) We actually have some other stuff failing at work
due to this exact bug so I will test against RHEL5 tomorrow also.
Jon.
-
On Fri, 2007-11-09 at 04:35 -0500, bo yang wrote:
> Driver will call cmd completion routine from Reset path without waiting for
> cmd completion from isr context.
Thanks. I'm going to take a look at this, as well as the other recent 2
patches for a couple of test kernels we have that are based
On Fri, 2007-11-09 at 04:35 -0500, bo yang wrote:
Driver will call cmd completion routine from Reset path without waiting for
cmd completion from isr context.
Thanks. I'm going to take a look at this, as well as the other recent 2
patches for a couple of test kernels we have that are based on
On Thu, 2007-11-08 at 13:10 +1100, Rusty Russell wrote:
> On Wednesday 07 November 2007 21:01:30 Jan Glauber wrote:
> > Hi Rusty,
> >
> > I've seen a symbol-resolving race on s390. The qeth module uses symbols
> > from qdio and although the loading order seems correct and the qdio
> > symbols
On Tue, 2007-11-06 at 16:26 -0800, Linus Torvalds wrote:
> It's full of such *riveting* entries like:
>
> James Bottomley:
> x86: voyager: fix bogus conversion to per_cpu for boot_cpu_info
Nobody just happens upon a Voyager quote like that, it takes (at least
some) skill to
On Tue, 2007-11-06 at 16:26 -0800, Linus Torvalds wrote:
It's full of such *riveting* entries like:
James Bottomley:
x86: voyager: fix bogus conversion to per_cpu for boot_cpu_info
Nobody just happens upon a Voyager quote like that, it takes (at least
some) skill to find,
On Thu, 2007-11-08 at 13:10 +1100, Rusty Russell wrote:
On Wednesday 07 November 2007 21:01:30 Jan Glauber wrote:
Hi Rusty,
I've seen a symbol-resolving race on s390. The qeth module uses symbols
from qdio and although the loading order seems correct and the qdio
symbols should be
Hey,
I wouldn't normally post news stories...but in case anyone is living
under a rock, not reading Slashdot, LWN, or one of a bazillion other
news sites that are *bound* to cover this at some point about now...
http://www.groklaw.net/article.php?story=20070914152904577
Have an awesome weekend,
Hey,
I wouldn't normally post news stories...but in case anyone is living
under a rock, not reading Slashdot, LWN, or one of a bazillion other
news sites that are *bound* to cover this at some point about now...
http://www.groklaw.net/article.php?story=20070914152904577
Have an awesome weekend,
On Thu, 2007-09-06 at 08:55 -0400, Neil Horman wrote:
> On Wed, Sep 05, 2007 at 05:39:11PM -0400, Jon Masters wrote:
> > On Wed, 2007-09-05 at 15:27 -0400, Neil Horman wrote:
> >
> > > Now, I suppose its possible that I've not been looking at the right
> > > sou
On Thu, 2007-09-06 at 08:41 +1000, Rusty Russell wrote:
> On Wed, 2007-09-05 at 16:26 -0400, Jon Masters wrote:
> > On Tue, 2007-09-04 at 16:30 -0400, Neil Horman wrote:
> >
> > > 2nd of two patches. This patch enhances modprobe to operate like rmmod
> > > in
On Wed, 2007-09-05 at 15:27 -0400, Neil Horman wrote:
> Now, I suppose its possible that I've not been looking at the right source
> tree
> when doing my work. I've based my modprobe patch on this git tree:
> http://git.kernel.org/?p=linux/kernel/git/kyle/module-init-tools.git;a=summary
> If
On Thu, 2007-09-06 at 06:51 +1000, Rusty Russell wrote:
> On Wed, 2007-09-05 at 15:27 -0400, Neil Horman wrote:
> > On Thu, Sep 06, 2007 at 03:41:37AM +1000, Rusty Russell wrote:
> > > You have this backwards: O_NONBLOCK is the default. That seems to be
> > > what everyone wants, although I
On Tue, 2007-09-04 at 16:30 -0400, Neil Horman wrote:
> 2nd of two patches. This patch enhances modprobe to operate like rmmod
> in non-blocking mode. It also adds a -w option to allow for explicit blocking
> operation.
As I suspected, this patch isn't in the tree. I am going to commit
On Wed, 2007-09-05 at 15:27 -0400, Neil Horman wrote:
> Now, I suppose its possible that I've not been looking at the right source
> tree
> when doing my work. I've based my modprobe patch on this git tree:
> http://git.kernel.org/?p=linux/kernel/git/kyle/module-init-tools.git;a=summary
> If
On Thu, 2007-09-06 at 03:41 +1000, Rusty Russell wrote:
> On Wed, 2007-09-05 at 13:08 -0400, Neil Horman wrote:
> > On Thu, Sep 06, 2007 at 02:13:26AM +1000, Rusty Russell wrote:
> > > On Wed, 2007-09-05 at 17:22 +0200, Patrick McHardy wrote:
> > > > But I'm wondering, wouldn't module refcounting
On Thu, 2007-09-06 at 03:41 +1000, Rusty Russell wrote:
On Wed, 2007-09-05 at 13:08 -0400, Neil Horman wrote:
On Thu, Sep 06, 2007 at 02:13:26AM +1000, Rusty Russell wrote:
On Wed, 2007-09-05 at 17:22 +0200, Patrick McHardy wrote:
But I'm wondering, wouldn't module refcounting alone fix
On Wed, 2007-09-05 at 15:27 -0400, Neil Horman wrote:
Now, I suppose its possible that I've not been looking at the right source
tree
when doing my work. I've based my modprobe patch on this git tree:
http://git.kernel.org/?p=linux/kernel/git/kyle/module-init-tools.git;a=summary
If theres
On Tue, 2007-09-04 at 16:30 -0400, Neil Horman wrote:
2nd of two patches. This patch enhances modprobe to operate like rmmod
in non-blocking mode. It also adds a -w option to allow for explicit blocking
operation.
As I suspected, this patch isn't in the tree. I am going to commit it
On Thu, 2007-09-06 at 06:51 +1000, Rusty Russell wrote:
On Wed, 2007-09-05 at 15:27 -0400, Neil Horman wrote:
On Thu, Sep 06, 2007 at 03:41:37AM +1000, Rusty Russell wrote:
You have this backwards: O_NONBLOCK is the default. That seems to be
what everyone wants, although I implemented
On Wed, 2007-09-05 at 15:27 -0400, Neil Horman wrote:
Now, I suppose its possible that I've not been looking at the right source
tree
when doing my work. I've based my modprobe patch on this git tree:
http://git.kernel.org/?p=linux/kernel/git/kyle/module-init-tools.git;a=summary
If theres
On Sat, 2007-06-09 at 15:59 +0200, Jan Engelhardt wrote:
> On Jun 9 2007 08:08, Jon Masters wrote:
> >
> >So I missed half of this conversation - you're saying that on a
> >CONFIG_DEBUG_KERNEL, you have such large .ko module files that depmod
> >segfaults? Can I get
On Sat, 2007-06-09 at 09:55 +0200, Jan Engelhardt wrote:
> On Jun 8 2007 08:40, Robert P. J. Day wrote:
> >>
> >> If you disable CONFIG_DEBUG_KERNEL, things should go back to normal
> >> sizes for you.
> >
> >grow so much compared to *which other modules*? the ones that came
> >with your distro?
On Sat, 2007-06-09 at 09:55 +0200, Jan Engelhardt wrote:
On Jun 8 2007 08:40, Robert P. J. Day wrote:
If you disable CONFIG_DEBUG_KERNEL, things should go back to normal
sizes for you.
grow so much compared to *which other modules*? the ones that came
with your distro? if that's the
On Sat, 2007-06-09 at 15:59 +0200, Jan Engelhardt wrote:
On Jun 9 2007 08:08, Jon Masters wrote:
So I missed half of this conversation - you're saying that on a
CONFIG_DEBUG_KERNEL, you have such large .ko module files that depmod
segfaults? Can I get a core dump or any further information
On Fri, 2007-06-08 at 17:16 +0200, Jan Engelhardt wrote:
> So, we had some ISO8859-1 and some UTF-8 in there already. (And as for
> MODULE_AUTHOR, it should stay there - 'fix' modinfo instead.)
Ok.
Jon.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Fri, 2007-06-08 at 17:16 +0200, Jan Engelhardt wrote:
So, we had some ISO8859-1 and some UTF-8 in there already. (And as for
MODULE_AUTHOR, it should stay there - 'fix' modinfo instead.)
Ok.
Jon.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
On Fri, 2007-06-08 at 02:04 +0200, Adrian Bunk wrote:
> The difference is that "ls" expects and handles such issues while
> "lsmod" (and most likely also other userspace working with kernel
> output) does not yet handle it resulting in problems if bytes are
> wrongly interpreted as control
On Fri, 2007-06-08 at 02:04 +0200, Adrian Bunk wrote:
The difference is that ls expects and handles such issues while
lsmod (and most likely also other userspace working with kernel
output) does not yet handle it resulting in problems if bytes are
wrongly interpreted as control codes.
I'm
On Mon, 2007-05-14 at 21:44 +0200, Jan-Benedict Glaw wrote:
> On Fri, 2007-05-11 10:06:17 +0200, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> wrote:
> > Jesper Juhl wrote:
> > > On 10/05/07, Shahbaz Khan <[EMAIL PROTECTED]> wrote:
> > why not adding a link to every kernel an kernel.org kernel,
> >
On Mon, 2007-05-14 at 21:44 +0200, Jan-Benedict Glaw wrote:
On Fri, 2007-05-11 10:06:17 +0200, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Jesper Juhl jesper.juhl () gmail ! com wrote:
On 10/05/07, Shahbaz Khan [EMAIL PROTECTED] wrote:
why not adding a link to every kernel an kernel.org
Jon Masters wrote:
Sergey Vlasov wrote:
Has a final decision about generated files been made? I don't see any
updates in the git repo, and man pages are still broken
I'm doing some patching this afternoon anyway, and it's on my todo.
I pushed up v3.3-pre11 just now. If all goes to plan
Jon Masters wrote:
Sergey Vlasov wrote:
Has a final decision about generated files been made? I don't see any
updates in the git repo, and man pages are still broken
I'm doing some patching this afternoon anyway, and it's on my todo.
I pushed up v3.3-pre11 just now. If all goes to plan
Sergey Vlasov wrote:
Has a final decision about generated files been made? I don't see any
updates in the git repo, and man pages are still broken
I'm doing some patching this afternoon anyway, and it's on my todo.
Jon.
-
To unsubscribe from this list: send the line "unsubscribe
Sergey Vlasov wrote:
Has a final decision about generated files been made? I don't see any
updates in the git repo, and man pages are still broken
I'm doing some patching this afternoon anyway, and it's on my todo.
Jon.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
Tejun Heo wrote:
Please take a look at the JMB quirk in drivers/pci/quirks.c in the
latest libata-dev#upstream tree for details.
For interest, I will, thanks for the info.
Jon.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Tejun Heo wrote:
Jon Masters wrote:
Chuck Ebbert wrote:
If you try to load both the pata_atiixp and the ahci driver
(for the same ATI SB600 adapter), very strange things happen.
The AHCI driver churns for three minutes or so, spewing
messages like this, then nothing works:
<6>ata3: SAT
Tejun Heo wrote:
Jon Masters wrote:
Chuck Ebbert wrote:
If you try to load both the pata_atiixp and the ahci driver
(for the same ATI SB600 adapter), very strange things happen.
The AHCI driver churns for three minutes or so, spewing
messages like this, then nothing works:
6ata3: SATA link
Tejun Heo wrote:
Please take a look at the JMB quirk in drivers/pci/quirks.c in the
latest libata-dev#upstream tree for details.
For interest, I will, thanks for the info.
Jon.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Chuck Ebbert wrote:
If you try to load both the pata_atiixp and the ahci driver
(for the same ATI SB600 adapter), very strange things happen.
The AHCI driver churns for three minutes or so, spewing
messages like this, then nothing works:
<6>ata3: SATA link up 3.0 Gbps (SStatus 123 SControl
Chuck Ebbert wrote:
If you try to load both the pata_atiixp and the ahci driver
(for the same ATI SB600 adapter), very strange things happen.
The AHCI driver churns for three minutes or so, spewing
messages like this, then nothing works:
6ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan Engelhardt wrote:
Out of the box perhaps if it is the .tar.bz2 archive, but the same does not
always hold for CVS repos, much less SVNs [random guess on svn]. He who pulls
from a developer tree mostly knows to run 'autogen.sh' or 'autoreconf -fi'
beforehand.
You know what, you're right of
Jan Engelhardt wrote:
Out of the box perhaps if it is the .tar.bz2 archive, but the same does not
always hold for CVS repos, much less SVNs [random guess on svn]. He who pulls
from a developer tree mostly knows to run 'autogen.sh' or 'autoreconf -fi'
beforehand.
You know what, you're right of
Luiz Fernando N. Capitulino wrote:
On Thu, 22 Feb 2007 09:52:20 -0500
Jon Masters <[EMAIL PROTECTED]> wrote:
| Sergey Vlasov wrote:
|
| > I see that you have merged some patches which change depmod.8.
| > However, this file is generated from doc/depmod.sgml, which was not
Luiz Fernando N. Capitulino wrote:
On Thu, 22 Feb 2007 09:52:20 -0500
Jon Masters [EMAIL PROTECTED] wrote:
| Sergey Vlasov wrote:
|
| I see that you have merged some patches which change depmod.8.
| However, this file is generated from doc/depmod.sgml, which was not
| changed appropriately
Sergey Vlasov wrote:
I see that you have merged some patches which change depmod.8.
However, this file is generated from doc/depmod.sgml, which was not
changed appropriately.
Ah. A valid point - Luiz, do you want to redo your patch or I can take a
look at the SGML source myself.
Jon.
-
To
Sergey Vlasov wrote:
I see that you have merged some patches which change depmod.8.
However, this file is generated from doc/depmod.sgml, which was not
changed appropriately.
Ah. A valid point - Luiz, do you want to redo your patch or I can take a
look at the SGML source myself.
Jon.
-
To
Yo,
After some delay[0] I have uploaded a new version of module-init-tools
to http://www.kerneltools.org/
This release mostly has a bunch of build fixes, some memory leakage
cleanups that will benefit systems that actually run out of memory
(embedded, etc.) and various other things in the
Yo,
After some delay[0] I have uploaded a new version of module-init-tools
to http://www.kerneltools.org/
This release mostly has a bunch of build fixes, some memory leakage
cleanups that will benefit systems that actually run out of memory
(embedded, etc.) and various other things in the
Alan wrote:
On Sat, 3 Feb 2007 21:47:36 +0100 (MET)
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
On Feb 3 2007 10:31, David Schwartz wrote:
The way out of the GPL problem is to make clear that it is *not* a
copyright enforcement scheme
So why do we have EXPORT_SYMBOL_GPL then, if
Because if
Alan wrote:
On Sat, 3 Feb 2007 21:47:36 +0100 (MET)
Jan Engelhardt [EMAIL PROTECTED] wrote:
On Feb 3 2007 10:31, David Schwartz wrote:
The way out of the GPL problem is to make clear that it is *not* a
copyright enforcement scheme
So why do we have EXPORT_SYMBOL_GPL then, if
Because if you
[EMAIL PROTECTED] wrote:
"With 100 million computers in use today, we should expect roughly 6 million
single bit errors per year. Computer hardware and software companies must
receive thousands of "side effect" bug reports and support calls due to memory
errors alone. The costs of NOT including
Arjan van de Ven wrote:
But you're right, the MODULE_LICENSE tag really does imply that
licenses other than the GPL are ok.
yup.. BSD licensed modules are clearly ok as well..
So I guess we're going to go with Jan's change then.
I just wanted to discuss this briefly since I'm very keen for
Jan Engelhardt wrote:
Proposed patch to prohibit loading modules that use early C string
termination ("GPL\0 for nothing, folks!") to trick the kernel believing
it is loading a GPL driver.
Ok. I totally dig the *idea* here - I mean, this issue has been ongoing
for a long time now. But I'd
Andrew Morton wrote:
No, I was thinking of a record which explicitly mentions module-init-tools.
It's not a part of the kernel, but it is closely connected to it, and this is
useful information to have in ./MAINTAINERS.
Ah, now that makes more sense. I was thinking you were thinking of an
On Wed, Jan 31, 2007 at 11:17:31PM -0800, Andrew Morton wrote:
> On Thu, 01 Feb 2007 01:28:59 -0500 Jon Masters <[EMAIL PROTECTED]> wrote:
> > I took over upstream maintainership of the module-init-tools package
> > from Rusty at the end of last year.
> Cool.
Jon Masters has taken over upstream maintainership of module-init-tools from
Rusty, update MAINTAINERS file to reflect this change and to provide
information about the location of new releases and the mailing list.
Signed-off-by: Jon Masters <[EMAIL PROTECTED]>
---
MAINTAINERS |7
Jon Masters has taken over upstream maintainership of module-init-tools from
Rusty, update MAINTAINERS file to reflect this change and to provide
information about the location of new releases and the mailing list.
Signed-off-by: Jon Masters [EMAIL PROTECTED]
---
MAINTAINERS |7 ---
1
On Wed, Jan 31, 2007 at 11:17:31PM -0800, Andrew Morton wrote:
On Thu, 01 Feb 2007 01:28:59 -0500 Jon Masters [EMAIL PROTECTED] wrote:
I took over upstream maintainership of the module-init-tools package
from Rusty at the end of last year.
Cool. A patch to the kernel's ./MAINTAINERS would
Andrew Morton wrote:
No, I was thinking of a record which explicitly mentions module-init-tools.
It's not a part of the kernel, but it is closely connected to it, and this is
useful information to have in ./MAINTAINERS.
Ah, now that makes more sense. I was thinking you were thinking of an
Jan Engelhardt wrote:
Proposed patch to prohibit loading modules that use early C string
termination (GPL\0 for nothing, folks!) to trick the kernel believing
it is loading a GPL driver.
Ok. I totally dig the *idea* here - I mean, this issue has been ongoing
for a long time now. But I'd
Arjan van de Ven wrote:
But you're right, the MODULE_LICENSE tag really does imply that
licenses other than the GPL are ok.
yup.. BSD licensed modules are clearly ok as well..
So I guess we're going to go with Jan's change then.
I just wanted to discuss this briefly since I'm very keen for
[EMAIL PROTECTED] wrote:
With 100 million computers in use today, we should expect roughly 6 million
single bit errors per year. Computer hardware and software companies must
receive thousands of side effect bug reports and support calls due to memory
errors alone. The costs of NOT including
Yo,
I took over upstream maintainership of the module-init-tools package
from Rusty at the end of last year. At this point, there's a public
wiki, new pre-release, bugzilla and all that jazz up and running:
http://www.kerneltools.org/ has links to the latest release.
There's a mailing list,
Yo,
I took over upstream maintainership of the module-init-tools package
from Rusty at the end of last year. At this point, there's a public
wiki, new pre-release, bugzilla and all that jazz up and running:
http://www.kerneltools.org/ has links to the latest release.
There's a mailing list,
On Apr 7, 2005 6:54 PM, Daniel Phillips <[EMAIL PROTECTED]> wrote:
> So I propose that everybody who is interested, pick one of the above projects
> and join it, to help get it to the point of being able to losslessly import
> the version graph. Given the importance, I think that _all_ viable
>
On Apr 7, 2005 6:54 PM, Daniel Phillips [EMAIL PROTECTED] wrote:
So I propose that everybody who is interested, pick one of the above projects
and join it, to help get it to the point of being able to losslessly import
the version graph. Given the importance, I think that _all_ viable
On Apr 6, 2005 4:42 PM, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> as a number of people are already aware (and in some
> cases have been aware over the last several weeks), we've
> been trying to work out a conflict over BK usage over the last
> month or two (and it feels like longer ;). That
On Apr 6, 2005 4:42 PM, Linus Torvalds [EMAIL PROTECTED] wrote:
as a number of people are already aware (and in some
cases have been aware over the last several weeks), we've
been trying to work out a conflict over BK usage over the last
month or two (and it feels like longer ;). That hasn't
701 - 800 of 816 matches
Mail list logo
