Re: Cheap hardware for router, perhaps fileserver?

[Quartz]

is seeing as I'm unlikely to get any more than "up to" 76Mbps from my
ISP's fibre anyway,


Effectively any hardware that still boots will work as a home router. A 
500mhz Pentium III with 64mb ram can handle a 100mbps connection without 
breaking a sweat.


Decide what you want to do about a fileserver first, that's the deciding 
factor for hardware.




CuBox
armv7
without
having to be too inventive and using binary blobs from odd places for
bootloaders and whatnot


Do be aware that i386 and amd64 are the more tested platforms by a wide 
margin. The further you go into niche territory the more stuff will stop 
working and the more you'll have to mess around.




and what
good deals there are,



I spent rather more on a mini-ITX PC system with a loud fan


Again, home router duties require negligible horsepower. If you don't 
need much from the fileserver front you can probably build a machine 
from parts in your basement (can't beat free), or you could easily get 
away with a lower cost low power passively-cooled itx system.

Re: urtwn driver has problems

[Peter Hessler]

On 2015 Sep 19 (Sat) at 20:26:02 + (+), Alexey Suslikov wrote:
:Stuart Henderson  spacehopper.org> writes:
: 
:> On 2015-09-18, Alexey Suslikov  gmail.com> wrote:
:> > I think you should try 5.8, there was stability fixes in urtwn(4).
:> 
:> 5.8 hasn't been released yet.
:
:How about "Various stability fixes for urtwn(4) driver" in 58.html then?
:

How about "To be released Oct 18, 2015" in 58.html then?


-- 
It's always darkest just before it gets pitch black.

Re: Cheap hardware for router, perhaps fileserver?

[Mark Carroll]

Many helpful replies so quickly, thank you. It looks like I should plan
to spend more and stick with x86 if it's so much better supported. The
mention of Mini-Box rang a bell as I used to have an M200 that worked
well. I try to avoid diversity in both hardware and software so, if I'm
spending a bit more anyway, perhaps I should even look out for a system
whose sibling could replace, for instance, the computer I use for
streaming TV. My fileserver needs would be modest -- I'm asking little
in terms of number of clients, reliability, size, throughput, etc. --
I am just looking to add enough value to justify spending more on a
'router', even to the level of Intel NUCs which look pretty good if
their hardware is solid.

As background, this OpenBSD effort is also partly about replacing the
various hardware I already have: nearly ten-year-old desktop machines
that are on their last legs (replacing parts by cannibalization or
buying used on eBay) and are enormous, noisy, and power-hungry. (My
current router is a full-height tower, a server retired from a past
employer, with one of the first single-core Opterons and the 2.5" drive
from its mini-ITX predecessor which died!) I figure if I'm reinstalling
stuff onto new hardware, it's a good time to try out OpenBSD too: if
nothing else, it makes me actually review configurations instead of just
copying them over.

-- Mark

Re: urtwn driver has problems

[Alexey Suslikov]

Peter Hessler  theapt.org> writes:

> 
> On 2015 Sep 19 (Sat) at 20:26:02 + (+), Alexey Suslikov wrote:
> :Stuart Henderson  spacehopper.org> writes:
> : 
> :> On 2015-09-18, Alexey Suslikov  gmail.com> wrote:
> :> > I think you should try 5.8, there was stability fixes in urtwn(4).
> :> 
> :> 5.8 hasn't been released yet.
> :
> :How about "Various stability fixes for urtwn(4) driver" in 58.html then?
> :
> 
> How about "To be released Oct 18, 2015" in 58.html then?

Given the fact of absence of any mentions of urtwn(4) in 58.html,
you get the idea right, Peter. Love OpenBSD so called meritocracy
again: drop tech stuff, whine about chatty users.

And, btw, good way to "attract" people having problem: wait for
release date.

Re: multiple headphone sockets and sndiod on Lenovo M83/Tiny-in-One 23

[Alexandre Ratchov]

On Sun, Sep 20, 2015 at 04:43:09AM +, mark hellewell wrote:
> On Sat, 19 Sep 2015 at 18:37 Remco  wrote:
> 
> > You've got 3 separate audio devices, azalia0, azalia1 and uaudio0.
> > azalia0: probably HDMI audio which isn't supported yet AFAICT
> > azalia1: on-board audio detected as audio0, sndiod normally attaches to
> > this
> >  device so all audio played on your systems is played through that.
> > uaudio0: your USB "Tiny-in-One 23" device, sndiod doesn't attach to this by
> >  default.
> >
> > To make sndiod use both devices you can add a line to your rc.conf.local:
> > sndiod_flags="-f rsnd/0 -f rsnd/1"
> > where rsnd/0 represents audio0, exposed as snd/0 by sndiod, and rsnd/1
> > represents audio/1, exposed as snd/1.
> >
> > Specifying either snd/0 or snd/1 in your application determines which
> > device
> > the audio is played on.
> >
> > If you want the USB device to be your default device you could try swapping
> > the parameters:
> > sndiod_flags="-f rsnd/1 -f rsnd/0"
> > If that doesn't work, try:
> > sndiod_flags="-f rsnd/0 -f rsnd/1 -s default"
> >
> > I hope this helps.
> >
> 
> Hi, and thanks for your reply!
> 
> With:
> 
> sndiod_flags="-f rsnd/1 -f rsnd/0"
> 
> in /etc/rc.conf.local sndiod does indeed appear to try to make the uaudio0
> device the
> default, however when I try to play audio (vlc, chrome) I now see the
> following in /var/log/messages:
> 
> Sep 20 14:07:40 obsd /bsd: uaudio_chan_open: error creating pipe:
> err=INVAL endpt=0x01
> 

hi,

Support for USB controllers and hubs is still incomplete. Basically
in the following cases isochronous transfers (used by audio devices)
don't work.

- ehci controllers with hubs between a usb-1.1 device and the
  controller doesn't work (bug causes packet corruption). It
  somewhat works if there's only one device on the hub and no
  full-duplex is used.

- xhci doesn't work at all for audio.

according to your dmesg:

uhub0 at usb0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
uhub3 at uhub0 port 10 "GenesysLogic USB2.0 Hub" rev 2.00/48.46 addr 5
uhub4 at uhub3 port 4 "Genesys Logic USB2.0 Hub" rev 2.00/32.98 addr 6
uaudio0 at uhub4 port 3 configuration 1 interface 0 "CONEXANT

the device is attached to xhci.

So try to find a port of the ehci root hub, if you can't then try
at least to find a port connected to ehci and disable full-duplex
(add "-m play" before "-f rsnd/1"). Possibly disable xhci (try
"boot -c" on the boot prompt), in which case it will show as ehci.

-- Alexandre

Re: tame(2) will by pass systrace rules

[Sebastien Marie]

On Sun, Sep 20, 2015 at 03:28:41PM +0800, johnw wrote:
> Hi all,
> 
> I run my program will systrace, I noticed the program can by pass systrace,
> If I add the tame(2) call to my program.
> 

Hi John,

Yes, it is the expected behaviour than when a program call tame(2),
systrace(4) usage in this program is skipped. You couldn't use
systrace(4) and tame(2) in the same program.

The tame(2) documentation don't have this information. I will see to add
it.

Thanks.
-- 
Sebastien Marie

Re: Cheap hardware for router, perhaps fileserver?

[Karel Gardas]

On Sun, Sep 20, 2015 at 3:33 AM, Predrag Punosevac
 wrote:
> 1. I don't like diversity at home so OpenBSD would be the first choice.
> 4TB HDD are cheap enough and I could mirror (RAID 1) all my personal
> data on two of them. There are two options for mirroring. Either use
> softraid or get a cheap used Areca hardware RAID card of e-bay. Those
> cards according to man pages have excellent support on OpenBSD (they are
> true open hardware). Use one of inexpensive Celeron based motherboards
> (you can get them under $50). I would be curious what OpenBSD gurus have
> to say about their experience with Areca on OpenBSD and building a
> OpenBSD file server in general.

The OpenBSD/SR RAID1 with checksum support is my future way for backup
server here. Coming from Solaris/ZFS domain I prefer software raid
over hardware so I'd not use hardware raid card unless it may be
switched to JBOD mode.

> 3. Just use ZFS/FreeBSD as I am doing at work. End up paying big bucks
> for Celeron or Atom motherboard which supports ECC RAM and at least 8
> perhaps 16 GB of it. You will not find those for $100 and the RAM ain't
> going to be cheap either. You might want to consider HBA like LSI SAS
> 9211-8i (those themself cost on e-bay around $100). This is by far the
> most expensive solution. Having a "proper" remote backup using ZFS
> replication would involve seting up two such server.

ECC is a must also on OpenBSD. It's not particular requirement of ZFS.
Anyway, ZFS itself does not require insane amount of RAM if you do not
consider dedup support. I remember running SXDE on AMD64 with 1GB RAM
and using that as a developer workstation for a year or so before
upgrade in the past. I've tuned some ZFS arc caching value somewhere
and it was running smoothly then.

tame(2) will by pass systrace rules

[johnw]

Hi all,

I run my program will systrace, I noticed the program can by pass 
systrace, If I add the tame(2) call to my program.


my program will connect to inet, if I run my program will systrace, I 
need to add systrace rule like this "native-connect:  permit",
I noticed, if I add the tame("inet", NULL) call before connect to inet, 
I can connect to inet, even do not need to add systrace 
rule(native-connect: XXX permit" without any error.


Thanks.

Re: Cheap hardware for router, perhaps fileserver?

[Quernus]

I faced a similar conundrum and in the end went for an HP Microserver G8. They
have 4 sata bays, plus as card slot. They have USB3. ILO remote management.
Very quiet and cheap. I pimped mine up a bit with more memory and a CPU
supporting VT-d:

https://www.quernus.co.uk/2015/08/26/upgrading-hp-microserver-g8-with-xeon/

I wanted ZFS for storage and OpenBSD due to easier IPSec configure and general
networking and security awesomeness. So I went for hybrid approach and run
OpenBSD under bhyve on FreeBSD:

https://www.quernus.co.uk/2015/07/27/openbsd-as-freebsd-router/

This gave me the best of both worlds on a single physical box.

-Matt

—
Matt Hamilton
Quernus
m...@quernus.co.uk
+44 117 325 3025
49b Easton Business Centre
Felix Road, Easton
Bristol, BS5 0HE

Quernus Ltd is a company registered in England and Wales. Registered number:
09076246


> On 20 Sep 2015, at 02:33, Predrag Punosevac  wrote:
>
> Router and file server are two very different things. I recently went
> through similar process. Even though at work I use Atom servers
> (naturally running OpenBSD amd64 port) for all our core network
> infrastructure and services I entertain the idea of buying non amd64
> hardware.  I looked at the state of armv7 port. I vetted all PR claims
> about Ubiquiti ERLite-3 and ended up buying this
>
> http://www.mini-box.com/Intel-D2500CCE-Mini-ITX-Motherboard
>
> as a router for my home network. (Don't worry the board is available and
> you can buy it from Amazon).
>
> File server is more interesting problem in my opinion. At work I use ZFS
> as our main file system to store data and run dozen of FreeBSD file
> servers. I also tested DragonFlyBSD and HAMMER1. I am three-way split
> when it comes to a home file server.
>
> 1. I don't like diversity at home so OpenBSD would be the first choice.
> 4TB HDD are cheap enough and I could mirror (RAID 1) all my personal
> data on two of them. There are two options for mirroring. Either use
> softraid or get a cheap used Areca hardware RAID card of e-bay. Those
> cards according to man pages have excellent support on OpenBSD (they are
> true open hardware). Use one of inexpensive Celeron based motherboards
> (you can get them under $50). I would be curious what OpenBSD gurus have
> to say about their experience with Areca on OpenBSD and building a
> OpenBSD file server in general.
>
>
> 2. Use the same hardware as above with DFBSD but take advantage of
> HAMMER1. You could use just 2HDD.  Set master PFS in one hard disk and a
> slave PFS in the other disk. For more than 2 disks I would use Areca
> hardware RAID cards. Note that HAMMER1 is network aware so it is
> tempting to set up slave PFS on a remote machine.
>
>
> 3. Just use ZFS/FreeBSD as I am doing at work. End up paying big bucks
> for Celeron or Atom motherboard which supports ECC RAM and at least 8
> perhaps 16 GB of it. You will not find those for $100 and the RAM ain't
> going to be cheap either. You might want to consider HBA like LSI SAS
> 9211-8i (those themself cost on e-bay around $100). This is by far the
> most expensive solution. Having a "proper" remote backup using ZFS
> replication would involve seting up two such server.
>
>
> Predrag

Re: audio codec RealTek ALC3263

[Remi Locherer]

On Sun, Sep 20, 2015 at 08:17:59AM +0200, Remi Locherer wrote:
> On Sat, Sep 19, 2015 at 07:26:56PM -0400, Bryan Steele wrote:
> > On Sat, Sep 19, 2015 at 06:44:13PM -0400, Bryan Steele wrote:
> > > On Sat, Sep 19, 2015 at 02:38:02PM +0200, Remi Locherer wrote:
> > > > Hi
> > > > 
> > > > My Dell XPS 13 has a RealTek ALC3263 codec (according to the BIOS). In
> > > > dmesg only the following shows up:
> > > > 
> > > > azalia0 at pci0 dev 3 function 0 "Intel Core 5G HD Audio" rev 0x09: msi
> > > > azalia0: No codecs found
> > > 
> > > This device is related to unsupported HDMI audio output, there should
> > > be a second azailia(4) device.
> > > 
> > > For example, my laptop has:
> > > 
> > > azalia1 at pci0 dev 27 function 0 "Intel 9 Series HD Audio" rev 0x03:
> > > msi
> > > azalia1: codecs: Realtek/0x0283
> > > audio0 at azalia1
> > > 
> > > > Of course there is no audio :-(
> > > 
> > > It appears this function is disabled on your system, you might want
> > > to check and see if there is a BIOS toggle, otherwise there's not
> > > much else that can be done.
> > > 
> > > > Regards,
> > > > Remi
> > > 
> > > -Bryan.
> > 
> > Actually, there may be some funny ACPI interactions going on
> > that appear responsible for this.
> > 
> > Can you try the following diff?
> > 
> > Linux has this workaround for your model..
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039
> > 
> > Index: dsdt.c
> > ===
> > RCS file: /cvs/src/sys/dev/acpi/dsdt.c,v
> > retrieving revision 1.218
> > diff -u -p -u -r1.218 dsdt.c
> > --- src/sys/dev/acpi/dsdt.c 20 Aug 2015 20:50:10 -  1.218
> > +++ src/sys/dev/acpi/dsdt.c 19 Sep 2015 23:11:54 -
> > @@ -1457,7 +1457,7 @@ struct aml_defval {
> > struct aml_value**gval;
> >  } aml_defobj[] = {
> > { "_OS_", AML_OBJTYPE_STRING, -1, osstring },
> > -   { "_REV", AML_OBJTYPE_INTEGER, 2, NULL },
> > +   { "_REV", AML_OBJTYPE_INTEGER, 5, NULL },
> > { "_GL", AML_OBJTYPE_MUTEX, 1, NULL, _global_lock },
> > { "_OSI", AML_OBJTYPE_METHOD, 1, aml_callosi },
> > 
> 
> I applied this and also commented out DIAGNOSTIC in
> azalia.c/azalia_get_response.

This morning I just did a reboot with the patched kernel. Now after a cold
boot there is another azalia device! And now I can listen to music with this
notebook. 

Thanks Bryan for the "coold boot" hint.

dmesg:
OpenBSD 5.8-current (GENERIC.MP.AUDIO_DEBUG) #1: Sun Sep 20 07:31:22 CEST 2015
r...@mistral.relo.ch:/usr/src/sys/arch/amd64/compile/GENERIC.MP.AUDIO_DEBUG
real mem = 8168914944 (7790MB)
avail mem = 7917355008 (7550MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed840 (84 entries)
bios0: vendor Dell Inc. version "A05" date 07/14/2015
bios0: Dell Inc. XPS 13 9343
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT SSDT TPM2 SSDT 
ASF! SSDT SSDT SSDT SSDT PCCT SSDT SSDT SSDT SLIC MSDM DMAR CSRT
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) 
PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) 
PXSX(S4) RP05(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2494.56 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2494.23 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2494.23 MHz
cpu2: 

Re: rc.shutdown powerdown

[Fred]

On 09/20/15 20:58, Quartz wrote:

Powerdown went away in July 2014.


The FAQ needs to be updated then:

http://www.openbsd.org/faq/faq10.html

"rc.shutdown

/etc/rc.shutdown is a script that is run at shutdown. Anything you want
done before the system shuts down should be added to this file. If you
have apm, you can also set "powerdown=YES", which will give you the
equivalent of "shutdown -p".
"



rc.shutdown is still needed if you need to run tasks before the 
reboot(8), halt(8), or when init(8) is signalled to shut the system down.


man 8 rc.shutdown

Re: speedup shutdown

[Philip Guenther]

On Sun, Sep 20, 2015 at 1:45 PM, Matthew Martin  wrote:
> On Sep 20, 2015 3:12 PM, "Quartz"  wrote:
>>
>> I have a machine where tapping the front panel power button correctly
> halts and powers off the machine however there's a solid 10 second
> delay after I press the button before anything happens. Is there any way to
> speed this process up?
>
> Hold the button down.

Heh, hard power-off, resulting in unclean filesystems probably isn't
what the original poster meant.

For power off via button, init runs "sh /etc/rc shutdown", then sends
all processes a SIGHUP, then waits 5 seconds.  If there are any
processes still alive it'll send SIGTERM and wait another 5 seconds.
If any are still alive at that point it'll send'em all SIGKILL and
wait another 5 seconds.  It'll then tell the kernel to halt the
system.

So, slow /etc/rc.d/* script delaying the /etc/rc shutdown step?  Or do
you have some daemon which isn't killed by its rc.d script, nor by
SIGHUP, thus requiring SIGTERM and at least 10 seconds?


Philip Guenther

Re: update/upgrade

[Nick Holland]

On 09/20/15 20:34, Quartz wrote:
>> You do that part on a bigger box, build releases there, and use
>> these to update the low power devices.
> 
> That doesn't really help the situation. These machines don't have 
> identical setups so you'd still have to do a lot of manual merging 
> and/or write and maintain a library of custom merge scripts for them.

You think the master builds are done on a machine that is identical to
yours at home?  No.

Build a -stable release on a same platform faster machine.  Now unpack
the .tgz files on the target machines, copy in /bsd, /bsd.rd, reboot.
ta-da, patched machine.  None of your configuration is touched by this
process.

If you are modifying the OpenBSD install to where this doesn't work, you
are on your own, but this has nothing to do with slow
hardware...building from source would do the same thing, as would upgrading.

Upgrades?  Do as usual from binary releases.

Nick.

Re: speedup shutdown

[Philip Guenther]

Oops, I misdescribed init's waiting behavior:

On Sun, Sep 20, 2015 at 5:59 PM, Philip Guenther  wrote:
...
> For power off via button, init runs "sh /etc/rc shutdown", then sends
> all processes a SIGHUP, then waits 5 seconds.  If there are any
> processes still alive it'll send SIGTERM and wait another 5 seconds.
> If any are still alive at that point it'll send'em all SIGKILL and
> wait another 5 seconds.  It'll then tell the kernel to halt the
> system.

It'll wait *up to* 5 seconds in each case: it'll continue immediately
to the kernel as soon as all processes are dead, so a 10 second wait
means slow /etc/rc.d script(s) or processes that won't die from SIGHUP
or SIGTERM, which is rude of them...

Philip Guenther

Re: speedup shutdown

[Quartz]

So, slow /etc/rc.d/* script delaying the /etc/rc shutdown step?  Or do
you have some daemon which isn't killed by its rc.d script, nor by
SIGHUP, thus requiring SIGTERM and at least 10 seconds?


This is a test system and it's pretty stock right now. Aside from the 
standard services like pf and ntp the only installed pkg is I think 
dnsmasq. It's possible there's something wrong there but I'm not sure 
where I should start looking.

Re: speedup shutdown

[Philip Guenther]

On Sun, Sep 20, 2015 at 6:12 PM, Quartz  wrote:
>> So, slow /etc/rc.d/* script delaying the /etc/rc shutdown step?  Or do
>> you have some daemon which isn't killed by its rc.d script, nor by
>> SIGHUP, thus requiring SIGTERM and at least 10 seconds?
>
> This is a test system and it's pretty stock right now. Aside from the
> standard services like pf and ntp the only installed pkg is I think dnsmasq.
> It's possible there's something wrong there but I'm not sure where I should
> start looking.

Hmm?   How about replicate the process and observe the results?  "time
sh /etc/rc shutdown".  See what's still running.  kill -HUP everything
except init and your session and see what's still running 5 seconds
later.  Then again with kill -TERM.  Whatever still standing is
slowing you down; for each one figure out whether and when it should
have died.

Philip Guenther

Re: OT: Exists some problem with dnscrypt-proxy package?

[frederick w. soucy]

On 2015.09.20, C.L. Martinez wrote:
> Hi all,
> 
>  I have installed an openbsd 5.7 VM today to do some tests with pf rules.
> One of the components to I need to enable in this gateway is
> unbound+dnscrypt-proxy.
> 
>  I have configured forwarding in unbound.conf:
> 
>  forward-zone:
> name: "."
> forward-addr: 127.0.0.1@4553
> 
>  And I have started dnscypt-proxy with the following arguments:
> 
> -d --user=_dnscrypt-proxy -a 127.0.0.1:4553 -R dnscrypt.eu-nl -p
> /var/run/dnscrypt-proxy.pid
> 
>  Output:
> 
> 32032 ??  Is  0:00.00 /usr/sbin/ftp-proxy -m 25
> 32411 ??  Is  0:00.00 /usr/local/sbin/dnscrypt-proxy -d
> --user=_dnscrypt-proxy -a 127.0.0.1:4553 -R dnscrypt.eu-nl -p
> /var/run/dnscrypt-proxy.pid
>  5667 ??  I   0:00.03 /usr/local/sbin/dnscrypt-proxy -d
> --user=_dnscrypt-proxy -a 127.0.0.1:4553 -R dnscrypt.eu-nl -p
> /var/run/dnscrypt-proxy.pid
>  1256 ??  Is  0:00.00 /usr/sbin/cron
> 17818 ??  Ss  0:00.12 sshd: root@ttyp0 (sshd)
>   527 ??  Is  0:00.05 unbound -c /var/unbound/etc/unbound.conf
> 30164 p0  Ss  0:00.02 -ksh (ksh)
>  7382 p0  R+  0:00.00 ps -xa
> 16881 C0  Is+ 0:00.00 /usr/libexec/getty std.9600 ttyC0
>  3047 C1  Is+ 0:00.00 /usr/libexec/getty std.9600 ttyC1
> 
>  And it doesn't works. But if I change unbound's forward section to:
> 
> forward-zone:
> name: "."
> #forward-addr: 127.0.0.1@4553
> forward-addr: 8.8.8.8
> 
>  Works ok. Removing all forward seciton, unbound works ok also. Then, I am
> doing something wrong but I don't know which.
> 
>  Any idea??
> 
>  Thanks.

i was having problems with dnscrypt.eu-nl today, could ping its ip but 
not get any dns resolution so i just switched to dnscrypt.eu-dk and 
everything is working again ymmv

Re: Suspend Hangs ThinkPad T450s

[Mark Kettenis]

> From: Aaron Poffenberger 
> Date: Sun, 20 Sep 2015 16:39:54 -0500
> 
> Another issue I noted in the ThinkPad dmesg. Pulling out as separate 
> request for reference sake.
> 
> Suspending now hangs system
>   - X11 disables correctly and screen goes dark
>   - Light on power switch begins to blink
>   - Screen comes back on at one of the consoles
>   - Can hear fans begin to spin up
>   - Keyboard unresponsive
>   - Have to force reboot
> 
> This was not a problem with build from 2015-09-16.

Just committed a fix for this.

Sorry about the delay; I was a little busy making your video work better ;).

Re: update/upgrade

[Quartz]

You do that part on a bigger box, build releases there, and use
these to update the low power devices.


That doesn't really help the situation. These machines don't have 
identical setups so you'd still have to do a lot of manual merging 
and/or write and maintain a library of custom merge scripts for them.

Re: update/upgrade

[Quartz]

As it was already stated in @misc,


I don't think I got that message. (?)


mtier is probably as safe as relying on
openbsd code.


I'm not worried so much about safety in the sense of compromised code, 
but rather the practicalities of setting up a workflow that depends on 
something that can disappear at any time without notice. Their website 
has zero information about them as a company or who (if any) of them are 
also OpenBSD devs or what. It also looks like they only started a couple 
years ago.

Re: speedup shutdown

[Quartz]

For power off via button, init runs "sh /etc/rc shutdown", then sends
all processes a SIGHUP, then waits 5 seconds.  If there are any
processes still alive it'll send SIGTERM and wait another 5 seconds.
If any are still alive at that point it'll send'em all SIGKILL and
wait another 5 seconds.  It'll then tell the kernel to halt the
system.


Is there a way to watch this process as it's happening to see where the 
holdup is? Watching it in general wouldn't be a bad idea. I guess a 
large part of the issue is not so much that it takes 10 seconds, but 
that there's no confirmation or indication that it's actually doing 
anything. It just sits there like it ignored you and you can continue 
typing at the command line. There's no output or anything until the 
"syncing disks" line finally pops up.

TEXTODROIT SERVICES

[Textodroit Services]

 Textodroit Services toujours au service de la communauté /
Textodroit Services always helping the community: textodr...@gmail.com Vous
ne voyez pas ce message ? *Ouvrir dans un navigateur*


 Si vous pensez avoir reçu cet email par erreur ou si vous souhaitez vous
désabonner, *cliquez ici*








 Vous avez reçu cet email car vous êtes abonné *à ce site*


 Si vous pensez avoir reçu cet email par erreur ou si vous souhaitez vous
désabonner, *cliquez ici*

Re: audio codec RealTek ALC3263

[Alexandre Ratchov]

On Sat, Sep 19, 2015 at 10:59:53PM +0200, Remi Locherer wrote:
> azalia0 at pci0 dev 3 function 0 "Intel Core 5G HD Audio" rev 0x09: msi
> azalia_reset: resetting
> azalia_reset: reset counter = 5000
> azalia_reset: reset counter = 5000
> azalia0: host: High Definition Audio rev. 1.0
> azalia0: host: 3 output, 0 input, and 0 bidi streams
> azalia0: found a codec at #0
> azalia_init_corb: CORB allocation succeeded.
> azalia_init_corb: CORBWP=0; size=256
> azalia_init_rirb: RIRB allocation succeeded.
> azalia_init_rirb: RIRBRP=0, size=256
> azalia0: RIRB time out

This could be caused by the no-snoop setting. Does this improve
things?

Index: azalia.c
===
RCS file: /cvs/src/sys/dev/pci/azalia.c,v
retrieving revision 1.222
diff -u -p -u -p -r1.222 azalia.c
--- azalia.c29 Jul 2015 08:06:29 -  1.222
+++ azalia.c20 Sep 2015 15:41:40 -
@@ -460,6 +460,7 @@ azalia_configure_pci(azalia_t *az)
case PCI_PRODUCT_INTEL_9SERIES_HDA:
case PCI_PRODUCT_INTEL_9SERIES_LP_HDA:
case PCI_PRODUCT_INTEL_BAYTRAIL_HDA:
+   case PCI_PRODUCT_INTEL_CORE5G_HDA_1:
reg = azalia_pci_read(az->pc, az->tag,
INTEL_PCIE_NOSNOOP_REG);
reg &= INTEL_PCIE_NOSNOOP_MASK;

Re: mini itx from intel

[fRANz]

On Sun, Sep 20, 2015 at 2:50 PM, frantisek holop  wrote:

> does anyone happen to have any of these?
> http://www.intel.com/content/www/us/en/nuc/nuc-comparison.html
> plz send dmesg if possible.

Hello,
I've got a D34010WYK, fully functional for me:

OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug  8 00:20:21 MDT 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8498110464 (8104MB)
avail mem = 8263110656 (7880MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec170 (83 entries)
bios0: vendor Intel Corp. version "WYLPT10H.86A.0032.2014.1119.1552"
date 11/19/2014
bios0: Intel Corporation D34010WYK
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT MCFG HPET SSDT SSDT DMAR CSRT
acpi0: wakeup devices PS2K(S3) PS2M(S3) PXSX(S4) RP01(S4) PXSX(S4)
RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4)
PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz, 1696.33 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz, 1696.07 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz, 1696.07 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz, 1696.07 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C2, C1, PSS
acpicpu1 at acpi0: C2, C1, PSS
acpicpu2 at acpi0: C2, C1, PSS
acpicpu3 at acpi0: C2, C1, PSS
acpipwrres0 at acpi0: FN00, resource for FAN0
acpipwrres1 at acpi0: FN01, resource for FAN1
acpipwrres2 at acpi0: FN02, resource for FAN2
acpipwrres3 at acpi0: FN03, resource for FAN3
acpipwrres4 at acpi0: FN04, resource for FAN4
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 105 degC
acpibat0 at acpi0: BAT0 not present
acpibat1 at acpi0: BAT1 not present
acpibat2 at acpi0: BAT2 not present
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: LID0
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 1696 MHz: speeds: 1701, 1700, 1600, 1500,
1400, 1300, 1200, 1100, 1000, 900, 800, 782 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x09
vga1 at pci0 dev 2 function 0 "Intel HD Graphics" rev 0x09
intagp at vga1 not configured
inteldrm0 at vga1
drm0 at inteldrm0
drm: Memory usable by graphics device = 2048M
error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register
before writing to 10
No connectors reported connected with modes
Cannot find any crtc or sizes - going 1024x768
inteldrm0: 1024x768
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x09: 

Re: mini itx from intel

[ludovic coues]

2015-09-20 14:50 GMT+02:00 frantisek holop :
> does anyone happen to have any of these?
> http://www.intel.com/content/www/us/en/nuc/nuc-comparison.html
>
> plz send dmesg if possible.

Here is a dmesg for my DN2820FYKH

OpenBSD 5.7 (GENERIC.MP) #881: Sun Mar  8 11:04:17 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4146388992 (3954MB)
avail mem = 4032094208 (3845MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebec0 (46 entries)
bios0: vendor Intel Corp. version "FYBYT10H.86A.0034.2014.0513.1413"
date 05/13/2014
bios0: 
\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?
\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG LPIT HPET SSDT SSDT SSDT UEFI
acpi0: wakeup devices UAR5(S4) UAR8(S4) PS2K(S3) PS2M(S3) XHC1(S4)
EHC1(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PWRB(S0) BRCM(S0)
BRC3(S0)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU N2830 @ 2.16GHz, 2167.17 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 83MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Celeron(R) CPU N2830 @ 2.16GHz, 2166.67 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 87 pins
acpimadt0: bogus nmi for apid 0
acpimadt0: bogus nmi for apid 2
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (RP03)
acpiprt4 at acpi0: bus 4 (RP04)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C1
acpicpu1 at acpi0: C1
acpipwrres0 at acpi0: PLPE
acpipwrres1 at acpi0: PLPE
acpipwrres2 at acpi0: USBC, resource for EHC1, OTG1
acpipwrres3 at acpi0: CLK0, resource for CAM1
acpipwrres4 at acpi0: CLK1, resource for CAM0, CAM2
acpipwrres5 at acpi0: FN00, resource for FAN0
acpitz0 at acpi0: critical temperature is 90 degC
acpibat0 at acpi0: BAT0 not present
acpibat1 at acpi0: BAT1 not present
acpibat2 at acpi0: BAT2 not present
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpivideo0 at acpi0: GFX0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Bay Trail Host" rev 0x0e
vga1 at pci0 dev 2 function 0 "Intel Bay Trail Video" rev 0x0e
intagp at vga1 not configured
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ahci0 at pci0 dev 19 function 0 "Intel Bay Trail AHCI" rev 0x0e: msi, AHCI 1.3
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0:  SCSI3
0/direct fixed naa.50004cf20e0f34d9
sd0: 953869MB, 512 bytes/sector, 1953525168 sectors
xhci0 at pci0 dev 20 function 0 "Intel Bay Trail xHCI" rev 0x0e: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
"Intel Bay Trail TXE" rev 0x0e at pci0 dev 26 function 0 not configured
azalia0 at pci0 dev 27 function 0 "Intel Bay Trail HD Audio" rev 0x0e: msi
azalia0: codecs: Realtek/0x0283, Intel/0x2882, using Realtek/0x0283
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel Bay Trail PCIE" rev 0x0e: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 1 "Intel Bay Trail PCIE" rev 0x0e: msi
pci2 at ppb1 bus 2
iwm0 at pci2 dev 0 function 0 "Intel Dual Band Wireless AC 7260" rev 0x73, msi
ppb2 at pci0 dev 28 function 2 "Intel Bay Trail PCIE" rev 0x0e: msi
pci3 at ppb2 bus 3
re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G
(0x4c00), msi, address c0:3f:d5:6c:ab:2b
rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
ppb3 at pci0 dev 28 function 3 "Intel Bay Trail PCIE" rev 0x0e: msi
pci4 at ppb3 bus 4
pcib0 at pci0 dev 31 function 0 "Intel Bay Trail LPC" rev 0x0e
ichiic0 at pci0 dev 31 function 3 "Intel Bay Trail SMBus" rev 0x0e:
apic 1 int 18
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 4GB DDR3 SDRAM PC3-12800 

mini itx from intel

[frantisek holop]

does anyone happen to have any of these?
http://www.intel.com/content/www/us/en/nuc/nuc-comparison.html

plz send dmesg if possible.

-f
-- 
loose lips sinks ships

Re: doas as root with /sbin/shutdown + related conf syntax query

[Theo Buehler]

On Sat, Sep 19, 2015 at 02:19:19PM +0100, Toby Slight wrote:
> I'm trying to let my user shutdown, reboot and suspend the computer without
> entering a password. This is my doas.conf:
> 
> permit keepenv { ENV PS1 SSH_AUTH_SOCK } :wheel
> permit nopass toby as root cmd /sbin/shutdown
> permit nopass toby as root cmd /sbin/reboot
> permit nopass toby as root cmd /usr/sbin/zzz
> 
> I can suspend successfully, but attempting to shutdown or reboot, returns:
> 
> ksh: shutdown: cannot execute - Permission denied

tedu already answered your question.  Nevertheless let me add two
points:

1. It looks like your user toby belongs to the group wheel, so you can
   communicate to /var/run/apmdev and hence you don't need further
   special privileges to run apm(8) or zzz(8).

2. If you add your user to the 'operator' group, you can run
   shutdown(8) without entering a password as well, so 
 $ shutdown -r now
   will reboot your box and you can halt with `-ph' instead of `-r'.

Thus, the only `doas nopass' rule that is actually needed is the
/sbin/reboot one, should you still want it in view of point 2.

Re: Cheap hardware for router, perhaps fileserver?

[lists]

On Sun, 20 Sep 2015 10:23:13 +0100
Mark Carroll  wrote:

> Many helpful replies so quickly, thank you. It looks like I should plan
> to spend more and stick with x86 if it's so much better supported. The
> mention of Mini-Box rang a bell as I used to have an M200 that worked
> well. I try to avoid diversity in both hardware and software so, if I'm
> spending a bit more anyway, perhaps I should even look out for a system
> whose sibling could replace, for instance, the computer I use for
> streaming TV. My fileserver needs would be modest -- I'm asking little
> in terms of number of clients, reliability, size, throughput, etc. --
> I am just looking to add enough value to justify spending more on a
> 'router', even to the level of Intel NUCs which look pretty good if
> their hardware is solid.
> 
> As background, this OpenBSD effort is also partly about replacing the
> various hardware I already have: nearly ten-year-old desktop machines
> that are on their last legs (replacing parts by cannibalization or
> buying used on eBay) and are enormous, noisy, and power-hungry. (My
> current router is a full-height tower, a server retired from a past
> employer, with one of the first single-core Opterons and the 2.5" drive
> from its mini-ITX predecessor which died!) I figure if I'm reinstalling
> stuff onto new hardware, it's a good time to try out OpenBSD too: if
> nothing else, it makes me actually review configurations instead of just
> copying them over.
> 
> -- Mark
> 
> 

Hi Mark,

Spend a bit more and look around for the Supermicro (Atom or why not
even Xeon CPU, look for the VT-* support as OpenBSD native hypervisor
is coming ahead) offers was going to be my suggestion too, solved it for
me multiple times so far. For me the BMC/IPMI option is indispensable,
with a 3-wire serial cable. Check out for dmesg posts on the mailing
list archive as well, there are pointers. Diversity is not bad, given
you have the resources (time and everything) to get to know the systems
well. ECC is a must for 24/7 systems or reliable use anyways. I'd stick
to reliable 3.5" HDDs and ventilate the system well with low noise
fans, and reusing 2.5" HDDs (in pairs) is OK but not my go to choice.
OpenBSD is a wonderful OS and provides a good foundation to expand
know-how and is very useful in all scenarios.

Regards,
Anton

Re: update/upgrade

[Nick Holland]

On 09/20/15 21:36, Quartz wrote:
>> You think the master builds are done on a machine that is identical to
>> yours at home?
> 
> Obviously not, but that doesn't have any bearing on what I said.

you rejected the right answer for wrong reasons, so what you said was
unclear at best.

>> Build a -stable release on a same platform faster machine.  Now unpack
>> the .tgz files on the target machines, copy in /bsd, /bsd.rd, reboot.
>> ta-da, patched machine.  None of your configuration is touched by this
>> process.
> 
> Maybe I'm unclear on what building -stable actually does. Correct me if 
> I'm wrong, but "world" encompasses a lot more than just the kernel and 
> ramdisk, right? Simply replacing just those two alone isn't fully 
> keeping on top of things.

"world" as you appear to be using it isn't an OpenBSDism, so I would
suggest you start at the top of FAQ5 (very top -- 5.1 might be among the
most important but failed to be understood concepts in OpenBSD), and
start reading.
   http://www.openbsd.org/faq/faq5.html
Your situation is even mentioned...
Reading with an open mind not fogged by other projects uses of various
words and processes or your own preconceptions of how things work is
highly recommended.

When you build a release, you are going through the process used for the
official releases, and generate the entire set of files you see in a
platform release directory on a distribution mirror.

You can then install a new -stable release on your slow hw as fast as
you can copy it over and unpack the tar files, and your downtime is
limited to the time of a reboot.  You can also install these releases on
blank hardware as well.

Nick.

Re: speedup shutdown

[Philip Guenther]

On Sun, Sep 20, 2015 at 7:24 PM, Quartz  wrote:
...
>> "time sh /etc/rc shutdown". See what's still running. kill -HUP everything
>>> except init and your session and see what's still running 5 seconds
>>> later.

Hmm, you truncated the suggested steps...


>> OK I'll try that, thanks.
>
>
> I'm missing something.
>
> Logged in as root, 'sh /etc/rc shutdown' returns instantly and according
> 'ps' everything's still running.

Okay, so it's not some pkg_script that's being slow.  That's good.


> Trying to then kill -HUP half the processes
> doesn't work (they just restart).

Saying "doesn't work" when they're behaving as documented on their
manpages is a bit odd.  Which of those survive after you do the step
that you truncated from the suggestion?  Checking one of my systems,
the answer is "NONE"...

(Why does init do HUP then TERM?  By default, HUP will terminate
logins and most user processes, getting most interactive processes out
of the way while logging and other base and network services are still
operating, so interactive processes can cleanly terminate.  TERM
should then kill the rest, leaving only processes having some sort of
problem (e.g., unresponsive NFS server) or that are badly behaved.)


Philip Guenther

Re: update/upgrade

[Josh Grosse]

On Sun, Sep 20, 2015 at 10:36:12PM -0400, Quartz wrote:
> >Does your embedded storage run NOR/NAND or something like SDHC Memory
> >Cards?
> >
> >If your systems are running SDHC you can easily create clones with a
> >laptop&  the DD utility.
> 
> A couple of them do, but it doesn't matter in this case. The main issue with
> compiling is that it can effectively knock the system offline for hours
> which isn't acceptable. Any process that involves shutting the machine off
> or booting into a separate OS image has the same problem.
> 
> It's just a question of minimizing downtime.

You build a release of -stable on one single platform, such as a workstation,
and then deploy it as a binary update to your production servers.
Build time is then separate from production maintenance windows.

My flight of -stable servers share the same architecture, and I have a single
build machine.  These servers are in redundant configurations using carp(4)
so I am able to perform maintenance without any operational downtime.  

I'll repeat -- without any operational downtime. 

But I have the luxury of deploying redundant systems with carp(4).

The maintenance windows do take about 10 minutes of wall time, because these 
machines are all "embedded" sized -- Alix systems -- and the slowest part of 
the update is untarring filesets onto their compact flash storage devices.
If they had magnetic drives or SSDs the windows would be less than 5 minutes.

Re: speedup shutdown

[Quartz]

Hmm? How about replicate the process and observe the results?


Well, I wasn't sure if that was the exact/entire process or just a summary.


"time

sh /etc/rc shutdown". See what's still running. kill -HUP everything
except init and your session and see what's still running 5 seconds
later.


OK I'll try that, thanks.


I'm missing something.

Logged in as root, 'sh /etc/rc shutdown' returns instantly and according 
'ps' everything's still running. Trying to then kill -HUP half the 
processes doesn't work (they just restart).

Re: update/upgrade

[Quartz]

"world" as you appear to be using it isn't an OpenBSDism,


 ugh. You're right, you're right... I'm also managing several 
FreeBSD projects and I'm getting things mixed up. Let me go through the 
man pages again and try to sort things out in my head.

Re: update/upgrade

[Rob Pierce]

On Sun, Sep 20, 2015 at 10:36:12PM -0400, Quartz wrote:
> >Does your embedded storage run NOR/NAND or something like SDHC Memory
> >Cards?
> >
> >If your systems are running SDHC you can easily create clones with a
> >laptop&  the DD utility.
> 
> A couple of them do, but it doesn't matter in this case. The main issue with
> compiling is that it can effectively knock the system offline for hours
> which isn't acceptable. Any process that involves shutting the machine off
> or booting into a separate OS image has the same problem.
> 
> It's just a question of minimizing downtime.

If availability is critical you might consider redundancy with CARP/pfsync.

Re: speedup shutdown

[Quartz]

Hmm?   How about replicate the process and observe the results?


Well, I wasn't sure if that was the exact/entire process or just a summary.


"time

sh /etc/rc shutdown".  See what's still running.  kill -HUP everything
except init and your session and see what's still running 5 seconds
later.


OK I'll try that, thanks.

Re: update/upgrade

[Quartz]

Does your embedded storage run NOR/NAND or something like SDHC Memory
Cards?

If your systems are running SDHC you can easily create clones with a
laptop&  the DD utility.


A couple of them do, but it doesn't matter in this case. The main issue 
with compiling is that it can effectively knock the system offline for 
hours which isn't acceptable. Any process that involves shutting the 
machine off or booting into a separate OS image has the same problem.


It's just a question of minimizing downtime.

Re: speedup shutdown

[Quartz]

"time sh /etc/rc shutdown". See what's still running. kill -HUP everything

except init and your session and see what's still running 5 seconds
later.


Hmm, you truncated the suggested steps...


You wrote:

"Hmm?   How about replicate the process and observe the results?  "time
sh /etc/rc shutdown".  See what's still running.  kill -HUP everything
except init and your session and see what's still running 5 seconds
later.  Then again with kill -TERM.  Whatever still standing is
slowing you down; for each one figure out whether and when it should
have died."

I took that to mean:

1) run (presumably as root) 'time sh /etc/rc shutdown'
2) check 'ps -aux' to see what's still running
3) 'kill -HUP [PID]' for each of the remaining processes
4) check 'ps -aux' again
5) 'kill -TERM [PID]' for each of the remaining processes
6) check 'ps -aux' again


I appear to be hung up near the beginning. 'sh /etc/rc shutdown' doesn't 
appear to do anything, since it returns instantly and the ps output from 
(2) is identical to ps output from before 'sh /etc/rc shutdown'. (3) 
"doesn't work" in the sense that it doesn't appear to actually stop 
[m]any services (presumably because I didn't do something correctly 
before this point).


Like I said, I'm missing something. There were a couple assumptions in 
there somewhere that I'm not picking up on. What exactly am I supposed 
to do in what order?

Re: update/upgrade

[Quartz]

You think the master builds are done on a machine that is identical to
yours at home?


Obviously not, but that doesn't have any bearing on what I said.



Build a -stable release on a same platform faster machine.  Now unpack
the .tgz files on the target machines, copy in /bsd, /bsd.rd, reboot.
ta-da, patched machine.  None of your configuration is touched by this
process.


Maybe I'm unclear on what building -stable actually does. Correct me if 
I'm wrong, but "world" encompasses a lot more than just the kernel and 
ramdisk, right? Simply replacing just those two alone isn't fully 
keeping on top of things.

Re: update/upgrade

[Josh Grosse]

On Sun, Sep 20, 2015 at 09:36:55PM -0400, Quartz wrote:
> >You think the master builds are done on a machine that is identical to
> >yours at home?
> 
> Obviously not, but that doesn't have any bearing on what I said.
> 
> 
> >Build a -stable release on a same platform faster machine.  Now unpack
> >the .tgz files on the target machines, copy in /bsd, /bsd.rd, reboot.
> >ta-da, patched machine.  None of your configuration is touched by this
> >process.
> 
> Maybe I'm unclear on what building -stable actually does. Correct me if I'm
> wrong, but "world" encompasses a lot more than just the kernel and ramdisk,
> right? Simply replacing just those two alone isn't fully keeping on top of
> things.
 
Please see FAQ 5.4, which articulates how to build a release (-stable, or 
-current).  The definitive documentation is release(8).

Re: update/upgrade

[Patrick Dohman]

> On Sep 20, 2015, at 3:49 PM, Quartz  wrote:
> 
> We have a bunch of low power embedded devices that we'd like to keep 
> reasonably up to date, but the disk space and cpu overhead of tracking 
> -stable is kind of a nonstarter. Is there another/better way of doing things 
> these days? (Other than applying dozens of patches manually).
> 

Does your embedded storage run NOR/NAND or something like SDHC Memory Cards?

If your systems are running SDHC you can easily create clones with a laptop & 
the DD utility.

Regards
Patrick

Re: update/upgrade

[Quartz]

If availability is critical you might consider redundancy with CARP/pfsync.


It's not critical enough to be worth dealing that. Going down for like 
15 minutes is fine, but most of a day is not.


In a perfect world we're looking for an update mechanism similar in 
speed and ease to other OSs where you can run a one liner on the live 
system which automatically downloads and installs a few files and 
reboots. I'm trying to get as close to that as possible without having 
to create and maintain a whole home-grown custom procedure.


It looks like the M:tier thing is pretty close, my only concern is how 
long it'll last before the maintainers lose interest and the project 
gets abandoned.

Re: speedup shutdown

[Philip Guenther]

On Sun, Sep 20, 2015 at 8:10 PM, Quartz  wrote:
 "time sh /etc/rc shutdown". See what's still running. kill -HUP
 everything
>
> except init and your session and see what's still running 5 seconds
> later.
>>
>>
>> Hmm, you truncated the suggested steps...
>
>
> You wrote:
>
> "Hmm?   How about replicate the process and observe the results?  "time
> sh /etc/rc shutdown".  See what's still running.  kill -HUP everything
> except init and your session and see what's still running 5 seconds
> later.  Then again with kill -TERM.  Whatever still standing is
> slowing you down; for each one figure out whether and when it should
> have died."
>
> I took that to mean:
>
> 1) run (presumably as root) 'time sh /etc/rc shutdown'
> 2) check 'ps -aux' to see what's still running
> 3) 'kill -HUP [PID]' for each of the remaining processes
> 4) check 'ps -aux' again
> 5) 'kill -TERM [PID]' for each of the remaining processes
> 6) check 'ps -aux' again

Yes.  Perhaps it isn't clear that I would *expect* stuff to still be
running at step 4, and thus for shutdown like this to take at least 5
seconds.

You said shutdown was taking "a solid 10 seconds", so I was under the
belief that some process was hanging around *past* step 6, and
requiring a SIGKILL to be taken down, but I guess we don't have the
data to conclude that.


> I appear to be hung up near the beginning. 'sh /etc/rc shutdown' doesn't
> appear to do anything, since it returns instantly and the ps output from (2)
> is identical to ps output from before 'sh /etc/rc shutdown'. (3) "doesn't
> work" in the sense that it doesn't appear to actually stop [m]any services
> (presumably because I didn't do something correctly before this point).

It sounds like things are behaving as expected for steps 1-4: shut
down packaged services (none, or they're quick), then shut down
interactive sessions, giving them 5 seconds to do so.

If the next step, the one you didn't describe the results of, killing
daemons with SIGTERM, leaves services running then there may be a bug
in those programs worth fixing.  Or maybe everything dies after the
SIGTERM and it's the kernel's shut down work, flushing stuff to disk
and such that is rounding out the 10 seconds.


Philip Guenther

update/upgrade

[Quartz]

We have a bunch of low power embedded devices that we'd like to keep 
reasonably up to date, but the disk space and cpu overhead of tracking 
-stable is kind of a nonstarter. Is there another/better way of doing 
things these days? (Other than applying dozens of patches manually).

Re: rc.shutdown powerdown

[Fred]

On 09/20/15 21:44, Quartz wrote:

On Sep 20 4:36 PM, Fred wrote:

On 09/20/15 20:58, Quartz wrote:

Powerdown went away in July 2014.


The FAQ needs to be updated then:

http://www.openbsd.org/faq/faq10.html

"rc.shutdown

/etc/rc.shutdown is a script that is run at shutdown. Anything you want
done before the system shuts down should be added to this file. If you
have apm, you can also set "powerdown=YES", which will give you the
equivalent of "shutdown -p".
"


Sorry misread your post.

The following diff removes the misleading entry from faq10:

--- faq10.html  Sun Sep 20 21:50:41 2015
+++ faq10nopower.html   Sun Sep 20 21:52:51 2015
@@ -298,8 +298,6 @@ and adding the daemon name to the pkg_scripts
 
 /etc/rc.shutdown is a script that is run at shutdown. Anything
 you want done before the system shuts down should be added to this file.
-If you have apm, you can also set powerdown=YES, which will
-give you the equivalent of shutdown -p.

 10.8 - I edited /etc/passwd, but the changes didn't seem 
to take

 place. Why?

Re: update/upgrade

[Pedro Tender]

Snapshots?
On Sep 20, 2015 9:54 PM, "Quartz"  wrote:

> We have a bunch of low power embedded devices that we'd like to keep
> reasonably up to date, but the disk space and cpu overhead of tracking
> -stable is kind of a nonstarter. Is there another/better way of doing
> things these days? (Other than applying dozens of patches manually).

Re: update/upgrade

[Quartz]

https://stable.mtier.org/


A cli update program that applies binary patches is pretty much perfect, 
but I'm not sure we want to rely on a 3rd party for that service. (And I 
know that a built-in update program is probably never going to happen).

Re: update/upgrade

[Christian Weisgerber]

On 2015-09-20, Quartz  wrote:

> We have a bunch of low power embedded devices that we'd like to keep 
> reasonably up to date, but the disk space and cpu overhead of tracking 
> -stable is kind of a nonstarter.

You do that part on a bigger box, build releases there, and use
these to update the low power devices.

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

xrandr: Failed to get size of gamma for output default

[Aaron Poffenberger]

I mentioned this in my dmesg for the Thinkpad T450s but thought it might 
also help others who have seen or may later see this issue to pull it 
out as a separate email.


In addition to the xrandr issue below I can't change backlight settings. 
Noting here in case they're related.


$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
  1920x1080  0.00*

$ xbacklight -set 50
No outputs have backlight property

Any thoughts or suggestions?

Cheers,

--Aaron

OpenBSD 5.8-current (GENERIC.MP) #1373: Sat Sep 19 20:30:49 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8255049728 (7872MB)
avail mem = 8000905216 (7630MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbcbfd000 (66 entries)
bios0: vendor LENOVO version "JBET47WW (1.12 )" date 03/10/2015
bios0: LENOVO 20BX001FUS
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT 
SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT TCPA SSDT UEFI MSDM BATB FPDT UEFI

acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 798.28 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT

cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 798.16 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 798.16 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT

cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 798.16 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT

cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS

acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1
acpipwrres1 at acpi0: NVP3, resource for PEG_
acpipwrres2 at acpi0: NVP2, resource for PEG_
acpitz0 at acpi0: critical temperature is 128 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model "45N" serial 12538 type LiP oem "SONY"
acpibat1 at acpi0: BAT1 model "45N1127" serial   420 type LION oem "LGC"
acpiac0 at acpi0: AC unit offline
acpithinkpad0 at acpi0
cpu0: Enhanced SpeedStep 798 MHz: 

Re: speedup shutdown

[Matthew Martin]

On Sep 20, 2015 3:12 PM, "Quartz"  wrote:
>
> I have a machine where tapping the front panel power button correctly
halts and powers off the machine however there's a solid 10 second
delay after I press the button before anything happens. Is there any way to
speed this process up?
>
Hold the button down.

Re: update/upgrade

[Kimmo Paasiala]

On Sun, Sep 20, 2015 at 11:49 PM, Quartz  wrote:
> We have a bunch of low power embedded devices that we'd like to keep
> reasonably up to date, but the disk space and cpu overhead of tracking
> -stable is kind of a nonstarter. Is there another/better way of doing things
> these days? (Other than applying dozens of patches manually).
>

Something like this?

http://www.bsdnow.tv/tutorials/stable-iso

Re: update/upgrade

[Josh Grosse]

On Sun, Sep 20, 2015 at 04:49:45PM -0400, Quartz wrote:
> We have a bunch of low power embedded devices that we'd like to keep
> reasonably up to date, but the disk space and cpu overhead of tracking
> -stable is kind of a nonstarter. Is there another/better way of doing things
> these days? (Other than applying dozens of patches manually).

https://stable.mtier.org/

Re: update/upgrade

[Quartz]

Snapshots?



Something like this?
http://www.bsdnow.tv/tutorials/stable-iso


Well, preferably something that doesn't require the machines to go 
offline for a while.

dmesg (current) Lenovo Thinkpad T450s

[Aaron Poffenberger]

* Notable Issue
  - Suspending now hangs system
- X11 disables correctly and screen goes dark
- Light on power switch begins to blink
- Screen comes back on at one of the consoles
- Can hear fans begin to spin up
- Keyboard unresponsive
- Have to force reboot
- Not a problem with build from 2015-09-16

* Display and X11
  - When X launches at boot the screen initially shows the ThinkPad
logo, repeated across the top and a repeating image of garbage or
a previous X session
- System is set to start X at run time via xdm(1)
  - xbacklight -set 50 returns "No outputs have backlight property"
  - xrandr returns error and partial results:
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
  1920x1080  0.00*
* Keyboard
  - Function keys by default are disabled, have to use Fn key in lower
left corner to activate them
  - F2/F3 (Volume Up/Down) work, though mplayer gets confused about
initial state, has to be unmuted when initial focus passed to
mplayer window to get it right
  - F5/f6 (Brightness control) do nothing
* Suspend/Resume (build 2015-09-16)
  - Resumes but X doesn't come back
  - Same issue reported here
+ https://marc.info/?l=openbsd-misc=143821623332021=2
  - Switching to alternate console via ctrl-alt-fn {1,2,...} works
when Fn-lock is set (Fn-Esc), but is not reliable when you have to
add the Fn key into a function sequence, e.g., Fn-ctrl-alt-fn1.

Frequently I see the esc sequence itself typed instead or I'm able
to switch to an alternate console but then can't get back. Again,
locking the Fn key on resolves this issue.
* Trackpad
  - Works very well, super sensitive to the point that setting
TapButton{1..3} to 0 is the best option.

OpenBSD 5.8-current (GENERIC.MP) #1373: Sat Sep 19 20:30:49 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8255049728 (7872MB)
avail mem = 8000905216 (7630MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbcbfd000 (66 entries)
bios0: vendor LENOVO version "JBET47WW (1.12 )" date 03/10/2015
bios0: LENOVO 20BX001FUS
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT 
SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT TCPA SSDT UEFI MSDM BATB FPDT UEFI

acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 798.28 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT

cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 798.16 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 798.16 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT

cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 798.16 MHz
cpu3: 

Re: update/upgrade

[Pedro Tender]

As it was already stated in @misc, mtier is probably as safe as relying on
openbsd code.
On Sep 20, 2015 10:29 PM, "Quartz"  wrote:

> https://stable.mtier.org/
>>
>
> A cli update program that applies binary patches is pretty much perfect,
> but I'm not sure we want to rely on a 3rd party for that service. (And I
> know that a built-in update program is probably never going to happen).

Suspend Hangs ThinkPad T450s

[Aaron Poffenberger]

Another issue I noted in the ThinkPad dmesg. Pulling out as separate 
request for reference sake.


Suspending now hangs system
 - X11 disables correctly and screen goes dark
 - Light on power switch begins to blink
 - Screen comes back on at one of the consoles
 - Can hear fans begin to spin up
 - Keyboard unresponsive
 - Have to force reboot

This was not a problem with build from 2015-09-16.

Cheers,

--Aaron

OpenBSD 5.8-current (GENERIC.MP) #1373: Sat Sep 19 20:30:49 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8255049728 (7872MB)
avail mem = 8000905216 (7630MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbcbfd000 (66 entries)
bios0: vendor LENOVO version "JBET47WW (1.12 )" date 03/10/2015
bios0: LENOVO 20BX001FUS
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT 
SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT TCPA SSDT UEFI MSDM BATB FPDT UEFI

acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 798.28 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT

cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 798.16 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 798.16 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT

cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 798.16 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT

cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS

acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1
acpipwrres1 at acpi0: NVP3, resource for PEG_
acpipwrres2 at acpi0: NVP2, resource for PEG_
acpitz0 at acpi0: critical temperature is 128 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model "45N" serial 12538 type LiP oem "SONY"
acpibat1 at acpi0: BAT1 model "45N1127" serial   420 type LION oem "LGC"
acpiac0 at acpi0: AC unit offline
acpithinkpad0 at acpi0
cpu0: Enhanced SpeedStep 798 MHz: speeds: 2601, 2600, 2500, 2300, 2100, 
2000, 1800, 1700, 1500, 1400, 1200, 1100, 900, 800, 600, 500 MHz

pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 5G 

Re: Cheap hardware for router, perhaps fileserver?

[Tim Kuijsten]

Op 20-09-15 om 11:23 schreef Mark Carroll:

 even to the level of Intel NUCs which look pretty good if
their hardware is solid.


I've recently installed an Intel NUC NUC5CPYH to be used as a quiet low 
power sftp file server. Support for the nic is recently added and the 
machine works perfect for sftp with only a few users (really not sure 
what the maximum amount of users would be).


http://marc.info/?l=openbsd-misc=144148311202959=2

OT: Exists some problem with dnscrypt-proxy package?

[C.L. Martinez]

Hi all,

 I have installed an openbsd 5.7 VM today to do some tests with pf 
rules. One of the components to I need to enable in this gateway is 
unbound+dnscrypt-proxy.


 I have configured forwarding in unbound.conf:

 forward-zone:
name: "."
forward-addr: 127.0.0.1@4553

 And I have started dnscypt-proxy with the following arguments:

-d --user=_dnscrypt-proxy -a 127.0.0.1:4553 -R dnscrypt.eu-nl -p 
/var/run/dnscrypt-proxy.pid


 Output:

32032 ??  Is  0:00.00 /usr/sbin/ftp-proxy -m 25
32411 ??  Is  0:00.00 /usr/local/sbin/dnscrypt-proxy -d 
--user=_dnscrypt-proxy -a 127.0.0.1:4553 -R dnscrypt.eu-nl -p 
/var/run/dnscrypt-proxy.pid
 5667 ??  I   0:00.03 /usr/local/sbin/dnscrypt-proxy -d 
--user=_dnscrypt-proxy -a 127.0.0.1:4553 -R dnscrypt.eu-nl -p 
/var/run/dnscrypt-proxy.pid

 1256 ??  Is  0:00.00 /usr/sbin/cron
17818 ??  Ss  0:00.12 sshd: root@ttyp0 (sshd)
  527 ??  Is  0:00.05 unbound -c /var/unbound/etc/unbound.conf
30164 p0  Ss  0:00.02 -ksh (ksh)
 7382 p0  R+  0:00.00 ps -xa
16881 C0  Is+ 0:00.00 /usr/libexec/getty std.9600 ttyC0
 3047 C1  Is+ 0:00.00 /usr/libexec/getty std.9600 ttyC1

 And it doesn't works. But if I change unbound's forward section to:

forward-zone:
name: "."
#forward-addr: 127.0.0.1@4553
forward-addr: 8.8.8.8

 Works ok. Removing all forward seciton, unbound works ok also. Then, I 
am doing something wrong but I don't know which.


 Any idea??

 Thanks.

Re: OT: Exists some problem with dnscrypt-proxy package?

[J Sisson]

With dnscrypt-proxy running, can you resolve hostnames?

dig @127.0.0.1 -p 4553 somehostname.com

If you can, do you have "do-not-query-localhost" set to "no" in your
unbound configuration?

On Sun, Sep 20, 2015 at 10:04 AM, C.L. Martinez 
wrote:

> Hi all,
>
>  I have installed an openbsd 5.7 VM today to do some tests with pf rules.
> One of the components to I need to enable in this gateway is
> unbound+dnscrypt-proxy.
>
>  I have configured forwarding in unbound.conf:
>
>  forward-zone:
> name: "."
> forward-addr: 127.0.0.1@4553
>
>  And I have started dnscypt-proxy with the following arguments:
>
> -d --user=_dnscrypt-proxy -a 127.0.0.1:4553 -R dnscrypt.eu-nl -p
> /var/run/dnscrypt-proxy.pid
>
>  Output:
>
> 32032 ??  Is  0:00.00 /usr/sbin/ftp-proxy -m 25
> 32411 ??  Is  0:00.00 /usr/local/sbin/dnscrypt-proxy -d
> --user=_dnscrypt-proxy -a 127.0.0.1:4553 -R dnscrypt.eu-nl -p
> /var/run/dnscrypt-proxy.pid
>  5667 ??  I   0:00.03 /usr/local/sbin/dnscrypt-proxy -d
> --user=_dnscrypt-proxy -a 127.0.0.1:4553 -R dnscrypt.eu-nl -p
> /var/run/dnscrypt-proxy.pid
>  1256 ??  Is  0:00.00 /usr/sbin/cron
> 17818 ??  Ss  0:00.12 sshd: root@ttyp0 (sshd)
>   527 ??  Is  0:00.05 unbound -c /var/unbound/etc/unbound.conf
> 30164 p0  Ss  0:00.02 -ksh (ksh)
>  7382 p0  R+  0:00.00 ps -xa
> 16881 C0  Is+ 0:00.00 /usr/libexec/getty std.9600 ttyC0
>  3047 C1  Is+ 0:00.00 /usr/libexec/getty std.9600 ttyC1
>
>  And it doesn't works. But if I change unbound's forward section to:
>
> forward-zone:
> name: "."
> #forward-addr: 127.0.0.1@4553
> forward-addr: 8.8.8.8
>
>  Works ok. Removing all forward seciton, unbound works ok also. Then, I am
> doing something wrong but I don't know which.
>
>  Any idea??
>
>  Thanks.
>
>


-- 
"BSD is what happens when Unix programmers port Unix to the x86.
Linux is what happens when x86 programmers write a Unix-like.
Windows is what happens when x86 programmers run all of their
programming textbooks through a blender, eat the ground up
remains of the text, and then code up what they can read in the
toilet 3 days later."

Re: audio codec RealTek ALC3263

[Remi Locherer]

On Sun, Sep 20, 2015 at 05:45:08PM +0200, Alexandre Ratchov wrote:
> On Sat, Sep 19, 2015 at 10:59:53PM +0200, Remi Locherer wrote:
> > azalia0 at pci0 dev 3 function 0 "Intel Core 5G HD Audio" rev 0x09: msi
> > azalia_reset: resetting
> > azalia_reset: reset counter = 5000
> > azalia_reset: reset counter = 5000
> > azalia0: host: High Definition Audio rev. 1.0
> > azalia0: host: 3 output, 0 input, and 0 bidi streams
> > azalia0: found a codec at #0
> > azalia_init_corb: CORB allocation succeeded.
> > azalia_init_corb: CORBWP=0; size=256
> > azalia_init_rirb: RIRB allocation succeeded.
> > azalia_init_rirb: RIRBRP=0, size=256
> > azalia0: RIRB time out
> 
> This could be caused by the no-snoop setting. Does this improve
> things?
> 
> Index: azalia.c
> ===
> RCS file: /cvs/src/sys/dev/pci/azalia.c,v
> retrieving revision 1.222
> diff -u -p -u -p -r1.222 azalia.c
> --- azalia.c  29 Jul 2015 08:06:29 -  1.222
> +++ azalia.c  20 Sep 2015 15:41:40 -
> @@ -460,6 +460,7 @@ azalia_configure_pci(azalia_t *az)
>   case PCI_PRODUCT_INTEL_9SERIES_HDA:
>   case PCI_PRODUCT_INTEL_9SERIES_LP_HDA:
>   case PCI_PRODUCT_INTEL_BAYTRAIL_HDA:
> + case PCI_PRODUCT_INTEL_CORE5G_HDA_1:
>   reg = azalia_pci_read(az->pc, az->tag,
>   INTEL_PCIE_NOSNOOP_REG);
>   reg &= INTEL_PCIE_NOSNOOP_MASK;
 
Should I try this patch after the result from the other patch after
a cold boot?

https://marc.info/?l=openbsd-misc=144277570223298=2

speedup shutdown

[Quartz]

I have a machine where tapping the front panel power button correctly 
halts and powers off the machine however there's a solid 10 second 
delay after I press the button before anything happens. Is there any way 
to speed this process up?

Re: doas as root with /sbin/shutdown + related conf syntax query

[Toby Slight]

On 20 September 2015 at 14:51, Theo Buehler  wrote:

> On Sat, Sep 19, 2015 at 02:19:19PM +0100, Toby Slight wrote:
> > I'm trying to let my user shutdown, reboot and suspend the computer
> without
> > entering a password. This is my doas.conf:
> >
> > permit keepenv { ENV PS1 SSH_AUTH_SOCK } :wheel
> > permit nopass toby as root cmd /sbin/shutdown
> > permit nopass toby as root cmd /sbin/reboot
> > permit nopass toby as root cmd /usr/sbin/zzz
> >
> > I can suspend successfully, but attempting to shutdown or reboot,
> returns:
> >
> > ksh: shutdown: cannot execute - Permission denied
>
> tedu already answered your question.  Nevertheless let me add two
> points:
>

Yeah - I replied a couple of times in haste from gmail, and thus the rest
of the conversation accidentally just got send to Tedu and not the list
(gmail defaults to reply to only the author of the last message). Doh!


>
> 1. It looks like your user toby belongs to the group wheel, so you can
>communicate to /var/run/apmdev and hence you don't need further
>special privileges to run apm(8) or zzz(8).
>
> 2. If you add your user to the 'operator' group, you can run
>shutdown(8) without entering a password as well, so
>  $ shutdown -r now
>will reboot your box and you can halt with `-ph' instead of `-r'.
>
> Thus, the only `doas nopass' rule that is actually needed is the
> /sbin/reboot one, should you still want it in view of point 2.
>

Many thanks for the extra tips. I've learn so much from this thread :-)

For reference here is the bit that I forgot to cc the list on:

On 19 September 2015 at 15:50, Ted Unangst  wrote:
>
>
> you have to run the doas command. it's not part of the shell.
>
> doas /sbin/shutdown
>

How come for zzz, I can run it as my user without pre-pending doas, and it
executes without asking for my password? Do executable in /sbin require
doas pre-pended but /usr/sbin don't? Also, even when I run doas shutdown,
it still asks for my password

Toby Slight wrote:
> On 19 September 2015 at 15:50, Ted Unangst  wrote:
> >
> >
> > you have to run the doas command. it's not part of the shell.
> >
> > doas /sbin/shutdown
> >
>
> How come for zzz, I can run it as my user without pre-pending doas, and it
> executes without asking for my password? Do executable in /sbin require
> doas pre-pended but /usr/sbin don't? Also, even when I run doas shutdown,
> it still asks for my password

anybody can run zzz. most things in /sbin are normal too, but shutdown is
special. if your doas.conf file says only /sbin/shutdown has no password,
then you have to type the path. or change the config to remove the path.

On 19 September 2015 at 17:58, Ted Unangst  wrote:
>
>
> anybody can run zzz. most things in /sbin are normal too, but shutdown is
> special. if your doas.conf file says only /sbin/shutdown has no password,
> then you have to type the path. or change the config to remove the path.
>

Ha - no way! I had no idea! All this time I assumed it required privilege
escalation. Did it used to? Perhaps just a hangover assumption from my
Linux days...

So it's the giving it the full path, or removing it from doas.conf that
does the trick, eh? Nice one - I shall give it whirl when I get home :-)
Thanks for the prompt responses and help.

I'm still somewhat curious though - how and why is shutdown special? What
about reboot? Also, is there a way to specify multiple commands in a single
line, or does every cmd need a separate line?

Toby Slight wrote:
> I'm still somewhat curious though - how and why is shutdown special? What
> about reboot? Also, is there a way to specify multiple commands in a
single
> line, or does every cmd need a separate line?

shutdown is setuid. just look at ls -l /sbin.

it has to be one command per line in doas.conf.

-- 
0x2b || !0x2b

Re: OT: Exists some problem with dnscrypt-proxy package?

[Raf Czlonka]

On Sun, Sep 20, 2015 at 06:04:19PM BST, C.L. Martinez wrote:
> Hi all,
> 
>  I have installed an openbsd 5.7 VM today to do some tests with pf rules.
> One of the components to I need to enable in this gateway is
> unbound+dnscrypt-proxy.
> 
>  I have configured forwarding in unbound.conf:
> 
>  forward-zone:
> name: "."
> forward-addr: 127.0.0.1@4553
> 
>  And I have started dnscypt-proxy with the following arguments:
> 
> -d --user=_dnscrypt-proxy -a 127.0.0.1:4553 -R dnscrypt.eu-nl -p
> /var/run/dnscrypt-proxy.pid
> 
>  Output:
> 
> 32032 ??  Is  0:00.00 /usr/sbin/ftp-proxy -m 25
> 32411 ??  Is  0:00.00 /usr/local/sbin/dnscrypt-proxy -d
> --user=_dnscrypt-proxy -a 127.0.0.1:4553 -R dnscrypt.eu-nl -p
> /var/run/dnscrypt-proxy.pid
>  5667 ??  I   0:00.03 /usr/local/sbin/dnscrypt-proxy -d
> --user=_dnscrypt-proxy -a 127.0.0.1:4553 -R dnscrypt.eu-nl -p
> /var/run/dnscrypt-proxy.pid
>  1256 ??  Is  0:00.00 /usr/sbin/cron
> 17818 ??  Ss  0:00.12 sshd: root@ttyp0 (sshd)
>   527 ??  Is  0:00.05 unbound -c /var/unbound/etc/unbound.conf
> 30164 p0  Ss  0:00.02 -ksh (ksh)
>  7382 p0  R+  0:00.00 ps -xa
> 16881 C0  Is+ 0:00.00 /usr/libexec/getty std.9600 ttyC0
>  3047 C1  Is+ 0:00.00 /usr/libexec/getty std.9600 ttyC1
> 
>  And it doesn't works. But if I change unbound's forward section to:
> 
> forward-zone:
> name: "."
> #forward-addr: 127.0.0.1@4553
> forward-addr: 8.8.8.8
> 
>  Works ok. Removing all forward seciton, unbound works ok also. Then, I am
> doing something wrong but I don't know which.
> 
>  Any idea??

dnscypt-proxy, being a package daemon, is started *after* unbound (base
early daemon)?

Raf

Re: rc.shutdown powerdown

[Quartz]

Powerdown went away in July 2014.


The FAQ needs to be updated then:

http://www.openbsd.org/faq/faq10.html

"rc.shutdown

/etc/rc.shutdown is a script that is run at shutdown. Anything you want 
done before the system shuts down should be added to this file. If you 
have apm, you can also set "powerdown=YES", which will give you the 
equivalent of "shutdown -p".

"

Re: rc.shutdown powerdown

[Quartz]

On Sep 20 4:36 PM, Fred wrote:

On 09/20/15 20:58, Quartz wrote:

Powerdown went away in July 2014.


The FAQ needs to be updated then:

http://www.openbsd.org/faq/faq10.html

"rc.shutdown

/etc/rc.shutdown is a script that is run at shutdown. Anything you want
done before the system shuts down should be added to this file. If you
have apm, you can also set "powerdown=YES", which will give you the
equivalent of "shutdown -p".
"



rc.shutdown is still needed if you need to run tasks before the
reboot(8), halt(8), or when init(8) is signalled to shut the system down.


I'm aware of what rc.shutdown is for. My issue is that the FAQ still 
suggests people add the poweroff parameter.

rc.shutdown powerdown

[Quartz]

Can someone explain in better detail what exactly the "powerdown=" line 
in rc.shutdown does? I have a few machines that range from full apm/acpi 
support to hardly none, but that line doesn't seem to affect anything on 
any of them, regardless what it's set to or if it's omitted completely.

Re: rc.shutdown powerdown

[Brian Conway]

Powerdown went away in July 2014.

https://marc.info/?l=openbsd-cvs=140532869022004=2

Also, rc.shutdown doesn't exist by default anymore (/etc/examples).

Brian Conway
Software Engineer, Owner
RCE Software, LLC


On Sun, Sep 20, 2015 at 1:01 PM, Quartz  wrote:
> Can someone explain in better detail what exactly the "powerdown=" line in
> rc.shutdown does? I have a few machines that range from full apm/acpi
> support to hardly none, but that line doesn't seem to affect anything on any
> of them, regardless what it's set to or if it's omitted completely.

Re: urtwn driver has problems

[Alan Corey]

Any chance of the stability fixes getting released as an official
patch?  The problems go back to at least 5.0.  I just mostly finished
a clean install of 5.7 on a new drive in my 5.2 machine.  I've got
another new 1 TB drive for my 5.0 machine.  The Firefox 5.0 in this is
getting ancient anyway.