On Tue, 20 Nov 2001, Michael Jang wrote: > > > The subject of "memory" is hardly addressed neither in the L1 nor L2 test > > objectives. What should we introduce in L1, and where? Some possible > > topics: > > > > - kernel boot option when kernel doesn't recognise all physical memory > > I assume this is the "linux mem=128MB" type of command at the boot prompt > (or in lilo.conf). I thought this issue became obsolete with kernel 2.2. > (unless you need more than 1GB, which I think was addressed with kernel > 2.4). > I beleive you are correct. But, should jr admins be prepared to deal with "legacy" systems which may have these limitations still? If so, understanding these concepts is still relevant and should still be included. An example may be a system in a factory with an internally proprietary program running. The internal program may have been written specific to kernel 2.0 or maybe 2.2. The Jr admin was sent out to upgrade memory on the (hopefully standalone for security purposes) machine, but it only is seeing 64 of the 128 installed...
> > > > - physical memory limits with Linux on IBM-PC-compatible Intel-based > > systems > > With the 64GB limit in kernel 2.4, is this really an issue at this point? Or > should this address the established 4GB limits for 32 bit CPUs? > Not everyone is running 2.4 today, and I think it's still key for admins to realize they may come in contact with older machines. Maybe it'll be important to address there are differences in limits between 32bit and 64bit systems just from a conceptual level? > > > > - limits to address space in Linux > > I think this is a similar issue to physical memory limits - or am I missing > something? > I don't know. Maybe Tom will be nice enough to remember why he said that :) > > > > - use of `free` command > > > > - use of `vmstat` command (recommended from JAS-2) > > These are both good tools to help troubleshoot memory problems (though I > think `top` covers what you see from `free`). > > -- Kara Pritchard Phone: 618-398-7360 Director of Exam Development http://www.lpi.org/ -- -- This message was sent from the lpi-examdev mailing list. Send `unsubscribe lpi-examdev' in the subject to [EMAIL PROTECTED] to leave the list.
