It's working fine here w/o modification. Maybe you need the latest
version or have somethinn enabled that I don't.
Gianluca Anzolin wrote:
>
> it seems there has been a change in the format of the /proc/cpuinfo file: infact
>'flags: ' became 'features: '
>
> This change broke xmms and could
On Sun, 19 Nov 2000, Jeff V. Merkey wrote:
> > o Small ISDN documentation fixes (Kai Germaschewski)
>
> Alan, On the ISDN issue, isdn4K-utils seems to be out of sync with
> kernels older than 2.2.16. Some #define's that used to be in
> the 2.2.14 patch don't seem to be in
In article <[EMAIL PROTECTED]> you write:
>On Sun, 19 Nov 2000, Alexander Viro wrote:
>> On Sun, 19 Nov 2000, David Lang wrote:
>> > there is a rootkit kernel module out there that, if loaded onto your
>> > system, can make it almost impossible to detect that your system has been
>> >
On Sun, 19 Nov 2000, Alexander Viro wrote:
> On Sun, 19 Nov 2000, David Lang wrote:
> > there is a rootkit kernel module out there that, if loaded onto your
> > system, can make it almost impossible to detect that your system has been
> > compramised. with module support disabled this isn't
Three small patches against test11-pre7
1) creates arch_init_modules(), removes alpha specific code from
module.c
2) makes non-modular try_inc_use_count() an inline for better
optimization.
3) Creates __modinfo define.
--
Brian Gerst
diff -urN
Markus Schoder wrote:
>
> --- Linus Torvalds <[EMAIL PROTECTED]> schrieb: >
>
> >
> > On Sat, 18 Nov 2000, adrian wrote:
> >
> > >
> > >
> > > On Sat, 18 Nov 2000, Linus Torvalds wrote:
> > >
> > > > There's almost certainly more than that. I'd
> > love to have a report on my
> > > > asm-only
On Sun, 19 Nov 2000 07:16:52 -0800 (PST),
David Lang <[EMAIL PROTECTED]> wrote:
>there is a rootkit kernel module out there that, if loaded onto your
>system, can make it almost impossible to detect that your system has been
>compramised. with module support disabled this isn't possible.
Wrong.
On Sun, 19 Nov 2000, David Lang wrote:
> there is a rootkit kernel module out there that, if loaded onto your
> system, can make it almost impossible to detect that your system has been
> compramised. with module support disabled this isn't possible.
Yes, it is. Easily. If you've got root you
-BEGIN PGP SIGNED MESSAGE-
there is a rootkit kernel module out there that, if loaded onto your
system, can make it almost impossible to detect that your system has been
compramised. with module support disabled this isn't possible.
if you have dynamic hardware, then yes it's nice to be
it seems there has been a change in the format of the /proc/cpuinfo file: infact
'flags: ' became 'features: '
This change broke xmms and could broke any other program which relies on
/proc/cpuinfo...
I hope the problem will be solved (in the kernel or in every other program which uses
Hi!
Thanks for the fast reply - but I can't follow. What is the _tuning
aspect_ and how is it modified?
Andre Hedrick <[EMAIL PROTECTED]> wrote:
>
> There is a problem that it does not downgrade the IO if all you have is
> iCRC errors. The threshold is 10 events without other errors and it
>
On 19 Nov 2000 12:56:17 GMT,
[EMAIL PROTECTED] (Gerd Knorr) wrote:
>Some generic way to make module args available as kernel args too
>would be nice. Or at least some simple one-liner I could put next to
>the MODULE_PARM() macro...
On my list for 2.5. If foo is declared as MODULE_PARM in
On Sun, Nov 19, 2000 at 07:24:16PM +0900, GOTO Masanori wrote:
> At Mon, 13 Nov 2000 11:13:19 -0500,
> Jakub Jelinek <[EMAIL PROTECTED]> wrote:
> > ago were done in the kernel, POSIX message queue passing is not doable in
> > userland without kernel help either (I have a message queue filesystem
> > Why? What is the point in compiling bttv statically into the kernel?
> > Unlike filesystems/ide/scsi/... you don't need it to get the box up.
> > No problem to compile the driver as module and configure it with
> > /etc/modules.conf ...
>
> Huh?
>
> Some systems are built without module
Eric W. Biederman wrote:
> The code wasn't trivially reusable, and the structures had a lot
> of overhead.
There's some overhead, but I think it's not too bad. I'll give it a
try ...
> The rebooting is done the rest is not yet.
Ah, and I already wondered where in all the APIC code you've
On Sun, Nov 19, 2000 at 03:39:43AM -0800, George Garvey wrote:
> Is this something to be concerned about? It sounds like a disaster waiting
> to happen from the message. This is on 2 systems (with similar disk setups
> [same other than size]).
> Nov 18 16:31:02 mwg kernel: md: serializing
> > > protocol for USB communication being diluted down. Realize that a 1KB
> > > block has 4 times the overhead of a 4KB block (on a per-byte-of-data
> > > basis). The usb-storage driver attempts to get the SCSI layer to give it
That guess would be dubious. Its also not IMHO enough to
> > o Fix file/block when spacing to tape beginning (Kai Maiksara)
> > o Small ISDN documentation fixes (Kai Germaschewski)
>
> Alan, On the ISDN issue, isdn4K-utils seems to be out of sync with=20
> kernels older than 2.2.16. Some #define's that used to be in
> the
Linus Torvalds wrote:
>
> ...
> But the algorithm itself should allow for other values. In fact, I think
> that you'll find that it works fine if you switch to non-exclusive
> wait-queues, and the only reason you see the repeatable D states is
> exactly the case where we didn't "take" the
> I'm getting '__alloc_pages: 7-order allocation failed.' every time I
> play something to my maestro card (using the maestro kernel module,
> with dsps_order=2)..
Its a debugging message.
> for (order = (dsps_order + (16-PAGE_SHIFT) + 1); order >= (dsps_order + 2 + 1);
>order--)
>
On Sun, Nov 19, 2000 at 03:39:43AM -0800, George Garvey wrote:
> Is this something to be concerned about? It sounds like a disaster waiting
> to happen from the message. This is on 2 systems (with similar disk setups
> [same other than size]).
Nothing to worry. (I got worried also when
Same problem as Vincent - OOPs when "ls" a mounted cdrom. It did work
once with a CD-R. My report symptoms are nearly identical to previous
post with same subject heading with a few differences:
[4.] Kernel version (from /proc/version):
Linux version 2.4.0-test11 (root@svcr-adsl) (gcc driver
Eric W. Biederman wrote:
> Hmm. What does it take to mount an NFS partition?
Mainly Sun RPC :-(
> Anyway. All I did was wrote a tiny libc that is just a bunch of
> wrappers for syscalls, and some string functions.
Certainly a good approach. It's also basically the idea behind newlib,
although
>= Original Message From [EMAIL PROTECTED] (Eric W. Biederman) =
>Werner Almesberger <[EMAIL PROTECTED]> writes:
>
>> Eric W. Biederman wrote:
>> > I have one that loads a second kernel over the network using dhcp
>> > to configure it's interface and tftp to fetch the image and boots
>> >
Tom Leete wrote:
>
> Hi,
>
> The second and third arguments of get_joliet_filename() are swapped.
>
> Tom
>
> --- linux-2.4.0-test11/fs/isofs/namei.c.origSat Nov 18 01:55:55 2000
> +++ linux-2.4.0-test11/fs/isofs/namei.c Sat Nov 18 07:08:05 2000
> @@ -127,7 +127,7 @@
>
Is this something to be concerned about? It sounds like a disaster waiting
to happen from the message. This is on 2 systems (with similar disk setups
[same other than size]).
dmesg from bootup:
Nov 18 16:31:01 mwg kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
Nov 18 16:31:01 mwg
Gerd Knorr wrote:
> Why? What is the point in compiling bttv statically into the kernel?
> Unlike filesystems/ide/scsi/... you don't need it to get the box up.
> No problem to compile the driver as module and configure it with
> /etc/modules.conf ...
Huh?
Some systems are built without module
[2.] Full description of the problem/report:
using gnome-terminal, the default alias ls='/bin/ls $LS_OPTIONS'
#mount /mnt/cdrom
#cd /mnt/cdrom
#ls
Segmentation fault
#ls
root@darkstar:~# umount /mnt/cdrom
umount: /mnt/cdrom: device is busy
root@darkstar:~# umount -f /mnt/cdrom
umount2: Device
"Eric W. Biederman" wrote:
> > Be sure lo is established before eth0 and you won't see this message.
>
> Hmm. How does the interaction work. I've been meaning to track it for
> a while but haven't yet.
>
> >From the cases I have observed it seems to be connected with arp requests
> that aren't
> As about the broken calling conventions of the IA32 ABI, I think it
> doesn't worth to break the binary compatibility at this late stage.
We are not at any late stage. The new 64-bit PC processors might
be accepted about as well as Microchannel and EISA were accepted.
Crummy old 32-bit
David Ford <[EMAIL PROTECTED]> writes:
> Andrew Park wrote:
>
> > I get a message
> >
> > neighbour table overflow
> >
> > What does that mean? It seems that
> >
> > net/ipv4/route.c
> >
> > is the place where it prints this. But under what circumstances
> > does this happen?
Werner Almesberger <[EMAIL PROTECTED]> writes:
> Eric W. Biederman wrote:
> > I have one that loads a second kernel over the network using dhcp
> > to configure it's interface and tftp to fetch the image and boots
> > that is only 20kb uncompressed
>
> Neat ;-) My goal is actually not only
Werner Almesberger <[EMAIL PROTECTED]> writes:
> Eric W. Biederman wrote:
> > Well there is that. Somehow implementing scatter/gather from
> > a user space process seemed like a potential mess, and extra work.
>
> Did you look at kiobufs ? I think they may just have the right
> functionality.
At Mon, 13 Nov 2000 11:13:19 -0500,
Jakub Jelinek <[EMAIL PROTECTED]> wrote:
> ago were done in the kernel, POSIX message queue passing is not doable in
> userland without kernel help either (I have a message queue filesystem
> kernel patch for this, but it is a 2.5 thing).
Interesting. Is yours
Compile failed:
megaraid.c: In function `mega_findCard':
megaraid.c:1906: warning: implicit declaration of function
`pci_resource_start'
drivers/scsi/scsi.a(megaraid.o): In function `mega_findCard':
megaraid.o(.text+0x19a7): undefined reference to `pci_resource_start'
Seems a #include is
On Sun, 19 Nov 2000 20:28:39 +1100,
Vincent <[EMAIL PROTECTED]> wrote:
>Nov 19 19:46:47 darkstar kernel: Unable to handle kernel paging request
>at virtual address dfdfdfc4
>Nov 19 19:46:47 darkstar kernel: *pde =
>EIP: 0010:[]
See linux/REPORTING-BUGS.
-
To unsubscribe from this
"Albert D. Cahalan" wrote:
>
> The 'D' means that the process is running uninterruptable kernel
> code that should never take long to execute. Usually it means
> the process is doing disk IO.
>
> To find where process 613 is stuck, do this:
>
> ps -p 613 -o comm,stat,f,pcpu,nwchan,wchan
361
On Sat, Nov 18, 2000 at 03:48:06PM -0800, H. Peter Anvin wrote:
> Followup to: <[EMAIL PROTECTED]>
> By author:Pavel Machek <[EMAIL PROTECTED]>
> In newsgroup: linux.dev.kernel
>
> > > Actually, on machines where RDTSC works correctly, you'd like to use
> > > that to detect a lost timer
Dear kernel hackers,
I am forwarding this message to you because the problem discussed
touches on several areas of the kernel: filesystems, SCSI and
USB.
I am including my original bug report sent to linux-usb-users
here:
-
As you may or may not have been aware, there
It is on kernel.org and the README tells you what to do to enable the stub
in ide-dma.c If it works let me know!
Cheers,
Andre Hedrick
CTO Timpanogas Research Group
EVP Linux Development, TRG
Linux ATA Development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Folks, the patch below is a combination of -EFBIG fixes posted
yesterday with _very_ preliminary stuff that deals with behaviour of
write() in cases when get_block() fails. It compiles, but that's about
all I can really promise.
Please, give it a try. It should be reasonably safe
On Sat, 18 Nov 2000 12:23:05 -0800 (PST), Andre Hedrick <[EMAIL PROTECTED]> wrote:
>
> If anyone is suffering from the dreaded "dmaproc error 14: unsupported"
> error and want to test a code that could get you out of that deadlock
> please speak up.
>
> Basically this is an Intel 440BX PIIX4
Werner Almesberger wrote:
> Gerd Knorr wrote:
> > It simply did'nt work correctly and often used to misdetect
> > random bt848 cards as either MIRO or Hauppauge (which where the first
> > available cards).
>
> Well, this means there's yet another mandatory __setup parameter :-(
Why? What is
Alex Romosan <[EMAIL PROTECTED]> writes:
> i forgot to bring up eth0 before attempting to connect to my dsl
> provider using ppp over ethernet and i got the following oops:
>
i hate it when i do this. the correct oops follows:
ksymoops 2.3.4 on i686 2.4.0-test11. Options used
-V
On Sat, 18 Nov 2000 18:50:00 +0100 (MET),
[EMAIL PROTECTED] (Rogier Wolff) wrote:
>Compile a kernel, marking "sx" and "riscom8" as modules.
>
>Install, modprobe sx, and voila, you'll pull in the riscom because
>its "block_til_ready" static was found to satisfy the block_til_ready
>from
i forgot to bring up eth0 before attempting to connect to my dsl
provider using ppp over ethernet and i got the following oops:
ksymoops 2.3.4 on i686 2.4.0-test11. Options used
-V (default)
-k /proc/ksyms (specified)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test11/
Linus, Ingo:
the attached patch, modifies a warning message in md.c which seems to
often cause confusion - the following email includes one example
there-of (there have been others over the months).
Hopefully the new text is clearer.
(patch against 2.4.0-test11-pre7)
NeilBrown
On
Oops.. linux/spinlock.h not asm/spinlock.h. The patch below
implements resource limits for ramfs, and unlike the previous version
actually compiles.
--
David Gibson, Technical Support Engineer, Linuxcare, Inc.
+61 2 6262 8990
[EMAIL PROTECTED], http://www.linuxcare.com/
Linuxcare. Support for
Folks, the patch below is a combination of -EFBIG fixes posted
yesterday with _very_ preliminary stuff that deals with behaviour of
write() in cases when get_block() fails. It compiles, but that's about
all I can really promise.
Please, give it a try. It should be reasonably safe
On Sat, 18 Nov 2000 18:50:00 +0100 (MET),
[EMAIL PROTECTED] (Rogier Wolff) wrote:
Compile a kernel, marking "sx" and "riscom8" as modules.
Install, modprobe sx, and voila, you'll pull in the riscom because
its "block_til_ready" static was found to satisfy the block_til_ready
from
Alex Romosan [EMAIL PROTECTED] writes:
i forgot to bring up eth0 before attempting to connect to my dsl
provider using ppp over ethernet and i got the following oops:
i hate it when i do this. the correct oops follows:
ksymoops 2.3.4 on i686 2.4.0-test11. Options used
-V (default)
Werner Almesberger wrote:
Gerd Knorr wrote:
It simply did'nt work correctly and often used to misdetect
random bt848 cards as either MIRO or Hauppauge (which where the first
available cards).
Well, this means there's yet another mandatory __setup parameter :-(
Why? What is the point
On Sat, 18 Nov 2000 12:23:05 -0800 (PST), Andre Hedrick [EMAIL PROTECTED] wrote:
If anyone is suffering from the dreaded "dmaproc error 14: unsupported"
error and want to test a code that could get you out of that deadlock
please speak up.
Basically this is an Intel 440BX PIIX4 issues,
It is on kernel.org and the README tells you what to do to enable the stub
in ide-dma.c If it works let me know!
Cheers,
Andre Hedrick
CTO Timpanogas Research Group
EVP Linux Development, TRG
Linux ATA Development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Dear kernel hackers,
I am forwarding this message to you because the problem discussed
touches on several areas of the kernel: filesystems, SCSI and
USB.
I am including my original bug report sent to linux-usb-users
here:
-
As you may or may not have been aware, there
On Sat, Nov 18, 2000 at 03:48:06PM -0800, H. Peter Anvin wrote:
Followup to: [EMAIL PROTECTED]
By author:Pavel Machek [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Actually, on machines where RDTSC works correctly, you'd like to use
that to detect a lost timer interrupt.
"Albert D. Cahalan" wrote:
The 'D' means that the process is running uninterruptable kernel
code that should never take long to execute. Usually it means
the process is doing disk IO.
To find where process 613 is stuck, do this:
ps -p 613 -o comm,stat,f,pcpu,nwchan,wchan
361 pts/1
On Sun, 19 Nov 2000 20:28:39 +1100,
Vincent [EMAIL PROTECTED] wrote:
Nov 19 19:46:47 darkstar kernel: Unable to handle kernel paging request
at virtual address dfdfdfc4
Nov 19 19:46:47 darkstar kernel: *pde =
EIP: 0010:[c486d5a7]
See linux/REPORTING-BUGS.
-
To unsubscribe from this
Compile failed:
megaraid.c: In function `mega_findCard':
megaraid.c:1906: warning: implicit declaration of function
`pci_resource_start'
drivers/scsi/scsi.a(megaraid.o): In function `mega_findCard':
megaraid.o(.text+0x19a7): undefined reference to `pci_resource_start'
Seems a #include
At Mon, 13 Nov 2000 11:13:19 -0500,
Jakub Jelinek [EMAIL PROTECTED] wrote:
ago were done in the kernel, POSIX message queue passing is not doable in
userland without kernel help either (I have a message queue filesystem
kernel patch for this, but it is a 2.5 thing).
Interesting. Is yours
Werner Almesberger [EMAIL PROTECTED] writes:
Eric W. Biederman wrote:
I have one that loads a second kernel over the network using dhcp
to configure it's interface and tftp to fetch the image and boots
that is only 20kb uncompressed
Neat ;-) My goal is actually not only size, but
Werner Almesberger [EMAIL PROTECTED] writes:
Eric W. Biederman wrote:
Well there is that. Somehow implementing scatter/gather from
a user space process seemed like a potential mess, and extra work.
Did you look at kiobufs ? I think they may just have the right
functionality. I always
David Ford [EMAIL PROTECTED] writes:
Andrew Park wrote:
I get a message
neighbour table overflow
What does that mean? It seems that
net/ipv4/route.c
is the place where it prints this. But under what circumstances
does this happen?
Thanks
It means you
As about the broken calling conventions of the IA32 ABI, I think it
doesn't worth to break the binary compatibility at this late stage.
We are not at any late stage. The new 64-bit PC processors might
be accepted about as well as Microchannel and EISA were accepted.
Crummy old 32-bit
"Eric W. Biederman" wrote:
Be sure lo is established before eth0 and you won't see this message.
Hmm. How does the interaction work. I've been meaning to track it for
a while but haven't yet.
From the cases I have observed it seems to be connected with arp requests
that aren't
[2.] Full description of the problem/report:
using gnome-terminal, the default alias ls='/bin/ls $LS_OPTIONS'
#mount /mnt/cdrom
#cd /mnt/cdrom
#ls
Segmentation fault
#ls
gnome-terminal freez
root@darkstar:~# umount /mnt/cdrom
umount: /mnt/cdrom: device is busy
root@darkstar:~# umount -f
Gerd Knorr wrote:
Why? What is the point in compiling bttv statically into the kernel?
Unlike filesystems/ide/scsi/... you don't need it to get the box up.
No problem to compile the driver as module and configure it with
/etc/modules.conf ...
Huh?
Some systems are built without module
Is this something to be concerned about? It sounds like a disaster waiting
to happen from the message. This is on 2 systems (with similar disk setups
[same other than size]).
dmesg from bootup:
Nov 18 16:31:01 mwg kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
Nov 18 16:31:01 mwg
Tom Leete wrote:
Hi,
The second and third arguments of get_joliet_filename() are swapped.
Tom
--- linux-2.4.0-test11/fs/isofs/namei.c.origSat Nov 18 01:55:55 2000
+++ linux-2.4.0-test11/fs/isofs/namei.c Sat Nov 18 07:08:05 2000
@@ -127,7 +127,7 @@
dpnt =
= Original Message From [EMAIL PROTECTED] (Eric W. Biederman) =
Werner Almesberger [EMAIL PROTECTED] writes:
Eric W. Biederman wrote:
I have one that loads a second kernel over the network using dhcp
to configure it's interface and tftp to fetch the image and boots
that is only
Same problem as Vincent - OOPs when "ls" a mounted cdrom. It did work
once with a CD-R. My report symptoms are nearly identical to previous
post with same subject heading with a few differences:
[4.] Kernel version (from /proc/version):
Linux version 2.4.0-test11 (root@svcr-adsl) (gcc driver
On Sun, Nov 19, 2000 at 03:39:43AM -0800, George Garvey wrote:
Is this something to be concerned about? It sounds like a disaster waiting
to happen from the message. This is on 2 systems (with similar disk setups
[same other than size]).
Nothing to worry. (I got worried also when I
Linus Torvalds wrote:
...
But the algorithm itself should allow for other values. In fact, I think
that you'll find that it works fine if you switch to non-exclusive
wait-queues, and the only reason you see the repeatable D states is
exactly the case where we didn't "take" the semaphore
I'm getting '__alloc_pages: 7-order allocation failed.' every time I
play something to my maestro card (using the maestro kernel module,
with dsps_order=2)..
Its a debugging message.
for (order = (dsps_order + (16-PAGE_SHIFT) + 1); order = (dsps_order + 2 + 1);
order--)
if((rawbuf
o Fix file/block when spacing to tape beginning (Kai Maiksara)
o Small ISDN documentation fixes (Kai Germaschewski)
Alan, On the ISDN issue, isdn4K-utils seems to be out of sync with=20
kernels older than 2.2.16. Some #define's that used to be in
the 2.2.14 patch
protocol for USB communication being diluted down. Realize that a 1KB
block has 4 times the overhead of a 4KB block (on a per-byte-of-data
basis). The usb-storage driver attempts to get the SCSI layer to give it
That guess would be dubious. Its also not IMHO enough to explain the
On Sun, Nov 19, 2000 at 03:39:43AM -0800, George Garvey wrote:
Is this something to be concerned about? It sounds like a disaster waiting
to happen from the message. This is on 2 systems (with similar disk setups
[same other than size]).
Nov 18 16:31:02 mwg kernel: md: serializing resync,
Eric W. Biederman wrote:
The code wasn't trivially reusable, and the structures had a lot
of overhead.
There's some overhead, but I think it's not too bad. I'll give it a
try ...
The rebooting is done the rest is not yet.
Ah, and I already wondered where in all the APIC code you've hidden
On Sun, Nov 19, 2000 at 07:24:16PM +0900, GOTO Masanori wrote:
At Mon, 13 Nov 2000 11:13:19 -0500,
Jakub Jelinek [EMAIL PROTECTED] wrote:
ago were done in the kernel, POSIX message queue passing is not doable in
userland without kernel help either (I have a message queue filesystem
kernel
On 19 Nov 2000 12:56:17 GMT,
[EMAIL PROTECTED] (Gerd Knorr) wrote:
Some generic way to make module args available as kernel args too
would be nice. Or at least some simple one-liner I could put next to
the MODULE_PARM() macro...
On my list for 2.5. If foo is declared as MODULE_PARM in object
Hi!
Thanks for the fast reply - but I can't follow. What is the _tuning
aspect_ and how is it modified?
Andre Hedrick [EMAIL PROTECTED] wrote:
There is a problem that it does not downgrade the IO if all you have is
iCRC errors. The threshold is 10 events without other errors and it
it seems there has been a change in the format of the /proc/cpuinfo file: infact
'flags: ' became 'features: '
This change broke xmms and could broke any other program which relies on
/proc/cpuinfo...
I hope the problem will be solved (in the kernel or in every other program which uses
On Sun, 19 Nov 2000, David Lang wrote:
there is a rootkit kernel module out there that, if loaded onto your
system, can make it almost impossible to detect that your system has been
compramised. with module support disabled this isn't possible.
Yes, it is. Easily. If you've got root you
On Sun, 19 Nov 2000 07:16:52 -0800 (PST),
David Lang [EMAIL PROTECTED] wrote:
there is a rootkit kernel module out there that, if loaded onto your
system, can make it almost impossible to detect that your system has been
compramised. with module support disabled this isn't possible.
Wrong.
Markus Schoder wrote:
--- Linus Torvalds [EMAIL PROTECTED] schrieb:
On Sat, 18 Nov 2000, adrian wrote:
On Sat, 18 Nov 2000, Linus Torvalds wrote:
There's almost certainly more than that. I'd
love to have a report on my
asm-only version, but even so I suspect it
Three small patches against test11-pre7
1) creates arch_init_modules(), removes alpha specific code from
module.c
2) makes non-modular try_inc_use_count() an inline for better
optimization.
3) Creates __modinfo define.
--
Brian Gerst
diff -urN
On Sun, 19 Nov 2000, Alexander Viro wrote:
On Sun, 19 Nov 2000, David Lang wrote:
there is a rootkit kernel module out there that, if loaded onto your
system, can make it almost impossible to detect that your system has been
compramised. with module support disabled this isn't possible.
In article [EMAIL PROTECTED] you write:
On Sun, 19 Nov 2000, Alexander Viro wrote:
On Sun, 19 Nov 2000, David Lang wrote:
there is a rootkit kernel module out there that, if loaded onto your
system, can make it almost impossible to detect that your system has been
compramised. with module
On Sun, 19 Nov 2000, Jeff V. Merkey wrote:
o Small ISDN documentation fixes (Kai Germaschewski)
Alan, On the ISDN issue, isdn4K-utils seems to be out of sync with
kernels older than 2.2.16. Some #define's that used to be in
the 2.2.14 patch don't seem to be in 2.2.17 .
It's working fine here w/o modification. Maybe you need the latest
version or have somethinn enabled that I don't.
Gianluca Anzolin wrote:
it seems there has been a change in the format of the /proc/cpuinfo file: infact
'flags: ' became 'features: '
This change broke xmms and could broke
On Sun, 19 Nov 2000, Christer Weinigel wrote:
In article [EMAIL PROTECTED] you write:
On Sun, 19 Nov 2000, Alexander Viro wrote:
On Sun, 19 Nov 2000, David Lang wrote:
there is a rootkit kernel module out there that, if loaded onto your
system, can make it almost impossible to detect
On Sun, 19 Nov 2000, Alexander Viro wrote:
Kernel on writeprotected floppy disk...
Cute. And when (not if) we get hit by new bug in the net/*/* you will drive
to the location of said router to upgrade the thing.
No, post/email a floppy to tech who swaps the floppy and reboots router.
-Dan
Jeff Garzik wrote:
dalecki wrote:
-#if LINUX_VERSION_CODE 0x020024
#include asm/uaccess.h
-#endif
*cheer*
I missd this point...
-u32 RDINDOOR (mega_host_config * megaCfg)
+ulong RDINDOOR (mega_host_config * megaCfg)
-void WRINDOOR (mega_host_config * megaCfg, u32 value)
Why not? /me has nearly everything compiled as modules.
Some people have extensive sh, awk and sed scripts to manage their systems, some
have compiled programs.
There is an introduced security weakness by using kernels.
??? Guess you mean "by using modules"? Which weakness? Other than
Miquel van Smoorenburg wrote:
In article [EMAIL PROTECTED],
dalecki [EMAIL PROTECTED] wrote:
This is a multi-part message in MIME format.
1. Merge the most current version (aka: 1.08) of the
MegaRAID driver from AMI in to the most current kernel
(2.4.0-test10 and friends).
The
Christer Weinigel wrote:
Kernel on writeprotected floppy disk...
So change the CMOS-settings so that the BIOS changes the boot order
from A, C, CD-ROM to C first instead. *grin* How long do you want
to keep playing Tic-Tac-Toe?
Of course, using capabilities and totally disabling access
My guess is that it's a plugin, the source for xmms doesn't have "cpuinfo" anywhere in
it.
-d
Gianluca Anzolin wrote:
it seems there has been a change in the format of the /proc/cpuinfo file: infact
'flags: ' became 'features: '
This change broke xmms and could broke any other program
On Sun, Nov 19, 2000 at 01:53:00AM +0100, bert hubert wrote:
: On Sat, Nov 18, 2000 at 03:15:28PM -0800, Dan Hollis wrote:
:
::: In that case, the wording of the manpage needs to be changed, as it
::: implies that 'either or both' of the filedescriptors can be sockets.
::
:: Its quite
On Sun, 19 Nov 2000, Taisuke Yamada wrote:
Earlier this month, I had sent in a patch to 2.2.18pre17 (with
IDE-patch from http://www.linux-ide.org/ applied) to add support
for IDE disk larger than 32GB, even if the disk required "clipping"
to reduce apparent disk size due to BIOS limitation.
At 11:26 17/11/2000, Alan Cox wrote:
drive problem, considering that another ide drive on the same controller
works fine with DMA enabled (a QUANTUM TRB850A) while the Conner
Peripherals 1275MB - CFS1275A fails with DMA enabled. They are in fact
both
And the Conner drives work fine on a
101 - 200 of 277 matches
Mail list logo
