-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fabian LoneStar Frédérick wrote:
> Hi,
>
> Do we have recursive dnotification facility in current kernel ?
>
> (cc me please).
>
> Best regards,
> Fabian
>
google inotify
- --
[Name ] :: [Matan I. Peled]
[Location ] ::
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fabian LoneStar Frédérick wrote:
Hi,
Do we have recursive dnotification facility in current kernel ?
(cc me please).
Best regards,
Fabian
google inotify
- --
[Name ] :: [Matan I. Peled]
[Location ] :: [Israel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Schau wrote:
> Hi Denis/All,
>
>
> I see the error in 2.6.12 as well (I just tried it). My setup ...
>
> Zyxel ZyAir B-100 pcmcia wireless card.
> D-Link AccessPoint.
>
>
> /brian
>
>
> Denis Vlasenko wrote:
>
>> On Saturday 30 July
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Schau wrote:
Hi Denis/All,
I see the error in 2.6.12 as well (I just tried it). My setup ...
Zyxel ZyAir B-100 pcmcia wireless card.
D-Link AccessPoint.
/brian
Denis Vlasenko wrote:
On Saturday 30 July 2005 17:54, Brian
Marcondes Monteiro de Arau wrote:
> Hi!
>
> I'm university student in Brazil and would like to know if during the process
> of compilation of the kernel of the linux the tecnology of cluster is used.
>
>
>
> Marcondes
>
Are you talking about using a cluster to compile the kernel? In that
Marcondes Monteiro de Arau wrote:
Hi!
I'm university student in Brazil and would like to know if during the process
of compilation of the kernel of the linux the tecnology of cluster is used.
Marcondes
Are you talking about using a cluster to compile the kernel? In that case,
Jon Smirl wrote:
> ODSL could then GPL the code and quiet the
> critics.
And also cause aaid GPL'ed code to be immediatly ported over to Windows. I don't
think BitMover could ever agree to that.
--
[Name ] :: [Matan I. Peled]
[Location ] :: [Israel]
[Public Key] ::
Jon Smirl wrote:
ODSL could then GPL the code and quiet the
critics.
And also cause aaid GPL'ed code to be immediatly ported over to Windows. I don't
think BitMover could ever agree to that.
--
[Name ] :: [Matan I. Peled]
[Location ] :: [Israel]
[Public Key] ::
Jacek Luczak wrote:
>
> Hi
>
> Early morning i made a 2.6.12-rc1 with RT-V0.7.43-05 and this is what I
> sow in dmesg after 6 hours of computers work:
>
>
Hmm... A lot of that seems to involve ndiswrapper. Is there any way you could
reproduce this without ndiswrapper loaded?
--
[Name ]
Jacek Luczak wrote:
Hi
Early morning i made a 2.6.12-rc1 with RT-V0.7.43-05 and this is what I
sow in dmesg after 6 hours of computers work:
SNIP!
Hmm... A lot of that seems to involve ndiswrapper. Is there any way you could
reproduce this without ndiswrapper loaded?
--
[Name ]
Bill Davidsen wrote:
I have to see what that generates. The problem is LOCALVERSION and current
use of both 3 and 4 field kernel versions. You need a smarter script to
handle that.
... To which the knee jerk solution would be ...
Name Linus's kernel releases 2.6.z.0 ... ?
--
[Name ] ::
Bill Davidsen wrote:
I have to see what that generates. The problem is LOCALVERSION and current
use of both 3 and 4 field kernel versions. You need a smarter script to
handle that.
... To which the knee jerk solution would be ...
Name Linus's kernel releases 2.6.z.0 ... ?
--
[Name ] ::
Arnd Bergmann wrote:
Nothing about the init command seems really necessary. Why not just do
that stuff from an /sbin/init script?
I'm not a kernel hacker by any definition, but I'm pretty sure its neccasery
because we want it to be done before /sbin/init is ran, AKA hide the kernel
messages :)
Arnd Bergmann wrote:
Nothing about the init command seems really necessary. Why not just do
that stuff from an /sbin/init script?
I'm not a kernel hacker by any definition, but I'm pretty sure its neccasery
because we want it to be done before /sbin/init is ran, AKA hide the kernel
messages :)
Mark McPherson wrote:
Hello all,
I have a Shuttle XPC with an nForce2 chipset.
Here's something which shows up in dmesg after booting
2.6.5-rc2-mm5; it does not appear in the Linux tree up through
2.6.5-rc2-bk9.
My external IEEE1394 drive attaches and detaches and
transfers data without apparent
Mark McPherson wrote:
Hello all,
I have a Shuttle XPC with an nForce2 chipset.
Here's something which shows up in dmesg after booting
2.6.5-rc2-mm5; it does not appear in the Linux tree up through
2.6.5-rc2-bk9.
My external IEEE1394 drive attaches and detaches and
transfers data without apparent
kernel-2.6.11-rc1-bk5 stops booting after the message
^
"Brought up 4 CPU'S"
Something makes me think that this message is not about the fact that the linux
kernel found 4 logical CPUs, but that it stopped after the message was shown :)
A .config would be nice, maybe
kernel-2.6.11-rc1-bk5 stops booting after the message
^
Brought up 4 CPU'S
Something makes me think that this message is not about the fact that the linux
kernel found 4 logical CPUs, but that it stopped after the message was shown :)
A .config would be nice, maybe a
18 matches
Mail list logo
