Michael Kerrisk <[EMAIL PROTECTED]> wrote:
> a) I did a
>
> s/internal kernel handle/open file description/
>
> since that is the POSIX term for the internal handle.
>
> b) It seems to me that you text doesn't quite make the point explicit
> enough. I've tried to rewrite it; could you please
Michael Kerrisk [EMAIL PROTECTED] wrote:
a) I did a
s/internal kernel handle/open file description/
since that is the POSIX term for the internal handle.
b) It seems to me that you text doesn't quite make the point explicit
enough. I've tried to rewrite it; could you please check:
Andi Kleen <[EMAIL PROTECTED]> wrote:
>> we were talking about the load order. This will solve the load order,
>> but if we have races like the kind you described, then the whole mISDN
>> design is broken.
>
> It's more a generic problem of the module code.
It's a problem of not enough
Andi Kleen [EMAIL PROTECTED] wrote:
we were talking about the load order. This will solve the load order,
but if we have races like the kind you described, then the whole mISDN
design is broken.
It's more a generic problem of the module code.
It's a problem of not enough synchronisation
Gene Heskett <[EMAIL PROTECTED]> wrote:
['cat /dev/hideaw0 | hexdump -v']
> Or some way to ship the
> $00's to /dev/null so hexdump ignores them?
.. | perl -pe 's/\00//g/' | ...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Gene Heskett [EMAIL PROTECTED] wrote:
['cat /dev/hideaw0 | hexdump -v']
Or some way to ship the
$00's to /dev/null so hexdump ignores them?
.. | perl -pe 's/\00//g/' | ...
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
Hans-Jürgen Koch <[EMAIL PROTECTED]> wrote:
> schrieb Jan Engelhardt <[EMAIL PROTECTED]>:
>> There is a much more interesting 'problem' with a "/dev/null
>> directory".
>>
>> Q: Why would you need such a directory?
>> A: To temporarily fool a program into believing it wrote something.
>>
>> Q:
rzryyvzy <[EMAIL PROTECTED]> wrote:
> /dev/null is often very useful, specially if programs force to save data in
> some file. But some programs like to creates different temporary file names,
> so /dev/null could no more work.
>
> What is with a "/dev/null"-directory?
> I mean a "blackhole
rzryyvzy [EMAIL PROTECTED] wrote:
/dev/null is often very useful, specially if programs force to save data in
some file. But some programs like to creates different temporary file names,
so /dev/null could no more work.
What is with a /dev/null-directory?
I mean a blackhole pseudo
Hans-Jürgen Koch [EMAIL PROTECTED] wrote:
schrieb Jan Engelhardt [EMAIL PROTECTED]:
There is a much more interesting 'problem' with a /dev/null
directory.
Q: Why would you need such a directory?
A: To temporarily fool a program into believing it wrote something.
Q: Should all files
Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Mon, 11 Feb 2008 16:17:33 -0700 Jonathan Corbet <[EMAIL PROTECTED]> wrote:
>> Avoid buffer overflows in get_user_pages()
>>
>> So I spent a while pounding my head against my monitor trying to figure
>> out the vmsplice() vulnerability - how could a
Andrew Morton [EMAIL PROTECTED] wrote:
On Mon, 11 Feb 2008 16:17:33 -0700 Jonathan Corbet [EMAIL PROTECTED] wrote:
Avoid buffer overflows in get_user_pages()
So I spent a while pounding my head against my monitor trying to figure
out the vmsplice() vulnerability - how could a failure to
Denis Cheng <[EMAIL PROTECTED]> wrote:
> use module_init/module_exit to replace the original cond-compiling, these
> macros were well designed to deal module/built-in compiling.
>
> the original __setup with null string was invalid and not executed,
> __setup("", ide_setup);
>
> however, with
Denis Cheng [EMAIL PROTECTED] wrote:
use module_init/module_exit to replace the original cond-compiling, these
macros were well designed to deal module/built-in compiling.
the original __setup with null string was invalid and not executed,
__setup(, ide_setup);
however, with the current
Enabling this option changes a hard panic on boot errors to a
soft panic, which does not stop the system completely.
You can still scroll the screen and read the messages.
Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
---
Fixed: s/SOFTPANIC/CONFIG_SOFTPANIC/
I did not implement shuttin
Trond Myklebust <[EMAIL PROTECTED]> wrote:
> On Mon, 2008-01-28 at 05:38 +0100, Andi Kleen wrote:
>> On Monday 28 January 2008 05:13:09 Trond Myklebust wrote:
>> > On Mon, 2008-01-28 at 03:58 +0100, Andi Kleen wrote:
>> > > The problem is that it's not a race in who gets to do its thing first,
>>
Enabling this option changes a hard panic on boot errors to a
soft panic, which does not stop the system completely.
You can still scroll the screen and read the messages.
Signed-Off-By: Bodo Eggert [EMAIL PROTECTED]
---
Fixed: s/SOFTPANIC/CONFIG_SOFTPANIC/
I did not implement shutting down
Trond Myklebust [EMAIL PROTECTED] wrote:
On Mon, 2008-01-28 at 05:38 +0100, Andi Kleen wrote:
On Monday 28 January 2008 05:13:09 Trond Myklebust wrote:
On Mon, 2008-01-28 at 03:58 +0100, Andi Kleen wrote:
The problem is that it's not a race in who gets to do its thing first,
but a
> +++ linux/fs/fcntl.c
> @@ -240,11 +240,15 @@ static int setfl(int fd, struct file * f
>
> lock_kernel();
> if ((arg ^ filp->f_flags) & FASYNC) {
> - if (filp->f_op && filp->f_op->fasync) {
> + if (filp->f_op && filp->f_op->unlocked_fasync)
> +
+++ linux/fs/fcntl.c
@@ -240,11 +240,15 @@ static int setfl(int fd, struct file * f
lock_kernel();
if ((arg ^ filp-f_flags) FASYNC) {
- if (filp-f_op filp-f_op-fasync) {
+ if (filp-f_op filp-f_op-unlocked_fasync)
+
On Fri, 25 Jan 2008, Jan Engelhardt wrote:
> On Jan 25 2008 15:54, Bodo Eggert wrote:
> >+#ifdef SOFTPANIC
>
> #ifdef CONFIG_SOFTPANIC?
Thanks. I remember having fixed it ...
--
Professionals are predictable, it's the amateurs that are dangerous.
--
To unsubscribe from this list
On Fri, 25 Jan 2008, Andi Kleen wrote:
> Bodo Eggert <[EMAIL PROTECTED]> writes:
> > Enabling this option changes a hard panic on boot errors to a
> > soft panic, which does not stop the system completely.
> > You can still scroll the screen and read the messages.
>
Enabling this option changes a hard panic on boot errors to a
soft panic, which does not stop the system completely.
You can still scroll the screen and read the messages.
Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
diff -pruN -X dontdiff linux-2.6.24.pure/include/linux/kernel.h
linux-
On Fri, 25 Jan 2008, Jan Engelhardt wrote:
On Jan 25 2008 15:54, Bodo Eggert wrote:
+#ifdef SOFTPANIC
#ifdef CONFIG_SOFTPANIC?
Thanks. I remember having fixed it ...
--
Professionals are predictable, it's the amateurs that are dangerous.
--
To unsubscribe from this list: send the line
Enabling this option changes a hard panic on boot errors to a
soft panic, which does not stop the system completely.
You can still scroll the screen and read the messages.
Signed-Off-By: Bodo Eggert [EMAIL PROTECTED]
diff -pruN -X dontdiff linux-2.6.24.pure/include/linux/kernel.h
linux-2.6.24
On Fri, 25 Jan 2008, Andi Kleen wrote:
Bodo Eggert [EMAIL PROTECTED] writes:
Enabling this option changes a hard panic on boot errors to a
soft panic, which does not stop the system completely.
You can still scroll the screen and read the messages.
I don't think it's a good idea to keep
Alan Cox <[EMAIL PROTECTED]> wrote:
>> I'd tried to advocate SIGDANGER some years ago as well, but none of
>> the kernel maintainers were interested. It definitely makes sense
>> to have some sort of mechanism like this. At the time I first brought
>> it up it was in conjunction with Netscape
Alan Cox [EMAIL PROTECTED] wrote:
I'd tried to advocate SIGDANGER some years ago as well, but none of
the kernel maintainers were interested. It definitely makes sense
to have some sort of mechanism like this. At the time I first brought
it up it was in conjunction with Netscape using too
Bjorn Helgaas <[EMAIL PROTECTED]> wrote:
> On Wednesday 16 January 2008 11:44:37 am H. Peter Anvin wrote:
>> Bjorn Helgaas wrote:
>> > +#ifdef CONFIG_X86
>> > + switch (port->iobase) {
>> > + case 0x3f8: return 0; /* COM1 -> ttyS0 */
>> > + case 0x2f8: return 1; /* COM2 ->
Bjorn Helgaas [EMAIL PROTECTED] wrote:
On Wednesday 16 January 2008 11:44:37 am H. Peter Anvin wrote:
Bjorn Helgaas wrote:
+#ifdef CONFIG_X86
+ switch (port-iobase) {
+ case 0x3f8: return 0; /* COM1 - ttyS0 */
+ case 0x2f8: return 1; /* COM2 - ttyS1 */
+ case
On Fri, 11 Jan 2008, Lennart Sorensen wrote:
> On Fri, Jan 11, 2008 at 05:22:45PM +0100, Bodo Eggert wrote:
> > What can happen if someone does tune2fs -Lroot /dev/usbstick
> > and puts that stick into this system?
>
> Don't know. I use UUIDs rather than LABELs. Having dup
Matthias Schniedermeyer <[EMAIL PROTECTED]> wrote:
>> > Don't use udev then. Good old static dev works fine if you have a fixed
>> > set of devices.
>>
>> It doesn't, with the unpredictable SCSI mapping insanity.
>
> That what LABEL und UUID-Support in mount is for.
>
> You label the
Al Boldi <[EMAIL PROTECTED]> wrote:
> Even after a black-out shutdown, the corruption is pretty minimal, using
> ext3fs at least. So let's take advantage of this fact and do an optimistic
> fsck, to assure integrity per-dir, and assume no external corruption. Then
> we release this checked dir
Abhishek Rai <[EMAIL PROTECTED]> wrote:
> Putting metacluster at the end of the block group gives slightly
> inferior sequential read throughput compared to putting it in the
> beginning or the middle, but the difference is very tiny and exists
> only for large files that span multiple block
Al Boldi [EMAIL PROTECTED] wrote:
Even after a black-out shutdown, the corruption is pretty minimal, using
ext3fs at least. So let's take advantage of this fact and do an optimistic
fsck, to assure integrity per-dir, and assume no external corruption. Then
we release this checked dir to the
Abhishek Rai [EMAIL PROTECTED] wrote:
Putting metacluster at the end of the block group gives slightly
inferior sequential read throughput compared to putting it in the
beginning or the middle, but the difference is very tiny and exists
only for large files that span multiple block groups.
Matthias Schniedermeyer [EMAIL PROTECTED] wrote:
Don't use udev then. Good old static dev works fine if you have a fixed
set of devices.
It doesn't, with the unpredictable SCSI mapping insanity.
That what LABEL und UUID-Support in mount is for.
You label the filesystems (e2label for
On Fri, 11 Jan 2008, Lennart Sorensen wrote:
On Fri, Jan 11, 2008 at 05:22:45PM +0100, Bodo Eggert wrote:
What can happen if someone does tune2fs -Lroot /dev/usbstick
and puts that stick into this system?
Don't know. I use UUIDs rather than LABELs. Having duplicated labels
just means
Tuomo Valkonen <[EMAIL PROTECTED]> wrote:
> On 2008-01-08, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>> "Power users" may still
>> use the index= option of sound card modules and wire it up in
>> /etc/modprobe.d if they prefer.
>
> Another very cryptic directory whose contents say nothing to me.
On Tue, 8 Jan 2008, Ondrej Zary wrote:
> On Tuesday 08 January 2008 18:24:02 David P. Reed wrote:
> > Windows these days does delays with timing loops or the scheduler. It
> > doesn't use a "port". Also, Windows XP only supports machines that tend
> > not to have timing problems that use
On Mon, 7 Jan 2008, Pavel Machek wrote:
> > Introduce config CONFIG_SOFTPANIC
> > Enabling this option changes a hard panic on boot errors to a
> > soft panic, which does not stop the system completely.
> > You can still scroll the screen and read the messages.
> >
On Mon, 7 Jan 2008, Alan Cox wrote:
> > But overclocking is not the problem for udelay, it would err to the safe
> > side. The problem would be a BUS having < 8 MHz, and since the days of
> > 80286, they are hard to find. IMO having an option to set the bus speed
> > for those systems should be
On Tue, 8 Jan 2008, Rene Herman wrote:
> On 08-01-08 00:24, H. Peter Anvin wrote:
> > Rene Herman wrote:
> > > Is this only about the ones then left for things like legacy PIC and PIT?
> > > Does anyone care about just sticking in a udelay(2) (or 1) there as a
> > > replacement and call it a day?
On Tue, 8 Jan 2008, Rene Herman wrote:
On 08-01-08 00:24, H. Peter Anvin wrote:
Rene Herman wrote:
Is this only about the ones then left for things like legacy PIC and PIT?
Does anyone care about just sticking in a udelay(2) (or 1) there as a
replacement and call it a day?
On Mon, 7 Jan 2008, Alan Cox wrote:
But overclocking is not the problem for udelay, it would err to the safe
side. The problem would be a BUS having 8 MHz, and since the days of
80286, they are hard to find. IMO having an option to set the bus speed
for those systems should be enough.
On Mon, 7 Jan 2008, Pavel Machek wrote:
Introduce config CONFIG_SOFTPANIC
Enabling this option changes a hard panic on boot errors to a
soft panic, which does not stop the system completely.
You can still scroll the screen and read the messages.
Signed-Off-By: Bodo Eggert [EMAIL
On Tue, 8 Jan 2008, Ondrej Zary wrote:
On Tuesday 08 January 2008 18:24:02 David P. Reed wrote:
Windows these days does delays with timing loops or the scheduler. It
doesn't use a port. Also, Windows XP only supports machines that tend
not to have timing problems that use delays.
Tuomo Valkonen [EMAIL PROTECTED] wrote:
On 2008-01-08, Jan Engelhardt [EMAIL PROTECTED] wrote:
Power users may still
use the index= option of sound card modules and wire it up in
/etc/modprobe.d if they prefer.
Another very cryptic directory whose contents say nothing to me.
Configuration
On Mon, 7 Jan 2008, H. Peter Anvin wrote:
> Bodo Eggert wrote:
> > But overclocking is not the problem for udelay, it would err to the safe
> > side. The problem would be a BUS having < 8 MHz, and since the days of
> > 80286, they are hard to find. IMO having an opt
On Mon, 7 Jan 2008, H. Peter Anvin wrote:
> Bodo Eggert wrote:
> > Christer Weinigel <[EMAIL PROTECTED]> wrote:
> > > How do you find out the speed of the ISA bus? AFAIK there is no
> > > standardized way to do that. On the Geode SC2200 the ISA bus speed is
&g
Christer Weinigel <[EMAIL PROTECTED]> wrote:
> How do you find out the speed of the ISA bus? AFAIK there is no
> standardized way to do that. On the Geode SC2200 the ISA bus speed is
> usually the PCI clock divided by 4 giving 33MHz/4=8.3MHz or
> 30/4=7.5MHz, but with no external ISA devices
> always be available and can implement any behavior desired (like droping into
> a dash).
ACK, but that's your part.
Introduce config CONFIG_SOFTPANIC
Enabling this option changes a hard panic on boot errors to a
soft panic, which does not stop the system completely.
You can still scrol
into
a dash).
ACK, but that's your part.
snip
Introduce config CONFIG_SOFTPANIC
Enabling this option changes a hard panic on boot errors to a
soft panic, which does not stop the system completely.
You can still scroll the screen and read the messages.
Signed-Off-By: Bodo Eggert [EMAIL PROTECTED
Christer Weinigel [EMAIL PROTECTED] wrote:
How do you find out the speed of the ISA bus? AFAIK there is no
standardized way to do that. On the Geode SC2200 the ISA bus speed is
usually the PCI clock divided by 4 giving 33MHz/4=8.3MHz or
30/4=7.5MHz, but with no external ISA devices it's
On Mon, 7 Jan 2008, H. Peter Anvin wrote:
Bodo Eggert wrote:
Christer Weinigel [EMAIL PROTECTED] wrote:
How do you find out the speed of the ISA bus? AFAIK there is no
standardized way to do that. On the Geode SC2200 the ISA bus speed is
usually the PCI clock divided by 4 giving
On Mon, 7 Jan 2008, H. Peter Anvin wrote:
Bodo Eggert wrote:
But overclocking is not the problem for udelay, it would err to the safe
side. The problem would be a BUS having 8 MHz, and since the days of
80286, they are hard to find. IMO having an option to set the bus speed
for those
Thanasis <[EMAIL PROTECTED]> wrote:
> on 12/31/2007 11:54 AM Jose de la Mancha wrote the following:
>> --> All RAID edition drives are more expensive that their equivalent
>> "desktop edition" drives (same model on "desktop edition"). Just take a look
>> at newegg for instance.
>>
On Wed, 2 Jan 2008, Herbert Xu wrote:
> Theodore Tso <[EMAIL PROTECTED]> wrote:
> > The question is whether the size of the Unix domain sockets support is
> > worth the complexity of yet another config option that we expose to
> > the user. For the embedded world, OK, maybe they want to save 14k
Abdel <[EMAIL PROTECTED]> wrote:
> In file include/asm-i386/system.h, _set_base and _set_limit use an
> useless do ... while(0)
>
> Why is this needed ?
http://kernelnewbies.org/FAQ/DoWhile0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Abdel [EMAIL PROTECTED] wrote:
In file include/asm-i386/system.h, _set_base and _set_limit use an
useless do ... while(0)
Why is this needed ?
http://kernelnewbies.org/FAQ/DoWhile0
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On Wed, 2 Jan 2008, Herbert Xu wrote:
Theodore Tso [EMAIL PROTECTED] wrote:
The question is whether the size of the Unix domain sockets support is
worth the complexity of yet another config option that we expose to
the user. For the embedded world, OK, maybe they want to save 14k of
Thanasis [EMAIL PROTECTED] wrote:
on 12/31/2007 11:54 AM Jose de la Mancha wrote the following:
-- All RAID edition drives are more expensive that their equivalent
desktop edition drives (same model on desktop edition). Just take a look
at newegg for instance.
On Mon, 31 Dec 2007, David Miller wrote:
> From: Bodo Eggert <[EMAIL PROTECTED]>
> > The big question is: Is there any non-embedded system where you have
> > to aim for a small kernel image?
>
> One some platforms, due to bootloader restrictions or whatever,
> ther
On Mon, 31 Dec 2007, Al Viro wrote:
> On Mon, Dec 31, 2007 at 03:03:20PM +0100, Bodo Eggert wrote:
> > On Mon, 31 Dec 2007, David Miller wrote:
> > > From: Bodo Eggert <[EMAIL PROTECTED]>
> > > > As suggested by Adrian Bunk, UNIX d
On Mon, 31 Dec 2007, Douglas Gilbert wrote:
> Matthew Wilcox wrote:
> > On Mon, Dec 31, 2007 at 10:16:43AM -0500, Douglas Gilbert wrote:
> >> Bodo Eggert wrote:
(Kicking netdev from CC)
> >>> ---
> >>> SCSI target support (SCSI_TGT) [N/m/y/?] (NEW) ?
On Mon, 31 Dec 2007, Adrian Bunk wrote:
> On Mon, Dec 31, 2007 at 02:26:42PM +0100, Bodo Eggert wrote:
> > On Mon, 31 Dec 2007, Adrian Bunk wrote:
> > > On Mon, Dec 31, 2007 at 01:09:43PM +0100, Bodo Eggert wrote:
> > > > As suggested by Adrian Bunk, UNIX domain
On Sun, 30 Dec 2007, Alan Cox wrote:
> On Sun, 30 Dec 2007 12:53:02 -0800
> "H. Peter Anvin" <[EMAIL PROTECTED]> wrote:
> > Bodo Eggert wrote:
> > > I've never seen code which would do that, and it was not suggested by any
> > > tutorial I ever saw
On Mon, 31 Dec 2007, David Miller wrote:
> From: Bodo Eggert <[EMAIL PROTECTED]>
> > As suggested by Adrian Bunk, UNIX domain sockets should always be built in
> > on normal systems. This is especially true since udev needs these sockets
> > and fails to run if
On Mon, 31 Dec 2007, Adrian Bunk wrote:
> On Mon, Dec 31, 2007 at 01:09:43PM +0100, Bodo Eggert wrote:
> > As suggested by Adrian Bunk, UNIX domain sockets should always be built in
> > on normal systems. This is especially true since udev needs these sockets
> > and f
In some of the Kconfig files, the options are not adequately decribed. I
collected a few of the bad descriptions I found:
---
Lowlevel video output switch controls (VIDEO_OUTPUT_CONTROL) [M/n/y/?] (NEW) ?
This framework adds support for low-level control of the video
output switch.
---
- What
As suggested by Adrian Bunk, UNIX domain sockets should always be built in
on normal systems. This is especially true since udev needs these sockets
and fails to run if UNIX=m.
Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
---
Last minute change: I decided against making it a bool b
Theewara Vorakosit <[EMAIL PROTECTED]> wrote:
> I get MAC address from ioctl. However, ifconfig can change this MAC
> address. Can I get a real physical MAC address of the NIC?
First, get a network card having a physical MAC. Most cards have only a
(currently configured) default MAC address,
Theewara Vorakosit [EMAIL PROTECTED] wrote:
I get MAC address from ioctl. However, ifconfig can change this MAC
address. Can I get a real physical MAC address of the NIC?
First, get a network card having a physical MAC. Most cards have only a
(currently configured) default MAC address, maybe
As suggested by Adrian Bunk, UNIX domain sockets should always be built in
on normal systems. This is especially true since udev needs these sockets
and fails to run if UNIX=m.
Signed-Off-By: Bodo Eggert [EMAIL PROTECTED]
---
Last minute change: I decided against making it a bool because
In some of the Kconfig files, the options are not adequately decribed. I
collected a few of the bad descriptions I found:
---
Lowlevel video output switch controls (VIDEO_OUTPUT_CONTROL) [M/n/y/?] (NEW) ?
This framework adds support for low-level control of the video
output switch.
---
- What
On Mon, 31 Dec 2007, Adrian Bunk wrote:
On Mon, Dec 31, 2007 at 01:09:43PM +0100, Bodo Eggert wrote:
As suggested by Adrian Bunk, UNIX domain sockets should always be built in
on normal systems. This is especially true since udev needs these sockets
and fails to run if UNIX=m.
Signed
On Mon, 31 Dec 2007, David Miller wrote:
From: Bodo Eggert [EMAIL PROTECTED]
As suggested by Adrian Bunk, UNIX domain sockets should always be built in
on normal systems. This is especially true since udev needs these sockets
and fails to run if UNIX=m.
Signed-Off-By: Bodo Eggert
On Sun, 30 Dec 2007, Alan Cox wrote:
On Sun, 30 Dec 2007 12:53:02 -0800
H. Peter Anvin [EMAIL PROTECTED] wrote:
Bodo Eggert wrote:
I've never seen code which would do that, and it was not suggested by any
tutorial I ever saw. I'd expect any machine to break on all kinds of
software
On Mon, 31 Dec 2007, Adrian Bunk wrote:
On Mon, Dec 31, 2007 at 02:26:42PM +0100, Bodo Eggert wrote:
On Mon, 31 Dec 2007, Adrian Bunk wrote:
On Mon, Dec 31, 2007 at 01:09:43PM +0100, Bodo Eggert wrote:
As suggested by Adrian Bunk, UNIX domain sockets should always be built
On Mon, 31 Dec 2007, Douglas Gilbert wrote:
Matthew Wilcox wrote:
On Mon, Dec 31, 2007 at 10:16:43AM -0500, Douglas Gilbert wrote:
Bodo Eggert wrote:
(Kicking netdev from CC)
---
SCSI target support (SCSI_TGT) [N/m/y/?] (NEW) ?
If you want to use SCSI target mode drivers enable
On Mon, 31 Dec 2007, Al Viro wrote:
On Mon, Dec 31, 2007 at 03:03:20PM +0100, Bodo Eggert wrote:
On Mon, 31 Dec 2007, David Miller wrote:
From: Bodo Eggert [EMAIL PROTECTED]
As suggested by Adrian Bunk, UNIX domain sockets should always be built
in
on normal systems
On Mon, 31 Dec 2007, David Miller wrote:
From: Bodo Eggert [EMAIL PROTECTED]
The big question is: Is there any non-embedded system where you have
to aim for a small kernel image?
One some platforms, due to bootloader restrictions or whatever,
there are hard limits on how large the main
On Sun, 30 Dec 2007, Ingo Molnar wrote:
> * H. Peter Anvin <[EMAIL PROTECTED]> wrote:
> > Ingo Molnar wrote:
> >> * Bodo Eggert <[EMAIL PROTECTED]> wrote:
> >>> BTW: The error function in linux-2.6.23/arch/i386/boot/compressed/misc.c
> >>&
Ingo Molnar <[EMAIL PROTECTED]> wrote:
> do you have any memories about the outb_p() use of misc_32.c:
>
> pos = (x + cols * y) * 2; /* Update cursor position */
> outb_p(14, vidport);
> outb_p(0xff & (pos >> 9), vidport+1);
> outb_p(15, vidport);
>
, the NUMLOCK status on Linus' famous laptop should be usable.
---
I'd like some information about how this patch works non non-IBM-compatible
x86 PCs. For now, I've documented the wordt possible outcome I can imagine.
Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
diff -pruN -X dontdiff
, the NUMLOCK status on Linus' famous laptop should be usable.
---
I'd like some information about how this patch works non non-IBM-compatible
x86 PCs. For now, I've documented the wordt possible outcome I can imagine.
Signed-Off-By: Bodo Eggert [EMAIL PROTECTED]
diff -pruN -X dontdiff linux
Ingo Molnar [EMAIL PROTECTED] wrote:
do you have any memories about the outb_p() use of misc_32.c:
pos = (x + cols * y) * 2; /* Update cursor position */
outb_p(14, vidport);
outb_p(0xff (pos 9), vidport+1);
outb_p(15, vidport);
outb_p(0xff
On Sun, 30 Dec 2007, Ingo Molnar wrote:
* H. Peter Anvin [EMAIL PROTECTED] wrote:
Ingo Molnar wrote:
* Bodo Eggert [EMAIL PROTECTED] wrote:
BTW: The error function in linux-2.6.23/arch/i386/boot/compressed/misc.c
uses while(1) without cpu_relax() in order to halt the machine
linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote:
> On Thu, 20 Dec 2007, Sam Ravnborg wrote:
>>> It never gets to the printk(). You were right about the
>>> compilation. Somebody changed the kernel to compile with
>>> parameter passing in REGISTERS! This means that EVERYTHING
>>> needs to be
On Wed, 19 Dec 2007, Al Viro wrote:
> On Wed, Dec 19, 2007 at 02:43:26PM +0100, Bodo Eggert wrote:
> > Since nobody knows about this "security boundary" and everybody knows about
> > the annoying "can't link across bind-mountpoints bug",
>
> ... how
On Wed, 19 Dec 2007, Al Viro wrote:
On Wed, Dec 19, 2007 at 02:43:26PM +0100, Bodo Eggert wrote:
Since nobody knows about this security boundary and everybody knows about
the annoying can't link across bind-mountpoints bug,
... how about teaching people to RTFM? Starting, perhaps
linux-os (Dick Johnson) [EMAIL PROTECTED] wrote:
On Thu, 20 Dec 2007, Sam Ravnborg wrote:
It never gets to the printk(). You were right about the
compilation. Somebody changed the kernel to compile with
parameter passing in REGISTERS! This means that EVERYTHING
needs to be compiled the same
Al Viro <[EMAIL PROTECTED]> wrote:
> On Tue, Dec 18, 2007 at 11:00:16PM +, Al Viro wrote:
>> On Tue, Dec 18, 2007 at 05:46:21PM -0500, Mark Lord wrote:
>> > Why does link(2) not support hard-linking across bind mount points
>> > of the same underlying filesystem ?
>>
>> Because it gives you
Al Viro [EMAIL PROTECTED] wrote:
On Tue, Dec 18, 2007 at 11:00:16PM +, Al Viro wrote:
On Tue, Dec 18, 2007 at 05:46:21PM -0500, Mark Lord wrote:
Why does link(2) not support hard-linking across bind mount points
of the same underlying filesystem ?
Because it gives you a security
Maxim Shchetynin <[EMAIL PROTECTED]> wrote:
> +config AZ_FS
> +tristate "AZFS filesystem support"
> +default m
^
STRONG NACK, I hate digging in the menu tree and hunting for things I
don't need.
> +help
> + Non-buffered
Maxim Shchetynin [EMAIL PROTECTED] wrote:
+config AZ_FS
+tristate AZFS filesystem support
+default m
^
STRONG NACK, I hate digging in the menu tree and hunting for things I
don't need.
+help
+ Non-buffered filesystem
Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
> Some versions of Xen 3.x set their magic number to "xen-3.[12]", so
> relax the test to match them.
> - BUG_ON(memcmp(xen_start_info->magic, "xen-3.0", 7) != 0);
> + BUG_ON(memcmp(xen_start_info->magic, "xen-3", 5) != 0);
Not
Jeremy Fitzhardinge [EMAIL PROTECTED] wrote:
Some versions of Xen 3.x set their magic number to xen-3.[12], so
relax the test to match them.
- BUG_ON(memcmp(xen_start_info-magic, xen-3.0, 7) != 0);
+ BUG_ON(memcmp(xen_start_info-magic, xen-3, 5) != 0);
Not
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 Cox <[EMAIL PROTECTED]> 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 Cox [EMAIL PROTECTED] wrote:
closed. But more
1 - 100 of 739 matches
Mail list logo