Re: DMCA Free OpenBSD VPS Hosting, multiple payment methods

2017-10-18 Thread Christoph R. Murauer
FYI : 1984.is provides in the settings of the VPS OpenBSD 5.9 and 6.1.

> Thanks Ajitabh, Christoph
>
> will give a try with the small island.
>
> cheers.
>
> x9p
>
>
>> As already recommanded in another post www.1984.is They are located
>> in
>> Reykjavík / Iceland. I had in the past a OpenBSD VPS there (now
>> shared
>> hosting but maybe again a VPS). They provide by default Ubuntu /
>> Debian but you also could use .ISO's. Drop them a mail about the
>> .ISO's, they are friendly but thats are Debian people and they are
>> unexperienced about OpenBSD - as they host using Debian / KVM.
>>
>> Remember, it is a island and sometimes they are not reachable  or
>> slow
>> (based on my location).
>>
>
>




Re: awk in OpenBSD

2017-10-18 Thread Adam Steen
I would guess the latest update Dec, 2012, doesn't off any worth upgrading for,

[1]
Dec 20, 2012:
fiddled makefile to get correct yacc and bison flags. pick yacc
(linux) or bison (mac) as necessary.
added __attribute__((__noreturn__)) to a couple of lines in
proto.h, to silence someone's enthusiastic checker.
fixed obscure call by value bug in split(a[1],a) reported on
9fans. the management of temporary values is just a mess; i
took a shortcut by making an extra string copy. thanks
to paul patience and arnold robbins for passing it on and for
proposed patches.
tiny fiddle in setfval to eliminate -0 results in T.expr, which
has irritated me for 20+ years.

[1] 
https://github.com/danfuzz/one-true-awk/blob/master/versions/2012-12-20/FIXES

On Thu, Oct 19, 2017 at 1:14 PM, Niels Kobschaetzki
 wrote:
>
>> On 19. Oct 2017, at 06:23, flipchan  wrote:
>>
>> Yeah blindly follow the flow of the others , DONT THINK SO
>
> That doesn’t explain the reasoning WHY the newer awk is not used.
>
>>> On October 19, 2017 4:25:09 AM GMT+02:00, Andras Farkas 
>>>  wrote:
>>> On the 6.2 release page, and confirmed in the source code, one can see
>>> The system includes the following major components from outside
>>> suppliers:
>>> Awk Aug 10, 2011 version
>>> This turns out to be one release behind upstream, where the latest
>>> release is from December 20 2012: a quick check shows that
>>> DragonFlyBSD, FreeBSD, and NetBSD all use this version.
>>>
>>> Just out of curiosity, is there a reason why OpenBSD uses the 2011
>>> release?
>
> Niels



Re: awk in OpenBSD

2017-10-18 Thread Theo de Raadt

i'm watching a bunch of losers who argue before running diff


> You didn't really make a great case for the newer awk, either. Is there a
> good reason to use the 2012 release from upstream? If so, you could submit
> a diff and explain the benefits.
> 
> On Oct 19, 2017 12:15 AM, "Niels Kobschaetzki" 
> wrote:
> 
> 
> > On 19. Oct 2017, at 06:23, flipchan  wrote:
> >
> > Yeah blindly follow the flow of the others , DONT THINK SO
> 
> That doesn=E2=80=99t explain the reasoning WHY the newer awk is not used.
> 
> >> On October 19, 2017 4:25:09 AM GMT+02:00, Andras Farkas <
> deepbluemist...@gmail.com> wrote:
> >> On the 6.2 release page, and confirmed in the source code, one can see
> >> The system includes the following major components from outside
> >> suppliers:
> >> Awk Aug 10, 2011 version
> >> This turns out to be one release behind upstream, where the latest
> >> release is from December 20 2012: a quick check shows that
> >> DragonFlyBSD, FreeBSD, and NetBSD all use this version.
> >>
> >> Just out of curiosity, is there a reason why OpenBSD uses the 2011
> >> release?
> 
> Niels



Re: awk in OpenBSD

2017-10-18 Thread Ax0n
You didn't really make a great case for the newer awk, either. Is there a
good reason to use the 2012 release from upstream? If so, you could submit
a diff and explain the benefits.

On Oct 19, 2017 12:15 AM, "Niels Kobschaetzki" 
wrote:


> On 19. Oct 2017, at 06:23, flipchan  wrote:
>
> Yeah blindly follow the flow of the others , DONT THINK SO

That doesn’t explain the reasoning WHY the newer awk is not used.

>> On October 19, 2017 4:25:09 AM GMT+02:00, Andras Farkas <
deepbluemist...@gmail.com> wrote:
>> On the 6.2 release page, and confirmed in the source code, one can see
>> The system includes the following major components from outside
>> suppliers:
>> Awk Aug 10, 2011 version
>> This turns out to be one release behind upstream, where the latest
>> release is from December 20 2012: a quick check shows that
>> DragonFlyBSD, FreeBSD, and NetBSD all use this version.
>>
>> Just out of curiosity, is there a reason why OpenBSD uses the 2011
>> release?

Niels


Re: awk in OpenBSD

2017-10-18 Thread Niels Kobschaetzki

> On 19. Oct 2017, at 06:23, flipchan  wrote:
> 
> Yeah blindly follow the flow of the others , DONT THINK SO

That doesn’t explain the reasoning WHY the newer awk is not used. 

