Contributed by grey on from the almost slipped off the radar dept.
The project page may be found here: http://www.nullcube.com/software/pyopenbsd.html
Below is the text from the original announcement back in November, which we unfortunately missed at that time:
PyOpenBSD is an extensive set of Python bindings for libraries and functionality specific to the OpenBSD operating system. PyOpenBSD's capabilities include interface manipulation, extensive access to network statistics, an interface to kernel events through kqueues, arbitrary network packet parsing and manipulation, and complete pcap bindings. For more information, please see the manual linked from the PyOpenBSD page. Please note that this is an Alpha release, intended mostly to invite participation and comments from the Python and OpenBSD communities. http://www.nullcube.com/software/pyopenbsd.html -- Aldo Cortesi aldo at nullcube.com http://www.nullcube.com Off: (02) 9283 1131 Mob: 0419 492 863
This looks like it could be really useful for python and OpenBSD fans; but I think my favourite comment (or at least the funniest) on the subject as uttered by Tim Newsham may be found here.
(Comments are closed)
By Dunceor (192.36.1.253) dunceor@gmail.com on
Comments
By FG (12.175.222.29) on
devel/py-openbsd
By grey (207.215.223.2) on
By Sean Brown (204.209.209.129) on
Comments
By Krunch (81.240.117.88) on http://krunch.servebeer.com/~krunch/
Comments
By johannes (131.130.1.143) on
Admittedly I am neither able to program in Perl nor do I have much clue about ioctl, i.e. it's just a wild idea.
Regards,
j.
Comments
By Anonymous Coward (67.34.129.203) on
use OpenBSD::pf;
my $pf = new pf;
$pf->block_in(from => '192.168.1.0/24', to => ANY);
By B (218.102.177.2) on
Comments
By Anonymous Coward (67.34.129.203) on
/usr/libdata/perl5/OpenBSD/Logger.pm
/usr/libdata/perl5/OpenBSD/Makewhatis.pm
/usr/libdata/perl5/OpenBSD/Makewhatis/Check.pm
/usr/libdata/perl5/OpenBSD/Makewhatis/Find.pm
/usr/libdata/perl5/OpenBSD/Makewhatis/Formated.pm
/usr/libdata/perl5/OpenBSD/Makewhatis/Unformated.pm
/usr/libdata/perl5/OpenBSD/Makewhatis/Whatis.pm
/usr/libdata/perl5/OpenBSD/PackageInfo.pm
/usr/libdata/perl5/OpenBSD/PackageLocator.pm
/usr/libdata/perl5/OpenBSD/PackageName.pm
/usr/libdata/perl5/OpenBSD/PackingElement.pm
/usr/libdata/perl5/OpenBSD/PackingList.pm
/usr/libdata/perl5/OpenBSD/PackingOld.pm
/usr/libdata/perl5/OpenBSD/PkgCfl.pm
/usr/libdata/perl5/OpenBSD/RequiredBy.pm
/usr/libdata/perl5/OpenBSD/Temp.pm
/usr/libdata/perl5/OpenBSD/Ustar.pm
/usr/libdata/perl5/OpenBSD/Vstat.pm
/usr/libdata/perl5/OpenBSD/md5.pm
Basically just a bunch of package system stuff...
By antonakis (193.58.186.122) on
By Anonymous Coward (81.209.99.177) on
Comments
By Bert (68.50.4.145) thrashbluegrass at antisocial dot com on
God knows, the first thing that popped into my mind was a GUI for a number of administrative tasks, which I am (and probably some friends are) probably going to start hacking on once the project gets to a good beta.
Sure, you can drop into an xterm to do that, but most people I know are scared stiff of a command prompt. Making a GUI admin console is one of those things that is a prerequisite for greater usage of unix on the desktop.
Comments
By Anonymous Coward (67.34.129.203) on
Comments
By Anonymous Coward (81.209.99.177) on
By Bert (68.50.4.145) thrashbluegrass at antisocial dot com on
Not really, and I don't really have to: if something can be offered on cheap x86 hardware, I'm willing to bet that it would compete favorably with the ultra-slick OSX at over a grand a pop for a machine. Especially since we're talking about me building something for my friends and family, not attempting to break into the commercial market.
Hell, if Apple would port their candy to Intel hardware, we'd probably see a massive dropout of Windows desktop users.
By Anonymous Coward (69.137.66.149) on
Comments
By Anonymous Coward (64.48.234.32) on
By SH (82.182.103.172) on
Comments
By Anonymous Coward (81.209.99.177) on
Comments
By tedu (67.127.59.81) on
By nickf (67.86.34.250) on
By jb (217.35.105.99) on
"insecure! theo said it!". boy, if you're driven by things like
that without even trying to use your brain to reckon stuffs are
secure (or not), i don't want to see your security policies :-P
By djm@ (218.214.226.34) on