Sep
23
2009
|
Written by HR
|
|
Wednesday, 23 September 2009 |
|
In spite of the economic downturn, or perhaps because of it, PBnJ Solutions is growing and so are the number of opportunities to come work with us. You won't find .NET work here though - we are (almost exclusively) FOSS tools based although that does not mean that our coding results are necessarily covered by GPL variants. Instead we use these FOSS tools and platforms to provide our clients with unique and cost-effective solutions to achieve their goals. Perhaps a few examples will give you a flavor of the kind of work we do...
One example would be the PERL programs that were developed for a large subsidiary of CitiBank which helped them route their massive email flow (100,000+ AFTER the SPAM filter) through a pair of machines which effectively duplicated each message and sent the clone on to a Microsoft Exchange Mailbox set up for archiving purposes.
Then there is the PHP-based component for Joomla!, a Content Management System (CMS), which helps a medical office manage its barrage of PDF submissions to credentialing organizations. Or perhaps the Ruby implementation of a psychological profile questionnaire management system.
This is not to mention the myriad of smaller tools we develop for our clients in the process of building Asterisk-based phone systems controlled by sophisticated PHP logic or outright command line utilities to manage commercial software packages such as Symantec NetBackup.
Read on to learn how you can contact us to work with PBnJ Solutions to work with the tools you love and earn a living too! |
|
Last Updated ( Tuesday, 06 October 2009 )
|
|
Read more...
|
|
Oct
06
2009
|
VMware Virtual NIC Choice and SYSPREPing Templates |
|
Written by Paul Winkeler
|
|
Tuesday, 06 October 2009 |
|
Under ESX 3.5 an enhanced NIC choice called vmxnet became available but only to 64-bit VMs. The idea behind this new virtual device is that by publishing itself as TCP/IP offload capable, the Windows OS will not bother to encapsulate data into a TCP/IP packet before handing it to the ethernet driver, instead leaving that task to the (virtual) hardware. As a result, the vmxnet device no longer has to parse and strip the TCP/IP packet information so it can hand the payload off to the *real* physical NIC and everybody wins.
This improvement was big enough that numerous VMs have been changed to 64-bit even if the guest Windows OS was still 32-bit; all just to gain access to that more efficient NIC. But guess what? No good deed goes unpunished and indeed neither does this one. When one of my customers came to me a few weeks ago with a scenario that prevented her from SYSPREPing a VM she tried to create from a template even after installing every SYSPREP CAB's contents into all possible folders, we, as well as VMware support, were stumped. Finally we discovered that the reason the option to customize the template deployment was grayed out was because of the mismatch between a 64-bit VM and a 32-bit guest OS! All we had to do was convert the template to a 32-bit VM and everything worked as advertised.
My biggest gripe here is that the VMware GUI gave absolutely no feedback to this effect. None. Zero, Zip, Zilch. Ah well, live and learn. |
|
Last Updated ( Tuesday, 06 October 2009 )
|
|
Sep
09
2009
|
IAX2: A bit more official |
|
Written by Administrator
|
|
Wednesday, 09 September 2009 |
|
After many years of hard work the Inter Asterisk eXchange protocol version 2 (IAX2) has been published under the auspices of the IETF as RFC 5456. Note that the editor uses the second sentence to clearly define this document: "It does not specify an Internet standard of any kind." Then again, it took the SIP RFC a long time to get to the standards track as well.
|
|
Read more...
|
|
|
|
<< Start < Prev 1 2 3 Next > End >>
|
| Results 1 - 4 of 12 |