>> On October 19, 2017 4:25:09 AM GMT+02:00, Andras Farkas 
>>  wrote:
>> On the 6.2 release page, and confirmed in the source code, one can see
>> The system includes the following major components from outside
>> suppliers:
>> Awk Aug 10, 2011 version
>> This turns out to be one release behind upstream, where the latest
>> release is from December 20 2012: a quick check shows that
>> DragonFlyBSD, FreeBSD, and NetBSD all use this version.
>> 
>> Just out of curiosity, is there a reason why OpenBSD uses the 2011
>> release?

Niels


PostgREST post in OpenBSD

2017-10-18 Thread Tito Mari Francis Escaño
Hi everyone! I'd like to ask if somebody already tried or is working
on a port of PostgREST (https://github.com/begriffs/postgrest) in
OpenBSD. It has a working FreeBSD port but of course I prefer it
running on arguably the most secure OS on the planet.
I'm not confident I can make a port on my VM hosting OBSD, anybody
tried this approach before?
Thanks in advance.



Re: awk in OpenBSD

2017-10-18 Thread flipchan
Yeah blindly follow the flow of the others , DONT THINK SO

On October 19, 2017 4:25:09 AM GMT+02:00, Andras Farkas 
 wrote:
>On the 6.2 release page, and confirmed in the source code, one can see
>The system includes the following major components from outside
>suppliers:
>Awk Aug 10, 2011 version
>This turns out to be one release behind upstream, where the latest
>release is from December 20 2012: a quick check shows that
>DragonFlyBSD, FreeBSD, and NetBSD all use this version.
>
>Just out of curiosity, is there a reason why OpenBSD uses the 2011
>release?

-- 
Take Care Sincerely flipchan layerprox dev

Re: atascsi_passthru_done, timeout

2017-10-18 Thread Predrag Punosevac
On Tue, Jun 27, 2017 at 2:19 PM, Jan Stary  wrote:
> This is current/amd64 (dmesg below).
> After installing smartmontools and running
> /usr/local/sbin/smartctl -t short /dev/sd0c
> in rc.local I get a log of
> 
> atascsi_passthru_done, timeout
> 
> in /var/log/messages. Is this anything to worry about?
> 
> Jan

It seems that this is still an issue 

# uname -a
OpenBSD oko.bagdala2.net 6.2 GENERIC.MP#0 amd64
# dmesg|tail -10
atascsi_passthru_done, timeout
atascsi_passthru_done, timeout
atascsi_passthru_done, timeout
atascsi_passthru_done, timeout
atascsi_passthru_done, timeout
atascsi_passthru_done, timeout
atascsi_passthru_done, timeout
atascsi_passthru_done, timeout
atascsi_passthru_done, timeout
atascsi_passthru_done, timeout



Can I specify the location of core dumps, e.g. "/var/crash/YYYY-MM-DD-processname.dateidx" or similar? (A general variant of the kern.nosuidcoredump=2 sysctl.)

2017-10-18 Thread tinkr
Hi,

Can I specify the location of core dumps?

So like, a general variant of the kern.nosuidcoredump=2 sysctl.

Having them in /var/crash/ could be a useful way to track crashes in any 
programs, maybe.

Ideally I'd like to provide a template string or via other option specify so 
coredumps would become "/var/crash/-MM-DD-processname.dateidx" or 
"/var/crash/-MM-DD-HH:MM:SS-processname.subsecondidx". The index would show 
the index of crash within the time period of that day or second.

(A separate question about userland trigger of unhandled SIGSEGV event in 
separate email.)

Tinker

Re: bioctl and S.M.A.R.T support for physical disks

2017-10-18 Thread Predrag Punosevac
smartctl -i  /dev/sd0c 

works for me as well. I would like to thank all of you who helped on and
off the list.

Predrag



awk in OpenBSD

2017-10-18 Thread Andras Farkas
On the 6.2 release page, and confirmed in the source code, one can see
The system includes the following major components from outside suppliers:
Awk Aug 10, 2011 version
This turns out to be one release behind upstream, where the latest
release is from December 20 2012: a quick check shows that
DragonFlyBSD, FreeBSD, and NetBSD all use this version.

Just out of curiosity, is there a reason why OpenBSD uses the 2011 release?



Re: Install process: couple of comments

2017-10-18 Thread Limaunion

On 10/18/2017 09:02 PM, trondd wrote:

On Wed, October 18, 2017 6:15 pm, Limaunion wrote:

On 10/17/2017 05:44 PM, Stuart Henderson wrote:

On 2017-10-16, Limaunion  wrote:

Hi! Last friday I upgraded my ALIX system from 6.0 to 6.2 using the PXE
boot method. In previous years I used an internal FTP server to perform
the upgrade, but for some reason this is not supported any more since a
couple of releases.


ftp support was removed from the installer, but you can place the same
files on an http/https server instead.


I mounted and published the ISO image using a
raspberrypi and NGINX (HTTP method). During the install process I hit
the following error 'unable to get a verified list of distribution
sets'(*). I couldn't find much help from google but after some time I
figured out that the install was looking for a file named index.txt,
that is not included in the ISO.


you want nearly all of the files from the release directory on a mirror,
you can skip install*.fs / install*.iso.


Maybe some of this information can be included to the install guide for
those of us doing a local HTTP upgrade, and also it would be great to
have the index.txt file included in the ISO.


you won't have the SHA256.sig to verify the files against the signify
signature in the iso either.


For the record, the kernel relinking (Relinking to create unique
kernel...) took about 14 minutes in my ALIX board and it takes about
2.5
minutes the library reordering during the boot process.


yes, it's terribly slow on machines with slow storage devices.
I tend to disable it on those (until I can justify replacing the
machine with something newer, which has other advantages too).





Hi! you mean that the library reordering can be disabled? care to share
how to do that? google didn't help...
Thanks for your comments.



Why does everyone always go straight to google? (Yeah, I know, silly
question.)  And then give up?

Looking at the code might be a better start.  Line 163 is particularly
interesting...

http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/etc/rc?annotate=1.519




Got it, thanks!



Re: Install process: couple of comments

2017-10-18 Thread trondd
On Wed, October 18, 2017 6:15 pm, Limaunion wrote:
> On 10/17/2017 05:44 PM, Stuart Henderson wrote:
>> On 2017-10-16, Limaunion  wrote:
>>> Hi! Last friday I upgraded my ALIX system from 6.0 to 6.2 using the PXE
>>> boot method. In previous years I used an internal FTP server to perform
>>> the upgrade, but for some reason this is not supported any more since a
>>> couple of releases.
>>
>> ftp support was removed from the installer, but you can place the same
>> files on an http/https server instead.
>>
>>> I mounted and published the ISO image using a
>>> raspberrypi and NGINX (HTTP method). During the install process I hit
>>> the following error 'unable to get a verified list of distribution
>>> sets'(*). I couldn't find much help from google but after some time I
>>> figured out that the install was looking for a file named index.txt,
>>> that is not included in the ISO.
>>
>> you want nearly all of the files from the release directory on a mirror,
>> you can skip install*.fs / install*.iso.
>>
>>> Maybe some of this information can be included to the install guide for
>>> those of us doing a local HTTP upgrade, and also it would be great to
>>> have the index.txt file included in the ISO.
>>
>> you won't have the SHA256.sig to verify the files against the signify
>> signature in the iso either.
>>
>>> For the record, the kernel relinking (Relinking to create unique
>>> kernel...) took about 14 minutes in my ALIX board and it takes about
>>> 2.5
>>> minutes the library reordering during the boot process.
>>
>> yes, it's terribly slow on machines with slow storage devices.
>> I tend to disable it on those (until I can justify replacing the
>> machine with something newer, which has other advantages too).
>>
>>
>>
>
> Hi! you mean that the library reordering can be disabled? care to share
> how to do that? google didn't help...
> Thanks for your comments.
>

Why does everyone always go straight to google? (Yeah, I know, silly
question.)  And then give up?

Looking at the code might be a better start.  Line 163 is particularly
interesting...

http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/etc/rc?annotate=1.519



Re: Install process: couple of comments

2017-10-18 Thread Limaunion

On 10/17/2017 05:44 PM, Stuart Henderson wrote:

On 2017-10-16, Limaunion  wrote:

Hi! Last friday I upgraded my ALIX system from 6.0 to 6.2 using the PXE
boot method. In previous years I used an internal FTP server to perform
the upgrade, but for some reason this is not supported any more since a
couple of releases.


ftp support was removed from the installer, but you can place the same
files on an http/https server instead.


I mounted and published the ISO image using a
raspberrypi and NGINX (HTTP method). During the install process I hit
the following error 'unable to get a verified list of distribution
sets'(*). I couldn't find much help from google but after some time I
figured out that the install was looking for a file named index.txt,
that is not included in the ISO.


you want nearly all of the files from the release directory on a mirror,
you can skip install*.fs / install*.iso.


Maybe some of this information can be included to the install guide for
those of us doing a local HTTP upgrade, and also it would be great to
have the index.txt file included in the ISO.


you won't have the SHA256.sig to verify the files against the signify
signature in the iso either.


For the record, the kernel relinking (Relinking to create unique
kernel...) took about 14 minutes in my ALIX board and it takes about 2.5
minutes the library reordering during the boot process.


yes, it's terribly slow on machines with slow storage devices.
I tend to disable it on those (until I can justify replacing the
machine with something newer, which has other advantages too).





Hi! you mean that the library reordering can be disabled? care to share 
how to do that? google didn't help...

Thanks for your comments.



Re: Guess what today is

2017-10-18 Thread jin
Happy birthday OpenBSD

On 18 Oct 2017 1:17 p.m., "STeve Andre'"  wrote:

> Happy birthday to OpenBSD--22 years old!
>
>


Re: Guess what today is

2017-10-18 Thread Lampshade
Happy birthday and live long OpenBSD!



Re: macppc netboot

2017-10-18 Thread Christian Weisgerber
On 2017-10-18, Solène Rapenne  wrote:

> Are you able to fetch /bsd.rd if you use tftp in command line ?

How is this relevant?

Netbooting is inherently machine-dependent.  Firmware aside, there
are also at least two OpenBSD bootloader flavors:
* pxeboot (amd64, i386) uses TFTP to load the kernel.
* netboot (alpha) and ofwboot.net (sparc64) load the kernel from
  an NFS server.

Looking at INSTALL.macppc, I see that macppc's ofwboot works along
the lines of alpha and sparc64.  If you are trying to give advice
based on amd64/i386, then this will be bogus and misleading.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de



Re: vmd: alpine-virt guest, clock synchronization issue

2017-10-18 Thread Mike Larkin
On Wed, Oct 18, 2017 at 12:07:16PM -0700, Mike Larkin wrote:
> On Sat, Oct 14, 2017 at 01:31:28PM -0600, Shane Harbour wrote:
> > On 10/14/2017 13:01, x9p wrote:
> > > Hi,
> > > 
> > > While running Alpine-virt 3.6.2 VM guest under OpenBSD 6.1 host, i noticed
> > > the clock frequency is 2x slower on the guest machine. This can be a
> > > problem for applications that relies on accurate time.
> > > 
> > > Even after sync clock with ntpd inside alpine-virt guest, it gets
> > > out-of-sync a few seconds later. I get on the guest about half the clock
> > > frequency of the host.
> > > 
> > > Anyone having similar problems?
> > > 
> > > cheers.
> > > 
> > > x9p
> > > 
> > 
> > I've noticed the same thing on my laptop running an amd64 6.2 install. It
> > was really very slow to install and slow via console and ssh now that I've
> > got it running.  I just thought it was something I had done/was doing.  Even
> > with ntpd running, it's now way behind.
> > 
> > Regards,
> > Shane
> > 
> 
> You should be able to set the timecounter source to 'tsc' in VMs running in
> -current. It is not the default choice (so set it in sysctl.conf if you want
> that). That should greatly help reduce time drifts.
> 
> You will really need -current though as the fix for this went in today.
> 
> -ml

To be super clear - you need -current on both the host and VM.

-ml



Re: vmd: alpine-virt guest, clock synchronization issue

2017-10-18 Thread x9p
Will update soon and try the fix.

Thanks for the hard work on vmm, ml.

cheers.

x9p

> On Sat, Oct 14, 2017 at 01:31:28PM -0600, Shane Harbour wrote:
>> On 10/14/2017 13:01, x9p wrote:
>> > Hi,
>> >
>> > While running Alpine-virt 3.6.2 VM guest under OpenBSD 6.1 host, i
>> noticed
>> > the clock frequency is 2x slower on the guest machine. This can be a
>> > problem for applications that relies on accurate time.
>> >
>> > Even after sync clock with ntpd inside alpine-virt guest, it gets
>> > out-of-sync a few seconds later. I get on the guest about half the
>> clock
>> > frequency of the host.
>> >
>> > Anyone having similar problems?
>> >
>> > cheers.
>> >
>> > x9p
>> >
>>
>> I've noticed the same thing on my laptop running an amd64 6.2 install.
>> It
>> was really very slow to install and slow via console and ssh now that
>> I've
>> got it running.  I just thought it was something I had done/was doing.
>> Even
>> with ntpd running, it's now way behind.
>>
>> Regards,
>> Shane
>>
>
> You should be able to set the timecounter source to 'tsc' in VMs running
> in
> -current. It is not the default choice (so set it in sysctl.conf if you
> want
> that). That should greatly help reduce time drifts.
>
> You will really need -current though as the fix for this went in today.
>
> -ml
>
>




Re: macppc netboot

2017-10-18 Thread Solène Rapenne

Je 2017-10-18 16:39, Daniel Boyd skribis:

OK -- from dhcpd.conf:

host cube {
next-server 192.168.60.157;
option subnet-mask 255.255.255.0;
option routers 192.168.60.1;
option root-path "/srv/obsd62";
fixed-address 192.168.60.235;
hardware ethernet 00:30:65:71:c6:e2;
}

And then in OF:
0 > boot enet:,ofwboot /bsd.rd
CLIENT: 003065571c6e2 192.168.60.235
SERVER: f 192.168.60.157
ROUTER: f 192.168.60.1
Transfer FILE: ofwboot \
TFTP-actual=fcbc TFTP-adler32=c626975c load-size=fcbc adler32=c626975c

Loading ELF

OpenBSD/macppc BOOT 1.6

Using IP address: 192.168.60.235
root addr=192.168.60.157 path=/srv/obsd62
callrpc: error = 2
open(/pci@f400/ethernet:/etc/boot.conf): Unknown error: code 72
boot>
Using IP address 192.168.60.235
root addr=192.168.60.157 path=/srv/obsd62
callrpc: error = 2
cannot open /pci@f400/ethernet:/etc/random.seed: Unknown error:
code 72
booting /pci@f400/ethernet:/bsd.rd Using IP address: 192.168.60.235
root addr=192.168.60.157 path=/srv/obsd62
callrcp: error = 2
open /pci@f400/ethernet:/bsd.rd: Unknown error: code 72
 failed(72). will try /bsd
...

So... DHCP is working... TFTP is working.  I just don't think NFS is
working.  I'm able to mount the nfs share on another computer, so, i'm
kind of out of ideas...

On Wed, 2017-10-18 at 14:50 +0200, Solène Rapenne wrote:


Are you able to fetch /bsd.rd if you use tftp in command line ?



Re: vmd: alpine-virt guest, clock synchronization issue

2017-10-18 Thread Mike Larkin
On Sat, Oct 14, 2017 at 01:31:28PM -0600, Shane Harbour wrote:
> On 10/14/2017 13:01, x9p wrote:
> > Hi,
> > 
> > While running Alpine-virt 3.6.2 VM guest under OpenBSD 6.1 host, i noticed
> > the clock frequency is 2x slower on the guest machine. This can be a
> > problem for applications that relies on accurate time.
> > 
> > Even after sync clock with ntpd inside alpine-virt guest, it gets
> > out-of-sync a few seconds later. I get on the guest about half the clock
> > frequency of the host.
> > 
> > Anyone having similar problems?
> > 
> > cheers.
> > 
> > x9p
> > 
> 
> I've noticed the same thing on my laptop running an amd64 6.2 install. It
> was really very slow to install and slow via console and ssh now that I've
> got it running.  I just thought it was something I had done/was doing.  Even
> with ntpd running, it's now way behind.
> 
> Regards,
> Shane
> 

You should be able to set the timecounter source to 'tsc' in VMs running in
-current. It is not the default choice (so set it in sysctl.conf if you want
that). That should greatly help reduce time drifts.

You will really need -current though as the fix for this went in today.

-ml



Re: macppc netboot

2017-10-18 Thread Daniel Boyd
OK -- from dhcpd.conf:

host cube {
next-server 192.168.60.157;
option subnet-mask 255.255.255.0;
option routers 192.168.60.1;
option root-path "/srv/obsd62";
fixed-address 192.168.60.235;
hardware ethernet 00:30:65:71:c6:e2;
}

And then in OF:
0 > boot enet:,ofwboot /bsd.rd
CLIENT: 003065571c6e2 192.168.60.235
SERVER: f 192.168.60.157
ROUTER: f 192.168.60.1
Transfer FILE: ofwboot \
TFTP-actual=fcbc TFTP-adler32=c626975c load-size=fcbc adler32=c626975c

Loading ELF
>> OpenBSD/macppc BOOT 1.6
Using IP address: 192.168.60.235
root addr=192.168.60.157 path=/srv/obsd62
callrpc: error = 2
open(/pci@f400/ethernet:/etc/boot.conf): Unknown error: code 72
boot>
Using IP address 192.168.60.235
root addr=192.168.60.157 path=/srv/obsd62
callrpc: error = 2
cannot open /pci@f400/ethernet:/etc/random.seed: Unknown error:
code 72
booting /pci@f400/ethernet:/bsd.rd Using IP address: 192.168.60.235
root addr=192.168.60.157 path=/srv/obsd62
callrcp: error = 2
open /pci@f400/ethernet:/bsd.rd: Unknown error: code 72
 failed(72). will try /bsd
...

So... DHCP is working... TFTP is working.  I just don't think NFS is
working.  I'm able to mount the nfs share on another computer, so, i'm
kind of out of ideas...

On Wed, 2017-10-18 at 14:50 +0200, Solène Rapenne wrote:
> Je 2017-10-18 00:47, Daniel Boyd skribis:
> > I'm attempting to install onto a G4 Cube with a busted CD-ROM
> > drive.
> > I've never done network booting before, so I'm sure I'm just
> > missing
> > something.
> > 
> > I set up NFS and TFTP on a linux box, copied ofwboot to the TFTP
> > share
> > and bsd.rd plus all the tgz files to the NFS share.
> > 
> > In Open Firmware, I'm setting:
> > 
> > default-server-ip -> ip of linux box
> > root-path -> "x.x.x.x:/path/to/nfs/share"
> > next-server -> ip of linux box
> > 
> > and then:
> > 
> > > boot enet:,ofwboot /bsd.rd
> > 
> > The TFTP part seems to be working.  I get:
> > 
> > > > OpenBSD/macppc BOOT 1.6
> > 
> > but then:
> > 
> > open(/pci@f400/ethernet:/etc/boot.conf): Unknown error: code 60
> > boot>
> > cannot open /pci@f400/ethernet:/etc/random.seed: Unknown error:
> > code 60
> > booting /pci@f400/ethernet:/bsd.rd: open
> > /pci@f400/ethernet:/bsd.rc: Unknown error: code 60 failed(60).
> > will
> > try /bsd
> > boot>
> > 
> > ..and then it fails to boot bsd
> > 
> > Am I required to set up a DHCP server, too?
> 
> Hello, I had the same problem 2 years ago :
> http://misc.openbsd.narkive.com/uSQMW0M5/need-help-to-install-openbsd
> -5-9-macppc-via-pxe
> 
> try with root-path "/path/to/nfs/share"
> in fact, if I remember well, the TFTP boot will use 
> $next-server:/$root-path so you don't
> need to put the ip in root-path.
> 
> 



Re: Guess what today is

2017-10-18 Thread Luka Kosanovic
Happy birthday, keep up the good work.

On Wed, Oct 18, 2017 at 7:54 PM, Sterling Archer  wrote:

> Happy birthday, thanks Theo, all the devs, past and present,
> and everyone who mailed in a dmesg after upgrading (hint).
>
> On Wed, Oct 18, 2017 at 7:21 PM, Matthew Graybosch
>  wrote:
> > On Wed, 18 Oct 2017 09:01:15 -0200
> > "x9p"  wrote:
> >
> >> Happy birthday and good f*cking amazing work.
> >
> > Damn right. I might be a johnny-come-lately desktop OpenBSD user, but I
> > won't go back to Linux except under duress.
> >
> > Even my wife likes it; she just doesn't know it's OpenBSD. =^.^=
> >
> > --
> > Matthew Graybosch
> > https://matthewgraybosch.com
> >
> > "If you didn't want me to say 'both', you should have used XOR."
> >
>
>
>
> --
> :wq!
>
>


Re: Guess what today is

2017-10-18 Thread Sterling Archer
Happy birthday, thanks Theo, all the devs, past and present,
and everyone who mailed in a dmesg after upgrading (hint).

On Wed, Oct 18, 2017 at 7:21 PM, Matthew Graybosch
 wrote:
> On Wed, 18 Oct 2017 09:01:15 -0200
> "x9p"  wrote:
>
>> Happy birthday and good f*cking amazing work.
>
> Damn right. I might be a johnny-come-lately desktop OpenBSD user, but I
> won't go back to Linux except under duress.
>
> Even my wife likes it; she just doesn't know it's OpenBSD. =^.^=
>
> --
> Matthew Graybosch
> https://matthewgraybosch.com
>
> "If you didn't want me to say 'both', you should have used XOR."
>



-- 
:wq!



Re: Guess what today is

2017-10-18 Thread Matthew Graybosch
On Wed, 18 Oct 2017 09:01:15 -0200
"x9p"  wrote:

> Happy birthday and good f*cking amazing work.

Damn right. I might be a johnny-come-lately desktop OpenBSD user, but I
won't go back to Linux except under duress.

Even my wife likes it; she just doesn't know it's OpenBSD. =^.^=

-- 
Matthew Graybosch
https://matthewgraybosch.com

"If you didn't want me to say 'both', you should have used XOR."



Re: Flask app as UWSGI returning 500 when accessed through OpenBSD HTTPD

2017-10-18 Thread Ajitabh Pandey
On Wed, Oct 18, 2017 at 7:25 PM, Ajitabh Pandey 
wrote:

>
> On Wed, Oct 18, 2017 at 7:14 PM, Jiri B  wrote:
>
>> On Wed, Oct 18, 2017 at 06:55:32PM +0530, Ajitabh Pandey wrote:
>> > On Wed, Oct 18, 2017 at 1:43 PM, Jiri B  wrote:
>> >
>> > > On Wed, Oct 18, 2017 at 01:40:06PM +0530, Ajitabh Pandey wrote:
>>
>> See?
>
>
> Yes, I see that. Thank you very much. I will try and figure out on how do
> I make uwsgi create socket with specific ownership and permissions. I would
> hate to chroot the uwsgi because that would mean to copy python libraries
> in /var/www :-)
>
> Thanks again for inputs here.
>

