G. Matthew Rice ha scritto: > On Thu, Sep 29, 2011 at 12:46 PM, Alessandro Selli > <[email protected]> wrote: > >> 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. >> > Are you certain?
About the almost? Pretty well, yeah. :-) > I know many proficient C/xxx programmers on Linux > that barely grasp the IP experience (they just aren't into that sort > of stuff; they do scientific stuff on Linux/Unix). They also whine > about pointers, though, ... > I know people are lazy and would rather learn less than more no matter what they are supposed to do. I do consider the use of such commands as ifconfig/ip, route and netstat as a non privileged user important to beginners to allow them to perform the most basic form of troubleshooting, but if the Linux Essentials Objectives must not be burdened with any troubleshooting at all, if we agree that a beginner must rely on external professional assistance to understand why he cannot browse his favorite pr0n sites on his meal break, then I will drop my point. >> 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. >> > You seem to be arguing out this issue in the e-mail but it looks like > you came to the same conclusion as Anselm and a few others; less > networking. Or the attribution '>'s may be getting messed up. > I'm arguing in favour of the inclusion of the ifconfig/ip, route, host and netstat commands in the Linux Essentials Objectives; however I do not agree with Anselm that this involves including «Manually setting up IP addresses» and like skills. To me all people should know is: 1) each host on a net has a unique IP address like 192.168.1.25 (no mention of IPv6, net addresses and netmasks); 2) a host on a net can communicate with hosts on other nets via a router (without detailing what difference there is between host- and net-routing); 3) a user can see the IP address of his/her box running the ip addr list or the ifconfig command; 4) a user can see the routing table running the ip route list or route commands (candidates should be able to tell if there is a default gateway or not, that's all); 5) a user can get the IP address of another host with the host command. 5b) And you can ping that bastard, too! :-) To me including the use of ping without these topics does not make sense; what use is ping if one cannot understand any of the data it produces on the screen? >> 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. >> > How about the file(1) command, then? > Ain't that command terribly useful and cool and ridiculously easy? :-) With kind regards, -- Alessandro Selli Tel: 340.839.73.05 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
