And thanks op for reminding me of this :)
Rsh: Ruby SHell
21–30 of 41 posts
Re: Rsh: Ruby SHell
#22Need windows version. Windows Terminal is the worst thing in the world.
WSL and you just can completely avoid Windows Terminal if you work on Windows but not with Windows. I.e I do devops, linux development in my Windows Box running an openSUSE box in WSL. It integrates pretty well with visual code for instance.
Re: Rsh: Ruby SHell
#23(slight ot, sorry!) This brings back great memories of one of the best assignment from my college time: We had an "Agile web development" course (~2007) with a precursory Ruby 101 workshop as well as a pre-course assignment to "create a shell in Ruby". It was such a joy to hack on this and learn that way. It was clearly wayyy too vast of a task to ever _complete_ it, but I learned so much Ruby there and couldn't stop…
Re: Rsh: Ruby SHell
#24Re: Rsh: Ruby SHell
#25Re: Rsh: Ruby SHell
#26Re: Rsh: Ruby SHell
#27How fast(or slow...) is the startup time?
Re: Rsh: Ruby SHell
#28Earlier quoted context omitted.
WSL and you just can completely avoid Windows Terminal if you work on Windows but not with Windows. I.e I do devops, linux development in my Windows Box running an openSUSE box in WSL. It integrates pretty well with visual code for instance.
Sadly, to use WSL effectively, you need to configure high enough Disk and Memory, the issue is WSL doesn't know how to clean up deleted volume.
Re: Rsh: Ruby SHell
#29Not great naming imho, this has been around for 40 years.. https://en.wikipedia.org/wiki/Remote_Shell
I'm imagining some auditor seeing an "rsh" binary on a Linux system and dinging the system on it, and weeks of back and forth emails and meetings required to determine that, no, in fact, this is not remote shell, it's Ruby shell, and it's actually not a valid audit finding.
And, of course, that's completely omitting the binary collision issue because frankly anybody with "old" rsh installed deserves whatever pain they get.