On Wed, Jan 12, 2011 at 07:04:55PM +0900, Toru Nishimura wrote:
> Another possiblity
> is to have DDB symbol table as a module. This would wape out
> the awesome burdern of SYMTAB_SPACE maintaintance when
> LIBSA bootloader is made smart enough to do that.
I'm sure the SYMTAB space fubar could be
> > options MEMORY_DISK_DYNAMIC ?
>
> miniroot.kmod works in an automagical way. I'm afraid that it's a
> bad concidence to keep adding MD_HOOK_BOO to solve situations.
Fortunately MEMORY_DISK_DYNAMIC is already in options(4).
> > We have to move boot.cfg(5) support and loading module
> > fun
options MEMORY_DISK_DYNAMIC ?
miniroot.kmod works in an automagical way. I'm afraid that it's a
bad concidence to keep adding MD_HOOK_BOO to solve situations.
We have to move boot.cfg(5) support and loading module
functions from i386/stand to MI libsa, I think.
I feel hesitated to do so si
> MODULAR miniroot.kmod would be benefitial to small
> embedded NetBSD products. miniroot.kmod is, in
> essense, a kind of "root on md0" switch.
options MEMORY_DISK_DYNAMIC ?
> MODULAR-aware
> LIBSA can choose to switch the target md0 image whose
> content is stripped down userland.
We have to
This eliminates the necessity to build a separate
INSTALL kernel which holds mdimage inside.
MODULAR miniroot.kmod would be benefitial to small
embedded NetBSD products. miniroot.kmod is, in
essense, a kind of "root on md0" switch. MODULAR-aware
LIBSA can choose to switch the target md0 image
This eliminates the necessity to build a separate
INSTALL kernel which holds mdimage inside.
That's what i386 did and miniroot.kmod was loaded via boot.cfg(5)
like distrib/i386/cdroms/installcd/boot.cfg.in in netbsd-5.
(-current doesn't use miniroot.kmod and use cd9660 root fs)
It's my routine
> The most interesting part of module preload facility is to allow
> miniroot.kmod. This eliminates the necessity to build a separate
> INSTALL kernel which holds mdimage inside.
That's what i386 did and miniroot.kmod was loaded via boot.cfg(5)
like distrib/i386/cdroms/installcd/boot.cfg.in in ne
Izumi Tsutui points;
It checks a file system type where the kernel is (to be) loaded
It's a norm case that a target kernel is stored in rootfs, I think.
Toru Nishimura / ALKYL Technology
> > So necessary info might be "which file-system modules are builtin?"
>
> LIBSA does heuristics to find rootfs type and then stats to see it can be
> loaded
> from a local or remote store.
It checks a file system type where the kernel is loaded
(as sys/arch/i386/stand/lib/exec.c:command_load_k
"Izumi Tsutsui" said;
So necessary info might be "which file-system modules are builtin?"
LIBSA does heuristics to find rootfs type and then stats to see it can be loaded
from a local or remote store.
(though I'm not sure if options NFS_BOOT_DHCP requires bpf(4) module or not)
The code se
"matthew green" points;
a flag that says "we want to try to load modules in the loader".
The most interesting part of module preload facility is to allow
miniroot.kmod. This eliminates the necessity to build a separate
INSTALL kernel which holds mdimage inside. Another possiblity
is to have
> > It would be nice if ELF kernel image holds "modules_enabled" value in
> > note section which allows LIBSA to tell whether the target kernel is
> > MODULAR or not.
>
> modular kernels don't *have* to have modules loaded via the boot
> loader. so what i think you're really after is a flag that
On Wed, Jan 12, 2011 at 01:59:42PM +1100, matthew green wrote:
> modular kernels don't *have* to have modules loaded via the boot
> loader. so what i think you're really after is a flag that says
> "we want to try to load modules in the loader".
We could have a note section that makes it easy to
> It would be nice if ELF kernel image holds "modules_enabled" value in
> note section which allows LIBSA to tell whether the target kernel is
> MODULAR or not.
modular kernels don't *have* to have modules loaded via the boot
loader. so what i think you're really after is a flag that says
"we wa
Folks,
It would be nice if ELF kernel image holds "modules_enabled" value in
note section which allows LIBSA to tell whether the target kernel is
MODULAR or not.
Toru Nishimura / ALKYL Technology
15 matches
Mail list logo
