Alessandro Selli <alessandrose...@linux.com> écrit : > Marc Baudoin wrote: > > >Basic shell first. Then vi because file management needs files... > >And it's a good idea to deal with vi soon so that people can use > >it to take notes. > > I disagree. Vi needs to be covered *after* regular expressions > are covered, as they are one of it's strong features. And you do > not need VI to create files: you can touch them, you can echo text > into them, or you can heredoc text into them, all abilities that are > covered in 103.1.
But redirections are in 103.4 (so no echo > ... in 103.1). > >In 103.1, . and source would make more sense in 105.2. > > Aren't they already there? I'm referring to > http://wiki.lpi.org/wiki/LPIC-1, where . and source are not > explicitly listed. What are you referring to? I'm referring to . and source, which are in 103.1 but they would make more sense in 105.2 (people . or source shell scripts, not any kind of executable file). > >I still find it hard to deal with shared libraries with people > >with no knowledge of C programming. > > There is no need to know anything of C programming to teach what > dynamically loaded libraries are and do. But it's much simpler that way. When strace and ltrace were part in 202, explaining their output to somebody with no knowledge of C was pretty difficult. > >Does the 102.3 subtopic, with only 1 question in the exam, needs > >to be maintained here? > > Yes, it definitely has to be there. Any sysadmin must understand > and be able to solve the problem a missing library file can cause to > applications not running or behaving in unexpected ways. > > >It would make much more sense in 201. > > "Linux kernel"? Why? In *exam* 201. > >Enough for 101, let's move to 102. In 105.1, /etc/bash.bashrc is > >missing in the awfully long list of bash configuration files > > The list is 13 items long, and they are not all configuration > files. It includes the commands env, export, set, unset, function, > alias and unalias. And the configuration files of bash, where /etc/bash.bashrc is missing. > Though I do agree this list too is too long, I wonder why you > think a thirteen item list is "awfully long" No, I think bash uses too many configuration files. > >In 109.2, configuration files (/etc/network/interfaces, > >/etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg-*) > >should be covered (they are used by ifup, which is in the > >objectives). > > The /etc/sysconfig/network and > /etc/sysconfig/network-scripts/ifcfg-* files are > distribution-specific. Debian and Ubuntu do not use them, yet they > do have ifup and ifdown. And ifup and ifdown use distribution-specific files so it would be better to cover those files. It's not always possible to ignore distribution-specific stuff and network configuration files are the kind of files we can't afford to ignore. -- Marc Baudoin Linagora formation - responsable pédagogique http://formation.linagora.com/ La présente transmission contient des informations confidentielles appartenant à Linagora, exclusivement destinées au(x) destinataire(s) identifié(s) ci-dessus. Si vous n'en faites pas partie, toute reproduction, distribution ou divulgation de tout ou partie des informations de cette transmission, ou toute action effectuée sur la base de celles-ci vous sont formellement interdites. Si vous avez reçu cette transmission par erreur, nous vous remercions de nous en avertir et de la détruire de votre système d'information. The present transmission contains privileged and confidential information belonging to Linagora, exclusively intended for the recipient(s) thereabove identified. If you are not one of these aforementioned recipients, any reproduction, distribution, disclosure of said information in whole or in part, as well as any action undertaken on the basis of said information are strictly prohibited. If you received the present transmission by mistake, please inform us and destroy it from your messenging and information systems. _______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
