This is a long response but I hope many will read through it.  There's a few
calls for opinions in it.

Also, Reinier, these are great comments. Thanks a lot.


Reinier Kleipool <[EMAIL PROTECTED]> writes:
> I am in favour of splitting topic 107 into Admin stuff / Network stuff. The
> SSH topic (Now 109.3) then can become a part of the Network stuff.

I've made the split (but left the SSH as part of Security; the SSH section
will be bigger in LPIC-2) and called the 'network stuff' Essential System
Services.

Just so everyone knows, I'm trying to keep the 'hardcore' admin stuff out of
LPIC-1 in favour of LPIC-2.  One major reason for this, is that I would like
to see LPIC-1 usable as a branch point for an 'admin track' plus a developer
one (yes, IMO, developers need a good grounding of their OS), a DBA track,
etc.


> Maybe the X stuff can be re-organized into SETUP: (X server / DM setup / Font
> server setup-and-use) and X SECURITY: (Listen to port 6000, xhost +, ssh -X)
> etc...

I expect that the X portion will be shrinking with this rewrite.  With x.org
and distros making configuration a lot easier than in the 'old days', plus now
that they don't like on a TCP port by default any more, it's becoming less of
an issue (and a bit of a lost art).


> Add something to topic 109 about secure passwords: cracklib, password aging,
> The concept that via PAM you could use other methods. But not HOW to do this:
> Should be in LPIC 2 by extending 210.3)

Password aging is part of 107.1 but I was kind of hoping to keep the PAM and
cracklib type topics to LPIC-2.  If enough people disagree (and you'll have
to speak up for me to know that you disagree ;)), I'll put it in.

I'm also a little hesitant to 'mention' a topic on LPIC-1 that is covered in
depth in LPIC-2.  It's lead to a lot of confusion on how much of the topic to
put into LPIC-1 courseware with the result usually being too much information
for the student (Reinier, wasn't that your comment in Utrecht?).  Again, I'll
bow to pressure if people think I'm offbase.


> * 101.1 Determine and Configure Hardware Settings*
> 
> Should this topic not include a conceptual knowledge of sysfs -> udev -> hald
> -> dbus. Not test all low level configs that can be made here. But an
> understanding how modules get loaded, device files are created and the GUI get
> a signal to display extra desktop icons? At least the concept of it all.

I agree and it was hinted at but I've put these in explicitly.


> * 102.1 Design hard disk layout*
> 
> There should be a topic about LVM. Most distributions propose LVM in the
> default install. Myself I have not installed a non-lvm system in the last 5
> years....
> LVM concepts: VolumeGroup -> LogicalVolume.
> Change size of an VG and an LV.
> Extend a file system inside an LV.

I was going to leave this (and RAID) as a LPIC-2 topic.  Again, to try and
keep the more 'admin' stuff out of LPIC-1 and into LPIC-2.


> Another topic to add:
> When to choose for 7+ partition system and a single partition (Desktop
> v.s. Server setup). Concept of: Flexibility vs easy to maintain.

We had questions like these on the existing exams and they cause no end of
complaints.  I dropped this sort of wording to get away from the more
'subjective' topics.


> * 102.3 Make and install programs from source*
> 
> Drop this topic. Should this whole topic be in the LPIC 1 exam at all. Working
> with Linux today can be done very professionally without fiddeling with source
> code. We actually warn students *NOT* to introduce source code that bypasses
> the package system in our courses!
> I propose to have a LPIC 2 exam topic about generating (rpm or deb)
> packages from source. Automatically you test the students ability to
> perform the configure / make / install cycle. Ordinary Linux users should
> not play with source code. This is something that should be left to
> packagers working with distributors or senior administrators within an
> organization. Clearly all LPIC 2 stuff....

This isn't a tough sell on me.  I have already 'dumbed' it down (the original
objectives included compiling SRPMs and src debian packages plus editting
Make files, etc) but would feel better about dropping it altogether and
putting it in LPIC-2.

Any naysayers?

Also, what would you suggest about the 102.4 objective, 'managing shared
libraries' is pretty much handled by packages, too.


> * 104.3 Control mounting and un-mounting file systems*
> 
> See earlier remark: File system can get mounted by GUI software after a
> signal. The /media directory.

I've added /media to the list of terms to make it official.


> * 104.5 Manage file permissions and ownership*
> 
> Drop the chattr requirement it's level 200.

Agreed.


> * 106.1 Install and Configure X11*
> 
> Drop xvidtune, it is very badly supported by most distributions. Most
> distributors supply other tools. Using xvidtune data can cause instability in
> the system...

Dropped.


> Add Conceptual functions of: Display Manager (Login screen), Session-manager
> (Environment preparation, kind of .profile), Window manager (Window
> decoration, movement etc..) and D-BUS (Signal and event software bus. No
> details please!)
> Add: Customizing the GUI: adding panels, Launchers. Concept of the .desktop
> file etc...

