Re: Cron logs in /var/cron/log instead of /var/log/cron?

> > That's the kind of comment that leads me to take bug reports less > > seriously in the future... diagnostic logs which would have solved > > the problem, will have been lost INTENTIONALLY. And then we get > > asked for help? Crazy. > > > > Thank you for that information; The impression I

Re: Cron logs in /var/cron/log instead of /var/log/cron?

On Sun, 02 Oct 2016 22:45:00 -0600 "Theo de Raadt" wrote: > > Why is it in /var/cron/log and not /var/log/cron by default? To me > > it makes more sense to have it all in /var/log/, but given it has > > been the default for several years, is there a reason (other than > >

Re: Cron logs in /var/cron/log instead of /var/log/cron?

> Why is it in /var/cron/log and not /var/log/cron by default? To me it > makes more sense to have it all in /var/log/, but given it has been the > default for several years, is there a reason (other than historic) that > the default is like that? That dates back to more than 20 years actually.

Cron logs in /var/cron/log instead of /var/log/cron?

I have noticed for the last 5 years of OpenBSD usage that the cron log location is /var/cron/log, instead of /var/log/cron: # $OpenBSD: syslog.conf,v 1.19 2015/11/26 15:25:14 deraadt Exp $ # *.notice;auth,authpriv,cron,ftp,kern,lpr,mail,user.none /var/log/messages

Fix paxtest output on OpenBSD 6.0?

Fix paxtest output on OpenBSD 6.0? Hallo :) Also I included a few other OS. Mirror for the post is here: https://pastebin.com/raw/y9qHwZxi Tests are after a default/fresh install (not livecd), using https://www.grsecurity.net/~spender/paxtest-0.9.15.tar.gz All OS were

Re: signify: write to stdout: Broken pipe

Hi, with some help from Alex Greif offlist helping me reproducing the issue, I decided to reinstall the system using a different mirror and different approaches. After lot of trying I found that I am running into the issue as soon as I install either quodlibet or keepassx on my system. Removing

Re: OpenBSD 6.0 bsd.rd doesn't boot on soekris net4801 [solved, but ...]

Am 02.10.2016 um 21:24 schrieb Paul Suh: >> On Oct 2, 2016, at 3:06 PM, Peer Janssen wrote: >> >> Now I reinstalled on another CF-Disk (4GB Transcend) with another method >> (miniboot.fs), this went through and first-rebooted just fine. >> >> But now halting the machine produces a

Re: OpenBSD 6.0 bsd.rd doesn't boot on soekris net4801 [solved, but ...]

> On Oct 2, 2016, at 3:06 PM, Peer Janssen wrote: > > Now I reinstalled on another CF-Disk (4GB Transcend) with another method > (miniboot.fs), this went through and first-rebooted just fine. > > But now halting the machine produces a panic: Peer, I suspect that part of the problem

Re: OpenBSD 6.0 bsd.rd doesn't boot on soekris net4801

On 10/02/16 11:53, Peer Janssen wrote: > Goal: Upgrade a working soekris net4801 from OpenBSD 4.6 to 6.0. good. > First I copied the complete 256 MB SiliconDrive CF-Disk to a newer > SanDisk 8 GB Ultra one and rebootet, which worked smoothly and fine. well, probably don't want to use that 256MB

Re: OpenBSD 6.0 bsd.rd doesn't boot on soekris net4801 [solved, but ...]

Now I reinstalled on another CF-Disk (4GB Transcend) with another method (miniboot.fs), this went through and first-rebooted just fine. But now halting the machine produces a panic: # halt -q -p syncing disks... panic: init died (signal 11, exit 0) Stopped at Debugger+0x7: leave TID

Re: OpenBSD 6.0 bsd.rd doesn't boot on soekris net4801

On 2016-10-02 16:54, Peer Janssen wrote: Goal: Upgrade a working soekris net4801 from OpenBSD 4.6 to 6.0. First I copied the complete 256 MB SiliconDrive CF-Disk to a newer SanDisk 8 GB Ultra one and rebootet, which worked smoothly and fine. [...] Is a system like the soekris net4801 not

Re: Unexpected behavior in su/doas

On 2016-10-02 18:14, Chris Bennett wrote: On Sun, Oct 02, 2016 at 01:03:28AM -0700, Philip Guenther wrote: On Sun, Oct 2, 2016 at 12:35 AM, Otto Moerbeek wrote: > On Sat, Oct 01, 2016 at 05:15:31PM -0500, Chris Bennett wrote: > >> On Sat, Oct 01, 2016 at 03:54:40PM -0600, Theo

Re: Unexpected behavior in su/doas

On Sun, Oct 02, 2016 at 01:03:28AM -0700, Philip Guenther wrote: > On Sun, Oct 2, 2016 at 12:35 AM, Otto Moerbeek wrote: > > On Sat, Oct 01, 2016 at 05:15:31PM -0500, Chris Bennett wrote: > > > >> On Sat, Oct 01, 2016 at 03:54:40PM -0600, Theo de Raadt wrote: > >> > Use of su,

OpenBSD 6.0 bsd.rd doesn't boot on soekris net4801

