I haven't built those projects specifically, but I've had luck building Go
projects on OpenBSD.
I recommend building Go from source. It's quite straightforward. On OpenBSD
5.9, you can install Go from ports, then use that to bootstrap the latest 1.7.3
version. I leave the ports version intac
Thank you and all the people involved in OpenBSD development for
providing me with a system I can trust and rely on!
I am running OpenBSD Current since a few months without any major issues
on my desktop
Greetings
rehcla
On 11/04/16 01:32, Theo de Raadt wrote:
Aren't the snapshots running
On Thu, November 3, 2016 9:52 pm, Chris Huxtable wrote:
> Nothing funky with users in pf. I have tried to strip my pf.conf way back
> in
> an attempt to remove possible issues
> but that hasnâ**t improved anything. I filter by interface, ip, and port,
> thats all (so far).
>
> Nothing odd in dmesg.
Nothing funky with users in pf. I have tried to strip my pf.conf way back in
an attempt to remove possible issues
but that hasn’t improved anything. I filter by interface, ip, and port,
thats all (so far).
Nothing odd in dmesg. What really has me for a loop is why does everything
work except this
> >>Aren't the snapshots running fairly well vetted code anyway - only
> >>using code that's been accepted into the source tree? Obviously not
> >>as well vetted as the -STABLE and -RELEASE, of course.
> >
> > Snapshots are generated as fast as we can, from what is commited.
>
> Doesn't uncommit
On Thu, November 3, 2016 9:19 pm, trondd wrote:
> On Thu, November 3, 2016 9:07 pm, Chris Huxtable wrote:
>> Same as before unfortunately.
>>
>> # pkg_add -v nano
>> Error from http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/
>> ftp: ftp.openbsd.org: no address associated with name
>> htt
My advice: If you really want the performance boost and you think a recent
snapshot will provide it, make sure your backups are good and test the
snapshot on comparable hardware as best you can. I usually restore the dump
to a similar system, then boot from a snapshot bsd.rd and choose "Upgrade",
a
On Thu, November 3, 2016 9:07 pm, Chris Huxtable wrote:
> Same as before unfortunately.
>
> # pkg_add -v nano
> Error from http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/
> ftp: ftp.openbsd.org: no address associated with name
> http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/ is e
Same as before unfortunately.
# pkg_add -v nano
Error from http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/
ftp: ftp.openbsd.org: no address associated with name
http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/ is empty
Error from http://openbsd.cs.toronto.edu/pub/OpenBSD/6.0/packa
That config looks completely rational. Perhaps add -v (or -vv .. -v) to
get more and more verbose error messages and see if something useful pops
up in the verbose output.
On Thu, Nov 3, 2016 at 3:19 PM, Chris Huxtable wrote:
> # cat /etc/pkg.conf
> installpath = http://ftp.openbsd.org/%m/
>
>>Aren't the snapshots running fairly well vetted code anyway - only
>>using code that's been accepted into the source tree? Obviously not
>>as well vetted as the -STABLE and -RELEASE, of course.
>
> Snapshots are generated as fast as we can, from what is commited.
Doesn't uncommitted code occas
>Aren't the snapshots running fairly well vetted code anyway - only
>using code that's been accepted into the source tree? Obviously not
>as well vetted as the -STABLE and -RELEASE, of course.
Snapshots are generated as fast as we can, from what is commited.
What gets commited may contain errors
Aren't the snapshots running fairly well vetted code anyway - only
using code that's been accepted into the source tree? Obviously not
as well vetted as the -STABLE and -RELEASE, of course.
On Fri, Nov 4, 2016 at 1:01 AM, Peter N. M. Hansteen wrote:
> On Thu, Nov 03, 2016 at 01:56:09AM -0400, al
On 11/03/2016 03:36 PM, Stefan Sperling wrote:
> On Thu, Nov 03, 2016 at 03:17:40PM -0400, Marina Brown wrote:
>> Hi All:
>>
>> I have been trying to create an nppp connection across my property -
>> about 100M for one of my friends who lives here. He wants less security
>> than i like behind my fi
On Thu, Nov 03, 2016 at 04:02:50PM -0400, trondd wrote:
>
> You actually have to install OpenBSD into that image. Try -k /bsd.rd first.
>
Ahh, so obvious in retrospect, thank you!
--
Patrik Lundin
# cat /etc/pkg.conf
installpath = http://ftp.openbsd.org/%m/
installpath += http://openbsd.cs.toronto.edu/%m/
installpath += http://athena.caslab.queensu.ca/%m/
# echo $PKG_PATH
PKG_PATH is empty as I use pkg.conf
> On Nov 3, 2016, at 3:43 PM, Ax0n wrote:
>
> Can we see the contents of /etc/pkg
On Thu, November 3, 2016 3:45 pm, Patrik Lundin wrote:
> Hello,
>
> I am trying to start a VMM guest based on the example commands in vmctl(8)
> without luck. The guest is panicking like so:
> ===
> panic: root filesystem has size 0
> ===
>
> Here are the commands I use:
> ===
> # vmctl create disk
Hello,
I am trying to start a VMM guest based on the example commands in vmctl(8)
without luck. The guest is panicking like so:
===
panic: root filesystem has size 0
===
Here are the commands I use:
===
# vmctl create disk.img -s 4.5G
vmctl: imagefile created
# ls -lh disk.img
-rw--- 1 root
Can we see the contents of /etc/pkg.conf and/or your $PKG_PATH variable
from inside root's session?
On Wed, Nov 2, 2016 at 6:48 PM, Chris Huxtable wrote:
> OpenBSD Community,
>
> I upgraded my OpenBSD router from 5.9 to 6.0 by clean install and copied a
> number of my old configs to the new inst
On Thu, Nov 03, 2016 at 03:17:40PM -0400, Marina Brown wrote:
> Hi All:
>
> I have been trying to create an nppp connection across my property -
> about 100M for one of my friends who lives here. He wants less security
> than i like behind my firewall. I have not been able to get OpenBSD to
> rout
Hi All:
I have been trying to create an nppp connection across my property -
about 100M for one of my friends who lives here. He wants less security
than i like behind my firewall. I have not been able to get OpenBSD to
route his connection out of the network. Here are my settings.
# uname -
On 1 November 2016 at 16:46, zack wrote:
> Hi,
>
> I'm running OpenBsd 6.0 instance on AWS using the public AMI. Attached
> EBS volume as /dev/xvda as i found in previous discussion, but it don't
> seems to get detected on the instance, nothing shows up on dmesg nor i
> can't find the new device.
On Thu, Nov 03, 2016 at 01:56:09AM -0400, alexmcwhir...@triadic.us wrote:
> I know, it'll happen when it happens...
>
> I have a few servers that could really use the updated SMP stuff that
> -current has. For some applications it's a night and day difference, but I'm
> not all to comfortable runn
Warning: Feckless opining
This is one of the nicer things about OpennBSD from a syadmin perspective.
The release cycle is predictable, and while you may not get a feature you
want from the core utils in the n+1 next release you can be sure that any
new features have been dogfooded thoroughly and a
If you need a rough estimate, you can add 6 months to the date of the
last release.
2016-11-03 6:56 GMT+01:00 :
> I know, it'll happen when it happens...
>
> I have a few servers that could really use the updated SMP stuff that
> -current has. For some applications it's a night and day difference
25 matches
Mail list logo
