On Wed, Jul 16, 2014 at 8:48 AM, Alessandro Selli <alessandrose...@linux.com > wrote:
> It's foundational to what end? System administration? Network > administration? Security? LPIC-1 is not foundational to everything > Linux. It's foundational to an end user perspective and to basic > Linux-box setup and troubleshooting. IMHO these users need not know > about RFCs Then why is IETF RFC 1918 part of Object 109.1 in Exam 102? People aren't looking at all of these considerations. They just harp on one example I made. Reverse DNS delegation zones I'm _not_ talking about Reverse DNS delegation zones. I'm talking about why we would avoid using CIDR /8, /16 and /24 examples for IPv4 and point out they are the Classful A, B and C subnets. I _only_ mentioned that the Classful subnets are required for many applications and services, only one being in-addr.arpa zones. There are many more examples. And that includes why there are 3 different sets of private reservations in IETF RFC1918 for IPv4, which _is_ in LPIC-1. ;) What really matters is not how difficult is is to explain, but whether > there are going to be questions asked in the exam. Then, like Anselm > just pointed out, each one will be free to beef up his/her own > courseware the way they like (and can). > Any junior sysadmin should know what they are looking at when they run "ip addr" on a system. That's my strongest, educated opinion having dealt with junior sysadmins. I've always looked at LPIC-1 as the foundation of what a junior sysadmin needs to understand to function in an Enterprise environment. To this end, CIDR is enough. > Please explain how CIDR is enough to understand IETF RFC1918. Also please explain how the Classful subnets are going to distract, let alone don't complement, RFC1918. I mean, there's a block reservation for each A, B and C for a reason. ;) I'm attaching an HTML example with two tables I use in basic network 101. > P.S. If you haven't noticed, I'm at odds with how IPv6 (and even IPv4) > > is often taught. We teach people so much cruft and ignore the most > > important, practical things. > I know, the world just *suks* :-) > Or filled with a lot of unnecessary details and not enough practicality. One of the first things I do with any Linux sysadmin is give them the output of "ip addr" from virtually any _stock_ Linux distribution and ask them what they understand about the network. A junior sysadmin should not have to get into bitwise masking and other details, but taught the basic identification realities of common networks. -- bjs
<<< text/html; charset=US-ASCII; name="IPexample.html": Unrecognized >>>
_______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
