-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > guest writes to /dev/ttyS0 > vmware connects its virtual S0 to the host's ttyFakeS0 > minicom on the host to ttyFakeS0 > or even > vmware S0 to host's ttyS0 > other remote machine do minicom to ttyS0 > > The reason for FakeS0 is that vmware does not know about ptys, > unfortunately. Yes, VMWare doesn't support serial port using host's ttys any more. My idea is: [host - application] <- read/write -> [virtual serial port /dev/ttyFakeS0] <- read/write over virtual null-modem serial cable -> [host - real serial port /dev/ttyS0] <- read/write -> [VMWare - application] But today I've just bought an USB-to-Serial converter and made for myself a null-modem serial cable. I use this null-modem cable to connect /dev/ttyS0 (native serial port) to /dev/tts/USB0 (USB-based serial port). My VMWare now can use one of those devices and the host use another one. Now above figure can be re-drawn like this: [host - application] <- read/write -> [/dev/tts/USB0] <- read/write over physical null-modem cable -> [/dev/ttyS0] <- read/write -> [VMWare - application] Anyway, later I'll try to write a device drivers act as virtual serial ports and virtual null-modem cables. Best regards, Mikado. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEJsrfNWc9T2Wr2JcRAl05AJ9Ee8zqagf0yjDk71mFAxwSskFltQCg0aM8 mELZ8uxHPaSYzLiZLM7Cxy4= =zI/+ -----END PGP SIGNATURE----- - : send the line "unsubscribe linux-c-programming" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
