On Fri, May 03, 2013 at 06:01:24PM -0400, Michael W. Lucas wrote:
> On Fri, May 03, 2013 at 10:41:32PM +0200, Erling Westenvik wrote:
> > To my astonishment: when printing a test page from cups, it outputs an
> > image of Tux!?!
>
> Cups is Linux-ware, ported to OpenBSD.
Used-to be linux-ware. Ac
On Fri, May 03, 2013 at 06:08:15PM -0700, Scott wrote:
> Ken,
> Thanks for the tip! pkg_scripts did the trick (I'd never seen that
> mechanism before). With regards to making adsuck play nice with dhcp (yes,
> I tired the "script" line from the readme only to get errors), maybe the
> dhclient-adsuc
Ken,
Thanks for the tip! pkg_scripts did the trick (I'd never seen that
mechanism before). With regards to making adsuck play nice with dhcp (yes,
I tired the "script" line from the readme only to get errors), maybe the
dhclient-adsuck script was rewritten? I've done nothing special and yet it
all
I want to use fastcgi and suexec to run php programs as particular users
from Apache in a chroot. I've found documentation on running suexec, but I
can't find anything OpenBSD specific on getting fastcgi and php into the
chroot so I can use them. If you could at least please just point me in the
di
On Fri, May 03, 2013 at 02:52:06PM -0700, Scott wrote:
> Good day,
> I can't get adsuck to start at boot on OpenBSD 5.3. I copied strings like a
> monkey and thought them over (even testing them in shell), but no luck.
>
> # grep adsuck /etc/rc.conf.local:
> adsuck_flags="-c /var/adsuck -f /files/
Michael W. Lucas wrote:
> > To my astonishment: when printing a test page from cups, it outputs an
> > image of Tux!?!
>
> Cups is Linux-ware, ported to OpenBSD.
> The name claims to be "common," but no, it's Linux-centric.
Actually...
"CUPS is the standards-based, open source printing system
Correct me if I'm wrong, but isn't CUPS originally UNIX-ware?
Quoting:
'UPS is the standards-based, open source printing system developed by
Apple Inc. for OS® X and other UNIX®-like operating systems.'
Best regards,
Nikola Gyurov
On Fri, May 3, 2013 at 3:01 PM, Michael W. Lucas
wrote:
> On Fri
On Fri, May 03, 2013 at 10:41:32PM +0200, Erling Westenvik wrote:
> To my astonishment: when printing a test page from cups, it outputs an
> image of Tux!?!
Cups is Linux-ware, ported to OpenBSD.
The name claims to be "common," but no, it's Linux-centric. As the
test logo shows.
==ml
--
Michae
Good day,
I can't get adsuck to start at boot on OpenBSD 5.3. I copied strings like a
monkey and thought them over (even testing them in shell), but no luck.
# grep adsuck /etc/rc.conf.local:
adsuck_flags="-c /var/adsuck -f /files/resolv.conf /files/hosts.small"
# cat /etc/rc.local:
if [ "$adsuck
To my astonishment: when printing a test page from cups, it outputs an
image of Tux!?!
>> Hello list,
>>
>> Has anyone managed to set dual boot on an UEFI box with "secure boot"
>> left
>> enabled? If the answer is yes, are there some instructions how to
>> achieve
>> that?
>>
>> I am trying to install -current on a Lenovo Y400 notebook, leaving
>> pre-installed windows 8 intact, as
* John Tate [2013-05-03 17:23]:
> I have a squid proxy listening in transparent mode on another faster
> system, but I can't seem to get packets there with pf. I tried simply
> modifying the other divert-to rule to use the IP address of that system. It
> doesn't seem to work, packets don't reach t
> Hello list,
>
> Has anyone managed to set dual boot on an UEFI box with "secure boot" left
> enabled? If the answer is yes, are there some instructions how to achieve
> that?
>
> I am trying to install -current on a Lenovo Y400 notebook, leaving
> pre-installed windows 8 intact, as per the wishes
John Tate wrote:
>I have a squid proxy listening in transparent mode on another faster
>system, but I can't seem to get packets there with pf. I tried simply
>modifying the other divert-to rule to use the IP address of that
>system. It
>doesn't seem to work, packets don't reach that system.
>
>#p
...to everyone involved. Beautiful stuff that really tickles my
obsessions. Outstanding, people.
--
Monty Brandenberg, Software Engineer MCB, Inc.
mcb...@panix.com P.O. Box 425292
mcb...@pobox.com
On 05/03/13 14:03, Peter J. Philipp wrote:
I recently reworked my network and made my G4 Cube an IPSEC tunneling
host. Here is what I have done.
[jupiter] <> [uranus] <--- wireless network starts here --->
[wireless router] <> [mars]
[snip]
Here is the CPU stats on mars:
CPU s
I have a squid proxy listening in transparent mode on another faster
system, but I can't seem to get packets there with pf. I tried simply
modifying the other divert-to rule to use the IP address of that system. It
doesn't seem to work, packets don't reach that system.
#pass in quick on $int_if in
On Fri, May 03, 2013 at 04:38:45PM +0200, Xianwen Chen wrote:
> Ted Unangst wrote:
> >I think the easiest option is to install vim and use that.
> I was going for that option. I asked the question on the list
> anyway. I thought I might have missed something.
> >In general, our policy is to only
On Fri, May 03, 2013 at 03:48:15PM +0200, Xianwen Chen wrote:
> Hi,
>
> I'm learning to use vi. I find that the buffer operation is
> different in vi than vim. For example, in vim, it is ':bn', ':bp',
> and ':bd' to go to next and previous buffer, and to close a buffer.
> Vi does not seem to hav
On Fri, May 3, 2013 at 9:38 AM, Xianwen Chen wrote:
> In general, our policy is to only document features that exist.
>> The list of features that don't exist would be a neverending list. If
>> you are reading something other than official openbsd documentation,
>> it's your responsibility to ve
Ted Unangst wrote:
I think the easiest option is to install vim and use that.
I was going for that option. I asked the question on the list anyway. I
thought I might have missed something.
In general, our policy is to only document features that exist.
The list of features that don't exist wou
On Fri, May 03, 2013 at 15:48, Xianwen Chen wrote:
> I'm learning to use vi. I find that the buffer operation is different in
> vi than vim. For example, in vim, it is ':bn', ':bp', and ':bd' to go
> to next and previous buffer, and to close a buffer. Vi does not seem to
> have them implemented.
Hi,
I'm learning to use vi. I find that the buffer operation is different in
vi than vim. For example, in vim, it is ':bn', ':bp', and ':bd' to go
to next and previous buffer, and to close a buffer. Vi does not seem to
have them implemented.
Because of the popularity of vim, a lot of docu
On Fri, May 03, 2013 at 02:03:08PM +0200, Peter J. Philipp wrote:
> I recently reworked my network and made my G4 Cube an IPSEC
> tunneling host. Here is what I have done.
>
> [jupiter] <> [uranus] <--- wireless network starts here --->
> [wireless router] <> [mars]
>
[snip]
> Consider
I recently reworked my network and made my G4 Cube an IPSEC tunneling
host. Here is what I have done.
[jupiter] <> [uranus] <--- wireless network starts here --->
[wireless router] <> [mars]
Jupiter is a core i7 computer running OpenBSD/amd64
Uranus is a Lanner atom based router runn
25 matches
Mail list logo
