is that (arguably)
the easiest way for an external app to communicate with wpa_supplicant
is via dbus, but wpa_supplicant in FreeBSD is built without dbus
support; another option would be to use something like
http://projects.otaku42.de/browser/python-wpactrl.
-James Butler
scripts to start
one or the other? Which one gets to claim port 631?
-James Butler
[1] Actually, PBI might work just fine even for
embedded if we address the disk bloat issue. One
approach would be to make
/Package/Bar/libfoo-2.8.7.so
a symlink or hardlink to
/Package/Shared/libfoo-2.8.7
with B4.0 alongside
A1.1 and B3.2.
I'll try to find the paper I'm recalling after work, until then I'll
just have to wave my hands in the air.
-James Butler
working on a new package system in MidnightBSD for some time. When we
weighed this issue, it was decided that letting users have old
scripts to start
one or the other? Which one gets to claim port 631?
-James Butler
[1] Actually, PBI might work just fine even for
embedded if we address the disk bloat issue. One
approach would be to make
/Package/Bar/libfoo-2.8.7.so
a symlink or hardlink to
/Package/Shared/libfoo-2.8.7
to get dockapps to work with if I make this change? I'd like to
try it out.
fvwm2 in one I'm quite sure about.
Openbox does natively, and Xfce can with a panel plugin.
-James Butler
___
freebsd-ports@freebsd.org mailing list
http
2009/7/24 Sahil Tandon sa...@tandon.net:
On Thu, 23 Jul 2009, Adam Townsend wrote:
I'm using the ports online (from the freebsd.org site) to get ports for my
my computers running FreeBSD (running on dial-up). I found that the Python
3.1 source links are all broken. They all contain
