Re: install(1) fails when reading from stdin

2017-09-28 Thread Matthias Kilian
On Tue, Sep 26, 2017 at 02:59:30PM +, Alfred Morgan wrote:
> Of course I can cat > a/b/myfile && chown me a/b/myfile && chgrp me
> a/b/myfile && chmod 0440 a/b/myfile but I know there is a stock command
> that fits the bill (install) but then I find to my disappointment that
> install can't accept stdin. What a let down and it feels anti-unix to me.

Please read the very last line of the DESCRIPTION section of
install(1) and then use install(1) followed by cat(1).

There's no point in adding features to  install(1).

Ciao,
Kili



X dont work

2017-09-28 Thread dieklu
SENDBUG: -*- sendbug -*-
SENDBUG: Lines starting with `SENDBUG' will be removed automatically.
SENDBUG:
SENDBUG: Choose from the following categories:
SENDBUG:
SENDBUG: system user library documentation kernel alpha amd64 arm hppa
i386 m88k mips64 powerpc sh sparc sparc64 vax
SENDBUG:
SENDBUG:
To: bugs@openbsd.org
Subject:X do not work
From: root
Cc: root
Reply-To: root>Synopsis:X do not work
>Category:Xwindow
>Environment:
System  : OpenBSD 6.1
Details : OpenBSD 6.1 (GENERIC.MP) #1: Mon Sep 18 21:02:53 CEST 2017
r...@foo.my.domain:/usr/src/sys/arch/i386/compile/GENERIC.MP
Architecture: OpenBSD.i386
Machine : i386
>Description:
I try to start Xwindow via X or startx or startkde or how ever and the
screen
goes away and thats where it hang.
>How-To-Repeat:
X, startx or startkde or how you start X
>Fix:
SENDBUG:
dmesg, pcidump, acpidump and usbdevs are attached.
SENDBUG: Feel free to delete or use the -D flag if they contain sensitive
information.dmesg:
OpenBSD 6.1 (GENERIC.MP) #1: Mon Sep 18 21:02:53 CEST 2017
r...@foo.my.domain:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Pentium(R) Dual-Core CPU T4300 @ 2.10GHz ("GenuineIntel" 686-class)
2.10 GHz
cpu0:
FPU,V86,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,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,XSAVE,LAHF,PERF,SENSOR
real mem  = 3149058048 (3003MB)
avail mem = 3076022272 (2933MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 10/27/09, BIOS32 rev. 0 @ 0xfdbe0, SMBIOS rev.
2.5 @ 0xbbebf000 (44 entries)
bios0: vendor Phoenix Technologies LTD version "1.02.28" date 10/27/2009
bios0: Wortmann AG MOBILE 2510
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET MCFG APIC SLIC BOOT SSDT SSDT SSDT
acpi0: wakeup devices P0P2(S4) PEGP(S4) P0P1(S4) USB0(S3) USB1(S3)
USB2(S3) USBR(S3) EHC1(S3) USB3(S3) USB4(S3) USB5(S3) EHC2(S3) HDEF(S3)
PXSX(S3) RP01(S3) PSL1(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Pentium(R) Dual-Core CPU T4300 @ 2.10GHz ("GenuineIntel" 686-class)
2.10 GHz
cpu1:
FPU,V86,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,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,XSAVE,LAHF,PERF,SENSOR
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (P0P2)
acpiprt2 at acpi0: bus 10 (P0P1)
acpiprt3 at acpi0: bus 2 (RP01)
acpiprt4 at acpi0: bus 4 (RP02)
acpiprt5 at acpi0: bus 6 (RP03)
acpiprt6 at acpi0: bus 8 (RP04)
acpiprt7 at acpi0: bus 9 (RP05)
acpiec0 at acpi0
acpicpu0 at acpi0: C1(@1 halt!), PSS
acpicpu1 at acpi0: C1(@1 halt!), PSS
acpitz0 at acpi0: critical temperature is 108 degC
"PNP0303" at acpi0 not configured
"PNP0F13" at acpi0 not configured
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT0 not present
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
"pnp0c14" at acpi0 not configured
acpivideo0 at acpi0: VGA_
acpivout0 at acpivideo0: LCD_
bios0: ROM list: 0xc/0x1! 0xd/0x1000
cpu0: Enhanced SpeedStep 2095 MHz: speeds: 2100, 1600, 1200 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
0:28:1: bridge mem address conflict 0xb800/0x400
0:28:2: bridge mem address conflict 0xb000/0x400
pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07
ppb0 at pci0 dev 1 function 0 "Intel GM45 PCIE" rev 0x07: apic 2 int 16
pci1 at ppb0 bus 1
inteldrm0 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0: msi
inteldrm0: 1280x800, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured
uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 2 int
16
uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 2 int
21
uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 2 int
19
ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x03: apic 2 int
19
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 82801I HD Audio" rev 0x03: msi
azalia0: codecs: Realtek ALC662, Intel/0x2802, using Realtek ALC662
audio0 at azalia0
ppb1 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x03: apic 2 int
17
pci2 at ppb1 bus 2
iwn0 at pci2 dev 0 function 0 "Intel 

Re: Crash if net.pipex enabled and traffic on OpenVPN network

2017-09-28 Thread Daniel Stocker
Kernel panic if the pipex is activated in the kernel and traffic is 
sent

or received on a tun interface of an OpenVPN network. The machine is a
PC Engine APU 2c4.


Can you try -current?
There have been a couple of fixes applied to pipex since 6.1.


haven't been able to reproduce the crash, neither on 6.1 than on 
current.


- apu2
- openvpn installed
- basic configuration applied
- pipex enabled
- ping tunX

regards
daniel



Re: Crash if net.pipex enabled and traffic on OpenVPN network

2017-09-28 Thread Stefan Sperling
On Wed, Sep 27, 2017 at 10:32:51PM +0200, Sébastien Douche wrote:
> >Synopsis: Crash if net.pipex enabled and traffic on OpenVPN network
> >Category: amd64
> >Environment:
>   System  : OpenBSD 6.1
>   Details : OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr  1 13:45:56
>   MDT 2017
>
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 
>   Architecture: OpenBSD.amd64
>   Machine : amd64
> >Description:
> Kernel panic if the pipex is activated in the kernel and traffic is sent
> or received on a tun interface of an OpenVPN network. The machine is a
> PC Engine APU 2c4.

Can you try -current?
There have been a couple of fixes applied to pipex since 6.1.