Nabble - OpenBSD

Re: Познание PF

2009-11-23T19:51:57Z

mitrofanzzz пишет:

> По сути 13 строка это "scrub in on $ext_if all fragment reassemble",
> скопипастил прямо из манов.

В 4.6 изменили scrub: "Removed pf(4) scrub rules, and only do one kind
of packet reassembly. Rulesets with scrub rules need to be modified
because of this."

В манах по 4.6 scrub уже через match:

"For example:
match in all scrub (no-df max-mss 1440)"

From forum: openbsd - Russian

OpenBSD and my portable mp3 player

2009-11-23T19:28:07Z

I am warning you ahead that some of this may be braindead simple or
trivial for some of you but
I am still sending this because many of you will benefit by this mail.

Here is what I did with my portable Sandisk mp3 player.

I have a strange problem.

I am a devout Hindu and I want to listen to Vedic chants every
morning. But now I live in a place far away
from my office.

So I wanted a way to listen to these slokas/mantras from my home.

Then I remembered that I had an old Sandisk pocket size mp3 player
lying idle with me.

I connected it to my USB port and OpenBSD recognized as:

umass0 at uhub0 port 2 configuration 1 interface 0 "SanDisk SDMX1 MP3
Player" rev 2.00/1.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <SanDisk, SDMX1 MP3 Player, 1.13> SCSI0
0/direct removable
sd0: 486MB, 512 bytes/sec, 995328 sec total

No, this was not the first time.

There was something wrong with my hub. And I had to try it few times.

Anyway once I got this far,

I created an fdisk partition.

# fdisk -e sd0
I created a FAT32 file system on it(ID 06).

Then disklabel would still give a weird output. I expected to see sd0i
as is the case with
the 0B file system ID.

First time I got it wrong. The player did not recognize my file system.

Then I got it right with this command.

# newfs_msdos /dev/sd0c

Now disklabel behaves itself. ;)

Mount it with

# mount /dev/sd0i /mnt

Copy all the mp3 files.

I converted to mp3 from flash videos using

$ ffmpeg -i foo.flv foo.mp3

Copy files to mp3 player.

# cp *mp3 /mnt
# cd
# umount /mnt

Disconnect and enjoy. ;)

When I ran into the format issue wikipedia helped and told me what
file system format I am supposed to use in mp3 players.

This morning when I listened to my Vedic chants I thought:

"Can't I just concatenate the three mantras rudram, chamakam and
purushasuktam mp3 files?"

That is what I did just now.

$ mp3cat rudram.mp3 chamakam.mp3 purushasuktam.mp3 --output=prayer.mp3

Now I can pray during my long town bus journey from home to office in
Chennai. ;)

Hopefully these tips will help some of you.

Thanks to OpenBSD and its great developers!

Ever yours,
-Girish

--
Gayatri Hitech
web: http://gayatri-hitech.com

SpamCheetah Spam filter:
http://spam-cheetah.com

From forum: openbsd user - misc

setpci problem writing

2009-11-23T18:55:25Z

Can't sort out what the problem is here.
setpci reads fine but is unable to write.

/dev/pci is a link to /dev/pci0

pci0 is rw for root

setpci -vG -s 2:04.0 3c.b

Trying method 8......using /dev/pci...OK
Decided to use obsd-device
Scanning bus 00 for devices...
Scanning bus 02 for devices...
Scanning bus 00 for devices...
pcilib: Bus 00 seen twice (firmware bug). Ignored.
Scanning bus 00 for devices...
pcilib: Bus 00 seen twice (firmware bug). Ignored.
Scanning bus 01 for devices...
0000:02:04.0 @3c = 0b

setpci -vG -s 2:04.0 3c.b=0xf

Trying method 8......using /dev/pci...OK
Decided to use obsd-device
Scanning bus 00 for devices...
Scanning bus 02 for devices...
Scanning bus 00 for devices...
pcilib: Bus 00 seen twice (firmware bug). Ignored.
Scanning bus 00 for devices...
pcilib: Bus 00 seen twice (firmware bug). Ignored.
Scanning bus 01 for devices...
setpci: obsd_write: ioctl(PCIOCWRITE) failed
0000:02:04.0 @3c 0f

setpci -vG -s 2:04.0 3c.b
Trying method 8......using /dev/pci...OK
Decided to use obsd-device
Scanning bus 00 for devices...
Scanning bus 02 for devices...
Scanning bus 00 for devices...
pcilib: Bus 00 seen twice (firmware bug). Ignored.
Scanning bus 00 for devices...
pcilib: Bus 00 seen twice (firmware bug). Ignored.
Scanning bus 01 for devices...
0000:02:04.0 @3c = 0b

From forum: openbsd user - misc

Re: TOSHIBA PORTEGE R600

2009-11-23T18:49:19Z

On Mon, Nov 23, 2009 at 9:42 PM, Nick Guenther <kousue@...> wrote:
> On Mon, Nov 23, 2009 at 6:51 PM, <peter.ericson@...> wrote:
>> Hi misc@I'm thinking of buying an R600 to run current on.Has anyone had
any
>> experience with these machines?From the spec sheet: Part Number
>> PPR61A-02200R <ES5.0> CPU
>> Intel® CoreTM2 Duo Processor ULV Su9400
>> (1.4GHz, 800mHz FSB, 3MB l2 cache)
>> mobile Intel® GS45 Express Chipset
>> Video/Graphics Intel® Graphics media Accelerator GS45
>> Wireless Communications Intel® 802.11 a/g/n, BluetoothTM V2.1 + EDR,
>> Built-in 3G HSPA BIOS ACPI, PnP, VESA, DPmS,
DDC,
>> Sm BIOS, PCI, BIOS support Audio
Intel®

>> High Definition Audio Sound Wired
>> Communications Intel® 1GBit Tx Ethernet + Active management
>> Technology (AmT) 4.0 Thanks in advance,Peter Ericson
>>
>>
>
>
> Funny you should ask. I have an R500 and it works fine, excepting the
> lack of ACPI support of course. The Fn-Mute key combo even works right
> away, no configuring needed (magic!). It's super flimsy though, I've
> had it's optical drive repaired twice and the DC in has come loose and
> I'm terrified of bumping the screen (it's 4mm thick). It's not the
> worst laptop I've heard of as far as heat goes but it definitely gets
> up there--I can't really do CPU intensive things on it since it'll get
> up to 95degC and hover there really quick. Wifi is wpi(4) and except
> for one firmware glitch once, and sometimes things lagging out (seems
> to be correlated with heat) until I reset the card, I've never had any
> problems. I'm not sure how different the R600 is, though.
>
> This BIOS doesn't seem to like (legacy) GRUB: it hangs on the logo
> screen unless I warm-boot or mash the F keys (very odd) but when I was
> just using the OpenBSD MBR it never did that.
>
> dmesg from 4.6-release:
> OpenBSD 4.6 (GENERIC.MP) #89: Thu Jul 9 21:32:39 MDT 2009
> deraadt@...:/usr/src/sys/arch/i386/compile/GENERIC.MP
> cpu0: Intel(R) Core(TM)2 CPU U7600 @ 1.20GHz ("GenuineIntel" 686-class) 1.20

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,CX16,
xTPR

