The path it's showing you in the installer says 'pub/OpenBSD/6.0/amd64'.
You have to change that to 'pub/OpenBSD/snapshots/amd64'. Official
release of 6.0 is expected September 1.
On 27 July 2016 at 18:25, Antonis Psaras wrote:
> I tried 2nd method using bsd.rd to
> On 27 Jul 2016, at 19:52, Florian Obser wrote:
>
> On Wed, Jul 27, 2016 at 07:34:32PM +0200, thoma...@twelveletter.com wrote:
>>> Synopsis: Man page for hostname.if contains outdated IPv6 autoconf
>>> information
>>> Category: documentation
>>> Environment:
>>
On Wed, Jul 27, 2016 at 07:34:32PM +0200, thoma...@twelveletter.com wrote:
> >Synopsis:Man page for hostname.if contains outdated IPv6 autoconf
> >information
> >Category:documentation
> >Environment:
> System : OpenBSD 6.0
> Details : OpenBSD 6.0 (GENERIC.MP) #3: Wed
>Synopsis: Man page for hostname.if contains outdated IPv6 autoconf
>information
>Category: documentation
>Environment:
System : OpenBSD 6.0
Details : OpenBSD 6.0 (GENERIC.MP) #3: Wed Jul 27 16:35:50 CEST 2016
I tried 2nd method using bsd.rd to update the system but I get an error message
stating that cannot find OpenBSD/amd64 6.0 sets.
Path is correct, I crossed check that.
When 6.0 is expected?
Regards
From: Mike Belopuhov [mailto:m...@belopuhov.com]
Sent: Wednesday, July 27, 2016
Antonis,
You need to grab the files from 'snapshots/amd64' instead
of the release directory, e.g. from here:
http://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/amd64/
And then either:
1) reinstall the system (i'd say it's easier to do that)
2) if you have access to the console, put new bsd.rd
> On Wed, Jul 27, 2016 at 09:42:23AM -0400, Raul Miller wrote:
> > On Wed, Jul 27, 2016 at 8:00 AM, Paul Fariello wrote:
> > > Ok. I didn't notice that relayd had a security filtering focus. If so,
> > > enforcing presence/absence of body is legit.
> >
> > Perhaps the
Hello Mike
Thank you for your quick response.
The problem is totally random and probably has to do with traffic on the
interface. Never the less, the problem always produce the problem on xnf0 which
is one of the Wan interfaces I have and never on xnf1 which is the LAN
interface or
Hi Raul,
On Wed, Jul 27, 2016 at 09:42:23AM -0400, Raul Miller wrote:
> On Wed, Jul 27, 2016 at 8:00 AM, Paul Fariello wrote:
> > Ok. I didn't notice that relayd had a security filtering focus. If so,
> > enforcing presence/absence of body is legit.
>
> Perhaps the
On Wed, Jul 27, 2016 at 8:00 AM, Paul Fariello wrote:
> Ok. I didn't notice that relayd had a security filtering focus. If so,
> enforcing presence/absence of body is legit.
Perhaps the security.html page on the openbsd site would interest you?
Did you know, for example, that
On Wed, Jul 27, 2016 at 01:31:28PM +0200, Reyk Floeter wrote:
>
> > On 27.07.2016, at 12:41, Paul Fariello wrote:
> >
> > On Wed, Jul 27, 2016 at 12:18:06PM +0200, Reyk Floeter wrote:
> >>
> >> What are you trying to do - removing this logic is obviously not how it
> >> was
> On 27.07.2016, at 12:41, Paul Fariello wrote:
>
> On Wed, Jul 27, 2016 at 12:18:06PM +0200, Reyk Floeter wrote:
>>
>> What are you trying to do - removing this logic is obviously not how it was
>> intended.
>> I think you shouldn't send superfluous diffs.
>
> I'm just
On Wed, Jul 27, 2016 at 12:46:56PM +0200, Michael Lechtermann wrote:
>
> > On 27Juli, 2016, at 12:26, Reyk Floeter wrote:
> >
> > better?
>
> Yes, I could apply the patch now, however I had to make one additional
> change. Now SVN appears to be working again.
>
> # diff -u
Great, yes, this OPTIONS change is correct.
Background: OPTIONS didn't have a body in the past, but RFC 7231 mentions that
it may have one for "future extensions". So the future is here…
btw., even Wikipedia interpreted it incorrectly as "No", I fixed it to
"Optional":
> On 27Juli, 2016, at 12:26, Reyk Floeter wrote:
>
> better?
Yes, I could apply the patch now, however I had to make one additional change.
Now SVN appears to be working again.
# diff -u relay_http.c.orig relay_http.c
--- relay_http.c.orig Wed Jul 27 10:43:22 2016
+++
On Wed, Jul 27, 2016 at 12:18:06PM +0200, Reyk Floeter wrote:
>
> What are you trying to do - removing this logic is obviously not how it was
> intended.
> I think you shouldn't send superfluous diffs.
I'm just trying to help. Maybe it's the wrong mailing list for such mail
exchanges. Should I
> On 27.07.2016, at 12:21, Michael Lechtermann wrote:
>
>> I once added the well-known webdav methods to httpd, the attached diff
>> syncs it to relayd. Could you give it a try?
>
> Thanks Reyk, looks like something isn’t right there…
>
> # patch -p0 < 1.patch
> Hmm...
> I once added the well-known webdav methods to httpd, the attached diff
> syncs it to relayd. Could you give it a try?
Thanks Reyk, looks like something isn’t right there…
# patch -p0 < 1.patch
Hmm... Looks like a unified diff to me...
The text leading up to this was:
> On 27.07.2016, at 12:05, Paul Fariello wrote:
>
> On Wed, Jul 27, 2016 at 11:26:28AM +0200, Paul Fariello wrote:
>> On Wed, Jul 27, 2016 at 11:08:17AM +0200, Michael Lechtermann wrote:
>>>
On 27Juli, 2016, at 10:19, Paul Fariello wrote:
On Wed, Jul 27, 2016 at 11:26:28AM +0200, Paul Fariello wrote:
> On Wed, Jul 27, 2016 at 11:08:17AM +0200, Michael Lechtermann wrote:
> >
> > > On 27Juli, 2016, at 10:19, Paul Fariello wrote:
> > >
> > > relayd logs and svn server log could really help.
> > >
> > > I can't
Hi Antonis,
While your report could have been a bit more detailed (for instance
describing how did you get into this situation), I'm aware of the
generic problem with failed interrupt delivery that can be triggered
under heavy network load, e.g. packet flood. I'm trying to fix this
right now.
On Fri, Jun 24, 2016 at 10:21:16AM +0200, Michael Lechtermann wrote:
> Hi,
>
> I have recently configured relayd as SSL accelerator and it is working really
> great. However it seems that not all http methods that are mentioned in the
> man page are actually supported by the http protocol.
>
>
On Wed, Jul 27, 2016 at 11:08:17AM +0200, Michael Lechtermann wrote:
>
> > On 27Juli, 2016, at 10:19, Paul Fariello wrote:
> >
> > relayd logs and svn server log could really help.
> >
> > I can't reproduce it since I don't have a working svn server.
>
> relayd doesn’t print
> On 27Juli, 2016, at 10:19, Paul Fariello wrote:
>
> relayd logs and svn server log could really help.
>
> I can't reproduce it since I don't have a working svn server.
relayd doesn’t print out anything in regards to this, even when using -d and
multiple -v
Apache also
On Tue, Jul 26, 2016 at 02:29:26PM +0200, Michael Lechtermann wrote:
> Hu Paul,
>
> the attached patch doesn't change anything for me. WebDAV still isn't working
> through relayd.
>
> # svn up
> svn: Server sent unexpected return value (400 Bad Request) in response to
> OPTIONS request for
> On 27Juli, 2016, at 09:55, Paul Fariello wrote:
>
> Do you have some logs from relayd ?
relayd is running with “-v”, but there is no log output regarding the failed
http OPTIONS.
-Michael
On Wed, Jul 27, 2016 at 10:01:43AM +0200, Stefan Sperling wrote:
> On Wed, Jul 27, 2016 at 09:55:24AM +0200, Paul Fariello wrote:
> > Do you know which http method svn is using ?
>
> See https://svn.apache.org/repos/asf/subversion/trunk/notes/http-and-webdav
Thanks for the reference.
--
Paul
On Wed, Jul 27, 2016 at 09:55:24AM +0200, Paul Fariello wrote:
> Do you know which http method svn is using ?
See https://svn.apache.org/repos/asf/subversion/trunk/notes/http-and-webdav
Hi Michael,
Do you know which http method svn is using ?
Do you have some logs from relayd ?
Regards,
Paul
On Tue, Jul 26, 2016 at 02:29:26PM +0200, Michael Lechtermann wrote:
> Hu Paul,
>
> the attached patch doesn't change anything for me. WebDAV still isn't working
> through relayd.
>
> #
Hello
I have installed OpenBSD 5.9 amd64 on XenServer 6.5 with all patches up to
The problem I have is that the xnf interfaces are getting unresponsive.
Console through XenCenter interface is working fine but some (not all) xnf
interface are not.
Console output
Strange thing
30 matches
Mail list logo