chuckula wrote:If your coding classes are relying heavily on Java then using Linux should be just as easy as Windows to give you some practical experience with Linux prior to your Linux course.
That's what I'm hoping for. I have to turn in zipped-up NetBeans projects for Java and use some sort of organized code editor for the web design course (right now I'm using Brackets and I'm open to suggestions on something better - VS Code is also available), and so I figure why not, right?
chuckula wrote:Based on the course description blurb I would spend a little time on these areas:
Practice using Bash & its associated utilities to do things like file management, copying/moving/deleting, and changing file permissions with "chmod" and optionally some of the more sophisticated ACL settings. [Edit: oh yeah, and using pipes (|) to chain commands together and shell input/output redirection (< >) to direct input & output data] On top of that, make sure to gain at least a passing familiarity with a bunch of favorite command line utilities including (but not limited to) find, grep, xargs, rsync, ssh/scp, and maybe even awk/sed.
The blurb further mentions shell programming: That will be a natural extension of using the standard command line and the utilities, so if you get comfortable using the command line, the shell programming won't be much of a leap (and will in many ways be a step backwards from a fully-formed OO language like java).
just brew it! wrote:f you're comfortable with the command line in macOS you're already (mostly) there in terms of Linux CLI. It'll all seem really familiar, as both use bash as their default shell. There are some differences in the CLI utilities, obviously; but things should be familiar enough that you won't feel lost.
Shell programming likely means bash scripting. Have you done any of that on macOS?
Just based on the description, you guys probably nailed it with what I need to figure out for class. I've got plenty of experience running Bash scripts, but they're just parts of command-line tools that go with building Genero packages. Not so much on the building side, though. I've also done a bit of fiddling with apt-get for installing/updating packages.
This course isn't targeted at administration. There are separate courses for Linux administration targeted at the people on an IT administration path, so I'm hoping that doing what I need to do in a VM and without multiple machines will be sufficient.
chuckula wrote:As for text editors... VIM UP HOMIE!
just brew it! wrote:Not sure whether they mean GUI text editors or terminal-mode text editors. GUI editors should not present any major surprises. Lowest common denominators for terminal-mode editors are nano and vi/vim; inflicting emacs on Linux n00bs would be pretty mean, I hope (and assume) they wouldn't do that.
20-some years ago I built a really basic web page using nothing but a telnet app for Windows and pico. I've used nano quite a bit on macOS and it seems almost identical.
chuckula wrote:
just brew it! wrote:You may also find it helpful to install the dwww package. This makes searchable, hyperlinked man pages for packages currently installed on your system available in your web browser at localhost/dwww.
This all looks very helpful, thank you both!
Addendum from SSK -->
ALWAYS PRONOUNCE IT LINE-UHCKS TO SHOW HOW l33T YOU ARE!
WAIT YOU MEAN IT'S NOT PRONOUNCED LIKE THAT????!!!
BTW, I don't know how Glorious does it when it comes to replying to threads with posts in this format. It took forever to format this thing just right.