Re: syscall 5 "cpath" continues with octeon

I am really not sure what problem you are facing for sure. I did a few times form scratch and every time it goes without any problems what so ever and I really don't see where your cpath can come from at all. And I see no pledge issue what so ever either. Are you sure that you are actually

Re: letsencrypt && https && openbsd.org = https://www.openbsd.org/

2015-12-13 7:17 GMT+01:00 Delan Azabani : > On Sun, Dec 13, 2015 at 6:28 AM, Kevin Chadwick wrote: >> On a low traffic site it already annoys me that I have to change it >> once per year with startSSL. > > This is what the tooling provided by Let's Encrypt

syscall 5 "cpath" continues with octeon

Hello All, Despite the very helpful reply from Daniel on this thread: http://marc.info/?l=openbsd-misc=14493626054=2 I'm faced with the same message upon accepting the default partition and disk layout: disklabel(19593): syscall 5 "cpath" Abort trap When attempting to use the Octeon

Re: syscall 5 "cpath" continues with octeon

Worst case, delete all partitions (EXCEPT the first one, the FAT one) and use only one, install, test and then redo as you see fit. You can mount your FAT partition and access it right? You do have the bsd.rd file on that FAT partition right? May be your fat partition conflict with one of the

Re: letsencrypt && https && openbsd.org = https://www.openbsd.org/

On Sun, Dec 13, 2015 at 6:28 AM, Kevin Chadwick wrote: > On a low traffic site it already annoys me that I have to change it > once per year with startSSL. This is what the tooling provided by Let's Encrypt is designed to solve. It shouldn't be hard to issue new

Re: Pictures are "blurred" in certain cases after snapshot upgrade (radeonrdrm related?)

Problem solved [1]. Thanks jsd@ [1]: https://www.marc.info/?l=openbsd-tech=144984739021388=2 On 12/11/15 16:19, Alexis de BRUYN wrote: Hi Everybody, After upgraded from snapshots/amd64 12/09/2015 (previous was 12/04/2015), Puffy is blurred on xdm login screen (like [1]). Puffy

Re: 8-Port Serial Port Card

On 2015-12-07 Mon 21:30 PM |, Jordon wrote: > I recently picked up a few PCI serial port cards from the junk pile at > work. My intent is to put one in my soon-to-be-retired Soekris net5501 > and install OpenBSD on it to turn it into an 8 port terminal switch. > > I tried the cards in a

Re: ld.so behavior with $ORIGIN

> How did people get by without needing this in the last three decades? Just trying to be positive on a feature that would have interest for me. Nevermind. It seems like most other unixes out there do have a way to retrieve the full path of a running program, mainly through /proc (be it

Re: letsencrypt && https && openbsd.org = https://www.openbsd.org/

On Sat, Dec 12, 2015 at 7:11 PM, Constantine A. Murenin wrote: > once you give in to https once, you're hooked You're only hooked if you use HSTS. > and have to keep paying someone every year, There are at least three CAs that provide free certificates, and one of those is

Re: letsencrypt && https && openbsd.org = https://www.openbsd.org/

On 11 December 2015 at 03:58, Kamil Cholewiński wrote: >> The official CD set contains the signify keys for that release and the >> next one. Once you have a known good copy of one set, you can always obtain >> future ones securely. >> >> You don't even need to use the CD

Re: ld.so behavior with $ORIGIN

On Sat, Dec 12, 2015 at 6:34 AM, Aurélien Vallée wrote: > It seems like most other unixes out there do have a way to retrieve the full > path of a running program, mainly through /proc (be it /proc/pid/exe on > Linux, or /proc/pid/path/a.out on Solaris (TBV). An issue,

Re: ld.so behavior with $ORIGIN

> I asked a question, and you didn't answer it. I did my best to try to find this out, but all I was able to dig are these release notes of ELF gABI. I will try to find how that was supposed to be solved at the time, but I fear these details are lost in time, and not available on much online

Re: ld.so behavior with $ORIGIN

>> It seems like most other unixes out there do have a way to retrieve the full >> path of a running program, mainly through /proc (be it /proc/pid/exe on >> Linux, or /proc/pid/path/a.out on Solaris (TBV). > An issue, though, is that this path does not have to refer to a file > which has

/bsd: athn0: device timeout

I own a Compex WLE200NX Atheros AR9280 Minipci-express Wlan Card and use it in hostap-mode. Every 10 minutes i get the following error: /bsd: athn0: device timeout The Wlan connections and all radio/video streaming stopps. Then i do manually a "sh /etc/netstart athn0" and the radio/video

Re: letsencrypt && https && openbsd.org = https://www.openbsd.org/

Thus said Tati Chevron on Fri, 11 Dec 2015 13:16:23 +: > On the other hand, if somebody actually received a fake OpenBSD CD in > the mail, and it was discovered, it would be a huge news story within > the IT industry. A bad download, much less so. My OpenBSD 5.7 CD arrived with a green

Re: Wireless connection mystery two OpenBSD machines suddenly cannot connect

from the command line ifconfig down I think this resets the device IIRC ifconfig up nwid wpakey At this point you should within a few seconds get an associated conneciton - if not there's another problem. On my thinkpad the little antenna light blinks then stays on constant when

Re: Wireless connection mystery two OpenBSD machines suddenly cannot connect

Carl Trachte wrote: from the command line ifconfig down I think this resets the device IIRC Mystery solved. The $3 transformer for the DSL modem is dying. If I unplug it and let it cool off everything works again :) Off to buy a new $3 transformer :) Thanks Carl and Unixreader for

Wireless connection mystery two OpenBSD machines suddenly cannot connect

I have two very different laptops running OpenBSD 5.8 with all patches. Both were connected to my home wireless via very simple hostname files: nwid foo wpakey bar dhcp Both stopped connecting today .. no link (sleeping). Both see the station via ifconfig scan with reasonable dB

Re: 8-Port Serial Port Card

On Sat, Dec 12, 2015 at 09:54:39AM +, Craig Skinner wrote: >On 2015-12-07 Mon 21:30 PM |, Jordon wrote: >> I recently picked up a few PCI serial port cards from the junk pile at >> work. My intent is to put one in my soon-to-be-retired Soekris net5501 >> and install OpenBSD on it to turn it

Re: letsencrypt && https && openbsd.org = https://www.openbsd.org/

> > and have to keep changing the cert every year. > > Your certificate cycling process should be automated, and it should > happen more frequently than once a year. Complete nonsense firstly and not a major point but you may have greater security than automating key changes and secondly the

Re: OpenBSD on GitHub

On Sun, Aug 05, 2012 at 05:35:47PM -0400, Kenneth R Westerback wrote: > On Sun, Aug 05, 2012 at 03:00:04PM -0400, Ted Unangst wrote: > > On Sun, Aug 05, 2012 at 10:46, Darrin Chandler wrote: > > > On Sat, Aug 04, 2012 at 07:05:38PM +0200, Marc Espie wrote: > > >> Well, git just has a different set

Re: ld.so behavior with $ORIGIN

Just as an update: I just spent some time reading NetBSD source code to understand how they are doing it. They seem to do exactly what Philip suggested: pack the execname from kern_exec in the elf auxiliary vector, and dirname() that on ld.so. On Sat, Dec 12, 2015 at 4:08 PM, Aurélien Vallée

Re: letsencrypt && https && openbsd.org = https://www.openbsd.org/

> > I would consider signify keys printed on CDs and copied across several > > web sites safer than trusting the hundreds of CA certs shipped with a > > standard web browser. > > Didn't we just established that with HPKP you can disregard the CA > completely? At least if you trust your fist