Theodore Y. Ts'o wrote:
>From: [EMAIL PROTECTED] (Rogier Wolff)
>So under a "good" patch maintenance system, I'd have liked to generate
>the patch, and have it wait until I approve it.
>
> We talked about doing something like that, but at that point you need
> PGP signatures of the
Kai Henningsen wrote:
> A classical memory corruption bug, and like most late-effect bugs hell to
> find without some sort of support for poking around in the actual program
> state.
Agreed. My usual debugging procedure is as follows:
1. try to reproduce the problem
2. make an educated gue
Andre Hedrick wrote:
> On Sat, 9 Sep 2000 [EMAIL PROTECTED] wrote:
> > Would it be possible to detect when the disk spins up, and do the flush then?
> Yes if you had a continuious polling of power status wrt standby.
I think the following flushing policy would work almost as well, while
remaining
Ingo Molnar wrote:
> On 2 Sep 2000, Jes Sorensen wrote:
> > Besides that you need to do copy-on-write if you want to be able to do
> > zero copy on write() from user space [...]
>
> i agree that this is hard - i'm not sure wether we want to go the pain to
> enable anonymous-buffer write()s do zer
Andi Kleen wrote:
> I'm not sure I understand the question. It would basically work like
> booting in BSD or most other Unixes: the bootloader knows ext2 and
> reads a filename that you pass as a command line option or a default
> from /. That file name would be available in the environment that i
Jan-Benedict Glaw wrote:
> On Thu, Aug 31, 2000 at 04:26:55PM +0200, [EMAIL PROTECTED] wrote:
> > But what about GRUB, LOADLIN, SILO, MILO, ... ?)
>
> I've written scripts do copy any useful piece of (debug) info to
> /boot. To cope with MILO, you can use:
Actually, this was a trick question, so
Andi Kleen wrote:
> What you need is a bootloader than can read uncompressed vmlinux directly,
> and use that for booting. Then you can always directly extract the System.map
> out of the vmlinux using nm or gdb.
And then pass this information to the soon to be running system via e.g.
an initrd
Alan Cox wrote:
> Use that argument 50 times and your kernel has grown 100K. Unfortunately
> everyone keeps using the argument and forgetting the cumulative effect
:-) The thing is that this information is something you access when
something is already going wrong. So avoiding a few possible fai
[EMAIL PROTECTED] wrote:
> Alan Cox wrote:
>> So cat it with a magic lead in after the bzImage gzip block into the bzImage.
> Granted, all those are borderline cases, but then 1-2 kB doesn't look
> like too high a price to pay for a solution that is inherently robust.
Ah, sorry, I first mis-read
Alan Cox wrote:
> > /lib/modules//.config is a big step up from the current situation
> > and I'm grateful. But I do want /proc/config.gz in the kernel.
>
> So cat it with a magic lead in after the bzImage gzip block into the bzImage.
> If you dont even know what file you are running for kernel
10 matches
Mail list logo
