from the quill of Chmouel Boudjnah <[EMAIL PROTECTED]> on scroll
<[EMAIL PROTECTED]>
>
> Yes, and this is a pain to generate with the normal kenrel rpm
> (because i
> will have to list each modules).
I don't think I follow. In my kernel rpm I have a "detour" in the
kernel build to go build freeswan after which it goes back to the kernel
building. When the build for a kernel type X (where X can be fb, smp,
secure) is done, why not just "move" the resulting ipsec.o to ipsec.o-X
and have ipsec.o-fb and ipsec.o-smp, etc. in the freeswan package and
link or move (or whatever) it into the modules directory on installation
depeneding on what kernel is running?
> on the boot you have a block of memory reserved for the bios and after
> you store the whole unziped initrd with unzipped kernel in memory.
Yes, but what I am saying is that I was under the impression that once
the kernel is booted and running, that block of memory that the initrd
disk image was on is freed back to the kernel. From the initrd.txt in
linux/Documentation/initrd.txt:
Operation
---------
When using initrd, the system boots as follows:
1) the boot loader loads the kernel and the initial RAM disk
2) the kernel converts initrd into a "normal" RAM disk and
frees the memory used by initrd
3) initrd is mounted read-write as root
4) /linuxrc is executed (this can be any valid executable, including
shell scripts; it is run with uid 0 and can do basically everything
init can do)
5) when linuxrc terminates, the "real" root file system is mounted
6) if a directory /initrd exists, the initrd is moved there
otherwise, initrd is unmounted
7) the usual boot sequence (e.g. invocation of /sbin/init) is
performed on the root file system
Further thots?
b.
--
Brian J. Murrell InterLinx Support Services, Inc.
North Vancouver, B.C. 604 983 UNIX
Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD
