PPPoE connection does not set IP
I'm trying to establish VDSL connection using an ECI modem over PPPoE. I'm running OpenBSD 6.8 on APU board from PC Engines. Relevant inerface configuration: /etc/hostname.em0 up /etc/hostname.pppoe0 inet 0.0.0.0 255.255.255.255 NONE mtu 1492 pppoedev em0 authproto chap authname 'my login' authkey 'my password' peerproto chap peerflag callin up dest 0.0.0.1 When I bring the interface up, I can see that it authenticates (tcpdump output is long so I put it below). I can observe that it authenticates and receives an IP address from the network ISP. However, when I check the interface, it does not set new IP and it is stuck with "no carrier":: pppoe0: flags=8810 mtu 1492 index 15 priority 0 llprio 3 dev: em0 state: initial sid: 0x0 PADI retries: 0 PADR retries: 0 groups: pppoe status: no carrier inet 0.0.0.1 --> 0.0.0.0 netmask 0xff00 How can I further investigate this issue? I'm a bit out of ideas. Cheers, KN Here is the output from tcpdump -i em0, showing the exchange between my APU board and ECI VDSL modem. tcpdump: listening on em0, link-type EN10MB 01:19:24.111229 PPPoE-Discovery code Initiation, version 1, type 1, id 0x, length 12 tag Service-Name, length 0 tag Host-Uniq, length 4 #\324\311\274 01:19:24.117698 PPPoE-Discovery code Initiation, version 1, type 1, id 0x, length 12 tag Service-Name, length 0 tag Host-Uniq, length 4 #\324\311\274 01:19:24.122470 PPPoE-Discovery code Offer, version 1, type 1, id 0x, length 47 tag Service-Name, length 0 tag AC-Name, length 11 acc-aln4.fb tag Host-Uniq, length 4 #\324\311\274 tag AC-Cookie, length 16 8\236\305\331\324?\035s\227\256\274\320\373\012\374h 01:19:24.122653 PPPoE-Discovery code Request, version 1, type 1, id 0x, length 32 tag Service-Name, length 0 tag AC-Cookie, length 16 8\236\305\331\324?\035s\227\256\274\320\373\012\374h tag Host-Uniq, length 4 #\324\311\274 01:19:24.123960 PPPoE-Discovery code Initiation, version 1, type 1, id 0x, length 12 tag Service-Name, length 0 tag Host-Uniq, length 4 #\324\311\274 01:19:24.130257 PPPoE-Discovery code Initiation, version 1, type 1, id 0x, length 12 tag Service-Name, length 0 tag Host-Uniq, length 4 #\324\311\274 01:19:24.145508 PPPoE-Discovery code Offer, version 1, type 1, id 0x, length 47 tag Service-Name, length 0 tag AC-Name, length 11 acc-aln4.fb tag Host-Uniq, length 4 #\324\311\274 tag AC-Cookie, length 16 8\236\305\331\324?\035s\227\256\274\320\373\012\374h 01:19:24.145724 PPPoE-Discovery code Request, version 1, type 1, id 0x, length 32 tag Service-Name, length 0 tag AC-Cookie, length 16 8\236\305\331\324?\035s\227\256\274\320\373\012\374h tag Host-Uniq, length 4 #\324\311\274 01:19:24.149589 PPPoE-Discovery code Confirm, version 1, type 1, id 0x144e, length 12 tag Service-Name, length 0 tag Host-Uniq, length 4 #\324\311\274 01:19:24.149639 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 16 LCP Configure-Request Id=0x01: Magic-Number=2012867662 Max-Rx-Unit=1492 01:19:24.185026 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 21 LCP Configure-Request Id=0x1f: Max-Rx-Unit=1492 Auth-Prot=CHAP/MD5 Magic-Number=538534638 01:19:24.185062 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 21 LCP Configure-Ack Id=0x1f: Max-Rx-Unit=1492 Auth-Prot=CHAP/MD5 Magic-Number=538534638 01:19:24.185167 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 16 LCP Configure-Ack Id=0x01: Magic-Number=2012867662 Max-Rx-Unit=1492 01:19:24.188465 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 64 CHAP Challenge Id=0x01: Value=706d4498c8643102f0a75b6e8b352fcfa2fa51bd8ccd9177de4ca5a23a29aa2a966e425fd373e1441c3d32a7f161 Name=acc-aln4.fb 01:19:24.188546 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 44 CHAP Response Id=0x01: Value=803993c026af19d16f54c02c499865c0 Name=<***MY LOGIN***> 01:19:24.232859 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 33 CHAP Success Id=0x01: Message=CHAP authentication success 01:19:24.233293 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 6 LCP Terminate-Request Id=0x02: 01:19:24.233726 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 12 IPCP Configure-Request Id=0xfe: IP-Address= 01:19:24.236687 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 6 LCP Terminate-Ack Id=0x02: 01:19:24.252350 PPPoE-Discovery code Terminate, version 1, type 1, id 0x144e, length 0 01:19:24.262382 PPPoE-Discovery code
Re: OT acpi failure
On 8.12.2020 14:35, tru...@tutanota.com wrote: hallo list, my machine had one of the ahci failures after which it very fast went stiff (just the caps and num locks did light on/off if appropriate keys got pressed). "very fast" means like a half a minute during which i managed to switch to ttyC0 to see this "one of the ahci failure" messages that i suspect come from the kernel(?): $ doas strings /bsd | fgrep ahci | tail -3 %s: ahci_pmp_probe_timeout: failed to clear active cmds: %08x ahci %s: ahci_pmp_probe_timeout: ccb in bad state %d yes, i panicked enough not to take down the message and whether it was the first or the third one of the three showed above (it definitely read "ahci0:" at the front of it and "31" at the very end of it) i'm not that concerned about because the sole question i have to you Gurus is if this is a dying motherboard or a dying hard disk (the boot one, the other two are data) i dare to ask because duckduckgoing from my corner of the web reveals 99% M$ noise with the remaining 1% even more nonsense. in the meantime i repluged the disk (with the same cable) to another sata port and i'm hoping to luckily survive till someone knowledgeable returns with the answer so i know what to mock Mr S.C. for. /tru It comes from here https://cvsweb.openbsd.org/src/sys/dev/ic/ahci.c?rev=1.37=text/x-cvsweb-markup Which points do default response in code on timeout, but why that timeout You can enable AHCI_DEBUG in here https://cvsweb.openbsd.org/src/sys/dev/ic/ahcivar.h?rev=1.10=text/x-cvsweb-markup Maybe it will show more details in dmesg then Besides that you have latest BIOS for this MB, you can try read SMART log with atactl(8) OpenBSD 6.7 (GENERIC.MP) #182: Thu May 7 11:11:58 MDT 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3991404544 (3806MB) avail mem = 3857817600 (3679MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0x9f400 (52 entries) bios0: vendor American Megatrends Inc. version "1701" date 11/18/2016 bios0: ASUSTeK Computer INC. M5A78L-M LX V2 acpi0 at bios0: ACPI 3.0 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT acpi0: wakeup devices PCE2(S4) PCE3(S4) PCE4(S4) RLAN(S4) PCE5(S4) PCE6(S4) PCE7(S4) PCE9(S4) PCEA(S4) PCEB(S4) PCEC(S4) SBAZ(S4) PS2K(S4) UAR1(S4) P0PC(S4) UHC1(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 16 (boot processor) cpu0: AMD FX(tm)-4170 Quad-Core Processor, 4219.57 MHz, 15-01-02 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,CPCTR,ITSC cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 17 (application processor) cpu1: AMD FX(tm)-4170 Quad-Core Processor, 4218.96 MHz, 15-01-02 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,CPCTR,ITSC cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 18 (application processor) cpu2: AMD FX(tm)-4170 Quad-Core Processor, 4218.97 MHz, 15-01-02 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,CPCTR,ITSC cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu2: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 19 (application processor) cpu3: AMD FX(tm)-4170 Quad-Core Processor, 4218.96 MHz, 15-01-02 cpu3:
Re: base LoC & committers
On 8.12.2020 19:43, Salvatore Cuzzilla wrote: do you know if it's possible to see some statistics about the committers? like for example number of commits per committer. The best statistic I know of is general feeling of quality out of the software, it's stability and simplicity. That tells me everything what is needed and is why others can't beat it no matter how much Powerpoint presentations about commiter statistics they throw out ;-) On Tue, 2020-12-08 at 15:53 +0100, Benjamin Baier wrote: On Tue, 08 Dec 2020 13:49:13 +0100 Salvatore Cuzzilla wrote: > Hi Everyone, > > just out of curiosity, I was asking myself: > > - approx how many LoC do we have in *base*? > - & how many committers are actually contributing to it? > > when I think about some other OS with a kernel of almost 30M LoC & > over > 5k committers I go insane :) > > > Regards, > Salvatore. $ cloc /usr/src 111439 text files. 85841 unique files. 55120 files ignored. github.com/AlDanial/cloc v 1.86 T=254.29 s (229.3 files/s, 94467.6 lines/s) --- Language files blankcomm ent code --- C1741212941481491 3937181673 C/C++ Header 14902 4933731021729 4255540 C++ 10637 483624 511 8112771795 Perl 4309 169414 228 936 956256 Bourne Shell 1263 57662 69942 434428 Markdown 279 47833 0 407365 PO File129 141599 190451 319672 Python1461 35581 35 610 134779 HTML 259 17553 993 128449 Assembly 969 21343 56 839 117720 yacc93 14004 8 880 108162 reStructuredText 775 49070 43 308 106806 Expect 460 14443 21 700 74931 make 2459 15471 8 987 68516 Windows Module Definition 200 6600 3 49 202 m4 177 5669 3 351 48578 CMake 882 5106 3 729 36458 ASP.NET 2 1013 18 24717 TeX 29 3094 12 237 21764 Pascal 58 3289 16 255 13924 Scheme 95 1438 146 12907 XML108828 396 10910 lex 35 1714 1 908 10441 awk 57686 1 607 8210 SWIG67 2752 508 7668 Fortran 77 183893 2886 7495 Oracle PL/SQL4180 1 6945 Go 26908 733 6507 Objective C++ 23 1097840 6332 Objective C211 1639629 6041 YAML 100 75 60 5954 OCaml 59 1366 2 512 4083 Fortran 90 73264818 3457 Korn Shell 83900 1118 3381 JSON41 1 0 2651 SQL 5 77 38 2343 sed 46221 593 1848 CSS 20282 105 1801 ANTLR Grammar2 0 0 1726 DOS Batch 30251103 1501 SVG 4 0 26 1361 Lisp12193 452 1147 Bourne Again Shell 8170236 899 diff25124 624628
Re: PPPoE connection does not set IP
On 9.12.2020 02:33, Chris Narkiewicz wrote: I'm trying to establish VDSL connection using an ECI modem over PPPoE. I'm running OpenBSD 6.8 on APU board from PC Engines. Relevant inerface configuration: /etc/hostname.em0 up /etc/hostname.pppoe0 inet 0.0.0.0 255.255.255.255 NONE mtu 1492 pppoedev em0 authproto chap authname 'my login' authkey 'my password' peerproto chap peerflag callin up dest 0.0.0.1 When I bring the interface up, I can see that it authenticates (tcpdump output is long so I put it below). I can observe that it authenticates and receives an IP address from the network ISP. However, when I check the interface, it does not set new IP and it is stuck with "no carrier":: pppoe0: flags=8810 mtu 1492 index 15 priority 0 llprio 3 dev: em0 state: initial sid: 0x0 PADI retries: 0 PADR retries: 0 groups: pppoe status: no carrier inet 0.0.0.1 --> 0.0.0.0 netmask 0xff00 How can I further investigate this issue? I'm a bit out of ideas. You can try to enable debug output in ifconfig(8) if that will provide more info. As well pppoe section example shows addition of default routes. Did you try with those lines if there will be change? Cheers, KN Here is the output from tcpdump -i em0, showing the exchange between my APU board and ECI VDSL modem. tcpdump: listening on em0, link-type EN10MB 01:19:24.111229 PPPoE-Discovery code Initiation, version 1, type 1, id 0x, length 12 tag Service-Name, length 0 tag Host-Uniq, length 4 #\324\311\274 01:19:24.117698 PPPoE-Discovery code Initiation, version 1, type 1, id 0x, length 12 tag Service-Name, length 0 tag Host-Uniq, length 4 #\324\311\274 01:19:24.122470 PPPoE-Discovery code Offer, version 1, type 1, id 0x, length 47 tag Service-Name, length 0 tag AC-Name, length 11 acc-aln4.fb tag Host-Uniq, length 4 #\324\311\274 tag AC-Cookie, length 16 8\236\305\331\324?\035s\227\256\274\320\373\012\374h 01:19:24.122653 PPPoE-Discovery code Request, version 1, type 1, id 0x, length 32 tag Service-Name, length 0 tag AC-Cookie, length 16 8\236\305\331\324?\035s\227\256\274\320\373\012\374h tag Host-Uniq, length 4 #\324\311\274 01:19:24.123960 PPPoE-Discovery code Initiation, version 1, type 1, id 0x, length 12 tag Service-Name, length 0 tag Host-Uniq, length 4 #\324\311\274 01:19:24.130257 PPPoE-Discovery code Initiation, version 1, type 1, id 0x, length 12 tag Service-Name, length 0 tag Host-Uniq, length 4 #\324\311\274 01:19:24.145508 PPPoE-Discovery code Offer, version 1, type 1, id 0x, length 47 tag Service-Name, length 0 tag AC-Name, length 11 acc-aln4.fb tag Host-Uniq, length 4 #\324\311\274 tag AC-Cookie, length 16 8\236\305\331\324?\035s\227\256\274\320\373\012\374h 01:19:24.145724 PPPoE-Discovery code Request, version 1, type 1, id 0x, length 32 tag Service-Name, length 0 tag AC-Cookie, length 16 8\236\305\331\324?\035s\227\256\274\320\373\012\374h tag Host-Uniq, length 4 #\324\311\274 01:19:24.149589 PPPoE-Discovery code Confirm, version 1, type 1, id 0x144e, length 12 tag Service-Name, length 0 tag Host-Uniq, length 4 #\324\311\274 01:19:24.149639 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 16 LCP Configure-Request Id=0x01: Magic-Number=2012867662 Max-Rx-Unit=1492 01:19:24.185026 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 21 LCP Configure-Request Id=0x1f: Max-Rx-Unit=1492 Auth-Prot=CHAP/MD5 Magic-Number=538534638 01:19:24.185062 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 21 LCP Configure-Ack Id=0x1f: Max-Rx-Unit=1492 Auth-Prot=CHAP/MD5 Magic-Number=538534638 01:19:24.185167 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 16 LCP Configure-Ack Id=0x01: Magic-Number=2012867662 Max-Rx-Unit=1492 01:19:24.188465 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 64 CHAP Challenge Id=0x01: Value=706d4498c8643102f0a75b6e8b352fcfa2fa51bd8ccd9177de4ca5a23a29aa2a966e425fd373e1441c3d32a7f161 Name=acc-aln4.fb 01:19:24.188546 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 44 CHAP Response Id=0x01: Value=803993c026af19d16f54c02c499865c0 Name=<***MY LOGIN***> 01:19:24.232859 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 33 CHAP Success Id=0x01: Message=CHAP authentication success 01:19:24.233293 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 6 LCP Terminate-Request Id=0x02: 01:19:24.233726 PPPoE-Session code Session, version 1, type 1, id 0x144e, length 12 IPCP Configure-Request Id=0xfe: IP-Address= 01:19:24.236687 PPPoE-Session code Session,
Default installurl and Package Source
Hi misc, I recently installed 6.8 on VM then applied errata patches. When I tried to install git, it complained that git is not in the packages-stable folder, I was pleasantly surprised. The /etc/installurl by default is http://cdn.openbsd.org/pub/OpenBSD, and I got error 503 on the site. Checking the default URL indicates it may be down, same goes for Cloudflare CDN, Verizon seems working alright. When I changed /etc/installurl to where I used to get packages: http://ftp.jaist.ac.jp/pub/OpenBSD, it worked as expected. This raised the following questions: Does this mean when we apply errata patches, we're now automatically using stable release and need to use stable packages? Is it advisable to keep the /etc/installurl automatically default to http://cdn.openbsd.org/pub/OpenBSD or should users be advised to select packages from package sources geographically near them? Please advise. Thanks and keep up the great work.
support new
0 C Brazil P RS T Santo Antonio da Patrulha Z 95500-000 O AMG Labs I Angelito Monteiro Goulart A Av. Cel Victor Villa Verde 126/301 M cont...@amglabs.net U https://www.amglabs.net/ B +55 51 92000 7613 X N We are a software development and server management company operating in the market since 2014. We work with the development of customized web systems and the deployment and management of servers based on open source technologies such as CentOS, Debian, FreeBSD, OpenBSD and Ubuntu Server.
Re: Unable to listen properly on UDP port 4500
Thanks and noted. Definitely not a masochist... I will adjust my ports accordingly. Cheers! Chris On 2020/12/8 16:29, Philip Guenther wrote: : bleys; grep 4500 /etc/services ipsec-nat-t 4500/tcp ipsec-msft # IPsec NAT-Traversal ipsec-nat-t 4500/udp ipsec-msft # IPsec NAT-Traversal : bleys; sysctl net.inet.esp.udpencap net.inet.esp.udpencap=1 : bleys You're trying to use the ipsec ESP encapsulation port, which is enabled by default. If you're a masochist and likes making your life more difficult, you can use that port for your own purposes by disabling that sysctl. If you're not a masochist, use a different port. Philip Guenther
Re: Unable to listen properly on UDP port 4500
: bleys; grep 4500 /etc/services ipsec-nat-t 4500/tcpipsec-msft # IPsec NAT-Traversal ipsec-nat-t 4500/udpipsec-msft # IPsec NAT-Traversal : bleys; sysctl net.inet.esp.udpencap net.inet.esp.udpencap=1 : bleys You're trying to use the ipsec ESP encapsulation port, which is enabled by default. If you're a masochist and likes making your life more difficult, you can use that port for your own purposes by disabling that sysctl. If you're not a masochist, use a different port. Philip Guenther On Tue, Dec 8, 2020 at 4:13 PM Chris Johnson wrote: > Hello All, > > I am unable to set up a localhost netcat listener on UDP port 4500 that > responds to a client on that same host. I encountered this issue > attempting to test whether UDP 4500 was open on our departmental firewall. > > Simple test case: Fresh build of OpenBSD 6.8. No local network, no > packet filter, no iked running. > > # netstat -na -f inet | grep 4500 > [empty] > # fstat | grep 4500 > [empty] > > $ nc -ul localhost 4501 & > [1] 72638 > $ nc -u localhost 4501 > Z > Z > ^C > $ pkill nc > > [1]+ Stopped nc -ul localhost 4501 > $ nc -ul localhost 4500 & > [2] 70181 > $ nc -u localhost 4500 > Z > ^C > $ pkill nc > [2]- Terminated nc -ul localhost 4500 > > The server running on port 4500 does not echo. Why not? Is there > something obvious that I'm missing? > > I've tried this on three different OpenBSD 6.8 systems (all amd64). Is > UDP 4500 reserved in some way? Other ports I've tried work fine. Linux > and MacOS systems work fine on this port. > > Cheers, > > Chris > >
Unable to listen properly on UDP port 4500
Hello All, I am unable to set up a localhost netcat listener on UDP port 4500 that responds to a client on that same host. I encountered this issue attempting to test whether UDP 4500 was open on our departmental firewall. Simple test case: Fresh build of OpenBSD 6.8. No local network, no packet filter, no iked running. # netstat -na -f inet | grep 4500 [empty] # fstat | grep 4500 [empty] $ nc -ul localhost 4501 & [1] 72638 $ nc -u localhost 4501 Z Z ^C $ pkill nc [1]+ Stopped nc -ul localhost 4501 $ nc -ul localhost 4500 & [2] 70181 $ nc -u localhost 4500 Z ^C $ pkill nc [2]- Terminated nc -ul localhost 4500 The server running on port 4500 does not echo. Why not? Is there something obvious that I'm missing? I've tried this on three different OpenBSD 6.8 systems (all amd64). Is UDP 4500 reserved in some way? Other ports I've tried work fine. Linux and MacOS systems work fine on this port. Cheers, Chris
Re: base LoC & committers
On Tue, 08 Dec 2020 19:43:30 +0100 Salvatore Cuzzilla wrote: > do you know if it's possible to see some statistics about the > committers? like for example number of commits per committer. Sounds like an Advent of Code puzzle, for grepping through /cvs/CVSROOT/ChangeLog* The answer for Part 1: sum of base (src) commits so far in 2020 is 7582. Part 2 to figure out which committer has the most commits in 2020 is left open as excercise for the reader. Hint it's ~740 commits. > On Tue, 2020-12-08 at 15:53 +0100, Benjamin Baier wrote: > > On Tue, 08 Dec 2020 13:49:13 +0100 > > Salvatore Cuzzilla wrote: > > > > > Hi Everyone, > > > > > > just out of curiosity, I was asking myself: > > > > > > - approx how many LoC do we have in *base*? > > > - & how many committers are actually contributing to it? > > > > > > when I think about some other OS with a kernel of almost 30M LoC & > > > over > > > 5k committers I go insane :) > > > > > > > > > Regards, > > > Salvatore. > > > > $ cloc /usr/src > > 111439 text files. > >85841 unique files. > >55120 files ignored.
Re: mongodb port
On 12/8/20 4:05 PM, Stuart Henderson wrote: > On 2020-12-08, Gregory Edigarov wrote: >> Hello, >> >> Just found that mongodb port/package doesn't not install >> mongodump/mongorestore binaries. >> Are there any problems with them? >> >> -- >> With best regards, >> Gregory Edigarov >> >> > Tempted to just reply with "if it needs backing up it shouldn't be > in mongodb", but... they aren't included in the main distfile and will > require modifying to work with OpenBSD. ;-) sure thing, it is rather about copying the data from one server to another, not a real backup. > https://github.com/mongodb/mongo-tools#building-tools > > $ ./make build > START | build > FAIL | build in 11.252428ms >| failed to detect local platform from kernel name "OpenBSD" > task(s) [build] failed > exit status 2 Will look into this, thanks for pointing, Stuart. -- With best regards, Gregory Edigarov
Re: base LoC & committers
Le mar. 8 déc. 2020 à 19:46, Salvatore Cuzzilla a écrit : > > do you know if it's possible to see some statistics about the > committers? like for example number of commits per committer. There's at least http://www.oxide.org/cvs/index.html
Re: base LoC & committers
do you know if it's possible to see some statistics about the committers? like for example number of commits per committer. On Tue, 2020-12-08 at 15:53 +0100, Benjamin Baier wrote: > On Tue, 08 Dec 2020 13:49:13 +0100 > Salvatore Cuzzilla wrote: > > > Hi Everyone, > > > > just out of curiosity, I was asking myself: > > > > - approx how many LoC do we have in *base*? > > - & how many committers are actually contributing to it? > > > > when I think about some other OS with a kernel of almost 30M LoC & > > over > > 5k committers I go insane :) > > > > > > Regards, > > Salvatore. > > $ cloc /usr/src > 111439 text files. >85841 unique files. >55120 files ignored. > > github.com/AlDanial/cloc v 1.86 T=254.29 s (229.3 files/s, 94467.6 > lines/s) > --- > > Language files blankcomm > ent code > --- > > C1741212941481491 > 3937181673 > C/C++ > Header 14902 4933731021729 > 4255540 > C++ 10637 483624 511 > 8112771795 > Perl 4309 169414 228 > 936 956256 > Bourne > Shell 1263 57662 69942 > 434428 > Markdown 279 47833 > 0 407365 > PO > File129 141599 190451 > 319672 > Python1461 35581 35 > 610 134779 > HTML 259 17553 > 993 128449 > Assembly 969 21343 56 > 839 117720 > yacc93 14004 8 > 880 108162 > reStructuredText 775 49070 43 > 308 106806 > Expect 460 14443 21 > 700 74931 > make 2459 15471 8 > 987 68516 > Windows Module > Definition 200 6600 3 49 > 202 > m4 177 5669 3 > 351 48578 > CMake 882 5106 3 > 729 36458 > ASP.NET 2 1013 > 18 24717 > TeX 29 3094 12 > 237 21764 > Pascal 58 3289 16 > 255 13924 > Scheme 95 1438 > 146 12907 > XML108828 > 396 10910 > lex 35 1714 1 > 908 10441 > awk 57686 1 > 607 8210 > SWIG67 2752 > 508 7668 > Fortran > 77 183893 2886 > 7495 > Oracle > PL/SQL4180 1 >6945 > Go 26908 > 733 6507 > Objective > C++ 23 1097840 > 6332 > Objective > C211 1639629 > 6041 > YAML 100 75 > 60 5954 > OCaml 59 1366 2 > 512 4083 > Fortran > 90 73264818 > 3457 > Korn > Shell 83900 1118 > 3381 > JSON41 1 > 0 2651 > SQL 5 77 > 38 2343 > sed 46221 > 593 1848 > CSS 20282 > 105 1801 > ANTLR > Grammar2 0 0 > 1726 > DOS > Batch 30251103 > 1501 > SVG 4 0 > 26 1361 > Lisp12193
FWD: OT its ahci not acpi failure of course
Date: 8 Dec 2020, 14:35 From: tru...@tutanota.com To: misc@openbsd.org Subject: OT acpi failure > hallo list, > > my machine had one of the ahci failures after which it very fast went > stiff (just the caps and num locks did light on/off if appropriate keys > got pressed). "very fast" means like a half a minute during which i > managed to switch to ttyC0 to see this "one of the ahci failure" > messages that i suspect come from the kernel(?): > > $ doas strings /bsd | fgrep ahci | tail -3 > %s: ahci_pmp_probe_timeout: failed to clear active cmds: %08x > ahci > %s: ahci_pmp_probe_timeout: ccb in bad state %d > > yes, i panicked enough not to take down the message and whether it was > the first or the third one of the three showed above (it definitely read > "ahci0:" at the front of it and "31" at the very end of it) i'm not that > concerned about because the sole question i have to you Gurus is if this > is a dying motherboard or a dying hard disk (the boot one, the other two > are data) > > i dare to ask because duckduckgoing from my corner of the web reveals > 99% M$ noise with the remaining 1% even more nonsense. > > in the meantime i repluged the disk (with the same cable) to another > sata port and i'm hoping to luckily survive till someone knowledgeable > returns with the answer so i know what to mock Mr S.C. for. > /tru > > > OpenBSD 6.7 (GENERIC.MP) #182: Thu May 7 11:11:58 MDT 2020 > > dera...@amd64.openbsd.org> :/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 3991404544 (3806MB) > avail mem = 3857817600 (3679MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.5 @ 0x9f400 (52 entries) > bios0: vendor American Megatrends Inc. version "1701" date 11/18/2016 > bios0: ASUSTeK Computer INC. M5A78L-M LX V2 > acpi0 at bios0: ACPI 3.0 > acpi0: sleep states S0 S1 S3 S4 S5 > acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT > acpi0: wakeup devices PCE2(S4) PCE3(S4) PCE4(S4) RLAN(S4) PCE5(S4) PCE6(S4) > PCE7(S4) PCE9(S4) PCEA(S4) PCEB(S4) PCEC(S4) SBAZ(S4) PS2K(S4) UAR1(S4) > P0PC(S4) UHC1(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 16 (boot processor) > cpu0: AMD FX(tm)-4170 Quad-Core Processor, 4219.57 MHz, 15-01-02 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,CPCTR,ITSC > cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line > 16-way L2 cache, 8MB 64b/line 64-way L3 cache > cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative > cpu0: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 200MHz > cpu0: mwait min=64, max=64, IBE > cpu1 at mainbus0: apid 17 (application processor) > cpu1: AMD FX(tm)-4170 Quad-Core Processor, 4218.96 MHz, 15-01-02 > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,CPCTR,ITSC > cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line > 16-way L2 cache, 8MB 64b/line 64-way L3 cache > cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative > cpu1: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative > cpu1: smt 1, core 0, package 0 > cpu2 at mainbus0: apid 18 (application processor) > cpu2: AMD FX(tm)-4170 Quad-Core Processor, 4218.97 MHz, 15-01-02 > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,CPCTR,ITSC > cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line > 16-way L2 cache, 8MB 64b/line 64-way L3 cache > cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative > cpu2: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative > cpu2: smt 0, core 1, package 0 > cpu3 at mainbus0: apid 19 (application processor) > cpu3: AMD FX(tm)-4170 Quad-Core Processor, 4218.96 MHz, 15-01-02 > cpu3: >
OT acpi failure
hallo list, my machine had one of the ahci failures after which it very fast went stiff (just the caps and num locks did light on/off if appropriate keys got pressed). "very fast" means like a half a minute during which i managed to switch to ttyC0 to see this "one of the ahci failure" messages that i suspect come from the kernel(?): $ doas strings /bsd | fgrep ahci | tail -3 %s: ahci_pmp_probe_timeout: failed to clear active cmds: %08x ahci %s: ahci_pmp_probe_timeout: ccb in bad state %d yes, i panicked enough not to take down the message and whether it was the first or the third one of the three showed above (it definitely read "ahci0:" at the front of it and "31" at the very end of it) i'm not that concerned about because the sole question i have to you Gurus is if this is a dying motherboard or a dying hard disk (the boot one, the other two are data) i dare to ask because duckduckgoing from my corner of the web reveals 99% M$ noise with the remaining 1% even more nonsense. in the meantime i repluged the disk (with the same cable) to another sata port and i'm hoping to luckily survive till someone knowledgeable returns with the answer so i know what to mock Mr S.C. for. /tru OpenBSD 6.7 (GENERIC.MP) #182: Thu May 7 11:11:58 MDT 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3991404544 (3806MB) avail mem = 3857817600 (3679MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0x9f400 (52 entries) bios0: vendor American Megatrends Inc. version "1701" date 11/18/2016 bios0: ASUSTeK Computer INC. M5A78L-M LX V2 acpi0 at bios0: ACPI 3.0 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT acpi0: wakeup devices PCE2(S4) PCE3(S4) PCE4(S4) RLAN(S4) PCE5(S4) PCE6(S4) PCE7(S4) PCE9(S4) PCEA(S4) PCEB(S4) PCEC(S4) SBAZ(S4) PS2K(S4) UAR1(S4) P0PC(S4) UHC1(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 16 (boot processor) cpu0: AMD FX(tm)-4170 Quad-Core Processor, 4219.57 MHz, 15-01-02 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,CPCTR,ITSC cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 17 (application processor) cpu1: AMD FX(tm)-4170 Quad-Core Processor, 4218.96 MHz, 15-01-02 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,CPCTR,ITSC cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 18 (application processor) cpu2: AMD FX(tm)-4170 Quad-Core Processor, 4218.97 MHz, 15-01-02 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,CPCTR,ITSC cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu2: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 19 (application processor) cpu3: AMD FX(tm)-4170 Quad-Core Processor, 4218.96 MHz, 15-01-02 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,CPCTR,ITSC cpu3: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu3: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu3: DTLB 32
Re: mongodb port
On 2020-12-08, Gregory Edigarov wrote: > > > On 12/8/20 4:05 PM, Stuart Henderson wrote: >> On 2020-12-08, Gregory Edigarov wrote: >>> Hello, >>> >>> Just found that mongodb port/package doesn't not install >>> mongodump/mongorestore binaries. >>> Are there any problems with them? >>> >>> -- >>> With best regards, >>> Gregory Edigarov >>> >>> >> Tempted to just reply with "if it needs backing up it shouldn't be >> in mongodb", but... they aren't included in the main distfile and will >> require modifying to work with OpenBSD. > ;-) sure thing, it is rather about copying the data from one server to > another, not a real backup. >> https://github.com/mongodb/mongo-tools#building-tools >> >> $ ./make build >> START | build >> FAIL | build in 11.252428ms >>| failed to detect local platform from kernel name "OpenBSD" >> task(s) [build] failed >> exit status 2 > Will look into this, thanks for pointing, Stuart. > -- > With best regards, > Gregory Edigarov > > I guess you can probably run it on $other_os to copy things around..
Could "re0: watchdog timeout" be caused by pf queues?
Hi, On my home router, since a year or two I've occasionally seen watchdog timeouts on re0 (which is connected with 1Gbps to a Cisco switch): re0: watchdog timeout They weren't frequent, but when they occurred it was always under high-ish throughput (300-400 Mbps). Yesterday however, one particular download from a machine on the LAN was able to consistently and repeatedly trigger a watchdog timeout. Starting the download resulted in a watchdog timeout within a second or two. It only stopped when I configured the downloading program to limit itself to ~40 Mbps or so. This was surprising, since I regularly can download stuff at 300-400Mbps. I've been trying things like switching gige master/slave mode and enabling/ disabling ethernet flow control. While this was all nicely shown in the output of ifconfig, it did not make any difference in symptoms. Is such a watchdog timeout always caused by the NIC, or could it also be caused by things like VLANs or an incorrect queue configuration? In other words, is it useful to try different configurations or is this a clear indication the the NIC itself is on its way out? Output of ifconfig and dmesg follows: lo0: flags=8049 mtu 32768 index 4 priority 0 llprio 3 groups: lo inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 re0: flags=8843 mtu 1500 lladdr 80:ee:73:a6:be:cf index 1 priority 0 llprio 3 media: Ethernet autoselect (1000baseT full-duplex,master) status: active inet 192.168.178.253 netmask 0xff00 broadcast 192.168.178.255 inet6 fe80::82ee:73ff:fea6:becf%re0 prefixlen 64 scopeid 0x1 inet6 2a03:10c3:391a:e0:: prefixlen 64 re1: flags=808843 mtu 1500 lladdr 80:ee:73:a6:be:ce index 2 priority 0 llprio 3 groups: egress media: Ethernet autoselect (1000baseT full-duplex) status: active inet 83.86.199.249 netmask 0xfe00 broadcast 83.86.199.255 enc0: flags=0<> index 3 priority 0 llprio 3 groups: enc status: active gif0: flags=8051 mtu 1476 index 5 priority 0 llprio 3 encap: txprio payload rxprio payload groups: gif egress tunnel: inet 83.86.199.249 -> 185.216.160.152 ttl 128 nodf ecn inet6 fe80::82ee:73ff:fea6:becf%gif0 -> prefixlen 64 scopeid 0x5 inet6 2a03:10c3:10:391a::2 -> 2a03:10c3:10:391a::1 prefixlen 128 gre0: flags=8051 rdomain 1 mtu 1476 index 6 priority 0 llprio 6 encap: vnetid none txprio payload rxprio packet groups: gre tunnel: inet 83.86.199.249 -> 185.216.160.152 ttl 128 nodf ecn rdomain 0 inet 10.0.0.1 --> 0.0.0.0 netmask 0xff00 vlan2: flags=8843 mtu 1500 lladdr 80:ee:73:a6:be:cf index 7 priority 0 llprio 3 encap: vnetid 2 parent re0 txprio packet rxprio outer groups: vlan media: Ethernet autoselect (1000baseT full-duplex,master) status: active inet 192.168.179.253 netmask 0xff00 broadcast 192.168.179.255 vlan3: flags=8843 mtu 1500 lladdr 80:ee:73:a6:be:cf index 8 priority 0 llprio 3 encap: vnetid 3 parent re0 txprio packet rxprio outer groups: vlan media: Ethernet autoselect (1000baseT full-duplex,master) status: active inet 10.0.0.253 netmask 0xff00 broadcast 10.0.0.255 vlan4: flags=8843 mtu 1500 lladdr 80:ee:73:a6:be:cf index 9 priority 0 llprio 3 encap: vnetid 4 parent re0 txprio packet rxprio outer groups: vlan media: Ethernet autoselect (1000baseT full-duplex,master) status: active inet 10.1.0.253 netmask 0xff00 broadcast 10.1.0.255 vlan5: flags=8843 mtu 1500 lladdr 80:ee:73:a6:be:cf index 10 priority 0 llprio 3 encap: vnetid 5 parent re0 txprio packet rxprio outer groups: vlan media: Ethernet autoselect (1000baseT full-duplex,master) status: active inet 172.16.0.253 netmask 0xff00 broadcast 172.16.0.255 vlan9: flags=8843 rdomain 1 mtu 1500 lladdr 80:ee:73:a6:be:cf index 11 priority 0 llprio 3 encap: vnetid 9 parent re0 txprio packet rxprio outer groups: vlan media: Ethernet autoselect (1000baseT full-duplex,master) status: active inet 185.216.161.105 netmask 0xfff8 broadcast 185.216.161.111 lo1: flags=8008 rdomain 1 mtu 32768 index 12 priority 0 llprio 3 groups: lo pflog0: flags=141 mtu 33136 index 13 priority 0 llprio 3 groups: pflog OpenBSD 6.8 (GENERIC.MP) #1: Tue Nov 3 09:06:04 MST 2020 r...@syspatch-68-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8456675328 (8064MB) avail mem = 8185331712 (7806MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec1e0 (77 entries) bios0:
Re: base LoC & committers
On Tue, 08 Dec 2020 13:49:13 +0100 Salvatore Cuzzilla wrote: > Hi Everyone, > > just out of curiosity, I was asking myself: > > - approx how many LoC do we have in *base*? > - & how many committers are actually contributing to it? > > when I think about some other OS with a kernel of almost 30M LoC & over > 5k committers I go insane :) > > > Regards, > Salvatore. $ cloc /usr/src 111439 text files. 85841 unique files. 55120 files ignored. github.com/AlDanial/cloc v 1.86 T=254.29 s (229.3 files/s, 94467.6 lines/s) --- Language files blankcomment code --- C1741212941481491393 7181673 C/C++ Header 14902 4933731021729 4255540 C++ 10637 483624 511811 2771795 Perl 4309 169414 228936 956256 Bourne Shell 1263 57662 69942 434428 Markdown 279 47833 0 407365 PO File129 141599 190451 319672 Python1461 35581 35610 134779 HTML 259 17553993 128449 Assembly 969 21343 56839 117720 yacc93 14004 8880 108162 reStructuredText 775 49070 43308 106806 Expect 460 14443 21700 74931 make 2459 15471 8987 68516 Windows Module Definition 200 6600 3 49202 m4 177 5669 3351 48578 CMake 882 5106 3729 36458 ASP.NET 2 1013 18 24717 TeX 29 3094 12237 21764 Pascal 58 3289 16255 13924 Scheme 95 1438146 12907 XML108828396 10910 lex 35 1714 1908 10441 awk 57686 1607 8210 SWIG67 2752508 7668 Fortran 77 183893 2886 7495 Oracle PL/SQL4180 1 6945 Go 26908733 6507 Objective C++ 23 1097840 6332 Objective C211 1639629 6041 YAML 100 75 60 5954 OCaml 59 1366 2512 4083 Fortran 90 73264818 3457 Korn Shell 83900 1118 3381 JSON41 1 0 2651 SQL 5 77 38 2343 sed 46221593 1848 CSS 20282105 1801 ANTLR Grammar2 0 0 1726 DOS Batch 30251103 1501 SVG 4 0 26 1361 Lisp12193452 1147 Bourne Again Shell 8170236 899 diff25124624 628 Forth1122162 596 C# 8 89107 570 JavaScript 4 79
Re: base LoC & committers
2020-12-08 13:49 GMT+01:00, Salvatore Cuzzilla : > Hi Everyone, > > just out of curiosity, I was asking myself: > > - approx how many LoC do we have in *base*? You have access to the sources. > - & how many committers are actually contributing to it? https://www.openbsd.org/donations.html > > when I think about some other OS with a kernel of almost 30M LoC & over > 5k committers I go insane :) > > > Regards, > Salvatore. > >
Re: mongodb port
On 2020-12-08, Gregory Edigarov wrote: > Hello, > > Just found that mongodb port/package doesn't not install > mongodump/mongorestore binaries. > Are there any problems with them? > > -- > With best regards, > Gregory Edigarov > > Tempted to just reply with "if it needs backing up it shouldn't be in mongodb", but... they aren't included in the main distfile and will require modifying to work with OpenBSD. https://github.com/mongodb/mongo-tools#building-tools $ ./make build START | build FAIL | build in 11.252428ms | failed to detect local platform from kernel name "OpenBSD" task(s) [build] failed exit status 2 There is some info at https://github.com/mongodb/mongo-tools/blob/master/PLATFORMSUPPORT.md but it only covers adding new Linux distros, not new OS.
base LoC & committers
Hi Everyone, just out of curiosity, I was asking myself: - approx how many LoC do we have in *base*? - & how many committers are actually contributing to it? when I think about some other OS with a kernel of almost 30M LoC & over 5k committers I go insane :) Regards, Salvatore.
mongodb port
Hello, Just found that mongodb port/package doesn't not install mongodump/mongorestore binaries. Are there any problems with them? -- With best regards, Gregory Edigarov
