account as expected.
Regards
Congratulations
Colonel Marion Horn Jr.
Executive trustee.
>>Hmm, I would have thought that /proc was more up to date, because it
>>would reflect changes. No reboot, never even considered it (I've
>>rescued too many junior sysadmins that think rebooting is _the_ answer).
>
>/proc/ksyms is dynamic, it changes as modules are loaded and unloaded.
>And ofte
In clouddancer.list.kernel, you wrote:
>
>Further to that, I followed Alan's lead and installed xfce. My laptop, which
>was really suffering under Gnome with 64 meg (much more so under KDE) is
>suddenly light on its feet. Not to mention that it built from source in
>under 10 minutes and insta
In clouddancer.list.kernel, you wrote:
>
>Hi all,
>
>Haven't been on this list for a while, and don't really know if this is the
>right place for this message... If not, pls let me know.
>...
>Hope you guys can do something with this message!
Nope. You need to run it thru ksymoops before the wi
In clouddancer.list.kernel, you wrote:
>
>On Mon, 25 Jun 2001 08:15:49 -0700 (PDT),
>[EMAIL PROTECTED] (Colonel) wrote:
>>ksymoops 2.4.1 on i686 2.4.5-ac12. Options used
>>Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says
>c01aad00,
>> POST IT. Give the rest of us some clues and the opportunity to check
>> evaluator's replies.
>
>Well, if you try that strategy you'll find you never get around to posting it
>because you'll be too worried about getting it right. The point is not to
>get it right, it's to get a starting poi
Why the symbol mismatch? Why ignore /proc over the System.map?
The system had very little running (because of prior lockups) during
the morning SQL activity. About 3/4 of a megabyte was being added to
the SQL databases, and that activity had been going on for 45 minutes
prior to the oops. No X,
In clouddancer.list.kernel, you wrote:
>
>On Monday 25 June 2001 03:46, Russell Leighton wrote:
>> I read this thread as asking the question:
>>
>> If VM management is viewed as an optimization problem,
>> then what exactly is the function that you are optimizing and what are
>> the constr
In clouddancer.list.kernel, you wrote:
>
>On Sun, 24 Jun 2001, Colonel wrote:
>
>> It's simple. I want the old reliable behavior back, the one I found
>> in kernels from 1.1.41 thru 2.2.14.
>
>And which one would that be ? Note that there have been
>4 diffe
In clouddancer.list.kernel, you wrote:
>
>Colonel wrote:
>> Ah, notice that the IRQ shifted? Perhaps there is something else on
>> irq 10, such as the SCSI controller? My video cards always end up on
>> that IRQ, perhaps the computer is still accessible via the networ
In clouddancer.list.kernel, you wrote:
>
>On Thu, 21 Jun 2001, Jason McMullan wrote:
>
>> One we know how we would 'train' our little VM critter, we
>> will know how to measure its performance. Once we have measures, we
>> can have good benchmarks. Once we have good benchmarks - we can pick
In clouddancer.list.kernel, you wrote:
>bttv0: Bt848 (rev 18) at 00:0f.0, irq: 10, latency: 64, memory: 0xd79ff000
> ** ^^ this worked in 2.2.19 as
>bttv0: Brooktree Bt848 (rev 18) bus: 0, devfn: 88, irq: 11, memory:
>
>It shouldn't matter, as userspace programs should not be able te fuck te
>
In clouddancer.list.kernel, you wrote:
>
> I upgraded a fileserver to 2.4.5 because of the RAID support (the 0.90
>patch I grabbed did not apply cleanly to 2.2.19, despite it being a fresh
>copy).
Look in the people/mingo directory for a patch
> Besides a nice speed increase (the EEPro no
Attempting to boot my 2.4 test box got as far as:
"Uncompressing Linux... Ok, booting the kernel"
It has been running previous versions of (working) 2.4 releases.
--My pid is Inigo Montoya. You killed -9 my parent process. Prepare to vi.
-
To unsubscribe from this list: send the line "un
In clouddancer.list.kernel, you wrote:
>
>Hi,
>
>I just added 128 MB of RAM to my machine which already had 128 MB and
>which has 128 MB swap. 128 MB RAM + 128 MB swap (either the new or the
>old 128 MB RAM) works, but the combination of that, 256 MB RAM + 128 MB
>swap, crashes the compu during st
In clouddancer.list.kernel, you wrote:
>
>[EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>> I have to ask, is this something you wrote, or an actual log from
>> something you wrote? (=:]
>
>What? Moi, perpetrate a trifling and crude hoax? You wound me, sir,
>by supposing I would ever stoop to such gauch
In list.kernel, you wrote:
>i think we are all missing the ball here: i am happy when i see driver
>support for a piece of hardware that i have _NEVER_ heard of and at most
>_ONE_ person uses it. why? it means more stuff works in linux. we
>dont need to defend how many people use hardware X.
In list.kernel, you wrote:
>
>Anyone concerned about the current size of the kernel source code? I am, and
No. Since you are up to date with the latest in everything, I cannot
see why you would be concerned about a few megabytes in your gigabyte
drives.
>i386, i486
>The Pentium processor has b
From: Colonel <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
In-reply-to: <[EMAIL PROTECTED]>
(message from Luigi Genoni on Wed, 13 Jun 2001 11:32:35 +0200 (CEST))
Subject: Re: your mail
Reply-to: [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
From: Colonel <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: ISA Soundblaster problem
Reply-to: [EMAIL PROTECTED]
The Maintainers list does not contain anyone for 2.4 Soundblaster
modules, so perhaps some one on the mailing list is aware of a
solution. My ISA Soundblaster 16wave
When the OOM kills the process that I am currently composing within
(an active character stream), that is a MICROSOFT WINDOWS behavior.
I don't care if it's hogging the machine, *I'M* using it! That is the
point after all, isn't it? A human sysadmin could kill my process
(and then I would hav
From: Colonel <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
In-reply-to: <[EMAIL PROTECTED]>
(message from Marcelo Tosatti on Mon, 23 Apr 2001 20:31:12 -0300
(BRT))
Subject: Re: 2.4.4-pre6 : THANKS! very snappy here [nt]
Reply-to: [EMAIL PROTECTED
In list.kernel, axel <[EMAIL PROTECTED]> wrote:
>
>How about correcting the needed gcc version in Documentation/Changes?
Linux, with up to date documention?? In your dreams perhaps.
>On Mon, 23 Apr 2001, Alan Cox wrote:
>
>> > after having had trouble with compilation due to old gcc version,
While tracking down a sound problem, I decided to compile in the
soundblaster rather than use modules. It's been a long time since I
ran sound under linux, but that used to work fine.
I watched the reboot, noticed the usual isapnp stuff (part of problem)
...
PCI: Probing PCI hardware
Limiting d
NT = no text
but since you read it, system seems like it's running twice as fast
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
In list.kernel, you wrote:
>
>
>cannot compile 2.4.4-pre6. This may have been reported, but I
>haven't seen it.
There was a solution mentioned Saturday.
>rwsem.o(.text+0x30): undefined reference to `__builtin_expect'
>rwsem.o(.text+0x73): undefined reference to `__builtin_expect'
>make: *** [vm
In list.kernel, linas wrote:
>
>First problem: In kernel-2.4.2 and earlier, if the machine is not cleanly
>shut down, then upon reboot, RAID reconstruction is automatically started.
>(For RAID-1, this more-or-less ammounts to copying the entire contents
>of one disk partition on one disk to anoth
In list.kernel, you wrote:
>
>On Tue, Apr 03, 2001 at 06:14:33PM -0700, Michael Peddemors wrote:
>> I think that this is one list where we have to keep the ability to post
>> from individuals separate from the need to make sure that their ISP or
>> company is compliant to a set a of rules.. The L
In kernel.list, you wrote:
>
>Oh, I realize this. I don't mind and even expect the occational crash
>right now in the 2.4.x series, but the frequency of these crashes fall
Well, you say this, but
...more whinny post deleted...
>to begin to help fix this problem (or these problems).
Twice your
> Linus,
> At present, drivers/video/chipsfb.c can only be used on PPC, and it
> doesn't compile even on PPC. The patch below makes it compile, and
> by changing it to use the generic inb/outb, means that there is at
> least a chance it can be used on other platforms. The patch is
> against 2.
In list.kernel.owner, you wrote:
>
>I want to report a constant problem I'm having with the loopback block driver
>in the new releases of the 2.4.x series of the Linux kernel.
Pick up the loop patches from Axboe at :
*.kernel.org/pub/linux/kernel/people/axboe/patches/
I solved all my problems w
From: "Tom Sightler" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Date: Tue, 20 Feb 2001 14:43:07 -0500
Content-Type: text/plain;
charset="iso-8859-1"
>> >I'm building a firewall on a P133 with 48 MB of memory using RH 7.0,
>> >latest updates, etc. and kernel 2
>There seem to be several reports of reiserfs falling over when memory is
>low. It seems to be undetermined if this problem is actually reiserfs
> or MM related, but there are other threads on this list regarding similar
> issues. This would explain why the same disk would wo
From: "Tom Sightler" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Date: Tue, 20 Feb 2001 14:43:07 -0500
Content-Type: text/plain;
charset="iso-8859-1"
>> >I'm building a firewall on a P133 with 48 MB of memory using RH 7.0,
>> >latest updates, etc. and kernel 2
Sender: [EMAIL PROTECTED]
Date: Tue, 20 Feb 2001 11:32:19 -0600
From: "James A. Pattie" <[EMAIL PROTECTED]>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
Colonel wrote:
> In clouddancer.list.kernel.owner, you wrote:
> >
>
For the other list readers with problems:
I used patch 2.4.2-pre2 (not pre3)
plus axboe's loop-4 patch (in the people directory).
[EMAIL PROTECTED]:/pub/linux/kernel/people/axboe/patches/2.4.2-pre1
It solves most problems here.
-
To unsubscribe from this list: send the line "unsubscribe
>mount -o loop=/dev/loop1 net.i /var/mnt/image/
ends up in an uninterruptable sleep state (system cannot umount /
during shutdown).
The test system is a 100MHz 486 Planar wall mount, same problem with
or without modules. The proper fs support is present in the kernel,
while CONFIG_DEVFS_FS is
37 matches
Mail list logo
