all appeared to be fine
> until the second reboot. Since then I'm hung on:
> >
> > Init: getty repeating too quickly on port /dev/ttyC0, sleeping
> >
> > I'll probably go through the cause tomorrow and find a solution. Just
> trying to be useful by making
n Fri, Oct 4, 2024, 11:31 Stuart Henderson wrote:
On 2024-10-03, Michael Joy wrote:
> Hey all, just did a sysupgrade -s on current. It all appeared to be fine
> until the second reboot. Since then I'm hung on:
>
> Init: getty repeating too quickly on port /dev/ttyC0, sleepin
On 2024/10/05 09:45, Pierre Peyronnel wrote:
> Happened to me too.
>
> Will I need to manually boot the next snapshot bsd kernel to fix ?
I don't know whether it was a kernel diff or a userland diff that was
the problem. But manually upgrading the machine (kernel+userland) to
the next snapshot (o
peared to be fine
> until the second reboot. Since then I'm hung on:
> >
> > Init: getty repeating too quickly on port /dev/ttyC0, sleeping
> >
> > I'll probably go through the cause tomorrow and find a solution. Just
> trying to be useful by making someone
On 2024-10-03, Michael Joy wrote:
> Hey all, just did a sysupgrade -s on current. It all appeared to be fine
> until the second reboot. Since then I'm hung on:
>
> Init: getty repeating too quickly on port /dev/ttyC0, sleeping
>
> I'll probably go through the cause
Hey all, just did a sysupgrade -s on current. It all appeared to be fine until
the second reboot. Since then I'm hung on:
Init: getty repeating too quickly on port /dev/ttyC0, sleeping
I'll probably go through the cause tomorrow and find a solution. Just trying to
be useful by maki
On Thu, Oct 26, 2023 at 9:03 PM Theo de Raadt wrote:
>
> Crystal Kolipe wrote:
>
> > On Thu, Oct 26, 2023 at 12:20:08PM -0400, Morgan Aldridge wrote:
> > > Yes, your assumption was correct, every keypress acts as if I had
> pressed
> > > enter. Thanks for c
ktrace -di of the process will show what is going on
Crystal Kolipe wrote:
> On Thu, Oct 26, 2023 at 12:20:08PM -0400, Morgan Aldridge wrote:
> > Yes, your assumption was correct, every keypress acts as if I had pressed
> > enter. Thanks for confirming!
>
> Getty re-disp
On Thu, Oct 26, 2023 at 12:20:08PM -0400, Morgan Aldridge wrote:
> Yes, your assumption was correct, every keypress acts as if I had pressed
> enter. Thanks for confirming!
Getty re-displays the login prompt when it sees either 0x00 or 0x80 on the
serial line. In fact, you can do it fr
characters or breaks (AFAICT).
> >
> > On the OpenBSD side (with getty disabled on the tty, of course), I ran
> `cu
> > dr -l ttyU1 -s 9600` and jumped the TX/RX pins, and confirmed that the
> > characters entered were received back without any breaks or odd
> charact
On Wed, Oct 25, 2023 at 01:35:39PM -0400, Morgan Aldridge wrote:
> On the terminal, keeping the same 9600 8N1 settings, but enabling local
> echo, and shorting the TX/RX pins gets me duplicated input with no odd
> characters or breaks (AFAICT).
>
> On the OpenBSD side (with getty
no shorts to ground or other pins, and no odd
> resistance on any of the connections. That's a good start.
>
> On the terminal, keeping the same 9600 8N1 settings, but enabling local
> echo, and shorting the TX/RX pins gets me duplicated input with no odd
> characters or breaks (AF
same 9600 8N1 settings, but enabling local
echo, and shorting the TX/RX pins gets me duplicated input with no odd
characters or breaks (AFAICT).
On the OpenBSD side (with getty disabled on the tty, of course), I ran `cu
dr -l ttyU1 -s 9600` and jumped the TX/RX pins, and confirmed that the
character
On Mon, Oct 23, 2023 at 11:37:10PM -0400, Morgan Aldridge wrote:
> I have experimented with the following with no change in the underlying
> issue of the terminal showing the login prompt, but each character input
> causing the login prompt to be resent:
If you short the tx/rx lines at the DE-9 en
INIT, have run ttyflags(8) (more
specifics below), have the terminal configured for 9600 8N1 with no flow
control, and the terminal does display the login prompt generated by
getty(8). Unfortunately, regardless of what input is provided on the
terminal, getty(8) just sends a new login prompt.
I only h
On Sat, Feb 09, 2019 at 06:28:04PM +, Edd Barrett wrote:
> ttyU0 "/usr/libexec/getty std.9600" vt220 on
For the archives, sthen@ guessed it. You have to add the 'softcar' flag
to your ttyU0 entry in /etc/ttys.
Works a charm.
--
Best Regards
Edd Barrett
http://www.theunixzoo.co.uk
Hi all,
I'm trying to get a USB->serial adapter serving a login prompt via getty.
Here's the converter in question:
---8<---
uftdi0 at uhub3 port 3 configuration 1 interface 0 "FTDI FT232R USB UART" rev
2.00/6.00 addr 2
ucom0 at uftdi0 portno 1
--->8---
The foll
I was setting up a new server where I wasn't sure whether com0 or com1 was
the port I wanted, so I turned on both tty00 and tty01 in /etc/ttys to see
which one to use in boot.conf. Edited the file, did the 'kill -HUP 1',
and... nothing. getty processes are listening on tty00 and
2016-10-21 12:04 GMT+02:00 Mihai Popescu :
> terminal: physical stuff, keyboard + screen + serial port for
> mainframe connection
Relevant: https://www.jwz.org/blog/2016/10/export-termaaa-60/
> enough. Also a link or a book indication for all this stuff will be
> fine.
We have man pages and wiki
frame connection
console: ? stdout, stderr, xconsole? have no idea yet!
tty: software, but that's all i know! maybe to manage a terminal at server side?
cua: software, device for interraction with serial port of the computer
getty: software to manage tty?
Don't bother with OS implementation deta
Miod Vallat wrote:
> > ttyC3 "/usr/libexec/getty std.192600" vt220 on secure
>
> As long as you are using a baud rate recognized by getty, things will
> still work and you won't notice a change, because wsdisplay(4) ttys
> ignore the terminal speed yo
> I would like to change /etc/ttys to get, for instance:
>
> ttyC3 "/usr/libexec/getty std.192600" vt220 on secure
>
> instead of :
>
> ttyC3 "/usr/libexec/getty std.9600" vt220 on secure
>
> Do you think i could run into p
On 2012-08-05, Ben Calvert wrote:
> you must read really fast!
>
> I prefer to set mine to 300 so I don't need to pipe things to more :)
>
> Seriously though, what are you trying to achieve with this setting?
> just because the text will scroll faster doesn't mean the machine
> will run faster..
On 08/05/12 07:14, Friedrich Locke wrote:
> I would like to change /etc/ttys to get, for instance:
>
> ttyC3 "/usr/libexec/getty std.192600" vt220 on secure
>
> instead of :
>
> ttyC3 "/usr/libexec/getty std.9600" vt220 on secure
Why?
92600 is not a "standard" speed.
>>
>>
>> HTH,
>> Dan #13685 (RS/Sec/SP)
>> The CCIE troubleshooting blog: http://dans-net.com
>> Bring order to your Private VLAN network: http://marathon-networks.com
>>
>>
>> On Sun, Aug 5, 2012 at 2:1
n-networks.com
>
>
> On Sun, Aug 5, 2012 at 2:14 PM, Friedrich Locke
> wrote:
>>
>> I would like to change /etc/ttys to get, for instance:
>>
>> ttyC3 "/usr/libexec/getty std.192600" vt220 on secure
>>
>> instead of :
>>
>>
blog: http://dans-net.com
Bring order to your Private VLAN network: http://marathon-networks.com
On Sun, Aug 5, 2012 at 2:14 PM, Friedrich Locke
wrote:
>
> I would like to change /etc/ttys to get, for instance:
>
> ttyC3 "/usr/libexec/getty std.192600" vt220 on s
I would like to change /etc/ttys to get, for instance:
ttyC3 "/usr/libexec/getty std.192600" vt220 on secure
instead of :
ttyC3 "/usr/libexec/getty std.9600" vt220 on secure
Do you think i could run into problems ?
Thanks in advance.
s where I could put something like
yes.
> #!/bin/sh
I recommend the use of ``#!/bin/sh -e'', see ksh(1).
> while [ ! ]; do
I use ``while :; do'' in such cases; BUT: please read init(8), it will
respawn your process anyways; read DIAGNOSTICS section carefully,
especiall
Thanks Marcus! I have been sidetracked with a few things,
but will give this technique a try soon.
I take it dostuff.sh is where I could put something like
#!/bin/sh
while [ ! ]; do
/usr/local/bin/ttyplay kickassci.demo
done
?
On Fri, Jun 15, 2012 at 09:36:43AM +0200, MERIGHI Marcus wrote:
da...@elven.com.au (David Diggles), 2012.06.15 (Fri) 00:20 (CEST):
> I want the default login console to run something like
> /usr/games/worms -n100
> or
> rsh host /opt/local/bin/xaos -driver aa -autopilot
the way I do it...
$ grep ttyC0 /etc/ttys
ttyC0 "/usr/local/libexec/getty.sh" vt220 on
I want the default login console to run something like
/usr/games/worms -n100
or
rsh host /opt/local/bin/xaos -driver aa -autopilot
Instead of
/usr/libexec/getty std.9600
I have tried changing it in /etc/ttys but this is not working.
How can I go about doing this?
It's for a mac68k asci
ere are no tty04..tty10 devices in /dev
>> > There are only tty00..tty03.
>>
>> we don't have devfs, our devices nodes are static. use MAKEDEV or mknod
>> to give you more.
>
> Thanks, guys! Your help is great.
>
> I see incoming calls.
>
> Now
>
> we don't have devfs, our devices nodes are static. use MAKEDEV or mknod
> to give you more.
Thanks, guys! Your help is great.
I see incoming calls.
Now I have in /etc/gettytab:
std.38400|38400-baud:\
:pp=/etc/ppp/ppplogin:\
:sp#38400:
# ps ax|grep getty
25750 ??
On 2009/05/08 14:20, Alexander Shikoff wrote:
> Hi Stuart,
>
> On Fri, May 08, 2009 at 10:35:35AM +, Stuart Henderson wrote:
> > On 2009-05-08, Alexander Shikoff wrote:
> > > I only have two serial ports on motherboard, I see them in dmesg:
> > > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16
* Alexander Shikoff [2009-05-08 13:39]:
> Well, I have no any cy-like card. Why I'm getting cuac# devices in /dev ?
they are always there
> There are no tty04..tty10 devices in /dev
cd /dev; sh MAKEDEV tty04
etc for the others
--
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Servic
Hi Stuart,
On Fri, May 08, 2009 at 10:35:35AM +, Stuart Henderson wrote:
> On 2009-05-08, Alexander Shikoff wrote:
> > I only have two serial ports on motherboard, I see them in dmesg:
> > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> > com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 1
On 2009-05-08, Alexander Shikoff wrote:
> I only have two serial ports on motherboard, I see them in dmesg:
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
>
> But if I understand correctly they are named as cua0[0..1].
>
>> PCI s
On Thu, May 07, 2009 at 02:27:51PM -0400, Brynet wrote:
> Hi Alexander,
Hello,
before we continue I'd like to tell that I'm a kind of newbie in OpenBSD.
I was using FreeBSD for last 5 years, many things in OpenBSD are almost
the same as in FreeBSD (and vice versa) but also there are many differenc
Hi Alexander,
Can you tell us how you came up with those device names? I think it'll
be more like /dev/{cua,tty}[0-7], though that range might be different
if you have any other com(4) devices.
PCI serial cards typically attach as puc(4), meaning com(4) devices
should appear.. or pccom(4).. if yo
Hello,
I have a box with serial 8-port Digi Neo card installed.
It was detected normally, e.g. I see that in dmesg
and all devices (cuac[0-7] and ttyc[0-7] are present in /dev directory.
Now I'm trying to setup dial-up server with getty and ppp.
I have added to /etc/ttys:
ttyc0 "/u
Hi,
I've managed to have an OpenBSD4.0 box connected to another box via
serial cable, with a getty running on both ends. I killed one getty and
connected to the serial port with a terminal program. But the other
getty was already gone, having spawned login. Now I have two login
processes a
Hi Folks,
I'm trying to configure the serial port (COM1) on a ProLiant DL380-G2
for logins running OpenBSD 3.9.
In /etc/ttys:
tty00 "/usr/libexec/getty std.9600" vt220 on secure
# dmesg | grep com
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
I've HUP
43 matches
Mail list logo