Re: httpd with multiple php-fpm pools in separate chroots
On 2020-01-04 09:21, Stuart Henderson wrote: On 2020-01-04, Nazar Zhuk wrote: I get SCRIPT_FILENAME passed from httpd relative to httpd chroot (/site1/htdocs/... ) and PHP being chrooted into /var/www/site1 needs that to be relative to it's own chroot (/htdocs/...). httpd is a bit inflexible (intentionally, I think). Can you work around it with ln -s . /var/www/site1/site1 ? Yes, this works, thanks. Is this intentional though, or is it that this use case hasn't been fully considered yet? Separate chroots for different FastCGI processes seems like a good idea to isolate those processes from each other. This could be configured with something like: fastcgi strip similar to how "request strip" works. I can write a patch if this is something the maintainers would be interested in adding. -- Nazar
Re: But there is Fossil...
>I am running Fossil to synchronize my ports work on >laptop and computer and I am amazed how easy it is, >how I wish I had my own domain to share my work >(both finished and WIP) to public... wow, you don't even have your own domain. you sound poor. that makes it easy to guess you don't know what it takes to run a large project where hundreds of people directly engage in the repository, and many thousands more observe. so you simply have no scope. you don't understand. you are utterly clueless what it takes to get to scale. so you don't know what you are talking about, and yet you show up here to preach. why don't you walk into the jungle and find some people to prosthelytize to? i'm going to guess that means go west. wow this is going downhill. random solo-repo people telling us what to do when Chuck Cranor and I started this whole export-the-repo model. get some perspective dude, hopefully in the jungle.
Re: But there is Fossil...
On 2020/01/05 00:33, go...@disroot.org wrote: > January 5, 2020 2:24 AM, "Roderick" wrote: > > > On Sun, 5 Jan 2020, go...@disroot.org wrote: > > > >> so I don't understand what's wrong with FreeBSD and OpenBSD. > > > > I do not see a problem in CVS. > > Sure, but I started this thread because of OpenBSD's plan > to migrate to Git. > What plan?
Re: But there is Fossil...
On Sun, Jan 05, 2020 at 12:33:58AM +, go...@disroot.org wrote: > January 5, 2020 2:24 AM, "Roderick" wrote: > > > On Sun, 5 Jan 2020, go...@disroot.org wrote: > > > >> so I don't understand what's wrong with FreeBSD and OpenBSD. > > > > I do not see a problem in CVS. > > Sure, but I started this thread because of OpenBSD's plan > to migrate to Git. Stop posting please.
Re: But there is Fossil...
January 5, 2020 2:24 AM, "Roderick" wrote: > On Sun, 5 Jan 2020, go...@disroot.org wrote: > >> so I don't understand what's wrong with FreeBSD and OpenBSD. > > I do not see a problem in CVS. Sure, but I started this thread because of OpenBSD's plan to migrate to Git.
Re: Request for recommendation - encryption and signature for file backup
On Sat, 4 Jan 2020, Philippe Meunier wrote: > Roderick wrote: > >I do use openssl for encrypting files in my laptop. > > So do I. I only encrypt the 0.001% of files that are really important and > then those files are encrypted on my computer too, not just on the backup > system [...] I have an encrypted partition, that I mount only when necessary. Perhaps that is also an alternative for Aham: mount, send backup, umount. Rodrigo
Re: But there is Fossil...
On Sun, 5 Jan 2020, go...@disroot.org wrote: > so I don't understand what's wrong with FreeBSD and OpenBSD. I do not see a problem in CVS.
Re: But there is Fossil...
January 4, 2020 10:36 PM, "Roderick" wrote: > On Sat, 4 Jan 2020, Karel Gardas wrote: > >> Fossil is superfine and I'd like it for various reasons too, but >> unfortunately >> it does not scale to the OpenBSD repo size well. >> >> As a test, you can try and clone fossil repo of NetBSD and I'm sure you will >> find out quickly why people are working on GoT and OpenGIT. > > Perhaps no test necessary, but to read this: > > http://fossil-scm.org/home/technote/be8f2f3447ef2ea3344f8058b6733aa08c08336f > Thank you, this was a really nice read and once again I am sure that GoT and OpenGit are ridiculous, that issue in Fossil should be fixed soon, so I don't understand what's wrong with FreeBSD and OpenBSD. > But is there realy a need to substitute CVS? > > And why should be any repository Git or Got like Git? Because any script > must be python? > > And yes, I also like fossil very much. > > Rodrigo
Re: panic: kernel diagnostic assertion in nd6.c on 6.6-stable amd64
On 1/4/2020 5:46 PM, Ben Lee wrote: Hi, I have an amd64 system that I am using as a router/firewall for my home network running OpenBSD 6.6-stable with the latest syspatches. I have been running it without problems in an IPv4-only configuration. Recently, I decided I wanted to experiment with running a dual stack IPv4 and IPv6 network. I think I have successfully added IPv6 to my configuration which seemed to be functioning correctly to the best of my knowledge, but I have started to encounter kernel panics that crash to the ddb debugger after about 12 hours of uptime. I believe the panics might be specifically occurring when the DHCPv6 lease expires or renews on my external interface and the IPv6 routing table is updated. The panics go away when I reverted back to my IPv4-only configuration so I believe the panics are specific to IPv6. I have been troubleshooting and researching and for the past week or so and I thought I would check to see if some more experienced OpenBSD users might have some advice on how to proceed with troubleshooting. At the end of this email, I have included the relevant section from /var/run/dmesg.boot related to one instance of the panic. It includes the boot messages, panic message, trace, and the output of ps I ran in ddb after the panic. I did find a similar bug report in the mail archive for openbsd-bugs that looks like it was unfortunately not resolved: https://marc.info/?l=openbsd-bugs=152587044611044=2 Some more info about my configuration that I think may be relevant: My ISP uses DHCPv6 prefix delegation to distribute IPv6 addresses so I used dhcpcd from ports installed using pkg_add. I used rad for router advertisements on my internal interfaces and I am using SLAAC to auto-configure IPv6 addresses. My system has 6 Intel NICs, em[0-5], and I also have 4 VLANs vlan[0-3] on em5 that I am using for my wireless AP. em0 is the external interface connected to my cable modem. em[1-5] are my internal interfaces. em[1-3] are each connected to separate computers, em4 is unconnected, and em5 and vlan[0-3] are connected to my wireless AP. The only other observation I had that might be related to the panic is regarding the "ndp info overwritten" and "cannot forward src" lines in my dmesg. The "ndp info overwritten" lines correspond to interfaces that were connected to devices/hosts that powered on at the time of the panic while I think that the "cannot forward src" messages correspond to em2 and em3 which were connected to computers that were powered off at the time of the panic, but were previously powered on to test if they were receiving IPv6 addresses. I am wondering if the computers being powered off at the time of the DHCPv6 lease update is triggering the panic and I think I might test this by only enabling IPv6 on em5 and vlan[0-3] which are connected to my wireless AP is always on. I would be happy to provide any other relevant info that I may have omitted. Thanks for reading. Ben ## OpenBSD 6.6 (GENERIC.MP) #3: Thu Nov 21 03:20:01 MST 2019 r...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4192743424 (3998MB) avail mem = 4052963328 (3865MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x8d317000 (85 entries) bios0: vendor American Megatrends Inc. version "5.12" date 07/08/2019 bios0: Protectli FW6 acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S5 acpi0: tables DSDT FACP APIC FPDT MCFG SSDT FIDT SSDT HPET SSDT SSDT UEFI SSDT LPIT WSMT SSDT SSDT SSDT SSDT DBGP DBG2 BGRT DMAR ASF! acpi0: wakeup devices PS2K(S0) PS2M(S0) RP09(S0) PXSX(S0) RP10(S0) PXSX(S0) RP11(S0) PXSX(S0) RP12(S0) PXSX(S0) RP13(S0) PXSX(S0) RP01(S0) PXSX(S0) RP02(S0) PXSX(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 3865U @ 1.80GHz, 1696.58 MHz, 06-8e-09 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,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,SMEP,ERMS,INVPCID,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN 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 24MHz 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) Celeron(R) CPU 3865U @ 1.80GHz, 1696.06 MHz, 06-8e-09 cpu1:
panic: kernel diagnostic assertion in nd6.c on 6.6-stable amd64
Hi, I have an amd64 system that I am using as a router/firewall for my home network running OpenBSD 6.6-stable with the latest syspatches. I have been running it without problems in an IPv4-only configuration. Recently, I decided I wanted to experiment with running a dual stack IPv4 and IPv6 network. I think I have successfully added IPv6 to my configuration which seemed to be functioning correctly to the best of my knowledge, but I have started to encounter kernel panics that crash to the ddb debugger after about 12 hours of uptime. I believe the panics might be specifically occurring when the DHCPv6 lease expires or renews on my external interface and the IPv6 routing table is updated. The panics go away when I reverted back to my IPv4-only configuration so I believe the panics are specific to IPv6. I have been troubleshooting and researching and for the past week or so and I thought I would check to see if some more experienced OpenBSD users might have some advice on how to proceed with troubleshooting. At the end of this email, I have included the relevant section from /var/run/dmesg.boot related to one instance of the panic. It includes the boot messages, panic message, trace, and the output of ps I ran in ddb after the panic. I did find a similar bug report in the mail archive for openbsd-bugs that looks like it was unfortunately not resolved: https://marc.info/?l=openbsd-bugs=152587044611044=2 Some more info about my configuration that I think may be relevant: My ISP uses DHCPv6 prefix delegation to distribute IPv6 addresses so I used dhcpcd from ports installed using pkg_add. I used rad for router advertisements on my internal interfaces and I am using SLAAC to auto-configure IPv6 addresses. My system has 6 Intel NICs, em[0-5], and I also have 4 VLANs vlan[0-3] on em5 that I am using for my wireless AP. em0 is the external interface connected to my cable modem. em[1-5] are my internal interfaces. em[1-3] are each connected to separate computers, em4 is unconnected, and em5 and vlan[0-3] are connected to my wireless AP. The only other observation I had that might be related to the panic is regarding the "ndp info overwritten" and "cannot forward src" lines in my dmesg. The "ndp info overwritten" lines correspond to interfaces that were connected to devices/hosts that powered on at the time of the panic while I think that the "cannot forward src" messages correspond to em2 and em3 which were connected to computers that were powered off at the time of the panic, but were previously powered on to test if they were receiving IPv6 addresses. I am wondering if the computers being powered off at the time of the DHCPv6 lease update is triggering the panic and I think I might test this by only enabling IPv6 on em5 and vlan[0-3] which are connected to my wireless AP is always on. I would be happy to provide any other relevant info that I may have omitted. Thanks for reading. Ben ## OpenBSD 6.6 (GENERIC.MP) #3: Thu Nov 21 03:20:01 MST 2019 r...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4192743424 (3998MB) avail mem = 4052963328 (3865MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x8d317000 (85 entries) bios0: vendor American Megatrends Inc. version "5.12" date 07/08/2019 bios0: Protectli FW6 acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S5 acpi0: tables DSDT FACP APIC FPDT MCFG SSDT FIDT SSDT HPET SSDT SSDT UEFI SSDT LPIT WSMT SSDT SSDT SSDT SSDT DBGP DBG2 BGRT DMAR ASF! acpi0: wakeup devices PS2K(S0) PS2M(S0) RP09(S0) PXSX(S0) RP10(S0) PXSX(S0) RP11(S0) PXSX(S0) RP12(S0) PXSX(S0) RP13(S0) PXSX(S0) RP01(S0) PXSX(S0) RP02(S0) PXSX(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 3865U @ 1.80GHz, 1696.58 MHz, 06-8e-09 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,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,SMEP,ERMS,INVPCID,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN 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 24MHz 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) Celeron(R) CPU 3865U @ 1.80GHz, 1696.06 MHz, 06-8e-09 cpu1:
[ANN] portable cwm 6.6
Hello, today I'm proud to release portable cwm 6.6. Portable cwm is a minor modification of the cwm version in OpenBSD CVS with a portable Makefile and a few compatibility features. It has been built successfully on OpenBSD, NetBSD, FreeBSD, OS X 10.9 and Linux. This port requires pkg-config, Xft, Xinerama and Xrandr. The included Makefile should work with both GNU make and BSD make. This version actively tracks changes in the OpenBSD CVS repository. Releases are roughly coordinated with OpenBSD releases. The source can be found at https://github.com/leahneukirchen/cwm A changelog can be found at https://github.com/leahneukirchen/cwm/blob/linux/README https://leahneukirchen.org/releases/cwm-6.6.tar.gz https://leahneukirchen.org/releases/cwm-6.6.tar.gz.asc https://leahneukirchen.org/releases/cwm-6.6.tar.gz.sig Releases are also signed with signify(1) using http://leahneukirchen.org/releases/cwm.pub namely: RWTdOib0PoIM0pmDAPnV2S9/AMRqTOVfTY/KAkFemdH13cqBDHdduTas -- Leah Neukirchenhttps://leahneukirchen.org/ 223d086dbebfb2f35f05af0c72c3d1b04fdd341123121c65105524ebd605655c cwm-6.6.tar.gz 3b42861ff403cfaf488b66b8b67c7f3f7bfb8247b23342f8bd0c89403fc35a0f cwm-6.6.tar.gz.asc 0bfe801679c138652125c1ef329916b65dea4f2663f665d7424ef7d178821a26 cwm-6.6.tar.gz.sig
Re: But there is Fossil...
On Sat, 4 Jan 2020, Karel Gardas wrote: > Fossil is superfine and I'd like it for various reasons too, but unfortunately > it does not scale to the OpenBSD repo size well. > > As a test, you can try and clone fossil repo of NetBSD and I'm sure you will > find out quickly why people are working on GoT and OpenGIT. Perhaps no test necessary, but to read this: http://fossil-scm.org/home/technote/be8f2f3447ef2ea3344f8058b6733aa08c08336f But is there realy a need to substitute CVS? And why should be any repository Git or Got like Git? Because any script must be python? And yes, I also like fossil very much. Rodrigo
panic: kernel diagnostic assertion in nd6.c on 6.6-stable amd64
Hi, I have an amd64 system that I am using as a router/firewall for my home network running OpenBSD 6.6-stable with the latest syspatches. I have been running it without problems in an IPv4-only configuration. Recently, I decided I wanted to experiment with running a dual stack IPv4 and IPv6 network. I think I have successfully added IPv6 to my configuration which seemed to be functioning correctly to the best of my knowledge, but I have started to encounter kernel panics that crash to the ddb debugger after about 12 hours of uptime. I believe the panics might be specifically occurring when the DHCPv6 lease expires or renews on my external interface and the IPv6 routing table is updated. The panics go away when I reverted back to my IPv4-only configuration so I believe the panics are specific to IPv6. I have been troubleshooting and researching and for the past week or so and I thought I would check to see if some more experienced OpenBSD users might have some advice on how to proceed with troubleshooting. At the end of this email, I have included the relevant section from /var/run/dmesg.boot related to one instance of the panic. It includes the boot messages, panic message, trace, and the output of ps I ran in ddb after the panic. I did find a similar bug report in the mail archive for openbsd-bugs that looks like it was unfortunately not resolved: https://marc.info/?l=openbsd-bugs=152587044611044=2 Some more info about my configuration that I think may be relevant: My ISP uses DHCPv6 prefix delegation to distribute IPv6 addresses so I used dhcpcd from ports installed using pkg_add. I used rad for router advertisements on my internal interfaces and I am using SLAAC to auto-configure IPv6 addresses. My system has 6 Intel NICs, em[0-5], and I also have 4 VLANs vlan[0-3] on em5 that I am using for my wireless AP. em0 is the external interface connected to my cable modem. em[1-5] are my internal interfaces. em[1-3] are each connected to separate computers, em4 is unconnected, and em5 and vlan[0-3] are connected to my wireless AP. The only other observation I had that might be related to the panic is regarding the "ndp info overwritten" and "cannot forward src" lines in my dmesg. The "ndp info overwritten" lines correspond to interfaces that were connected to devices/hosts that powered on at the time of the panic while I think that the "cannot forward src" messages correspond to em2 and em3 which were connected to computers that were powered off at the time of the panic, but were previously powered on to test if they were receiving IPv6 addresses. I am wondering if the computers being powered off at the time of the DHCPv6 lease update is triggering the panic and I think I might test this by only enabling IPv6 on em5 and vlan[0-3] which are connected to my wireless AP is always on. I would be happy to provide any other relevant info that I may have omitted. Thanks for reading. Ben ## OpenBSD 6.6 (GENERIC.MP) #3: Thu Nov 21 03:20:01 MST 2019 r...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENER IC.MP real mem = 4192743424 (3998MB) avail mem = 4052963328 (3865MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x8d317000 (85 entries) bios0: vendor American Megatrends Inc. version "5.12" date 07/08/2019 bios0: Protectli FW6 acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S5 acpi0: tables DSDT FACP APIC FPDT MCFG SSDT FIDT SSDT HPET SSDT SSDT UEFI SSDT LPIT WSMT SSDT SSDT SSDT SSDT DBGP DBG2 BGRT DMAR ASF! acpi0: wakeup devices PS2K(S0) PS2M(S0) RP09(S0) PXSX(S0) RP10(S0) PXSX(S0) RP11(S0) PXSX(S0) RP12(S0) PXSX(S0) RP13(S0) PXSX(S0) RP01(S0) PXSX(S0) RP02(S0) PXSX(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 3865U @ 1.80GHz, 1696.58 MHz, 06-8e-09 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,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,M OVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3 DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,SMEP,ERMS,INVPCID,MPX,RDSEED,SMA P,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSA VEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN 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 24MHz 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) Celeron(R) CPU 3865U @ 1.80GHz, 1696.06 MHz, 06-8e-09 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,
Re: But there is Fossil...
Fossil is superfine and I'd like it for various reasons too, but unfortunately it does not scale to the OpenBSD repo size well. As a test, you can try and clone fossil repo of NetBSD and I'm sure you will find out quickly why people are working on GoT and OpenGIT. On 1/4/20 5:20 PM, go...@disroot.org wrote: Git is the most popular VCS (and most ugly), meanwhile there are people who prefer to reimplement it because they don't like its license... FreeBSD is working on OpenGit, OpenBSD is working on Game of Trees, but why reimplement the wheel instead of using a better solution: Fossil? I like CVS and SQLite used CVS in the past and then they INNOVATED Fossil - distributed version control system, usable as CVS, it has neat autosync feature, I don't need to explicitly use push and pull because that happens automatically. Fossil can also work with multiple branches at once (Git can work only with one branch at time). And Fossil's web UI is amazing, have you ever seen Fossil's timeline? I am sure people behind Fossil are the people who love CVS, they made CVS perfect (unlike people behind SVN). I am running Fossil to synchronize my ports work on laptop and computer and I am amazed how easy it is, how I wish I had my own domain to share my work (both finished and WIP) to public...
panic: kernel diagnostic assertion in nd6.c on 6.6-stable amd64
Hi, I have an amd64 system that I am using as a router/firewall for my home network running OpenBSD 6.6-stable with the latest syspatches. I have been running it without problems in an IPv4-only configuration. Recently, I decided I wanted to experiment with running a dual stack IPv4 and IPv6 network. I think I have successfully added IPv6 to my configuration which seemed to be functioning correctly to the best of my knowledge, but I have started to encounter kernel panics that crash to the ddb debugger after about 12 hours of uptime. I believe the panics might be specifically occurring when the DHCPv6 lease expires or renews on my external interface and the IPv6 routing table is updated. The panics go away when I reverted back to my IPv4-only configuration so I believe the panics are specific to IPv6. I have been troubleshooting and researching and for the past week or so and I thought I would check to see if some more experienced OpenBSD users might have some advice on how to proceed with troubleshooting. At the end of this email, I have included the relevant section from /var/run/dmesg.boot related to one instance of the panic. It includes the boot messages, panic message, trace, and the output of ps I ran in ddb after the panic. I did find a similar bug report in the mail archive for openbsd-bugs that looks like it was unfortunately not resolved: https://marc.info/?l=openbsd-bugs=152587044611044=2 Some more info about my configuration that I think may be relevant: My ISP uses DHCPv6 prefix delegation to distribute IPv6 addresses so I used dhcpcd from ports installed using pkg_add. I used rad for router advertisements on my internal interfaces and I am using SLAAC to auto-configure IPv6 addresses. My system has 6 Intel NICs, em[0-5], and I also have 4 VLANs vlan[0-3] on em5 that I am using for my wireless AP. em0 is the external interface connected to my cable modem. em[1-5] are my internal interfaces. em[1-3] are each connected to separate computers, em4 is unconnected, and em5 and vlan[0-3] are connected to my wireless AP. The only other observation I had that might be related to the panic is regarding the "ndp info overwritten" and "cannot forward src" lines in my dmesg. The "ndp info overwritten" lines correspond to interfaces that were connected to devices/hosts that powered on at the time of the panic while I think that the "cannot forward src" messages correspond to em2 and em3 which were connected to computers that were powered off at the time of the panic, but were previously powered on to test if they were receiving IPv6 addresses. I am wondering if the computers being powered off at the time of the DHCPv6 lease update is triggering the panic and I think I might test this by only enabling IPv6 on em5 and vlan[0-3] which are connected to my wireless AP is always on. I would be happy to provide any other relevant info that I may have omitted. Thanks for reading. Ben ## OpenBSD 6.6 (GENERIC.MP) #3: Thu Nov 21 03:20:01 MST 2019 r...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4192743424 (3998MB) avail mem = 4052963328 (3865MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x8d317000 (85 entries) bios0: vendor American Megatrends Inc. version "5.12" date 07/08/2019 bios0: Protectli FW6 acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S5 acpi0: tables DSDT FACP APIC FPDT MCFG SSDT FIDT SSDT HPET SSDT SSDT UEFI SSDT LPIT WSMT SSDT SSDT SSDT SSDT DBGP DBG2 BGRT DMAR ASF! acpi0: wakeup devices PS2K(S0) PS2M(S0) RP09(S0) PXSX(S0) RP10(S0) PXSX(S0) RP11(S0) PXSX(S0) RP12(S0) PXSX(S0) RP13(S0) PXSX(S0) RP01(S0) PXSX(S0) RP02(S0) PXSX(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 3865U @ 1.80GHz, 1696.58 MHz, 06-8e-09 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,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,SMEP,ERMS,INVPCID,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN 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 24MHz 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) Celeron(R) CPU 3865U @ 1.80GHz, 1696.06 MHz, 06-8e-09 cpu1:
Re: Request for recommendation - encryption and signature for file backup
Namaste Philippe, Merci beaucoup for your reply. > Sent: Saturday, January 04, 2020 at 3:54 PM > From: "Philippe Meunier" > To: "Aham Brahmasmi" > Cc: misc@openbsd.org, Roderick > Subject: Re: Request for recommendation - encryption and signature for file > backup > > >Aham Brahmasmi wrote: > >> In my limited understanding, to securely backup and restore a file, the > >> steps are: > >> > >> To backup: > >> Step 1 - encrypt the file using a tool > >> Step 2 - sign the encrypted file using a tool > >> Step 3 - backup the signature and the encrypted file > >> > >> To restore: > >> Step 1 - verify the encrypted backup with its signature > >> If Step 1 exits with success, > >> Step 2 - decrypt backup to file > >> If Step 2 exits with success, > >> Step 3 - use file to restore > > The signature verification step is useless: if someone can change an > encrypted file on your backup system then they can change the corresponding > signature file on the same backup system too. I am not a cryptographer, and neither am I a math expert. Let us assume that someone has access to the backup - both the encrypted file and its signature. This person does not have access to the encryption key and the private signing key - else this discussion is moot. This person changes the encrypted file and the corresponding signature file as well. Now, when this modified file is verified against the modified signature using the public signing key, would the verification fail or succeed? If I am not wrong, the verification should fail. In short, this is by definition of signature itself. For a longer explanation, to generate a valid signature, this person will need to have access to the private signing key. Since this person does not have access to the private signing key, the person can modify the encrypted file, but not generate a valid signature of the modified encrypted file. And modifying the original signature does not mean much - the verification with the public signing key will fail. For example, consider the OpenBSD release signing system. (I think) Theo signs the releases using a private signing key. If I am not wrong, only Theo has access to the private signing key, but we all have access to the public signing key. The bsd.rd is released along with its signature in the SHA256.sig file. We run signify(1) to verify the bsd.rd with its signature in the SHA256.sig file and the base.pub public signing key. Let us assume I get access to the download server and I replace the perl based installer with a rust based installer in the bsd.rd. I also change the SHA256.sig file. I do not think I will fool anybody who uses signify to verify the all-new-improved-rust-based-installer bsd.rd with the base.pub. And if you think I came up with this, no. I have only rehashed tedu@'s paper on signify - https://www.openbsd.org/papers/bsdcan-signify.html > If you use (symmetric) encryption then there is probably no need for a > signature in your simple use case anyway: if the encrypted file correctly > decrypts (which is usually easy to tell for data files like text or images) > with the password that only you know then you can assume that nobody > changed the content of the encrypted file on your backup system. If > someone changed the content of the encrypted file on your backup system > then, when you try to decrypt it, either the decrypt will fail or the > result will look like random garbage (hence the "usually easy" above). For files like compressed database backups, I am not sure I can determine whether a file has been correctly decrypted or not by looking at whether the result looks like random garbage. > If your goal is just to prevent people from looking at the content of your > file if they somehow access your backup system then encryption is really > all you need. If you're worried that people might actively try to attack > you through your backup system then you have bigger problems which are > probably beyond what random people on a mailing list can help you with... In the case of compressed database backups, it may also be possible that the backup may have changed due to bit-rot. So decrypting the backup and restoring it assuming no bit-rot may not be exactly preferable. > Roderick wrote: > >I do use openssl for encrypting files in my laptop. > > So do I. I only encrypt the 0.001% of files that are really important and > then those files are encrypted on my computer too, not just on the backup > system (because if a file is important enough to be encrypted on your > backup system then it's probably important enough to be encrypted on your > computer too). Something like: > > openssl enc -aes256 -e < foo > foo.aes256 > > then I delete foo. (To decrypt use the -d option instead of -e; and read > carefully the openssl(1) man page before you type the command above because > you have no reason to trust me, right?) Then I do backups without worrying > about whether a file is encrypted or not. YMMV. I am not sure
Re: But there is Fossil...
On Sat, Jan 04, 2020 at 04:59:40PM +, go...@disroot.org wrote: > I never read Please stop wasting our time then. Thanks, Florian -- I'm not entirely sure you are real.
Re: Request for recommendation - encryption and signature for file backup
>Aham Brahmasmi wrote: >> In my limited understanding, to securely backup and restore a file, the >> steps are: >> >> To backup: >> Step 1 - encrypt the file using a tool >> Step 2 - sign the encrypted file using a tool >> Step 3 - backup the signature and the encrypted file >> >> To restore: >> Step 1 - verify the encrypted backup with its signature >> If Step 1 exits with success, >> Step 2 - decrypt backup to file >> If Step 2 exits with success, >> Step 3 - use file to restore The signature verification step is useless: if someone can change an encrypted file on your backup system then they can change the corresponding signature file on the same backup system too. If you use (symmetric) encryption then there is probably no need for a signature in your simple use case anyway: if the encrypted file correctly decrypts (which is usually easy to tell for data files like text or images) with the password that only you know then you can assume that nobody changed the content of the encrypted file on your backup system. If someone changed the content of the encrypted file on your backup system then, when you try to decrypt it, either the decrypt will fail or the result will look like random garbage (hence the "usually easy" above). If your goal is just to prevent people from looking at the content of your file if they somehow access your backup system then encryption is really all you need. If you're worried that people might actively try to attack you through your backup system then you have bigger problems which are probably beyond what random people on a mailing list can help you with... Roderick wrote: >I do use openssl for encrypting files in my laptop. So do I. I only encrypt the 0.001% of files that are really important and then those files are encrypted on my computer too, not just on the backup system (because if a file is important enough to be encrypted on your backup system then it's probably important enough to be encrypted on your computer too). Something like: openssl enc -aes256 -e < foo > foo.aes256 then I delete foo. (To decrypt use the -d option instead of -e; and read carefully the openssl(1) man page before you type the command above because you have no reason to trust me, right?) Then I do backups without worrying about whether a file is encrypted or not. YMMV. Philippe
Re: But there is Fossil...
January 4, 2020 6:45 PM, cho...@jtan.com wrote: > go...@disroot.org writes: > >> Git is the most popular VCS (and most ugly), meanwhile >> there are people who prefer to reimplement it because >> they don't like its license... FreeBSD is working on OpenGit, >> OpenBSD is working on Game of Trees, but why reimplement >> the wheel instead of using a better solution: Fossil? >> >> [snip 3 paragraphs of indecent exposure] > > How convenient that there is a tradition of collecting together the > questions that are asked frequently into a location that's easy to > find. A list of "Frequently Asked Questions", if you will. > > I'd never even heard of Game of Trees until your email yet I've > already been able to answer all of your questions by reading it's > own god-damn website. > > https://gameoftrees.org/faq.html > > Read The Fucking FAQ > > Matthew I never read entire FAQ, what I actually read is chosen based on header's name, if header's name does not match what I am looking for, I simply skip it to not waste time on reading what I don't need to know, so it was enough for me to read goals.
Re: APU2 fails to boot on OpenBSD 6.6-current #521
On Sat, Jan 4, 2020 at 1:34 PM Mischa wrote: > > On 20 Dec at 06:16, William Ahern wrote: > > On Fri, Dec 13, 2019 at 10:52:03PM +0100, Alexander Pluhar wrote: > > > > > > > Just upgraded my APU2 to the latest -current and it seems to hang on > > > > the disk. > > > > It was fine running on -current #512. > > > > > > I encountered this problem on 6.6 stable with the latest syspatches > > > installed after > > > updating the APU firmware[1] to 4.11.0.1. > > > > > > It worked again after downgrading to 4.10.0.3. > > > > > > [1] https://pcengines.github.io > > > > Here's the github ticket: https://github.com/pcengines/coreboot/issues/356 > > Looks like the culprit has been found and a fix submitted upstream. > > > > 4.11.0.2 is released: https://pcengines.github.io/#mr-30 I can confirm that this solves the problem. Talk about bleeding edge. I received my apu4c4 yesterday, tried to install OpenBSD on it today. First time using an APU, and *of course* I was hit by this bug. Fortunately I found the solution thanks to this email. After the upgrade to 4.11.0.2 I could continue installing OpenBSD 6.6. My apu4c4 was shipped from the store the same day as this patch came out. Had I waited one more day I would have been blissfully unaware. :)
Re: But there is Fossil...
go...@disroot.org writes: > Git is the most popular VCS (and most ugly), meanwhile > there are people who prefer to reimplement it because > they don't like its license... FreeBSD is working on OpenGit, > OpenBSD is working on Game of Trees, but why reimplement > the wheel instead of using a better solution: Fossil? > > [snip 3 paragraphs of indecent exposure] How convenient that there is a tradition of collecting together the questions that are asked frequently into a location that's easy to find. A list of "Frequently Asked Questions", if you will. I'd never even heard of Game of Trees until your email yet I've already been able to answer all of your questions by reading it's own god-damn website. https://gameoftrees.org/faq.html Read The Fucking FAQ Matthew
But there is Fossil...
Git is the most popular VCS (and most ugly), meanwhile there are people who prefer to reimplement it because they don't like its license... FreeBSD is working on OpenGit, OpenBSD is working on Game of Trees, but why reimplement the wheel instead of using a better solution: Fossil? I like CVS and SQLite used CVS in the past and then they INNOVATED Fossil - distributed version control system, usable as CVS, it has neat autosync feature, I don't need to explicitly use push and pull because that happens automatically. Fossil can also work with multiple branches at once (Git can work only with one branch at time). And Fossil's web UI is amazing, have you ever seen Fossil's timeline? I am sure people behind Fossil are the people who love CVS, they made CVS perfect (unlike people behind SVN). I am running Fossil to synchronize my ports work on laptop and computer and I am amazed how easy it is, how I wish I had my own domain to share my work (both finished and WIP) to public...
Re: httpd with multiple php-fpm pools in separate chroots
On 2020-01-04, Nazar Zhuk wrote: > I get SCRIPT_FILENAME passed from httpd relative to httpd chroot > (/site1/htdocs/... ) and PHP being chrooted into /var/www/site1 needs > that to be relative to it's own chroot (/htdocs/...). httpd is a bit inflexible (intentionally, I think). Can you work around it with ln -s . /var/www/site1/site1 ?
Re: ttyC0 floods with error messages
I'm the original poster of this thread, don't mean to whip a dead horse, but this post is to confirm the state of this issue. The most recent -current release before this post has fixed this issue for me. OpenBSD 6.6-current (GENERIC.MP) #573: Sat Dec 28 19:13:57 MST 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP I'm longer greeted with the given train of messages from kernel. >wsmouse0 at ums0 mux 0 >wsmouse0 detached >ums0 detached >uhidev2 detached >uhidev2 at uhub5 port 2 configuration 1 interface 0 "Logitech USB Optical >Mouse" rev 2.00/72.00 addr 3 >uhidev2: iclass 3/1 >ums0 at uhidev2: 3 buttons, Z dir Major props to the OpenBSD Devs for dealing with this successfully and in such a short time.
Re: Turbo boost and performance degradation
On Tue, Dec 31, 2019 at 02:07:26PM -0500, Raul Miller wrote: > This might be relevant: > > hw.setperf=0 > hey, sorry for late reply actually setting that one to 100 doesn't help to solve the problem, CPU frequency is still 1100 MHz and everything was still lagging > See also: https://man.openbsd.org/cpu.4 > > -- > Raul > > On Tue, Dec 31, 2019 at 1:57 PM Leo wrote: > > > > hi > > > > my russian friend has a trouble running OpenBSD > > on his laptop, he reports that Turbo Boost is > > not working (OpenBSD limits him to 1100 MHz), > > he also reports that he owns /dev/drm0, but > > everything is slow, he can't even play videos > > in Firefox > > > > I attach his dmesg, Xorg.0.log and sysctl hw: > > OpenBSD 6.6-current (GENERIC.MP) #576: Mon Dec 30 11:57:39 MST 2019 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 4096020480 (3906MB) > > avail mem = 3959422976 (3776MB) > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xfaf60 (44 entries) > > bios0: vendor LENOVO version "6GCN24WW" date 11/13/2017 > > bios0: LENOVO 81A4 > > acpi0 at bios0: ACPI 5.0 > > acpi0: sleep states S0 S3 S4 S5 > > acpi0: tables DSDT FACP UEFI BDAT DBG2 DBGP HPET LPIT APIC MCFG NPKT PRAM > > WSMT SSDT SSDT BATB SSDT SSDT SSDT SSDT MSDM SSDT FPDT BGRT WDAT UEFI > > acpi0: wakeup devices LID0(S3) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) > > PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) XHC_(S4) > > XDCI(S4) HDAS(S3) > > acpitimer0 at acpi0: 3579545 Hz, 24 bits > > acpihpet0 at acpi0: 1920 Hz > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: Intel(R) Celeron(R) CPU N3350 @ 1.10GHz, 1097.97 MHz, 06-5c-09 > > 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,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN > > cpu0: 1MB 64b/line 16-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 19MHz > > cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE > > cpu1 at mainbus0: apid 4 (application processor) > > cpu1: Intel(R) Celeron(R) CPU N3350 @ 1.10GHz, 1097.49 MHz, 06-5c-09 > > 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,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN > > cpu1: 1MB 64b/line 16-way L2 cache > > cpu1: smt 0, core 2, package 0 > > ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins > > acpimcfg0 at acpi0 > > acpimcfg0: addr 0xe000, bus 0-63 > > acpiprt0 at acpi0: bus 0 (PCI0) > > acpiprt1 at acpi0: bus 1 (RP01) > > acpiprt2 at acpi0: bus 2 (RP02) > > acpiprt3 at acpi0: bus -1 (RP03) > > acpiprt4 at acpi0: bus -1 (RP04) > > acpiprt5 at acpi0: bus -1 (RP05) > > acpiprt6 at acpi0: bus -1 (RP06) > > acpiec0 at acpi0 > > acpicpu0 at acpi0: C3(10@150 mwait.1@0x60), C2(10@50 mwait.1@0x21), > > C1(1000@1 mwait.1@0x1), PSS > > acpicpu1 at acpi0: C3(10@150 mwait.1@0x60), C2(10@50 mwait.1@0x21), > > C1(1000@1 mwait.1@0x1), PSS > > acpipwrres0 at acpi0: FN00, resource for FAN0 > > acpitz0 at acpi0: critical temperature is 100 degC > > aplgpio0 at acpi0: GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins > > acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 > > acpibat0 at acpi0: BAT1 model "BASE-BAT" serial 12345678 type LiP oem > > "LENOVO" > > "VPC2004" at acpi0 not configured > > acpibtn0 at acpi0: LID0 > > "SYNA2B38" at acpi0 not configured > > acpiac0 at acpi0: AC unit offline > > acpibtn1 at acpi0: PWRB > > acpicmos0 at acpi0 > > aplgpio1 at acpi0: GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins > > aplgpio2 at acpi0: GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins > > aplgpio3 at acpi0: GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins > > "INT33A1" at acpi0 not configured > > "INT3400" at acpi0 not configured > > "INT3406" at acpi0 not configured > > "INT3403" at acpi0 not configured > > "INT3403" at acpi0 not configured > > "PNP0C0B" at acpi0 not configured > > acpivideo0 at acpi0: GFX0 > > acpivout0 at acpivideo0: DD1F > > cpu0: Enhanced SpeedStep 1097 MHz: speeds: 1101, 1100, 1000, 900, 800 MHz > > pci0 at mainbus0 bus 0 > > pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b > > vendor "Intel", unknown
Re: APU2 fails to boot on OpenBSD 6.6-current #521
On 20 Dec at 06:16, William Ahern wrote: > On Fri, Dec 13, 2019 at 10:52:03PM +0100, Alexander Pluhar wrote: > > > > > Just upgraded my APU2 to the latest -current and it seems to hang on the > > > disk. > > > It was fine running on -current #512. > > > > I encountered this problem on 6.6 stable with the latest syspatches > > installed after > > updating the APU firmware[1] to 4.11.0.1. > > > > It worked again after downgrading to 4.10.0.3. > > > > [1] https://pcengines.github.io > > Here's the github ticket: https://github.com/pcengines/coreboot/issues/356 > Looks like the culprit has been found and a fix submitted upstream. > 4.11.0.2 is released: https://pcengines.github.io/#mr-30 Mischa
Re: Openrsync manpage - EXAMPLES and SEE ALSO
Hello Aham,
Aham Brahmasmi wrote on Wed, Jan 01, 2020 at 02:27:59PM +0100:
> I was under the (now incorrect) impression that the rsync{d}.5 links
> were related to configuration files for rsync{d}, hence my query. I now
> understand that they are rsync protocol descriptions.
No one provided an opinion whether the protocol manuals are accurate
and worth installing, so i simply deleted the two .Xrs for now,
see the commit below.
Thanks for reporting the dead links,
Ingo
CVSROOT:/cvs
Module name:src
Changes by: schwa...@cvs.openbsd.org2020/01/04 04:53:53
Modified files:
usr.bin/rsync : rsync.1
Log message:
Delete .Xrs to rsync(5) and rsyncd(5).
If somebody wants to install these two manual pages describing the
protocols, it is easy to put these two links back.
Dead links reported by .
OK jmc@ florian@
Index: rsync.1
===
RCS file: /cvs/src/usr.bin/rsync/rsync.1,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- rsync.1 9 Aug 2019 05:28:01 - 1.19
+++ rsync.1 4 Jan 2020 11:53:53 - 1.20
@@ -1,4 +1,4 @@
-.\"$OpenBSD: rsync.1,v 1.19 2019/08/09 05:28:01 claudio Exp $
+.\"$OpenBSD: rsync.1,v 1.20 2020/01/04 11:53:53 schwarze Exp $
.\"
.\" Copyright (c) 2019 Kristaps Dzonsons
.\"
@@ -14,7 +14,7 @@
.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
.\"
-.Dd $Mdocdate: August 9 2019 $
+.Dd $Mdocdate: January 4 2020 $
.Dt OPENRSYNC 1
.Os
.Sh NAME
@@ -252,9 +252,7 @@
.Dl % rsync -t bar baz ../dest
.\" .Sh DIAGNOSTICS
.Sh SEE ALSO
-.Xr ssh 1 ,
-.Xr rsync 5 ,
-.Xr rsyncd 5
+.Xr ssh 1
.Sh STANDARDS
.Nm
is compatible with rsync protocol version 27