> real mem = 1064202240 (1014MB)
> avail mem = 1020198912 (972MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 10/30/07, BIOS32 rev. 0 @
> 0xfcb25, SMBIOS rev. 2.4 @ 0xec000 (40 entries)
> bios0: vendor TOSHIBA version "Version 1.50" date 10/30/2007
> bios0: TOSHIBA PORTEGE R500
> acpi0 at bios0: rev 0
> acpi0: tables DSDT FACP SSDT BOOT APIC MCFG HPET TCPA SLIC SSDT SSDT
> acpi0: wakeup devices USB1(S3) USB3(S3) USB4(S3) EHCI(S3) GLAN(S4)
> WLAN(S4) LID_(S4) PWRB(S4) HS87(S4) HS86(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: apic clock running at 133MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 CPU U7600 @ 1.20GHz ("GenuineIntel" 686-class) 1.20

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,CX16,
xTPR

> ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 20, 24 pins
> ioapic0: misconfigured as apic 0, remapped to apid 1
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 3 (PCIB)
> acpiprt2 at acpi0: bus 1 (PEX1)
> acpiprt3 at acpi0: bus 2 (MPEX)
> acpicpu0 at acpi0: C3, C2, C1, PSS
> acpicpu1 at acpi0: C3, C2, C1, PSS
> acpipwrres0 at acpi0: PDOC
> acpitz0 at acpi0: critical temperature 102 degC
> acpibtn0 at acpi0: LID_
> acpibat0 at acpi0: BAT1 model "G71C00086210" serial 0000000796 type
> Li-ION oem "0"
> acpibtn1 at acpi0: PWRB
> acpiac0 at acpi0: AC unit offline
> acpidock0 at acpi0: DOCK not docked (0)
> acpivideo0 at acpi0: VGA_
> acpivout0 at acpivideo0: LCD_
> acpivout1 at acpivideo0: CRT_
> acpivout2 at acpivideo0: DVI_
> bios0: ROM list: 0xc0000/0x10000 0xe0000/0x10000!
> cpu0: Enhanced SpeedStep 1198 MHz: speeds: 1200, 800 MHz
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
> vga1 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> intagp0 at vga1
> agp0 at intagp0: aperture at 0xe0000000, size 0x10000000
> inteldrm0 at vga1: apic 1 int 16 (irq 10)
> drm0 at inteldrm0
> "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:
> apic 1 int 22 (irq 255)
> azalia0: codecs: Realtek ALC262
> audio0 at azalia0
> ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02
> pci1 at ppb0 bus 1
> em0 at pci1 dev 0 function 0 "Intel PRO/1000MT (82573L)" rev 0x00:
> apic 1 int 16 (irq 10), address 00:15:b7:43:a0:f2
> ppb1 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02
> pci2 at ppb1 bus 2
> wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02:
> apic 1 int 18 (irq 11), MoW1, address 00:1c:bf:78:7f:04
> uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1
> int 23 (irq 11)
> uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1
> int 19 (irq 11)
> uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1
> int 18 (irq 11)
> uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1
> int 16 (irq 10)
> ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1
> int 23 (irq 11)
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> ppb2 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
> pci3 at ppb2 bus 3
> cbb0 at pci3 dev 11 function 0 "TI PCIXX12 CardBus" rev 0x00: apic 1
> int 21 (irq 255)
> "TI PCIXX12 FireWire" rev 0x00 at pci3 dev 11 function 1 not configured
> sdhc0 at pci3 dev 11 function 3 "TI PCIXX12 Secure Data" rev 0x00:
> apic 1 int 23 (irq 255)
> sdmmc0 at sdhc0
> cardslot0 at cbb0 slot 0 flags 0
> cardbus0 at cardslot0: bus 4 device 0 cacheline 0x8, lattimer 0x20
> pcmcia0 at cardslot0
> ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02: PM

disabled
> ahci0 at pci0 dev 31 function 2 "Intel 82801GBM AHCI" rev 0x02: apic 1
> int 19 (irq 11), AHCI 1.1
> scsibus0 at ahci0: 32 targets
> sd0 at scsibus0 targ 0 lun 0: <ATA, TOSHIBA MK1637GS, DL03> SCSI3 0/direct
fixed

> sd0: 152627MB, 512 bytes/sec, 312581808 sec total
> usb1 at uhci0: USB revision 1.0
> uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> usb2 at uhci1: USB revision 1.0
> uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> usb3 at uhci2: USB revision 1.0
> uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> usb4 at uhci3: USB revision 1.0
> uhub4 at usb4 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> isa0 at ichpcib0
> isadma0 at isa0
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pms0 at pckbc0 (aux slot)
> pckbc0: using irq 12 for aux slot
> wsmouse0 at pms0 mux 0
> pcppi0 at isa0 port 0x61
> midi0 at pcppi0: <PC speaker>
> spkr0 at pcppi0
> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> mtrr: Pentium Pro MTRR support
> umass0 at uhub0 port 4 configuration 1 interface 0 "TOSHIBA Optical
> Drive Controller" rev 2.00/0.00 addr 2
> umass0: using ATAPI over Bulk-Only
> scsibus1 at umass0: 2 targets, initiator 0
> cd0 at scsibus1 targ 1 lun 0: <MATSHITA, DVD-RAM UJ-844S, 1.10> ATAPI
> 5/cdrom removable
> ugen0 at uhub2 port 1 "AuthenTec Fingerprint Sensor" rev 1.10/c.10 addr 2
> softraid0 at root
> root on sd0a swap on sd0b dump on sd0b
>
> -Nick
>

Oh and thought you might want these:

record.adc_mute=off
record.adc=120,120
record.adc2_mute=off
record.adc2=120,120
record.adc3_mute=off
record.adc3=120,120
inputs.mix_source=mic,beep,hp
inputs.mix_mic=120,120
inputs.mix_mic2=120,120
inputs.mix_beep=120,120
inputs.mix_hp=120,120
outputs.mix2=16,16
inputs.mix2_source=dac2,mix
outputs.mix3=16,16
inputs.mix3_source=dac,mix
outputs.spkr_source=mix2
outputs.spkr_mute=off
outputs.spkr_dir=output
outputs.spkr_boost=off
outputs.hp_source=mix3
outputs.hp_mute=off
inputs.hp=85,85
outputs.hp_dir=output
outputs.hp_boost=off
outputs.mic_source=mix2
outputs.mic_mute=off
inputs.mic=85,85
outputs.mic_dir=input-vr80
outputs.mic_boost=off
inputs.mic2=85,85
outputs.mic2_dir=input-vr80
record.adc3_source=mic,mic2,beep,hp,mix
record.adc2_source=mic,mic2,beep,hp,mix
record.adc_source=mic,mic2,beep,hp,mix
outputs.hp_sense=unplugged
outputs.mic_sense=unplugged
outputs.spkr_muters=hp,mic
outputs.master=16,16
outputs.master.mute=off
outputs.master.slaves=mix2,mix3,spkr,hp
record.volume=120,120
record.volume.mute=off
record.volume.slaves=adc,adc2,adc3

name=HD-Audio
version=1.0
config=azalia0
encodings=slinear_le:16,slinear_le:20,slinear_le:24
properties=full_duplex,independent
full_duplex=0
fullduplex=0
blocksize=9600
hiwat=6
lowat=4
output_muted=0
monitor_gain=0
mode=
play.rate=48000
play.channels=2
play.precision=16
play.encoding=slinear_le
play.gain=16
play.balance=32
play.port=0x0
play.avail_ports=0x0
play.seek=0
play.samples=0
play.eof=0
play.pause=0
play.error=0
play.waiting=0
play.open=0
play.active=0
play.buffer_size=65536
play.block_size=9600
play.errors=0
record.rate=48000
record.channels=2
record.precision=16
record.encoding=slinear_le
record.gain=120
record.balance=32
record.port=0x0
record.avail_ports=0x0
record.seek=0
record.samples=0
record.eof=0
record.pause=0
record.error=0
record.waiting=0
record.open=0
record.active=0
record.buffer_size=65536
record.block_size=9600
record.errors=0

$ glxgears -info
Failed to initialize GEM. Falling back to classic.
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
GL_RENDERER = Mesa DRI Intel(R) 945GM 20090418 2009Q1 x86/MMX/SSE2
GL_VERSION = 1.4 Mesa 7.4.1
GL_VENDOR = Tungsten Graphics, Inc
GL_EXTENSIONS = GL_ARB_depth_texture GL_ARB_fragment_program
GL_ARB_multisample GL_ARB_multitexture GL_ARB_point_parameters
GL_ARB_shadow GL_ARB_texture_border_clamp GL_ARB_texture_compression
GL_ARB_texture_cube_map GL_ARB_texture_env_add
GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar
GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat
GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle
GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object
GL_ARB_vertex_program GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra
GL_EXT_blend_color GL_EXT_blend_equation_separate
GL_EXT_blend_func_separate GL_EXT_blend_logic_op GL_EXT_blend_minmax
GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_cull_vertex
GL_EXT_compiled_vertex_array GL_EXT_copy_texture
GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_multi_draw_arrays
GL_EXT_packed_depth_stencil GL_EXT_packed_pixels
GL_EXT_point_parameters GL_EXT_polygon_offset GL_EXT_rescale_normal
GL_EXT_secondary_color GL_EXT_separate_specular_color
GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_subtexture
GL_EXT_texture GL_EXT_texture3D GL_EXT_texture_edge_clamp
GL_EXT_texture_env_add GL_EXT_texture_env_combine
GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic
GL_EXT_texture_lod_bias GL_EXT_texture_object GL_EXT_texture_rectangle
GL_EXT_vertex_array GL_3DFX_texture_compression_FXT1
GL_APPLE_client_storage GL_APPLE_packed_pixels
GL_ATI_blend_equation_separate GL_ATI_texture_env_combine3
GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat
GL_INGR_blend_func_separate GL_MESA_pack_invert GL_MESA_ycbcr_texture
GL_MESA_window_pos GL_NV_blend_square GL_NV_light_max_exponent
GL_NV_point_sprite GL_NV_texture_rectangle GL_NV_texgen_reflection
GL_NV_vertex_program GL_NV_vertex_program1_1 GL_OES_read_format
GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp
GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SGIX_depth_texture
GL_SUN_multi_draw_arrays

And more about it's heat problems: I can't run a GL screensaver
because the screensaver will make the fan speed up. I don't know about
you but I'm used to thinking of screensaver mode as "it's safe, I can
stop paying attention to it".

-Nick

From forum: openbsd user - misc

Re: TOSHIBA PORTEGE R600

2009-11-23T18:42:49Z

On Mon, Nov 23, 2009 at 6:51 PM, <peter.ericson@...> wrote:
> Hi misc@I'm thinking of buying an R600 to run current on.Has anyone had any
> experience with these machines?From the spec sheet: Part Number
> PPR61A-02200R <ES5.0> CPU
> Intel® CoreTM2 Duo Processor ULV Su9400
> (1.4GHz, 800mHz FSB, 3MB l2 cache)
> mobile Intel® GS45 Express Chipset
> Video/Graphics Intel® Graphics media Accelerator GS45
> Wireless Communications Intel® 802.11 a/g/n, BluetoothTM V2.1 + EDR,
> Built-in 3G HSPA BIOS ACPI, PnP, VESA, DPmS,
DDC,
> Sm BIOS, PCI, BIOS support Audio
Intel®
> High Definition Audio Sound Wired
> Communications Intel® 1GBit Tx Ethernet + Active management
> Technology (AmT) 4.0 Thanks in advance,Peter Ericson
>
>

Funny you should ask. I have an R500 and it works fine, excepting the
lack of ACPI support of course. The Fn-Mute key combo even works right
away, no configuring needed (magic!). It's super flimsy though, I've
had it's optical drive repaired twice and the DC in has come loose and
I'm terrified of bumping the screen (it's 4mm thick). It's not the
worst laptop I've heard of as far as heat goes but it definitely gets
up there--I can't really do CPU intensive things on it since it'll get
up to 95degC and hover there really quick. Wifi is wpi(4) and except
for one firmware glitch once, and sometimes things lagging out (seems
to be correlated with heat) until I reset the card, I've never had any
problems. I'm not sure how different the R600 is, though.

This BIOS doesn't seem to like (legacy) GRUB: it hangs on the logo
screen unless I warm-boot or mash the F keys (very odd) but when I was
just using the OpenBSD MBR it never did that.

dmesg from 4.6-release:
OpenBSD 4.6 (GENERIC.MP) #89: Thu Jul 9 21:32:39 MDT 2009
deraadt@...:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Core(TM)2 CPU U7600 @ 1.20GHz ("GenuineIntel" 686-class) 1.20
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,CX16,
xTPR
real mem = 1064202240 (1014MB)
avail mem = 1020198912 (972MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 10/30/07, BIOS32 rev. 0 @
0xfcb25, SMBIOS rev. 2.4 @ 0xec000 (40 entries)
bios0: vendor TOSHIBA version "Version 1.50" date 10/30/2007
bios0: TOSHIBA PORTEGE R500
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP SSDT BOOT APIC MCFG HPET TCPA SLIC SSDT SSDT
acpi0: wakeup devices USB1(S3) USB3(S3) USB4(S3) EHCI(S3) GLAN(S4)
WLAN(S4) LID_(S4) PWRB(S4) HS87(S4) HS86(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 133MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU U7600 @ 1.20GHz ("GenuineIntel" 686-class) 1.20
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,CX16,
xTPR
ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 3 (PCIB)
acpiprt2 at acpi0: bus 1 (PEX1)
acpiprt3 at acpi0: bus 2 (MPEX)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpipwrres0 at acpi0: PDOC
acpitz0 at acpi0: critical temperature 102 degC
acpibtn0 at acpi0: LID_
acpibat0 at acpi0: BAT1 model "G71C00086210" serial 0000000796 type
Li-ION oem "0"
acpibtn1 at acpi0: PWRB
acpiac0 at acpi0: AC unit offline
acpidock0 at acpi0: DOCK not docked (0)
acpivideo0 at acpi0: VGA_
acpivout0 at acpivideo0: LCD_
acpivout1 at acpivideo0: CRT_
acpivout2 at acpivideo0: DVI_
bios0: ROM list: 0xc0000/0x10000 0xe0000/0x10000!
cpu0: Enhanced SpeedStep 1198 MHz: speeds: 1200, 800 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
vga1 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0xe0000000, size 0x10000000
inteldrm0 at vga1: apic 1 int 16 (irq 10)
drm0 at inteldrm0
"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:
apic 1 int 22 (irq 255)
azalia0: codecs: Realtek ALC262
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02
pci1 at ppb0 bus 1
em0 at pci1 dev 0 function 0 "Intel PRO/1000MT (82573L)" rev 0x00:
apic 1 int 16 (irq 10), address 00:15:b7:43:a0:f2
ppb1 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02
pci2 at ppb1 bus 2
wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02:
apic 1 int 18 (irq 11), MoW1, address 00:1c:bf:78:7f:04
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1
int 23 (irq 11)
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1
int 19 (irq 11)
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1
int 18 (irq 11)
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1
int 16 (irq 10)
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1
int 23 (irq 11)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb2 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
pci3 at ppb2 bus 3
cbb0 at pci3 dev 11 function 0 "TI PCIXX12 CardBus" rev 0x00: apic 1
int 21 (irq 255)
"TI PCIXX12 FireWire" rev 0x00 at pci3 dev 11 function 1 not configured
sdhc0 at pci3 dev 11 function 3 "TI PCIXX12 Secure Data" rev 0x00:
apic 1 int 23 (irq 255)
sdmmc0 at sdhc0
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 4 device 0 cacheline 0x8, lattimer 0x20
pcmcia0 at cardslot0
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02: PM disabled
ahci0 at pci0 dev 31 function 2 "Intel 82801GBM AHCI" rev 0x02: apic 1
int 19 (irq 11), AHCI 1.1
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0: <ATA, TOSHIBA MK1637GS, DL03> SCSI3 0/direct
fixed
sd0: 152627MB, 512 bytes/sec, 312581808 sec total
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb4 at uhci3: USB revision 1.0
uhub4 at usb4 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at ichpcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
mtrr: Pentium Pro MTRR support
umass0 at uhub0 port 4 configuration 1 interface 0 "TOSHIBA Optical
Drive Controller" rev 2.00/0.00 addr 2
umass0: using ATAPI over Bulk-Only
scsibus1 at umass0: 2 targets, initiator 0
cd0 at scsibus1 targ 1 lun 0: <MATSHITA, DVD-RAM UJ-844S, 1.10> ATAPI
5/cdrom removable
ugen0 at uhub2 port 1 "AuthenTec Fingerprint Sensor" rev 1.10/c.10 addr 2
softraid0 at root
root on sd0a swap on sd0b dump on sd0b

-Nick

From forum: openbsd user - misc

Познание PF

2009-11-23T18:23:50Z

Доброго здоровья многоуважаемый all.
Хотел орагнизовать дома простейшую точку доступа, для начала.
И попутно немного разобраться с PF.
Но натолкнулся на странные грабли.
Подскажите в чем моя ошибка.

За основу взял http://www.openbsd.ru/docs/wireless.html

Ось такова:

# uname -a
OpenBSD ogate.home.net 4.6 GENERIC#58 i386

Конфиг pf:

# Используемые макросы
ext_if = "vr0"
wlan_if = "rum0"

set require-order no

# Не фильтровать на интерфейсе обратной петли
set skip on lo

# Выполнить нормализацию входящего трафика
#scrub in on $ext_if fragment reassemble
scrub in on $ext_if all fragment reassemble

# Трансляция адресов на внешнем интерфейсе
nat on $ext_if from ! ($ext_if) -> ($ext_if:0)

# Блокирование всего входящего трафика
block in
block return-rst in proto tcp

# Применить защиту от IP-спуфинга
antispoof quick for $wlan_if

# Разрешить исходящие запросы
pass out proto tcp all flags S/SA modulate state
pass out proto { udp icmp } all keep state

# Разрешить доступ к ssh из беспроводной сети с ограниченным количеством
# подключений (для того, чтобы попытаться предотвратить попытки взлома
паролей)
pass in on $wlan_if proto tcp to ($wlan_if) port ssh keep state
(max-src-conn 10, max-src-conn-rate 15/5, overload <blocked> flush
global)

Посылает сюда:

pfctl -ef /etc/pf.conf
/etc/pf.conf:13: syntax error
pfctl: Syntax error in config file: pf rules not loaded

По сути 13 строка это "scrub in on $ext_if all fragment reassemble",
скопипастил прямо из манов.

Без этой строчки все робит.
Заранее благодарен.

--
С уважением Сохин Никита Александрович...

From forum: openbsd - Russian

FIX: Yelp should depend on xulrunner-1.8 package

2009-11-23T18:19:01Z

pkg_add asked me which xulrunner to install. I've choose 1.9 version and
installation failed. See attached patch.

--
best regards
q#

diff -ruN -xCVS /usr/ports/x11/gnome/yelp/Makefile yelp/Makefile
--- /usr/ports/x11/gnome/yelp/Makefile Sun Nov 22 20:19:00 2009
+++ yelp/Makefile Mon Nov 23 21:45:15 2009
@@ -4,6 +4,7 @@

GNOME_PROJECT= yelp
GNOME_VERSION= 2.28.1
+PKGNAME= ${DISTNAME}p0

# GPLv2
PERMIT_PACKAGE_CDROM= Yes
@@ -31,7 +32,7 @@
::x11/gnome/users-guide \
::x11/gnome/doc-utils
LIB_DEPENDS= startup-notification-1::devel/startup-notification \
- xulrunner/gtkembedmoz,xulrunner/xpcom,xulrunner/xul::devel/xulrunner/1.8,-main \
+ xulrunner/gtkembedmoz,xulrunner/xpcom,xulrunner/xul:xulrunner->=1.8,<1.9:devel/xulrunner/1.8,-main \
exslt,xslt::textproc/libxslt \
rarian::textproc/rarian

From forum: openbsd user - ports

Вниманию налогоплательщиков - срок до 14 декабря!!!

2009-11-23T18:02:32Z

Sb`f`el{e bk`dek|v{, psjnbndhrekh h ck`bm{e asxc`krep{, QOD TN, ophakhf`erq njnmw`mhe cnd` h hlemmn b }rh dmh g`jnmnd`rek|qrbn opednqr`bker bnglnfmnqr| ophmr| pexemhe - hqonk|gnb`r| sopnyemms~ hkh nays~ qhqrels m`kncnnaknfemh. Pexemhe menaxndhln ophmr| dn 14 dej`ap 2009 cnd`. Onlmhre, b qbgh q opedqrnyhl ophmrhel M`kncnbncn Jndejq` Sjp`hm{, s B`q eqr| bnglnfmnqr| onqkedmhi p`g bnqonk|gnb`r|q opehlsyeqrb`lh edhmncn m`knc`! N dnqrnhmqrb`x h mednqr`rj`x j`fdni hg qhqrel m`kncnnaknfemh B{ sgm`ere m` m`xel qelhm`pe. L{ onlnfel B`l qdek`r| op`bhk|m{i b{anp, hqxnd hg }jnmnlhweqjhx h m`kncnb{x onqkedqrbhi ophlememh sopnyemmni m`kncnnaknfemh.
4 dej`ap 2009 cnd` / (O44) 223*25*71

"Bqe n edhmnl m`knce b Sjp`hme. J`j oepeirh m` edhm{i m`knc q qnxp`memhel dhm`lhjh p`gbhrh ahgmeq` (opedophrh).
Ocoaemmnqrh c rowjh gpemh }jomnlhweqjhx hmrepeqnb makocook`rek|yhj`. Owebhdm{e opehlsyeqrb` h medncr`rjh edhmocn m`knca. Cjp{r{e bnglofmnqrh edhmoco m`koca dk ~pkhv h COD TN. Qsyeqrbemm{e mednqr`rjh h ncp`mhwemh EM, jnrnp{x qeiw`q mer, mn asdsr b qksw`e ophmrh M`kncnbncn Jndejq`."

1.Oepexnd m` sok`rs edhmncn m`knc` h bngbp`r m` nays~ qhqrels m`kncnnaknfemh.
2. Sqknbh, onpdnj, nqnaemmnqrh, ncp`mhwemh on qpnj`l dk ophmrh pexemh psjnbndhrekel.
3. Nqnaemmnqrh m`kncnnaknfemh ok`rek|yhjnb edhmncn m`knc`- ~phdhweqjhx h thghweqjhx khv.
4. A`g` m`kncnnaknfemh - mespecskhpnb`mm{e bnopnq{ EM, n jnrnp{x menaxndhln gm`r|.
5. MDQ oph edhmnl m`knce, nqnaemmnqrh oph qr`bj`x 6% h 10%, opehlsyeqrb` j`qqnbncn lernd` h jb`pr`k|mncn oephnd`; b{anp nrwermncn oephnd`; m`kncnb{i jpedhr on p`qxnd`l, jnrnp{e nopedek~rq b opnvemr`x nr m`kncnnak`c`elni opha{kh (pejk`lm` p`gd`w`, opedqr`bhrek|qjhe p`qxnd{); sok`r` MDQ w`qrm{lh opedophmhl`reklh-ok`rek|yhj`lh edhmncn m`knc`.
6. B{ok`r` dhbhdemdnb ok`rek|yhj`lh edhmncn m`knc`.
7. Bedemhe asxc`krepqjncn h m`kncnbncn swer` "edhmnm`knfmhj`lh"
8. Bnglnfmnqrh norhlhg`vhh m`kncnnaknfemh q hqonk|gnb`mhel ok`rek|yhjnb edhmncn m`knc`.
9. Rnb`pnnalemm{e noep`vhh ok`rek|yhjnb edhmncn m`knc`
10. Opnd`f` rnb`p` m` sqknbhx dncnbnp` jnlhqqhh hkh onpswemh. Bejqek h edhmnm`knfmhjh. Rpsdnsqrpniqrbn hmb`khdnb. Jsok-opnd`f` NQ h edhmyhjh.
11. Thm`mqnb` onlny| m` bngbp`rmni nqmnbe.
12. Ophlememhe na{wm{x vem oph opnbedemhh noep`vhi q ok`rek|yhj`lh edhmncn m`knc`.
13. Noep`vhh q m`khwmnqr|~. Ncp`mhwemh oph m`khwm{x p`qwer`x.
14. Nqsyeqrbkemhe derek|mnqrh, me sj`g`mmni b qbhderek|qrbe na sok`re edhmncn m`knc`.
15. "Ondbndm{e j`lmh" h bnglnfmnqrh edhmncn m`knc` oph norhlhg`vhh m`kncnb{x ok`refei.
16. M`knch h qanp{ nag`rek|m{e dk "edhmyhjnb". Dnonkmhrek|m{e bgmnq{ b OT, ok`rhr| hkh me ok`rhr|?
17. Mepeghdemr{ h edhm{i m`knc.
18. Bg`hlng`wer q Oemqhnmm{l tnmdnl - onpdnj opnbedemh h nrnap`femh b asxc`krepqjnl swere.
19. Wrn msfmn swhr{b`r| "na{wm{l" opedophrhl oph p`anre q ok`rek|yhj`lh edhmncn m`knc`.
20. Nrwermnqr| ok`rek|yhjnb edhmncn m`knc`, qpnjh sok`r{, nrberqrbemmnqr|, hqop`bkemhe nxhanj, ophlememhe jnqbemm{x lerndnb.
21. Nrber{ m` bnopnq{ h hmdhbhds`k|mne jnmqsk|rhpnb`mhe sw`qrmhjnb.

Sw`qrhe - 580 cpm, g` 2-x - 1020,00 cpm.

"Jpsck{i qrnk" q meank|xhl jnkhweqrbnl sw`qrmhjnb, oplne nayemhe q kejrnpnl, bnglnfmnqr| onkswhr| jb`khthvhpnb`mm{i h naqrnrek|m{i nrber m` hmrepeqs~yhi b`q bnopnq. Opnbndr - Wkem{ Qn~g` `sdhrnpnb Sjp`hm{ h TOA@S, `sdhrnp{-op`jrhjh q lmncnkermhl qr`fel, qoevh`khqr{ on bnopnq`l swer` h m`kncnnaknfemh, jnmqsk|r`mr{ on jnmtkhjr`l h qsdeam{l qonp`l q m`kncnb{lh npc`m`lh. Mh ndhm B`x bnopnq me nqr`merq aeg naqrnrek|mncn nrber`.

B`fmn! Sw`qrmhjh qelhm`p` lncsr ophnapeqrh w`qrmne opedophrhe m` edhmnl 10%-l m`knce q whqrni m`kncnbni ahncp`thei.

/\/\/\/\/\/\/\/\/\
goldvita
pmonsds
yhcsswosmo
rrijdpjy
ifowlktmbb

From forum: openbsd user - www

Re: phrase 'log rotation' in newsyslog.8

2009-11-23T17:11:13Z

Jason McIntyre just said:

> i'll change it to "rotate log files".

Good.
As Matthew observed, files are renamed and deleted, but not trimmed.

While here, i must admit i don't like the first two sentences of
newsyslog(8) at all.

* The text doesn't start by saying what the tool really does.
* When it finally comes to the point, in line 2, the verb
employed ("archive") is not very clear.
* The word "should" looks ugly in manuals.
* The wording "if necessary" is unnecessarily imprecise.
* The phrase "is determined to require" says the same as the
preceding sentence, but again without telling what "necessary",
"determine" and "require" actually refer to.

I think the following is more precise and easier to understand.
Besides, it's shorter:

Index: newsyslog.8
===================================================================
RCS file: /cvs/src/usr.bin/newsyslog/newsyslog.8,v
retrieving revision 1.44
diff -u -p -r1.44 newsyslog.8
--- newsyslog.8 31 May 2007 19:20:13 -0000 1.44
+++ newsyslog.8 24 Nov 2009 00:57:08 -0000
@@ -54,13 +54,12 @@
.Op Fl f Ar config_file
.Op Ar log ...
.Sh DESCRIPTION
+When a logfile exceeds a configurable size or age,
.Nm
-is a program that should be scheduled to run periodically by
+renames it and creates an empty file in its place.
+It is usually run by
.Xr cron 8 .
-When it is executed it archives log files if necessary.
-If a log file is determined to require archiving,
-.Nm
-rearranges the files so that
+After rotation,
.Pa logfile
is empty,
.Pa logfile.0

From forum: openbsd dev - tech

Re: Possible update for OpenSSH FAQ

2009-11-23T16:31:31Z

Fred Mobach wrote:
> Is this the correct e-mail address for posting comments about the
> OpenSSH FAQ ? If not, which e-mail address should I use ?
>
> Perhaps the following addition for OpenSSH FAQ 3.14 (as of 2009-nov-23)
> might be usefull :
> chown <user>:<group> ~/.ssh/{authorized_keys,

Thanks, I've added a chown (for the user only, the user:group syntax is
not portable, and the group is not relevant when there's no group write
as recommended).

--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

From forum: openbsd user - www

TOSHIBA PORTEGE R600

2009-11-23T16:03:45Z

Hi @misc

Apologies for the previous email, I tried to send a plain text email
from bigpond webmail and it stripped out the newlines.

Anyway, I'm thinking about buying an R600 to run current on, has
anyone had experience with this machine?

Part Number PPR61A-02200R <ES5.0>
CPU Intel. CoreTM2 Duo Processor ULV Su9400
(1.4GHz, 800mHz FSB, 3MB l2 cache)
mobile Intel. GS45 Express Chipset
Video/Graphics Intel. Graphics media Accelerator GS45
Wireless Communications Intel. 802.11 a/g/n, BluetoothTM V2.1 +
EDR, Built-in 3G HSPA
BIOS ACPI, PnP, VESA, DPmS, DDC, Sm BIOS, PCI,
BIOS support
Audio Intel. High Definition Audio Sound
Wired Communications Intel. 1GBit Tx Ethernet + Active
management Technology (AmT) 4.0

Thanks in advance,

--
Peter Ericson

From forum: openbsd user - misc

Re: Problem installing 4.6 on Toshiba Libretto 70CT

2009-11-23T15:53:49Z

On 11/18/09, Hou, Ruoyu <phoenixhou@...> wrote:

> All tests ended with
> kernel: integer divide fault trap, code=0
> Stopped at cpu_switchto+0x76: popl %ebx
>
> When softraid disabled
> ddb>trace
> cpu_switchto(d073cfa0,a26000,d0a20f18,d0a20ef8,d0202f41) at
> cpu_switchto+0x76
> (null)(d020241,0,d0a20f18,d037cab8,d0854018) at 0
> end(d0746c60,d073cfa0,0,d073cf57,0) at 0xd0a20ef8
> config_rootfound(d073cfa0,0,d0a20fa0,d0360adf,2) at config_rootfound+0x3c
> main(0,0,0,0,0) at main+0x4b8
>
> When acpi disabled/apm disabled/apm & acpi disabled
> ddb>trace
> cpu_switchto(d0851534,d0c17800,d0a20f18,d03763c9,d0c17800) at
> cpu_switchto+0x76
>
> cfdata(d0c17800,0c17800,0,0,d15ca984) at cfdata+0x44e8
> config_attach(0,d084a0a4,0,0,d073cf57) at config_attach+0xfd
> config_rootfound(d073cfa0,0,d0a20fa0,d0360adf,2) at config_rootfound+0x27
> main(0,0,0,0,0) at main+0x4b3

Hi misc@,

I tried this again with 23 Nov 09 snapshot, but it is still crashing
with an integer divide fault trap, as per PR 6052 [1].

The verbose output of dmesg and the ps and trace are included below [2].

The Libretto 70CT works fine with OpenBSD 4.3. This is not a major
issue, I'm just fond of my Libretto 70CT and want it running the
latest and greatest OS with 4.6 :~) I am happy to continue debugging
this issue but would be keen to have any pointers in the right
direction.

Thanks,

Fred

[1] http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=6052
[2]The verbose output is shown below:

Script started on Mon Nov 23 23:11:23 2009
x41:fred ~> cu -l /dev/cuaU0 -s19200
Connected
>> OpenBSD/i386 BOOT 3.02
boot> bsd -c
booting hd0a:bsd:
/-\|/6774012-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-
\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\
|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|
/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/
-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-
\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\+1054568
[52+352880|/-\|/-\|/-\|/-\|/-\|/+335902-\|/-\|/-\|/-\|/-\|/]=0x81f89c
entry point at 0x200120

[ using 689208 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2009 OpenBSD. All rights reserved. http://www.OpenBSD.org

OpenBSD 4.6-current (GENERIC) #391: Mon Nov 23 05:29:52 MST 2009
deraadt@...:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium/MMX ("GenuineIntel" 586-class) 121 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX
real mem = 16478208 (15MB)
avail mem = 7233536 (6MB)
User Kernel Config
UKC> verbose
autoconf verbose enabled
UKC> quit
Continuing...
>>> probing for mainbus0
>>> mainbus probe returned 1
mainbus0 at root

>>> probing for pci*
>>> pci probe returned 0
>>> probing for amdmsr0
>>> amdmsr probe returned 0
>>> probing for isa0
>>> isa probe returned 0
>>> probing for eisa0
>>> eisa probe returned 0
>>> probing for bios0
>>> bios probe returned 1
>>> probing for cpu0
>>> cpu probe returned 0
>>> probing for ioapic*
>>> ioapic probe returned 0
>>> probing for esm0
>>> esm probe returned 0
>>> bios probe won

bios0 at mainbus0: AT/286+ BIOS, date 11/11/97
>>> probing for apm0
>>> apm probe returned 1
>>> probing for mpbios0
>>> mpbios probe returned 0
>>> probing for pcibios0
>>> pcibios probe returned 0
>>> probing for acpi0
>>> acpi probe returned 0
>>> apm probe won
apm0 at bios0: Power Management spec V1.2
apm0: battery life expectancy 1%
apm0: AC on, battery charge low, charging
>>> probing for mpbios0
>>> mpbios probe returned 0
>>> probing for pcibios0
>>> pcibios probe returned 0
>>> probing for acpi0
>>> acpi probe returned 0
>>> no winning probe
pcibios at bios0 function 0x1a not configured
bios0: ROM list: 0xe4000/0xc000

>>> probing for pci*
>>> pci probe returned 0
>>> probing for amdmsr0
>>> amdmsr probe returned 0
>>> probing for isa0
>>> isa probe returned 0
>>> probing for eisa0
>>> eisa probe returned 0
>>> probing for cpu0
>>> cpu probe returned 1
>>> probing for ioapic*
>>> ioapic probe returned 0
>>> probing for esm0
>>> esm probe returned 0
>>> cpu probe won

cpu0 at mainbus0: (uniprocessor)
cpu0: F00F bug workaround installed

>>> probing for pci*
>>> pci probe returned 0
>>> probing for amdmsr0
>>> amdmsr probe returned 0
>>> probing for isa0
>>> isa probe returned 1
>>> probing for eisa0
>>> eisa probe returned 0
>>> probing for ioapic*
>>> ioapic probe returned 0
>>> probing for esm0
>>> esm probe returned 0
>>> isa probe won

isa0 at mainbus0
>>> probing for isadma0
>>> probing for isadma0 succeeded
isadma0 at isa0
>>> probing for ast0
>>> probing for ast0 failed
>>> probing for com0
>>> probing for com0 succeeded
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
>>> probing for com1
>>> probing for com1 succeeded
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
>>> probing for com2
>>> probing for com2 failed
>>> probing for cy0
>>> probing for cy0 failed
>>> probing for pckbc0
>>> probing for pckbc0 succeeded
pckbc0 at isa0 port 0x60/5
>>> probing for pckbd*
>>> pckbd probe returned 2
>>> probing for pms*
>>> pms probe returned 0
>>> probing for pmsi*
>>> pmsi probe returned 0
>>> pckbd probe won
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
>>> probing for wskbd*
>>> wskbd probe returned 1
>>> wskbd probe won
wskbd0 at pckbd0: console keyboard
>>> probing for pckbd*
>>> pckbd probe returned 0
>>> probing for pms*
>>> pms probe returned 10
>>> probing for pmsi*
>>> pmsi probe returned 0
>>> pms probe won
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
>>> probing for wsmouse*
>>> wsmouse probe returned 1
>>> wsmouse probe won
wsmouse0 at pms0 mux 0
>>> probing for vga0
>>> probing for vga0 succeeded
vga0 at isa0 port 0x3b0/48 iomem 0xa0000/131072
>>> probing for inteldrm*
>>> inteldrm probe returned 0
>>> probing for radeondrm*
>>> radeondrm probe returned 0
>>> probing for intagp*
>>> intagp probe returned 0
>>> probing for wsdisplay*
>>> wsdisplay probe returned 1
>>> wsdisplay probe won
wsdisplay0 at vga0 mux 1: console (80x25, vt100 emulation), using wskbd0
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)

>>> probing for pcdisplay0
>>> probing for pcdisplay0 failed
>>> probing for bha0
>>> probing for bha0 failed
>>> probing for aic0
>>> probing for aic0 failed
>>> probing for aha0
>>> probing for aha0 failed
>>> probing for aha1
>>> probing for aha1 failed
>>> probing for uha0
>>> probing for uha0 failed
>>> probing for wdc0
>>> probing for wdc0 succeeded

wdc0 at isa0 port 0x1f0/8 irq 14
>>> probing for atapiscsi*
>>> atapiscsi probe returned 0
>>> probing for wd*
>>> wd probe returned 1
>>> wd probe won
wd0 at wdc0 channel 0 drive 0: <IBM-DDLA-21620>
wd0: 16-sector PIO, LBA, 1551MB, 3177216 sectors
wd0(wdc0:0:0): using BIOS timings

>>> probing for wdc1
>>> probing for wdc1 failed
>>> probing for lc0
>>> probing for lc0 failed
>>> probing for lc1
>>> probing for lc1 failed
>>> probing for ne0
>>> probing for ne0 failed
>>> probing for ne1
>>> probing for ne1 failed
>>> probing for ne2
>>> probing for ne2 failed
>>> probing for we0
>>> probing for we0 failed
>>> probing for we1
>>> probing for we1 failed
>>> probing for ec0
>>> probing for ec0 failed
>>> probing for ep0
>>> probing for ep0 failed
>>> probing for ep*
>>> probing for ep* finished
>>> probing for ie0
>>> probing for ie0 failed
>>> probing for ex0
>>> probing for ex0 failed
>>> probing for le0
>>> probing for le0 failed
>>> probing for sm0
>>> probing for sm0 failed
>>> probing for mpu*
>>> probing for mpu* finished
>>> probing for sb0
>>> probing for sb0 succeeded

sb0 at isa0 port 0x220/24 irq 5 drq 1: dsp v3.01
>>> probing for audio*
>>> audio probe returned 0
>>> probing for midi*
>>> midi probe returned 1
>>> probing for opl*
>>> opl probe returned 0
>>> midi probe won
midi0 at sb0: <SB MIDI UART>
>>> probing for audio*
>>> audio probe returned 1
>>> probing for midi*
>>> midi probe returned 0
>>> probing for opl*
>>> opl probe returned 0
>>> audio probe won
audio0 at sb0
>>> probing for audio*
>>> audio probe returned 0
>>> probing for midi*
>>> midi probe returned 0
>>> probing for opl*
>>> opl probe returned 3
>>> opl probe won
opl0 at sb0: model OPL3
>>> probing for midi*
>>> midi probe returned 1
>>> midi probe won
midi1 at opl0: <SB Yamaha OPL3>
>>> probing for pas0
>>> probing for pas0 failed
>>> probing for pss0
>>> probing for pss0 failed
>>> probing for wss0
>>> probing for wss0 succeeded
wss0 at isa0 port 0x530/8 irq 10 drq 0: CS4231 or AD1845 (vers 4)
>>> probing for audio*
>>> audio probe returned 1
>>> audio probe won
audio1 at wss0
>>> probing for gus0
>>> probing for gus0 failed
>>> probing for pcppi0
>>> probing for pcppi0 succeeded
pcppi0 at isa0 port 0x61
>>> probing for midi*
>>> midi probe returned 1
>>> probing for spkr0
>>> spkr probe returned 1
>>> midi probe won
midi2 at pcppi0: <PC speaker>
>>> probing for midi*
>>> midi probe returned 0
>>> probing for spkr0
>>> spkr probe returned 1
>>> spkr probe won
spkr0 at pcppi0
>>> probing for midi*
>>> midi probe returned 0
>>> no winning probe
>>> probing for lpt0
>>> probing for lpt0 succeeded
lpt0 at isa0 port 0x378/4 irq 7

>>> probing for lpt1
>>> probing for lpt1 failed
>>> probing for lpt2
>>> probing for lpt2 failed
>>> probing for wbsio*
>>> probing for wbsio* finished
>>> probing for wbsio*
>>> probing for wbsio* finished
>>> probing for schsio*
>>> probing for schsio* finished
>>> probing for schsio*
>>> probing for schsio* finished
>>> probing for schsio*
>>> probing for schsio* finished
>>> probing for schsio*
>>> probing for schsio* finished
>>> probing for lm0
>>> probing for lm0 failed
>>> probing for fins0
>>> probing for fins0 failed
>>> probing for nsclpcsio*
>>> probing for nsclpcsio* finished
>>> probing for nsclpcsio*
>>> probing for nsclpcsio* finished
>>> probing for gscsio*
>>> probing for gscsio* finished
>>> probing for gscsio*
>>> probing for gscsio* finished
>>> probing for it*
>>> probing for it* finished
>>> probing for it*
>>> probing for it* finished
>>> probing for viasio*
>>> probing for viasio* finished
>>> probing for viasio*
>>> probing for viasio* finished
>>> probing for aps0
>>> probing for aps0 failed
>>> probing for npx0
>>> probing for npx0 succeeded

npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16

>>> probing for lms0
>>> probing for lms0 failed
>>> probing for lms1
>>> probing for lms1 failed
>>> probing for mms0
>>> probing for mms0 failed
>>> probing for mms1
>>> probing for mms1 failed
>>> probing for fdc0
>>> probing for fdc0 failed
>>> probing for isapnp0
>>> probing for isapnp0 failed
>>> probing for pcic0
>>> probing for pcic0 succeeded

pcic0 at isa0 port 0x3e0/2 iomem 0xd0000/65536
pcic0 controller 0: <Intel 82365SL rev 1> has sockets A and B
>>> probing for pcmcia*
>>> pcmcia probe returned 1
>>> pcmcia probe won
pcmcia0 at pcic0 controller 0 socket 0

>>> probing for ep*
>>> ep probe returned 0
>>> probing for ne*
>>> ne probe returned 0
>>> probing for wi*
>>> wi probe returned 0
>>> probing for an*
>>> an probe returned 0
>>> probing for malo*
>>> malo probe returned 0
>>> probing for com*
>>> com probe returned 0
>>> probing for aic*
>>> aic probe returned 0
>>> probing for wdc*
>>> wdc probe returned 0
>>> probing for sm*
>>> sm probe returned 0
>>> probing for xe*
>>> xe probe returned 1
>>> probing for ray*
>>> ray probe returned 0
>>> xe probe won

xe0 at pcmcia0 function 0 "Xircom, CreditCard 10Base-T, PS-CE2-10"
port 0x340/16, irq 9: address 00:80:c7:42:37:d9
>>> probing for pcmcia*
>>> pcmcia probe returned 1
>>> pcmcia probe won
pcmcia1 at pcic0 controller 0 socket 1
pcic0: irq 11, polling enabled
>>> probing for pcic1
>>> probing for pcic1 failed
>>> probing for pcic2
>>> probing for pcic2 failed
biomask e145 netmask e345 ttymask fbdf
>>> probing for vscsi0
>>> vscsi probe returned 1
vscsi0 at root
>>> probing for scsibus*
>>> scsibus probe returned 1
>>> scsibus probe won
scsibus0 at vscsi0: 256 targets
>>> probing for softraid0
>>> softraid probe returned 1
softraid0 at root
kernel: integer divide fault trap, code=0
Stopped at cpu_switchto+0x76: popl %ebx
ddb> ps
PID PPID PGRP UID S FLAGS WAIT COMMAND
8 0 0 0 2 0x100200 pfpurge
7 0 0 0 2 0x100200 pcic0,0,1
6 0 0 0 2 0x100200 pcic0,0,0
5 0 0 0 2 0x100200 apm0
4 0 0 0 2 0x100200 syswq
3 0 0 0 2 0x100200 idle0
2 0 0 0 2 0x100200 kmthread
* 1 0 0 0 7 0 swapper
0 -1 0 0 3 0x80200 wdccmd swapper
ddb> trace
cpu_switchto(d0852554,d0bdb800,d0a21f18,d0376839,d0bdb800) at
cpu_switchto+0x76

cfdata(d0bdb800,d0bdb800,0,0,d100a984) at cfdata+0x44e8
config_attach(0,d084b0a4,0,0,d073db77) at config_attach+0xfd
config_rootfound(d073dbc0,0,d0a21fa0,d0360f4f,2) at config_rootfound+0x27
main(0,0,0,0,0) at main+0x4b3
ddb> boot poweroff

Attempting to power down...
~
[EOT]
x41:fred ~> exit

Script done on Mon Nov 23 23:30:35 2009

From forum: openbsd user - misc

TOSHIBA PORTEGE R600

2009-11-23T15:51:27Z

Hi misc@I'm thinking of buying an R600 to run current on.Has anyone had any
experience with these machines?From the spec sheet: Part Number
PPR61A-02200R <ES5.0> CPU
Intel® CoreTM2 Duo Processor ULV Su9400
(1.4GHz, 800mHz FSB, 3MB l2 cache)
mobile Intel® GS45 Express Chipset
Video/Graphics Intel® Graphics media Accelerator GS45
Wireless Communications Intel® 802.11 a/g/n, BluetoothTM V2.1 + EDR,
Built-in 3G HSPA BIOS ACPI, PnP, VESA, DPmS, DDC,
Sm BIOS, PCI, BIOS support Audio Intel®
High Definition Audio Sound Wired
Communications Intel® 1GBit Tx Ethernet + Active management
Technology (AmT) 4.0 Thanks in advance,Peter Ericson

From forum: openbsd user - misc

Re: Hardware versus Software RAID

2009-11-23T15:49:01Z

On Sun, Nov 22, 2009 at 5:53 PM, Nick Holland
<nick@...> wrote:
> Theodore Wynnychenko wrote:
> ...
>> Anyway, I had not considered the possibility of a controller failure.
>
> bad...
>
>> I also wondered if it was possible to remove a drive from the mirrored
>> hardware array, and see if it is recognized by a plain old SATA
controller.
>> So, I did this by shutting the system down, enabling the motherboard's
SATA
>> controller, and moving one of the drive cables to this standard SATA
>> controller.
>
> good...
>
>> Unfortunately, while the array comes up and is accessible, even though it
is
>> degraded; I cannot access the drive now attached to the standard SATA
>> controller. If I try to fsck it, I get an "unknown special file or file
>> system" message.
>>
>> So, it seems, with ami and this megaraid card, I will not be able to
recover

>> from a controller failure by hooking a drive up to a standard SATA
>> controller.
>
> and thus, you find that one person's experience with ONE set of hardware
> can not be universally generalized.
>
>> So, my question: How likely is a raid controller failure (with the LSI
>> Megaraid PCI cards),
>
> Wrong question.
> Right question would be: so what do you do when it does fail?
>
> Spare RAID hardware is required if rapid repair is needed if diving
> for your backup system is not what you are after, after the failure of
> one little component. And...I do believe that is the point of RAID.
>
>> and would I be better off just chucking the Megaraid
>> card and using software raid with the drives connected via the standard

SATA

>> controllers?
>
> If you have a single, non-redundant drive, you KNOW you have a significant
> exposure to failure, and you will have backups and such, or be ready to
> take a bit of downtime and data loss.
> When you implement RAID, you start telling yourself you have all
> kinds of tolerance to unhappy events, and then you start to believe it.
>
> With a spare controller, you could have rapid repair.
> Without a spare controller, the failure of the controller has the EXACT
> same impact that the failure of a drive on a single drive, non-RAID system:
> complete and total loss of data on the system and recovery of your data
> from the backup which you wish you had been making.
>
> here's the fun (=terrifying) part: WITH a spare controller, things can
> get at least as unpleasant as above.
>
> If you just set up your RAID system and "get it working" and then toss it
> into production, and hope magic will happen when something breaks, you
> would probably have been better off with a simpler configuration with no
> RAID. I'm serious. The worst data-loss events I have seen involved
> RAID. If you don't understand your chosen RAID solution, given
> enough time and/or enough opportunity, your downtime will be extended,
> and your data will be lost.
>
> Not only should you have "similar" spare controllers, you need IDENTICAL
> spare controllers -- right down to the firmware versions. Yes, I have
> seen firmware notes which had big warnings of "unable to read arrays
> made by version X of the firmware or hardware". Are you ready to bet
> that every option on this version of the card you have is compatible
> with every option of the card you hope to buy when your existing one
> dies? If you believe this, I ask you a question: why are there so many
> updates to RAID controller firmware made if they are so perfect?
> What's the first bit of advice you always seem to hear on a new server
> setup? "Update the firmware". Why? Because the old one was crap.
> Amazingly, the one you just installed is now perfect. Yeah, right.
>
> It's a numbers game. If you have five disks on a machine, maybe you
> have a 1 in 4 chance of failing in a two year life cycle of the machine.
> If you put a sixth disk in the machine and RAID the bunch of 'em, you
> get a MUCH lower likelihood of failure due to a disk, but much higher
> due to failure of a RAID controller (which had no chance of failing
> on the system that didn't have it), maybe 1 in 20 (or maybe one in 200
> or one in 2000..whatever). You also add the possibility of failure of
> process (i.e., one drive fails, you say, "what's the rush?" and rather
> than rushing out and buying a new drive, you send the old one off for
> warranty replacement, and in the weeks you wait, a second drive fails.
> I saw this recently... big array with a few terabytes of important
> data blew out a disk. First failure was not having a spare disk on
> hand. Second failure was rather than running out and BUYING a new disk
> and putting it in the machine, the old drive was sent off for warranty
> replacement, and the system ran without redundancy until it came back.
> At that point, they put a very firm value on the safety of their data:
> <$100. In this case, the disaster did not happen. Pulling numbers
> out of thin air, I'd say failure of process might be something like 1
> in 3 when you think you have hardware to save you from failures...more
> like 1 in 10 when you know you are living on the edge).
>
> (90% of all statistics are made up. 100% of those were...but they may
> be closer than you would like).
>
> If that spare controller costs you $400, but loss of data or extended
> downtime is worth $4000 to you, ok, maybe it is worth the gamble of
> living without a spare. If your data is worth, say, $40k, maybe you
> just better spend the money for a spare controller, regardless of what
> you think the likelihood of failure is.
>
> But now that you have your RAID system in place, you had better
> experiment with it to make sure you know how to handle drive failure
> and replacement, and in the case of hardware, how to handle HARDWARE
> failure and replacement (i.e., move the disk pack to a new controller).
> Hint: it is often not as easy as you think to move the disk pack to
> new hardware. It seems hardware vendors often don't consider that
> anything other than disks fail. *sigh*
>
>> I figure there must be some performance loss, but I can't
>> imagine I will ever notice it looking at old pictures.
>
> Here's an alternate potential solution: put two or more simple disks
> in the computer, and periodically copy the data from the primary to
> the backup... Not applicable in all cases, but actually superior
> in some. It gives you a nice opportunity to think about and evaluate
> changes you made before committing them to all media. (DNS servers
> and firewalls are two cases where I have used this effectively: the
> data isn't all that volatile, if you lose a day's changes, not the
> end of the world, but if you don't do it right, it is really nice to
> just copy the old file back quickly rather than go digging through
> tape).
>
> Note that this system has its own potential failure modes -- if your
> primary disk has lost data that the system hasn't noticed yet, it WILL
> notice during the copy operation, and probably destroy the "mirror"
> data in the process of noticing...so your backups are still important.
>
>> Finally, I am wondering. I had assumed that the hardware controller

really
>> didn't do that much when in RAID1, and just passed the writes/reads
to/from

>> both of the disks, resulting in 2 (basically) normal drives. Obviously, I
>> was wrong. I am wondering why/how the raid controller needs to modify the
>> disk's file system when it's only mirroring 2 drives? (I really could not
>> find anything by google-ing around on this.)
>
> here's where I say, "you need to think about and simulate all imaginable
> failure modes", and you start to understand how these things work.
>
> The hardware RAID systems I've worked with treat RAID1 as one of several
> different RAID systems supported...they don't treat it significantly
> different than RAID5, RAID1+0, etc.
>
> There is more to RAID1 than duping the data to two drives and keeping them
> the same. All HW RAID systems that I have seen use some kind of signature
> to mark the drives as part of a RAID set (RAID1 or otherwise). The
> signature is quite important:
>
> * Let's say you have six drives, three RAID1 pairs. While servicing the
> computer, you unplug the drive cables to extract or install some other
> card in the machine...you then realize you didn't make note of what cable
> went where. How do you want your RAID controller to handle this? You
> probably really hope it spots the pairs and re-connects them appropriately.
>
> * What if you need to swap out a drive while the system is off? Which
> drive does it use on power-up?
>
> * What if you replace a drive while the system is off with another drive
> that was recycled from a system with a compatible RAID card? Which is the
> one that should be used and which should be ignored?
>
> * What if you power up a system and it has two drives attached that it
> knows nothing about? Pick one and blindly copy it to the other? Assume
> they are in sync?
>
> * What if you can't replace the failed drive with one that is identical
> to it? What if the new drive is a bigger or a few blocks smaller?
>
> The signature that helps resolve the above has to be somewhere on the
> disk. Some systems try to hide it some place the OS would never notice
> (I believe I read some tech notes on one system that stuck it on the
> very last sector of the disk, with the assumption that very few OSs ever
> put anything there, I've seen one other RAID system that seemed to do
> that, as the drives COULD be removed from the RAID system and used
> directly on a standard controller), but others just plop it at the
> front of the physical disk, and create the array in the remaining
> space.
>
> The point of RAID1 isn't to dupe the data on two drives, the point of
> RAID1 is to have the system rapidly recoverable when something goes
> horribly wrong. Duping the data between two drives is the way to meet
> that end, but there is more to it than two blind copies of the same
> data.
>
>> I hope I don't sound too clueless for asking.
>
> No more clueless than 90% of the people out there setting up RAID
> disasters in waiting... Many very smart people who seem to think
> that Magic Happens (or that think they will have a job elsewhere)
> when things go wrong.
>
> Nick.
>
>

You hit on a lot of things that I didn't even consider, Nick. I think
very few people think about the controller when they design a RAID
array. Even fewer, as you said, would consider how said controller
works in the event of a drive failure.

Every method has its caveats. You could chuck two identical RAID
cards into a box and put 2 striped disks on each, mirroring the two in
software - but you'd also need to understand how the system copes with
a drive failing on either card - and realise that in the improbable
situation where a drive fails on both cards, you're toast unless you
implemented a bulletproof backup plan when you put the damn thing into
production. You'd also need to know how to get the stripe on a card
going again, and then rebuild the mirror. You'd need to understand
how this works as well so you don't go trashing your mirror during the
rebuild because it didn't go how you thought it would.

"Magic blue smoke" is for the computer illiterate. As the
administrator of the system you're installing, you need to have a
comprehensive understanding of its inner workings. As we now realise
today, this includes the underlying hardware and the firmware that
drives it. The only way I can see this being done is to test every
scenario you think you'll encounter and watch the results, including
what happens when you (need to) intervene. Write up a testing plan
with what you expect to happen with each type of failure and how
you'll simulate it. When you do each test, write down what really
happened, especially if it differs in any way to your expectations.
That's the only way I can see you being able to understand your beast.
Once you've done that, if the machine was intended for use in a
production environment, I'd buy the same stuff again and build a new
box, using the current one as a failover or development machine - it
would have been stressed in the testing and can't be considered
reliable for a production environment.

I've learned a lot from your post (and I'm sure many others have).
Thank you, Nick. If I could, I'd shout you a beer (or whatever your
poison is). Feel free to correct me if you think I am wrong.

--
Aaron Mason - Programmer, open source addict
I've taken my software vows - for beta or for worse

From forum: openbsd user - misc

Re: Question regarding to dsniff.

2009-11-23T15:28:46Z

On Mon, Nov 23, 2009 at 12:39 PM, Mateusz Gierblinski
<mateusz.gierblinski@...> wrote:
> Hello
>
> I'm playing around with some security tools and I would like to test out the
> dsniff package. I have tried to install dsniff using ports, db, libnet &
> dsniff had been compiled but on the end of the installation process log file
> told me that the installation of dsniff had been faked. Why?
>

You built from ports right? Ports "fakes" installation to somewhere
under the ports tree, then builds a package from that, then, if you've
said 'make install', runs pkg_add on that package.

From forum: openbsd user - misc

Re: ksh experts take a look please (tiny patch inside)

2009-11-23T15:03:47Z

On Sun, Nov 22, 2009 at 9:11 PM, Philip Guenther <guenther@...> wrote:
> On Sat, Nov 21, 2009 at 9:21 PM, patrick keshishian <sidster@...> wrote:
>> On Sat, Nov 21, 2009 at 09:15:17PM -0800, patrick keshishian wrote:
>>> I wonder if included patch is a correct fix for the following
>>> "glitch" I'm seeing with ksh in `set -o vi' mode:
...

Ya know, it's much easier to reproduce this if you actually confirm
that you're in vi mode instead of just 'remembering' that you use vi
mode everywhere. Yep, looks like a cute glitch. 'scuse me while I
finish this crow pie...

Philip

From forum: openbsd dev - tech

Re: UPDATE: scummvm 1.0.0

2009-11-23T14:52:25Z

Dawe wrote:

> Jonathan Gray wrote:
>> please test, on your favourite !i386 arch especially.
>>
>
> Tested with "Beneath a Steel Sky" and "Day of the Tantacle" on amd64 and
> powerpc.
> On amd64 both games worked fine.
> On powerpc DOTT worked but with BASS there's a segmentation fault right
> after the intro.
>
> Here's the backtrace:
> (gdb) backtrace
> #0 0x01d8780c in Sky::Debug::script (command=0, scriptData=0x2d00203c)
> at endian.h:137
> #1 0x01d8d480 in Sky::Logic::script (this=0x2b144800, scriptNo=22348,
> offset=1) at engines/sky/logic.cpp:1267
> #2 0x01d8be40 in Sky::Logic::logicScript (this=0x2b144800)
> at engines/sky/logic.cpp:193
> #3 0x01d8bd5c in Sky::Logic::engine (this=0x2b144800)
> at engines/sky/logic.cpp:160
> #4 0x01d7a208 in Sky::SkyEngine::go (this=0x24525f00)
> at engines/sky/sky.cpp:207
> #5 0x01d7a208 in Sky::SkyEngine::go (this=0x24525f00)
> at engines/sky/sky.cpp:207
> #6 0x01d7a208 in Sky::SkyEngine::go (this=0x24525f00)
> at engines/sky/sky.cpp:207
> #7 0x01d7a208 in Sky::SkyEngine::go (this=0x24525f00)
> at engines/sky/sky.cpp:207
> #8 0x01d7a208 in Sky::SkyEngine::go (this=0x24525f00)
> at engines/sky/sky.cpp:207
> #9 0x01d7a208 in Sky::SkyEngine::go (this=0x24525f00)
> at engines/sky/sky.cpp:207
> Previous frame inner to this frame (corrupt stack?)
>

I checked if this is a regression, it's not. The current 0.13.1p0
package has the same issue on powerpc.

From forum: openbsd user - ports

Re: ksh experts take a look please (tiny patch inside)

2009-11-23T14:20:34Z

On Sun, Nov 22, 2009 at 09:11:14PM -0800, Philip Guenther wrote:

> On Sat, Nov 21, 2009 at 9:21 PM, patrick keshishian <sidster@...>
> wrote:
> > On Sat, Nov 21, 2009 at 09:15:17PM -0800, patrick keshishian wrote:
> >> I wonder if included patch is a correct fix for the following
> >> "glitch" I'm seeing with ksh in `set -o vi' mode:
> >>
> >> Demonstration of "glitch":
> >> $ touch a.c a.h
> >> $ ls a.<TAB><RETURN>
> >> ls: a.: No such file or directory
> >> $ <TAB>
> >> a.c a.h
> >> $
> >>
> >> With patch:
> >> $ ls a.
> >
> > And of course I had to screw this up, but I think the point
> > was made.
> >
> > Above should've been:
> >
> > $ ls a.<TAB><RETURN>
> >> ls: a.: No such file or directory
> >> $ <TAB><BEEP>
>
> <squint>
>
> I *think* you're saying that it's continuing to do completion of the
> "a." prefix when you hit tab, even after you've hit enter and are
> sitting at a fresh prompt. Is that the behavior you're trying to
> report? If so, I'm unable to reproduce that on -current, i386,
> neither at the console, in an xterm, in screen in an xterm, nor in
> tmux in an xterm. Could you confirm the problem behavior and describe
> where you're experiencing it?

I can reproduce the behaviour.
The following experiment may show the behaviour more clearly:

-> needed for ksh:
$ set -o vi
$ set -o vi-tabcomplete
-> needed in current dir, two files with identical start:
$ touch foo.bar foo.baz

-> type some comand + first part of filename:
$ ls foo
-> press tab to perform stage 1 expansion resulting in:
$ ls foo.ba
-> press enter to perform command:
ls: foo.ba: No such file or directory
$
-> press tab again and see the system perform the second stage of the
completion of the previous command:
foo.bar foo.baz
$

further demonstration illustrating a failed reset:
-> type comand + first part of filename;
$ ls foo
-> press tab to perform stage 1 expansion resulting in:
$ ls foo.ba
-> press tab to perform stage 2 expansion resulting in:
foo.bar foo.baz
-> press enter to perform command:
ls: foo.ba: No such file or directory
$
-> press tab again and see the system perform the third stage of the
completion of the previous command (reset to initial text before first
completion):
$ ls foo

If I read the patch in the original post correctly that patch resets the
completion engine state when a \r or \n is intered into the shell.

> Philip Guenther

Janjaap van Velthooven
-- ________________________________________
/ __/ /_ / ______/ /_ __/ __/ /___ /
/ /_ __/___/_/_ /___ / / __/ /___ / / janjaap@...
/___/_/_________/_____/_/_/_/_______/_/_/

From forum: openbsd dev - tech

Re: Intel PRO/1000MF (82545GM) Hardware Initialization Failed - 4.6 amd64

2009-11-23T14:18:37Z

Ben Franklan wrote:
> Hi All
> I have 2 identical machines running 4.6 stable. I have tried removing
> some of the other hardware and changing some irq settings in the bios,
> but there is not really much to change. Does anyone have any advice on
> getting these network cards to work?
>
>

the relevant error is this one

> em0 at pci3 dev 2 function 0 "Intel PRO/1000MF (82545GM)" rev 0x04:
> apic 3 int 3 (irq 6)em0: Hardware Initialization Failedem0: Unable to
> initialize the hardware
>

try booting a snapshot kernel on the machine, it should work. i had this
problem with some em interfaces with snapshots from a few months back so
i am guessing it's in 4.6 release.

From forum: openbsd user - misc

Re: WIP: multimedia/gpodder

2009-11-23T14:11:37Z

Updated:
Installs man pages on $PREFIX/man, by patching
the relevant files. (Pointed out by Stuart Henderson).

Buttons appear correct after creating ~/.gtkrc-2.0
with gtk-icon-theme-name = "gnome". I suppose I needed
it because I'm not running gnome.

http://cosmico.net/tmp/gpodder.tgz as well as attached.

thanks,
--rodolfo

gpodder.tgz (3K) Download Attachment

From forum: openbsd user - ports

ShippingExplorer - Live Vessel Tracking (Ship Tracking via Automatic Identification System)

2009-11-23T13:44:20Z

HomeFeaturesVideosPricingDownloadOrder

How does it work?
Our systems collect data from AIS receivers placed around seas, canals, and ports. The data is immediately sent to our servers which then distribute that data in real-time to our customers via the Internet.

What is AIS?
The Automatic Identification System (AIS) is required on passenger ships, tankers, and ships with a gross tonnage of 300+. They're all equipped with an AIS transponder which regularly transmits live data about its ship's position, name, size, speed, course, destination, etc. More...
Get Free Access!
You are already receiving AIS data (e.g. ShipPlotter) or are willing to setup our receiver in your region? Get your personal key to use ShippingExplorer for FREE. Contact us for further information.

Try the Demo
Everyone interested can try our software with a few restrictions and a delay of up to 72 hours. Just download our program and use "DEMO" as your key.

Get a Test-Key
You can get your personal test-key. It's limited for 5 days of use but provides you all features for testing purposes. Just contact us with your request.

Welcome
ShippingExplorer is a cost-effective software to track vessels with live data. It displays all vessels in range at their exact position on your favorite map. Additional information, photos, track history, etc. about vessels can be viewed right away in our client software.
The new version also allows you to use filters on the map (such as "All vessels heading to Rotterdam", "All cargo ships", "All German vessels" and much more).
Also a new Alert Zone system was introduced. You draw a zone on the map and once the specified ship enters that zone you'll be alerted via e-mail or SMS on your cell phone. Latest News 31.05.09, Weather Overlays
New version of ShippingExplorer includes port- and seaweather and many more new features. 10.03.09, One More In Turkey
Zonguldak was added. 10.03.09, 1st Caspian Sea Port
Aktau was added. 04.03.09, Egypt Areas Added
Port Said was added and many more are to come!

Covered Areas

...many more to come.

Contact Us | Dealers | English, Psqqjhi
) 2006-2009 ShippingExplorer. All rights reserved.

From forum: openbsd user - misc

Вниманию налогоплательщиков - срок до 14 декабря!!!

2009-11-23T13:41:08Z

From forum: openbsd user - www

Re: phrase 'log rotation' in newsyslog.8

2009-11-23T13:40:09Z

* Jason McIntyre <jmc@...> [091123 15:06]:

> On Mon, Nov 23, 2009 at 11:55:01AM -0800, Matthew Dempsky wrote:
> > On Mon, Nov 23, 2009 at 11:11 AM, Jason McIntyre <jmc@...> wrote:
> > > anyone else want to chip in?
> >
> > I think "rotate log files" is sufficiently clear. I think that's
> > jargon that most sysadmins would understand, and it's also probably
> > the first thing people would search for.
> >
> > I'm not a fan of describing it as "trimming", because the files
> > themselves are never trimmed (i.e., truncate(2)), but I can understand
> > the use.
> >
> > I think any text mentioning that it's to maintain a reasonable size is
> > redundant; that seems like a pretty basic feature that you'd assume of
> > any real log rotation system.
> >
> > Just my 2c.
>
> these are pretty much my thoughts. so unless anyone comes up with a
> compelling reason not to, i'll change it to "rotate log files".
>
> jmc
>

FWIW, I agree too.

jim

From forum: openbsd dev - tech

ShippingExplorer - Live Vessel Tracking (Ship Tracking via Automatic Identification System)

2009-11-23T13:38:03Z

From forum: openbsd user - www

Re: ralink слабый сигнал

2009-11-23T13:34:47Z

On Mon, Nov 23, 2009 at 17:50 +0300, Алексей Бабкин wrote:

> Здравствуйте, Mike.
>
> Вы писали 23 ноября 2009 г., 16:26:56:
>
> > On Mon, Nov 23, 2009 at 16:54 +0400, mitrofanzzz wrote:
> >> Troex Nevelin пишет:
> >>>
> > ну если такой как на картинке:
> > http://crypt.org.ru/~mkb/pub/net5501/net5501.jpg
>
>
> А теперь по подробней можно, что это за платка (мамка) ?
> тож вот хотелось себе такой софт роутерю :)
>

ну хочется, купите, кто ж мешает-то (:

> И как он роутит и проксируем муоьтикасты?
>

думаю таки же как и синглкасты.

>
>
>
> --
> С уважением,
> Алексей mailto:a.babkin@...
>
>

From forum: openbsd - Russian

Re: ralink слабый сигнал

2009-11-23T13:27:02Z

On Mon, Nov 23, 2009 at 22:03 +0300, Andrey N. Oktyabrski wrote:
> Anton Maksimenkov wrote:
>> Так soekris же. http://www.soekris.com/
>> А net5501 как бы говорит нам, что это net5501... :)
> Кстати, об альтернативах... Заводится ли OpenBSD хоть на чём-то из этого?
> http://routerboard.com/pricelist.php?started_from_home=1
>
> Вроде на сайте написано, что "пока нет", но routerboard'ов много...
>
>

OpenBSD/socppc -current на RB600 должен работать. только не ожидайте
хорошей производительости. это ж SoC всё-таки...

и я не уверен насчет wireless (да и чего угодно другого в miniPCI).
всё никак руки не доходят ral на n1200[1] завести и проверить :)

[1] http://crypt.org.ru/~mkb/pub/thecus/thecus.jpg

From forum: openbsd - Russian

Intel PRO/1000MF (82545GM) Hardware Initialization Failed - 4.6 amd64

2009-11-23T13:26:45Z

Hi All
I have 2 identical machines running 4.6 stable. I have tried removing
some of the other hardware and changing some irq settings in the bios,
but there is not really much to change. Does anyone have any advice on
getting these network cards to work?

-Ben

# dmesg | grep em0
em0 at pci3 dev 2 function 0 "Intel PRO/1000MF (82545GM)" rev 0x04:
apic 3 int 3 (irq 6)em0: Hardware Initialization Failedem0: Unable to
initialize the hardware

# pcidump
Domain /dev/pci0:
0:0:0: Intel 3200/3210 Host
0:1:0: Intel 3200/3210 PCIE
0:28:0: Intel 82801I PCIE
0:28:4: Intel 82801I PCIE
0:28:5: Intel 82801I PCIE
0:29:0: Intel 82801I USB
0:29:1: Intel 82801I USB
0:29:2: Intel 82801I USB
0:29:7: Intel 82801I USB
0:30:0: Intel 82801BA Hub-to-PCI
0:31:0: Intel 82801IR LPC
0:31:2: Intel 82801I SATA
2:0:0: Intel PCIE-PCIE
3:2:0: Intel PRO/1000MF (82545GM)
4:0:0: Broadcom BCM5721
5:0:0: Broadcom BCM5721
6:5:0: ATI ES1000

# dmesg
OpenBSD 4.6-stable (GENERIC.MP) #0: Mon Nov 23 06:04:07 EST 2009
root@...:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3487244288 (3325MB)
avail mem = 3370917888 (3214MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xcff9c000 (46 entries)
bios0: vendor Dell Inc. version "1.4.3" date 05/15/2009
bios0: Dell Inc. PowerEdge R200
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP APIC SPCR HPET MCFG WD__ SLIC ERST HEST BERT
EINJ SSDT SSDT SSDT
acpi0: wakeup devices PCI0(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E3110 @ 3.00GHz, 3000.61 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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,CX16,xTPR,NXE,LONG
cpu0: 6MB 64b/line 16-way L2 cache
cpu0: apic clock running at 333MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Xeon(R) CPU E3110 @ 3.00GHz, 3000.21 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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,CX16,xTPR,NXE,LONG
cpu1: 6MB 64b/line 16-way L2 cache
ioapic0 at mainbus0 apid 2 pa 0xfec00000, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
ioapic1 at mainbus0 apid 3 pa 0xfec10000, version 20, 24 pins
ioapic1: misconfigured as apic 0, remapped to apid 3
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEX1)
acpiprt2 at acpi0: bus 2 (SBE0)
acpiprt3 at acpi0: bus 3 (PXHA)
acpiprt4 at acpi0: bus 4 (SBE4)
acpiprt5 at acpi0: bus 5 (SBE5)
acpiprt6 at acpi0: bus 6 (COMP)
acpicpu0 at acpi0: PSS
acpicpu1 at acpi0: PSS
ipmi at mainbus0 not configured
cpu0: Enhanced SpeedStep 3000 MHz: speeds: 3000, 2667, 2333, 2000 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 3200/3210 Host" rev 0x01
ppb0 at pci0 dev 1 function 0 "Intel 3200/3210 PCIE" rev 0x01: apic 2
int 16 (irq 15)
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x02
pci2 at ppb1 bus 2
ppb2 at pci2 dev 0 function 0 "Intel PCIE-PCIE" rev 0x09
pci3 at ppb2 bus 3
em0 at pci3 dev 2 function 0 "Intel PRO/1000MF (82545GM)" rev 0x04:
apic 3 int 3 (irq 6)em0: Hardware Initialization Failedem0: Unable to
initialize the hardware
ppb3 at pci0 dev 28 function 4 "Intel 82801I PCIE" rev 0x02
pci4 at ppb3 bus 4
bge0 at pci4 dev 0 function 0 "Broadcom BCM5721" rev 0x21, BCM5750 C1
(0x4201): apic 2 int 16 (irq 15), address 00:25:64:3c:72:24
brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
ppb4 at pci0 dev 28 function 5 "Intel 82801I PCIE" rev 0x02
pci5 at ppb4 bus 5
bge1 at pci5 dev 0 function 0 "Broadcom BCM5721" rev 0x21, BCM5750 C1
(0x4201): apic 2 int 17 (irq 14), address 00:25:64:3c:72:25
brgphy1 at bge1 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
uhci0 at pci0 dev 29 function 0 "Intel 82801I USB" rev 0x02: apic 2
int 21 (irq 11)
uhci1 at pci0 dev 29 function 1 "Intel 82801I USB" rev 0x02: apic 2
int 20 (irq 10)
uhci2 at pci0 dev 29 function 2 "Intel 82801I USB" rev 0x02: apic 2
int 21 (irq 11)
ehci0 at pci0 dev 29 function 7 "Intel 82801I USB" rev 0x02: apic 2
int 21 (irq 11)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb5 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0x92
pci6 at ppb5 bus 6
vga1 at pci6 dev 5 function 0 "ATI ES1000" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
radeondrm0 at vga1: apic 2 int 19 (irq 6)
drm0 at radeondrm0
pcib0 at pci0 dev 31 function 0 "Intel 82801IR LPC" rev 0x02
pciide0 at pci0 dev 31 function 2 "Intel 82801I SATA" rev 0x02: DMA,
channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide0: using apic 2 int 23 (irq 14) for native-PCI interrupt
wd0 at pciide0 channel 0 drive 0: <WDC WD1602ABKS-18N8A0>
wd0: 16-sector PIO, LBA48, 152587MB, 312500000 sectors
atapiscsi0 at pciide0 channel 0 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <TSSTcorp, DVD-ROM TS-L333A, D550> ATAPI
5/cdrom removable
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
cd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
wd1 at pciide0 channel 1 drive 0: <WDC WD1602ABKS-18N8A0>
wd1: 16-sector PIO, LBA48, 152587MB, 312500000 sectors
wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
spkr0 at pcppi0
mtrr: Pentium Pro MTRR support
uhub4 at uhub0 port 5 "Cypress Semiconductor USB2 Hub" rev 2.00/0.0b addr 2
uhub5 at uhub4 port 1 "Mitsumi Electric Hub in Apple Extended USB
Keyboard" rev 1.10/1.22 addr 3
uhidev0 at uhub5 port 1 configuration 1 interface 0 "Mitsumi Electric
Apple Extended USB Keyboard" rev 1.10/1.22 addr 4
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 modifier keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub5 port 1 configuration 1 interface 1 "Mitsumi Electric
Apple Extended USB Keyboard" rev 1.10/1.22 addr 4
uhidev1: iclass 3/0, 3 report ids
uhid0 at uhidev1 reportid 2: input=1, output=0, feature=0
uhid1 at uhidev1 reportid 3: input=3, output=0, feature=0
uhidev2 at uhub5 port 2 configuration 1 interface 0 "Primax
Electronics Apple Optical USB Mouse" rev 1.10/1.10 addr 5
uhidev2: iclass 3/1
ums0 at uhidev2: 4 buttons, Z and W dir
wsmouse0 at ums0 mux 0
softraid0 at root
root on wd0a swap on wd0b dump on wd0b

# pcidump -v
Domain /dev/pci0:
0:0:0: Intel 3200/3210 Host
0x0000: Vendor ID: 8086 Product ID: 29f0
0x0004: Command: 0146 Status ID: 2090
0x0008: Class: 06 Subclass: 00 Interface: 00 Revision: 01
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR empty (00000000)
0x0014: BAR empty (00000000)
0x0018: BAR empty (00000000)
0x001c: BAR empty (00000000)
0x0020: BAR empty (00000000)
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 0000 Product ID: 0000
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
0x00e0: Capability 0x09: Vendor Specific
0:1:0: Intel 3200/3210 PCIE
0x0000: Vendor ID: 8086 Product ID: 29f1
0x0004: Command: 0147 Status ID: 0010
0x0008: Class: 06 Subclass: 04 Interface: 00 Revision: 01
0x000c: BIST: 00 Header Type: 01 Latency Timer: 00 Cache Line Size: 10
0x0010: 00000000
0x0014: 00000000
0x0018: Primary Bus: 0 Secondary Bus: 1 Subordinate Bus: 1
Secondary Latency Timer: 00
0x001c: I/O Base: f0 I/O Limit: 00 Secondary Status: 0000
0x0020: Memory Base: fff0 Memory Limit: 0000
0x0024: Prefetch Memory Base: fff1 Prefetch Memory Limit: 0001
0x0028: Prefetch Memory Base Upper 32 Bits: 00000000
0x002c: Prefetch Memory Limit Upper 32 Bits: 00000000
0x0030: I/O Base Upper 16 Bits: 0000 I/O Limit Upper 16 Bits: 0000
0x0038: Expansion ROM Base Address: 00000000
0x003c: Interrupt Pin: 01 Line: 0f Bridge Control: 0007
0x0088: Capability 0x0d: PCI-PCI
0x0080: Capability 0x01: Power Management
0x0090: Capability 0x05: Message Signaled Interrupts (MSI)
0x00a0: Capability 0x10: PCI Express
0:28:0: Intel 82801I PCIE
0x0000: Vendor ID: 8086 Product ID: 2940
0x0004: Command: 0147 Status ID: 0010
0x0008: Class: 06 Subclass: 04 Interface: 00 Revision: 02
0x000c: BIST: 00 Header Type: 81 Latency Timer: 00 Cache Line Size: 10
0x0010: 00000000
0x0014: 00000000
0x0018: Primary Bus: 0 Secondary Bus: 2 Subordinate Bus: 3
Secondary Latency Timer: 00
0x001c: I/O Base: e0 I/O Limit: e0 Secondary Status: 2000
0x0020: Memory Base: dfc0 Memory Limit: dfc0
0x0024: Prefetch Memory Base: fff1 Prefetch Memory Limit: 0001
0x0028: Prefetch Memory Base Upper 32 Bits: 00000000
0x002c: Prefetch Memory Limit Upper 32 Bits: 00000000
0x0030: I/O Base Upper 16 Bits: 0000 I/O Limit Upper 16 Bits: 0000
0x0038: Expansion ROM Base Address: 00000000
0x003c: Interrupt Pin: 01 Line: 0f Bridge Control: 0007
0x0040: Capability 0x10: PCI Express
0x0080: Capability 0x05: Message Signaled Interrupts (MSI)
0x0090: Capability 0x0d: PCI-PCI
0x00a0: Capability 0x01: Power Management
0:28:4: Intel 82801I PCIE
0x0000: Vendor ID: 8086 Product ID: 2948
0x0004: Command: 0147 Status ID: 0010
0x0008: Class: 06 Subclass: 04 Interface: 00 Revision: 02
0x000c: BIST: 00 Header Type: 81 Latency Timer: 00 Cache Line Size: 10
0x0010: 00000000
0x0014: 00000000
0x0018: Primary Bus: 0 Secondary Bus: 4 Subordinate Bus: 4
Secondary Latency Timer: 00
0x001c: I/O Base: f0 I/O Limit: 00 Secondary Status: 0000
0x0020: Memory Base: dfd0 Memory Limit: dfd0
0x0024: Prefetch Memory Base: fff1 Prefetch Memory Limit: 0001
0x0028: Prefetch Memory Base Upper 32 Bits: 00000000
0x002c: Prefetch Memory Limit Upper 32 Bits: 00000000
0x0030: I/O Base Upper 16 Bits: 0000 I/O Limit Upper 16 Bits: 0000
0x0038: Expansion ROM Base Address: 00000000
0x003c: Interrupt Pin: 01 Line: 0f Bridge Control: 0007
0x0040: Capability 0x10: PCI Express
0x0080: Capability 0x05: Message Signaled Interrupts (MSI)
0x0090: Capability 0x0d: PCI-PCI
0x00a0: Capability 0x01: Power Management
0:28:5: Intel 82801I PCIE
0x0000: Vendor ID: 8086 Product ID: 294a
0x0004: Command: 0147 Status ID: 0010
0x0008: Class: 06 Subclass: 04 Interface: 00 Revision: 02
0x000c: BIST: 00 Header Type: 81 Latency Timer: 00 Cache Line Size: 10
0x0010: 00000000
0x0014: 00000000
0x0018: Primary Bus: 0 Secondary Bus: 5 Subordinate Bus: 5
Secondary Latency Timer: 00
0x001c: I/O Base: f0 I/O Limit: 00 Secondary Status: 0000
0x0020: Memory Base: dfe0 Memory Limit: dfe0
0x0024: Prefetch Memory Base: fff1 Prefetch Memory Limit: 0001
0x0028: Prefetch Memory Base Upper 32 Bits: 00000000
0x002c: Prefetch Memory Limit Upper 32 Bits: 00000000
0x0030: I/O Base Upper 16 Bits: 0000 I/O Limit Upper 16 Bits: 0000
0x0038: Expansion ROM Base Address: 00000000
0x003c: Interrupt Pin: 02 Line: 0e Bridge Control: 0007
0x0040: Capability 0x10: PCI Express
0x0080: Capability 0x05: Message Signaled Interrupts (MSI)
0x0090: Capability 0x0d: PCI-PCI
0x00a0: Capability 0x01: Power Management
0:29:0: Intel 82801I USB
0x0000: Vendor ID: 8086 Product ID: 2934
0x0004: Command: 0005 Status ID: 0290
0x0008: Class: 0c Subclass: 03 Interface: 00 Revision: 02
0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR empty (00000000)
0x0014: BAR empty (00000000)
0x0018: BAR empty (00000000)
0x001c: BAR empty (00000000)
0x0020: BAR io addr: 0x0000cc60
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 1028 Product ID: 023c
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00
0x0050: Capability 0x13: Reserved
0:29:1: Intel 82801I USB
0x0000: Vendor ID: 8086 Product ID: 2935
0x0004: Command: 0005 Status ID: 0290
0x0008: Class: 0c Subclass: 03 Interface: 00 Revision: 02
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR empty (00000000)
0x0014: BAR empty (00000000)
0x0018: BAR empty (00000000)
0x001c: BAR empty (00000000)
0x0020: BAR io addr: 0x0000cc80
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 1028 Product ID: 023c
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 02 Line: 0a Min Gnt: 00 Max Lat: 00
0x0050: Capability 0x13: Reserved
0:29:2: Intel 82801I USB
0x0000: Vendor ID: 8086 Product ID: 2936
0x0004: Command: 0005 Status ID: 0290
0x0008: Class: 0c Subclass: 03 Interface: 00 Revision: 02
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR empty (00000000)
0x0014: BAR empty (00000000)
0x0018: BAR empty (00000000)
0x001c: BAR empty (00000000)
0x0020: BAR io addr: 0x0000cca0
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 1028 Product ID: 023c
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 03 Line: 0b Min Gnt: 00 Max Lat: 00
0x0050: Capability 0x13: Reserved
0:29:7: Intel 82801I USB
0x0000: Vendor ID: 8086 Product ID: 293a
0x0004: Command: 0146 Status ID: 0290
0x0008: Class: 0c Subclass: 03 Interface: 20 Revision: 02
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR mem 32bit addr: 0xdfbffc00
0x0014: BAR empty (00000000)
0x0018: BAR empty (00000000)
0x001c: BAR empty (00000000)
0x0020: BAR empty (00000000)
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 1028 Product ID: 023c
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00
0x0050: Capability 0x01: Power Management
0x0058: Capability 0x0a: Debug Port
0x0098: Capability 0x13: Reserved
0:30:0: Intel 82801BA Hub-to-PCI
0x0000: Vendor ID: 8086 Product ID: 244e
0x0004: Command: 0147 Status ID: 0010
0x0008: Class: 06 Subclass: 04 Interface: 01 Revision: 92
0x000c: BIST: 00 Header Type: 01 Latency Timer: 00 Cache Line Size: 00
0x0010: 00000000
0x0014: 00000000
0x0018: Primary Bus: 0 Secondary Bus: 6 Subordinate Bus: 6
Secondary Latency Timer: 20
0x001c: I/O Base: d0 I/O Limit: d0 Secondary Status: 2280
0x0020: Memory Base: dff0 Memory Limit: dff0
0x0024: Prefetch Memory Base: d001 Prefetch Memory Limit: d7f1
0x0028: Prefetch Memory Base Upper 32 Bits: 00000000
0x002c: Prefetch Memory Limit Upper 32 Bits: 00000000
0x0030: I/O Base Upper 16 Bits: 0000 I/O Limit Upper 16 Bits: 0000
0x0038: Expansion ROM Base Address: 00000000
0x003c: Interrupt Pin: 00 Line: ff Bridge Control: 000b
0x0050: Capability 0x0d: PCI-PCI
0:31:0: Intel 82801IR LPC
0x0000: Vendor ID: 8086 Product ID: 2916
0x0004: Command: 0147 Status ID: 0210
0x0008: Class: 06 Subclass: 01 Interface: 00 Revision: 02
0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR empty (00000000)
0x0014: BAR empty (00000000)
0x0018: BAR empty (00000000)
0x001c: BAR empty (00000000)
0x0020: BAR empty (00000000)
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 0000 Product ID: 0000
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
0x00e0: Capability 0x09: Vendor Specific
0:31:2: Intel 82801I SATA
0x0000: Vendor ID: 8086 Product ID: 2920
0x0004: Command: 0047 Status ID: 02b0
0x0008: Class: 01 Subclass: 01 Interface: 8f Revision: 02
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR io addr: 0x0000cc30
0x0014: BAR io addr: 0x0000cc28
0x0018: BAR io addr: 0x0000cc38
0x001c: BAR io addr: 0x0000cc2c
0x0020: BAR io addr: 0x0000cc40
0x0024: BAR io addr: 0x0000cc50
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 1028 Product ID: 023c
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 03 Line: 0e Min Gnt: 00 Max Lat: 00
0x0070: Capability 0x01: Power Management
0x00b0: Capability 0x13: Reserved
2:0:0: Intel PCIE-PCIE
0x0000: Vendor ID: 8086 Product ID: 032c
0x0004: Command: 0147 Status ID: 0010
0x0008: Class: 06 Subclass: 04 Interface: 00 Revision: 09
0x000c: BIST: 00 Header Type: 81 Latency Timer: 00 Cache Line Size: 10
0x0010: 00000000
0x0014: 00000000
0x0018: Primary Bus: 2 Secondary Bus: 3 Subordinate Bus: 3
Secondary Latency Timer: 40
0x001c: I/O Base: e0 I/O Limit: e0 Secondary Status: 22a0
0x0020: Memory Base: dfc0 Memory Limit: dfc0
0x0024: Prefetch Memory Base: fff1 Prefetch Memory Limit: 0001
0x0028: Prefetch Memory Base Upper 32 Bits: 00000000
0x002c: Prefetch Memory Limit Upper 32 Bits: 00000000
0x0030: I/O Base Upper 16 Bits: 0000 I/O Limit Upper 16 Bits: 0000
0x0038: Expansion ROM Base Address: 00000000
0x003c: Interrupt Pin: 00 Line: 00 Bridge Control: 0007
0x0044: Capability 0x10: PCI Express
0x005c: Capability 0x05: Message Signaled Interrupts (MSI)
0x006c: Capability 0x01: Power Management
0x00d8: Capability 0x07: PCI-X
3:2:0: Intel PRO/1000MF (82545GM)
0x0000: Vendor ID: 8086 Product ID: 1027
0x0004: Command: 0157 Status ID: 0230
0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 04
0x000c: BIST: 00 Header Type: 00 Latency Timer: 40 Cache Line Size: 10
0x0010: BAR mem 64bit addr: 0x00000000dfca0000
0x0018: BAR mem 64bit addr: 0x00000000dfcc0000
0x0020: BAR io addr: 0x0000ecc0
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 8086 Product ID: 1002
0x0030: Expansion ROM Base Address: dfc00000
0x0038: 00000000
0x003c: Interrupt Pin: 01 Line: 06 Min Gnt: ff Max Lat: 00
0x00dc: Capability 0x01: Power Management
0x00e4: Capability 0x07: PCI-X
0x00f0: Capability 0x05: Message Signaled Interrupts (MSI)
4:0:0: Broadcom BCM5721
0x0000: Vendor ID: 14e4 Product ID: 1659
0x0004: Command: 0146 Status ID: 0010
0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 21
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 10
0x0010: BAR mem 64bit addr: 0x00000000dfdf0000
0x0018: BAR empty (00000000)
0x001c: BAR empty (00000000)
0x0020: BAR empty (00000000)
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 1028 Product ID: 023c
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 01 Line: 0f Min Gnt: 00 Max Lat: 00
0x0048: Capability 0x01: Power Management
0x0050: Capability 0x03: Vital Product Data (VPD)
0x0058: Capability 0x05: Message Signaled Interrupts (MSI)
0x00d0: Capability 0x10: PCI Express
5:0:0: Broadcom BCM5721
0x0000: Vendor ID: 14e4 Product ID: 1659
0x0004: Command: 0146 Status ID: 0010
0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 21
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 10
0x0010: BAR mem 64bit addr: 0x00000000dfef0000
0x0018: BAR empty (00000000)
0x001c: BAR empty (00000000)
0x0020: BAR empty (00000000)
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 1028 Product ID: 023c
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 01 Line: 0e Min Gnt: 00 Max Lat: 00
0x0048: Capability 0x01: Power Management
0x0050: Capability 0x03: Vital Product Data (VPD)
0x0058: Capability 0x05: Message Signaled Interrupts (MSI)
0x00d0: Capability 0x10: PCI Express
6:5:0: ATI ES1000
0x0000: Vendor ID: 1002 Product ID: 515e
0x0004: Command: 0187 Status ID: 0290
0x0008: Class: 03 Subclass: 00 Interface: 00 Revision: 02
0x000c: BIST: 00 Header Type: 00 Latency Timer: 20 Cache Line Size: 10
0x0010: BAR mem prefetchable 32bit addr: 0xd0000000
0x0014: BAR io addr: 0x0000dc00
0x0018: BAR mem 32bit addr: 0xdfff0000
0x001c: BAR empty (00000000)
0x0020: BAR empty (00000000)
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 1028 Product ID: 023c
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 01 Line: 06 Min Gnt: 08 Max Lat: 00
0x0050: Capability 0x01: Power Management

From forum: openbsd user - misc

Escuela Sistemica 2010

2009-11-23T13:02:24Z

[IMAGE]

Director General: Dr. Horacio Serebrinsky

Vicedirector: Dr. Marcelo R. Ceberio

La Escuela Sistimica Argentina es una institucisn que desarrolla
actividades de formacisn de Terapeutas familiares sistimicos,
investigacisn y asistencia psicolsgica.

Abierta la Inscripcisn

Inicio de actividades: Marzo 2010

REUNISN INFORMATIVA: 26 de noviembre, 20 hs.

Consulte por entrevistas personalizadas

POSTGRADO EN EL MODELO SISTIMICO:

E.S.A. desarrolla un Postgrado de alta excelencia acadimica centrado en
el modelo sistimico. En pos de este objetivo, diseqa un programa que
integra teorma y practica y que permite potenciar la creatividad de la
psicoterapia y otros contextos.

Duracisn: 3 msdulos anuales dictados en 2 o 3 aqos

Modalidades de cursada:

7 Regular con frecuencia semanal (2 o 3 aqos) - Inicio: 31 de marzo 2010

7 Intensivo con frecuencia mensual (2 aqos) - Inicio: 09 de abril 2010

7 1er msdulo: Miircoles de 13 a 15.30 o de 19 a 21.30 hs. - Inicio: 31 de
marzo

7 2do msdulo: Lunes de 13 a 15.30 o de 19 a 21.30 hs. - Inicio: 29 de
marzo

7 3er msdulo: Jueves de 13 a 15.30 o de 19 a 21.30 hs. - Inicio: 25 de
marzo

POSTGRADO EN MANAGEMENT SISTIMICO. El pensamiento sistimico en las
organizaciones:

Duracisn: 2 aqos de 16 msdulos: 64 encuentros de dos horas semanales y 16
jornadas de "Open Cases".

Inicio: 05 y 06 de abril 2010

7 1er aqo: Lunes de 19 a 21 hs

7 2do aqo: Martes de 19 a 20 hs

POSTGRADO EN EL TRATAMIENTO DE LAS ADICCIONES DESDE EL MODELO SISTIMICO:

Duracisn: 2 aqos distribuidos en dos cuatrimestres de 16 clases cada uno.

Frecuencia: una vez a la semana 2hs.

Clases tesricas articuladas con casos clmnicos. Pasantmas en diversas
comunidades terapiuticas.

Inicio: 06 de abril 2010

7 1er aqo: Martes de 11 a 13 hs.

7 2do aqo: Martes de 9 a 11 hs.

Cursos de especializacisn (anuales y cuatrimestrales):

7 Psicoterapia infantil con enfoque familiar: Duracisn: Anual.

7 Terapia de pareja: Duracisn: Cuatrimestral.

7 Especializacisn en terapeutas de grupo: Duracisn: Anual.

7 Trastornos de la alimentacisn: Duracisn: 2 cuatrimestres.

7 Psicodiagnsstico: Duracisn: Anual

7 Violencia familiar

7 Trastornos de ansiedad

Cursos mensuales:

7 Acompaqamiento terapiutico, Introduccisn a la terapia sexual, Familias
ensambladas, Hipnosis ericksoniana, Depresisn, Adopcisn, Operadores
Socio-Terapiuticos y Mediacisn entre otros.

SOLICITE PROGRAMAS

Ateneos abiertos al pzblico en general.

CONSULTE POR NUESTRAS ACTIVIDADES EN

SANTA FE, CSRDOBA Y BOLIVIA

DEPARTAMENTO DE ASISTENCIA El equipo profesional de E.S.A realiza
tratamientos terapiuticos individuales, pareja, familia y grupo, en
diferentes trastornos (alimentarios, panico, obsesivos, adicciones,
psicosis. jugadores compulsivos, etc.), psicodiagnssticos, orientacisn
vocacional.

------------------------------------------------------------------------

INFORMES E INSCRIPCISN:

Fray Justo S. M. de Oro 1843 (C1414DBC) Cap. Fed.
Te/Fax: 4774-2875/6112 4899-1053
info@... / www.escuelasistemica.com.ar

[demime 1.01d removed an attachment of type image/jpeg which had a name of banner2.jpg]

From forum: openbsd user - misc

GOOD. DAY

2009-11-23T12:44:42Z

You are invited to "GOOD. DAY".

By your host Isaka Bello:

Date: Monday November 23, 2009

Time: 8:30 pm - 9:30 pm (GMT +00:00)
Street: My Dear, My name is Mr.isaka Bello I am the Credit and audits manager with bank of Africa. (BOA) bank of Africa in Ouagadougou Burkina Faso West Africa. I have a business proposal in the tune of $11.6m, (Eleven Million six Hundred Thousand United Statse Dollar only) after the successful transfer;We will share in ratio of 40% for you and 60% for me. and you be interested,So we can commence all arrangements? And I will Give you more information on how we would handle This project. Please treat this business with utmost Confidentiality and send me the Following information's bellow to enable us commence immediately: (1) Full names: (2) Private phone number: (3) Current residential address: (4) Occupation: (5) Age and Sex: Best Regards, Mr.isaka Bello

Will you attend? RSVP to this invitation at:

http://calendar.yahoo.com/isaka_bello13?v=126&a1=0&iid=GxIUH0x%40DKs5%40FR4Xhi3ddl%404ptD%40eRGphAgIx%40%40&igid=shaEjNlbvJrz%40HiYDxp5Ypd%40V%40aEaa3TRxdWB-n%40Vgv%40

Copyright ) 2009 All Rights Reserved
www.yahoo.com

Privacy Policy:
http://privacy.yahoo.com/privacy/us

Terms of Service:
http://docs.yahoo.com/info/terms/

From forum: openbsd user - misc

Re: phrase 'log rotation' in newsyslog.8

2009-11-23T12:15:30Z

Jason McIntyre wrote:

> hmm. it can compress logs too - should we stick that in? (i'm joking)
> the point is to make it sane. so the question is still is there a
> difference between trimming logs and rotating them? and, if there is, is
> it a distinction that a manual page description needs to make?

rotatelogs(8) is also included in base and uses the term 'rotate'. In
both rotatelogs(8) and newsystlog(8), the log, as whole file, slides
down a fifo queue on its way to the bitbucket.

I always previously heard that process referred to as 'rotate' and was
using that as the search term via apropos in my hunt for
newsyslog.conf(8) Due to the simplicity of apropos the words to index
the man page on must be in the title whether trim, rotate or both at the
same time. I propose the new title because that is the word I was
searching for.

/Lars

From forum: openbsd dev - tech

Re: phrase 'log rotation' in newsyslog.8

2009-11-23T12:01:56Z

On Mon, Nov 23, 2009 at 11:55:01AM -0800, Matthew Dempsky wrote:

> On Mon, Nov 23, 2009 at 11:11 AM, Jason McIntyre <jmc@...> wrote:
> > anyone else want to chip in?
>
> I think "rotate log files" is sufficiently clear. I think that's
> jargon that most sysadmins would understand, and it's also probably
> the first thing people would search for.
>
> I'm not a fan of describing it as "trimming", because the files
> themselves are never trimmed (i.e., truncate(2)), but I can understand
> the use.
>
> I think any text mentioning that it's to maintain a reasonable size is
> redundant; that seems like a pretty basic feature that you'd assume of
> any real log rotation system.
>
> Just my 2c.

these are pretty much my thoughts. so unless anyone comes up with a
compelling reason not to, i'll change it to "rotate log files".

jmc

From forum: openbsd dev - tech

Re: phrase 'log rotation' in newsyslog.8

2009-11-23T11:55:01Z

On Mon, Nov 23, 2009 at 11:11 AM, Jason McIntyre <jmc@...> wrote:
> anyone else want to chip in?

I think "rotate log files" is sufficiently clear. I think that's
jargon that most sysadmins would understand, and it's also probably
the first thing people would search for.

I'm not a fan of describing it as "trimming", because the files
themselves are never trimmed (i.e., truncate(2)), but I can understand
the use.

I think any text mentioning that it's to maintain a reasonable size is
redundant; that seems like a pretty basic feature that you'd assume of
any real log rotation system.

Just my 2c.

From forum: openbsd dev - tech

Re: phrase 'log rotation' in newsyslog.8

2009-11-23T11:49:15Z

On Mon, Nov 23, 2009 at 08:27:45PM +0100, Robert wrote:

> >
> > i wonder what the difference between "trim" and "rotate" is, in this
> > context. and whether it's a point we need to make anyway.
> >
> > it could be we can get away with just "rotate log files", but i'm not
> > sure. (what if someone is looking for an app that archives log files,
> > for example, instead of one that rotates/trims them.)
> >
> > anyone else want to chip in?
> > jmc
>
>
> rotate, archive and/or trim logfiles
>
> - Robert

hmm. it can compress logs too - should we stick that in? (i'm joking)
the point is to make it sane. so the question is still is there a
difference between trimming logs and rotating them? and, if there is, is
it a distinction that a manual page description needs to make?

jmc

From forum: openbsd dev - tech

Re: merge some gstreamer plugins

2009-11-23T11:37:22Z

On Mon, Nov 23, 2009 at 06:16:34PM +0100, Antoine Jacoutot wrote:

> On Mon, 23 Nov 2009, Mikolaj Kucharski wrote:
> > Could someone try to make PLIST changes to gstreamer-plugins-* after the
> > merge to resolve conflict mentioned above in this email. I cannot find
> > where I'm wrong with my diff. TIA.
> >
> > http://marc.info/?l=openbsd-ports&m=125866602429263&q=p3
>
> I am in the progress of updating all gstreamers components to their
> latest release. This is a lot of work and I already have a giant diff,
> so I'm not going to add to it for now.
> Once the update is in, the thing to try will be to update from 4.6 pkg
> to current, see how it goes and fix from there.
>
> For now, I'm already to deep into the mess...

Alright, thanks for update. I will prepare 4.6-stable then.

--
best regards
q#

From forum: openbsd user - ports

Re: phrase 'log rotation' in newsyslog.8

2009-11-23T11:27:45Z

On Mon, 23 Nov 2009 19:12:46 +0001
Jason McIntyre <jmc@...> wrote:

> On Mon, Nov 23, 2009 at 02:16:22PM +0200, lars wrote:
> > Thanks. The change can be smaller then.
> >
> > /Lars
> >
> > On Mon, 23 Nov 2009, Stuart Henderson wrote:
> > >...apropos(1) only searches titles ...
> >
> >
> > $ cvs diff -uNp newsyslog.8
> > Index: newsyslog.8
> > ===================================================================
> > RCS file: /cvs/src/usr.bin/newsyslog/newsyslog.8,v
> > retrieving revision 1.44
> > diff -u -p -r1.44 newsyslog.8
> > --- newsyslog.8 31 May 2007 19:20:13 -0000 1.44
> > +++ newsyslog.8 23 Nov 2009 12:16:23 -0000
> > @@ -46,7 +46,7 @@
> > .Os
> > .Sh NAME
> > .Nm newsyslog
> > -.Nd trim log files to manageable sizes
> > +.Nd rotate log files and trim them to manageable sizes
> > .Sh SYNOPSIS
> > .Nm newsyslog
> > .Op Fl Fmnrv
>
> i wonder what the difference between "trim" and "rotate" is, in this
> context. and whether it's a point we need to make anyway.
>
> it could be we can get away with just "rotate log files", but i'm not
> sure. (what if someone is looking for an app that archives log files,
> for example, instead of one that rotates/trims them.)
>
> anyone else want to chip in?
> jmc

rotate, archive and/or trim logfiles

- Robert

From forum: openbsd dev - tech