Re: Libreoffice calc crash
On Tue, Aug 8, 2017 at 8:21 AM, Thubanwrote: > On 6.1 amd64, Libreoffice calc crash every time you : > - Select a cell and write changes > - Validate (by clicking elsewhere or pressing Return) > > It seems the process soffice.bin is still up, but localc is unusable. > > Anyone experiments the same issue ? > > dmesg : > > OpenBSD 6.1 (GENERIC.MP) #19: Thu Aug 3 14:59:44 CEST 2017 > rob...@syspatch-61-amd64.openbsd.org:/usr/src/sys/arch/ > amd64/compile/GENERIC.MP > I'm running -current snapshot dated Thu Aug 3 12:12:07 MDT 2017 with libreoffice-5.2.7.2p5v0 and have been doing some heavy work in Calc for the last hour without any issues. What exactly you mean by "write changes" and "validate"; just typing values in a cell and pressing Enter to finish your entry? Does it happen on a blank spreadsheet? Do you have the user account set to the "staff" class, or somehow assigning it a high datasize limit in login.conf?
Re: OpenBSD Traning Docs / How Tos
Hello Ingo, Theo, all, Thanks for taking the time to respond to my mail, I understand & agree with many of your points made, the ones I disagree with I will discuss with you over a Pint of Beer or 2, at some conference :) Ill take on board your suggestions of lots of little edits / little patches as opposed to large re-works of manuals / docs. Both of your inputs allow me to make a start at it ...and we will take it from there. We can revisit the possibility of tutorials (Not How Tos)once my understanding and documentation ability improves and that I can formulate a proposed approach that the team would would be happy with. (but this is clearly some way down the road) Thanks again and any other suggestions and tips welcome PS @Ingo Appreciate the pointers to your slides on mdoc(7) On 8 August 2017 at 03:48, Ingo Schwarzewrote: > Hi Tom, > > you are aware that the term "HOWTO" is very strongly detested round > here, right? It is considered a synonym for so-called documentation > that is imprecise, unsystematic, and tells the user to type some > random commands they won't understand because the HOWTO doesn't > really explain how things actually work. > > > Tom Smyth wrote on Mon, Aug 07, 2017 at 11:46:46PM +0100: > >> Im currently working on internal training documentation for >> our operations and field teams for dealing with OpenBSD based >> equipment. These documents would focus on OpenBSDs Network stack >> and its capabilities, diagnostics and configuration manipulation > > It would probably be hard to pick an area where working on the > documentation is harder than in the vicinity of the network stack. > Some important manual pages in that area are below-average quality > both regarding content and markup (including pf.conf(5) and > ifconfig(8)), and that is not a coincidence: The subject matter is > unusually difficult, the number of features to explain is unusually > large, the number of people qualified to judge the accuracy of the > manual pages and proposed changes is unusually small, and many of > them are unusually busy. > >> Since Im going to that trouble I thought maybe my effort could >> be aligned with the goals of the project, > > As a matter of principle, OpenBSD documentation is reference > documentation. So if you want to help the project, that would mean > improving manual pages (or maybe occasionally the FAQ, but much > less frequently). Both aim for exactness and conciseness above all > else, so writing substantial amounts of new text is unlikely to help. > >> and perhaps reduce the workload from some of the developers > > I'm not aware of any developers who currently spend significant > time on network stack documentation, so the effect would be improving > documentation, not reducing workload. But that is fine, we consider > documentation important. > > It will *increase* the workload on the developers in question because > they will have to check your diffs - jmc@ and myself will usually > be unable to do that alone because we don't understand the network > stack well enough. > >> advocates of the OpenBSD Project. > > I'm not aware of the existance of advocates, and there are certainly > no advocates who work on documentation. > >> I was discussing this with some developers at BSDCan but I didnt >> come away with a clear view of how to approach it. > > Give the manual pages to your field engineers as training documentation > for specific tasks, see how they fare with them, and if they fail > to set things up properly, figure out why. If the reason is that > they don't read carefully enough (being used to low-quality > documentation), work with them to improve their reading skills. If > the reason is that some features are not described, or with too > little precision, or wrongly, send patches to fix the gaps and bugs. > If the reason is that everything is described exactly but the subject > matter is so complicated that assembling actual commands or > configuration from the description alone is very hard, work on > adding or improving examples, focussing on *conciseness*. In any > case, the shorter the patches you send, the better. Anything > containing long newly-written text is probably of little use, at > least until you will have collected a lot of experience working on > OpenBSD documentation. > > It seems likely to me that all three elements will be needed, and > that both the first and the second will require more time and effort > than the third. > >> Could the members of OpenBSD who are responsible for OpenBSD >> Documentation, and indeed anyone who is interested in advancing / >> improving the documentation of OpenBSD get in touch so that I can >> adopt an approach that is compatible with the overall direction of >> the project and that I can finally provide practical support for >> a project that I have benefited from for so long. > > There is only one way. Get started, find bugs and gaps in the > manual pages, send patches (to
Re: syspatch question
On Tue, Aug 08, 2017 at 01:10:22PM -0400, tec...@protonmail.com wrote: > I had this exact issue a few days ago, I just re-partitioned to a > bigger size so not have to face the issue again as was a new install > anyway. But, sure would be nice to see this added. Thanks > > > From: marko.cu...@mimar.rs > > - at the moment of writing this, there are 025 patches. If applying > > them all at once, they (perhaps needlessly) need quite some space > > in /tmp (my mfs for /tmp is 256m, and it got filled already at 012), > > as a result of (I guess) deleting /tmp/syspatch.XX only > > after all the patches are applied, or after /tmp gets filled up. > > Perhaps it is possible to flush /tmp earlier in the process (maybe > > after each patch is applied successfully)? Have you tried with -current? Here is a change from June that might be what you're looking for: https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/syspatch/syspatch.sh#rev1.108
Re: gmail and hotmail blocking mail sent from my IP
I understand that given everyone uses gmail, hotmail or mail provided by some multinational hosting service they assume mail coming from residential connections cannot be other thing but spam sent from hacked machines. But someone paying for a static IP in a residential connection is the opposite case. When you have to deal with thousands of users you resort to any trick you find on the Internet and start to blindly blacklist all; this is a big servers problem. And the more users you have to deal with the worse. On the contrary, from my part, I have just a pair of personal addresses, so it's not a big deal for me to audit my server and use more sane, less harmful and, overall, more effective measures to filter spam and to prevent spam be sent from my machine. And I think this is the direction everyone should point to instead of resting day after day more and more on big companies for everything. In general, everyone should tend to decentralize instead of monopolize. The real problem is the passive attitude most people assume in the use of the Internet (and life in general but I don't want to bore you with cheap philosophy. :-)) > > Regards, Thank you for your advice. +1, way more spam comes from universities and enterprise machines than residential static ips with PTR records. It is not your error to fix. BTW Microsoft have their own SPF sign up thing but if I recall it was too much hastle and maybe pay for. Keep ignoring those that suggest using your ISP, why would you send *all* your mail through a likely untrustworthy mail system. Just accept that hotmail users often fish mail out of spam because the big mail systems are crappy.
Re: OpenBSD IPsec/L2TP to Android VPN?
You know... I can connect but can't do anything else. What is a good way to test my connection? Should I be able to ping an internal IP? Or browse my internal samba shares remotely? From: Daniel Mumford Sent: Tuesday, August 8, 2017 10:12:45 AM To: aaron marcher; R0me0 *** Cc: OpenBSD Misc Subject: Re: OpenBSD IPsec/L2TP to Android VPN? I'm up and running. Just have to clean it up a little. Thanks for your help. Dan From: Daniel Mumford Sent: Monday, August 7, 2017 10:17:07 PM To: aaron marcher; R0me0 *** Cc: OpenBSD Misc Subject: Re: OpenBSD IPsec/L2TP to Android VPN? Thanks. The links are helpful. I am troubleshooting through the log messages. Thanks again. Dan. From: owner-m...@openbsd.orgon behalf of R0me0 *** Sent: Monday, August 7, 2017 1:56:41 PM To: aaron marcher Cc: OpenBSD Misc Subject: Re: OpenBSD IPsec/L2TP to Android VPN? https://www.authbsd.com/blog/?p=20 2017-08-07 14:54 GMT-03:00 aaron marcher : > hi dan, > > i recently set up something like that using the following two tutorials > (note that this is l2tp/ipsec instead of raw ipsec): > > - http://bluepilltech.blogspot.co.at/2017/02/openbsd-l2tp- > over-ipsec-android-601-ios.html > - http://blog.fuckingwith.it/2016/04/openbsd-l2tpipsec-vpn- > for-android.html > > regards, > drkhsh > > On 17-08-07 Mon, Daniel Mumford wrote: > > > > First post on mail list. Hope I do it correctly. > > > > Is there anyone able to assist setting up an IPsec VPN between Openbsd > machine and an android device? > > > > I have worked on for a week or so to no avail. I would like to get a > good understanding of the necessary configuration. > > > > Thanks in advance. > > Dan > > -- > web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ > gpg: 0x435BF54B > >
Re: possible YP faq-doc bug ?
Hi Harold, harold felton wrote on Tue, Aug 08, 2017 at 04:19:59AM -0700: > yp-server step 9: i think requires cmd '# rcctl enable ypserv' > rather than just the file-listed to survive a reboot... > yp-client step 3: requires similar cmd '# rcctl enable ypbind' > rather than just the file-listed... True, the FAQ was outdated in several respects, including these ones. Thanks for reporting, i just updated it. > while testing this, i seemed to find that checking quotas during > bootup with only ypbind (without ypserv) on my local machine > became locked-up... hitting ^C while locked-up then would > immediately cause the normal done-message to appear... Right now, i have no idea what is going on in that repsect. I never used quotas, so i just fixed the easier parts. > as i said, i do not know much (about yp) and am still trying to > setup yp-password-changing - which seems to want a non-existent > yppasswdd (daemon) next ??? That was deleted about two years ago: https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/libexec/rpc.yppasswdd/Attic/Makefile Yours, Ingo
Re: syspatch question
I had this exact issue a few days ago, I just re-partitioned to a bigger size so not have to face the issue again as was a new install anyway. But, sure would be nice to see this added. Thanks > Original Message > Subject: Re: syspatch question > Local Time: August 8, 2017 4:20 PM > UTC Time: August 8, 2017 3:20 PM > From: marko.cu...@mimar.rs > To: Antoine Jacoutot> misc@openbsd.org, Igor Falcomata' > On Tue, 08 Aug 2017 13:14:43 +0200 > Antoine Jacoutot wrote: >> I"ll have a look at it thanks. > I"m aware that noone is going to optimize syspatch for my corner case, > but here are a few observations regarding my experience with it: > - at the moment of writing this, there are 025 patches. If applying > them all at once, they (perhaps needlessly) need quite some space > in /tmp (my mfs for /tmp is 256m, and it got filled already at 012), > as a result of (I guess) deleting /tmp/syspatch.XX only > after all the patches are applied, or after /tmp gets filled up. > Perhaps it is possible to flush /tmp earlier in the process (maybe > after each patch is applied successfully)? > - syspatch silently fails if it cannot contact installurl server. > Perhaps some warning could be added? > Best regards, > -- > Before enlightenment - chop wood, draw water. > After enlightenment - chop wood, draw water. > Marko Cupać > https://www.mimar.rs/
Re: gmail and hotmail blocking mail sent from my IP
My suggestion to resolve the whole issue: forward mail through your ISP's mailserver or go and buy a cheap VPS. Amazon EC2 micro instances work fine for the purpose, and it is possible with some hackery to install OpenBSD on them. --- “Lanie, I’m going to print more printers. Lots more printers. One for everyone. That’s worth going to jail for. That’s worth anything.” - Printcrime by Cory Doctrow Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html On Tue, Aug 8, 2017 at 5:25 PM, Walter Alejandro Iglesiaswrote: > In article <20170808121343.46a8ddb9@fir.internal> you wrote: > > Hi Walter: > > > > On Sun, 6 Aug 2017 19:45:22 +0200 Walter Alejandro Iglesias wrote: > > > What determines those "ranges", who regulates that? > > > > Some ISPs submit IP blocks to various blacklists. e.g: > > https://www.Spamhaus.Org/faq/section/Spamhaus%20PBL#242 > > http://www.Sorbs.Net/faq/dul.shtml > > > > Asking your ISP to exclude your addresses might help. > > > I sent an email to my ISP, they don't even know about this lists. :-) > > Besides, I sent an email to spamhaus.org suggesting them not to include > static IPs in their PBL list by default as they do. > > > I'll take this chance to share my thinking with everyone here. > > I understand that given everyone uses gmail, hotmail or mail provided by > some multinational hosting service they assume mail coming from > residential connections cannot be other thing but spam sent from hacked > machines. But someone paying for a static IP in a residential > connection is the opposite case. When you have to deal with thousands > of users you resort to any trick you find on the Internet and start to > blindly blacklist all; this is a big servers problem. And the more > users you have to deal with the worse. On the contrary, from my part, I > have just a pair of personal addresses, so it's not a big deal for me to > audit my server and use more sane, less harmful and, overall, more > effective measures to filter spam and to prevent spam be sent from my > machine. And I think this is the direction everyone should point to > instead of resting day after day more and more on big companies for > everything. In general, everyone should tend to decentralize instead of > monopolize. The real problem is the passive attitude most people assume > in the use of the Internet (and life in general but I don't want to bore > you with cheap philosophy. :-)) > > > > > > Regards, > > > Thank you for your advice. > >
Re: gmail and hotmail blocking mail sent from my IP
In article <20170808121343.46a8ddb9@fir.internal> you wrote: > Hi Walter: > > On Sun, 6 Aug 2017 19:45:22 +0200 Walter Alejandro Iglesias wrote: > > What determines those "ranges", who regulates that? > > Some ISPs submit IP blocks to various blacklists. e.g: > https://www.Spamhaus.Org/faq/section/Spamhaus%20PBL#242 > http://www.Sorbs.Net/faq/dul.shtml > > Asking your ISP to exclude your addresses might help. I sent an email to my ISP, they don't even know about this lists. :-) Besides, I sent an email to spamhaus.org suggesting them not to include static IPs in their PBL list by default as they do. I'll take this chance to share my thinking with everyone here. I understand that given everyone uses gmail, hotmail or mail provided by some multinational hosting service they assume mail coming from residential connections cannot be other thing but spam sent from hacked machines. But someone paying for a static IP in a residential connection is the opposite case. When you have to deal with thousands of users you resort to any trick you find on the Internet and start to blindly blacklist all; this is a big servers problem. And the more users you have to deal with the worse. On the contrary, from my part, I have just a pair of personal addresses, so it's not a big deal for me to audit my server and use more sane, less harmful and, overall, more effective measures to filter spam and to prevent spam be sent from my machine. And I think this is the direction everyone should point to instead of resting day after day more and more on big companies for everything. In general, everyone should tend to decentralize instead of monopolize. The real problem is the passive attitude most people assume in the use of the Internet (and life in general but I don't want to bore you with cheap philosophy. :-)) > > Regards, Thank you for your advice.
Re: syspatch question
On Tue, 08 Aug 2017 13:14:43 +0200 Antoine Jacoutotwrote: > I'll have a look at it thanks. I'm aware that noone is going to optimize syspatch for my corner case, but here are a few observations regarding my experience with it: - at the moment of writing this, there are 025 patches. If applying them all at once, they (perhaps needlessly) need quite some space in /tmp (my mfs for /tmp is 256m, and it got filled already at 012), as a result of (I guess) deleting /tmp/syspatch.XX only after all the patches are applied, or after /tmp gets filled up. Perhaps it is possible to flush /tmp earlier in the process (maybe after each patch is applied successfully)? - syspatch silently fails if it cannot contact installurl server. Perhaps some warning could be added? Best regards, -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
Re: OpenBSD IPsec/L2TP to Android VPN?
I'm up and running. Just have to clean it up a little. Thanks for your help. Dan From: Daniel Mumford Sent: Monday, August 7, 2017 10:17:07 PM To: aaron marcher; R0me0 *** Cc: OpenBSD Misc Subject: Re: OpenBSD IPsec/L2TP to Android VPN? Thanks. The links are helpful. I am troubleshooting through the log messages. Thanks again. Dan. From: owner-m...@openbsd.orgon behalf of R0me0 *** Sent: Monday, August 7, 2017 1:56:41 PM To: aaron marcher Cc: OpenBSD Misc Subject: Re: OpenBSD IPsec/L2TP to Android VPN? https://www.authbsd.com/blog/?p=20 2017-08-07 14:54 GMT-03:00 aaron marcher : > hi dan, > > i recently set up something like that using the following two tutorials > (note that this is l2tp/ipsec instead of raw ipsec): > > - http://bluepilltech.blogspot.co.at/2017/02/openbsd-l2tp- > over-ipsec-android-601-ios.html > - http://blog.fuckingwith.it/2016/04/openbsd-l2tpipsec-vpn- > for-android.html > > regards, > drkhsh > > On 17-08-07 Mon, Daniel Mumford wrote: > > > > First post on mail list. Hope I do it correctly. > > > > Is there anyone able to assist setting up an IPsec VPN between Openbsd > machine and an android device? > > > > I have worked on for a week or so to no avail. I would like to get a > good understanding of the necessary configuration. > > > > Thanks in advance. > > Dan > > -- > web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ > gpg: 0x435BF54B > >
Libreoffice calc crash
On 6.1 amd64, Libreoffice calc crash every time you : - Select a cell and write changes - Validate (by clicking elsewhere or pressing Return) It seems the process soffice.bin is still up, but localc is unusable. Anyone experiments the same issue ? dmesg : OpenBSD 6.1 (GENERIC.MP) #19: Thu Aug 3 14:59:44 CEST 2017 rob...@syspatch-61-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 8454270976 (8062MB) avail mem = 8193368064 (7813MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (65 entries) bios0: vendor LENOVO version "8CET46WW (1.26 )" date 07/11/2011 bios0: LENOVO 4174EL7 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT SSDT DMAR UEFI UEFI UEFI acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2492.28 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2492283000 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus 5 (EXP4) acpiprt5 at acpi0: bus 13 (EXP5) acpicpu0 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS acpicpu1 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS acpicpu2 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS acpicpu3 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 acpitz0 at acpi0: critical temperature is 97 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "PNP0303" at acpi0 not configured "LEN0015" at acpi0 not configured "SMO1200" at acpi0 not configured acpibat0 at acpi0: BAT0 model "42T4845" serial 20446 type LION oem "SANYO" acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured acpivideo0 at acpi0: VID_ acpivout at acpivideo0 not configured acpivideo1 at acpi0: VID_ cpu0: Enhanced SpeedStep 2492 MHz: speeds: 2501, 2500, 2200, 2000, 1800, 1600, 1400, 1200, 1000, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0
Re: OpenBSD Traning Docs / How Tos
On 08/08/17 03:54, Mihai Popescu wrote: > Hello Tom, > > I am not an expert user of OpenBSD but I want to tell you the FAQ is > the first step. That is maintained by Nick Holland, ... I really hate to correct someone who says such nice things about my work, but ... I stepped aside a while back to wiggle priorities around in my life a bit. I am happy to report that Theo Buehler and T. J. Townsend have stepped up and done a great job of maintaining and improving the FAQ (and much of the rest of the website, and making contributions to the rest of the project as well). (I am, of course, still active in the OpenBSD community, but racking up more miles on my motorcycles, too...) Nick.
possible YP faq-doc bug ?
howdee, not sure, since this is the first time ive tried to do it, but... faq10 - YP setups yp-server step 9: i think requires cmd '# rcctl enable ypserv' rather than just the file-listed to survive a reboot... yp-client step 3: requires similar cmd '# rcctl enable ypbind' rather than just the file-listed... while testing this, i seemed to find that checking quotas during bootup with only ypbind (without ypserv) on my local machine became locked-up... hitting ^C while locked-up then would immediately cause the normal done-message to appear... as i said, i do not know much (about yp) and am still trying to setup yp-password-changing - which seems to want a non-existent yppasswdd (daemon) next ??? i only read misc-digest-daily - so apologies-in-advance if i do not see replies quickly... also, if it matters, i could provide my yp information that was semi-copied from the faq (moved src-dir)... it appears that for-my-uses, i should just use cron and scp as mentioned in the faq already... also, since im enclosing my dmesg - apparently i still have a bit of hw-debug to do (prolly uefi or somesuch)... anyways... sincerely, hfelton syncing disks... done rebooting. OpenBSD 6.1-current (GENERIC.MP) #48: Mon Aug 7 15:24:13 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 10410303488 (9928MB) avail mem = 10088443904 (9621MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe96e0 (74 entries) bios0: vendor American Megatrends Inc. version "4.6.5" date 05/22/2014 bios0: ZOTAC ZBOX-ID88/ID89/ID90 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG MSDM HPET SSDT SSDT SSDT BGRT acpi0: wakeup devices P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i3-3220T CPU @ 2.80GHz, 2794.13 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2794125600 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i3-3220T CPU @ 2.80GHz, 2793.66 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i3-3220T CPU @ 2.80GHz, 2793.66 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i3-3220T CPU @ 2.80GHz, 2793.66 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 2 (RP01) acpiprt3 at acpi0: bus 3 (RP02) acpiprt4 at acpi0: bus 4 (RP03) acpiprt5 at acpi0: bus -1 (RP04) acpiprt6 at acpi0: bus 5 (RP05) acpiprt7 at acpi0: bus -1 (RP06) acpiprt8 at acpi0: bus -1 (RP07) acpiprt9 at acpi0: bus -1 (RP08) acpiprt10 at acpi0: bus 1 (PEG0) acpiprt11 at acpi0: bus -1 (PEG1) acpiprt12 at acpi0: bus -1 (PEG2) acpiprt13 at acpi0: bus -1 (PEG3) acpiec0 at acpi0: not present acpicpu0 at acpi0: C3(350@80 mwait.1@0x20), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(350@80 mwait.1@0x20), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(350@80 mwait.1@0x20), C2(500@59 mwait.1@0x10), C1(1000@1
Re: syspatch question
On August 8, 2017 12:28:46 PM GMT+02:00, Igor Falcomata'wrote: >On Thu, Aug 31, 2017 at 13:56:13, Marko Cupa?? wrote: > >>...but the problem I am facing is that syspatch -l shows installed >>patches up to 013: > >I got the same problem; after a quick investigation i found that >syspatch will >silently fail if TMPDIR is defined and isn't /tmp (i suspect is related >to the >ftp part, because it quits just after the CWD, but i haven't >investigated more >deeply): > >CWD pub/OpenBSD/syspatch/6.1/amd64 >250 CWD command successful >QUIT > >This way should work: ># TMPDIR=/tmp syspatch -c > >ciao, >I. I'll have a look at it thanks. -- Antoine
Re: gmail and hotmail blocking mail sent from my IP
Hi Walter: On Sun, 6 Aug 2017 19:45:22 +0200 Walter Alejandro Iglesias wrote: > What determines those "ranges", who regulates that? Some ISPs submit IP blocks to various blacklists. e.g: https://www.Spamhaus.Org/faq/section/Spamhaus%20PBL#242 http://www.Sorbs.Net/faq/dul.shtml Asking your ISP to exclude your addresses might help. Regards, -- Craig Skinner | http://twitter.com/Craig_Skinner | http://linkd.in/yGqkv7
Re: syspatch question
On Thu, Aug 31, 2017 at 13:56:13, Marko Cupa?? wrote: >...but the problem I am facing is that syspatch -l shows installed >patches up to 013: I got the same problem; after a quick investigation i found that syspatch will silently fail if TMPDIR is defined and isn't /tmp (i suspect is related to the ftp part, because it quits just after the CWD, but i haven't investigated more deeply): CWD pub/OpenBSD/syspatch/6.1/amd64 250 CWD command successful QUIT This way should work: # TMPDIR=/tmp syspatch -c ciao, I.
Re: OpenBSD Traning Docs / How Tos
Hello Tom, I am not an expert user of OpenBSD but I want to tell you the FAQ is the first step. That is maintained by Nick Holland, an OpenBSD user an a man with great experince on the field. You may think that FAQ is redundant for man, or even that man paragraphs are simply copied into the FAQ, but this is not the case! Nick Holland took great care into selecting the scenarios and walk you thru OpenBSD installation and configuration with great care and warnings. He did a nice structure with hyperlink and man pages in order to prepare you for basic steps. You can even extrapolate and do your own custom configurations. If you still need details, there are a few books there written by OpenBSD users. One can get a simple idea about how things are put together by reading that FAQ. If you will try to use HOWTOs, there will be a time when people will cripple an OpenBSD installation and there is nothing to be done in time. Creating another parallel documentation is a fancy activity, but mostly a waste of time. Think at one thing: over time, changes are done to the system and the documentation you've created must be modified. Even worse, think that old documentation is at hand and some user will try to use it on a new system. There are also many implication much better detailed on the lists by well trained people. Many tanks to them, too. Thank you for listening.
Re: odd segfault when adding -lutil
Hey thanks a million! I looked on your homepage and didn't find any paypal address listed so I'm going to donate in your name to Theo. I think when you two meet Theo should buy you a beer with part of the money. :-), or any other beverage in case you don't like beer. Thanks again! Donation sent. -peter On 08/08/17 01:36, Jeremie Courreges-Anglas wrote: > On Mon, Aug 07 2017, "Peter J. Philipp"wrote: >> Hi, > Hi, > >> I'm writing to misc because I did a change with my programming project and >> it doesn't work, in fact the program does not start up but in the dynamic >> linking stage (it seems) cores on segmentation violation. I have tried >> different architectures (amd64 and octeon) and -current and both have the >> same problem, but I develop mostly on 6.1. When I run it through a debugger >> I get this: >> >> (gdb) run >> Starting program: /usr/local/sbin/delphinusdnsd >> (no debugging symbols found) >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x18c933300c94 in ?? () from /usr/local/sbin/delphinusdnsd >> (gdb) bt >> #0 0x18c933300c94 in ?? () from /usr/local/sbin/delphinusdnsd >> #1 0x18c933300b3e in ?? () from /usr/local/sbin/delphinusdnsd >> #2 0x in ?? () >> >> Apparently somewhere in the program something jumps to location 0 and from >> there it's downhill. >> >> Also the very first system call (a geteuid()) does not get called making me >> think it's before main() has been called. I'm completely boggled by this. >> >> # kdump | grep -3 geteuid >> # >> >> The last committed snapshot of my program is found here, and afaik it works: >> >> http://delphinusdns.org/delphinusdnsd-snapshot.tgz >> >> The changes I'm working on now which causes this weird behaviour is to tie in >> imsg into my program and that means linking -lutil with this program. I've >> checked if there was any macro collisions with TAILQ's or RB_HEAD's and >> tried >> to move those out of the way but still I get the segmentation fault. >> >> If anyone has an idea as to what could be the cause of this I'd be grateful. > Your program blows up the stack right at the start of main(), and gdb > doesn't seem to handle this very nicely. egdb from ports shows you > the faulty instruction in the listing of ''disas main'', gdb from base > doesn't seem to do that (but you can still find it out manually). > > Increasing the max stack size with ulimit -s, reducing the size of the > parent_ibuf and child_ibuf arrays, or allocating them in a different way > would work around those issues. > > [...] >