On Tue, 1 Oct 2002 14:27, Matthias Urlichs wrote: > > but would not work for calling Debconf from Bash. > > You're right -- bash lacks this feature. However, the context of the > original question specifically mentioned Perl (or so I remember -- anyway, > it used backticks, and nobody would use backticks in bash just for their > side effects of running a program ;-).
True, the original question was about Perl, but there are bigger issues to consider. > > Debconf could easily run in a client-server manner and the client could > > connect to a unix domain socket. > > Unfortunately, the current protocol is too stateful for that -- this However the interface that is exported to the application is not stateful at all. > idea would insert a client process between the display system and the > configuree, but it won't change the real problem -- the various shell > functions would still need a shared file descriptor. Hmmm... you could do > it with a pair of FIFOs in the file system, though. I'll have to think > about that. Yes, a pair of FIFO's will allow regular shell scripts to do the debconf thing. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]