And I was right, the splashy_main.c from tags/0.2.2 and the one in trunk are not in sync ;-)<br><br> if (g_ascii_strncasecmp (basename (argv[0]), "splashy_chvt", 12) == 0)<br> {<br> char *c = argv[1];
<br> for (c = argv[1]; *c != '\0'; c++)<br> if (!isdigit (*c))<br> {<br> g_printerr ("%s\n", USAGE);<br> return 1;
<br> }<br> /*<br> * behave like chvt <br> */<br> splashy_chvt (atoi (argv[1]));<br> return 0;<br> } else {<br> /* go to an unused tty */
<br> int vt_fd = open ("/dev/tty8", O_RDWR);<br> switch_console(8, vt_fd);<br> close (vt_fd);<br> }<br><br>Tim,<br>is there a reason why we should not do this in splashy_main.c ? Diff tags/0.2.2/src/splashy_main.c (or branches/0.2.x/src/splashy_main.c for that matter) against the same file in trunk/src/splashy_main.c to see stuff that is missing:
<br><br><br><br><div><span class="gmail_quote">On 2/17/07, <b class="gmail_sendername">Luis</b> <<a href="mailto:lemsx1@gmail.com">lemsx1@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello Pat,</blockquote><div><br>[snip] <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Long story short, what I witnessed tonight is exactly what I witnessed a
<br>> year ago: resource contention. Splashy takes two ttys, stays on one of<br>> them, init is forced to take another, things expect to be on the tty<br>> that init is on, there is a lock.<br><br>I'll have a fresh look at this issue and see why tty8 is not been used.
<br><br>> Something I had meant to experiment with last year (never got the<br>> chance), was to make splashy open a higher tty by default, say tty6 or<br>> tty9. Perhaps if init is on tty0 it will be happier. Maybe there could
<br>> be some experimentation whether a tty even needs to be opened?<br>><br>> The line that opens the tty has a blatant error, btw:<br>> "O_RDONLY|O_WRONLY" makes no sense whatsoever. It should be either-or,
<br>> or O_RDWR. This might be another source of problems if it does not run<br>> as designed.<br><br>This might be just the problem. I can't recall exactly why we used<br>both flags there. But I remember looking at examples of this and
<br>reading the man page for the system call. I'll try using O_RDWR.<br><br>> Sorry about the long eMail. Perhaps something useful will come of this.<br>> I feel we will be a big step closer when we figure out why tty2 is used,
<br>> amongst other things.<br>><br>> It's all in the tty's, folks.<br>> --Pat<br><br></blockquote></div><br clear="all"><br>-- <br>----)(----- <br>Luis Mondesi<br>*NIX Guru<br><br>"Feliz el hombre que ha hallado sabiduria y el hombre que consigue discernimiento, porque el tenerla como ganancia es mejor que tener la plata como ganancia; y el tenerla como producto, [mejor] que el oro mismo" (Prov 3:13-14).
<br><br>01010101 01110011<br>01100101 00100000<br>01010101 01100010<br>01110101 01101110<br>01110100 01110101<br>00100000 01001100<br>01101001 01101110<br>01110101 01111000