Dear group,
is anyone running yacy on a openbsd box?
I tested the latest one yacy on a 5.3 amd64 but didn't succeed. The only
resource I found was:
http://ventejuy.es/cgi-bin/post?p=11051522005289 (in Spanish!)
but was unable to connect to localhost:8090
Thanks
On Sun, Aug 04, 2013 at 11:08:39AM +0300, Tony Berth wrote:
> Dear group,
>
> is anyone running yacy on a openbsd box?
>
> I tested the latest one yacy on a 5.3 amd64 but didn't succeed. The only
> resource I found was:
>
> http://ventejuy.es/cgi-bin/post?p=11051522005289 (in Spanish!)
>
>
Is there some GUI-front-end for (at least) the wlan related functionality of
ifconfig?
(No need to argue here, about the flexability of ifconfig and the restrictions
of
any GUI-approach)
The point is, that using OBSD as a workstation on a laptop, requires a lot of
authentification at different
"Mirco Richter" writes:
> Is there some GUI-front-end for (at least) the wlan related functionality of
> ifconfig?
http://www.undeadly.org/cgi?action=article&sid=20110420080633 hints
that M:tier (http://www.mtier.org/) has something of that sort, but I
can't specifically remember whether they'v
On Sun, Aug 04, 2013 at 12:07:29PM +0200, Mirco Richter wrote:
> Is there some GUI-front-end for (at least) the wlan related functionality of
> ifconfig?
>
> (No need to argue here, about the flexability of ifconfig and the
> restrictions of
> any GUI-approach)
>
> The point is, that using OBSD
> Doing this on the terminal is simply a waste of time and it would be rational
> to have a GUI for at least this subset of the full ifconfig functionality.
Care to elaborate on that? What makes it slow for you on the terminal? What
would a GUI need to have to be faster? Don't tell me you want
I don't use a GUI but I hacked together a little Python script that
basically calls `ifconfig wpi0 scan` to obtain a list of available
networks, filters out the known ones, sorts them by priority and signal
strength and then configures the one on the top of the list with
ifconfig and if need be, wi
On Sun, Aug 4, 2013 at 2:04 PM, Stefan Sperling wrote:
> I've looked into porting network manager and wcid some time back.
> It's horrid. They both rely on Linux-specific features like udev
> so it's not trivial to port them.
Maybe porting the one below could be easier:
https://github.com/pcbsd
Erling Westenvik [erling.westen...@gmail.com] wrote:
>
> physical disks:
> sd0a: 64 + N-64
> sd1a: 64 + N-64
> RAID 1 volume:
> sd2a: 64 + 64 + N-128
> CRYPTO volume:
> sd3a: 64 + 64 + 64 + N-196
>
> The space wasted on large disks is negligible but I would really like to
> know at which
Hi,
I am trying to configure poptop on OpenBSD 5.3 without success. I've
installed the package and configured the files as
the /usr/local/share/doc/pkg-readmes/poptop-1.3.4p4 says but didn't work so
I started to change things here and there without success. These are the
facts:
/etc/pptpd.con
Hi,
Why not use the embedded package in OpenBSD 5.3 : npppd ??
conf files : /etc/npppd/npppd.conf and npppd-users
Below a link that will help you on :
http://fr.slideshare.net/GiovanniBechis/npppd-easy-vpn-with-openbsd
Cheers,
Wesley
Le 2013-08-05 4:48, Alvaro Mantilla Gimenez a écrit :
Hi,
I approve Wesley,
if you use OpenBSD 5.3 you should use npppd it's simpler than poptop and
have nearly the same functionalities
--
Best regards,
Loïc BLOT,
UNIX systems, security and network expert
http://www.unix-experience.fr
Le lundi 05 août 2013 à 08:46 +0400, Wesley MOUEDINE ASSABY a éc
12 matches
Mail list logo
