Re: Debian initramfs/initrd, was Re: stack smashing detected
On 2/9/23 2:22 AM, John Paul Adrian Glaubitz wrote:
> On Wed, 2023-02-08 at 10:39 -0700, Stan Johnson wrote:
>> On 2/7/23 4:20 PM, Finn Thain wrote:
>>>
>>> On Tue, 7 Feb 2023, Stan Johnson wrote:
>>> ...
>>> Preventing pointless key generation would be beneficial for all Macs,
>>> Amigas, Ataris, emulators etc. and measuring the performance of one model
>>> of Mac versus that of another model seems a bit irrelevant to me.
>>>
>>
>> Sure, but unless Debian unsupported
>
> What do you mean by »Debian unsupported«? You mean »Debian Ports«?
Yes, I mean Debian Ports.
>
>> is willing to manage config files for the various systems, then it's
>> not likely to happen. I currently use separate config files for the
>> following Macs, to build kernels with no initrd, no modules, and only
>> minimal network and video support:
>>
>> 1) 68030 8 MiB, no network (PB-170)
>> 2) 68030 >8 MiB (SE/30, IIci, IIfx, Centris LC III, etc.)
>> 3) 68040 (Centris 650, PB 550c, etc.)
>
> Debian supports different kernel configuration per architecture, the concept
> is called »flavors«. We could certainly add a »-lean« or »-light« flavor
> for smaller systems.
In that case, a "flavor" for small-memory, slower systems would be
great. For example, it wouldn't need keys or certificates, or any of the
things that aren't relevant for early 1990s Macs (USB, Firewire,
wireless, etc.).
>
>> If the stack smashing is caused by a kernel bug that is hidden by
>> Debian's choice of config options, then it would still be useful to
>> identify the bug. If there is something missing from my config files
>> that is causing the problem, then that would still be a kernel bug in
>> its sanity checking of options. Your script will be helpful if it
>> becomes necessary to identify specific offending options.
>
> FWIW, I haven't seen this issue on my Amiga although I haven't run a
> dist-upgrade for a while now. I guess, I am going to do that in the
> near future.
>
> Adrian
>
ok, thanks
-Stan
Reply to:
- References:
- Re: stack smashing detected
- From: Stan Johnson <userm57@yahoo.com>
- Debian initramfs/initrd, was Re: stack smashing detected
- From: Finn Thain <fthain@linux-m68k.org>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: Stan Johnson <userm57@yahoo.com>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: Geert Uytterhoeven <geert@linux-m68k.org>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: Stan Johnson <userm57@yahoo.com>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: Geert Uytterhoeven <geert@linux-m68k.org>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: Stan Johnson <userm57@yahoo.com>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: Finn Thain <fthain@linux-m68k.org>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: Stan Johnson <userm57@yahoo.com>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: Brad Boyer <flar@allandria.com>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: Stan Johnson <userm57@yahoo.com>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: Finn Thain <fthain@linux-m68k.org>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: Stan Johnson <userm57@yahoo.com>
- Re: Debian initramfs/initrd, was Re: stack smashing detected
- From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>