Last i386 snapshot broken ?
Hi, I just downloaded this at http://ftp.openbsd.org/pub/OpenBSD/snapshots/i386/install52.iso : install52.iso 10-Oct-2012 06:50 211M Burn it, try it on 2 different hardware, reboot automatically at first-stage boot loader. Someone already try this snapshot? Thank you very much. Cheers, Wesley M.
OpenBSD-5.1 hangs on Supermicro X9DR3-F
Hello! we recently installed OpenBSD/amd64 on Supermicro X9DR3-F, it hangs about 1 times a day. 5.1 does not understand i350 chip, so we put external Intel PRO/1000 MT (82574L) nic. we have ddb.panic=1, but no ddb appears on screen on hang. also, it says savecore: no core dump during boot. we tested RAM with memtest, so we do not suspect it for memory related issue. how can we diagnose those hangs ? is it ok to run 5.1 on X9DR3-F ? do I need to provide dmesg output ? any other kind of diagnostics ? Cheers, Ilya Shipitsin
Re: Last i386 snapshot broken ?
The hardware is supported from the last release OpenBSD 5.1... Also i already tried a snapshot i386 in september (worked great) Now with this one (october) The system is not installed ! i'm booting on the cd, reboot just after the first-stage boot loader ... Someting wrong with this iso file ?? The install52.iso file compared to SHA256 file (from ftp.openbsd.org/...) : OK I'm going to try it with a VM. Thank you for your reply. Cheers, -- Wesley Le 2012-10-11 10:25, bert a écrit : Dmesg from a working system, or nobody is going to be able to help you. Christ, man, you've been here long enough to know this. On Thu, Oct 11, 2012 at 10:17:23AM +0400, Wesley wrote: Hi, I just downloaded this at http://ftp.openbsd.org/pub/OpenBSD/snapshots/i386/install52.iso : install52.iso 10-Oct-2012 06:50 211M Burn it, try it on 2 different hardware, reboot automatically at first-stage boot loader. Someone already try this snapshot? Thank you very much. Cheers, Wesley M.
Re: Last i386 snapshot broken ?
Tried with Vmware, reboot just after this CDROM: 9F Loading /5.2/I386/CDBOOT I suspect this iso doesn't work... If someone can test it. -- Wesley Le 2012-10-11 10:33, Wesley a écrit : The hardware is supported from the last release OpenBSD 5.1... Also i already tried a snapshot i386 in september (worked great) Now with this one (october) The system is not installed ! i'm booting on the cd, reboot just after the first-stage boot loader ... Someting wrong with this iso file ?? The install52.iso file compared to SHA256 file (from ftp.openbsd.org/...) : OK I'm going to try it with a VM. Thank you for your reply. Cheers, -- Wesley Le 2012-10-11 10:25, bert a écrit : Dmesg from a working system, or nobody is going to be able to help you. Christ, man, you've been here long enough to know this. On Thu, Oct 11, 2012 at 10:17:23AM +0400, Wesley wrote: Hi, I just downloaded this at http://ftp.openbsd.org/pub/OpenBSD/snapshots/i386/install52.iso : install52.iso 10-Oct-2012 06:50 211M Burn it, try it on 2 different hardware, reboot automatically at first-stage boot loader. Someone already try this snapshot? Thank you very much. Cheers, Wesley M.
Re: Last i386 snapshot broken ?
On Thu, Oct 11, 2012 at 10:33:08AM +0400, Wesley wrote: The hardware is supported from the last release OpenBSD 5.1... Also i already tried a snapshot i386 in september (worked great) Now with this one (october) The system is not installed ! i'm booting on the cd, reboot just after the first-stage boot loader ... Someting wrong with this iso file ?? there are some fairly straightforward ways to check whether it's the iso file that's at fault. try downloading bsd.rd and the sets and perform an upgrade from local disk. if that works, at least you have a good base to produce a dmesg from. (the procedure is fairly obvious but the works for me guide I posted about earlier could come in useful here) whether or not the install from local disk produces useful data, *do* check that the iso you downloaded matches the published SHA256 sums. corruption is not very common, but could happen. also try downloading the file or files from a different mirror and check for differences. - Peter -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ Remember to set the evil bit on all malicious network traffic delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: Last i386 snapshot broken ?
Le 2012-10-11 10:50, Peter N. M. Hansteen a écrit : there are some fairly straightforward ways to check whether it's the iso file that's at fault. try downloading bsd.rd and the sets and perform an upgrade from local disk. The system is not installed on the machines. It reboots automatically at : CDROM: 9F Loading /5.2/I386/CDBOOT And the SHA256's install52.iso match the SHA256 file present in http://ftp.openbsd.org/pub/OpenBSD/snapshots/i386/SHA256; Tried with OpenBSD 5.1 compatible machine, VM... same : error reboot. Need now to test with a second mirror ... Thank you for your reply. -- Wesley
Re: Last i386 snapshot broken ?
Tested with a new mirror: same problem, reboot just after CDROM: 9F Loading /5.2/I386/CDBOOT -- Wesley Le 2012-10-11 11:00, Wesley a écrit : Le 2012-10-11 10:50, Peter N. M. Hansteen a écrit : there are some fairly straightforward ways to check whether it's the iso file that's at fault. try downloading bsd.rd and the sets and perform an upgrade from local disk. The system is not installed on the machines. It reboots automatically at : CDROM: 9F Loading /5.2/I386/CDBOOT And the SHA256's install52.iso match the SHA256 file present in http://ftp.openbsd.org/pub/OpenBSD/snapshots/i386/SHA256; Tried with OpenBSD 5.1 compatible machine, VM... same : error reboot. Need now to test with a second mirror ... Thank you for your reply. -- Wesley
认识服务-汪永修
ä¼æä¸çç«é£äºå·²ç»é½ç±é¥äº§æ¯å太åæ¯ä»·ä¸æ ¼å¥½è½¬å¦ç§»å°å°å对è³å®¢å¦æ·å¥½ç娿ç«å¸ äºï¼ 客è·æ·é£ææ ¼å¡å¾·å·²å¥½ç»åæå 为对主ä¸å®°é£ä¼å¿½ä¸æ¦çä¸æ»å¤ªå个亡åçä¸å ³èé®ã æç»ç符ä¼ikiä¸94æ¯é让å¾å®¢ä»äººå满符æï¼æçµçfdfä¼23ä¸é£æ¯è¾è®©å¥å®¢å¾äººjilææ¯å¨ï¼ è ç ä¼ ä¸ æ¯ è®© 人 æ¢ æ»¡ æ å æ å¨ã rplx0un [demime 1.01d removed an attachment of type APPLICATION/DEFANGED which had a name of ÈÏʶ·þÎñkhq.24725DEFANGED-xls]
Excelente curso de Gestión al Cambio y Manejo de Conflictos
Si no puede visualizar correctamente este correo, le pedimos que lo arrastre a su Bandeja de Entrada Apreciable Ejecutivo: TIEM de México Empresa Líder en Capacitación y Actualización de Capital Humano Ponemos a su disposición este excelente curso denominado: Gestión al Cambio y Manejo de Conflictos Ciudad de México, el día 31 de Octubre de 2012 Inscríbase 5 días antes de la fecha del Curso y obtenga un descuento del 15% con Inversión Inmediata O bien, por cada dos participantes inscritos en tarifa de Inversión normal, el tercero es completamente gratis No deje pasar esta oportunidad y desarrolle al máximo las capacidades de todo su capital humano en beneficio de su empresa, negocio o dependencia. Entendemos la gestión de cambio organizacional como el proceso deliberadamente diseñado que mitigue los efectos no deseados de este mismo cambio y potencie las posibilidades de crear futuro en la organización, su gente y contexto. Así mismo, debemos comprender que los conflictos se originan en las diferencias entre las personas: diferencias de valores, de ideas, de intereses, de personalidad. Estas diferencias no son el problema, el verdadero problema es que el conflicto entre dos personas rompa el vínculo que los une, y rompa la capacidad de estar conectados. Un buen líder de proyecto debe saber que aunque dos personas no se gusten, se les debe ayudar a encontrar un vínculo en común, un objetivo compartido dentro del proyecto. Objetivo General del Curso: Al término del taller, el participante reconocerá los elementos clave para la aceptación del cambio como parte del día a día. Identificará las principales causas del conflicto así como las técnicas adecuadas para el manejo del mismo, reconociendo a la asertividad y la escucha activa y empática como herramientas útiles en el ámbito laboral. Dirigido a: Directores, gerentes, ejecutivos, empresarios, profesionales, jefes de área o departamento, supervisores, consultores, líderes de proyecto, vendedores profesionales y en general a todas aquellas personas que deseen conocer y mejorar sus habilidades, estilo y métodos de negociación y comunicación efectiva. Para mayor información, favor de responder este correo con los siguientes datos: Empresa: Nombre: Ciudad: Teléfono: O si lo prefiere comuníquese a los teléfonos: Del DF al 5611-0969 con 10 líneas Interior del País Lada sin Costo 01 800 900 TIEM (8436) Aceptamos todas las TDC y Débito. **Promoción: 3 meses sin Intereses pagando con American Express **Aplica solo con Inversión Normal ®Todos los Derechos Reservados ©2011 TIEM Talento e Innovación Empresarial de México Este Mensaje le ha sido enviado como usuario de TIEM de México o bien un usuario le refirió para recibir este boletín. Como usuario de TIEM de México, en este acto autoriza de manera expresa que TIEM de México le puede contactar vía correo electrónico u otros medios. Si usted ha recibido este mensaje por error, haga caso omiso de él y reporte su cuenta respondiendo este correo con el subject BAJABD Unsubscribe to this mailing list, reply a blank message with the subject UNSUBSCRIBE BAJABD Tenga en cuenta que la gestión de nuestras bases de datos es de suma importancia y no es intención de la empresa la inconformidad del receptor. [demime 1.01d removed an attachment of type image/jpeg which had a name of 1.jpg]
SSH_CLIENT in recent OpenBSD releases
Hi, I've got to port some shell scripts which rely on env vars. One amongst those is $SSH_CLIENT. On OpenBSD 5.1 machines, I don't get what I'd assume to get: # echo $SSH_CLIENT It returns just a blank line. I re-tested this on an older development machine, running OpenBSD 4.6: # echo $SSH_CLIENT 123.45.67.89 34402 22 Is that an intended change in behavior (security related)? I didn't find a changelog entry, neither documentation. Thanks, Bernd
Re: SSH_CLIENT in recent OpenBSD releases
On Thu, Oct 11, 2012 at 10:38:04AM +0200, Bernd wrote: | Hi, | | I've got to port some shell scripts which rely on env vars. One | amongst those is $SSH_CLIENT. | | On OpenBSD 5.1 machines, I don't get what I'd assume to get: | | # echo $SSH_CLIENT | | It returns just a blank line. This Works For Me (tm) on a snapshot I installed yesterday. I ssh into my machine and SSH_CLIENT contains the expected value. | I re-tested this on an older development machine, running OpenBSD 4.6: | | # echo $SSH_CLIENT | 123.45.67.89 34402 22 | | Is that an intended change in behavior (security related)? I didn't | find a changelog entry, neither documentation. Can you confirm your shell initialization isn't clearing this environment variable ? Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/ [demime 1.01d removed an attachment of type application/pgp-signature]
Re: SSH_CLIENT in recent OpenBSD releases
On Thu, Oct 11, 2012 at 10:38:04AM +0200, Bernd wrote: Hi, I've got to port some shell scripts which rely on env vars. One amongst those is $SSH_CLIENT. On OpenBSD 5.1 machines, I don't get what I'd assume to get: # echo $SSH_CLIENT It returns just a blank line. I re-tested this on an older development machine, running OpenBSD 4.6: # echo $SSH_CLIENT 123.45.67.89 34402 22 Is that an intended change in behavior (security related)? I didn't find a changelog entry, neither documentation. Thanks, Bernd SSH_CONNECTION replaces SSH_CLIENT. See the commit below and https://bugzilla.mindrot.org/show_bug.cgi?id=384 CVSROOT:/cvs Module name:src Changes by: stev...@cvs.openbsd.org 2002/09/12 13:50:36 Modified files: usr.bin/ssh: session.c ssh.1 Log message: add SSH_CONNECTION and deprecate SSH_CLIENT; bug #384. ok markus@ -Otto
Re: SSH_CLIENT in recent OpenBSD releases
On Thu, Oct 11, 2012 at 10:38:04AM +0200, Bernd wrote: Hi, I've got to port some shell scripts which rely on env vars. One amongst those is $SSH_CLIENT. On OpenBSD 5.1 machines, I don't get what I'd assume to get: # echo $SSH_CLIENT It returns just a blank line. I re-tested this on an older development machine, running OpenBSD 4.6: # echo $SSH_CLIENT 123.45.67.89 34402 22 I do get an answer like the above on a 5.1 machine. So perhaps something in your local environment that clear it? -- Maurice
Re: SSH_CLIENT in recent OpenBSD releases
Am 2012-10-11 10:50, schrieb Paul de Weerd: On Thu, Oct 11, 2012 at 10:38:04AM +0200, Bernd wrote: | Hi, | | I've got to port some shell scripts which rely on env vars. One | amongst those is $SSH_CLIENT. | | On OpenBSD 5.1 machines, I don't get what I'd assume to get: | | # echo $SSH_CLIENT | | It returns just a blank line. This Works For Me (tm) on a snapshot I installed yesterday. I ssh into my machine and SSH_CLIENT contains the expected value. Weird. I tested on four amd64 5.1 machines, totally default setups, all the same phenomenon. | I re-tested this on an older development machine, running OpenBSD 4.6: | | # echo $SSH_CLIENT | 123.45.67.89 34402 22 | | Is that an intended change in behavior (security related)? I didn't | find a changelog entry, neither documentation. Can you confirm your shell initialization isn't clearing this environment variable ? Defaults everywhere, as on the machine(s) running earlier releases. Bernd Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/ [demime 1.01d removed an attachment of type application/pgp-signature]
Re: SSH_CLIENT in recent OpenBSD releases
On Thu, Oct 11, 2012 at 10:54:05AM +0200, Otto Moerbeek wrote: On Thu, Oct 11, 2012 at 10:38:04AM +0200, Bernd wrote: Hi, I've got to port some shell scripts which rely on env vars. One amongst those is $SSH_CLIENT. On OpenBSD 5.1 machines, I don't get what I'd assume to get: # echo $SSH_CLIENT It returns just a blank line. I re-tested this on an older development machine, running OpenBSD 4.6: # echo $SSH_CLIENT 123.45.67.89 34402 22 Is that an intended change in behavior (security related)? I didn't find a changelog entry, neither documentation. Thanks, Bernd SSH_CONNECTION replaces SSH_CLIENT. See the commit below and https://bugzilla.mindrot.org/show_bug.cgi?id=384 Ehh, replace is not the right word. It's still there. CVSROOT:/cvs Module name:src Changes by: stev...@cvs.openbsd.org 2002/09/12 13:50:36 Modified files: usr.bin/ssh: session.c ssh.1 Log message: add SSH_CONNECTION and deprecate SSH_CLIENT; bug #384. ok markus@ -Otto
Re: SSH_CLIENT in recent OpenBSD releases
Am 2012-10-11 10:38, schrieb Bernd: Hi, I've got to port some shell scripts which rely on env vars. One amongst those is $SSH_CLIENT. On OpenBSD 5.1 machines, I don't get what I'd assume to get: # echo $SSH_CLIENT It returns just a blank line. Logged in as normal user, became root via 'su -'. That triggers mentioned behavior, just using 'su' keeps it behaving as expected. Thanks, Bernd I re-tested this on an older development machine, running OpenBSD 4.6: # echo $SSH_CLIENT 123.45.67.89 34402 22 Is that an intended change in behavior (security related)? I didn't find a changelog entry, neither documentation. Thanks, Bernd
iscsid(8) and FreeNAS 8.2.0
Hi Misc@,
Has anyone tried using OBSD iscsid(8) initiator and FreeNAS target? I was
trying to do it on amd64 -current but so far unsuccessful.
Best Regards,
Insan
iscsi.conf
--
target Disk2 {
enabled
normal
targetaddr 10.10.10.139
targetname iqn.2012-03.xxx.net:disk2
}
/var/log/messages
-
Oct 11 13:25:46 backend iscsid[11678]: fatal: vscsi_open: No such file or
directory
dmesg
-
OpenBSD 5.2-current (GENERIC.MP) #4: Mon Oct 1 19:44:56 WIT 2012
r...@backend.xxx.xxx:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8578588672 (8181MB)
avail mem = 8327753728 (7941MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdf7fe000 (134 entries)
bios0: vendor HP version P67 date 05/05/2011
bios0: HP ProLiant DL380 G7
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP SPCR MCFG HPET SPMI ERST APIC SRAT BERT
HEST DMAR SSDT SSDT SSDT SSDT SSDT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2133.06 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: apic clock running at 133MHz
cpu1 at mainbus0: apid 20 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2132.73 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu1: 256KB 64b/line 8-way L2 cache
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2132.73 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu2: 256KB 64b/line 8-way L2 cache
cpu3 at mainbus0: apid 18 (application processor)
cpu3: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2132.73 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu3: 256KB 64b/line 8-way L2 cache
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic1 at mainbus0: apid 0 pa 0xfec8, version 20, 24 pins
acpiprt0 at acpi0: bus 1 (IP2P)
acpiprt1 at acpi0: bus 3 (IPT1)
acpiprt2 at acpi0: bus 4 (IPT3)
acpiprt3 at acpi0: bus 2 (IPT5)
acpiprt4 at acpi0: bus 5 (PT01)
acpiprt5 at acpi0: bus 17 (PT03)
acpiprt6 at acpi0: bus 20 (PT04)
acpiprt7 at acpi0: bus 21 (PT05)
acpiprt8 at acpi0: bus 24 (PT06)
acpiprt9 at acpi0: bus 14 (PT07)
acpiprt10 at acpi0: bus 11 (PT08)
acpiprt11 at acpi0: bus 8 (PT09)
acpiprt12 at acpi0: bus 7 (PT0A)
acpiprt13 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C3, C3, C1
acpicpu1 at acpi0: C3, C3, C1
acpicpu2 at acpi0: C3, C3, C1
acpicpu3 at acpi0: C3, C3, C1
acpitz0 at acpi0: critical temperature is 31 degC
ipmi at mainbus0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel 5520 Host rev 0x13
ppb0 at pci0 dev 1 function 0 Intel X58 PCIE rev 0x13
pci1 at ppb0 bus 5
ciss0 at pci1 dev 0 function 0 Hewlett-Packard Smart Array rev 0x01:
apic 0 int 4
ciss0: 1 LD, HW rev 2, FW 5.70/5.70, 64bit fifo rro
scsibus0 at ciss0: 1 targets
sd0 at scsibus0 targ 0 lun 0: HP, LOGICAL VOLUME, 5.70 SCSI3 0/direct
fixed
sd0: 286070MB, 512 bytes/sector, 585871964 sectors
ppb1 at pci0 dev 2 function 0 Intel X58 PCIE rev 0x13
pci2 at ppb1 bus 6
ppb2 at pci0 dev 3 function 0 Intel X58 PCIE rev 0x13
pci3 at ppb2 bus 17
ppb3 at pci0 dev 4 function 0 Intel X58 PCIE rev 0x13
pci4 at ppb3 bus 20
ppb4 at pci0 dev 5 function 0 Intel X58 PCIE rev 0x13
pci5 at ppb4 bus 21
ppb5 at pci0 dev 6 function 0 Intel X58 PCIE rev 0x13
pci6 at ppb5 bus 24
ppb6 at pci0 dev 7 function 0 Intel X58 PCIE rev 0x13
pci7 at ppb6 bus 14
ppb7 at pci0 dev 8 function 0 Intel X58 PCIE rev 0x13
pci8 at ppb7 bus 11
ppb8 at pci0 dev 9 function 0 Intel X58 PCIE rev 0x13
pci9 at ppb8 bus 8
ppb9 at pci0 dev 10 function 0 Intel X58 PCIE rev 0x13
pci10 at ppb9 bus 7
pchb1 at pci0 dev 13 function 0 vendor Intel, unknown product 0x343a rev
0x13
pchb2 at pci0 dev 13 function 1 vendor Intel, unknown product 0x343b rev
0x13
pchb3 at pci0 dev 13 function 2 vendor Intel, unknown product 0x343c rev
0x13
pchb4 at pci0 dev 13 function 3 vendor Intel, unknown product 0x343d rev
0x13
pchb5 at pci0 dev 13 function 4 Intel
Re: SSH_CLIENT in recent OpenBSD releases
Am 2012-10-11 11:01, schrieb Otto Moerbeek: On Thu, Oct 11, 2012 at 10:54:05AM +0200, Otto Moerbeek wrote: On Thu, Oct 11, 2012 at 10:38:04AM +0200, Bernd wrote: Hi, I've got to port some shell scripts which rely on env vars. One amongst those is $SSH_CLIENT. On OpenBSD 5.1 machines, I don't get what I'd assume to get: # echo $SSH_CLIENT It returns just a blank line. I re-tested this on an older development machine, running OpenBSD 4.6: # echo $SSH_CLIENT 123.45.67.89 34402 22 Is that an intended change in behavior (security related)? I didn't find a changelog entry, neither documentation. Thanks, Bernd SSH_CONNECTION replaces SSH_CLIENT. See the commit below and https://bugzilla.mindrot.org/show_bug.cgi?id=384 Ehh, replace is not the right word. It's still there. Thanks for that hint, but still: # echo $SSH_CONNECTION # echo $SSH_CLIENT # On the older machines, interesingly (and 'of course'), both return sensible data. Bernd CVSROOT:/cvs Module name:src Changes by: stev...@cvs.openbsd.org 2002/09/12 13:50:36 Modified files: usr.bin/ssh: session.c ssh.1 Log message: add SSH_CONNECTION and deprecate SSH_CLIENT; bug #384. ok markus@ -Otto
Re: SSH_CLIENT in recent OpenBSD releases
On 2012 Oct 11 (Thu) at 11:15:24 +0200 (+0200), Bernd wrote: :Am 2012-10-11 10:38, schrieb Bernd: :Hi, : :I've got to port some shell scripts which rely on env vars. One :amongst those is $SSH_CLIENT. : :On OpenBSD 5.1 machines, I don't get what I'd assume to get: : :# echo $SSH_CLIENT : :It returns just a blank line. : :Logged in as normal user, became root via 'su -'. That triggers :mentioned behavior, just using 'su' keeps it behaving as expected. : $ man su ... - Same as the -l option (deprecated). ... -l Simulate a full login. The environment is discarded except for HOME, SHELL, PATH, TERM, LOGNAME, and USER. HOME and SHELL are modified as above. LOGNAME and USER are set to the target login. PATH is set to the value specified by the ``path'' entry in login.conf(5). TERM is imported from your current environment. The invoked shell is the target login's, and su will change directory to the target login's home directory. -- Distress, n.: A disease incurred by exposure to the prosperity of a friend. -- Ambrose Bierce, The Devil's Dictionary
Re: SSH_CLIENT in recent OpenBSD releases
Am 2012-10-11 11:29, schrieb Peter Hessler: On 2012 Oct 11 (Thu) at 11:15:24 +0200 (+0200), Bernd wrote: :Am 2012-10-11 10:38, schrieb Bernd: :Hi, : :I've got to port some shell scripts which rely on env vars. One :amongst those is $SSH_CLIENT. : :On OpenBSD 5.1 machines, I don't get what I'd assume to get: : :# echo $SSH_CLIENT : :It returns just a blank line. : :Logged in as normal user, became root via 'su -'. That triggers :mentioned behavior, just using 'su' keeps it behaving as expected. : $ man su ... - Same as the -l option (deprecated). ... -l Simulate a full login. The environment is discarded except for HOME, SHELL, PATH, TERM, LOGNAME, and USER. HOME and SHELL are modified as above. LOGNAME and USER are set to the target login. PATH is set to the value specified by the ``path'' entry in login.conf(5). TERM is imported from your current environment. The invoked shell is the target login's, and su will change directory to the target login's home directory. Known for decades, sure. Still wonder what changed. Machines are pretty extremely default setups. Bernd
Re: the idea of /fastboot ?
Op Wed, 10 Oct 2012 03:43:35 +0200 schreef Artturi Alm artturi@gmail.com: 2012/10/10 Philip Guenther guent...@gmail.com: On Tue, Oct 9, 2012 at 5:01 PM, Theo de Raadt dera...@cvs.openbsd.org wrote: Yes, it is a relic. You may take action against it, Ted. Don't forget to also remove the shutdown(8) bits that use it. Philip Guenther was bored, does this miss anything? Index: rc.8 Index: pathnames.h Index: shutdown.8 Index: shutdown.c Index: rc What about init.8 and init.c? They also mention fastboot. -- Gemaakt met Opera's revolutionaire e-mailprogramma: http://www.opera.com/mail/ (Remove the obvious prefix to reply privately.)
Re: Last i386 snapshot broken ?
I com back, so i tested iso files : install52.iso, cd52.iso (from i386 snapshots) Same problem, reboot just after : CDROM: 9F Loading /5.2/I386/CDBOOT If someone can rebuild the snapshots... Cheers, -- Wesley Le 2012-10-11 11:15, Wesley a écrit : Tested with a new mirror: same problem, reboot just after CDROM: 9F Loading /5.2/I386/CDBOOT -- Wesley Le 2012-10-11 11:00, Wesley a écrit : Le 2012-10-11 10:50, Peter N. M. Hansteen a écrit : there are some fairly straightforward ways to check whether it's the iso file that's at fault. try downloading bsd.rd and the sets and perform an upgrade from local disk. The system is not installed on the machines. It reboots automatically at : CDROM: 9F Loading /5.2/I386/CDBOOT And the SHA256's install52.iso match the SHA256 file present in http://ftp.openbsd.org/pub/OpenBSD/snapshots/i386/SHA256; Tried with OpenBSD 5.1 compatible machine, VM... same : error reboot. Need now to test with a second mirror ... Thank you for your reply. -- Wesley
Re: the idea of /fastboot ?
ÓÒÅÄÁ, 10 ÏËÔÑÂÒÑ 2012 Ç. ÐÏÌØÚÏ×ÁÔÅÌØ Nick Holland ÐÉÓÁÌ: On 10/09/2012 12:55 PM, éÌØÑ ûÉÐÉÃÉÎ wrote: Hello! I'm investigating /etc/rc script. And I found the following there: if [ -e /fastboot ]; then echo Fast boot: skipping disk checks. elif [ X$1 = Xautoboot ]; then echo Automatic boot in progress: starting file system checks. hmm... if I put /fastboot, no filesystem will be checked ? so says the code, yes. how it supposed to work for non-nfs filesystems ? properly? they'll be not checked, too? Just one more question. If /fastboot presents, filesystem won't be checked, right? But how does fsck detects if there's /fastboot? Is it possible thing to do without actually mount it? Is it possible to mount dirty filesystem in read-only mode ? If not, it doesn't make sense at all.
Detone sus ventas en Internet [9 Nov. Centro Banamex]
Newsletter. iMex Internet Marketing Experts, Ferias, Congresos, Talleres, Seminarios y Webinars. Digitalizando Empresas en México y América Latina. ¿No puede ver correctamente este correo? Vealo en su navegador. Congreso iMex Internet Marketing Experts 2012 Congreso iMex Internet Marketing Experts VII Edición 9 de Noviembre 2012, Centro Banamex Celebrando nuestra VII Edición, vuelve a la Cd. de México Congreso iMex Internet Marketing Experts, uno de los mayores meetings especializados de capacitación corporativa en herramientas, servicios y tendencias de alto impacto en marketing digital para México y América Latina. Comunicación efectiva, posicionamiento de marca, mayores ventas, excelente ROI, presencia en el mercado y alta competitividad. Internet hará esto y mucho más por su empresa. La manera de hacer negocios ha evolucionado... ¿es usted parte de esta evolución digital? Descargue el programa del evento haciendo Click Aquí o bien responda este Newsletter con sus datos completos. Presentado por iMex, Yahoo, Nokia, Tesseract, Socialmetrix, Green Loveseat, Abaco Digital, Pumpabox, Business Thinking, Soicos y Xtream Networks. Programa PDF Descargue un folleto PDF con los detalles del evento. Regístro Tramite su registro y boletaje electrónico. Mayores informes al: +52 (33) 1188 0002 o bien escríbanos a i...@congresoimex.com y un representante del equipo iMex se pondrá en contacto con usted. [IMAGE] iMex en Facebook [IMAGE] iMex en Twitter [IMAGE] Compartir Newsletter ¿Como Participar? Visite nuestro Sitio Oficial. Contamos con cuotas preferenciales a estudiantes, ex-participantes y pre-registro. Fecha limite 1 de Octubre de 2012. Reserve sus lugares. Cupo limitado a 200 PAX. Síguenos en Twitter | Síguenos en Facebook Copyright © 2012 iMex Internet Marketing Experts, All rights reserved. iMex Internet Marketing Experts Newsletter De acuerdo a la Ley Federal de Protección de Datos Personales en Posesión de los Particulares, aprobada el día 13 de abril de 2010 en los artículos 3, Fracciones II y VII, y 33, así como la denominación del capítulo II, del Título Segundo, de la Ley Federal de Transparencia y Acceso a la Información Pública Gubernamental, le solicitamos amablemente que si usted no es misc@openbsd.org o le gustaría darse de baja de nuestra lista de correos y no recibir más comunicación de nosotros, responda este correo con el subject BAJA BEM12 para su desuscripción y borrado de nuestros registros. Le recordamos que nosotros sólo promovemos valores empresariales, sin el afán de molestarle o poner en peligro sus datos, sino como un servicio de difusión y promoción, siempre bajo su consentimiento y conformidad. Se entenderá que el titular consiente tácitamente el tratamiento de sus datos, cuando habiéndose puesto a su disposición el presente aviso de privacidad, no manifieste su oposición. Agradecemos de antemano sus atenciones.
Re: quick query.
thanks, it took me a while to find 2.2.39, but thanks to you guys its ok now. PEBKAC indeed... On 10 October 2012 21:05, Bob Beck b...@obtuse.com wrote: It is for me #export PKG_PATH= http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64 # pkg_add tor tor-0.2.2.39: ok The following new rcscripts were installed: /etc/rc.d/tor See rc.d(8) for details. # pkg_info tor Information for inst:tor-0.2.2.39 Comment: anonymity service using onion routing Description: Tor is a connection-based low-latency anonymous communication system that protects TCP streams: web browsing, instant messaging, irc, ssh, etc. Maintainer: Pascal Stumpf pascal.stu...@cubes.de WWW: http://www.torproject.org/ Looks like PEBKAC. On Wed, Oct 10, 2012 at 4:48 PM, sharon dvir bpmcont...@gmail.com wrote: it looks like Tor just isn't there. which means that in order to go from 2.2.35 to 2.2.39 i'll have to compile it manually. which is no problem, but hence a need for the tool i originally asked about. or am i missing something? BTW, 2.2.39 fixes some remote exploits for Tor, in case anyone is running it. thanks everyone. On 10 October 2012 18:09, Peter N. M. Hansteen pe...@bsdly.net wrote: Martin Pelikan martin.peli...@gmail.com writes: as sthen@ kindly corrected me the some time ago, we now have pkg.conf(5) and installpath. You're right of course -- pkg.conf has been with us for a while (first appearance in 4.8 it seems). This way it'll work even if you don't invoke package updates from your shell, but using some kind of remote administration software for example. Yes. That functionality would be relevant to the OP. I'd managed to forget all about it, probably because the old .profile trick works so well in other contexts. - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ Remember to set the evil bit on all malicious network traffic delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: the idea of /fastboot ?
On Thu, Oct 11, 2012 at 05:10:19PM +0600, ??? wrote: ?, 10 ??? 2012 ?. Nick Holland ?: On 10/09/2012 12:55 PM, ??? wrote: Hello! I'm investigating /etc/rc script. And I found the following there: if [ -e /fastboot ]; then echo Fast boot: skipping disk checks. elif [ X$1 = Xautoboot ]; then echo Automatic boot in progress: starting file system checks. hmm... if I put /fastboot, no filesystem will be checked ? so says the code, yes. how it supposed to work for non-nfs filesystems ? properly? they'll be not checked, too? Just one more question. If /fastboot presents, filesystem won't be checked, right? But how does fsck detects if there's /fastboot? Is it possible thing to do without actually mount it? fsck does not do anything with /fastboot. The rc script (which calls fsck) does that. During boot, the / filesystem is initially mounted read-only, and then is possibly checked by the rc script. After that, the root filesystem ro status is updated to rw. Is it possible to mount dirty filesystem in read-only mode ? If not, it doesn't make sense at all. Yes, you can mount dirty filesystem with -f. Even read-write iirc. Very dangerous. -Otto
Re: the idea of /fastboot ?
On Thu, Oct 11, 2012, at 07:10 AM, Илья Шипицин wrote: ÓÒÅÄÁ, 10 ÏËÔÑÂÒÑ 2012 Ç. ÐÏÌØÚÏ×ÁÔÅÌØ Nick Holland ÐÉÓÁÌ: On 10/09/2012 12:55 PM, éÌØÑ ûÉÐÉÃÉÎ wrote: Hello! I'm investigating /etc/rc script. And I found the following there: if [ -e /fastboot ]; then echo Fast boot: skipping disk checks. elif [ X$1 = Xautoboot ]; then echo Automatic boot in progress: starting file system checks. hmm... if I put /fastboot, no filesystem will be checked ? so says the code, yes. how it supposed to work for non-nfs filesystems ? properly? they'll be not checked, too? Just one more question. If /fastboot presents, filesystem won't be checked, right? But how does fsck detects if there's /fastboot? Is it possible thing to do without actually mount it? Is it possible to mount dirty filesystem in read-only mode ? If not, it doesn't make sense at all. Dude, stop worrying about it. It is deprecated. Unless you put it there it will never be there.
Re: the idea of /fastboot ?
Илья Шипицин chipits...@gmail.com writes: [...] Just one more question. If /fastboot presents, filesystem won't be checked, right? That's what's supposed to happen. Else /fastboot wouldn't exist, I guess. But how does fsck detects if there's /fastboot? Is it possible thing to do without actually mount it? How would one access the fsck executable? Or the /etc/fstab file? Is it possible to mount dirty filesystem in read-only mode ? If not, it doesn't make sense at all. Then there seems to be only one option. :) -- Jérémie Courrèges-Anglas GPG fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
Re: Last i386 snapshot broken ?
On 10/11/12 12:51, Wesley wrote: I com back, so i tested iso files : install52.iso, cd52.iso (from i386 snapshots) Same problem, reboot just after : CDROM: 9F Loading /5.2/I386/CDBOOT I can confirm that. Same here. -current (i386) 10/10/12 -- Udo
Re: the idea of /fastboot ?
2012/10/11 Otto Moerbeek o...@drijf.net On Thu, Oct 11, 2012 at 05:10:19PM +0600, ??? wrote: ?, 10 ??? 2012 ?. Nick Holland ?: On 10/09/2012 12:55 PM, ??? wrote: Hello! I'm investigating /etc/rc script. And I found the following there: if [ -e /fastboot ]; then echo Fast boot: skipping disk checks. elif [ X$1 = Xautoboot ]; then echo Automatic boot in progress: starting file system checks. hmm... if I put /fastboot, no filesystem will be checked ? so says the code, yes. how it supposed to work for non-nfs filesystems ? properly? they'll be not checked, too? Just one more question. If /fastboot presents, filesystem won't be checked, right? But how does fsck detects if there's /fastboot? Is it possible thing to do without actually mount it? fsck does not do anything with /fastboot. The rc script (which calls fsck) does that. During boot, the / filesystem is initially mounted read-only, and then is possibly checked by the rc script. After that, the root filesystem ro status is updated to rw. thank you. it is clear now. very similar to Linux and FreeBSD. Is it possible to mount dirty filesystem in read-only mode ? If not, it doesn't make sense at all. Yes, you can mount dirty filesystem with -f. Even read-write iirc. Very dangerous. I'm struggling with 7Tb filesystems, it takes about 30 minutes to check them in case of cold reset. Too much. Very too much. and currently, no journals or anything else which could speed up 7Tb filesystems check ? -Otto
Re: Last i386 snapshot broken ?
Satisfied to see that i'm not the only one. ;-) Le 2012-10-11 15:39, Udo Siewert a écrit : On 10/11/12 12:51, Wesley wrote: I com back, so i tested iso files : install52.iso, cd52.iso (from i386 snapshots) Same problem, reboot just after : CDROM: 9F Loading /5.2/I386/CDBOOT I can confirm that. Same here. -current (i386) 10/10/12
Re: OpenBSD-5.1 hangs on Supermicro X9DR3-F
On Thu, Oct 11, 2012 at 12:30:56PM +0600, ??? wrote: Hello! we recently installed OpenBSD/amd64 on Supermicro X9DR3-F, it hangs about 1 times a day. 5.1 does not understand i350 chip, so we put external Intel PRO/1000 MT (82574L) nic. we have ddb.panic=1, but no ddb appears on screen on hang. also, it says savecore: no core dump during boot. we tested RAM with memtest, so we do not suspect it for memory related issue. how can we diagnose those hangs ? is it ok to run 5.1 on X9DR3-F ? do I need to provide dmesg output ? any other kind of diagnostics ? Cheers, Ilya Shipitsin http://openbsd.org/report.html Ken
Re: Last i386 snapshot broken ?
On Thu, Oct 11, 2012 at 02:51:22PM +0400, Wesley wrote: I com back, so i tested iso files : install52.iso, cd52.iso (from i386 snapshots) Same problem, reboot just after : CDROM: 9F Loading /5.2/I386/CDBOOT If someone can rebuild the snapshots... Cheers, -- Wesley Snaps are built almost everyday. You seem to have hit something in the current effort to improved the boot blocks. Wait a day or so and try the latest snapshot then. Ken Le 2012-10-11 11:15, Wesley a ??crit??: Tested with a new mirror: same problem, reboot just after CDROM: 9F Loading /5.2/I386/CDBOOT -- Wesley Le 2012-10-11 11:00, Wesley a ??crit??: Le 2012-10-11 10:50, Peter N. M. Hansteen a ??crit??: there are some fairly straightforward ways to check whether it's the iso file that's at fault. try downloading bsd.rd and the sets and perform an upgrade from local disk. The system is not installed on the machines. It reboots automatically at : CDROM: 9F Loading /5.2/I386/CDBOOT And the SHA256's install52.iso match the SHA256 file present in http://ftp.openbsd.org/pub/OpenBSD/snapshots/i386/SHA256; Tried with OpenBSD 5.1 compatible machine, VM... same : error reboot. Need now to test with a second mirror ... Thank you for your reply. -- Wesley
Re: Last i386 snapshot broken ?
On Thu, Oct 11, 2012 at 08:19:48AM -0400, Kenneth R Westerback wrote: Snaps are built almost everyday. You seem to have hit something in the current effort to improved the boot blocks. Wait a day or so and try the latest snapshot then. In the meanwhile I can confirm that the snapshot as a whole upgraded without any problems from my previously installed October 3rd-snapshot to todays current. i386. Blessed be the bsd.rd.
Re: the idea of /fastboot ?
... I'm struggling with 7Tb filesystems, it takes about 30 minutes to check them in case of cold reset. Too much. Very too much. and currently, no journals or anything else which could speed up 7Tb filesystems check ? Almost always (in my mind/experience), file systems that big are bad design. Break your system into chunks, you will end up much happier, and I suspect your users will be, too. Advanced file systems have costs that have to be considered in system design. ZFS is everyone's favorite file system at the moment, but having played with it a bit, even if it re-released with a ISC/BSD license (don't wait up), I doubt it would ever be accepted into OpenBSD -- it's a knobfest, it's anything BUT set it and ignore it; it's job security for people setting up such systems. In your case...if you have multiple 500GB or 1TB file systems, you can hopefully mount most of them R/O, and not have to worry about fsck times at all. Nick.
Re: Last i386 snapshot broken ?
Hi, Confirm the iso is somehow got problem. I've tried with my virtualbox. Stuck at CD-ROM:E0 Loading /5.2/I386/CDBOOT On Thu, Oct 11, 2012 at 9:14 PM, Erling Westenvik erling.westen...@gmail.com wrote: On Thu, Oct 11, 2012 at 08:19:48AM -0400, Kenneth R Westerback wrote: Snaps are built almost everyday. You seem to have hit something in the current effort to improved the boot blocks. Wait a day or so and try the latest snapshot then. In the meanwhile I can confirm that the snapshot as a whole upgraded without any problems from my previously installed October 3rd-snapshot to todays current. i386. Blessed be the bsd.rd. -- -- 7.2-RELEASE-p6
Re: SSH_CLIENT in recent OpenBSD releases
On Oct 11 10:38:04, be...@kroenchenstadt.de wrote: Hi, I've got to port some shell scripts which rely on env vars. One amongst those is $SSH_CLIENT. On OpenBSD 5.1 machines, I don't get what I'd assume to get: # echo $SSH_CLIENT It returns just a blank line. Are you in fact ssh-connected to the machine you are running this on? That is, are you running this in the sshd-spawned shell?
Re: the idea of /fastboot ?
Is it possible to mount dirty filesystem in read-only mode ? If not, it doesn't make sense at all. Yes, you can mount dirty filesystem with -f. Even read-write iirc. Very dangerous. I'm struggling with 7Tb filesystems, it takes about 30 minutes to check them in case of cold reset. Too much. Very too much. and currently, no journals or anything else which could speed up 7Tb filesystems check ? man newfs, in particular the -i option. What does 'df -hi' say about your filesystem?
Re: the idea of /fastboot ?
On Thu, Oct 11, 2012 at 10:09:50AM -0400, Nick Holland wrote: Almost always (in my mind/experience), file systems that big are bad My /usr/ports/mind/experience appear to be broken..
Re: the idea of /fastboot ?
2012/10/11 Jan Stary h...@stare.cz Is it possible to mount dirty filesystem in read-only mode ? If not, it doesn't make sense at all. Yes, you can mount dirty filesystem with -f. Even read-write iirc. Very dangerous. I'm struggling with 7Tb filesystems, it takes about 30 minutes to check them in case of cold reset. Too much. Very too much. and currently, no journals or anything else which could speed up 7Tb filesystems check ? man newfs, in particular the -i option. What does 'df -hi' say about your filesystem? # df -hi Filesystem SizeUsed Avail Capacity iused ifree %iused Mounted on /dev/sd0a 377G2.7G356G 1% 158121 24804949 1% / /dev/sd1a 6.7T331G6.1T 5%8041 228037269 0% /big
Re: the idea of /fastboot ?
On Thu, Oct 11, 2012 at 5:24 AM, Eric Furman ericfur...@fastmail.net wrote: On Thu, Oct 11, 2012, at 07:10 AM, Илья Шипицин wrote: ÓÒÅÄÁ, 10 ÏËÔÑÂÒÑ 2012 Ç. ÐÏÌØÚÏ×ÁÔÅÌØ Nick Holland ÐÉÓÁÌ: how it supposed to work for non-nfs filesystems ? properly? they'll be not checked, too? Just one more question. If /fastboot presents, filesystem won't be checked, right? But how does fsck detects if there's /fastboot? Is it possible thing to do without actually mount it? Is it possible to mount dirty filesystem in read-only mode ? If not, it doesn't make sense at all. Dude, stop worrying about it. It is deprecated. Unless you put it there it will never be there. I recall seeing a script called fastboot that looked something like: #!/bin/sh touch /fastboot sync sync halt Not sure what OS that was but I know the fastboot command was present in 4.2 BSD and SunOS 4.1.3.
Re: the idea of /fastboot ?
2012/10/11 Nick Holland n...@holland-consulting.net ... I'm struggling with 7Tb filesystems, it takes about 30 minutes to check them in case of cold reset. Too much. Very too much. and currently, no journals or anything else which could speed up 7Tb filesystems check ? Almost always (in my mind/experience), file systems that big are bad design. Break your system into chunks, you will end up much happier, and I suspect your users will be, too. Advanced file systems have costs that have to be considered in system design. ZFS is everyone's favorite file system at the moment, but having played with it a bit, even if it re-released with a ISC/BSD license (don't wait up), I doubt it would ever be accepted into OpenBSD -- it's a knobfest, it's anything BUT set it and ignore it; it's job security for people setting up such systems. In your case...if you have multiple 500GB or 1TB file systems, you can hopefully mount most of them R/O, and not have to worry about fsck times at all. Nick. there are http access logs for half an year. it's easier to rotate them on a single filesystem from many points of view, we also share it via samba (very tricky to share many chunks). and it is bad idea to mount access logs R/O. difficult to rotate.
Trouble waking up with -current
Hi misc@, I've been running the latest -current for a few days and facing an issue with USB and sleep/wake up process. When I boot with some USB device plugged in, I have no problem. However, if I disconnect, I see it in the dmesg. If I connect it again, there is no dmesg message and the device becomes unusable. This isn't a new issue, but I used to solve this putting the box to sleep and waking it up soon after. The problem is that, with the latest -current, I can't put it to sleep. It seems to begin the process, makes some movement, but returns with a blank screen, and I need to cold reboot. It used to work just fine with 5.1. Any ideas? Thank you. OpenBSD 5.2-current (GENERIC.MP) #35: Tue Oct 2 14:25:50 MDT 2012 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3184132096 (3036MB) avail mem = 3076956160 (2934MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xfc480 (33 entries) bios0: vendor American Megatrends Inc. version 200.T02 date 10/26/2010 bios0: POSITIVO POSITIVO MOBILE acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG SLIC ECDT DBGP BOOT OEMB HPET GSCI ATKG SSDT acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB5(S3) EUSB(S3) USB3(S3) USB4(S3) USB6(S3) USBE(S3) HDAC(S3) P0P1(S4) P0P2(S3) P0P3(S3) WLAN(S3) P0P4(S3) P0P7(S4) GLAN(S4) P0P8(S3) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Pentium(R) Dual-Core CPU T4500 @ 2.30GHz, 3220.54 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,XSAVE,NXE,LONG,LAHF cpu0: 1MB 64b/line 4-way L2 cache cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Pentium(R) Dual-Core CPU T4500 @ 2.30GHz, 2300.08 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,XSAVE,NXE,LONG,LAHF cpu1: 1MB 64b/line 4-way L2 cache ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiec0 at acpi0 acpihpet0 at acpi0: 14318179 Hz acpi0: unable to load \\_SB_.PCI0._INI.USBT acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 1 (P0P2) acpiprt3 at acpi0: bus 2 (P0P3) acpiprt4 at acpi0: bus 3 (P0P4) acpiprt5 at acpi0: bus 5 (P0P7) acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpitz0 at acpi0: critical temperature is 110 degC acpiac0 at acpi0: AC unit in unknown state acpibat0 at acpi0: BAT0 not present acpiasus at acpi0 not configured acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: LID_ cpu0: Enhanced SpeedStep 3220 MHz: speeds: 2300, 1600, 1200 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel GM45 Host rev 0x09 vga1 at pci0 dev 2 function 0 Intel GM45 Video rev 0x09 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 0xd000, size 0x1000 inteldrm0 at vga1: apic 2 int 16 drm0 at inteldrm0 Intel GM45 Video rev 0x09 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x03: apic 2 int 16 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x03: apic 2 int 17 uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x03: apic 2 int 19 ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x03: apic 2 int 18 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 82801I HD Audio rev 0x03: msi azalia0: codecs: Realtek ALC269, Intel/0x2802, using Realtek ALC269 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x03: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 1 Intel 82801I PCIE rev 0x03: msi pci2 at ppb1 bus 2 athn0 at pci2 dev 0 function 0 Atheros AR2427 rev 0x01: apic 2 int 17 athn0: AR9285 rev 2 (1T1R), ROM rev 13, address 48:5d:60:a2:e0:6a ppb2 at pci0 dev 28 function 2 Intel 82801I PCIE rev 0x03: msi pci3 at ppb2 bus 3 ppb3 at pci0 dev 28 function 5 Intel 82801I PCIE rev 0x03: msi pci4 at ppb3 bus 5 re0 at pci4 dev 0 function 0 Realtek 8168 rev 0x03: RTL8168D/8111D (0x2800), apic 2 int 17, address e0:69:95:a1:cb:1b rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 uhci3 at pci0 dev 29 function 0 Intel 82801I USB rev 0x03: apic 2 int 23 uhci4 at pci0 dev 29 function 1 Intel 82801I USB rev 0x03: apic 2 int 19 uhci5 at pci0 dev 29 function 2 Intel 82801I USB rev 0x03: apic 2 int 18 ehci1 at pci0 dev 29 function 7 Intel 82801I USB rev 0x03: apic 2 int 23 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x93 pci5 at ppb4 bus 6 pcib0 at pci0 dev 31
Re: the idea of /fastboot ?
On Thu, Oct 11, 2012 at 09:22:13PM +0600, ??? wrote: 2012/10/11 Jan Stary h...@stare.cz Is it possible to mount dirty filesystem in read-only mode ? If not, it doesn't make sense at all. Yes, you can mount dirty filesystem with -f. Even read-write iirc. Very dangerous. I'm struggling with 7Tb filesystems, it takes about 30 minutes to check them in case of cold reset. Too much. Very too much. and currently, no journals or anything else which could speed up 7Tb filesystems check ? man newfs, in particular the -i option. What does 'df -hi' say about your filesystem? # df -hi Filesystem SizeUsed Avail Capacity iused ifree %iused Mounted on /dev/sd0a 377G2.7G356G 1% 158121 24804949 1% / /dev/sd1a 6.7T331G6.1T 5%8041 228037269 0% /big Relatively few very big files. What's the fragment and block size used on this filesystem? # dumpfs /dev/rwd1a | grep ^[bf]size -Otto
Re: Trouble waking up with -current
Sorry for going off-topic, but is this normal? T4500 doesn't have Turbo Boost... cpu0: Pentium(R) Dual-Core CPU T4500 @ 2.30GHz, 3220.54 MHz cpu1: Pentium(R) Dual-Core CPU T4500 @ 2.30GHz, 2300.08 MHz
Re: iscsid(8) and FreeNAS 8.2.0
Do you have a /dev/vscsi0 ?
If not, cd /dev and ./MAKEDEV vscsi
Insan Praja SW [insan.pr...@gmail.com] wrote:
Hi Misc@,
Has anyone tried using OBSD iscsid(8) initiator and FreeNAS target?
I was trying to do it on amd64 -current but so far unsuccessful.
Best Regards,
Insan
iscsi.conf
--
target Disk2 {
enabled
normal
targetaddr 10.10.10.139
targetname iqn.2012-03.xxx.net:disk2
}
/var/log/messages
-
Oct 11 13:25:46 backend iscsid[11678]: fatal: vscsi_open: No such
file or directory
dmesg
-
OpenBSD 5.2-current (GENERIC.MP) #4: Mon Oct 1 19:44:56 WIT 2012
r...@backend.xxx.xxx:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8578588672 (8181MB)
avail mem = 8327753728 (7941MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdf7fe000 (134 entries)
bios0: vendor HP version P67 date 05/05/2011
bios0: HP ProLiant DL380 G7
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP SPCR MCFG HPET SPMI ERST APIC SRAT
BERT HEST DMAR SSDT SSDT SSDT SSDT SSDT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2133.06 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: apic clock running at 133MHz
cpu1 at mainbus0: apid 20 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2132.73 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu1: 256KB 64b/line 8-way L2 cache
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2132.73 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu2: 256KB 64b/line 8-way L2 cache
cpu3 at mainbus0: apid 18 (application processor)
cpu3: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2132.73 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu3: 256KB 64b/line 8-way L2 cache
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic1 at mainbus0: apid 0 pa 0xfec8, version 20, 24 pins
acpiprt0 at acpi0: bus 1 (IP2P)
acpiprt1 at acpi0: bus 3 (IPT1)
acpiprt2 at acpi0: bus 4 (IPT3)
acpiprt3 at acpi0: bus 2 (IPT5)
acpiprt4 at acpi0: bus 5 (PT01)
acpiprt5 at acpi0: bus 17 (PT03)
acpiprt6 at acpi0: bus 20 (PT04)
acpiprt7 at acpi0: bus 21 (PT05)
acpiprt8 at acpi0: bus 24 (PT06)
acpiprt9 at acpi0: bus 14 (PT07)
acpiprt10 at acpi0: bus 11 (PT08)
acpiprt11 at acpi0: bus 8 (PT09)
acpiprt12 at acpi0: bus 7 (PT0A)
acpiprt13 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C3, C3, C1
acpicpu1 at acpi0: C3, C3, C1
acpicpu2 at acpi0: C3, C3, C1
acpicpu3 at acpi0: C3, C3, C1
acpitz0 at acpi0: critical temperature is 31 degC
ipmi at mainbus0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel 5520 Host rev 0x13
ppb0 at pci0 dev 1 function 0 Intel X58 PCIE rev 0x13
pci1 at ppb0 bus 5
ciss0 at pci1 dev 0 function 0 Hewlett-Packard Smart Array rev
0x01: apic 0 int 4
ciss0: 1 LD, HW rev 2, FW 5.70/5.70, 64bit fifo rro
scsibus0 at ciss0: 1 targets
sd0 at scsibus0 targ 0 lun 0: HP, LOGICAL VOLUME, 5.70 SCSI3
0/direct fixed
sd0: 286070MB, 512 bytes/sector, 585871964 sectors
ppb1 at pci0 dev 2 function 0 Intel X58 PCIE rev 0x13
pci2 at ppb1 bus 6
ppb2 at pci0 dev 3 function 0 Intel X58 PCIE rev 0x13
pci3 at ppb2 bus 17
ppb3 at pci0 dev 4 function 0 Intel X58 PCIE rev 0x13
pci4 at ppb3 bus 20
ppb4 at pci0 dev 5 function 0 Intel X58 PCIE rev 0x13
pci5 at ppb4 bus 21
ppb5 at pci0 dev 6 function 0 Intel X58 PCIE rev 0x13
pci6 at ppb5 bus 24
ppb6 at pci0 dev 7 function 0 Intel X58 PCIE rev 0x13
pci7 at ppb6 bus 14
ppb7 at pci0 dev 8 function 0 Intel X58 PCIE rev 0x13
pci8 at ppb7 bus 11
ppb8 at pci0 dev 9 function 0 Intel X58 PCIE rev 0x13
pci9 at ppb8 bus 8
ppb9 at pci0 dev 10 function 0 Intel X58 PCIE rev 0x13
pci10 at ppb9 bus 7
pchb1 at pci0 dev 13 function 0 vendor Intel, unknown product
0x343a rev 0x13
pchb2 at pci0 dev 13 function 1 vendor Intel, unknown product
0x343b rev 0x13
Re: the idea of /fastboot ?
On Thu, Oct 11, 2012 at 09:29:50PM +0600, �?л�?�? Шипи�?ин wrote: there are http access logs for half an year. it's easier to rotate them on a single filesystem from many points of view, we also share it via samba (very tricky to share many chunks). and it is bad idea to mount access logs R/O. difficult to rotate. Bad design totally! I remember struggling with backup/restore times to satisfy SLA with huge filesystems having many files... And those were logs. One of proposals we did was to split filesystem into smaller ones and keep old logs on filesystems with read-only. Backup would be skipped, and restore (in this it was TSM) would be much faster if image would be used. j.
Re: iscsid(8) and FreeNAS 8.2.0
On Thu, 11 Oct 2012 23:34:03 +0700, Chris Cappuccio ch...@nmedia.net
wrote:
Do you have a /dev/vscsi0 ?
$ ls -la /dev | grep vscsi
crw--- 1 root wheel 90, 0 Oct 8 22:42 vscsi0
$
If not, cd /dev and ./MAKEDEV vscsi
Insan Praja SW [insan.pr...@gmail.com] wrote:
Hi Misc@,
Has anyone tried using OBSD iscsid(8) initiator and FreeNAS target?
I was trying to do it on amd64 -current but so far unsuccessful.
Best Regards,
Insan
iscsi.conf
--
target Disk2 {
enabled
normal
targetaddr 10.10.10.139
targetname iqn.2012-03.xxx.net:disk2
}
Thanks
/var/log/messages
-
Oct 11 13:25:46 backend iscsid[11678]: fatal: vscsi_open: No such
file or directory
dmesg
-
OpenBSD 5.2-current (GENERIC.MP) #4: Mon Oct 1 19:44:56 WIT 2012
r...@backend.xxx.xxx:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8578588672 (8181MB)
avail mem = 8327753728 (7941MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdf7fe000 (134 entries)
bios0: vendor HP version P67 date 05/05/2011
bios0: HP ProLiant DL380 G7
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP SPCR MCFG HPET SPMI ERST APIC SRAT
BERT HEST DMAR SSDT SSDT SSDT SSDT SSDT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2133.06 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: apic clock running at 133MHz
cpu1 at mainbus0: apid 20 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2132.73 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu1: 256KB 64b/line 8-way L2 cache
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2132.73 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu2: 256KB 64b/line 8-way L2 cache
cpu3 at mainbus0: apid 18 (application processor)
cpu3: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2132.73 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu3: 256KB 64b/line 8-way L2 cache
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic1 at mainbus0: apid 0 pa 0xfec8, version 20, 24 pins
acpiprt0 at acpi0: bus 1 (IP2P)
acpiprt1 at acpi0: bus 3 (IPT1)
acpiprt2 at acpi0: bus 4 (IPT3)
acpiprt3 at acpi0: bus 2 (IPT5)
acpiprt4 at acpi0: bus 5 (PT01)
acpiprt5 at acpi0: bus 17 (PT03)
acpiprt6 at acpi0: bus 20 (PT04)
acpiprt7 at acpi0: bus 21 (PT05)
acpiprt8 at acpi0: bus 24 (PT06)
acpiprt9 at acpi0: bus 14 (PT07)
acpiprt10 at acpi0: bus 11 (PT08)
acpiprt11 at acpi0: bus 8 (PT09)
acpiprt12 at acpi0: bus 7 (PT0A)
acpiprt13 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C3, C3, C1
acpicpu1 at acpi0: C3, C3, C1
acpicpu2 at acpi0: C3, C3, C1
acpicpu3 at acpi0: C3, C3, C1
acpitz0 at acpi0: critical temperature is 31 degC
ipmi at mainbus0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel 5520 Host rev 0x13
ppb0 at pci0 dev 1 function 0 Intel X58 PCIE rev 0x13
pci1 at ppb0 bus 5
ciss0 at pci1 dev 0 function 0 Hewlett-Packard Smart Array rev
0x01: apic 0 int 4
ciss0: 1 LD, HW rev 2, FW 5.70/5.70, 64bit fifo rro
scsibus0 at ciss0: 1 targets
sd0 at scsibus0 targ 0 lun 0: HP, LOGICAL VOLUME, 5.70 SCSI3
0/direct fixed
sd0: 286070MB, 512 bytes/sector, 585871964 sectors
ppb1 at pci0 dev 2 function 0 Intel X58 PCIE rev 0x13
pci2 at ppb1 bus 6
ppb2 at pci0 dev 3 function 0 Intel X58 PCIE rev 0x13
pci3 at ppb2 bus 17
ppb3 at pci0 dev 4 function 0 Intel X58 PCIE rev 0x13
pci4 at ppb3 bus 20
ppb4 at pci0 dev 5 function 0 Intel X58 PCIE rev 0x13
pci5 at ppb4 bus 21
ppb5 at pci0 dev 6 function 0 Intel X58 PCIE rev 0x13
pci6 at ppb5 bus 24
ppb6 at pci0 dev 7 function 0 Intel X58 PCIE rev 0x13
pci7 at ppb6 bus 14
ppb7 at pci0 dev 8 function 0 Intel X58 PCIE rev 0x13
pci8 at ppb7 bus 11
ppb8 at pci0 dev 9 function 0 Intel X58 PCIE rev 0x13
pci9 at ppb8 bus 8
ppb9 at pci0 dev 10 function 0 Intel X58 PCIE rev 0x13
pci10 at ppb9 bus 7
pchb1 at pci0 dev 13 function 0 vendor Intel, unknown product
0x343a rev 0x13
Re: iscsid(8) and FreeNAS 8.2.0
Sorry, paste-ing info from the wrong machine. This is the vscsi0 on the
right machine.
$ ls -la /dev | grep vscsi
crw--- 1 root wheel 89, 0 Aug 31 11:28 vscsi0
On Thu, 11 Oct 2012 23:34:03 +0700, Chris Cappuccio ch...@nmedia.net
wrote:
Do you have a /dev/vscsi0 ?
$ ls -la /dev | grep vscsi
crw--- 1 root wheel 90, 0 Oct 8 22:42 vscsi0
$
If not, cd /dev and ./MAKEDEV vscsi
Insan Praja SW [insan.pr...@gmail.com] wrote:
Hi Misc@,
Has anyone tried using OBSD iscsid(8) initiator and FreeNAS target?
I was trying to do it on amd64 -current but so far unsuccessful.
Best Regards,
Insan
iscsi.conf
--
target Disk2 {
enabled
normal
targetaddr 10.10.10.139
targetname iqn.2012-03.xxx.net:disk2
}
Thanks
/var/log/messages
-
Oct 11 13:25:46 backend iscsid[11678]: fatal: vscsi_open: No such
file or directory
dmesg
-
OpenBSD 5.2-current (GENERIC.MP) #4: Mon Oct 1 19:44:56 WIT 2012
r...@backend.xxx.xxx:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8578588672 (8181MB)
avail mem = 8327753728 (7941MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdf7fe000 (134 entries)
bios0: vendor HP version P67 date 05/05/2011
bios0: HP ProLiant DL380 G7
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP SPCR MCFG HPET SPMI ERST APIC SRAT
BERT HEST DMAR SSDT SSDT SSDT SSDT SSDT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2133.06 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: apic clock running at 133MHz
cpu1 at mainbus0: apid 20 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2132.73 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu1: 256KB 64b/line 8-way L2 cache
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2132.73 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu2: 256KB 64b/line 8-way L2 cache
cpu3 at mainbus0: apid 18 (application processor)
cpu3: Intel(R) Xeon(R) CPU E5606 @ 2.13GHz, 2132.73 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
cpu3: 256KB 64b/line 8-way L2 cache
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic1 at mainbus0: apid 0 pa 0xfec8, version 20, 24 pins
acpiprt0 at acpi0: bus 1 (IP2P)
acpiprt1 at acpi0: bus 3 (IPT1)
acpiprt2 at acpi0: bus 4 (IPT3)
acpiprt3 at acpi0: bus 2 (IPT5)
acpiprt4 at acpi0: bus 5 (PT01)
acpiprt5 at acpi0: bus 17 (PT03)
acpiprt6 at acpi0: bus 20 (PT04)
acpiprt7 at acpi0: bus 21 (PT05)
acpiprt8 at acpi0: bus 24 (PT06)
acpiprt9 at acpi0: bus 14 (PT07)
acpiprt10 at acpi0: bus 11 (PT08)
acpiprt11 at acpi0: bus 8 (PT09)
acpiprt12 at acpi0: bus 7 (PT0A)
acpiprt13 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C3, C3, C1
acpicpu1 at acpi0: C3, C3, C1
acpicpu2 at acpi0: C3, C3, C1
acpicpu3 at acpi0: C3, C3, C1
acpitz0 at acpi0: critical temperature is 31 degC
ipmi at mainbus0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel 5520 Host rev 0x13
ppb0 at pci0 dev 1 function 0 Intel X58 PCIE rev 0x13
pci1 at ppb0 bus 5
ciss0 at pci1 dev 0 function 0 Hewlett-Packard Smart Array rev
0x01: apic 0 int 4
ciss0: 1 LD, HW rev 2, FW 5.70/5.70, 64bit fifo rro
scsibus0 at ciss0: 1 targets
sd0 at scsibus0 targ 0 lun 0: HP, LOGICAL VOLUME, 5.70 SCSI3
0/direct fixed
sd0: 286070MB, 512 bytes/sector, 585871964 sectors
ppb1 at pci0 dev 2 function 0 Intel X58 PCIE rev 0x13
pci2 at ppb1 bus 6
ppb2 at pci0 dev 3 function 0 Intel X58 PCIE rev 0x13
pci3 at ppb2 bus 17
ppb3 at pci0 dev 4 function 0 Intel X58 PCIE rev 0x13
pci4 at ppb3 bus 20
ppb4 at pci0 dev 5 function 0 Intel X58 PCIE rev 0x13
pci5 at ppb4 bus 21
ppb5 at pci0 dev 6 function 0 Intel X58 PCIE rev 0x13
pci6 at ppb5 bus 24
ppb6 at pci0 dev 7 function 0 Intel X58 PCIE rev 0x13
pci7 at ppb6 bus 14
ppb7 at pci0 dev 8 function 0 Intel X58 PCIE rev 0x13
pci8 at ppb7 bus 11
ppb8 at pci0 dev 9 function 0 Intel X58 PCIE rev
Re: SSH_CLIENT in recent OpenBSD releases
Missed the earlier part of this thread but... If you su - to another userid the environment variable appears to get unset. To the OP have you su'd or are do trying this immediately on login. I am running 5.1-stable and current and $SSH_CLIENT is valid on both boxes. On Thu, Oct 11, 2012 at 05:02:39PM +0200, Jan Stary wrote: On Oct 11 10:38:04, be...@kroenchenstadt.de wrote: Hi, I've got to port some shell scripts which rely on env vars. One amongst those is $SSH_CLIENT. On OpenBSD 5.1 machines, I don't get what I'd assume to get: # echo $SSH_CLIENT It returns just a blank line. Are you in fact ssh-connected to the machine you are running this on? That is, are you running this in the sshd-spawned shell? -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachmentsCode Blue or Go Home!
Re: the idea of /fastboot ?
2012/10/11 Jiri B ji...@devio.us On Thu, Oct 11, 2012 at 09:29:50PM +0600, �л�� Шипи�ин wrote: there are http access logs for half an year. it's easier to rotate them on a single filesystem from many points of view, we also share it via samba (very tricky to share many chunks). and it is bad idea to mount access logs R/O. difficult to rotate. Bad design totally! I remember struggling with backup/restore times to satisfy SLA with huge filesystems having many files... And those were logs. One of proposals we did was to split filesystem into smaller ones and keep old logs on filesystems with read-only. Backup would be skipped, and restore (in this it was TSM) would be much faster if image would be used. j. they are not old logs. generally, today's log is access.log, yesterday's log is access.log.0 and so on. every rotate renames all the logs. older logs are removed. too many tricks with r/o filesystems. also, when dealing with rotating logs within single filesystem, it's cheap, data is not moved. and what if I want to move/rotate many-many-gigabytes logs in case of better design when there're many chunks ? I guess it is hard (and pretty useless) operation from filesystem point of view. ok, I can change configs of web-server to store logs in different location every day. you call it better design ??
Re: OpenBSD-5.1 hangs on Supermicro X9DR3-F
2012/10/11 Kenneth R Westerback kwesterb...@rogers.com On Thu, Oct 11, 2012 at 12:30:56PM +0600, ??? wrote: Hello! we recently installed OpenBSD/amd64 on Supermicro X9DR3-F, it hangs about 1 times a day. 5.1 does not understand i350 chip, so we put external Intel PRO/1000 MT (82574L) nic. we have ddb.panic=1, but no ddb appears on screen on hang. also, it says savecore: no core dump during boot. we tested RAM with memtest, so we do not suspect it for memory related issue. how can we diagnose those hangs ? is it ok to run 5.1 on X9DR3-F ? do I need to provide dmesg output ? any other kind of diagnostics ? Cheers, Ilya Shipitsin http://openbsd.org/report.html Ken it just hangs silently. from http://openbsd.org/report.html point of view it is useless. the only thing I have is dmesg output. so, I'm asking, how to collect information in case of silent hang behaviour it will be very useless bug report without that information. like blah-blah-blah, it hangs about once a day. silently
首個網上體育免費雜誌 《GO! SPORTS BUDDIES》
Having problems viewing this email? Please click here. For enquiry, please send email to i...@globalsportsexpo.com å¦ç¡æ³é±è®ä»¥ä¸çå §å®¹ï¼è«ææ¤ãå¦æä»»ä½æ¥è©¢è«é»éµè³i...@globalsportsexpo.com å¦ææ¨ä¸æ³æ¶å°æåç信件ï¼è«æé裡éå® Important Notice: Base on the Unsolicited Electronic Messages Ordinance,if you DO NOT want to receive any promotional email messages from us in the future, please kindly reply this e-mail for DELETION. If you would like to continue to receive our promotional email massages, you do not need to reply us.
Re: the idea of /fastboot ?
On 10/11/2012 01:15 PM, Илья Шипицин wrote: 2012/10/11 Jiri B ji...@devio.us On Thu, Oct 11, 2012 at 09:29:50PM +0600, Ã?лÑ?Ñ? ШипиÑ?ин wrote: there are http access logs for half an year. this is a trivial case where using multiple file systems works wonderfully. it's easier to rotate them on a single filesystem from many points of view, easier ONLY in the didn't have to think about anything sense. Not in the I'll be ripping my hair out over and over again sense. Doing it wrong is usually very easy...initially. we also share it via samba (very tricky to share many chunks). actually, no. /log shared here. Only this is shared. /log/a (full, ro) /b (full, ro) /c (partly full, rw) /d (empty, waiting to be used, rw) /curr - sym link to the active chunk -- in this case, /log/c /smb/[a..d] are individual file systems. and it is bad idea to mount access logs R/O. difficult to rotate. actually, your archival copies should be RO, if you are required to retain them for legal or security reasons. You don't want them changing...you probably want secure hashes made to prove they didn't change. Bad design totally! I remember struggling with backup/restore times to satisfy SLA with huge filesystems having many files... And those were logs. One of proposals we did was to split filesystem into smaller ones and keep old logs on filesystems with read-only. Backup would be skipped, and restore (in this it was TSM) would be much faster if image would be used. j. they are not old logs. generally, today's log is access.log, yesterday's log is access.log.0 and so on. every rotate renames all the logs. older logs are removed. too many tricks with r/o filesystems. also, when dealing with rotating logs within single filesystem, it's cheap, data is not moved. and what if I want to move/rotate many-many-gigabytes logs in case of better design when there're many chunks ? I guess it is hard (and pretty useless) operation from filesystem point of view. incorrect. ok, I can change configs of web-server to store logs in different location every day. you call it better design ?? First solution that leaps to my mind: move your logging to syslog, and send the syslog output to another machine. Now, the availability of your logging system doesn't impact the availability of your webserver. Set up your logging server to log to /log/curr. That's a symlink to a particular chunk of disk. At midnight, you have a little script run, it looks to see if you are within a couple days of being out of disk space on the current archive chunk, if so, you change the symlink (note files already open on the old one will stay open, be ready for that) to the next recording partition. (note: this symlink could also point to a directory within the partition). You can do this in a fixed rotation, I prefer to have a predefined list of use this next, as I've had to off-line storage that I wasn't likely to need, but needed to retain. Another solution: If you don't like remote syslogging (i.e., you absolutely have to retain every line of access, you can't tolerate losing log data when you reboot the log machine, and you don't want to use a buffering log agent app), you could simply scp off the old log files. Generate an sha256 hash for the file when it is rotated out, and when you see the hash, copy the file and its hash over to the log storage machine, verify the hash, and if it matches, delete it from the source machine. If it doesn't match, re-copy the file next time 'round. Really, simple stuff. Much simpler than trying to manage data in one big chunk. What do you plan to do when 7TB isn't enough to retain your required six months of data? How do you back it all up? How do you restore it when the array barfs? If you wish to upgrade your logging capability, build out a new logging system, point the systems at it, mothball the old system and when your retention period is over, wipe the old system (look ma! no copying terabytes of data!). I know some people trying to manage many terabytes of fast-moving data in one chunk. They started with FreeBSD and ZFS, but had problems with it (and a definite Linux bias), so they jumped to Linux, but again are finding Big File Systems are difficult. Would be so much easier for so many reasons if they just chunked their data across multiple file systems... Ah well... Nick.
Re: openbsd router performance (i know.. again)
Hi all, I'm waiting for the 5.2 to reinstall my routers/firewalls and see if things on my hardware improved. I'll also disable MP; how about 386 vs amd64? Is there any difference in terms of speed in managing interrupt and forwarding traffic? I've found a post from Henning telling that 386 is much better for routing/firewalling but it was 5-6 years ago and I'm sure things changed a lot Thanks for your help, can't wait to see my 5.2 cd on my desk :) Alessandro On Wed, Sep 26, 2012 at 5:31 PM, noah pugsley noah.pugs...@gmail.comwrote: What is your performance like with -current and no knob twisting? On Wed, Sep 26, 2012 at 4:45 AM, rik rikc...@gmail.com wrote: Hi, I'm a happy Openbsd user; we've beeing using it since 2001 as router/firewall in our datacenter facility (we host as ONG some no profit project and website). At the moment we're using a couple of SuperMicro with the following specs: OpenBSD 5.0 (GENERIC.MP) #59: Wed Aug 17 10:19:44 MDT 2011 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz (GenuineIntel 686-class) 2.98 GHz cpu0: FPU,V86,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,CNXT-ID,CX16,xTPR,PDCM real mem = 3890663424 (3710MB) avail mem = 3816964096 (3640MB) ppb3 at pci0 dev 28 function 4 Intel 82801G PCIE rev 0x01: apic 2 int 17 em0 at pci4 dev 0 function 0 Intel PRO/1000MT (82573E) rev 0x03: msi, address 00:30:xx:xx:xx:xx ppb4 at pci0 dev 28 function 5 Intel 82801G PCIE rev 0x01: apic 2 int 16 em1 at pci5 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: msi, address 00:30:xx:xx:xx:xx the netcard are on-board. Unfortunately we're a bit straggling with the performances as we have almost 100% interrupt with 110Mbps and 12k pps We've already increased net.inet.ip.ifq.maxlen to 500 in order to avoid packet loss and also disabling pf has no influence. Do you think these performances are fair and we have to upgrade to better hardware to have higher pps and Mpbs? Beside trying to upgrade to the last stable and not use MP we have no idea how to procede Thanks for your help Alessandro
Re: the idea of /fastboot ?
I'm struggling with 7Tb filesystems, it takes about 30 minutes to check them in case of cold reset. Too much. Very too much. and currently, no journals or anything else which could speed up 7Tb filesystems check ? man newfs, in particular the -i option. What does 'df -hi' say about your filesystem? # df -hi Filesystem SizeUsed Avail Capacity iused ifree %iused Mounted on /dev/sd0a 377G2.7G356G 1% 158121 24804949 1% / /dev/sd1a 6.7T331G6.1T 5%8041 228037269 0% /big That makes you prepared for having 228037269 inodes on that file systems. Also, that makes you eligible for a fsck that long. there are http access logs for half an year. Let's say half a year is 180 days; let's say you rotate daily. Am I right at thinking that you want to be prepared to keep and rotate the http logs of about 1266873 machines daily for the next 180 days? Since when have you accumulated the 8041 inodes that are there now? If you know in advance this filesystem is gonna store apache logs, how big is your typical daily log? From your numbers (331G occupied by 8041 files), it's about 44M per file. How big a block/fragment size do you use on this filesystem then?
Re: the idea of /fastboot ?
On 10/11/12 22:27, Nick Holland wrote: On 10/11/2012 01:15 PM, Илья Шипицин wrote: 2012/10/11 Jiri B ji...@devio.us On Thu, Oct 11, 2012 at 09:29:50PM +0600, Ã?лÑ?Ñ? ШипиÑ?ин wrote: there are http access logs for half an year. this is a trivial case where using multiple file systems works wonderfully. it's easier to rotate them on a single filesystem from many points of view, easier ONLY in the didn't have to think about anything sense. Not in the I'll be ripping my hair out over and over again sense. Doing it wrong is usually very easy...initially. we also share it via samba (very tricky to share many chunks). actually, no. /log shared here. Only this is shared. /log/a (full, ro) /b (full, ro) /c (partly full, rw) /d (empty, waiting to be used, rw) /curr - sym link to the active chunk -- in this case, /log/c /smb/[a..d] are individual file systems. and it is bad idea to mount access logs R/O. difficult to rotate. actually, your archival copies should be RO, if you are required to retain them for legal or security reasons. You don't want them changing...you probably want secure hashes made to prove they didn't change. Bad design totally! I remember struggling with backup/restore times to satisfy SLA with huge filesystems having many files... And those were logs. One of proposals we did was to split filesystem into smaller ones and keep old logs on filesystems with read-only. Backup would be skipped, and restore (in this it was TSM) would be much faster if image would be used. j. they are not old logs. generally, today's log is access.log, yesterday's log is access.log.0 and so on. every rotate renames all the logs. older logs are removed. too many tricks with r/o filesystems. also, when dealing with rotating logs within single filesystem, it's cheap, data is not moved. and what if I want to move/rotate many-many-gigabytes logs in case of better design when there're many chunks ? I guess it is hard (and pretty useless) operation from filesystem point of view. incorrect. ok, I can change configs of web-server to store logs in different location every day. you call it better design ?? First solution that leaps to my mind: move your logging to syslog, and send the syslog output to another machine. Now, the availability of your logging system doesn't impact the availability of your webserver. Set up your logging server to log to /log/curr. That's a symlink to a particular chunk of disk. At midnight, you have a little script run, it looks to see if you are within a couple days of being out of disk space on the current archive chunk, if so, you change the symlink (note files already open on the old one will stay open, be ready for that) to the next recording partition. (note: this symlink could also point to a directory within the partition). You can do this in a fixed rotation, I prefer to have a predefined list of use this next, as I've had to off-line storage that I wasn't likely to need, but needed to retain. Another solution: If you don't like remote syslogging (i.e., you absolutely have to retain every line of access, you can't tolerate losing log data when you reboot the log machine, and you don't want to use a buffering log agent app), you could simply scp off the old log files. Generate an sha256 hash for the file when it is rotated out, and when you see the hash, copy the file and its hash over to the log storage machine, verify the hash, and if it matches, delete it from the source machine. If it doesn't match, re-copy the file next time 'round. Really, simple stuff. Much simpler than trying to manage data in one big chunk. What do you plan to do when 7TB isn't enough to retain your required six months of data? How do you back it all up? How do you restore it when the array barfs? If you wish to upgrade your logging capability, build out a new logging system, point the systems at it, mothball the old system and when your retention period is over, wipe the old system (look ma! no copying terabytes of data!). I know some people trying to manage many terabytes of fast-moving data in one chunk. They started with FreeBSD and ZFS, but had problems with it (and a definite Linux bias), so they jumped to Linux, but again are finding Big File Systems are difficult. Would be so much easier for so many reasons if they just chunked their data across multiple file systems... Ah well... Nick. Only thing I find annoying is that I tend to run out of partitions... :-P /Alexander
Re: iscsid(8) and FreeNAS 8.2.0
On Thu, Oct 11, 2012 at 04:05:28PM +0700, Insan Praja SW wrote:
Hi Misc@,
Has anyone tried using OBSD iscsid(8) initiator and FreeNAS target?
I was trying to do it on amd64 -current but so far unsuccessful.
Best Regards,
Insan
iscsi.conf
--
target Disk2 {
enabled
normal
targetaddr 10.10.10.139
targetname iqn.2012-03.xxx.net:disk2
}
/var/log/messages
-
Oct 11 13:25:46 backend iscsid[11678]: fatal: vscsi_open: No such
file or directory
Funky. Did you try iscsid -dvn /dev/vscsi0 ?
I have never seen the open() call fail for vscsi. You could also try to
open /dev/vscsi0 with cat just to see if that fails too.
--
:wq Claudio
Re: tadpole sparc64 notebook running OpenBSD 5.1 dmesg
I'm feeling quite envious ;) ciao David On Thu, Oct 11, 2012 at 11:11 PM, Maxim Belooussov beloous...@gmail.com wrote: Hi all, It's kinda cool to see that wireless and sd card reader devices work. console is keyboard/display Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2012 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.1 (GENERIC) #130: Sun Feb 12 12:19:20 MST 2012 dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC real mem = 536870912 (512MB) avail mem = 514727936 (490MB) mainbus0 at root: SPARCLE 500SX (UltraSPARC-IIe 500MHz) cpu0 at mainbus0: SUNW,UltraSPARC-IIe (rev 1.4) @ 500 MHz cpu0: physical 16K instruction (32 b/l), 16K data (32 b/l), 256K external (64 b/l) psycho0 at mainbus0: pci108e,a001, impl 0, version 0, ign 7c0 psycho0: bus range 0-255, PCI bus 0 psycho0: dvma map c000-dfff pci0 at psycho0 ebus0 at pci0 dev 12 function 0 Altera EBus rev 0x01 flashprom at ebus0 addr 0-f not configured clock1 at ebus0 addr 0-1fff: mk48t59 ebus1 at pci0 dev 7 function 0 Acer Labs M1533 ISA rev 0x00 dma at ebus1 addr 0- not configured com0 at ebus1 addr 3f8-3ff ivec 0x2b: ns16550a, 16 byte fifo pckbc0 at ebus1 addr 60-67, 60-67 ivec 0x29 ivec 0x26 ivec 0x2a pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard pms0 at pckbc0 (aux slot) wsmouse0 at pms0 mux 0 TAD,wb-memstick at ebus1 addr 148-14f ivec 0xe not configured wbsd0 at ebus1 addr 358-35f ivec 0xa sdmmc0 at wbsd0 alipm0 at pci0 dev 17 function 0 Acer Labs M7101 Power rev 0x00: 74KHz clock iic0 at alipm0 dc0 at pci0 dev 1 function 0 Davicom DM9102 rev 0x31: ivec 0x7c6, address 00:00:83:ce:04:04 amphy0 at dc0 phy 1: DM9102 10/100 PHY, rev. 0 wi0 at pci0 dev 11 function 0 Intersil PRISM2.5 rev 0x01: ivec 0x7d4 wi0: PRISM2.5 ISL3874A(Mini-PCI) (0x8013), Firmware 1.0.7 (primary), 1.4.9 (station), address 00:90:96:72:1d:e8 ohci0 at pci0 dev 2 function 0 NEC USB rev 0x43: ivec 0x7dc, version 1.0 ohci1 at pci0 dev 2 function 1 NEC USB rev 0x43: ivec 0x7dd, version 1.0 ehci0 at pci0 dev 2 function 2 NEC USB rev 0x04: ivec 0x7de usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NEC EHCI root hub rev 2.00/1.00 addr 1 cbb0 at pci0 dev 3 function 0 TI PCI1225 CardBus rev 0x01: ivec 0x7da autri0 at pci0 dev 8 function 0 Acer Labs M5451 Audio rev 0x01: ivec 0x7e3 ac97: codec id 0x83847609 (SigmaTel STAC9721/23) ac97: codec features 18 bit DAC, 18 bit ADC, SigmaTel 3D audio0 at autri0 midi0 at autri0: 4DWAVE MIDI UART pciide0 at pci0 dev 13 function 0 Acer Labs M5229 UDMA IDE rev 0xc3: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using ivec 0x7cc for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: IC25N040ATMR04-0 wd0: 16-sector PIO, LBA48, 38154MB, 78140160 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TEAC, CD-224E, J.9A ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 machfb0 at pci0 dev 19 function 0 ATI Mach64 rev 0x64 machfb0: ATY,RageMobility, 1400x1050 wsdisplay0 at machfb0 mux 1: console (std, sun emulation), using wskbd0 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 NEC OHCI root hub rev 1.00/1.00 addr 1 usb2 at ohci1: USB revision 1.0 uhub2 at usb2 NEC OHCI root hub rev 1.00/1.00 addr 1 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 1 device 0 cacheline 0x10, lattimer 0x20 pcmcia0 at cardslot0 vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets bootpath: /pci@1f,0/ide@d,0/disk@0,0 root on wd0a (66dd7746863e7550.a) swap on wd0b dump on wd0b Max
Re: tadpole sparc64 notebook running OpenBSD 5.1 dmesg
same here ... i wish i could find an affordable tadpole on ebay ... :-) On Thu, Oct 11, 2012 at 11:36:07PM +0200, David Coppa wrote: I'm feeling quite envious ;) ciao David On Thu, Oct 11, 2012 at 11:11 PM, Maxim Belooussov beloous...@gmail.com wrote: Hi all, It's kinda cool to see that wireless and sd card reader devices work. console is keyboard/display Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2012 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.1 (GENERIC) #130: Sun Feb 12 12:19:20 MST 2012 dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC real mem = 536870912 (512MB) avail mem = 514727936 (490MB) mainbus0 at root: SPARCLE 500SX (UltraSPARC-IIe 500MHz) cpu0 at mainbus0: SUNW,UltraSPARC-IIe (rev 1.4) @ 500 MHz cpu0: physical 16K instruction (32 b/l), 16K data (32 b/l), 256K external (64 b/l) psycho0 at mainbus0: pci108e,a001, impl 0, version 0, ign 7c0 psycho0: bus range 0-255, PCI bus 0 psycho0: dvma map c000-dfff pci0 at psycho0 ebus0 at pci0 dev 12 function 0 Altera EBus rev 0x01 flashprom at ebus0 addr 0-f not configured clock1 at ebus0 addr 0-1fff: mk48t59 ebus1 at pci0 dev 7 function 0 Acer Labs M1533 ISA rev 0x00 dma at ebus1 addr 0- not configured com0 at ebus1 addr 3f8-3ff ivec 0x2b: ns16550a, 16 byte fifo pckbc0 at ebus1 addr 60-67, 60-67 ivec 0x29 ivec 0x26 ivec 0x2a pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard pms0 at pckbc0 (aux slot) wsmouse0 at pms0 mux 0 TAD,wb-memstick at ebus1 addr 148-14f ivec 0xe not configured wbsd0 at ebus1 addr 358-35f ivec 0xa sdmmc0 at wbsd0 alipm0 at pci0 dev 17 function 0 Acer Labs M7101 Power rev 0x00: 74KHz clock iic0 at alipm0 dc0 at pci0 dev 1 function 0 Davicom DM9102 rev 0x31: ivec 0x7c6, address 00:00:83:ce:04:04 amphy0 at dc0 phy 1: DM9102 10/100 PHY, rev. 0 wi0 at pci0 dev 11 function 0 Intersil PRISM2.5 rev 0x01: ivec 0x7d4 wi0: PRISM2.5 ISL3874A(Mini-PCI) (0x8013), Firmware 1.0.7 (primary), 1.4.9 (station), address 00:90:96:72:1d:e8 ohci0 at pci0 dev 2 function 0 NEC USB rev 0x43: ivec 0x7dc, version 1.0 ohci1 at pci0 dev 2 function 1 NEC USB rev 0x43: ivec 0x7dd, version 1.0 ehci0 at pci0 dev 2 function 2 NEC USB rev 0x04: ivec 0x7de usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NEC EHCI root hub rev 2.00/1.00 addr 1 cbb0 at pci0 dev 3 function 0 TI PCI1225 CardBus rev 0x01: ivec 0x7da autri0 at pci0 dev 8 function 0 Acer Labs M5451 Audio rev 0x01: ivec 0x7e3 ac97: codec id 0x83847609 (SigmaTel STAC9721/23) ac97: codec features 18 bit DAC, 18 bit ADC, SigmaTel 3D audio0 at autri0 midi0 at autri0: 4DWAVE MIDI UART pciide0 at pci0 dev 13 function 0 Acer Labs M5229 UDMA IDE rev 0xc3: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using ivec 0x7cc for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: IC25N040ATMR04-0 wd0: 16-sector PIO, LBA48, 38154MB, 78140160 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TEAC, CD-224E, J.9A ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 machfb0 at pci0 dev 19 function 0 ATI Mach64 rev 0x64 machfb0: ATY,RageMobility, 1400x1050 wsdisplay0 at machfb0 mux 1: console (std, sun emulation), using wskbd0 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 NEC OHCI root hub rev 1.00/1.00 addr 1 usb2 at ohci1: USB revision 1.0 uhub2 at usb2 NEC OHCI root hub rev 1.00/1.00 addr 1 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 1 device 0 cacheline 0x10, lattimer 0x20 pcmcia0 at cardslot0 vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets bootpath: /pci@1f,0/ide@d,0/disk@0,0 root on wd0a (66dd7746863e7550.a) swap on wd0b dump on wd0b Max -- Gilles Chehade https://www.poolp.org @poolpOrg
Re: ZTE USB MF636
Never mind folks... there was a PIN on the SIM card that I needed to enter. . On Thu, Oct 11, 2012 at 4:20 PM, Aaron Mason simplersolut...@gmail.com wrote: On Thu, Oct 11, 2012 at 4:15 PM, Aaron Mason simplersolut...@gmail.com wrote: Hi all A USB 3G modem whose model number adorns my subject line has fallen into my lap, and I sought to see if it would dial into Telstra's Next-G network from OpenBSD - its dmesg output is below: umsm0 at uhub0 port 1 configuration 1 interface 0 ZTE,Incorporated ZTE WCDMA Technologies MSM rev 2.00/0.00 addr 2 umsm0 detached umsm0 at uhub0 port 1 configuration 1 interface 0 ZTE,Incorporated ZTE WCDMA Technologies MSM rev 2.00/0.00 addr 2 ucom0 at umsm0 umsm1 at uhub0 port 1 configuration 1 interface 1 ZTE,Incorporated ZTE WCDMA Technologies MSM rev 2.00/0.00 addr 2 ucom1 at umsm1 umass0 at uhub0 port 1 configuration 1 interface 2 ZTE,Incorporated ZTE WCDMA Technologies MSM rev 2.00/0.00 addr 2 umass0: using SCSI over Bulk-Only scsibus3 at umass0: 2 targets, initiator 0 sd0 at scsibus3 targ 1 lun 0: ZTE, MMC Storage, 2.31 SCSI2 0/direct removable serial.19d20031567890ABCDEF umsm2 at uhub0 port 1 configuration 1 interface 3 ZTE,Incorporated ZTE WCDMA Technologies MSM rev 2.00/0.00 addr 2 ucom2 at umsm2 Despite following countless guides, I cannot for the life of me get it to establish a connection. At one point it would connect but then IPCP would timeout, now it simply and unhelpfully says Connect script failed - any ideas? My peer and chat files are below. Anybody in Australia who's managed to get connected to Telstra Next-G from OpenBSD (and one of the dongles they supply no less), please let me know which order I must chant and throw the chicken bones. # cat /etc/ppp/peers/telstra /dev/cuaU2 debug crtscts 921600 defaultroute noauth :10.64.64.64 connect '/usr/sbin/chat -v -f /etc/ppp/telstra.chat' # cat /etc/ppp/telstra.chat ABORT NO CARRIER ABORT NO DIALTONE ABORT ERROR ABORT NO ANSWER ABORT BUSY ABORT Username/Password Incorrect TIMEOUT 15 ATZ OK ATE1 #OK ATQ0V1E1S0=0C1D2+FCLASS=0 OK 'AT+CGDCONT=1,IP,telstra.internet' OK ATDT*99***1# TIMEOUT 30 CONNECT \d\c -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse An update - I followed the instructions at http://karlbsd.blogspot.com/2011/03/openbsd-nc4200-using-celcom-zte-mf190.html and got the following which may be more useful to those looking at this: # ppp Working in interactive mode Using interface: tun0 Warning: No default entry found in config file. ppp ON kangaskhan set device /dev/cuaU2 ppp ON kangaskhan set speed 384000 ppp ON kangaskhan show physical Name: deflink State: closed Device: N/A Link Type: interactive Connect Count: 0 Queued Packets: 0 Phone Number:N/A Defaults: Device List: /dev/cuaU2 Characteristics: 384000bps, cs8, no parity, CTS/RTS on CD check delay: device specific Connect time: 0:00:00 0 octets in, 0 octets out 0 packets in, 0 packets out Overall 0 bytes/sec ppp ON kangaskhan term deflink: Entering terminal mode on /dev/cuaU2 Type `~?' for help AT OK ATZ OK AT+CGDCONT=1,IP,telstra.internet' ERROR AT+CGDCONT=1,IP,telstra.internet ERROR ATDT*99# ERROR -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse
El curso que nadie se debe perder Ortografía y Redacción para Ejecutivos Cierre de Reservaciones
Apreciable Ejecutivo: TIEM de México Empresa Líder en Capacitación y Actualización de Capital Humano Debido al gran éxito obtenido, ponemos nuevamente a su disposición este excelente curso denominado: Ortografía y Redacción para Ejecutivos Ciudad de México, el día 16 de Octubre de 2012 Inscríbase 5 días antes de la fecha del Curso y obtenga un descuento del 15% con Inversión Inmediata No deje pasar esta oportunidad e Invierta en su Desarrollo Personal y Profesional Una parte importante de la imagen y la personalidad es la facilidad o dificultad con la cual nos expresamos y logramos despertar el interés de nuestro interlocutor o lector. Este importante curso le ofrece la oportunidad de desarrollar habilidades y técnicas que le permitirán tener una comunicación escrita eficaz para expresarse correctamente con claridad, fluidez y precisión, en los diferentes tipos de documentos que se requieran en su área de trabajo. Su participación le permitirá: Obtener un aprendizaje significativo de los acentos y las letras. Valorar la lectura como el medio para mejorar la ortografía y la redacción. Saber cómo desarrollar un estilo de redacción. Tips para actualizar y modernizar los escritos administrativos. Aprender a realizar escritos concisos y sencillos. Facilitar la tarea de trasmitir las ideas. Saber cómo utilizar correctamente los diferentes documentos. Evitar la repetición o la corrección de errores. Para mayor información, favor de responder este correo con los siguientes datos: Empresa: Nombre: Ciudad: Teléfono: O si lo prefiere comuníquese a los teléfonos: Del DF al 5611-0969 con 10 líneas Interior del País Lada sin Costo 01 800 900 TIEM (8436) Aceptamos todas las TDC y Débito. **Promoción: 3 meses sin Intereses pagando con American Express **Aplica solo con Inversión Normal ®Todos los Derechos Reservados ©2011 TIEM Talento e Innovación Empresarial de México Este Mensaje le ha sido enviado como usuario de TIEM de México o bien un usuario le refirió para recibir este boletín. Como usuario de TIEM de México, en este acto autoriza de manera expresa que TIEM de México le puede contactar vía correo electrónico u otros medios. Si usted ha recibido este mensaje por error, haga caso omiso de él y reporte su cuenta respondiendo este correo con el subject BAJABD Unsubscribe to this mailing list, reply a blank message with the subject UNSUBSCRIBE BAJABD Tenga en cuenta que la gestión de nuestras bases de datos es de suma importancia y no es intención de la empresa la inconformidad del receptor.
Re: OpenBSD-5.1 hangs on Supermicro X9DR3-F
On 2012-10-11, Илья Шипицин chipits...@gmail.com wrote: 2012/10/11 Kenneth R Westerback kwesterb...@rogers.com On Thu, Oct 11, 2012 at 12:30:56PM +0600, ??? wrote: Hello! we recently installed OpenBSD/amd64 on Supermicro X9DR3-F, it hangs about 1 times a day. 5.1 does not understand i350 chip, so we put external Intel PRO/1000 MT (82574L) nic. we have ddb.panic=1, but no ddb appears on screen on hang. also, it says savecore: no core dump during boot. we tested RAM with memtest, so we do not suspect it for memory related issue. how can we diagnose those hangs ? is it ok to run 5.1 on X9DR3-F ? do I need to provide dmesg output ? any other kind of diagnostics ? Cheers, Ilya Shipitsin http://openbsd.org/report.html Ken it just hangs silently. from http://openbsd.org/report.html point of view it is useless. Before reporting bugs/problems with released versions, go through this checklist: 1. First check for patches and notes regarding the release. 2. Next find out if there is a newer release available. 3. The last thing to check is for changes made between OpenBSD versions. check...for changes made between OpenBSD versions could mean dig through commit logs looking for something which might help, or it could mean try it with -current. another thing you could try is comparing i386/amd64. and when you test -current, you can compare using the i350 with using the external nic. (I only have limited experience of supermicro but some of the experience I do have tells me not to trust them to get things right every time when add-on cards are used). the only thing I have is dmesg output. 3. The OpenBSD kernel output. You can get this with the dmesg command, but it is possible that your dmesg output does not contain all the information that is captured in /var/run/dmesg.boot. If this is the case, include information from both. *Please include this in all bug ^^ reports.* so, I'm asking, how to collect information in case of silent hang behaviour it will be very useless bug report without that information. like blah-blah-blah, it hangs about once a day. silently you can add to this easily with a bit of testing and thinking about what information might be useful. blah-blah-blah, here is a dmesg, it hangs about once a day silently, this happens at various times | always the same time each day, it does | doesn't seem to be affected by high levels of network traffic / disk io / ... it does | doesn't happen if I leave the machine idle and disconnected from the network. basically try and think of more things which might possibly help, test them, then make a nice list of things which you've tried..
Re: Last i386 snapshot broken ?
On 2012-10-11, Yusof Khalid - FreeBSD / OpenBSD frysha...@gmail.com wrote: Hi, Confirm the iso is somehow got problem. I've tried with my virtualbox. Stuck at CD-ROM:E0 Loading /5.2/I386/CDBOOT As Ken mentioned, You seem to have hit something in the current effort to improved the boot blocks. Wait a day or so and try the latest snapshot then. If this still happens on a new snap (e.g. files dated from 12-Oct onwards; not yet biult I think...) then this might be useful information.
Re: iscsid(8) and FreeNAS 8.2.0
Hi all,
On Fri, 12 Oct 2012 04:18:31 +0700, Claudio Jeker
cje...@diehard.n-r-g.com wrote:
On Thu, Oct 11, 2012 at 04:05:28PM +0700, Insan Praja SW wrote:
Hi Misc@,
Has anyone tried using OBSD iscsid(8) initiator and FreeNAS target?
I was trying to do it on amd64 -current but so far unsuccessful.
Best Regards,
Insan
iscsi.conf
--
target Disk2 {
enabled
normal
targetaddr 10.10.10.139
targetname iqn.2012-03.xxx.net:disk2
}
/var/log/messages
-
Oct 11 13:25:46 backend iscsid[11678]: fatal: vscsi_open: No such
file or directory
Funky. Did you try iscsid -dvn /dev/vscsi0 ?
I have never seen the open() call fail for vscsi. You could also try to
open /dev/vscsi0 with cat just to see if that fails too.
$ sudo iscsid -dvn /dev/vscsi0
startup
iscsid: unknown user _iscsid
$ sudo cat /dev/vscsi0
cat: /dev/vscsi0: Operation not supported by device
$
Thanks,
Insan Praja SW
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
Re: the idea of /fastboot ?
On Wed, Oct 10, 2012 at 02:44:32PM +0600, ??? wrote: ?, 10 ??? 2012 ?. Nick Holland ?: On 10/09/2012 12:55 PM, ??? wrote: Hello! I'm investigating /etc/rc script. And I found the following there: if [ -e /fastboot ]; then echo Fast boot: skipping disk checks. elif [ X$1 = Xautoboot ]; then echo Automatic boot in progress: starting file system checks. hmm... if I put /fastboot, no filesystem will be checked ? so says the code, yes. how it supposed to work for non-nfs filesystems ? properly? they'll be not checked, too? I think I'm missing part of your question...but the answer is in the code, which you are already reading. I meant, in case of NFS you don't need to fsck at all. However, there's no need to indicate such case. mount already knows if there nfs stuff. Often, on my diskless client (every mount is NFS), I'll put an immuable /fastboot on the server in the NFS root directory. It saves the machine from downloading and executing one small program that would do nothing. On some extremely slow arch, there's a noticable difference. (But OpenBSD discontinuated that arch. Still bitter about it.) You don't normally fsck an nfs mount (that advisory has always satisfied my curiosity sufficiently, I've never actually tried it. I probably should). fsck does not do the actual file system checks. That's the job for the fsck_FILESYSTEMTYPE programs. Only fsck_ffs, fsck_ext2fs and fsck_msdos exists on OpenBSD. Every other type of filesystem can not be checked.