Goal: Upgrade a working soekris net4801 from OpenBSD 4.6 to 6.0. First I copied the complete 256 MB SiliconDrive CF-Disk to a newer SanDisk 8 GB Ultra one and rebootet, which worked smoothly and fine. I took the bsd.rd from an OpenBSD 6.0 i386 machine: # ls -l /bsd.rd -rw-r--r-- 1 root wheel

HP MediaSmart 470 only recognizes 2 drives

I’ve been running OpenBSD on an old HP MediaSmart 470 box. I just installed 5.9 yesterday. The BIOS reports 3 installed drives: IDE Channel 2 Master : ST31500541AS CC34 (OpenBSD disklabel) IDE Channel 2 Slave : WDC WD20EFRX-68EUZN0 82.00A82 (new, unformatted) IDE

Fix paxtest output on OpenBSD 6.0?

Hallo :) Also I included a few other OS. Mirror for the post: https://pastebin.com/raw/y9qHwZxi Tests are after a default/fresh install (not livecd), using https://www.grsecurity.net/~spender/paxtest-0.9.15.tar.gz All OS were installed/tested in VirtualBox-5.1.6_110634_el7-1.x86_64 on a

Re: getopt(3) in echo(1)

On September 30, 2016 5:16:57 PM GMT+02:00, Otto Moerbeek wrote: >On Fri, Sep 30, 2016 at 04:47:33PM +0200, Paul de Weerd wrote: > >> On Fri, Sep 30, 2016 at 04:40:16PM +0200, Jan Stary wrote: >> | echo.c says >> | >> |/* This utility may NOT do getopt(3) option parsing. */ >>

Re: signify: write to stdout: Broken pipe

Hi Alex, On Sun, 2 Oct 2016 15:47:36 +0200 Alex Greif wrote: > I experienced the same. what I did: > - install todays snapshot > - sysmerge > - pkg_add -nu ---> reported the problems > - pkg_add -u sudo ---> reported problems but installed correctly > anyway > -

Re: signify: write to stdout: Broken pipe

I experienced the same. what I did: - install todays snapshot - sysmerge - pkg_add -nu ---> reported the problems - pkg_add -u sudo ---> reported problems but installed correctly anyway - reboot - pkg_add -nu ---> reported no problems - pkg_add -u ---> reported no problems noc clue what the

Re: OpenBSD 6.0 does not detect my USB ethernet interface

I'm also a newbie, but I think there is no drivers for your device on OpenBSD. Maybe you can solve the problem with PPPoE: http://man.openbsd.org/OpenBSD-current/man4/pppoe.4 Have a good day! Raffaele On Sun, 2 Oct 2016 08:15:31 + (UTC) Farhad Benyamin wrote: >

Re: signify: write to stdout: Broken pipe

Hi misc, On Sat, 01 Oct 2016 14:50:35 -0400 "Joe Gidi" wrote: > And, as is so often the case, I figured out the problem right after > sending > that email. My old 'sudo' package was apparently not entirely > functional after > updating the base system. 'doas pkg_add -u'

OpenBSD 6.0 does not detect my USB ethernet interface

Hello, I installed OpenBSD 6.0 (GENERIC kernel) on a AMD64 machine. The system can't detect my USB ethernet interface, altough LED of USB on modem is light up. I also had this problem on NetBSD 7.0.1, during installation it can't detect this interface, but I don't try to solve it. I am grateful

Re: Looking for DMVPN implementation

On Sat, Oct 01, 2016 at 10:44:02PM +, Jens Sauer wrote: > Hi OpenBSD community, > > i'm looking for an OpenSource implementation of DMVPN (Dynamic Multipoint > Virtual private network). > > Currently i just found the draft (from 2013) : > https://tools.ietf.org/html/draft-detienne-dmvpn-00

Re: Unexpected behavior in su/doas

> > This is just one mechanism on tty, there are others. On other > > descriptors there are other abilities. > > > > Would you mind explaining this a little bit. I don't really mean the > sudo/doas part. > > How to do operations without retaining access to a tty? > > What other descriptors?

Re: Unexpected behavior in su/doas

On Sun, Oct 2, 2016 at 12:35 AM, Otto Moerbeek wrote: > On Sat, Oct 01, 2016 at 05:15:31PM -0500, Chris Bennett wrote: > >> On Sat, Oct 01, 2016 at 03:54:40PM -0600, Theo de Raadt wrote: >> > Use of su, doas, or sudo -- means you EXPLICITLY want the tty to >> > remain the same. >>

Re: Unexpected behavior in su/doas

On Sat, Oct 01, 2016 at 05:15:31PM -0500, Chris Bennett wrote: > On Sat, Oct 01, 2016 at 03:54:40PM -0600, Theo de Raadt wrote: > > Use of su, doas, or sudo -- means you EXPLICITLY want the tty to > > remain the same. > > > > De-escalation using these "sudo" or "doas" like tools on a tty is > >

Re: Unexpected behavior in su/doas

On Sun, Oct 02, 2016 at 07:10:12AM +0200, Sebastien Marie wrote: > On Sat, Oct 01, 2016 at 05:15:31PM -0500, Chris Bennett wrote: > > On Sat, Oct 01, 2016 at 03:54:40PM -0600, Theo de Raadt wrote: > > > Use of su, doas, or sudo -- means you EXPLICITLY want the tty to > > > remain the same. > > >