The kernel program, rarely. Although I'll break out various cpio, squash, etc... images for the ramfs when debugging.
-- Bryan J Smith - UCF '97 Engr - http://www.linkedin.com/in/bjsmith ----------------------------------------------------------------- "In a way, Bortles is the personification of the UCF football program. Each has many of the elements that everyone claims to want, and yet they are nobody's first choice. Coming out of high school, Bortles had the size and the arm to play at a more prestigious program. UCF likewise has the market size and the talent base to play in a more prestigious conference than the American Athletic. But timing and circumstances conspired to put both where they are now." -- Andy Staples, CNN-Sports Illustrated On Fri, Jul 18, 2014 at 11:03 AM, Alessandro Selli < alessandrose...@linux.com> wrote: > Anselm Lingnau wrote: > > [...] > > > I don't think anyone has actually used non-bzImage kernels for the last > decade > > or so. Even kernels that are called »vmlinuz« are bzImage kernels > nowadays, > > simply because today's kernels – at least for the mainstream > distributions > > that LPI focuses on – tend to be way too big to be non-bzImage kernels. > > Is this true for embedded systems, too? I noticed ARM-platform > kernels have some peculiarities that I haven't studied yet (like the > /media/boot directory), but that do set them apart from the typical > 386/x86_64 world. And could someone confirm they are indeed that > different, should we take notice? > > > Regards, > > > Alessandro > _______________________________________________ > lpi-examdev mailing list > lpi-examdev@lpi.org > http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev >
_______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
