On Thu, Sep 29, 2011 at 07:08:12PM +0200, Alessandro Selli wrote:
> <html>
>   <head>
>     <meta content="text/html; charset=windows-1252"
>       http-equiv="Content-Type">
>   </head>
>   <body bgcolor="#FFFFFF" text="#000000">
>     G. Matthew Rice ha scritto:
>     <blockquote
> cite="mid:cafkqhhmhfdqf53yy_touiicy-vkbh7qnfrg9kbm-+oe36v6...@mail.gmail.com"
>       type="cite">
>       <pre wrap="">On Thu, Sep 29, 2011 at 4:28 AM, Alessandro Selli
> <a class="moz-txt-link-rfc2396E" 
> href="mailto:[email protected]";>&lt;[email protected]&gt;</a> 
> wrote:
> </pre>
>       <blockquote type="cite">
>         <pre wrap="">Also I think, the “Description” part: “Knowledge of 
> major Linux Operating
> Systems..” should be changed to “ Knowledge of major Linux distributions...”
> 
>   I think you're right here.  A skill Linux Essentials candidates should
> have is the capability to discern between an OS and a distribution (with all
> the overlapping and grey areas between them).
> </pre>
>       </blockquote>
>       <pre wrap="">
> Guys, check out:
> 
>     <a class="moz-txt-link-freetext" 
> href="http://wiki.lpi.org/wiki/LinuxEssentials#1.2.2_Choosing_an_Operating_System";>http://wiki.lpi.org/wiki/LinuxEssentials#1.2.2_Choosing_an_Operating_System</a></pre>
>     </blockquote>
>     <br>
>       Right, however the point is whether the section name should be
>     changed into "Knowledge of major Linux distributions".<br>
>     <br>
>     <blockquote
> cite="mid:cafkqhhmhfdqf53yy_touiicy-vkbh7qnfrg9kbm-+oe36v6...@mail.gmail.com"
>       type="cite">
>       <pre wrap="">
> It's meant as a choosing between different OSes and distros (maybe
> someone can justify a MS solution, too).
> </pre>
>     </blockquote>
>     <br>
>       I wonder if and why a prospective Linux Essentials certified
>     person would be required to know the differences between a generic
>     Linux distribution, Windows and MacOS X.  I've never had any
>     experience of MacOS X, to say one.<br>
>     <br>
>     <blockquote
> cite="mid:cafkqhhmhfdqf53yy_touiicy-vkbh7qnfrg9kbm-+oe36v6...@mail.gmail.com"
>       type="cite">
>       <blockquote type="cite">
>         <pre wrap="">Topic 1.3.4
> 
> xargs, sort &amp; cut are some advanced topics mainly used in scripts, I think
> they do not fill in Essential Skills of Linux, they are also covered in
> LPIC-1. I think we should add the “locate” command here instead.
> </pre>
>       </blockquote>
>       <pre wrap="">
> I added 'locate' to help/man section.  nothing on how the locate db
> gets updated, though.</pre>
>     </blockquote>
>     <br>
>       I wouldn't add <font face="Courier New, Courier, 
> monospace">updatedb</font>
>     to the list, however the candidate should be aware that <font
>       face="monospace">locate</font> gets it's data out of a database. 
>     Knowing that this database is updated by a command called <font
>       face="Courier New, Courier, monospace">updatedb</font> wouldn't be
>     too much, I opine.<br>
>     <br>
>     <blockquote
> cite="mid:cafkqhhmhfdqf53yy_touiicy-vkbh7qnfrg9kbm-+oe36v6...@mail.gmail.com"
>       type="cite">
>       <blockquote type="cite">
>         <pre wrap="">  I do use sort and cut routinely on the command line, 
> and sometimes xargs
> as well, but I do agree the later is not a trivial command and probably not
> very useful to a beginner.
> </pre>
>       </blockquote>
>       <pre wrap="">
> Guys, I doubt that the questions would go beyond the level of:
> 
>     find | xargs grep | cut
> 
> I'd rather people learn that than:
> 
>     find -exec grep | cut
> 
> Besides, after the first combo, they should be ready for litany of
> humdrum commands that they'll discover.
> </pre>
>     </blockquote>
>     <br>
>       All right, I agree.<br>
>     <br>
>     <blockquote
> cite="mid:cafkqhhmhfdqf53yy_touiicy-vkbh7qnfrg9kbm-+oe36v6...@mail.gmail.com"
>       type="cite">
>       <blockquote type="cite">
>         <pre wrap="">Topic 1.5.4
> 
> I think “Hidden files” term should be changed to “doted files” or “non
> displayed” files.
> 
>   I wonder what they are called in the POSIX documents that describe their
> behaviour.  Does anyone know?  I'd take that to be their official name.
> </pre>
>       </blockquote>
>       <pre wrap="">
> They deftly avoid calling them anything, I think:
> </pre>
>     </blockquote>
>     <br>
>       How cowardly!  :-)<br>
>     <br>
>     <br>
>       Bye,<br>
>     <br>
>     <br>
>     -- <br>
>     Alessandro Selli, <a class="moz-txt-link-freetext" 
> href="http://alessandro.route-add.net";>http://alessandro.route-add.net</a><br>
>     VOIP: <a class="moz-txt-link-abbreviated" 
> href="mailto:sip:[email protected]";>sip:[email protected]</a><br>
>     Chiave PGP/GPG Key: EC885A8B<br>
>   </body>
> </html>

That's pretty hard to read.

Could you either send plain text email, or at the very least send both
plain text and html?  All mail clients do have that option (although at
least some versions of firebird stupidly defaults to html only).

-- 
Len Sorensen
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev

Reply via email to