Free Linux Foundation Online Class
-
I've only ever had to use vi a few times, but it's been often enough that I keep a vi reference on my Nexus tablet at all times. This is neat that they are offering some free training. Kinda keeps the spirit of Open Source / GNU alive.
-
@scottalanmiller said:
@PSX_Defector said:
@scottalanmiller said:
@PSX_Defector said:
Nifty. Wonder how deep they are going and how much command line zealotry they will be pushing. Yeah yeah, everything is command driven, but for lots of us, we don't need to learn the subtle nuances of vi when pico will do the job just as well. Most of the CLI zealots demand you learn vi and vi only.
For good reason. I've seen knowing vi mean the difference between being the guy fixes the servers or the guy who fetches his coffee.
Ultimately it's a text editor. There is nothing inherently different between vi and pico or any of the hundreds of text editors out there. There isn't anything compelling to use it other than zealotry.
You don't see the same kind of craziness when it comes to Notepad and Wordpad in Windows. Wordpad is a much more feature rich and since Windows 7 more in line with Office with the ribbon and such. But you don't see Windows zealots screaming about how you are not really using Windows if you don't use Notepad and Notepad only.
There is a huge difference. That difference is: included by default. vi is the only option on every enterprise UNIX out of the box. It's only about operational mindset, not zealotry. For engineers it doesn't matter what you learn because you add what you want. For admins, you use what you have and the most reliable answer is vi.
Which leads us back to zealotry. Just because Notepad is the default text editor in Windows doesn't make it the best, nor does it make it bad. But dare say vi sucks, you get the herpaderp brigade out in force thumping an O'Reiley vi book in your face. Sure, it's required for POSIX compliance, but it doesn't mean it's good.
If I have to use vi, I do. But I generally load whatever I feel like, or use one of the alternate ones that are much more intuitive, pico being my usual choice. I'm sure if I spent nothing but weeks in training ON A TEXT EDITOR maybe I would be more proficient. But once again, it's a [moderated] text editor. It shouldn't require a guide, nor doing things in such an archaic way.
-
Learning to use what is available isn't zealotry towards vi. We all hate vi. It's zealotry to reliable support perhaps.
-
@scottalanmiller said:
Learning to use what is available isn't zealotry towards vi. We all want to :q vi. It's zealotry to reliable support perhaps.
FTFY
-
Lol. What's funny is in the enterprise space I literally see nothing but vi. From developers to tech managers to the admins and engineers. I never thought that it would be so ubiquitous.
-
That's a function of it being a part of POSIX compliance. It's included in Cygwin, BSD, Linux, etc. etc. With our enterprise, we have multiple text editors installed by default from our implementation team.
-
@scottalanmiller Thanks for posting this.
-
@PSX_Defector said:
That's a function of it being a part of POSIX compliance. It's included in Cygwin, BSD, Linux, etc. etc. With our enterprise, we have multiple text editors installed by default from our implementation team.
Sure. Most shops will. It's when you switch shops or work on customer gear or something that it matters. For me the big moment was when production went down at IBM Endicott and I was the only person in the entire facility who could work on the vi-only Solaris systems.
-
vi is definitely a pain but it's actually what I'm used to. I haven't done much real text editing via CLI in so long that since I've only used vi lately and nano once I'm just more familiar with vi. I would say it's beneficial to know vi and at least one or two others so you can be flexible. But vi is a crucial one to know.
-
After all these years, I like vi now. 20 years of vi this year.
-
@scottalanmiller It's not great but honestly I do very little with it.
vi file
I
make changes
Esc
:wq!Done! I'm not doing anything crazy. Editing config files in basic ways. For me it works.
-
Find a vi cheat sheet. That's all that you really need. It has a lot of power.
-
got me one of those
-
@art_of_shred said:
got me one of those
The biggest things are knowing how to exit and save. vi used to be far worse. Now we have cursor key support and delete. So not insane like it used to be.
-
Erg, looks like the class starts " 3rd Quarter 2014"—
- https://www.edx.org/course/linuxfoundationx/linuxfoundationx-lfs101x-introduction-1621
- Also, https://www.edx.org/school/linuxfoundationx
- Cool they have an "audit" option for those unable to fully commit, but want exposure to the material
-
@RoguePacket said:
Erg, looks like the class starts " 3rd Quarter 2014"—
Yeah, just an early announcement at this point.
