On Mon, Aug 5, 2019 at 12:37 PM Marco Verleun <[email protected]> wrote:
> Given the fact that they are junior I think we expect to much from them if > they have to recover systems from very complex boot problems. > Forget I said 'emergency,' use 'minimal.' It's funny that people say Red Hat is 'bloat' because my RHEL systems are pretty minimal. Please understand my point, and don't take issue with the one I didn't intend ... ;) Vi is quite likely your best friend at those moments, but wouldn’t a junior > admin consult a more experienced colleague? > Yes. And I'm on the other side of the phone, but haven't remoted in yet because my computer is packed up or in another location, but have to because he cannot edit a text file. This is my point ... everything stops because a sysadmin doesn't know Vi. Not that he doesn't know what he is doing, but he cannot edit a text file. That's the problem. What we're saying with LPIC-1 is that Vi isn't important to know. I take issue with that, because it's one of the top 3 PITA I have to deal with. ;) The 'rite of passage' is the symptom because anyone who has dealt with thousands of sysadmins over the decades and dreaded those who don't know Vi for a reason. > As an organization you probable contact the most experienced engineer if > there are problems of this magnitude. And if the data is not important it’s > probably quicker to deploy a new instance. > Agreed ... except it's one of the few system with the persistent database stores, and not completely stateless. Again, are we seriously saying junior sysadmins don't need to know Vi? That it's one of the lowest tools in their bag? That editing text files in a minimal mode is unnecessary? That's the argument. If a supermajority agree that Vi only needs 1 (or even 0) questions, then I'll comply. But I haven't heard a good argument yet other than, "We should test other stuff." And in counter to that, I say ... "Yes, let's test other stuff ... and get rid of 'interactive break-fix' then." - bjs
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
