| 00:58:48 | Neuromante | is away: no toy |
| 01:21:57 | Neuromante | is back (gone 00:23:05) |
| 15:47:49 | andersee | is away: eating breakfast |
| 16:47:39 | andersee | is back (gone 00:59:47) |
| 17:52:35 | softweyr | andersee: thanks for the quick email response. ;^) |
| 17:55:28 | andersee | softweyr: no prob |
| 17:55:30 | andersee | :) |
| 18:03:53 | softweyr | building now... |
| 18:16:40 | andersee | softweyr: so are you doing Linux stuff these days? using uClibc? |
| 18:58:26 | andersee | Morning BZFlag |
| 18:58:34 | andersee | or rather, afternoon |
| 19:48:59 | softweyr | andersee: yes, to both. |
| 19:49:20 | softweyr | oh, actually, we're using busybox on 2 platforms but uClibc on only one. |
| 19:49:49 | softweyr | we weren't sure how robust and fast the thread library is on uClibc for our "big" platform. |
| 19:50:12 | softweyr | we also use tinylogin and utelnetd (now) on the PPC platform. |
| 19:50:27 | andersee | softweyr: cool |
| 19:50:45 | andersee | softweyr: BTW, utelnetd is now in busybox 0.61 pre... |
| 19:50:56 | softweyr | andersee: cool. |
| 19:51:11 | softweyr | we'll need to update to 0.61 once it hits release. |
| 19:51:31 | softweyr | meeting... back in 20 mins or so. |
| 19:52:28 | softweyr | meeting postponed. |
| 19:52:47 | softweyr | our "expansion" boxes have 2x 2.4GHz P4's with 8 or 16 GB RAM. |
| 19:52:56 | softweyr | that's why we're on Linux now. ;^) |
| 20:00:31 | andersee | Ahh |
| 20:00:42 | andersee | Bit tricky to do that with freeBSD. :) |
| 20:02:13 | andersee | I've been intending to do a freeBsd port for some time now. Never gotten around to it. |
| 20:02:36 | andersee | With the 0.61 series, the infrastructure is in place to actually make it work |
| 20:51:06 | BZFlag | andersee: hmm... does askfirst get a controlling tty? |
| 20:51:37 | BZFlag | and is there any diff between a ^: entry and a ^tty1: entry? |
| 20:52:32 | BZFlag | is tty1 then considered a "controling tty" ? |
| 20:54:00 | andersee | BZFlag: yes. askfirst does get a controlling tty. |
| 20:54:24 | andersee | BZFlag: With askfirst I assume it will be used interactively, so it gets a ctty |
| 20:55:09 | sandman | where's the problem with *always* providing a ctty like sysvinit does ? |
| 20:55:28 | andersee | Right now, I decided whether an init action needs a ctty depending on the type of action. |
| 20:55:33 | andersee | sandman: do they? |
| 20:55:49 | andersee | sandman: I thought they did not provide one for respawn actions |
| 20:56:11 | sandman | sorry -- I thought you said so in your mail |
| 20:56:21 | sandman | just forget this comment then ;) |
| 20:57:28 | BZFlag | if there is a device listed, can't that be set as the ctty? |
| 20:58:41 | BZFlag | should probably look at the code. =) |
| 22:33:48 | BZFlag | seems to me if there is a device listed, we should try setting it to ctty. If that fails, then continue anyway. I think it would fail for devices like null, yes? so: |
| 22:34:43 | BZFlag | null::respawn:/sbin/tuxphone |
| 22:34:48 | BZFlag | would still be ok. |
| 22:35:42 | BZFlag | some may want "::sysinit:/etc/init.d/rcS" and some may like "console::sysinit:/etc/init.d/rcS" ;-) |
| 22:39:36 | andersee | BZFlag: that is probably a reasonable solution |