On Fri, 11 May 2001, Matti Aarnio wrote:
> *) "systems" include vger itself (it has died this week alone 4-5 times),
Yikes! That's not a very good advertisement. Anything
that the Linux-using public should know about?
Matthew.
-
To unsubscribe from this list: send the line "unsubscribe lin
On Sun, 22 Apr 2001, Russell King wrote:
> > C: CONFIG_SCSI_BLARG
> > F: drivers/scsi/blarg.c
> > F: drivers/scsi/blarg.h
> And what would:
>
> C: CONFIG_ARM
>
> tell you? Nothing that is not described in the rest of the "ARM PORT"
> entry.
True, but it would tell it to a script without interv
On Tue, 6 Mar 2001, Jonathan Lahr wrote:
[ sorry to reply over another reply, but I don't have
the original of this ]
> > Tridge and I tried out the postgresql benchmark you used here and this
> > contention is due to a bug in postgres. From a quick strace, we found
> > the threads do a load o
On Tue, 27 Feb 2001, icognito wrote:
> anyone know if there is an updated repository for the linux-wlan
> project? i need drivers for the baystack 660 and none of the wlan n
> modules in the distro in the site
> (http://www.linux-wlan.com/linux-wlan/linux-wlan-0.3.4.tar.gz) compile
> under 2.4.2.
On Thu, 22 Feb 2001, Robert Read wrote:
> Please apply one line patch to the top level Makefile. This points
> the build tools at the correct linux include dir.
Or please don't, it's incorrect.
It breaks cross-compiling, and just generally wrong. If your
system won't build without this, it's
ng the problem for me for now. (it could be entirely
> wrong, but it's letting me at least get some other work done :)
Thanks.
Below is what Andi Kleen sent me last time this came up.
Matthew.
>From [EMAIL PROTECTED] Thu Feb 22 15:19:51 2001
Date: Mon, 4 Sep 2000 12:06:02 +0200
From:
On Mon, 19 Feb 2001, Jeff Garzik wrote:
> > But, unfortunately, sendfile (in 2.2 and 2.4) appears not
> > to support sendfile(2)ing a device:
>
> Correct... sendfile(2) is only for sources/destinations that can be
> ripped through the page cache.
I knew that, but was surprised that /dev/zero did
Hi,
I'm looking for a fast way to initialise a file to zeroes
(without holes) and reckoned that sendfile from /dev/zero
would be the way to go.
But, unfortunately, sendfile (in 2.2 and 2.4) appears not
to support sendfile(2)ing a device:
$ cat foo.c
main()
{
if(sendfile(1, 0, 0, 1024) <
On Thu, 8 Feb 2001, dean gaudet wrote:
> responses come back from both eth0 and eth1, listing each of their
> respective MAC addresses... it's essentially a race condition at this
> point as to whether i'll get the right MAC address. ("right" means
> the MAC for server:eth1).
2.2.18 and 2.4 ap
On Tue, 30 Jan 2001, Rik van Riel wrote:
> While reclaiming swap space when you run out is pretty
> trivial to do, Linus doesn't seem to like the idea all
> that much and Disk Space Is Cheap(tm) so it's not very
> high on my list of things to do.
'anybody who says "disk is cheap" deserves to be
On Mon, 8 Jan 2001, Paul Powell wrote:
> 'console=ttys0','console=cua0','console=ttys0,9600n8', etc
^
console=ttyS0
Matthew.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://w
On Mon, 11 Dec 2000, Frédéric L . W . Meunier wrote:
> > I disagree with the patch. The bug is in printk
>
> No problem. So, it's a bug report instead. I have no clues, and just
> thought it'd be a fix :)
>
> Not sure if 2.2.17 reported the double %% from syslog. I usually look
> at my dmesg.
If
On Sat, 9 Dec 2000, Matthew Kirkwood wrote:
> I once managed to make it assign a socket 0 card to both sockets
> and completely ignore socket 1, but can't reproduce this now.
Did it again. It seems that if I boot with anything
in socket 0, socket 1 becomes useless.
Matthew.
-
To
Hi,
It seems that the BUG() at skbuff.c:175 (2.4.0test12pre7)
kills the machine dead; BUG() isn't (or doesn't appear to
be) interrupt safe:
alloc_skb called nonatomically from interrupt c0194b81
kernel BUG at skbuff.c:175!
invalid operand:
[..]
Code: 0f 0b 83 c4 0c 89 f6 83 e7 fe be 20 c5 2
Hi,
The aforementioned kernel seems to have a minor bug on
(at least) my laptop -- it looks like a potential off-
by-one in the socket handling:
After a clean bootup:
# cardctl status 0
no card
# cardctl status 1
no card
Insert a card in socket 0
# cardctl status 0
no card
# cardctl statu
On 1 Dec 2000, H. Peter Anvin wrote:
> > open("/dev/random", O_RDONLY) = 3
> > read(3, "q\321Nu\204\251^\234i\254\350\370\363\"\305\366R\2708V"..., 72) = 29
> > close(3)= 0
> >
> > Have the semantics of the device changed, or is vpnd doing
> > something w
On Fri, 1 Dec 2000 [EMAIL PROTECTED] wrote:
> > open("/dev/random", O_RDONLY) = 3
> > read(3, "q\321Nu\204\251^\234i\254\350\370\363\"\305\366R\2708V"..., 72) = 29
> > close(3)= 0
> I've seen that happen with kernel version 2.2.16!
Indeed, you are corre
Hi,
It looks like the random driver in 2.4test will return a
short read, rather than blocking. This is breaking vpnd
(http://sunsite.dk/vpnd/) which breaks with "failed to
gather random data" or similar.
Here's a sample strace:
open("/dev/random", O_RDONLY) = 3
read(3, "q\321Nu\204\2
On Sat, 25 Nov 2000, J . A . Magallon wrote:
> Could the default target install names int the std kernel be changed to
> System.map -> System.map-$(KERNELRELEASE)
> vmlinuz-> vmlinuz-$(KERNELRELEASE)
> and then symlink to that ?
>
> I think everyone that has a stable2.2, a devel 2.2 and a te
On Fri, 17 Nov 2000, Russell King wrote:
> Therefore, it should be reserved independent of whether we have the
> driver loaded/in kernel or not.
Is this not an argument for a more flexible resource allocation
API? One offering both:
res = allocate_resource(restype, dev, RES_ALLOC_UNUSED, re
On Tue, 7 Nov 2000, Jeff V. Merkey wrote:
(Please forgive this snippage making Jeff look less literate
than he is, even after several beers.)
> We need a format that allow
[..]
> the right one based on architecture.
Oh, we already have that. It's called source code.
Matthew.
-
To unsubscribe
On Sat, 23 Sep 2000, safemode wrote:
> Reply ALL also results in 2 mails being sent instead of one but of
> course this is usually not a problem since one is going direct and the
> other is going through vger, but still... it's kind of wasteful to
> resources and i dont see any harm in Reply-to b
Tsk, forgot the cc.
-- Forwarded message --
Date: Thu, 21 Sep 2000 23:59:09 +0100 (BST)
From: Matthew Kirkwood <[EMAIL PROTECTED]>
To: Linus Torvalds <[EMAIL PROTECTED]>
Subject: [PATCH] RAID autorun fix
Hi,
The attached diff makes RAID autorun work for me.
I
Hi,
It seems that it's fairly easy to get a ramfs stuck:
# mkdir bar
# mount -t ramfs bar bar
# umount bar
# mount -t ramfs bar bar
# chown nobody bar
# umount bar
umount: /root/bar: device is busy
#
This doesn't appear to affect ext2 filesystems, though.
Matthew
--
$ grep -c ramfs /proc/moun
On Tue, 19 Sep 2000, Linus Torvalds wrote:
> > moving the software RAID drivers into drivers/md/,
> Make it so.
OK. Apply the attached diff and then:
$ mv drivers/block/{md,raid{0,1,5},xor}.c drivers/md/
and all might be well.
The Config.in should probably move at some stage too.
I'm not v
Hi,
It would appear that the changes in pre3 and pre4 break
RAID autorun. This is rather bothersome for those who
have RAIDed root filesystems.
It's probably solely an init-order thing but, short of
moving the software RAID drivers into drivers/md/, I
can't see an easy way to fix it.
cheers,
M
On Thu, 14 Sep 2000, David S. Miller wrote:
>Does anyone think that allocating skbs during system idle time
>would be useful?
>
> I really don't like these sorts of things, because it makes an
> assumption as to what memory is about to be used for.
I agree. Surely The Linux Way (tm) wo
On Wed, 13 Sep 2000, Torben Mathiasen wrote:
> > 2.4 seems to have problems scanning SCSI busses.
> Could you try out this patch. The module_init/exit stuff in sd.c has
> given some people a real headache.
Worked great, thanks.
Matthew.
-
To unsubscribe from this list: send the line "unsubscr
On Wed, 13 Sep 2000, Alan Cox wrote:
> > [1] I understand the RAID issue with disk format compatibility, which
> > makes the current RAID patch unacceptable for official 2.2 usage.
> > I just wish somebody would *solve* that issue.[2]
> Solve that and the tool back compatibility problem
On Wed, 13 Sep 2000, Torben Mathiasen wrote:
> > 2.4 seems to have problems scanning SCSI busses.
> Could you try out this patch. The module_init/exit stuff in sd.c has
> given some people a real headache.
I don't have sd modularised. Will it make any difference?
MAtthew.
-
To unsubscribe fr
hdd, hde and hdf. /proc/scsi/scsi shows only three, but
/proc/partitions shows six.
More information is below in a correspondance that I had
with the 395 driver author.
Is this a familiar picture to anyone?
Matthew.
-- Forwarded message --
Date: Wed, 13 Sep 2000 15:41:36 +0100 (BS
On Tue, 12 Sep 2000, Rik van Riel wrote:
[ outrageous cc: list trimmed ]
> > >We simply keep track of how old the oldest request
> > >in the queue is, and when that request is getting
> > >too old (say 1/2 second), we /stop/ all the others
> >
> > Going in function of time is obviously wrong. A
On Sun, 10 Sep 2000, David S. Miller wrote:
>Over on the freebsd-questions mailing list you can see desperate
>people trying to convert Linux systems over to that other OS to
>escape Linux 2.2.xx NFS. This is kind of serious, you know?
>
> So basically the situation is that people pre
Hi,
In the past few days, a couple of our webservers (dual P3s)
have started to emit $SUBJECT into the kernel logs fairly
frequently:
Sep 7 06:41:04 web2 kernel: initial req->mss below 8
Sep 7 06:56:03 web2 last message repeated 18 times
Sep 7 07:56:04 web2 last message repeated 18 times
Sep
On Mon, 4 Sep 2000, Andi Kleen wrote:
> > /proc/sys/net/ipv4/\"correct\"_arp_reply_interface_selection
> It is called arpfilter. Here is the old 2.2.16 version (applies to 2.4
> with minor changes)
>
> It is useful for various things, one of them being automatic load
> balancing for incoming con
On Mon, 4 Sep 2000, Bartlomiej Zolnierkiewicz wrote:
> > > > Odd. I started seeing mailbox corruption the day before the first post
> > > > showed up here. Since it was only one list (BUGTRAQ) and I'm still at
> > >
> > > weird. currently my pine crashes on me when i close my bugtraq
> > > fold
On Sat, 2 Sep 2000, Alan Cox wrote:
> > I see the point, but it bites sufficiently often that I don't
> > understand why there is no interesting in improving this
> > behaviour.
>
> For a large number of scenarios it makes vastly more sense.
Please forgive my obtuseness, but I am unable to conce
On Sun, 3 Sep 2000, Neal H Walfield wrote:
> Starting twelve days ago the load average has increased by one every
> twenty-four hours. Normally, it remains close to 0. At the moment,
> they are at twelve; I imagine that tomorrow, they will be at thirteen:
Does the kernel log show any oopses?
On Sat, 2 Sep 2000, Alan Cox wrote:
> Fix your routing tables ?
and several other people have said similar things in the past.
I see the point, but it bites sufficiently often that I don't
understand why there is no interesting in improving this
behaviour.
I have several hosts with multiple or
On Thu, 31 Aug 2000, Andi Kleen wrote:
> > > And why is nvram access not SYS_RAWIO ?
> >
> > You cant make the nvram tamper with arbitary memory
>
> But it is clearly hardware access isn't it ?
So is /dev/fd0. And you can set a lot of interesting
ioctl()s with a handle to that and CAP_SYS_AD
On Thu, 31 Aug 2000, Andi Kleen wrote:
> > > Clearly? How do MTRR changes relate to rawio ?
> >
> > RAWIO is about hardware level access not Stephens O_DIRECT stuff
>
> So why is /proc/kcore access SYS_RAWIO then ?
I kind of overloaded CAP_SYS_RAWIO to restrict access to bits
of arbitrary memor
On Thu, 31 Aug 2000, Tigran Aivazian wrote:
> Actually, microcode driver checks CAP_SYS_RAWIO only on open() so it
> would allow access to the receiver of fd even he has no CAP_SYS_RAWIO
> privilege. Hmmm, maybe I should put it back into write() method, as
> Linus (or someone else) did at some po
On Wed, 30 Aug 2000, Arnaldo Carvalho de Melo wrote:
> Please consider applying.
And then please don't apply.
>case MTRRIOC_ADD_ENTRY:
> - if ( !suser () ) return -EPERM;
> + if ( !capable(CAP_SYS_ADMIN) ) return -EPERM;
Please think further about these random cha
43 matches
Mail list logo
