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.
Very few people take notes using VI, all newcomers use gedit of leafpad.
Then file management. Then processes. Then and only then pipes because
ps | grep allows for great exercises.
You need piping also to count output lines of basic commands like
ls. Redirection operators are incomplete if one moves piping to be
dealt with elsewhere. The current topic organization looks reasonable
to me: first one learns about text stream filters, then about
redirection and pipes, then one learns about process commands. Finally
one can put everything together to filter commands' output, including
ps, the way he/she likes.
[...]
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?
Is exec really useful
Regardless if one uses it or not in his/her own place, it is required
knowledge indeed.
[...]
In 103.2, is the pr command (designed for matrix printers, which are
seldom used today) really useful?
Little used today, indeed, but one wight want to columnate or
paginate text for other than printing.
I also doubt expand, fmt, join, paste, split and unexpand are heavily
used.
I think people should at least be aware that they exist and perform
some specific actions on text input. People who script a lot, now and
then do need commands that are seldom used on the prompt.
On the other hand, more and less are useful filters, which are not
listed here.
Quote: "*The following is a partial list of the used files, terms and
utilities:*"
In fact, I think the list is too long at 18 items. I think lists should
be limited to half a dozen items, ten at most.
In 103.3, xz should be added to the list of compression programs.
As before.
The title for topic 102, "Linux Installation and Package Management",
is not accurate. Linux installation is not dealt with.
It refers to "102.2 Install a boot manager". Distro installation is
not covered because LPI must keep vendor neutral and installation
programs tend to change pretty often and every distribution has it's
own. We could just consider if we could add an awareness point
concerning the main installation methods generally available, i.e. CD,
USB-stick, network or from an already installed OS.
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.
Myself I know close to nothing of C programming!
[...]
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? Dynamically loaded libraries are used by
userland applications, not by the kernel.
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. Though I do agree this list too is too long, I wonder why you
think a thirteen item list is "awfully long" while you think two more
commands ought to be added to an 18 items long list.
In 106.1, should xhost still be covered given its coarse security?
Basic knowledge of xauth should replace it,
They are both insecure, as they provide no encryption of data sent
over the network. In some protected, closed environments they are still
used (diskless workstations, information booth, info- or
advertisement-panel, and the like).
knowing that ssh -X automatically does everything necessary. In 107.1,
vipw is dearly missing...
Again, lists are not to be considered exhaustive. 107.1 already
lists 12 items...
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.
109.4 should immediately follow 109.2 and so /etc/resolv.conf,
/etc/hosts and /etc/nsswitch.conf should not be covered in 109.2.
Why? The files you list are "Basic network configuration" files.
In 110.2, shouldn't inetd and xinetd be removed? I think they haven't
been used by default on any distribution for quite some time now.
[alessandro@hal9k:~$ ls /etc/*inet*
/etc/inetd.conf /etc/inetd.conf.bak
[alessandro@hal9k:~$ lsb_release -d
Description: Debian GNU/Linux 7.6 (wheezy)
[alessandro@hal9k:~$
http://debian-handbook.info/browse/wheezy/sect.inetd.html
*/ALTERNATIVE/ Other |inetd| commands*
While Debian installs openbsd-inetd by default, there is no lack of
alternatives: we can mention inetutils-inetd, micro-inetd, rlinetd and
xinetd.
Standalone daemons are the default now (even if I still launch my UW
IMAP from inetd, but that's me).
It depends: you might not want them in an embedded device, or a
smartphone or something in between.
Regards,
Alessandro
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
