Re: uvm_fault on resume with athn(4)
hey josh, this should be fixed in src/sys/dev/pci/if_athn_pci.c r1.13. sorry for the inconvenience, but thank you for the report, especially the backtrace. cheers, dlg On 23 November 2013 16:37, Josh Grosse wrote: > Summary: with src/sys/dev/pci/if_athn_pci.c at revision 1.12, > suspend/resume > will produce a uvm_fault on resume. I cannot reproduce the panic if I > revert > to revision 1.11. > > Of note: ddb(4) produces a brief traceback and a prompt but is inoperative. > I am unable to get a dump if ddb.panic=0. This traceback was transposed > by hand. > > uvm_fault(0xd0b1a860, 0x0, 0, 1) -> e > kernel: page fault trap, code=0 > Stopped at mtx_enter+0x6: movl0x4(%ecx),%eax > mtx_enter(10,8002,50,d1fea000,d1fc6a80) at mtx_enter+0x6 > task_add(0,d1fec088,f5bc7e1c,d03cfde5,d1fea000) at task_add+0x20 > athn_pci_activate(d1fea000,3,f5bc7e1c,d0597b3e,d1fc6a80) at > athn_pci_activate+0x2b > config_activate_children(d1fc6a80,3,f5bc7e4c,d059582c,0) at > config_activate_children+0x45 > config_activate_children(d1fb6f00,3,4,100106,f5bc7e7c) at > config_activate_children+0x45 > ppbactivate(d1fb6f00,3,f5bc7ebc,d0597b3e,d1e7b900) at ppbactivate+0x289 > config_activate_children(d1e7b900,3,0,3,0) at config_activate_children+0x45 > config_activate_children(d1f67000,3,0,c731,3) at > config_activate_children+0x45 > acpi_sleep_state(d1e7a400,3,f5bc7f5c,d0ecb31a,d205e570) at > acpi_sleep_state+0x2c3 > acpi_sleep_task(d1e7a400,3,d6efe91c,1,d1e7a400) at acpi_sleep_task+0x1a > ddb{0}> > > OpenBSD 5.4-current (GENERIC.MP) #141: Thu Nov 21 15:03:32 MST 2013 > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP > cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class) 1.60 > GHz > cpu0: > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF > real mem = 1064497152 (1015MB) > avail mem = 1035247616 (987MB) > mainbus0 at root > bios0 at mainbus0: AT/286+ BIOS, date 04/18/11, BIOS32 rev. 0 @ 0xf0010, > SMBIOS rev. 2.5 @ 0xf0720 (30 entries) > bios0: vendor American Megatrends Inc. version "1601" date 04/18/2011 > bios0: ASUSTeK Computer INC. 1005HA > acpi0 at bios0: rev 0 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT > acpi0: wakeup devices P0P2(S4) P0P1(S4) HDAC(S4) P0P4(S4) P0P8(S4) > P0P5(S4) P0P7(S4) P0P9(S4) P0P6(S4) > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: apic clock running at 133MHz > cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2, IBE > cpu1 at mainbus0: apid 1 (application processor) > cpu1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class) 1.60 > GHz > cpu1: > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins > ioapic0: misconfigured as apic 1, remapped to apid 2 > acpimcfg0 at acpi0 addr 0xe000, bus 0-63 > acpihpet0 at acpi0: 14318179 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 2 (P0P5) > acpiprt2 at acpi0: bus 1 (P0P7) > acpiprt3 at acpi0: bus -1 (P0P6) > acpiec0 at acpi0 > acpicpu0 at acpi0: C3, C2, C1, PSS > acpicpu1 at acpi0: C3, C2, C1, PSS > acpitz0 at acpi0: critical temperature is 88 degC > acpibat0 at acpi0: BAT0 model "1005HA" serial type LION oem "ASUS" > acpiac0 at acpi0: AC unit offline > acpiasus0 at acpi0 > acpibtn0 at acpi0: LID_ > acpibtn1 at acpi0: SLPB > acpibtn2 at acpi0: PWRB > bios0: ROM list: 0xc/0xec00! > cpu0: Enhanced SpeedStep 1600 MHz: speeds: 1600, 1333, 1067, 800 MHz > pci0 at mainbus0 bus 0: configuration mode 1 (bios) > pchb0 at pci0 dev 0 function 0 "Intel 82945GME Host" rev 0x03 > vga1 at pci0 dev 2 function 0 "Intel 82945GME Video" rev 0x03 > intagp0 at vga1 > agp0 at intagp0: aperture at 0xd000, size 0x1000 > inteldrm0 at vga1 > drm0 at inteldrm0 > inteldrm0: 1024x600 > wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) > wsdisplay0: screen 1-5 added (std, vt100 emulation) > "Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured > azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi > azalia0: codecs: Realtek ALC269 > audio0 at azalia0 > ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 2 int 16 > pci1 at ppb0 bus 4 > ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 2 int 17 > pci2 at ppb1 bus 2 > athn0 at pci2 dev 0 function 0 "Atheros AR9285" rev 0x01: apic 2 int 17 > athn0: AR9285 rev 2 (1T1R), ROM rev 13, address 00:25:d3:8a:f6:b4 > ppb2 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x02: apic 2 int 19 > pci3 at ppb2 bus 1 > alc0 at pci3 dev 0 function 0 "Attansic Technology L2C" rev 0xc0: msi, > address 90:e6:ba:37:cf:5e > atphy0 a
uvm_fault on resume with athn(4)
Summary: with src/sys/dev/pci/if_athn_pci.c at revision 1.12, suspend/resume will produce a uvm_fault on resume. I cannot reproduce the panic if I revert to revision 1.11. Of note: ddb(4) produces a brief traceback and a prompt but is inoperative. I am unable to get a dump if ddb.panic=0. This traceback was transposed by hand. uvm_fault(0xd0b1a860, 0x0, 0, 1) -> e kernel: page fault trap, code=0 Stopped at mtx_enter+0x6: movl0x4(%ecx),%eax mtx_enter(10,8002,50,d1fea000,d1fc6a80) at mtx_enter+0x6 task_add(0,d1fec088,f5bc7e1c,d03cfde5,d1fea000) at task_add+0x20 athn_pci_activate(d1fea000,3,f5bc7e1c,d0597b3e,d1fc6a80) at athn_pci_activate+0x2b config_activate_children(d1fc6a80,3,f5bc7e4c,d059582c,0) at config_activate_children+0x45 config_activate_children(d1fb6f00,3,4,100106,f5bc7e7c) at config_activate_children+0x45 ppbactivate(d1fb6f00,3,f5bc7ebc,d0597b3e,d1e7b900) at ppbactivate+0x289 config_activate_children(d1e7b900,3,0,3,0) at config_activate_children+0x45 config_activate_children(d1f67000,3,0,c731,3) at config_activate_children+0x45 acpi_sleep_state(d1e7a400,3,f5bc7f5c,d0ecb31a,d205e570) at acpi_sleep_state+0x2c3 acpi_sleep_task(d1e7a400,3,d6efe91c,1,d1e7a400) at acpi_sleep_task+0x1a ddb{0}> OpenBSD 5.4-current (GENERIC.MP) #141: Thu Nov 21 15:03:32 MST 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class) 1.60 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF real mem = 1064497152 (1015MB) avail mem = 1035247616 (987MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 04/18/11, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.5 @ 0xf0720 (30 entries) bios0: vendor American Megatrends Inc. version "1601" date 04/18/2011 bios0: ASUSTeK Computer INC. 1005HA acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT acpi0: wakeup devices P0P2(S4) P0P1(S4) HDAC(S4) P0P4(S4) P0P8(S4) P0P5(S4) P0P7(S4) P0P9(S4) P0P6(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 133MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class) 1.60 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 1, remapped to apid 2 acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (P0P5) acpiprt2 at acpi0: bus 1 (P0P7) acpiprt3 at acpi0: bus -1 (P0P6) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpitz0 at acpi0: critical temperature is 88 degC acpibat0 at acpi0: BAT0 model "1005HA" serial type LION oem "ASUS" acpiac0 at acpi0: AC unit offline acpiasus0 at acpi0 acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: PWRB bios0: ROM list: 0xc/0xec00! cpu0: Enhanced SpeedStep 1600 MHz: speeds: 1600, 1333, 1067, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 "Intel 82945GME Host" rev 0x03 vga1 at pci0 dev 2 function 0 "Intel 82945GME Video" rev 0x03 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1024x600 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi azalia0: codecs: Realtek ALC269 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 2 int 16 pci1 at ppb0 bus 4 ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 2 int 17 pci2 at ppb1 bus 2 athn0 at pci2 dev 0 function 0 "Atheros AR9285" rev 0x01: apic 2 int 17 athn0: AR9285 rev 2 (1T1R), ROM rev 13, address 00:25:d3:8a:f6:b4 ppb2 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x02: apic 2 int 19 pci3 at ppb2 bus 1 alc0 at pci3 dev 0 function 0 "Attansic Technology L2C" rev 0xc0: msi, address 90:e6:ba:37:cf:5e atphy0 at alc0 phy 0: F1 10/100/1000 PHY, rev. 11 uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 2 int 23 uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 2 int 19 uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 2 int 18 uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 2 int 16 ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic
Re: Patch to remove "adult" content from spamd(8) man page
On 11/22/2013 10:50 AM, Rick Pettit wrote: Lewis, If censorship is your thing, why don’t you start by censoring yourself. What you are asking for here is offensive. -Rick +1 On Nov 22, 2013, at 12:26 PM, Paolo Aglialoro wrote: Il 22/nov/2013 19:07 "J. Lewis Muir" ha scritto: On 11/22/13 11:17 AM, Giancarlo Razzolini wrote: If it's offensive for you, compile your own spamd man page with the diff you so happily provided, and live the rest of your life happy. Remember to always take this pill again on 1st of May, and 1st of November, every year. Hi, Giancarlo. Well, no one wants to maintain a patch forever. I'd maintain it for a while if there was a good chance it would get accepted at some point, but if there's no chance, then I wouldn't bother. I'm a little puzzled over the whole resistance to the patch. If I wrote a man page for some software I wrote, and if an example in it was considered off-color by someone, and that someone submitted a patch to me to change it slightly to no longer be off-color to them, and they asked in a kind way, and the patch didn't hurt the clarity of the man page in any way, I would likely accept the patch. How am I hurt by it? I may not agree with the person, but why would I insist on keeping an example that seems off-color to them? If it's somehow offensive to them and can be changed in a small way not to be, then I would accept the patch to change it. Everybody wins--no big deal. Lewis +1
Re: Patch to remove "adult" content from spamd(8) man page
> It looks like a pretty one-sided deal you're proposing: > passive-aggressive moves to control the speech of those who have > respected your freedom to express your opinion and be heard. Pretty > damned selfish behavior on your part as far as I can tell. Michael -- well said.
Re: Patch to remove "adult" content from spamd(8) man page
On Nov 22, 2013, at 10:06 AM, J. Lewis Muir wrote: > On 11/22/13 11:17 AM, Giancarlo Razzolini wrote: >> If it's offensive for you, compile your own spamd man page with >> the diff you so happily provided, and live the rest of your life >> happy. Remember to always take this pill again on 1st of May, and 1st >> of November, every year. > > Hi, Giancarlo. > > Well, no one wants to maintain a patch forever. I'd maintain it for a > while if there was a good chance it would get accepted at some point, > but if there's no chance, then I wouldn't bother. > > I'm a little puzzled over the whole resistance to the patch. If I > wrote a man page for some software I wrote, and if an example in it was > considered off-color by someone, and that someone submitted a patch to > me to change it slightly to no longer be off-color to them, and they > asked in a kind way, and the patch didn't hurt the clarity of the man > page in any way, I would likely accept the patch. How am I hurt by it? > I may not agree with the person, but why would I insist on keeping an > example that seems off-color to them? If it's somehow offensive to them > and can be changed in a small way not to be, then I would accept the > patch to change it. Everybody wins--no big deal. > > Lewis > It looks like a pretty one-sided deal you're proposing: passive-aggressive moves to control the speech of those who have respected your freedom to express your opinion and be heard. Pretty damned selfish behavior on your part as far as I can tell. If I had the skill, time and energy to generate a patch it would be for something that's actually broken and in need of fixing. M
Re: mongodb
On Fri, Nov 22, 2013 at 4:18 PM, Chris Smith wrote: > Mentioned previously: > > On Tue, Oct 22, 2013 at 12:29 PM, Stuart Henderson > wrote: > > Note that the mongodb port is currently broken (and has been since > 5.3-ish iirc). > > Wondering if mongodb is operational with -current? > > No
mongodb
Mentioned previously: On Tue, Oct 22, 2013 at 12:29 PM, Stuart Henderson wrote: > Note that the mongodb port is currently broken (and has been since 5.3-ish > iirc). Wondering if mongodb is operational with -current? Thank you, Chris
Re: npppd l2tp/ipsec - openbsd client
On 2013-11-22, haris wrote: > Hi, > > first of all, thanks @sthen for your answer (OP has no net access atm). > > We are to the point where the clients get ip (windows/linux/OpenBSD) and > traffic is passing through the server as expected. > > There is a very strange problem with ssh service though. While internet > traffic > is being routed as expected, when we try to ssh, we can't connect (from > OpenBSD > clients) to any server. This is very likely to be an MTU problem. Packets of certain sizes get through OK but packets larger than a certain size won't make it through. This is hitting OpenSSH rather than PuTTY because, with default settings, OpenSSH's negotiation packets are larger than PuTTY's (more options, more ciphers, etc). If you connect with PuTTY and start sending a bunch of bulk data over the connection (cat a large file or something), I am pretty sure that will stall too. Things you can try to fix it: - lower MTU on the ppp interface - "tcp-mss-adjust yes" in npppd - pf "match ... scrub (max-mss $somevalue)"
Re: Patch to remove "adult" content from spamd(8) man page
On Fri, 22 Nov 2013, J. Lewis Muir wrote: > On 11/22/13 11:17 AM, Giancarlo Razzolini wrote: > > If it's offensive for you, compile your own spamd man page with > > the diff you so happily provided, and live the rest of your life > > happy. Remember to always take this pill again on 1st of May, and 1st > > of November, every year. > > Hi, Giancarlo. > > Well, no one wants to maintain a patch forever. I'd maintain it for a > while if there was a good chance it would get accepted at some point, > but if there's no chance, then I wouldn't bother. > > I'm a little puzzled over the whole resistance to the patch. If I > wrote a man page for some software I wrote, and if an example in it was > considered off-color by someone, and that someone submitted a patch to > me to change it slightly to no longer be off-color to them, and they > asked in a kind way, and the patch didn't hurt the clarity of the man > page in any way, I would likely accept the patch. How am I hurt by it? > I may not agree with the person, but why would I insist on keeping an > example that seems off-color to them? If it's somehow offensive to them > and can be changed in a small way not to be, then I would accept the > patch to change it. Everybody wins--no big deal. I don't know about others, but I tend to say something that offends others far more often than others saying something that offends me. It's not that I intend to offend people -- in many cases I have no idea why they were offended. For the most part, I've given up worrying about it. Eric
Re: Patch to remove "adult" content from spamd(8) man page
On 22 November 2013 10:06, J. Lewis Muir wrote: > On 11/22/13 11:17 AM, Giancarlo Razzolini wrote: >> If it's offensive for you, compile your own spamd man page with >> the diff you so happily provided, and live the rest of your life >> happy. Remember to always take this pill again on 1st of May, and 1st >> of November, every year. > > Hi, Giancarlo. > > Well, no one wants to maintain a patch forever. I'd maintain it for a > while if there was a good chance it would get accepted at some point, > but if there's no chance, then I wouldn't bother. > > I'm a little puzzled over the whole resistance to the patch. If I > wrote a man page for some software I wrote, and if an example in it was > considered off-color by someone, and that someone submitted a patch to > me to change it slightly to no longer be off-color to them, and they > asked in a kind way, and the patch didn't hurt the clarity of the man > page in any way, I would likely accept the patch. How am I hurt by it? > I may not agree with the person, but why would I insist on keeping an > example that seems off-color to them? If it's somehow offensive to them > and can be changed in a small way not to be, then I would accept the > patch to change it. Everybody wins--no big deal. > > Lewis Yet, (0), you're not the one who wrote this software, or, in fact, any other *BSD software that I could find, so I'm not sure you're empirically qualified to make the claim about authorship that you're now making, and, (1), what makes you think that your patch doesn't hurt the clarity of the man-page in any way? C.
Re: Patch to remove "adult" content from spamd(8) man page
On Fri, Nov 22, 2013 at 09:48:02PM +0100, Alexander Hall wrote: > > I'm pretty sure Bob has noticed (and likely quite some time ago > ignored) this conversation. > > You made your point and argumented for it. It does not apply here > though, so stop. Now. Please. > Actually, the longer it runs, the bigger my shitlist to test some filters grows :-P -- Gilles Chehade https://www.poolp.org @poolpOrg
Re: Patch to remove "adult" content from spamd(8) man page
On 11/22/13 20:09, J. Lewis Muir wrote: On 11/22/13 12:34 PM, System Administrator wrote: Hi J. Lewis, I am not a developer, but I've been lurking on this list for a very long time and on that basis can tell you that you've committed two cardinal sins as far as this mailing list is concerned: 1) you failed to do your homework -- had you done some research, in particular about the OpenBSD development philosophy, you would know that Hi, Jacob. It's unclear to me exactly what homework you think I failed to do. I am aware of and like lots of things that the OpenBSD project strives for. 2) OpenBSD is the ultimate volunteer effort -- the developers do it in their "free" time FOR PERSONAL FUN. Many of them have made it very clear that they would cease development if it stops being fun. Your original message (title and intro) goes to the heart of this issue. Its tone and attitude is no different than the efforts in the Bible Belt to ban Mark Twain's Huckleberry Fin from public libraries, i.e. since somebody finds some content to be "offensive" lets get rid of it irrespective of the overall true value or consideration for the fact that the author has used the "offensive" language ON PURPOSE. I don't see it that way. Huckleberry Finn is a book, and I don't need to read it unless I want to. The spamd(8) man page is a man page I need to read in order to understand how to use spamd. And if the author of the spamd(8) man page did use the "offensive" language on purpose and thinks it's important to keep it that way, I would accept that. I'd disagree, but I'd accept that. But it seems the author doesn't think it's so important either way. So, I don't get the strong resistance. I'm pretty sure Bob has noticed (and likely quite some time ago ignored) this conversation. You made your point and argumented for it. It does not apply here though, so stop. Now. Please. /Alexander
Re: Patch to remove "adult" content from spamd(8) man page
J. Lewis Muir wrote: If it's somehow offensive to them and can be changed in a small way not to be, then I would accept the patch to change it. Everybody wins--no big deal. If everybody adapts what they say, to what they think others want to hear, then we no longer have freedom of speach. Everybody looses. But then I live in a country that, unlike the USA, actually has freedom of speach... Best regards, Mikkel C. Simonsen
Re: Patch to remove "adult" content from spamd(8) man page
On Nov 21 20:04:32, gil...@poolp.org wrote: > On Thu, Nov 21, 2013 at 08:02:06PM +0100, za...@gmx.com wrote: > > Different people have different concepts of morality. I believe it > > would be better to remove anything that is controversial, for > > whatever reason You emails are controversial, apparently. Remove them, just to be on the safe side.
Re: Patch to remove "adult" content from spamd(8) man page
> > I don't see it that way. Huckleberry Finn is a book, and I don't need > > to read it unless I want to. The spamd(8) man page is a man page I need > > to read in order to understand how to use spamd. > > Let me fix that for you: > > "The spamd(8) man page is a man page I don't need to read it unless I > want to use spamd, a choice I am making of my own free will, and if I > don't like it, I guess I could just go use some other software that > doesn't get my panties in a bunch." > > Maybe you could try spam assassin instead? Unless, of course, you find > the metaphor of "killing" spam offensive... http://spamassassin.apache.org/tests_3_0_x.html He might be out of luck. There might not be software to do this, without being offended. In which case it probably falls back to the "manual method"...
Re: Patch to remove "adult" content from spamd(8) man page
> 2) OpenBSD is the ultimate volunteer effort -- the developers do it in > their "free" time FOR PERSONAL FUN. Many of them have made it very > clear that they would cease development if it stops being fun. Your > original message (title and intro) goes to the heart of this issue. Its > tone and attitude is no different than the efforts in the Bible Belt to > ban Mark Twain's Huckleberry Fin from public libraries, i.e. since > somebody finds some content to be "offensive" lets get rid of it > irrespective of the overall true value or consideration for the fact > that the author has used the "offensive" language ON PURPOSE. Personally, I find the ls command offensive. It could show files with "nasty words" in them. This is about more than my adult view; I know there are children forced by their parents to use OpenBSD, like little Tom who lives a block over. One option is to add a "content filter" directly inside the ls command, so that it will simply skip those files. Another variation would be to add the support to the kernel itself, this would also help other adirectory traversal code. It might face significant kernel growth. Of course we would have to find a way to manage the nasty word dictionary, and not expose it in the source tree in an open fashion. Blob, anyone? If we make this change in the kernel, we also need to be sensitive to the way that the NFS kernel code traverses directories. For now, I have chosen a simpler solution. (If this actually gets commited, we could call it the final solution). ok? Index: Makefile === RCS file: /cvs/src/bin/Makefile,v retrieving revision 1.10 diff -u -p -u -r1.10 Makefile --- Makefile18 May 2007 16:08:12 - 1.10 +++ Makefile22 Nov 2013 19:24:12 - @@ -1,7 +1,7 @@ # $OpenBSD: Makefile,v 1.10 2007/05/18 16:08:12 deraadt Exp $ SUBDIR=cat chio chmod cp csh date dd df domainname echo \ - ed expr hostname kill ksh ln ls md5 mkdir mt \ + ed expr hostname kill ksh ln md5 mkdir mt \ mv pax ps pwd rcp rm rmail rmdir sleep stty \ sync systrace test Index: ls/Makefile === RCS file: ls/Makefile diff -N ls/Makefile --- ls/Makefile 6 Aug 2003 19:09:09 - 1.7 +++ /dev/null 1 Jan 1970 00:00:00 - @@ -1,8 +0,0 @@ -# $OpenBSD: Makefile,v 1.7 2003/08/06 19:09:09 tedu Exp $ - -PROG= ls -SRCS= cmp.c ls.c main.c print.c util.c -DPADD= ${LIBUTIL} -LDADD= -lutil - -.include Index: ls/cmp.c === RCS file: ls/cmp.c diff -N ls/cmp.c --- ls/cmp.c27 Oct 2009 23:59:21 - 1.6 +++ /dev/null 1 Jan 1970 00:00:00 - @@ -1,167 +0,0 @@ -/* $OpenBSD: cmp.c,v 1.6 2009/10/27 23:59:21 deraadt Exp $ */ -/* $NetBSD: cmp.c,v 1.10 1996/07/08 10:32:01 mycroft Exp $ */ - -/* - * Copyright (c) 1989, 1993 - * The Regents of the University of California. All rights reserved. - * - * This code is derived from software contributed to Berkeley by - * Michael Fischbein. - * - * Redistribution and use in source and binary forms, with or without - * modification, are permitted provided that the following conditions - * are met: - * 1. Redistributions of source code must retain the above copyright - *notice, this list of conditions and the following disclaimer. - * 2. Redistributions in binary form must reproduce the above copyright - *notice, this list of conditions and the following disclaimer in the - *documentation and/or other materials provided with the distribution. - * 3. Neither the name of the University nor the names of its contributors - *may be used to endorse or promote products derived from this software - *without specific prior written permission. - * - * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND - * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE - * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE - * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE - * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL - * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS - * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) - * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT - * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY - * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF - * SUCH DAMAGE. - */ - -#include -#include - -#include -#include - -#include "ls.h" -#include "extern.h" - -int -namecmp(const FTSENT *a, const FTSENT *b) -{ - return (strcmp(a->fts_name, b->fts_name)); -} - -int -revnamecmp(const FTSENT *a, const FTSENT *b) -{ - return (strcmp(b->fts_name, a->fts_name)); -} - -int -modcmp(const FTSENT *a, con
Re: Patch to remove "adult" content from spamd(8) man page
On Fri, Nov 22, 2013 at 01:09:36PM -0600, J. Lewis Muir wrote: > I don't see it that way. Huckleberry Finn is a book, and I don't need > to read it unless I want to. The spamd(8) man page is a man page I need > to read in order to understand how to use spamd. Let me fix that for you: "The spamd(8) man page is a man page I don't need to read it unless I want to use spamd, a choice I am making of my own free will, and if I don't like it, I guess I could just go use some other software that doesn't get my panties in a bunch." Maybe you could try spam assassin instead? Unless, of course, you find the metaphor of "killing" spam offensive...
Re: Patch to remove "adult" content from spamd(8) man page
Hi J. Lewis, I am not a developer, but I've been lurking on this list for a very long time and on that basis can tell you that you've committed two cardinal sins as far as this mailing list is concerned: 1) you failed to do your homework -- had you done some research, in particular about the OpenBSD development philosophy, you would know that 2) OpenBSD is the ultimate volunteer effort -- the developers do it in their "free" time FOR PERSONAL FUN. Many of them have made it very clear that they would cease development if it stops being fun. Your original message (title and intro) goes to the heart of this issue. Its tone and attitude is no different than the efforts in the Bible Belt to ban Mark Twain's Huckleberry Fin from public libraries, i.e. since somebody finds some content to be "offensive" lets get rid of it irrespective of the overall true value or consideration for the fact that the author has used the "offensive" language ON PURPOSE. -Jacob. On 22 Nov 2013 at 12:06, J. Lewis Muir wrote: ... > > I'm a little puzzled over the whole resistance to the patch. If I > wrote a man page for some software I wrote, and if an example in it was > considered off-color by someone, and that someone submitted a patch to > me to change it slightly to no longer be off-color to them, and they > asked in a kind way, and the patch didn't hurt the clarity of the man > page in any way, I would likely accept the patch. How am I hurt by it? > I may not agree with the person, but why would I insist on keeping an > example that seems off-color to them? If it's somehow offensive to them > and can be changed in a small way not to be, then I would accept the > patch to change it. Everybody wins--no big deal. > > Lewis
Re: Patch to remove "adult" content from spamd(8) man page
On 11/22/13 12:34 PM, System Administrator wrote: > Hi J. Lewis, > > I am not a developer, but I've been lurking on this list for a very > long time and on that basis can tell you that you've committed two > cardinal sins as far as this mailing list is concerned: > > 1) you failed to do your homework -- had you done some research, in > particular about the OpenBSD development philosophy, you would know > that Hi, Jacob. It's unclear to me exactly what homework you think I failed to do. I am aware of and like lots of things that the OpenBSD project strives for. > 2) OpenBSD is the ultimate volunteer effort -- the developers do > it in their "free" time FOR PERSONAL FUN. Many of them have made > it very clear that they would cease development if it stops being > fun. Your original message (title and intro) goes to the heart of this > issue. Its tone and attitude is no different than the efforts in the > Bible Belt to ban Mark Twain's Huckleberry Fin from public libraries, > i.e. since somebody finds some content to be "offensive" lets get rid > of it irrespective of the overall true value or consideration for the > fact that the author has used the "offensive" language ON PURPOSE. I don't see it that way. Huckleberry Finn is a book, and I don't need to read it unless I want to. The spamd(8) man page is a man page I need to read in order to understand how to use spamd. And if the author of the spamd(8) man page did use the "offensive" language on purpose and thinks it's important to keep it that way, I would accept that. I'd disagree, but I'd accept that. But it seems the author doesn't think it's so important either way. So, I don't get the strong resistance. Thanks, Lewis
Re: Patch to remove "adult" content from spamd(8) man page
On Fri, Nov 22, 2013 at 1:06 PM, J. Lewis Muir wrote: > On 11/22/13 11:17 AM, Giancarlo Razzolini wrote: >> If it's offensive for you, compile your own spamd man page with >> the diff you so happily provided, and live the rest of your life >> happy. Remember to always take this pill again on 1st of May, and 1st >> of November, every year. > > Hi, Giancarlo. > > Well, no one wants to maintain a patch forever. I'd maintain it for a > while if there was a good chance it would get accepted at some point, > but if there's no chance, then I wouldn't bother. > > I'm a little puzzled over the whole resistance to the patch. If I > wrote a man page for some software I wrote, and if an example in it was > considered off-color by someone, and that someone submitted a patch to > me to change it slightly to no longer be off-color to them, and they > asked in a kind way, and the patch didn't hurt the clarity of the man > page in any way, I would likely accept the patch. How am I hurt by it? > I may not agree with the person, but why would I insist on keeping an > example that seems off-color to them? If it's somehow offensive to them > and can be changed in a small way not to be, then I would accept the > patch to change it. Everybody wins--no big deal. What you don't seem to understand is that the developers of OpenBSD, most importantly the project leader, don't see it your way, and it's THEIR project. You don't do the work, they do. They give it to us as a gift. Theo made this point earlier, but unfortunately it seems to need reiterating. This issue is subjective, a matter of taste, and they get to make the decisions on such matters. In my opinion, this discussion has gone way past the point of diminishing returns (I think it started there). You've been told "we're going to do it my way, because I'm the mommy", which most people would respond to by ceasing and desisting.
Re: Patch to remove "adult" content from spamd(8) man page
Lewis, If censorship is your thing, why don’t you start by censoring yourself. What you are asking for here is offensive. -Rick On Nov 22, 2013, at 12:26 PM, Paolo Aglialoro wrote: > Il 22/nov/2013 19:07 "J. Lewis Muir" ha scritto: >> >> On 11/22/13 11:17 AM, Giancarlo Razzolini wrote: >>> If it's offensive for you, compile your own spamd man page with >>> the diff you so happily provided, and live the rest of your life >>> happy. Remember to always take this pill again on 1st of May, and 1st >>> of November, every year. >> >> Hi, Giancarlo. >> >> Well, no one wants to maintain a patch forever. I'd maintain it for a >> while if there was a good chance it would get accepted at some point, >> but if there's no chance, then I wouldn't bother. >> >> I'm a little puzzled over the whole resistance to the patch. If I >> wrote a man page for some software I wrote, and if an example in it was >> considered off-color by someone, and that someone submitted a patch to >> me to change it slightly to no longer be off-color to them, and they >> asked in a kind way, and the patch didn't hurt the clarity of the man >> page in any way, I would likely accept the patch. How am I hurt by it? >> I may not agree with the person, but why would I insist on keeping an >> example that seems off-color to them? If it's somehow offensive to them >> and can be changed in a small way not to be, then I would accept the >> patch to change it. Everybody wins--no big deal. >> >> Lewis > > +1
Re: Patch to remove "adult" content from spamd(8) man page
On Fri, Nov 22, 2013 at 11:06 AM, J. Lewis Muir wrote: > Well, no one wants to maintain a patch forever. You lead a charmed life, my friend. Be well.
Re: Patch to remove "adult" content from spamd(8) man page
Il 22/nov/2013 19:07 "J. Lewis Muir" ha scritto: > > On 11/22/13 11:17 AM, Giancarlo Razzolini wrote: > > If it's offensive for you, compile your own spamd man page with > > the diff you so happily provided, and live the rest of your life > > happy. Remember to always take this pill again on 1st of May, and 1st > > of November, every year. > > Hi, Giancarlo. > > Well, no one wants to maintain a patch forever. I'd maintain it for a > while if there was a good chance it would get accepted at some point, > but if there's no chance, then I wouldn't bother. > > I'm a little puzzled over the whole resistance to the patch. If I > wrote a man page for some software I wrote, and if an example in it was > considered off-color by someone, and that someone submitted a patch to > me to change it slightly to no longer be off-color to them, and they > asked in a kind way, and the patch didn't hurt the clarity of the man > page in any way, I would likely accept the patch. How am I hurt by it? > I may not agree with the person, but why would I insist on keeping an > example that seems off-color to them? If it's somehow offensive to them > and can be changed in a small way not to be, then I would accept the > patch to change it. Everybody wins--no big deal. > > Lewis +1
Re: Patch to remove "adult" content from spamd(8) man page
On 11/22/13 11:17 AM, Giancarlo Razzolini wrote: > If it's offensive for you, compile your own spamd man page with > the diff you so happily provided, and live the rest of your life > happy. Remember to always take this pill again on 1st of May, and 1st > of November, every year. Hi, Giancarlo. Well, no one wants to maintain a patch forever. I'd maintain it for a while if there was a good chance it would get accepted at some point, but if there's no chance, then I wouldn't bother. I'm a little puzzled over the whole resistance to the patch. If I wrote a man page for some software I wrote, and if an example in it was considered off-color by someone, and that someone submitted a patch to me to change it slightly to no longer be off-color to them, and they asked in a kind way, and the patch didn't hurt the clarity of the man page in any way, I would likely accept the patch. How am I hurt by it? I may not agree with the person, but why would I insist on keeping an example that seems off-color to them? If it's somehow offensive to them and can be changed in a small way not to be, then I would accept the patch to change it. Everybody wins--no big deal. Lewis
Re: npppd l2tp/ipsec - openbsd client
On Fri, Nov 22, 2013 at 06:41:37PM +0200, Jeff Goettsch wrote: > What does /etc/ssh/ssh_config look like on the OpenBSD client? The file is the default that comes with OpenBSD. No change there... -- A: Because we read from top to bottom, left to right. Q: Why should I start my reply below the quoted text? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Patch to remove "adult" content from spamd(8) man page
Em 21-11-2013 18:44, J. Lewis Muir escreveu: > Hi, Shawn. I understand that, and I'm not trying to tell people how > they should talk on a mailing list. But to me documentation for a > project like OpenBSD is different. It's not individual people talking > however they like to talk. It's well-written text intended for users > to read to understand some part of the OpenBSD operating system. I > don't know of other OpenBSD user-facing documentation (i.e. website, > man pages, etc.) that has off-color (at least to me) content. Thanks, > Lewis If it's offensive for you, compile your own spamd man page with the diff you so happily provided, and live the rest of your life happy. Remember to always take this pill again on 1st of May, and 1st of November, every year. This thread at least put some laughs on some people's faces. -- Giancarlo Razzolini GPG: 4096R/77B981BC
Re: npppd l2tp/ipsec - openbsd client
What does /etc/ssh/ssh_config look like on the OpenBSD client? -- Jeff Goettsch Agricultural and Resource Economics University of California, Davis http://agecon.ucdavis.edu/ On Fri, November 22, 2013 6:52 am, haris wrote: > Hi, > > first of all, thanks @sthen for your answer (OP has no net access atm). > > We are to the point where the clients get ip (windows/linux/OpenBSD) and > traffic is passing through the server as expected. > > There is a very strange problem with ssh service though. While internet > traffic > is being routed as expected, when we try to ssh, we can't connect (from > OpenBSD > clients) to any server. > > [..snip..] > debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<3072<8192) sent > debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP > > and it just hangs there. > > Test time with windows, and with PuTTY, there is absolutely no problem. I > can > connect anywhere with absolutely no problem. At this point, I went with > the > crazy idea to try PuTTY on OpenBSD. And ssh with PuTTY works... We can't > get > our heads aroun this problem and why this is happening. > > ## pf.conf @ server ## > NIC="" > set skip on {lo0} > block # block stateless traffic > pass # establish keep-state > block in on ! lo0 proto tcp to port 6000:6010 > block in on vic0 > #vpn > extip="" > pass in quick inet proto tcp from any to $NIC port {} flags S/SA > keep > state > pass quick proto { esp, ah } from any to any > pass in quick on egress proto udp from any to any port {500, 4500} keep > state > pass quick on enc0 from any to any keep state (if-bound) > pass out quick on egress inet from 10.0.10.0/24 to any nat-to (egress:0) > pass out on vic0 > > > Does anyone has a solution to this problem? > > Thanks. > > -- > A: Because we read from top to bottom, left to right. > Q: Why should I start my reply below the quoted text? > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > > [demime 1.01d removed an attachment of type application/pgp-signature]
Re: npppd l2tp/ipsec - openbsd client
Hi, first of all, thanks @sthen for your answer (OP has no net access atm). We are to the point where the clients get ip (windows/linux/OpenBSD) and traffic is passing through the server as expected. There is a very strange problem with ssh service though. While internet traffic is being routed as expected, when we try to ssh, we can't connect (from OpenBSD clients) to any server. [..snip..] debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<3072<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP and it just hangs there. Test time with windows, and with PuTTY, there is absolutely no problem. I can connect anywhere with absolutely no problem. At this point, I went with the crazy idea to try PuTTY on OpenBSD. And ssh with PuTTY works... We can't get our heads aroun this problem and why this is happening. ## pf.conf @ server ## NIC="" set skip on {lo0} block # block stateless traffic pass# establish keep-state block in on ! lo0 proto tcp to port 6000:6010 block in on vic0 #vpn extip="" pass in quick inet proto tcp from any to $NIC port {} flags S/SA keep state pass quick proto { esp, ah } from any to any pass in quick on egress proto udp from any to any port {500, 4500} keep state pass quick on enc0 from any to any keep state (if-bound) pass out quick on egress inet from 10.0.10.0/24 to any nat-to (egress:0) pass out on vic0 Does anyone has a solution to this problem? Thanks. -- A: Because we read from top to bottom, left to right. Q: Why should I start my reply below the quoted text? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? [demime 1.01d removed an attachment of type application/pgp-signature]