Anselm Lingnau ha scritto:
Alessandro Selli wrote (quoting Mehdi Amiri):In this case, a person who is proficient in the "Knowledge of Linux Development and Major Distributions" is expected to know about not just Android, Debian and CentOS, but also about RedHat, Fedora, SuSE/Novell, Ubuntu, Slackware and Mandriva, and possibly a few more.I think this gets silly very quickly. What do you mean »know about« – Know that: 1) they exist, 2) they are a Linux-based OS (and not a soda brand). must MQCs have heard the name and be able to tell that it refers to a Linux distribution (rather than, say, a soft drink brand or a gangsta rap artist), or more? It's open to discussion whether this is enough or if people should also know, for instance, if a specific distro is RPM or DEB based. To me, they should be aware of the principal three software packaging techniques (RPM, DEB and TGZ) and know the major distribution what packaging they use. Do we require MQCs to be able to enumerate three important differences between, say, Ubuntu and CentOS? Could you? Of course i can, but I am not a Linux Essentials candidate. I did not propose a set number of differences such a person should be aware of, too. I am open to proposals and discussion. Could the guy in the next cubicle? Is (s)he interested in a Linux Essentials certification? Between any two distributions from »the List«? Where does the List stop? Turbolinux? Arch Linux? Red Flag Linux? Knoppix? LPI does not produce full requirements and lists, only "a partial list of the used files, terms and utilities". But I do think a prospective Linux Essentials certification candidate should be aware of the *major* Linux distributions. A basic use of netstat is both easy and a useful tool to detect, for instance, currently established TCP/IP connections. Even a beginner, IMO, should be able to do netstat | grep ftp to see if there are currently open FTP sockets. It only involves the notions of Internet connections being ON (that is, ESTABLISHED) and being OFF (everything else). It should not entail any knowledge of TPC protocols, packets, flags and states. for something that new Linux users basically don't need to know. Who can say that? A basic TCP/IP networking knowledge is required almost everywhere one is supposed to put his/her hands on a keyboard. The way for new users to get a Linux machine on the net these days is by plugging in the network cable and letting DHCP do its thing. This does not have anything to do with being a most basic knowledge of TCP connections appropriate in the Linux Essentials Objectives or not. Why is routing considered important while seeing if the Internet connection is working or not irrilevant? Home users will have an already-working DHCP server in their DSL or cable router, and school or enterprise users will have access to one courtesy of their IT department (and are usually not encouraged to set up their own machines, anyway). If things don't work you call the hotline and/or admin. The hotline will probably ask you to check if the Internet connection is configured and working. Manually setting up IP addresses, etc., is, in 2011, not introductory stuff and best left in LPI-102 where it belongs. I never considered introducing manual networking configuration in the Linux Essentials Objectives. But I do think knowing one's box IP address to be relevant to beginners, too. I might be wrong, but doing ip addr list or ifconfig | grep inet does not look like rocket science to me. Having said that, I can see a certain minimal amount of sense in having »ping«, but routing? ifconfig? netstat? resolv.conf (which is incidentally misspelled in the wiki)? Give me a break. This is supposed to be an *introductory* exam. I agree system config files should be left out, but basic networking tools can be used by newbies, with no switches or parameters, just to give a look at how (and if) the ethernet interface is configured. What use is pinging hosts if one does not have the faintest idea of how an Internet connection works, if one ignores even what an IP address is? Also, do note that nslookup has been officially deprecated for a very long time now. host does all that is needed for an Essential certification, and is easier too. Topic 1.3.3 We can also add XZ & 7z, 7-zip suite as well. They are very popular these days,I agree, anyway the same I stated above holds here as well: "The following is a partial list of the used files, terms and utilities" means that the fact lzma, xz etc. are not listed does not mean they are left out of the objective.I don't think the point of this objective is to cover every compression tool under the sun. If you have seen one, you have basically seen them all (or ought to be able to figure them out from the man page). One should at least know that there are at least three ways to compress a file under the sun, and not look in amazement at a tar.xz file with no idea if that is an alien creature or a tropical flower. I do think it is important for the introductory exam to not drag in too much stuff that is not also in LPIC-1. To me the difference is that, though many fields overlap, in the Essentials exam one learns just there there are these strange beasts out in the wild, while in LPIC-1 one learns how to tame them and get them do your job. [...] Think of the introductory exam as a »feeder« for LPIC-1 rather than an independent exam. Right. Now on trying to define what is and what is not a "feeder" :-) Greetings, -- Alessandro Selli, http://alessandro.route-add.net VOIP: sip:[email protected] Chiave PGP/GPG Key: EC885A8B |
_______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