The *dm are covered in the next objective, session-managers seem to be one
offs for each wm and dbus is going to be covered in the 101.1 and the
mounting file systems objective.  And I was hoping to skip over many GUI
topics like the panels and launchers that you mentioned.  Unless people
pressure me on these ones...


> Maybe Add: Xhost security: xhost +myfriend. (Absolutly drop x-mit-cookie! 
> No-one uses it).

It's implied by the 'xhost' term in the list.  Is this not explicit enough?


> Maybe Add: X font server: Concept of... It's use to download proprietary fonts
> from other *NIX systems to get nice display output.


> Maybe Add: X forwarding using ssh -X.

Was going to leave this for the SSH section.  I'll add it there explicitly,
though.


> Maybe: Split topic into SETUP and SECURIY parts.

Does anyone else feel this way?  I am expecting X not to be too large of a
component to the new LPIC-1 exams and splitting them could cause their
relative weights to get them dropped (or close to it) after the JTA survey.


> * 106.2 Setup a display manager*
> 
> Add Understanding that the X server by default does not listen to port
> 6000. You have to configure *DM for that to happen! Tools: gdm-setup.


> * 106.3 Accessibility*
> 
> YES! this a a new topic that really deserves some attention!

Agreed.  I know that this is dragging a lot of people into areas that they
don't have to deal with often (or ever) so this objective will be starting at
an 'awareness' of the technologies level.  Maybe to grow from that when we
reassess the objectives in 2010.


> * 107.2 Tune the user environment and system environment variables*
> 
> This topic is more of the same asĀ  "105.1 Customize and use the shell
> environment" Merge the two.
> Maybe Add: Customizing a GUI session: Where to put GUI environment changes:
> .xsession.

Merged.  but moved /etc/skel to 107.1 (the managing users objective).


> * 107.4 Localisation and Internationalisation (L10N and I18N)*
> 
> Yes I am in favour of such an item. But do not delve too deep into the
> background of the whole NLS system. A conceptual knowledge of the LANG
> variable, and the existence of message catalogs should suffice. Drop many
> of the files and tools. Do leave the timezone localization in there. (I
> have no idea what you are testing with hwclock... please elaborate or move
> it to 107.5 Maintain system time)

Agreed.  This was a brain dump from one of the guys on the list (I think
Bruno).  I've trimmed it and dropped the hwclock (it's already in 107.5).

Let me know what you think.  I dropped the ones around the developer side and
the compilation of tz info and left it to reporting and conversion tools and
ideas.


> * 107.6 System logging*
> 
> This topic is in bad need for *ELABORATION* There is now a phletora of syslog
> implementations. Which one are we actually testing? Maybe leave it a the
> conceptual level plus understanding of several implementations but do not test
> [old|new]-sylog-something.conf actual config file questions. Concepts:
> Message facility and Message severity.
> Syslog destinations: File/ terminal / application / other syslog server.

I've made LPIC-1 just standard syslog, its facilities, priorities and
actions.


> Syslog via UDP: Logging non Linux data (Other Unix / Network router / external
> Firewall etc...)
> Messages are filtered by the syslogger config file.
> Syslog can be analysed with LogWatch.

This plus syslog-ng will be at the LPIC-2 level.


> * 107.7 Perform basic configuration of Mail Tranfer Agent (MTA)*
> 
> Make VERY CLEAR that this topic only touches the basics: No delving into
> sendmail.mc / sendmail.cf.
> Maybe add: Understand that most distributions ship with local mail sending
> ONLY. No relay from the LAN... (Not how to disable this is LPIC 2 stuff, see
> above about sendmail.mc)
> Maybe Add: Creating one or more email addresses: virtuserfile and
> local-host-names.

I've changed it to the basics (aliases and forwarding) plus added 'knowledge
of commonly available MTA programs (postfix, sendmail, qmail, exim) (no
configuration)'.


> * 108.2 Basic Network Configuration*
> 
> Maybe NetworkManager should be tested as well.

Nah, that'd be too easy on them :)


> * 109.1 Perform security administration tasks*
> 
> Drop chattr.
> Add: chage, 

Done.

> Add: concept of cracklib. Know about secure passwords / personal
> accounts / no root access

I'm saving the cracklib stuff for LPIC-2 and the personal accounts is covered
elsewhere.  As for no root access, I'm saving that for the SSH server side
and other topics in LPIC-2 (and sudo can cover it a little, too).


> Elaborate more on what's expected for the sudo topic. This can cover a lot,
> but what is tested?

I've added:

    * Basic sudo configuration and usage.

and /etc/sudoers to the list.

Read that a simple aliases and user specifications, using sudo on the
commandline and 'what is this sudo thing anyway?' coverage.

-- 
g. matthew rice <[EMAIL PROTECTED]>      starnix care, toronto, ontario, ca
phone: 647.722.5301 x242                                  gpg id: EF9AAD20
http://www.starnix.com              professional linux services & products
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev

Reply via email to