> not even Unix sysadmins still wear bell-bottom corduroy trousers and platform soles.
Hiking boots, since you never know when a mountain will appear in the middle of the computer room. A lot of docker images don't contain 'vi'. You can load them with apt and yum after an update or two but it's a real PITA when all you want to do is make a small change to /etc/resolv.conf or something. On Tue, Aug 6, 2019 at 5:13 PM Anselm Lingnau <[email protected]> wrote: > Bryan J Smith wrote: > > > And now you switch to my way of thinking. ;) > > > > I.e., you have to conceed Vi != sendmail, and that Vi is still the > > _default_, if any. ;) > > > > That if we're talking about reducing/removing Vi, we're really talking > > about removing 'interactive' altogether? If so, agreed! ;) > > Nope. I don't have a big issue with vi coverage at weight 1, simply > because > basic vi is quite easy to learn. I think the current weight-3 objective is > a > waste of two perfectly good weight points. > > What I can't stand is people claiming that vi is the One True Editor and > that > you can't be a True Sysadmin™ unless you use vi. Vi is a living fossil > that by > historical accident is left over from the 1970s. It is cool but only in > the > sense that a coelacanth is cool; you can't help but be impressed that it > managed to stick around as long as it did in a world that changed such a > lot > in the meantime. Other 1970s icons haven't fared nearly as well; not even > Unix > sysadmins still wear bell-bottom corduroy trousers and platform soles. > > As far as “removing 'interactive' altogether” is concerned, I think we > need to > draw a line somewhere. The trend is towards automation and chances are > that in > the future we'll type fewer commands into interactive shells. But the > shell > and the Unix toolkit of commands are going to stick around for a while > (there > will always be scripts or Ansible playbooks). So “removing 'interactive' > altogether” may be easier said than done. I'm all in favour of > acknowledging > the importance of tools like Ansible but perhaps not in LPIC-1. > > > It's not about reducing Vi's importance for 'interactive' so other > > questions can be asked. It's about removing text editing altogether. > > I could live with not covering text editing in LPIC-1 at all. That of > course > wouldn't mean text editing doesn't exist or people shouldn't edit text, > it's > just that (a) text editing on Linux in 2019 doesn't necessarily mean “vi”, > and > (b) we don't examine people on other very basic skills like typing or > using a > mouse either, we just assume that they're proficient enough at these > skills to > do whatever is needed. Adding the use of a text editor to this set of > basic > skills isn't a huge thing, and we can assume that basic exam prep > materials > and classes will still have a thing or two to say about text editing, even > if > it is “run the ‘vimtutor’ command and I'll see you in a quarter of an > hour”. > > > Agreed! Why didn't you just say you agreed with me then? ;) > > Because I really don't. > > Anselm > -- > Anselm Lingnau · [email protected] · https://www.tuxcademy.org > Freie Schulungsmaterialien für Linux und Open-Source-Software > Free Training Materials for Linux and Open-Source Software > > > _______________________________________________ > lpi-examdev mailing list > [email protected] > https://list.lpi.org/mailman/listinfo/lpi-examdev
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
