Andriy
Developer
I don't know. Read tmux docsIt cannot be done with tmux?
I don't know. Read tmux docsIt cannot be done with tmux?
Now that's just paranoia. If you have sensible settings for SSH, you'll be fine. Not to mention that realistically speaking, your VM is most likely not even visible to port scanners on the Internet, and you don't present an attractive target for anyone capable of launching an attack that does any real damage. I have a few devices with SSH access sitting behind a 192.168.1.1/24 network, tell me if you can see them.
Surprisingly, not everyone has the ability to get Internet-legal, routable IPv6 addresses, not without a tunnel to a service provider like Hurricane Electric... I've seen comments on these Forums that some people are 'still stuck with a tunnel provider'.IPv6 nowadays
They look like a hard link
$ ls -i -1 /usr/bin/cu /usr/bin/tip
5032 /usr/bin/cu
5032 /usr/bin/tip
[code]
(I know we’re getting off topic, sorry.) Check out /rescue for the mother of all depends-on/argv[0] examples.They look like a hard link
Code:$ ls -i -1 /usr/bin/cu /usr/bin/tip 5032 /usr/bin/cu 5032 /usr/bin/tip [code]
I am indeed using HE, there is not much problem with that - they even delegate the reverse-DNS to my own nameservers.Surprisingly, not everyone has the ability to get Internet-legal, routable IPv6 addresses, not without a tunnel to a service provider like Hurricane Electric... I've seen comments on these Forums that some people are 'still stuck with a tunnel provider'.
That is everywhere. Businesses are reluctant to go IPv6, for unknown reasons (maybe lack of skill). But if you have a business, you can choose your uplink, and if you are private site, tunnels are not such bad.I'm on US West Coast, and my market still doesn't have a handle on IPv6, in spite of claims that 'IPv6 is supported'. Maybe technically possible, but certainly not routed from private devices yet.
I cannot run tip(1) from ssh, thus it is useless.
For the other part cu(1) does work, but all the shell functionality is totally broken, cannot edit lines (move the cursor) and use TUI or anything.Yes, they are. cu is my favorite, very simple and does not require any configuration file.
And have tried cu(1), and it gives a serial console, but the serial console is broken, cannot use TUI or edit lines (move the cursor).
Just tried minicom, it works but looks like also has the same problems of cu(1), maybe I have no configured any of them well.How about minicom?
I do it fairly often. Not sure why you can't get it to play ball. Any specific error messages?I cannot run tip(1) from ssh, thus it is useless.
This is because serial terminals are more limited as per the standard.For the other part cu(1) does work, but all the shell functionality is totally broken, cannot edit lines (move the cursor) and use TUI or anything.
Probably will work, but with that level of indirection, how many escape sequences will be there?.I do it fairly often. Not sure why you can't get it to play ball. Any specific error messages?
Try ssh -> tmux -> tip.
It is not possible to configure it to speak vt100?.This is because serial terminals are more limited as per the standard.
The tmux escape sequence is quite different so doesn't count. But yep, the i.e ~~. may be more awkward for ssh+tip.Probably will work, but with that level of indirection, how many escape sequences will be there?.
Interesting. What is the TERM env variable at any of these points? (minus grub perhaps).The error message was "missing interactive session".
It is not possible to configure it to speak vt100?.
Also grub does not even respond to the arrow key
First we start withThe tmux escape sequence is quite different so doesn't count. But yep, the i.e ~~. may be more awkward for ssh+tip.
Interesting. What is the TERM env variable at any of these points? (minus grub perhaps).
xterm-256color
at a row session of Konsole, then I enter with ssh to the machine, ssh my-user@my-machine 'echo $TERM'
,and get nothing. And finally when entering in the debian-12-nocloud-amd64.img
with bhyve, I got vt220
.