Estoy leyendo el manual de minicom (man minicom
), encontré este párrafo:
Serial port setup
A - Serial device
/dev/tty1 or /dev/ttyS1 for most people. /dev/cua<n> is still possible under linux, but not recommended any more because these devices are obsolete and
many newly installed systems with kernel 2.2.x or newer don't have them. Use /dev/ttyS<n> instead. You may also have /dev/modem as a symlink to the
real device.
If you have modems connected to two or more serial ports, you may specify all of them here in a list separated by space, comma or semicolon. When Mini‐
com starts, it checks the list until it finds an available modem and uses that one. (However, you can't specify different init strings to them..at
least not yet.)
To use a UNIX socket for communication the device name must be prefixed with "unix#" following by the full path and the filename of the socket. Minicom
will then try to connect to this socket as a client. As long as it cannot connect to the socket it stays 'offline'. As soon as the connection estab‐
lishes, minicom goes 'online'. If the server closes the socket, minicom switches to 'offline' again.
Entonces, creo que el estado en línea/fuera de línea se usa solo con sockets UNIX. Nunca usé esto, pero hice algunas aplicaciones con USB y DB9 y todas funcionaron con el indicador "fuera de línea". Si su comunicación no funciona, verifique que la tasa de baudios y la paridad sean correctas.
Это зависит от того, что вы хотите сделать:
Если вы просто хотите использовать беспроводной адаптер хоста для подключения к сети вместо проводного (ТиранияDefault
)просто:
VMNet Information
на Bridged
Automatic
фактическим адаптером, который вы хотите использовать ИЛИ
Запускайте инструменты взлома из безопасности с вашей виртуальной машины:Вы не можете, потому что: