News for hackers. Stuff that matters.
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by marcosdumay on Tuesday July 04, 2017 @10:19PM (#14699597)
There's no problem with exposing a rlogin or telnet server over an RS232 interface, or a USB port. There is no reason why clients for using those should be hard to install.
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by SwellJoe on Wednesday July 05, 2017 @12:32AM (#14699996)
I'm not saying they should be hard to install; I'm saying they shouldn't be in the core installation.

Also, it's been ~15 years since I used an RS232 interface (for serial interfaces to servers/routers); it's been almost that long since you could buy a system with an RS232 interface at all (aside from maybe embedded systems that haven't been updated in years). And, I've never used a USB port for a terminal connection; I guess it is possible but is it ever done?

But, really, why have something that's so out of the ordinary in a default installation?

Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by biktor_gj on Wednesday July 05, 2017 @01:19AM (#14700106)
All Cisco, HP ProCurve etc. still use serial (they tend to have serial over USB these days) interface for configuration. You can connect via SSH / telnet, but to configure the management interface you first need to connect to that serial port and give it an IP address...
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by mmarx on Wednesday July 05, 2017 @02:18AM (#14700285)
HP/HPE/Aruba switches have shipped with DHCP enabled in the factory config for at least the last seven years, so you very much don't need a serial console to configure those. The Cisco WLAN controller I came across last week, however, wouldn't do anything until you plugged in a serial cable.
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by tsomctl on Wednesday July 05, 2017 @01:15AM (#14700097)
There's this company called Cisco that makes routers with serial ports.
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by SwellJoe on Wednesday July 05, 2017 @01:32AM (#14700136)
Never heard of'em.
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by wang_li on Wednesday July 05, 2017 @01:01PM (#14704112)
>it's been almost that long since you could buy a system with an RS232 interface at all (aside from maybe embedded systems that haven't been updated in years).

I don't know what kind of computers you are buying, but I've yet to see a retail, server-class, motherboard without a 9-pin serial port in the back.

Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by SwellJoe on Wednesday July 05, 2017 @04:34PM (#14705879)
My colo has a crash cart with keyboard/video/mouse. I don't know what I'd get out of using the serial port for anything. I think only one of my servers actually has an RS232 port, but I haven't actually looked at the hardware in over a year.

But, maybe most servers do still have RS232.

Nonetheless, rlogin/rcp/etc. are not useful tools for a serial console. I don't even know how you'd use them in such a circumstance. Are you using rlogin/rsh/rcp/rwhatever over RS232 to your servers? How? Why?

Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by wang_li on Thursday July 06, 2017 @07:33PM (#14714833)
Well, in the past we'd use multi-port serial terminal servers and all the hosts had their serial ports as their console hardwired to the terminal server. These days the servers all include IPMI with KVM redirection. But the serial ports are still there.

As far as using any TCP/IP based protocols over the serial port, I suppose you could do something silly with SLIP or PPP, but honestly I don't know why. The whole point of the serial port is that it's damned simple and firmware can easily initialize it and use it for IO extremely early in the boot process.

Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by yellowapple on Wednesday July 05, 2017 @11:09AM (#14702976)
I personally use RS232 quite regularly in order to hook into the console ports on Cisco hardware and some servers. Really handy if, say, SSH is disabled on a router and you need to get in to enable it.
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by vbernat on Wednesday July 05, 2017 @02:08AM (#14700250)
What does it mean to expose a telnet server on an RS232 interface? Are you running SLIRP on top of it? I think you mean exposing a login prompt (through getty or similar). No telnet server is needed.
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by sigjuice on Wednesday July 05, 2017 @02:06AM (#14700245)
How does telnet/rlogin over RS232 work? Do you use SLIP or PPP or is there some other mechanism?
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by SwellJoe on Wednesday July 05, 2017 @02:35AM (#14700330)
That's also a good question. I always used something like minicom or similar to connect when I had to do that sort of nonsense on a regular basis. I don't know how one would use telnet or rlogin to talk to a, say, Cisco, router over RS232. You'd have to jump through some serious hoops, I would think, to use rlogin or telnet.

It's been so long since I've worked with that kind of thing I didn't really even think through what an odd comment it is to suggest that serial consoles on routers are a good reason to keep rsh around in a default FreeBSD install. It makes no sense at all. I'm beginning to think nerds just like to argue.

Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by sigjuice on Wednesday July 05, 2017 @02:50AM (#14700370)
Agreed. Minicom is a reasonable choice. These days I use screen /dev/ttyS0
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by kstrauser on Wednesday July 05, 2017 @12:56PM (#14704065)
FreeBSD still ships with the "tip" command for that: https://www.freebsd.org/cgi/man.cgi?tip(1)