Date: Fri, 19 Apr 1996 03:14:34 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: David Muir Sharnoff <muir@idiom.com> Cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), ache@astral.msk.su (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=), nate@sri.MT.net, scrappy@freefall.freebsd.org, freebsd-bugs@freefall.freebsd.org, core@freebsd.org Subject: Re: bin/1019 Message-ID: <17866.829908874@time.cdrom.com> In-Reply-To: Your message of "Fri, 19 Apr 1996 01:52:09 PDT." <199604190852.BAA03814@idiom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> As for me doing a better job of detecting it, I'm not sure. Certainly > not immediatly. I think a more interesting thing would be to work on > either mgetty or faxgetty and teach them to do it. I would like to be > able to receive faxes too! It seems like this is the kind of problem that screams out for further generalization. What about implementing a "super getty" that allowed you to configure it dynamically to recognise certain patterns (using some suitably powerful pattern specification format) and invoke some program *other* than login based upon this? You could read in the possible patterns and then construct a fairly simple state machine out of it (maybe a trie?). One analogy (though a poor one :-) might be how the kernel uses different image activators to load binaries based on what headers it sees on them. This would be a similar sort thing, except getty would be handing off to a different "handler program" based on the initial handshake. It certainly seems that having things like mgetty/ppp getty/foo getty and bar getty is a non-optimal solution to the problem. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17866.829908874>