I am now able to create the socket with correct permission / ownership.
Here is the uwsgi ini file -

[uwsgi]
module = wsgi
# process related settings
master = 1
processes = 4
threads = 2

socket = /var/www/run/hello.sock
# approprite ownership and permissions on socket
chmod-socket = 660
chown-socket = www:www

# clear environment on exit
vaccume = true
wsgi-file = myproject.py

and I am running it as -

$ doas uwsgi --ini hellopy.ini --callable app

and this is the permissions now -

$ ls -l /var/www/run
total 0
srw-rw  1 www  www  0 Oct 18 19:47 hello.sock=

Now when I access

http://192.168.1.111/hello/

request just times out (return code 408)

access.log just shows -

default x.y.a.b - - [18/Oct/2017:19:48:41 +0530]" " 408 0

There is nothing in error.log

Any idea what am I doing wrong.

Regards.
-- 
Ajitabh Pandey
http://ajitabhpandey.info/


Re: bioctl and S.M.A.R.T support for physical disks

2017-10-18 Thread Juan Francisco Cantero Hurtado
On Tue, Oct 17, 2017 at 11:30:16PM -0400, Predrag Punosevac wrote:
> Hi Misc,
> 
> I am using 
> 
> # bioctl sd4
> Volume  Status   Size Device  
> softraid0 0 Online  2000396018176 sd4 RAID1 
>   0 Online  2000396018176 0:0.0   noencl 
>   1 Online  2000396018176 0:1.0   noencl 
>  
> for my desktop
> 
> # uname -a
> OpenBSD oko.bagdala2.net 6.2 GENERIC.MP#0 amd64
> 
> Physical drives used to create mirror on this machine are 
> /dev/sd0 and /dev/sd1
> 
> When I try to probe the drives with S.M.A.R.T utility I get 
> 
> # smartctl -i -d sat /dev/sd0

