On 2018/08/30 20:54, D'Arcy Cain wrote:
My latest build of NetBSD 8 results in a kernel size of 24,964,488
bytes. Not sure if "kernel" is really the right term any more. :-)
I have installed it on all of my servers except for one. It is a HP
ProLiant DL160se G6. The failure is something like
On Thu, 30 Aug 2018, Edgar Fu? wrote:
Anyone know what my next steps are?
I usually manually cut down my kernel size (formerly, I used adjustkernel
for that) by digging through dmesg.boot and the kernel config. With the
cut-down kernel, I then look for "not configured" messages in dmesg.boot.
M
Paul Goyette wrote:
>I've been running a load-everything-as-modules-when-needed system for
>years. :) My 8.99.22 kernel weighs in at under 12MB:
>
>-rwxr-xr-x 1 root wheel 12102488 Jul 26 14:00 /netbsd
I don't even build modules, this is the kernel on my main machine:
-rwxr-xr-x 1 root
On Thu, 30 Aug 2018, Greg Troxel wrote:
Two thoughts:
When trimming, ls -lSr in the kernel build directory will identify
large objects.
We have had kernel modules for a while, but I'm not entirely clear on
where we are. I would think that moving to a mode of aggressively not
including t
If anyone is interested in reducing large sizes, try this:
$ nm --print-size --size-sort --radix=d /netbsd
some of the biggest offenders come from:
neo(4)'s neo-ceoff.h
sys/dev/microcode in general
etc.
Also, looking at it with xxd, a lot of stuff is just zeroes.
I assumed it is the alignment pa
On 2018-08-30 10:00 AM, Mouse wrote:
>> My latest build of NetBSD 8 results in a kernel size of 24,964,488
>> bytes. Not sure if "kernel" is really the right term any more. :-)
>
> Indeed!
>
> I had a similar experience recently; it was with 5.2, but I suspect
> much the same applies to -8. I
Two thoughts:
When trimming, ls -lSr in the kernel build directory will identify
large objects.
We have had kernel modules for a while, but I'm not entirely clear on
where we are. I would think that moving to a mode of aggressively not
including things that can be modules and loading
> My latest build of NetBSD 8 results in a kernel size of 24,964,488
> bytes. Not sure if "kernel" is really the right term any more. :-)
Indeed!
I had a similar experience recently; it was with 5.2, but I suspect
much the same applies to -8. I wanted a kernel that booted faster,
rather than b
> Anyone know what my next steps are?
I usually manually cut down my kernel size (formerly, I used adjustkernel
for that) by digging through dmesg.boot and the kernel config. With the
cut-down kernel, I then look for "not configured" messages in dmesg.boot.
My 8 kernel is 12MB (for 6, it was 7,3M
My latest build of NetBSD 8 results in a kernel size of 24,964,488
bytes. Not sure if "kernel" is really the right term any more. :-)
I have installed it on all of my servers except for one. It is a HP
ProLiant DL160se G6. The failure is something like this:
Read header failed: input/output e
10 matches
Mail list logo
