Re: console mode not allowing login
Hi Todd, On 21 October 2016 at 12:58, Todd C. Millerwrote: > It sounds like you need to enable getty on the serial port. To > login on the serial console you should have a line like the following > in /etc/ttys: > > tty00 "/usr/libexec/getty std.9600" vt220 on secure > That did it! Thanks so much for the simple fix. > - todd -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: console mode not allowing login
It sounds like you need to enable getty on the serial port. To login on the serial console you should have a line like the following in /etc/ttys: tty00 "/usr/libexec/getty std.9600" vt220 on secure - todd
console mode not allowing login
Hi All, After my machine is completed booting up and ready for login, I can't see anymore text in the console. Which also means I can't login to the machine via console. # cat /etc/boot.conf set tty com0 set timeout 60 I'm connecting to the openbsd machine via freebsd with this command: cu -l /dev/cuaU0 -9600 DHCPREQUEST on bge0 to 255.255.255.255 DHCPACK from 192.168.0.1 (6c:b0:ce:59:cf:bb) bound to 192.168.0.20 -- renewal in 1800 seconds. reordering libraries: done. starting early daemons: syslogd pflogd ntpd. starting RPC daemons:. savecore: no core dump acpidump: RSDT entry 6 is corrupt checking quotas: done. clearing /tmp kern.securelevel: 0 -> 1 creating runtime link editor directory cache. preserving editor files. starting network daemons: sshd smtpd sndiod. starting local daemons: cron. Fri Oct 21 12:45:19 PDT 2016 The date is the last line printed. Any suggestions? -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info