You're probably right. There's a sourceforge project called openhttpd
(http://sourceforge.net/projects/openhttpd/), but it seems to be made by
someone named Peter Müller, whereas `whois openhttpd.net` seems to
indicate that the owner of the site is named Volker Kokula.
On 22/12/14 14:41, Eric Furm
On 21/12/14 07:45, Theo de Raadt wrote:
>> I've noticed that, when trying to build the installxx.iso and
>> installxx.fs images, instead of using the already defined ${RELEASEDIR}
>> used by the remainder of the process, two new variables are used instead:
>>
>> RELXDIR?= /home/relx-${MACHINE
I've noticed that, when trying to build the installxx.iso and
installxx.fs images, instead of using the already defined ${RELEASEDIR}
used by the remainder of the process, two new variables are used instead:
RELXDIR?= /home/relx-${MACHINE}
RELDIR?=/home/rel-${MACHINE}
I can see that
On 12/12/14 15:36, Theo de Raadt wrote:
>> On 12/12/14 15:25, Martin Brandenburg wrote:
>>> Riley Baird wrote:
>>>
>>>> On 07/12/14 23:42, Kaspars Bankovskis wrote:
>>>>> Your changes to the system will be very small, and most of the time
>&g
On 08/12/14 01:07, Dmitrij D. Czarkoff wrote:
> Riley Baird said:
>> However, remember that if someone doesn't know much about OpenBSD, they
>> will either: a) think that OpenBSD does not contain binary-only firmware
>> due to the "Blob-Busters" marketing or b)
On 12/12/14 15:25, Martin Brandenburg wrote:
> Riley Baird wrote:
>
>> On 07/12/14 23:42, Kaspars Bankovskis wrote:
>>> Your changes to the system will be very small, and most of the time
>>> you'll be just renaming 'openbsd' to something else, and s
On 08/12/14 01:00, Luiz Roberto dos Santos wrote:
> At 7 Dec 2014 12:42:41 + (UTC) from Kaspars Bankovskis
> :
>> there are more useful things to do, don't you think so?
> Agree. Riley, I think you don't get the point here. The firmware blob are
> *not* running on the system, but on device.
>
On 08/12/14 00:36, Bryan Steele wrote:
> On Sun, Dec 07, 2014 at 07:35:03PM +1100, Riley Baird wrote:
>> I agree entirely. For this reason, I think it would be best to keep
>> system internals (e.g. uname, includes, etc.) using the name OpenBSD
>> with only the main user-visib
On 07/12/14 23:42, Kaspars Bankovskis wrote:
> Your changes to the system will be very small, and most of the time
> you'll be just renaming 'openbsd' to something else, and syncing back
> changes from upstream. If you have time for that, lucky you. But there
> are more useful things to do, don't y
On 07/12/14 23:37, Martin Schröder wrote:
> 2014-12-06 9:45 GMT+01:00 Riley Baird
> :
>> I have a few questions about OpenBSD's trademark policy. (I tried
>> looking, but I couldn't find a document.)
>
> Is OpenBSD actually a registered trademark? The USPTO doe
After a private conversation with Theo, I've decided that I'm not going
to respond to any of your emails for 4-6 days. You'll still get a
response, but just not now. :)
On 07/12/14 21:51, Joel Rees wrote:
> On Sun, Dec 7, 2014 at 7:09 PM, Riley Baird
> wrote:
>>>>>> I have a few questions about OpenBSD's trademark policy. (I tried
>>>>>> looking, but I couldn't find a document.)
>>>>>>
>>
On 07/12/14 21:32, Brad Smith wrote:
> On 12/07/14 05:18, Riley Baird wrote:
>> On 07/12/14 20:52, Otto Moerbeek wrote:
>>> On Sun, Dec 07, 2014 at 08:29:48PM +1100, Riley Baird wrote:
>>>
>>>> On 07/12/14 20:20, Dmitrij D. Czarkoff wrote:
>>>>>
On 07/12/14 20:52, Otto Moerbeek wrote:
> On Sun, Dec 07, 2014 at 08:29:48PM +1100, Riley Baird wrote:
>
>> On 07/12/14 20:20, Dmitrij D. Czarkoff wrote:
>>> Riley Baird said:
>>>> As for why I want to create the distro, I think that OpenBSD has
>>>> e
I have a few questions about OpenBSD's trademark policy. (I tried
looking, but I couldn't find a document.)
1. What is OpenBSD's stance on allowing derivative distros to keep the
name "OpenBSD" throughout the system?
>>>
>>> It's a ton of work to change the name. I'm curiou
On 07/12/14 20:20, Dmitrij D. Czarkoff wrote:
> Riley Baird said:
>> As for why I want to create the distro, I think that OpenBSD has
>> excellent security, and I would like to create a version without the
>> binary-only microcode included.
>
> Isn't it easier to
On 07/12/14 19:59, Brad Smith wrote:
> On 12/07/14 03:35, Riley Baird wrote:
>> As for why I want to create the distro, I think that OpenBSD has
>> excellent security, and I would like to create a version without the
>> binary-only microcode included.
>
> Doesn'
On 07/12/14 19:53, Kaspars Bankovskis wrote:
> On Sun, Dec 07, 2014 at 07:35:03PM +1100, Riley Baird wrote:
>> As for why I want to create the distro, I think that OpenBSD has
>> excellent security, and I would like to create a version without the
>> binary-only microcod
On 07/12/14 09:05, Daniel Dickman wrote:
> On Sat, Dec 6, 2014 at 3:45 AM, Riley Baird
> wrote:
>> I have a few questions about OpenBSD's trademark policy. (I tried
>> looking, but I couldn't find a document.)
>>
>> 1. What is OpenBSD's stance on al
On 07/12/14 09:35, Adam Thompson wrote:
> On 14-12-06 03:20 PM, Riley Baird wrote:
>> Okay, I'll change the name. What I'm wondering is, which mentions of
>> the OpenBSD name should I change? For example, you said before that
>> the OpenBSD name may not be remo
> Not sure what you mean by "throughout the system" -- it's case-by-case.
> If you see a copyright with the OpenBSD.org email address, you keep
> that, per the license. If your end result is clearly not OpenBSD and
> something is referring to the overall product, you SHOULD change it,
> since the
On 07/12/14 01:59, Christian Weisgerber wrote:
> On 2014-12-06, Nick Holland wrote:
>
>>> I have a few questions about OpenBSD's trademark policy.
>>
>> Short answer: follow the license.
>
> The license governs _copyright_. The _trademark_ is a wholly
> different beast.
Exactly correct. Take F
tem would you
require the change in?
3. From other discussions on the mailing list, it seems that the "Puffy"
logo is restricted, so I imagine it would be necessary to change the
default xdm configuration, but nothing else.
Thanks for considering,
Riley Baird
> You didn't mention it, so I'll point out that you need to run
> slowcgi(8) to proxy between FastCGI and CGI scripts.
I just tried running slowcgi(8) and the script worked. Thanks!
> Try this:
>
> ---begin---
> #!/usr/bin/perl
>
> print "Content-Type: text/html\n\n";
> print "Hello!";
> ---end---
I've just done it, and I still get the same error.
r,
http://192.168.1.55/cgi-bin/script.pl simply says "500 Internal Server
Error".
A script as simple as the below brings up this error, but it has been
tested with other scripts:
#!/usr/bin/perl
print "Hello!"
Thanks for reading,
Riley Baird
26 matches
Mail list logo
