Dear all, Thanks for all of your comments. Seems like it's time to wrap things up. I'll send several emails today to address all your comments grouped by topics -- sorry for not following up individually, there are so many thoughts that it would become quite spammy.
Let's get started with the coverage of various tools. Most of these comments relate to objective 1.2, 'Major Open Source Applications'. We should keep in mind that this objective is mostly an awareness objective. We do not cover any of the applications in detail, we just expect the candidates to know they exist. That's why we have a lot of applications in here, to ensure candidates understand the variety of the open source ecosystem. This also gives us more flexibility regarding the amount of tools. Regarding the tools at awareness level: * I've added Chromium, Codium, Forgejo and PostgreSQL. I've kept the respective vendor names like Chrome and VS Code because these are the names candidates will more likely hear elsewhere. For the same reason, MySQL is still in the draft. I wouldn't add any project governance aspects to Linux Essentials. * GPG was added. * Regarding R: The main point of having R in this awareness objective is knowing "If I need advanced statistics, R is the open source tool to take a closer look at". We wouldn't ask for anything more specific. R is included more to address the variety of the open source ecosystem and to introduce the name to candidates who might take Linux Essentials a side course while studying a subject that leverages statistics. * nano / vi: We do not cover the actual use of any editor. I'd assume candidates will likely get started with nano, so they should definitely know it exists. They will, however, also hear people talking about vi, so we should require them to know what it is, too. But both are on awareness level, so no detailed knowledge like exiting the editor is required. * apt-get / apt: A major difference is that the CLI of apt-get is stable, that's why it's commonly used in Dockerfiles/Containerfiles. There might be candidates who use Linux Essentials to complement their development / cloud native skills, I'd like to keep both apt and apt-get. * Ansible was removed from 1.4, "Awareness of configuration management tools" was kept as a key knowledge area. * And (I know, it's not a tool), RISC-V was not added to the draft yet since it seems to be rarely used. Feel free to follow up on this. Regarding the tools we cover in more detail: * rm / rmdir: I would prefer to keep both tools, since they are commonly taught and I agree that it might be a good idea to not encourage Linux beginners to use rm -r too often. * sort / uniq: Just because sort -u exists, I think uniq doesn't harm and can actually be quite handy in a training where the concept of pipelines is taught (one tool per purpose). * zip / unzip: I would keep zip and unzip, since Linux Essentials candidates might come from the Windows world where they are used to the ZIP format and might find it helpful to both transfer files and leverage the similarities of the various compression tools. * dig / host: Really understanding the output of dig requires detailed knowledge of the DNS protocol which is beyond the scope of Linux Essentials. Therefore I'd prefer to stick with host, which is good enough for resolving the records we cover in this exam without additional distraction or the need to go into DNS details -- DNS is one aspect in a single objective, knowing that it serves to resolve names and addresses should be enough. Also retrieving all "relevant" records in one command is easier than having to query e.g. A and AAAA specifically. * locate / find : Since it seems like some of you miss a way of finding files, I've added 'Searching for files based on file names' and the command 'find' to 2.3. I think we can justify using find in this very limited scope and thereby avoid covering updatedb and the reasons why only specific paths are included. * Bash builtin help: I am a little on the fence here. For (almost) all commands we have in the exam, a man page and/or helpful -h output exists, and we're not going into any Bash specifics in Linux Essentials. Since there won't be a lot to look up here during the exam preparation, I'd prefer to leave it out. But again, feel free to follow up :) Stay tuned for some more emails, and, as always, please follow up if you'd like to add any thoughts. Fabian On Mon, Jan 5, 2026 at 9:06 PM Fabian Thorns <[email protected]> wrote: > Hi there, > > I hope you've all had a good start into the new year, despite the world > getting more mad every day. We'll focus on the sane stuff and start working > on an update for Linux Essentials in 2026. I've created a draft for the new > objectives, which I'd like to share with you today. > > The current version of the draft is available in the LPI wiki: > > https://wiki.lpi.org/wiki/Linux_Essentials_Objectives_V2.0 > > There is also diff between the current version 1.6 and the initial draft > for version 2.0: > > > https://wiki.lpi.org/w/index.php?title=Linux_Essentials_Objectives_V2.0&diff=5878&oldid=5877 > > A lot of the changes are improvements in the descriptions and > objective/topic names. The overall outline and weights hasn't changed, but > some objectives were restructured and received updates, i.e. regarding > Linux distributions and using Linux in the cloud. I've also added SSH and > systemctl and journalctl, while syslog and net-utils are gone now. > > I'd appreciate you taking a look at the proposed changes, i.e. if you're > teaching Linux Essentials, but, of course, everyone is invited to review > the draft. If you have any additional suggestions or comments, please feel > follow up on the list or privately. > > Looking forward to your thoughts, > > Fabian > > -- > Fabian Thorns <[email protected]> GPG: F1426B12 > Director of Product Development, Linux Professional Institute > -- Fabian Thorns <[email protected]> GPG: F1426B12 Director of Product Development, Linux Professional Institute
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