Try "smartctl -i -d sat /dev/rsd0c".

> smartctl 6.5 2016-05-07 r4318 [x86_64-unknown-openbsd6.2] (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke,
> www.smartmontools.org
> 
> Smartctl open device: /dev/sd0 [SAT] failed: Operation not supported by
> device
> 
> 
> and this is without device option
> 
> # smartctl -i  /dev/sd0   
> smartctl 6.5 2016-05-07 r4318 [x86_64-unknown-openbsd6.2] (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke,
> www.smartmontools.org
> 
> Smartctl open device: /dev/sd0 failed: Operation not supported by device
> 
> It makes me wonder if S.M.A.R.T. support for physical disks is added to
> bioctl since 2006/7 when Marco Peereboom was talking about that on
> NYC*BUG. I am using high end enterprise drives on this machine which do
> support S.M.A.R.T. and I did enable S.M.A.R.T. in bios.
> 
> Cheers,
> Predrag
> 

-- 
Juan Francisco Cantero Hurtado http://juanfra.info



Re: Flask app as UWSGI returning 500 when accessed through OpenBSD HTTPD

2017-10-18 Thread Ajitabh Pandey
On Wed, Oct 18, 2017 at 7:14 PM, Jiri B  wrote:

> On Wed, Oct 18, 2017 at 06:55:32PM +0530, Ajitabh Pandey wrote:
> > On Wed, Oct 18, 2017 at 1:43 PM, Jiri B  wrote:
> >
> > > On Wed, Oct 18, 2017 at 01:40:06PM +0530, Ajitabh Pandey wrote:
> > >
> > > Can httpd access the socket? What are permissions?
> >
> > Here are the perms -
> >
> > srwxr-xr-x  1 root  daemon  0 Oct 18 13:35 hello.sock
>
> And voila, they are wrong. How would httpd daemon be able
> to write there?
>
> See what slowcgi, a fastcgi->cgi daemon says about socket:
>
>   slowcgi opens a socket at /var/www/run/slowcgi.sock, owned by www:www,
>   with permissions 0660.  It will then chroot(8) to /var/www and drop
>   privileges to user "www".
>
> See?
>


Yes, I see that. Thank you very much. I will try and figure out on how do I
make uwsgi create socket with specific ownership and permissions. I would
hate to chroot the uwsgi because that would mean to copy python libraries
in /var/www :-)

Thanks again for inputs here.
-- 
Ajitabh Pandey
http://ajitabhpandey.info/


Re: Flask app as UWSGI returning 500 when accessed through OpenBSD HTTPD

2017-10-18 Thread Jiri B
On Wed, Oct 18, 2017 at 06:55:32PM +0530, Ajitabh Pandey wrote:
> On Wed, Oct 18, 2017 at 1:43 PM, Jiri B  wrote:
> 
> > On Wed, Oct 18, 2017 at 01:40:06PM +0530, Ajitabh Pandey wrote:
> >
> > Can httpd access the socket? What are permissions?
> >
> > j.
> >
> 
> Here are the perms -
> 
> srwxr-xr-x  1 root  daemon  0 Oct 18 13:35 hello.sock

And voila, they are wrong. How would httpd daemon be able
to write there?

See what slowcgi, a fastcgi->cgi daemon says about socket:

  slowcgi opens a socket at /var/www/run/slowcgi.sock, owned by www:www,
  with permissions 0660.  It will then chroot(8) to /var/www and drop
  privileges to user "www".

See?

j.



Re: Flask app as UWSGI returning 500 when accessed through OpenBSD HTTPD

2017-10-18 Thread Ajitabh Pandey
On Wed, Oct 18, 2017 at 1:43 PM, Jiri B  wrote:

> On Wed, Oct 18, 2017 at 01:40:06PM +0530, Ajitabh Pandey wrote:
>
> Can httpd access the socket? What are permissions?
>
> j.
>

Here are the perms -

srwxr-xr-x  1 root  daemon  0 Oct 18 13:35 hello.sock

-- 
Ajitabh Pandey
http://ajitabhpandey.info/


Re: Flask app as UWSGI returning 500 when accessed through OpenBSD HTTPD

2017-10-18 Thread Ajitabh Pandey
On Wed, 18 Oct 2017 at 4:45 PM, Gregory Edigarov  wrote:

> >
> > I get 500
> >
> hi, what's in your error.log?


Nothing is in the error log. The access log indicates one line with 500 in
it.


Re: macppc netboot

2017-10-18 Thread Solène Rapenne

Je 2017-10-18 00:47, Daniel Boyd skribis:

I'm attempting to install onto a G4 Cube with a busted CD-ROM drive.
I've never done network booting before, so I'm sure I'm just missing
something.

I set up NFS and TFTP on a linux box, copied ofwboot to the TFTP share
and bsd.rd plus all the tgz files to the NFS share.

In Open Firmware, I'm setting:

default-server-ip -> ip of linux box
root-path -> "x.x.x.x:/path/to/nfs/share"
next-server -> ip of linux box

and then:


boot enet:,ofwboot /bsd.rd


The TFTP part seems to be working.  I get:


OpenBSD/macppc BOOT 1.6


but then:

open(/pci@f400/ethernet:/etc/boot.conf): Unknown error: code 60
boot>
cannot open /pci@f400/ethernet:/etc/random.seed: Unknown error:
code 60
booting /pci@f400/ethernet:/bsd.rd: open
/pci@f400/ethernet:/bsd.rc: Unknown error: code 60 failed(60). will
try /bsd
boot>

..and then it fails to boot bsd

Am I required to set up a DHCP server, too?


Hello, I had the same problem 2 years ago :
http://misc.openbsd.narkive.com/uSQMW0M5/need-help-to-install-openbsd-5-9-macppc-via-pxe

try with root-path "/path/to/nfs/share"
in fact, if I remember well, the TFTP boot will use 
$next-server:/$root-path so you don't

need to put the ip in root-path.



Re: Flask app as UWSGI returning 500 when accessed through OpenBSD HTTPD

2017-10-18 Thread Gregory Edigarov

On 18.10.17 10:36, Ajitabh Pandey wrote:

$ uwsgi --http : --wsgi-file myproject.py --master --callable app

$ curl http://127.0.0.1:/

returns the contents, but when I access the page as

http://192.168.1.111/hello/

I get 500.

Any pointers will be helpful.


hi, what's in your error.log?



Re: Guess what today is

2017-10-18 Thread flipchan
OMG, happy birthday!!!

On October 18, 2017 12:16:09 PM GMT+02:00, STeve Andre'  wrote:
>Happy birthday to OpenBSD--22 years old!

-- 
Take Care Sincerely flipchan layerprox dev

Re: bioctl and S.M.A.R.T support for physical disks

2017-10-18 Thread Vijay Sankar


Quoting Predrag Punosevac :


Hi Misc,

I am using

# bioctl sd4
Volume  Status   Size Device
softraid0 0 Online  2000396018176 sd4 RAID1
  0 Online  2000396018176 0:0.0   noencl 
  1 Online  2000396018176 0:1.0   noencl 

for my desktop

# uname -a
OpenBSD oko.bagdala2.net 6.2 GENERIC.MP#0 amd64

Physical drives used to create mirror on this machine are
/dev/sd0 and /dev/sd1

When I try to probe the drives with S.M.A.R.T utility I get

# smartctl -i -d sat /dev/sd0
smartctl 6.5 2016-05-07 r4318 [x86_64-unknown-openbsd6.2] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke,
www.smartmontools.org

Smartctl open device: /dev/sd0 [SAT] failed: Operation not supported by
device


and this is without device option

# smartctl -i  /dev/sd0
smartctl 6.5 2016-05-07 r4318 [x86_64-unknown-openbsd6.2] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke,
www.smartmontools.org

Smartctl open device: /dev/sd0 failed: Operation not supported by device

It makes me wonder if S.M.A.R.T. support for physical disks is added to
bioctl since 2006/7 when Marco Peereboom was talking about that on
NYC*BUG. I am using high end enterprise drives on this machine which do
support S.M.A.R.T. and I did enable S.M.A.R.T. in bios.

Cheers,
Predrag


Hi,

smartctl -i  /dev/sd0c works

Vijay

--
Vijay Sankar, M.Eng., P.Eng.
ForeTell Technologies Limited
vsan...@foretell.ca



Re: Guess what today is

2017-10-18 Thread x9p

Happy birthday and good f*cking amazing work.

> Oh, yes. Happy birthday.
>
>> Happy birthday to OpenBSD--22 years old!
>>
>>
>
>
>




Re: Guess what today is

2017-10-18 Thread Christoph R. Murauer
Oh, yes. Happy birthday.

> Happy birthday to OpenBSD--22 years old!
>
>




Guess what today is

2017-10-18 Thread STeve Andre'

Happy birthday to OpenBSD--22 years old!



Re: Flask app as UWSGI returning 500 when accessed through OpenBSD HTTPD

2017-10-18 Thread Jiri B
On Wed, Oct 18, 2017 at 01:40:06PM +0530, Ajitabh Pandey wrote:
> Thanks for the quick response. I tried that, still getting 500 the same
> problem -
> 
> $ doas uwsgi --socket /var/www/run/hello.sock --wsgi-file myproject.py
> --master --callable app
> 
> In /etc/httpd.conf -
> 
>   location "/hello/*" {
> fastcgi socket "/run/hello.sock"
>   }

Can httpd access the socket? What are permissions?

j.



Re: Flask app as UWSGI returning 500 when accessed through OpenBSD HTTPD

2017-10-18 Thread Ajitabh Pandey
Thanks for the quick response. I tried that, still getting 500 the same
problem -

$ doas uwsgi --socket /var/www/run/hello.sock --wsgi-file myproject.py
--master --callable app

In /etc/httpd.conf -

  location "/hello/*" {
fastcgi socket "/run/hello.sock"
  }

Regards.
-- 
Ajitabh Pandey


On Wed, Oct 18, 2017 at 1:22 PM, Kim Zeitler 
wrote:

> Hi
>
> you have a slight error, fastcgi wants a socket not a port.
>
> On 10/18/17 09:36, Ajitabh Pandey wrote:
>
>> Hi,
>>
>> I am trying to setup a sample flask application proxy through OpenBSD
>> httpd. Here is the config -
>>
>> --
>> ext_ip="192.168.1.111"
>>
>> prefork 2
>>
>> server "default" {
>>listen on $ext_ip port 80
>>root "/htdocs"
>>
>>location "/hello/*" {
>>  fastcgi socket ":"
>>}
>>
>
> from httpd.conf(5)
> ...
> Enable FastCGI instead of serving files.  The socket is a local
>  path name within the chroot(2) root directory of httpd(8) and
>  defaults to /run/slowcgi.sock.
> ...
>
> Try running uwsgi with a socket in /var/www/run instead of an tcp port
>
>
> --
> Kim Zeitler
> Bachelor of Science (Hons)
>
> Konzept Informationssysteme GmbH
> Am Weiher 13 • 88709 Meersburg
>
> Fon: +49 7532 4466-240
> Fax: +49 7532 4466-66
> kim.zeit...@konzept-is.de
> www.konzept-is.de
>
> Amtsgericht Freiburg 581491 • Geschäftsführer: Dr. Peer Griebel,
> Frank Häßler, Dr. Christophe Schoenenberger
>
>


-- 
Ajitabh Pandey
http://ajitabhpandey.info/ | http://unixclinic.net/ |
http://buddingthoughts.info
ICQ - 150615062
Registered Linux User - 240748


Flask app as UWSGI returning 500 when accessed through OpenBSD HTTPD

2017-10-18 Thread Ajitabh Pandey
Hi,

I am trying to setup a sample flask application proxy through OpenBSD
httpd. Here is the config -

--
ext_ip="192.168.1.111"

prefork 2

server "default" {
  listen on $ext_ip port 80
  root "/htdocs"

  location "/hello/*" {
fastcgi socket ":"
  }
}

types {
  text/csscss
  text/html   html htm
  text/plain  txt
  image/gif   gif
  image/jpeg  jpeg jpg
  image/png   png
  application/javascript  js
  application/xml xml
}
--

The flask app is

--
from flask import Flask
app = Flask(__name__)

@app.route("/")
def hello():
return "Hello There!"

if __name__ == "__main__":
app.run(host='127.0.0.1')

I am running UWSGI as -
--

$ uwsgi --http : --wsgi-file myproject.py --master --callable app

$ curl http://127.0.0.1:/

returns the contents, but when I access the page as

http://192.168.1.111/hello/

I get 500.

Any pointers will be helpful.

Regards.
-- 
Ajitabh Pandey
http://ajitabhpandey.info/


Re: macppc netboot

2017-10-18 Thread Janne Johansson
2017-10-18 0:47 GMT+02:00 Daniel Boyd :

> I'm attempting to install onto a G4 Cube with a busted CD-ROM drive.
> I've never done network booting before, so I'm sure I'm just missing
> something.
>

Make sure to read and follow ALL the steps in "man diskless" that has
anything to
do with PPC boots, don't cut corners, don't skip stuff that you think won't
be needed
and it will probably work for you. I had a bunch of odd platforms
netbooting a long
time ago, and the manpage worked every time for me, and the netbootings
failed
every time I did not read and follow it to the letter.

Also, having a tcpdump going might help, to see what actually gets asked for
in the tftp requests and so on.

-- 
May the most significant bit of your life be positive.