[Fwd: Vgetty question]

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

> Actually I think this is a good design.  You have low level functions
> (tio.o, locks.o, logfile.o - they could be in a library, but I didn't do
> that for portability), mid level functions (libvoice.a) and high level
> programs (vgetty, vm).  How would you do this differently?
For portability ?
Please say me what a library have to do with portability !!!

> > Why didn't you use standard file locking ?
> What do you mean by this?  The only place mgetty/vgetty does "file
> locking" is for the serial port, and there is only one "standard" way to
> do that - using LCK..ttySx files, and this is what locks.o is doing.
flock can do it all.

> > Why doesn't you act as a server which could serve other applications
> > using modem
> > ( and no, this is not off topic because vgetty is, as far as i know, the
> > only software
> > which has driver for several modem... )
> 
> This can be done using the "vm shell" interface - you have the "server"
> (vm) and the "client" (the voice shell), they talk to each other, and the
> client can use vm to talk to the modem.  What are you missing?

Duh, you mean to make shell vm call from a C program ?
This is dirty...

> Where's the difference between "make an exec call / talk to a pipe" and
> "make a socket call and have inetd exec() a server process"?

1: Vgetty listen on a pipe ? If yes say me where is it.
2: Why to use inetd, a process can fork() when it got a connection...
Vgetty is a server at a modem level but not at an applications level...
As i've said, vgetty is the only software with many modem driver
included,
you've made this work... 
and it's fine, so what i say is that it could be
cool that other modem applications can reuse these drivers.

> Hmmm.  Why do you want to use vgetty for that *at all*?  You're not using
> any of vgetty's capabilities, and sending three AT commands to the modem
> is pretty easy...  I don' think vgetty is the right approach for *this*.

What i'm trying to explain you is that we should had an interface to
vgetty
for an user to make voice communication.
( for all modem that support it )

> What you want doesn't need vgetty's power, "chat" can do it just fine.

Don't understand your point of view here... But :
I don't want to make a soft only for my modem,
and this is the problem... Vgetty have many modem driver in it...
So using vgetty power could be just fine... And adding to vgetty the
possibility to ask the modem for a full voice mode communication (
LOCAL_HANDSET )
should be possible... ( for modem that support this feature )

Not to long this time... I hope :-)

-- 
             			  -- Yoann
	It is well known that M$ products don't call free() after a malloc().
	The Unix community wish them good luck for their future developments.