match nat-to pass rule combination pflog output Clarification
Hi, I have these rules for the interface vr1 match out on vr1 inet from 172.16.0.0/12 to any nat-to (vr1) round-robin pass in log (all, to pflog1) quick on vr0 inet from tataips to any flags S/SA keep state label route-to 122.247.14...@vr1 pass out log (all, to pflog3) quick on vr1 all flags S/SA keep state label When I ssh from an IP 172.16.50.62 in the tataips table to a host 68.208.88.43 in the internet I get this corresponding traffic in pflog3 Aug 19 11:57:26.180191 rule 6.atelandtata.2/(match) pass out on vr1: 172.16.50.62.37105 68.208.88.43.22: S 2259539342:2259539342(0) win 5840 mss 1460,sackOK,timestamp 1855434[|tcp] (DF) Aug 19 11:57:26.439956 rule 6/(match) pass in on vr1: 68.208.88.43.22 172.16.50.62.37105: S 1444742373:1444742373(0) ack 2259539343 win 5792 mss 1460,sackOK,timestamp 3649103802[|tcp] (DF) Aug 19 11:57:26.440115 rule 6/(match) pass out on vr1: 122.247.145.232.64346 68.208.88.43.22: . ack 1444742374 win 92 nop,nop,timestamp 1855513 3649103802 (DF) Aug 19 11:57:26.705532 rule 6/(match) pass in on vr1: 68.208.88.43.22 172.16.50.62.37105: P 1:37(36) ack 1 win 46 nop,nop,timestamp 3649103869 1855513 (DF) Even though there is a match rule to nat In the first pflog3 out put I see the IP 172.16.50.62 But in the next line I see the Nated IP 122.247.145.232 Why is that private IP not natted in the first line? Thanks :-) --Siju
Re: [OT] securely sharing documents on OpenBSD?
2010/8/17, Jiri B. ji...@live.com: what's up with vpn and samba? who goes around, comes around... -- Martin Pelik an
Re: MeTA1 (was: MTA choice)
On Wed, 18 Aug 2010 11:43:49 -0700 Claus Assmann ca+openbsd_m...@esmtp.org wrote: On Wed, Aug 18, 2010, Gregory Edigarov wrote: Meta1, which is viewed by some as a sendmail made right is still in very deep pre-alpha state... what a pity. Despite being called pre-alpha MeTA1 runs without problems for years at various sites. It's in pre-alpha to make my life easier: I can make changes without offering backward compatibility. While I try to avoid that, it reduces my workload if those changes are deemed necessary (however, I provided scripts/instructions for upgrading each time this happened). Alternatively, I could just go through the release process to make MeTA1-1.0.0 available and then start MeTA1-2.0.PreAlpha0, but I'm not sure whether that's the right thing to do. Do quote the MeTA1 docs: PreAlpha: This means the software is not feature complete and hence might be missing some functionality that is considered important by different users. Additionally, there might be no compatibility in data structures stored on disk between different pre-alpha versions, e.g., when upgrading from PreAlpha16 to PreAlpha17 the main queue format may have changed without checks in the software for this. Hence old queues must be drained before upgrading. Moreover, the protocols used for communication between MeTA1 modules may have changed without providing backward compatibility, therefore modules from different releases must not be used together. Such incompatibilities are usually stated in the list of changes. Yeah, I got the point, thank you. -- With best regards, Gregory Edigarov
Re: Some apps kill/hang X when using scrotwm(1) as wm
On Tue, Aug 17, 2010 at 1:39 PM, Marco Peereboom sl...@peereboom.us wrote: I bet that is the controlled shut down where applications create windows and then destroy them before scrotwm can focus on them. B I fixed this in cvs and would appreciate a test report. B CVS instructions are on the www scrotwm page and it conveniently installs over the pkg. I checked out sources from cvs and then make ; sudo make install, but it's still same version as in packages/ports (0.9.25). Same version type is in scrotwm.c On Tue, Aug 17, 2010 at 09:30:57AM +0200, Tomas Bodzar wrote: Hi all, did someone saw similar problem in scrotwm(1)? Eg. when I start xeyes(1) on empty workspace from menu M-p it simply shut down X. If I start eg. xcalc(1) then everything is ok. Another problem is with xlock(1). When I want to lock my screen and start xlock(1) eg. this way 'xlock -mode atlantis' then my computer completely hangs and I must to turn it off with button on case. Last problem which I discovered is with warzone game. When I start it on empty workspace then it says that timing of monitor is not ok for this app and X is not working anymore and I must kill X from console. So someone here with similar behaviour? OpenBSD 4.8 (GENERIC.MP) #356: Mon Aug B 9 00:28:02 MDT 2010 B B dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error 11memory_size cpu0: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (GenuineIntel 686-class) 2.93 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3 ,CX16,xTPR,PDCM,SSE4.1,XSAVE real mem B = 3487125504 (3325MB) avail mem = 3420106752 (3261MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 02/13/10, BIOS32 rev. 0 @ 0xffea0, SMBIOS rev. 2.5 @ 0xf0450 (82 entries) bios0: vendor Dell Inc. version A03 date 02/13/2010 bios0: Dell Inc. OptiPlex 780 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET DMAR SLIC SSDT SSDT SSDT acpi0: wakeup devices VBTN(S4) PCI0(S5) PCI4(S5) PCI3(S5) PCI1(S5) PCI5(S5) PCI6(S5) MOU_(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) 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 265MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (GenuineIntel 686-class) 2.93 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3 ,CX16,xTPR,PDCM,SSE4.1,XSAVE ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 4 (PCI4) acpiprt1 at acpi0: bus 2 (PCI2) acpiprt2 at acpi0: bus 3 (PCI3) acpiprt3 at acpi0: bus 1 (PCI1) acpiprt4 at acpi0: bus -1 (PCI5) acpiprt5 at acpi0: bus -1 (PCI6) acpiprt6 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C1, PSS acpicpu1 at acpi0: C1, PSS acpibtn0 at acpi0: VBTN bios0: ROM list: 0xc/0x1 0xd/0x2000! 0xd2000/0x2800! 0xd4800/0x3800 cpu0: Enhanced SpeedStep 2926 MHz: speeds: 2933, 2667, 2400, 2133, 1867, 1600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel Q45 Host rev 0x03 ppb0 at pci0 dev 1 function 0 Intel Q45 PCIE rev 0x03: apic 8 int 16 (irq 11) pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Radeon HD 3470 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 8 int 16 (irq 11) drm0 at radeondrm0 em0 at pci0 dev 25 function 0 Intel ICH10 D BM LM rev 0x02: apic 8 int 21 (irq 10), address XX:XX:XX:XX:XX:XX uhci0 at pci0 dev 26 function 0 Intel 82801JD USB rev 0x02: apic 8 int 16 (irq 11) uhci1 at pci0 dev 26 function 1 Intel 82801JD USB rev 0x02: apic 8 int 17 (irq 9) uhci2 at pci0 dev 26 function 2 Intel 82801JD USB rev 0x02: apic 8 int 22 (irq 3) ehci0 at pci0 dev 26 function 7 Intel 82801JD USB rev 0x02: apic 8 int 22 (irq 3) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 82801JD HD Audio rev 0x02: apic 8 int 16 (irq 11) azalia0: codecs: Analog Devices AD1984A audio0 at azalia0 ppb1 at pci0 dev 28 function 0 Intel 82801JD PCIE rev 0x02: apic 8 int 16 (irq 11) pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 1 Intel 82801JD PCIE rev 0x02: apic 8 int 17 (irq 9) pci3 at ppb2 bus 3 uhci3 at pci0 dev 29 function 0 Intel 82801JD USB rev 0x02: apic 8 int 23 (irq 10) uhci4 at pci0 dev 29 function 1 Intel 82801JD USB rev 0x02: apic 8 int 17 (irq 9) uhci5 at pci0 dev 29 function 2 Intel 82801JD USB rev 0x02: apic 8 int 18 (irq 10) ehci1
Re: Smtpd use
Hi,
I tried other test:
I configured /etc/mailer.conf to use smtpctl and makemap.
my /etc/mail/virtual :
wes...@totoxx.org: wesley
r...@totoxx.org: root
After i done : makemap -t aliases -o /etc/mail/virtual.db /etc/mail/virtual
my /etc/mail/smtpd.conf :
listen on lo0
listen on sis0
map aliases { source db /etc/mail/aliases.db }
map virtual { source db /etc/mail/virtual.db }
accept for local deliver to mbox
accept from all for domain totoxx.org deliver to mbox
accept for all relay
I can send email for example to @gmail, but i comes with the name of my
hostname : wes...@puffymail.my.domain instead of wes...@totoxx.org. Why ?
I can't receive emails. Can you help me, please ?
On Wed, 18 Aug 2010 14:28:20 +0200, Gilles Chehade gil...@poolp.org
wrote:
yes it is possible to send mails with the one from 4.7 but it lacks
many bug fixes and you shouldn't use it
your smtpd.conf lacks a rule to allow local host to send outgoing
mails:
accept for all relay
Re: Smtpd use
On 8/19/2010 11:51 AM, open...@e-solutions.re wrote:
Hi,
I tried other test:
I configured /etc/mailer.conf to use smtpctl and makemap.
my /etc/mail/virtual :
wes...@totoxx.org: wesley
r...@totoxx.org: root
After i done : makemap -t aliases -o /etc/mail/virtual.db /etc/mail/virtual
my /etc/mail/smtpd.conf :
listen on lo0
listen on sis0
map aliases { source db /etc/mail/aliases.db }
map virtual { source db /etc/mail/virtual.db }
accept for local deliver to mbox
accept from all for domain totoxx.org deliver to mbox
accept for all relay
I can send email for example to @gmail, but i comes with the name of my
hostname : wes...@puffymail.my.domain instead of wes...@totoxx.org. Why ?
I can't receive emails. Can you help me, please ?
smtpd does not support masquerading, you need to use a MUA that lets you
provide the sender address. if you want mailer-daemons to come from
totoxx.org you need to set your machine hostname to totoxx.org
i don't know if jacek has plans to implement masquerading in a near
future, you need to ask him
gilles
Re: Some apps kill/hang X when using scrotwm(1) as wm
no it isn't. the external version isn't the same as the cvs version. obviously we don't change the external version after every commit. use m-s-v for the real version. On Thu, Aug 19, 2010 at 10:32:38AM +0200, Tomas Bodzar wrote: On Tue, Aug 17, 2010 at 1:39 PM, Marco Peereboom sl...@peereboom.us wrote: I bet that is the controlled shut down where applications create windows and then destroy them before scrotwm can focus on them. B I fixed this in cvs and would appreciate a test report. B CVS instructions are on the www scrotwm page and it conveniently installs over the pkg. I checked out sources from cvs and then make ; sudo make install, but it's still same version as in packages/ports (0.9.25). Same version type is in scrotwm.c On Tue, Aug 17, 2010 at 09:30:57AM +0200, Tomas Bodzar wrote: Hi all, did someone saw similar problem in scrotwm(1)? Eg. when I start xeyes(1) on empty workspace from menu M-p it simply shut down X. If I start eg. xcalc(1) then everything is ok. Another problem is with xlock(1). When I want to lock my screen and start xlock(1) eg. this way 'xlock -mode atlantis' then my computer completely hangs and I must to turn it off with button on case. Last problem which I discovered is with warzone game. When I start it on empty workspace then it says that timing of monitor is not ok for this app and X is not working anymore and I must kill X from console. So someone here with similar behaviour? OpenBSD 4.8 (GENERIC.MP) #356: Mon Aug B 9 00:28:02 MDT 2010 B B dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error 11memory_size cpu0: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (GenuineIntel 686-class) 2.93 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3 ,CX16,xTPR,PDCM,SSE4.1,XSAVE real mem B = 3487125504 (3325MB) avail mem = 3420106752 (3261MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 02/13/10, BIOS32 rev. 0 @ 0xffea0, SMBIOS rev. 2.5 @ 0xf0450 (82 entries) bios0: vendor Dell Inc. version A03 date 02/13/2010 bios0: Dell Inc. OptiPlex 780 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET DMAR SLIC SSDT SSDT SSDT acpi0: wakeup devices VBTN(S4) PCI0(S5) PCI4(S5) PCI3(S5) PCI1(S5) PCI5(S5) PCI6(S5) MOU_(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) 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 265MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (GenuineIntel 686-class) 2.93 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3 ,CX16,xTPR,PDCM,SSE4.1,XSAVE ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 4 (PCI4) acpiprt1 at acpi0: bus 2 (PCI2) acpiprt2 at acpi0: bus 3 (PCI3) acpiprt3 at acpi0: bus 1 (PCI1) acpiprt4 at acpi0: bus -1 (PCI5) acpiprt5 at acpi0: bus -1 (PCI6) acpiprt6 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C1, PSS acpicpu1 at acpi0: C1, PSS acpibtn0 at acpi0: VBTN bios0: ROM list: 0xc/0x1 0xd/0x2000! 0xd2000/0x2800! 0xd4800/0x3800 cpu0: Enhanced SpeedStep 2926 MHz: speeds: 2933, 2667, 2400, 2133, 1867, 1600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel Q45 Host rev 0x03 ppb0 at pci0 dev 1 function 0 Intel Q45 PCIE rev 0x03: apic 8 int 16 (irq 11) pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Radeon HD 3470 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 8 int 16 (irq 11) drm0 at radeondrm0 em0 at pci0 dev 25 function 0 Intel ICH10 D BM LM rev 0x02: apic 8 int 21 (irq 10), address XX:XX:XX:XX:XX:XX uhci0 at pci0 dev 26 function 0 Intel 82801JD USB rev 0x02: apic 8 int 16 (irq 11) uhci1 at pci0 dev 26 function 1 Intel 82801JD USB rev 0x02: apic 8 int 17 (irq 9) uhci2 at pci0 dev 26 function 2 Intel 82801JD USB rev 0x02: apic 8 int 22 (irq 3) ehci0 at pci0 dev 26 function 7 Intel 82801JD USB rev 0x02: apic 8 int 22 (irq 3) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 82801JD HD Audio rev 0x02: apic 8 int 16 (irq 11) azalia0: codecs: Analog Devices AD1984A audio0 at azalia0 ppb1 at pci0 dev 28 function 0 Intel 82801JD PCIE rev 0x02: apic 8 int 16 (irq 11) pci2 at ppb1 bus 2 ppb2 at pci0 dev
Re: undeadly article
On 18 August 2010 23:57, Jacob Meuser jake...@sdf.lonestar.org wrote: On Wed, Aug 18, 2010 at 04:28:57PM +0300, Mihai Popescu B.S. wrote: Hello, My post was not intended as a direct hit for the article. I told my opinion to misc@ because undeadly ask for subscription, no more anonymous coward post. Am I wrong ? I target airport behaviour with my comment. I use the airport for 6 flight until now, no problem at all with security teams. I was quick and polite in answers and the time with them was short. Most of them have the nose to see what they are dealing with. bullshit. sorry, but that is not true. I regularly get picked on by authority, but it's alwasy just been a pointless hassle. I'll never forget the time a cop stopped me in my own neighborhood, in the rain, for walking against a signal, when his car was the only moving vehicle within a half mile. the best part was when he dropped his papers in a puddle. Flying from Melbourne to Sydney, at the Qantas baggage scanner I was very sternly challenged as to what exactly an item was on my keyring (a rubber Corsair Flash Voyager GT 16GB thumbdrive). Before I could answer, she said is this an MP3 player!?, as if it was a crime. No, it's a thumb drive storage device, oh okay then. Seriously. I'd hate it to have been one of the new Corsair Padlock2 drives, complete with number pads and blinken lights that blinken with key presses without the need for power from a computer. I'm sure it would have been taken for a wireless detonation device. Then when I carry on lots of explosives (spare Li-ion laptop batteries on account that we can't courier them any more with laptops between offices!), nobody blinks an eye! Even though I now know that I had too many of them. Shane
Re: Some apps kill/hang X when using scrotwm(1) as wm
On Thu, Aug 19, 2010 at 1:53 PM, Marco Peereboom sl...@peereboom.us wrote: no it isn't. B the external version isn't the same as the cvs version. obviously we don't change the external version after every commit. use m-s-v for the real version. Welcome to scrotwm V0.9.25 cvs tag: $scrotwm: scrotwm.c,v 1.300 2010/08/11 03:15:40 marco Exp $ but problem is still same. On Thu, Aug 19, 2010 at 10:32:38AM +0200, Tomas Bodzar wrote: On Tue, Aug 17, 2010 at 1:39 PM, Marco Peereboom sl...@peereboom.us wrote: I bet that is the controlled shut down where applications create windows and then destroy them before scrotwm can focus on them. B I fixed this in cvs and would appreciate a test report. B CVS instructions are on the www scrotwm page and it conveniently installs over the pkg. I checked out sources from cvs and then make ; sudo make install, but it's still same version as in packages/ports (0.9.25). Same version type is in scrotwm.c On Tue, Aug 17, 2010 at 09:30:57AM +0200, Tomas Bodzar wrote: Hi all, did someone saw similar problem in scrotwm(1)? Eg. when I start xeyes(1) on empty workspace from menu M-p it simply shut down X. If I start eg. xcalc(1) then everything is ok. Another problem is with xlock(1). When I want to lock my screen and start xlock(1) eg. this way 'xlock -mode atlantis' then my computer completely hangs and I must to turn it off with button on case. Last problem which I discovered is with warzone game. When I start it on empty workspace then it says that timing of monitor is not ok for this app and X is not working anymore and I must kill X from console. So someone here with similar behaviour? OpenBSD 4.8 (GENERIC.MP) #356: Mon Aug B 9 00:28:02 MDT 2010 B B B B dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error 11memory_size cpu0: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (GenuineIntel 686-class) 2.93 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3 ,CX16,xTPR,PDCM,SSE4.1,XSAVE real mem B = 3487125504 (3325MB) avail mem = 3420106752 (3261MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 02/13/10, BIOS32 rev. 0 @ 0xffea0, SMBIOS rev. 2.5 @ 0xf0450 (82 entries) bios0: vendor Dell Inc. version A03 date 02/13/2010 bios0: Dell Inc. OptiPlex 780 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET DMAR SLIC SSDT SSDT SSDT acpi0: wakeup devices VBTN(S4) PCI0(S5) PCI4(S5) PCI3(S5) PCI1(S5) PCI5(S5) PCI6(S5) MOU_(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) 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 265MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (GenuineIntel 686-class) 2.93 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3 ,CX16,xTPR,PDCM,SSE4.1,XSAVE ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 4 (PCI4) acpiprt1 at acpi0: bus 2 (PCI2) acpiprt2 at acpi0: bus 3 (PCI3) acpiprt3 at acpi0: bus 1 (PCI1) acpiprt4 at acpi0: bus -1 (PCI5) acpiprt5 at acpi0: bus -1 (PCI6) acpiprt6 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C1, PSS acpicpu1 at acpi0: C1, PSS acpibtn0 at acpi0: VBTN bios0: ROM list: 0xc/0x1 0xd/0x2000! 0xd2000/0x2800! 0xd4800/0x3800 cpu0: Enhanced SpeedStep 2926 MHz: speeds: 2933, 2667, 2400, 2133, 1867, 1600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel Q45 Host rev 0x03 ppb0 at pci0 dev 1 function 0 Intel Q45 PCIE rev 0x03: apic 8 int 16 (irq 11) pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Radeon HD 3470 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 8 int 16 (irq 11) drm0 at radeondrm0 em0 at pci0 dev 25 function 0 Intel ICH10 D BM LM rev 0x02: apic 8 int 21 (irq 10), address XX:XX:XX:XX:XX:XX uhci0 at pci0 dev 26 function 0 Intel 82801JD USB rev 0x02: apic 8 int 16 (irq 11) uhci1 at pci0 dev 26 function 1 Intel 82801JD USB rev 0x02: apic 8 int 17 (irq 9) uhci2 at pci0 dev 26 function 2 Intel 82801JD USB rev 0x02: apic 8 int 22 (irq 3) ehci0 at pci0 dev 26 function 7 Intel 82801JD USB rev 0x02: apic 8 int 22 (irq 3) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 82801JD HD Audio rev 0x02: apic 8
Stunning new products from Cast in Style - Varity is the spice of life
Please click here if the e-mail below is not displayed correctly Cast in Style www.castinstyle.co.uk Beautiful Cast Iron Home and Garden Ware Clothes Airers Pot Racks Bells Bolts, Latches Hinges Boot Scrapers Pulls Brackets Cabinet Knobs Clocks Cookware Door Knobs Handles Door Furniture Door Knockers Door Mats Door Stops Drawer Handles Pulls Electrical Switches Fires Fire baskets Garden Gate Furniture Hat Coat Hooks Homeware Kitchenware Letterboxes Rim Locks Latches Signs Sun Dials Trivets Wall Art Window Furniture Wine Racks Have you seen Cast in Style Recently? 2500 New Products Added this Year Superior quality Architectural Homeware Remove me from this newsletter
Re: undeadly article
Hello, Here is my last post to this thread. No time to argue out of the subject. My point is it is safer not to hurt yourself, in this case is safer to avoid unnecessary conflicts and treatments on the airport. Why ? The worst thing it can happen in this situation is well, you are held there and you can't reach anymore the hackathon meeting. So nice. I was drive to open this thread by the memory of another case with someone from open source. My intention was not to judge people ( J.C. vs. R) but behaviours. So J.C. of course you are others are free to do and write whatever you like, but I think your scenario was set up from home. I know what sarcasm is, please avoid using wikipedia as a reference, it looks not so nice. Here are a few translations of my own for local humour, here in Eastern Europe ( no hints included : ) You do not put a flea on a white paper. You do not wear a towel on your head if you don't have a headache. No hate involved from my side.
Pragmatics of Following current
Hi Guys, I have been meaning to follow current for a couple of weeks now. I read the Building Sources page and it seems like I should follow the process of: cvs up src xenocara ports - compile - install, where install includes merging of configuration files. Moreover, I should also keep an eye on the Following -current webpage for any change I should make. This looks like a lot of work every-time you run cvs up (mainly the compilation of ports and merging of conf files). I was wondering how do you usually work on current and if you all follow this process through-fully. If not, what kind of tricks do you use to make the process easier. For now, I am using snapshots with binary packages. Thanks in advance, Luis.
Re: Pragmatics of Following current
On Thu, Aug 19, 2010 at 12:02:11PM -0400, Luis Useche wrote: Hi Guys, I have been meaning to follow current for a couple of weeks now. I read the Building Sources page and it seems like I should follow the process of: cvs up src xenocara ports - compile - install, where install includes merging of configuration files. Moreover, I should also keep an eye on the Following -current webpage for any change I should make. This looks like a lot of work every-time you run cvs up (mainly the compilation of ports and merging of conf files). I was wondering how do you usually work on current and if you all follow this process through-fully. If not, what kind of tricks do you use to make the process easier. For now, I am using snapshots with binary packages. Quite honestly, that's more useful, as snapshots a) are generally close enough to -current that you're more or less running -current anyway; and b) sometimes contain diffs which haven't made -current but need testing, which means that you're actually running a more -current -current at times Thanks in advance, You're welcome...from *the future* - Bert Luis.
Re: Pragmatics of Following current
Quoting Luis Useche use...@gmail.com: Hi Guys, I have been meaning to follow current for a couple of weeks now. I read the Building Sources page and it seems like I should follow the process of: cvs up src xenocara ports - compile - install, where install includes merging of configuration files. Moreover, I should also keep an eye on the Following -current webpage for any change I should make. This looks like a lot of work every-time you run cvs up (mainly the compilation of ports and merging of conf files). I was wondering how do you usually work on current and if you all follow this process through-fully. If not, what kind of tricks do you use to make the process easier. For now, I am using snapshots with binary packages. Thanks in advance, Luis. It really is't that hard to do. If you follow the examples for all this in the release man page, it is straightforward, and when you crash into something odd, it's at least a 90% chance that you botched something, as opposed to the tree being borked. Subscribing to the src changes list is really very very usefu. This lets you see the changes to the system at the atomic level, and in time you'll recognize the stuff that needs only a kernel recompile, or even just a part of userland to be rebuilt. At first though, rebuilding eveything is the right way to go. It really isn't a lot of work. If you run script(1) when doing a cvsup you can go back to that and see whats new, which might be a big help in determining if you want to rebuild stuff or not. Depening on whats being changed the most in a given week, you might not bother rebuilding things for a while. Other times, a single change to a library where the major number is bumped you'd want to rebuild everything. A certain amount of experimentation on a spare machine is a great way to blow things up and then let you figure out how to repair stuff in a non pressure-cooker environment. By taking the time to learn and messing things up you'll be in much better shape for real systems that you depend on. A door-stop 400MHz Dell with 256M is a great system for doing with with if you're on a budget. Building your own packages is harder, in that you can screw up in lots of ways. You also want as fast a machine as you can get for that. My 2.1GHz package machine takes about 60 hours for a run. But before you do that learn about OpenBSD proper first. --STeve Andre'
Re: Smtpd use
Hi, I juste tried it, and it works very fine !! I added SMTPS without any difficulty ! Very good job !! On Thu, 19 Aug 2010 12:13:08 +0200, Gilles Chehade gil...@poolp.org wrote: smtpd does not support masquerading, you need to use a MUA that lets you provide the sender address. if you want mailer-daemons to come from totoxx.org you need to set your machine hostname to totoxx.org i don't know if jacek has plans to implement masquerading in a near future, you need to ask him gilles
Economize até 70% em suas Ligações!
Economize ati 70% em suas ligagues! === Ola misc@openbsd.org reservamos uma oferta especial para vocj! Flex Premier Economize em suas ligagues Locais, DDD e DDI O plano flex i desiginado a qualquer tipo de empresa ou residencia, e conta com tarifas super economicas para ligagues Local, DDD e DDI Tarifas: Local: Fixo R$ 0,12 Msvel R$ 0,65 LDNFIxo R$ 0,16 Msvel R$ 0,71 Longa Distancia Internacional..Sob consulta. Flex Premier Business = Flex Business ja i voltado para uso comercial, onde possui franquia de minutos e tarifas mais economicas sendo possivel fazer ligagues Locais, DDD e DDI com tarifa fixa, independente de dia e horario. Tarifas: LocalFixo R$ 0,07 Movel R$ 0,59 LDN..Fixo R$ 0,10 Msvel R$ 0,65 Longa Distancia Internacional..Sob consulta. Vale lembrar que sua empresa podera efetuar uma avaliagco gratuita do servigo. Para maiores informagues entre em contato conosco Atenciosamente, Ismael M. Soares Gerente de Vendas EMAIL ism...@premiervoice.net.br CE +55 18 8811-0902 PTT Vendas [demime 1.01d removed an attachment of type image/png which had a name of 1.png] [demime 1.01d removed an attachment of type image/jpeg which had a name of 2.jpg] [demime 1.01d removed an attachment of type image/png which had a name of 3.png] [demime 1.01d removed an attachment of type image/png which had a name of 4.png] [demime 1.01d removed an attachment of type image/png which had a name of 5.png]
ANDAMIOS TRIBUNAS VALLAS GRADAS ESCALERAS - misc
TRIBUNAS METALICAS GRADAS MOVILES ESCENARIOS -PASARELAS VALLAS METALICAS ANDAMIOS TUBULARES ELEVADOR DE DURLOCK MONTACARGAS-ELEVADORES ESCALERAS MOVILES HERRAMIENTAS PARA LA CONSTRUCCION CABALLETES EXTENSIBLES Visite www.nuevosairesnet.com.ar E- mails infonuevosai...@coopenetcolon.com.ar nuevosairesandam...@hotmail.com
can donate a eeepc 701 battery
hi there, i have an extra battery for the eeepc701, the original one that came with it. contact me offlist if interested. developers go to the top of the list :] -f -- dos tip: don't use dos.
Handbook for Managing Teleworkers - A guide for managers teleworkers - Ref: 989582
To: misc@openbsd.org ***A five-step management process for managing teleworkers Now available... Handbook for Managing Teleworkers A Five-Step Management Process for Managing Teleworkers 212 Pages ISBN: 978-0-9844038-2-0 by Don Philpott, Senior Editor, Government Training Inc. Publications (TM) Sandra Gurvis Writer, instructor and speaker on modern telework issues and solutions (For additional details and to order through our secure server, go to www.GovernmentTrainingInc.com) NEW ! Special note: Your order will include a password access to a web-based copy of the book available for reading (not downloading) on line. Quote: This is perfect. Our agency has just made a major commitment to telework - but had not management plan to support this decision. Your five-step process is excellent. Gives us a management framework and a process that can be easily followed by manager and teleworker alike. Quote: Thanks for your book. We found the templates and Five-Step process to be of highest value. Sandra really understands the opportunties and pitfalls. Quote: We have teleworkers scattered all through our organization. None of the managers believed it was working. It wasn't until we implemented your plan that we began to see the problems and areas where teleworking was working. Quote: Your use of highlighted text made reading the book easy and fun. ORC:n41452:misc@openbsd.org:0::ORC About the Author: Sandra Gurvis Sandra Gurvis (www.sgurvis.com), serves as professional development instructor for Government Training Inc (GTI), and is the author of fourteen books and hundreds of magazine articles. Her titles include MANAGING THE TELECOMMUTING EMPLOYEE with Michael Amigoni (Adams , 2009), MANAGEMENT BASICS, 2nd ed ( Adams , 2007), and CAREER FOR CONFORMISTS (Marlowe, 2001), which was a selection of the Quality Paperback Book Club. Her books have been featured on Good Morning America, CBS Up to the Minute, ABC World News Tonight, in USA Today and in other newspapers and on television and radio stations across the country; and have been excerpted in magazines. Sandra has traveled throughout the US , lecturing and providing information on telework and telecommuting, as well as other issues relating to management and self-employment. She lives in Columbus , Ohio . About the Book: Telework Book Review: Handbook for Managing Teleworkers If you are a teleworker, a teleworker manager, a government agency implementing telework or a major company considering it, this is a must read book While teleworking has started to gain traction, especially at federal level, there are still many myths surrounding it as well as concerns from senior managers who fear loss of control over staff not working in the office. This book is an A-Z guide aimed at managers tasked with introducing teleworking or overseeing teleworkers and ensuring that everything runs smoothly. The rules for managing teleworking are the same whether you are a federal or state employee or work for a private company or organization. The book is also very useful to people who are thinking of teleworking or trying to persuade their employers to introduce it. The guide starts with an overview of what teleworking is, why it was introduced and what the current situation is. It then takes you through an easy to understand Five-Step Process to determine whether teleworking is right for your organization and, if so, how best it can be implemented. Step One gives you the tools you need to decide whether your organization needs teleworking. It looks at the jobs suitable for teleworking, the benefits and the technology needed to make it happen. Step Two focuses on putting together a teleworking team. This includes successful strategies for telework programs, creating guidelines for managers and employees, writing telework agreements and selecting the right people. There are also important sections on safety, security and the legal rights of teleworkers. Step Three is all about organization getting together a winning game plan. In addition, there is information about training and setting up a continuity-of-operations plan to maintain essential functions in the event of a major disaster. Step Four covers implementation how you make it all happen. In addition, there is guidance on insurances, taxes and health care options and how they impact teleworkers. Step Five discusses maintenance now that you have set up your teleworking program what do you have to do to ensure it runs smoothly. The authors both teleworkers - have drawn heavily on authoritative materials published by a wide range of federal agencies and organizations to provide case studies and best practices. The wealth of practical information is organized into an easy to follow, high value 5-Step process that provides an invaluable resource to telework managers and teleworkers alike. Each step in the process is supported by
