Re: how normal is this ?
On Sun, Jun 10, 2012 at 7:43 PM, Francois Pussault fpussa...@contactoffice.fr wrote: From: Tomas Bodzar tomas.bod...@gmail.com Sent: Sun Jun 10 19:19:57 CEST 2012 To: Francois Pussault fpussa...@contactoffice.fr Subject: Re: how normal is this ? On Sun, Jun 10, 2012 at 7:05 PM, Francois Pussault fpussa...@contactoffice.fr wrote: hi all, here is my default memory setup : hw.machine=i386 hw.model=Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz (GenuineIntel 686-class) [..] hw.physmem=2136907776 hw.usermem=2062499840 hw.ncpufound=2 hw.allowpowerdown=1 top info : Memory: Real: 437M/956M act/tot Free: 1039M Cache: 376M Swap: 0K/2047M for some reasons, I don't know yet, some applications securely answer Cannot allocate memory until memory in Real decrease to about 300M/956M. (...even if I guess those applications are written with foot...this is strange). but I have 1039M free some swap free so why that ? Is this range of memory protected or reserved to something ? Any method to force memory Real to be higher have less Free memory in default should be a solution too.. ulimit -a man login.conf on i386 max 1GB/process (~700MB real memory/process) per design check /var/log/messages for some uvm errors thanks Regards # ulimit -a time(cpu-seconds) unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 2097152 stack(kbytes) 8192 lockedmem(kbytes) 680574 memory(kbytes) 2035316 nofiles(descriptors) 128 processes 1310 # I don't see any thing anormal in dmesg I use the default login.conf setup. So i guess this is due a linux binary bad coded so not very well supported even with kern.emul.linux=1 # enable running Linux binaries line uncommented in sysctl.conf... It's not default, because such a datasize is not possible on i386. It will not work. So something modified that (either you or that app you're trying). because this binary runs well in a qemu Virtual Machine running debian... so I guess it is application issue then problem is solved because is is isolated.
filesystem mount sync and async
Hello, I have not found any information in the man page or otherwise that conflicts with the bellow, it just does not seem like the following should be possible: # grep home /etc/fstab 424dc014a22db950.f /home ffs ro,nodev,nosuid,noatime # mount|grep home /dev/sd0f on /home type ffs (local, noatime, nodev, nosuid, read-only) # mount -uwo async /home # mount|grep home /dev/sd0f on /home type ffs (asynchronous, local, noatime, nodev, nosuid) # mount -uro sync /home # mount|grep /home /dev/sd0f on /home type ffs (asynchronous, local, noatime, nodev, nosuid, read-only, synchronous) I am however not familiar with the intricacies of filesystems, which probably makes me wrong. At least posting this will make my curiosity go away.
Re: filesystem mount sync and async
hOn Mon, Jun 11, 2012 at 09:35:56AM +0300, Dimitrios Moustos wrote: Hello, I have not found any information in the man page or otherwise that conflicts with the bellow, it just does not seem like the following should be possible: # grep home /etc/fstab 424dc014a22db950.f /home ffs ro,nodev,nosuid,noatime # mount|grep home /dev/sd0f on /home type ffs (local, noatime, nodev, nosuid, read-only) # mount -uwo async /home # mount|grep home /dev/sd0f on /home type ffs (asynchronous, local, noatime, nodev, nosuid) # mount -uro sync /home # mount|grep /home /dev/sd0f on /home type ffs (asynchronous, local, noatime, nodev, nosuid, read-only, synchronous) I am however not familiar with the intricacies of filesystems, which probably makes me wrong. At least posting this will make my curiosity go away. The async flag concerns metadata i/o. The sysnc flags concerns regular data i/o. The two flags are separate, the negations of these flags are noasycn and nosync respectively. Yes, this is confusing, but playing with these flags is for experts only. -Otto
Re: filesystem mount sync and async
On 2012-06-11, Dimitrios Moustos dot...@dotbit.ro wrote: Hello, I have not found any information in the man page or otherwise that conflicts with the bellow, it just does not seem like the following should be possible: # grep home /etc/fstab 424dc014a22db950.f /home ffs ro,nodev,nosuid,noatime # mount|grep home /dev/sd0f on /home type ffs (local, noatime, nodev, nosuid, read-only) # mount -uwo async /home # mount|grep home /dev/sd0f on /home type ffs (asynchronous, local, noatime, nodev, nosuid) # mount -uro sync /home # mount|grep /home /dev/sd0f on /home type ffs (asynchronous, local, noatime, nodev, nosuid, read-only, synchronous) I am however not familiar with the intricacies of filesystems, which probably makes me wrong. At least posting this will make my curiosity go away. async/noasync and sync/nosync are different things. From GNATS PR kernel/6452: Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: thib State-Changed-When: Mon Apr 18 12:35:11 MDT 2011 State-Changed-Why: The async and sync mount options are not mutually exclusive. By default, metadata is written out synchronously while data is written out either synchronously or delayed. The async options allows metadata to be written out asynchronously, as well as data. The sync options forces all data io to be written out synchronously, but has no effect on metadata. So, what you end up with if you filesystem is mounted with both options set, is that metadata will be written out async, but data sync. Granted, this isn't very clear (even the kernel side is a bit murky), but this isn't a bug either.
Re: About wine ?
On Mon, Jun 11, 2012 at 10:35:50AM +0800, z_axis wrote: I know wine port has been stopped. I wonder whether or not it is applicable to port wine to OpenBSD ? Wine works great on FreeBSD, why cannot it run on OpenBSD ? Somebody has to resolve the issues in the code :) Take it from ports in Attic, IIRC. If you need Windoze, install an ESXi box and voila. jirib
Reactivar su cuenta
Centro de Seguridad - BBVA net  Nos pusimos en contacto por correo electrónico con usted hace poco para pedirle ayuda en la resolución de un problema en su cuenta de BBVA. Su cuenta aún está limitada temporalmente porque no hemos tenido noticias suyas. Queremos colaborar con usted para normalizar la situación de su cuenta lo antes posible.  Cual es el problema?http://www.bbva.es/TBLS/segmento/cuenta/actualizar/index.jsp  Hemos observado una actividad inusual en la tarjeta de crédito vinculada a su cuenta BBVA.  Cómo puede ayudar?  Suele ser muy fácil. En la mayorÃa de las ocasiones, sólo necesitamos un poco más de información sobre su cuenta o sobre sus datos personales para actualizar su cuenta.Para ayudarnos y ver qué funcionalidades están limitadas en su cuenta hasta que se resuelvael problema, inicie sesión en su cuenta y visite el Centro de Ayuda Centro de Ayuda:http://www.bbva.es/TBLS/segmento/centro-ayuda/index.jsp  Para ponerse en contacto con nosotros, inicie sesión en su cuenta y haga clic en Contactar en la parte inferior de cualquier página.  © BBVA net S.A 2012Todos los derechos reservados.
Re: About wine ?
On Mon, Jun 11, 2012 at 10:35:50AM +0800, z_axis wrote: I know wine port has been stopped. I wonder whether or not it is applicable to port wine to OpenBSD ? Wine works great on FreeBSD, why cannot it run on OpenBSD ? Somebody has to resolve the issues in the code :) Take it from ports in Attic, IIRC. If you need Windoze, install an ESXi box and voila. I personally don't care for WINE but would really like to know more more about virtualization options on OpenBSD hosts; VirtualBox is the only reason I need to keep some Debian hosts around (that and my secret crush on Larry Ellison). F.ex. compat_linux is x86-only and it's not clear how it plays with chroot, which I know is imperfect, but saying it can run Linux Skype! without some sandboxing doesn't seem too safe. Qemu seems like a good project given the flack it gets on wikipedia (very Cartesian, I know), how well can it run on OpenBSD? what's holding it back? which kernel improvements/patches will help? if all VM is counter-security, why? Where do we come from and is there life after death? I demand to know. -- p
Re: About wine ?
On Mon, Jun 11, 2012 at 03:49:21PM +0200, Peter Laufenberg wrote: I personally don't care for WINE but would really like to know more more about virtualization options on OpenBSD hosts; VirtualBox is the only reason I need to keep some Debian hosts around (that and my secret crush on Larry Ellison). F.ex. compat_linux is x86-only and it's not clear how it plays with chroot, which I know is imperfect, but saying it can run Linux Skype! without some sandboxing doesn't seem too safe. Qemu seems like a good project given the flack it gets on wikipedia (very Cartesian, I know), how well can it run on OpenBSD? what's holding it back? which kernel improvements/patches will help? if all VM is counter-security, why? Where do we come from and is there life after death? I demand to know. Why don't you first search archives? jirib
Re: OpenBSD on minimac
Jan Stary h...@stare.cz writes: On Jun 10 13:42:28, Martin Pieuchot wrote: On 10/06/12(Sun) 12:51, Jan Stary wrote: I got this Mac Mini on my hands, and I would like to install current/macppc on it. According to ... I only have the minimac, not the other apple paraphernalia; in particular, I don't have an apple keyboard, so there's no way for me to press cmd+alt+o+f. According to INSTALL.macppc, it's Command + Option + O + F actually; is there a way to do that on a non-apple keyboard? I have the usual PC keyboard attached to it via USB. I'm not sure why, but I've found that my Happy Hacker usb keyboard will not get me to the openfirmware prompt on my powermac3,4 when holding its equivalent to [Cmd Option O F]. I gave up on it for that purpose and bought a used Apple keyboard I keep in the closet for when I need to do that. ANyway, even a non-apple keyborad makes it possibel, obviously, to boot while holding [C] pressed. What could be the reason it doesn't work? It's not obvious to me that [C] should work with a non-Apple keyboard because I don't know the reason [Cmd Option O F] doesn't work. If I remember rightly, the happy hacker had toggle switches for PC vs. Mac mode which I tried without success, so I wonder if it's not something more than the keyboard not sending the right key code for cmd or option. e.g. do keyboards need to have their state initialized in some way at start up? Does OpenBSD do this correctly while Open Firmware has no clue what it's talking to? I would try [C] on mine to see if it works with the Happy Hacker, but I don't think Apple had introduced that feature yet when the Digital Audio PowerMac came out (hey, my computer's still newer than my car and twice as new as my bicycle so stop yer snickering). - Mike
Re: setsockopt question
On 2012-06-10 11:26, Peter J. Philipp wrote:
+ if (setsockopt(udp[i], IPPROTO_IPV6,
+ IPV6_HOPLIMIT,on, sizeof(on)) 0) {
s/IPV6_HOPLIMIT/IPV6_RECVHOPLIMIT/
RFC 3542 for more info.
Simon
openntpd siginfo status
Recently I made the switch from ntp to openntpd. Seemingly random
memory write errors by the ntp daemon finally convinced me that ntp had
become too bloated for the reliability I desired.
So far, my experience with openntpd has been very good. But I missed
some of the status reporting ability of ntp (e.g, the 'ntpq -c peer'
command). As part of the daily.local script, I like to capture the
openntpd SIGINFO status, but somehow 4 out of 4 peers valid was not
the level of information I wanted. I decided to offer my first code
patch here.
In this patch, I had the following goals:
- no changes to existing time-computation algorithms and data
structures
- no new include files required for compiling
- no new libraries required for linking
- no changes to any files used by make
- treat current openntpd data structures as read-only
- leave current status messages unchanged, as some folk may be using
log file scanners
- log the new status informaiton as info priority to avoid cluttering
more important log files
- within the above constraints, provide useful status of openntpd's
interaction with the peers
This is the output you will see in daemon.log when a SIGINFO signal is
received (presuming that syslog puts daemon.info into that file)
=== start of output
ntpd[1503]: 4 out of 4 peers valid
ntpd[1503]: clock is synced, stratum 3
ntpd[1503]: peer
ntpd[1503]:wt tl st next poll offset delay
jitter
ntpd[1503]: 10.20.1.1 ntp.89lr.home
ntpd[1503]: 1 10 3 688s 1550s 0.985mS 0.346mS
0.081mS
ntpd[1503]: 64.113.32.10 from pool 1.us.pool.ntp.org
ntpd[1503]: 1 10 2 721s 1609s 6.404mS51.893mS
2.624mS
ntpd[1503]: 67.18.187.111 from pool 1.us.pool.ntp.org
ntpd[1503]: 1 10 2 684s 1533s-2.835mS80.682mS
4.734mS
ntpd[1503]: 208.53.158.34 from pool 1.us.pool.ntp.org
ntpd[1503]: 1 10 2 641s 1547s-0.624mS41.273mS
0.388mS
=== end of output
where the columns for each peer are: weight, trustlevel, stratum, time
remaining to the next poll, poll interval, local clock's offset from
the peer's clock, network delay, jitter in the network delay.
With the above goals in mind, I offer the following patch for 5.1.
=== begin file ntp_5-1.patch
Apply by doing:
cd /usr/src
patch -p0 ntp_5-1.patch
And then rebuild and install ntpd:
cd /usr/src/usr.sbin/ntpd
make obj
make depend
make
make install
And finally, run the new version:
/etc/rc.d/ntpd restart
===
--- usr.sbin/ntpd/ntp.c
+++ usr.sbin/ntpd/ntp.c Sun Jun 10 15:07:30 2012
@@ -761,23 +761,103 @@
}
lastreport = now;
if (peer_cnt 0) {
- log_warnx(%u out of %u peers valid, peer_cnt - badpeers,
- peer_cnt);
+
+ log_warnx(%u out of %u peers valid,
+ peer_cnt - badpeers, peer_cnt);
+
+ if (conf-status.synced == 1)
+ log_info(clock is synced, stratum %u,
+ conf-status.stratum);
+ else log_info(clock is unsynced);
+
+ log_info(peer);
+ log_info( wt tl st next poll offset
+ delay jitter);
+
TAILQ_FOREACH(p, conf-ntp_peers, entry) {
+ const char *a = not resolved;
+ const char *pool = ;
+
+ if (p-addr)
+ a = log_sockaddr(
+ (struct sockaddr *)p-addr-ss);
+ if (p-addr_head.pool)
+ pool = from pool ;
+
+ log_info(%s %s%s %s,
+ a, pool, p-addr_head.name,
+ print_rtable(p-rtable) );
+
if (p-trustlevel TRUSTLEVEL_BADPEER) {
- const char *a = not resolved;
- const char *pool = ;
- if (p-addr)
- a = log_sockaddr(
- (struct sockaddr *)p-addr-ss);
- if (p-addr_head.pool)
- pool = from pool ;
log_warnx(bad peer %s%s (%s) %s,
pool, p-addr_head.name, a,
print_rtable(p-rtable));
}
+ else {
+ u_int8_t shift, best, validdelaycnt, jittercnt;
+ double avg_offset, avg_delay, jitter;
+
+ validdelaycnt = best = 0;
+ avg_offset = avg_delay = 0.0;
+ for (shift = 0; shift OFFSET_ARRAY_SIZE;
+
Writing Prize 1,000,000 yen, ongoing now!
Writing Prize 1,000,000 yen, ongoing now! If you contribute articles, brilliant enouf, to the Guest Book below, then, you'll have chances to get about 100,000 to 800,000 yen as a total, as a prize. Guest Book http://jbbs.livedoor.com/bbs/read.cgi/study/3729/1088236761 Why is this world unhappy? http://www2.tba.t-com.ne.jp/a-z/english/index.htm
◆『万有サロン』書き込み大賞・総額100万円◆
￥￥￥『万有サロン』書き込み大賞・総額100万円 この掲示板に優秀な書き込みをして、総額100万円の賞金をゲットしよう！ (*^^)v 万有サロン http://jbbs.livedoor.jp/study/3729/ 書き込み大賞の詳細 http://jbbs.livedoor.jp/bbs/read.cgi/study/3729/1069922074/78- 書き込み大賞の詳細(資料倉庫内) http://www2.tba.t-com.ne.jp/a-z/omake/banyu/taisho.htm また、あらゆる疑問に関する質問を、携帯電話でも受け付けています。 電話番号 080-4437-4187 ￥
Re: About wine ?
On Mon, Jun 11, 2012 at 3:49 PM, Peter Laufenberg open...@laufenberg.ch wrote: Qemu seems like a good project given the flack it gets on wikipedia (very Cartesian, I know), how well can it run on OpenBSD? what's holding it back? which kernel improvements/patches will help? if all VM is counter-security, why? Where do we come from and is there life after death? I demand to know. Qemu is fine on OpenBSD, but slow, because for some time already it's without KVM in OpenBSD. Probably one of the reasons for www.bitrig.org I see. Lofty goals with a questionable fork rationale. Maybe removing doc references to floppies and tapes would improve the modernity perception. From Jiri: Why don't you first search archives? - digressions into exotic sports cars? - marketing plugs? - out of date? -- p
Re: OpenBSD on minimac
I got this Mac Mini on my hands, and I would like to install current/macppc on it. According to http://www.openbsd.org/macppc.html#hardware the following MicMini's are supported: Mac mini (PowerMac10,1) Mac mini (Late 2005 (PowerMac10,2)) My model number is A1103. A quick search suggests that it's the same as PowerMac10,1 - is that correct? If so, it should be supported. My problem is it won't boot from install51.iso. I hold the [c] key while booting up, but it still boots into the MacOSX 10.5.8 that is currently installed on the disk, instead of booting from the CD. An other way to boot from the CD would be to get into the openfirmware prompt holding cmd+alt+O+F when your machine starts, then type: boot cd:,\\:tbxi I only have the minimac, not the other apple paraphernalia; in particular, I don't have an apple keyboard, so there's no way for me to press cmd+alt+o+f. According to INSTALL.macppc, it's Command + Option + O + F actually; is there a way to do that on a non-apple keyboard? I have the usual PC keyboard attached to it via USB. Win+Alt+O+F then. This get me to the Open Firmware prompt - thank you. In Open Firmware, I am trying to boot off the install CD. Strangely, boot cd:,ofwboot /5.1/macppc/bsd.rd doesn't work: MAC-PARTS: bad partition can't OPEN cd:,ofwboot Can't open device or file ok but boot hd:,ofwboot /5.1/macppc/bsd.rd does boot the CD (note the diference - cd vs hd). I understand that hd and cd are just devaliases; in my case, hd /pci@f400/ata-6@d/disk@0 cd /pci@f400/ata-6@d/disk@1 Does that mean that those device aliases are somehow mixed up? Anyway, once started, the installation goes through smoothly. Unlike ofw, the install script recognizes 'cd' as the CD correctly (when choosing where to install the sets from). I chose MBR instead of HFS, as I do not intend to dual boot MacOSX. Now, my last problem is that I cannot boot the installed /bsd. I understand that OFW needs to be configured to boot it, but I run into the same problem as during the installation: the expected boot hd:,ofwboot /bsd apparently tries to boot from the CD - it starts spinning, and fails with open /pci@f400/ata-6@d/disk@0/bsd: No such file or directory I have tried boot ide0:,ofwboot /bsd boot ide1:,ofwboot /bsd boot ultra0:,ofwboot /bsd boot ultra1:,ofwboot /bsd - all of them fail with Can't open device or file. The only thing that I can get to boot is boot hd:,ofwboot /5.1/macppc/bsd i.e., the kernel from the install CD. Once booted, the system is there as I installed it and runs fine. Obviously, I would like to boot the /bsd I installed on disk. Isuppose this is an Open Firmware problem rather then an OpenBSD problem. Namely, Idon't know how to address the harddisk I installed on from within open firmware. Can someone enlighten me please? Jan [ using 496832 bytes of bsd ELF symbol table ] console out [ATY,RockHopper2_A]console in [keyboard] , using USB using parent ATY,RockHopper2Paren:: memaddr 9800 size 800, : consaddr 9c008000, : ioaddr 9002, size 2: memtag 8000, iotag 8000: width 1440 linebytes 1536 height 900 depth 8 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 uvm_km_kmem_grow: grown to 0xee00 OpenBSD 5.1-current (GENERIC) #201: Wed Jun 6 14:56:55 MDT 2012 dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC real mem = 1073741824 (1024MB) avail mem = 1032257536 (984MB) mainbus0 at root: model PowerMac10,2 cpu0 at mainbus0: 7447A (Revision 0x102): 1499 MHz: 512KB L2 cache mem0 at mainbus0 spdmem0 at mem0: 1GB DDR SDRAM non-parity PC3200CL3.0 memc0 at mainbus0: uni-n hw-clock at memc0 not configured kiic0 at memc0 offset 0xf8001000 iic0 at kiic0 mpcpcibr0 at mainbus0 pci: uni-north, Revision 0xff pci0 at mpcpcibr0 bus 0 pchb0 at pci0 dev 11 function 0 Apple UniNorth AGP rev 0x00 vgafb0 at pci0 dev 16 function 0 ATI Radeon 9200 rev 0x01, mmio wsdisplay0 at vgafb0 mux 1: console (std, vt100 emulation) mpcpcibr1 at mainbus0 pci: uni-north, Revision 0x5 pci1 at mpcpcibr1 bus 0 pchb1 at pci1 dev 11 function 0 Apple UniNorth PCI rev 0x00 bwi0 at pci1 dev 18 function 0 Broadcom BCM4318 rev 0x02: irq 52, address 00:11:24:bf:cb:2a macobio0 at pci1 dev 23 function 0 Apple Intrepid rev 0x00 openpic0 at macobio0 offset 0x4: version 0x4614 feature 3f0302 LE macgpio0 at macobio0 offset 0x50 modem-reset at macgpio0 offset 0x1d not configured modem-power at macgpio0 offset 0x1c not configured macgpio1 at macgpio0 offset 0x9 irq 47 programmer-switch at macgpio0 offset 0x11 not configured gpio5 at macgpio0 offset 0x6f not configured gpio6 at macgpio0
Re: setsockopt question
On Mon, Jun 11, 2012 at 12:16:28PM -0400, Simon Perreault wrote:
On 2012-06-10 11:26, Peter J. Philipp wrote:
+if (setsockopt(udp[i], IPPROTO_IPV6,
+IPV6_HOPLIMIT,on, sizeof(on)) 0) {
s/IPV6_HOPLIMIT/IPV6_RECVHOPLIMIT/
RFC 3542 for more info.
Simon
Awesome, it works now! Thank you!
-peter
Re: About wine ?
On Mon, Jun 11, 2012 at 1:30 PM, Peter Laufenberg open...@laufenberg.ch wrote: On Mon, Jun 11, 2012 at 3:49 PM, Peter Laufenberg open...@laufenberg.ch wrote: Qemu seems like a good project given the flack it gets on wikipedia (very Cartesian, I know), how well can it run on OpenBSD? what's holding it back? which kernel improvements/patches will help? if all VM is counter-security, why? Where do we come from and is there life after death? I demand to know. Qemu is fine on OpenBSD, but slow, because for some time already it's without KVM in OpenBSD. Probably one of the reasons for www.bitrig.org I see. Lofty goals with a questionable fork rationale. Maybe removing doc references to floppies and tapes would improve the modernity perception. they also removed code makefiles really arent set up for mass edits. it's hard to do static checks From Jiri: Why don't you first search archives? - digressions into exotic sports cars? - marketing plugs? - out of date? -- p
Re: OpenBSD on minimac
I understand that hd and cd are just devaliases; in my case, hd /pci@f400/ata-6@d/disk@0 cd /pci@f400/ata-6@d/disk@1 Does that mean that those device aliases are somehow mixed up? Well, given the dmesg says... cd0 at scsibus0 targ 0 lun 0: MATSHITA, DVD-R UJ-825, DAND ATAPI 5/cdrom removable wd0 at wdc1 channel 0 drive 1: ST9808211A ... I'd say they are. Obviously, I would like to boot the /bsd I installed on disk. Isuppose this is an Open Firmware problem rather then an OpenBSD problem. Namely, Idon't know how to address the harddisk I installed on from within open firmware. Can someone enlighten me please? Try: setenv boot-device /pci@f400/ata-6@d/disk@1:,ofwboot Miod
Taller de Manejo Óptimo de la Ventanilla Única de Comercio Exterior 314034
314034 [IMAGE] Taller de Manejo Óptimo de la Ventanilla Única de Comercio Exterior 18 de Junio, Cd. de México. Un taller totalmente práctico guiado por un experto. Optimice sus procesos y ahorre dinero con esta práctica herramienta! ¡Reciba la información completa, Inscríbase y Capacítese! Por favor responda este e-mail con los datos siguientes. Empresa, Nombre, Teléfono, Email, Número de Interesados En breve recibirá temario, reseña de expositor y tarifas. Si lo prefiere comuníquese a los teléfonos donde con gusto uno de nuestros ejecutivos le atenderá. Teléfonos: (0133) 8851-2365, (0133) 8851-2741 con más de 10 líneas. Pms Capacitación Efectiva de México es una empresa Registrada ante la STPS Trabajamos con expertos en la materia para poder brindar herramientas tácticas, vanguardistas y de fácil aplicación. Síguenos en Twitter@pmscapacitacion o bien en Facebook PMS de México Tip del día! Planea: Evita los problemas de vivir al momento y crear estrategias de último momento. Planea tus objetivos, elige un rumbo y mantente. Anticipa posibles causales de emergencia y diseña planes de contingencia previos que permitan conocer rutas a seguir. Esto ayudará a crear metas en su compañía, compartirlas con su equipo y anticipar obstáculos. Copyright (C) 2011, PMS Capacitación Efectiva de México S.C. Derechos Reservados. E-Mail MARKETING SERVICE POWERED BY MEDIAMKTOOLS. Este Mensaje ha sido enviado a misc@openbsd.org como usuario de Pms de México o bien un usuario le refirió para recibir este boletín. Como usuario de Pms de México, en este acto autoriza de manera expresa que Pms de México le puede contactar vía correo electrónico u otros medios. ALTO, si en esta ocasión la información recibida no fue de su interés pero desea recibir información personalizada en relación a otros temas favor de indicarlo. Si usted ha recibido este mensaje por error, haga caso omiso de el y de antemano una sincera disculpa por la molestia, reporte su cuenta respondiendo este correo con el subject BAJAVUCE Unsubscribe to this mailing list, reply a blank message with the subject UNSUBSCRIBE BAJAVUCE Tenga en cuenta que la gestión de nuestras bases de datos es de suma importancia para nosotros y no es intención de la empresa la inconformidad del receptor, nuestra intención es promover herramientas de utilidad para el [demime 1.01d removed an attachment of type image/jpeg which had a name of imagecomercio001.jpg]
ospf6d.conf -- Man page discrepancy
Running 5.1-RELEASE. According to ospf6d.conf(5): *router-dead-time* /seconds/ Set the router dead time, a.k.a. neighbor inactivity timer. The default value is 40 seconds; valid range is 2-2147483647 seconds. When a neighbor has been inactive for router-dead-time its state is set to DOWN. Neighbors that have been inactive for more than 24 hours are completely removed. However, when I try to set this value to, say, 60 seconds (well within the range specified above), I get the following when starting ospf6d: /etc/ospf6d.conf:13: router-dead-time out of range (2-65535) Just thought I'd bring this up, see if anyone could shed some light on this. -- Thanks, Andrew Klettke Systems Admin Optic Fusion 253-830-2943
Re: ospf6d.conf -- Man page discrepancy
Hi Andrew On Mon, Jun 11, 2012 at 02:10:51PM -0700, Andrew Klettke wrote: Running 5.1-RELEASE. According to ospf6d.conf(5): *router-dead-time* /seconds/ Set the router dead time, a.k.a. neighbor inactivity timer. The default value is 40 seconds; valid range is 2-2147483647 seconds. When a neighbor has been inactive for router-dead-time its state is set to DOWN. Neighbors that have been inactive for more than 24 hours are completely removed. However, when I try to set this value to, say, 60 seconds (well within the range specified above), I get the following when starting ospf6d: /etc/ospf6d.conf:13: router-dead-time out of range (2-65535) Just thought I'd bring this up, see if anyone could shed some light on this. ospf6d started more or less as a copy of ospfd, and this is obviously a leftover in the manpage. dead_interval in parse.y is of type u_int32_t in ospfd and u_int16_t (65535) in ospf6d. The commit logs explains this: The router dead_interval switched from 32bit to a 16bit value in OSPFv3. I looked at this only out of curiosity and I'm not a dev, nor do I know much about ospfd. So take this with caution :-) Cheers Robert
Solid state disk geometry
Dear Mailing Listeners, Let me know, please, whether it makes sense to modify disk geometry for solid state disks? Which meaning have the default values of cylinders, heads, and sectors for these devices? As an example, here are my sd1 data: # fdisk sd1 Disk: sd1 geometry: 7783/255/63 [125045424 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 1 2 - 7782 254 63 [ 64: 125033831 ] OpenBSD Are there any disktab entries available more suitable for usual models of solid state disks? At least it seemed reasonable to me to take multiples of 64 blocks for the partition sizes and offsets: # disklabel sd1 # /dev/rsd1c: type: SCSI disk: SCSI disk label: SSDSA2SH064G1GC duid: 78faa8282eb6f8fa flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 7783 total sectors: 125045424 boundstart: 64 boundend: 125033895 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 2097152 64 4.2BSD 2048 163841 # / b: 33554432 2097216swap # none c:1250454240 unused d: 67108864 35651648 4.2BSD 2048 163841 # /home To make things complete, here is the dmesg output after upgrading to 5.1. Many thanks to the OpenBSD developers to keep the ball in play! Radeon version xf86-video-ati-6.14.3 on ATI FirePro 2270 is a big progress; it gives me a brillant digital image! Sometimes there are blackscreens after switching back from X11 to console, which can be resolved by rebooting the machine over network. Package qcad is missing but can be compiled easily from the ports collection. Best regards, Jens OpenBSD 5.1 (GENERIC.MP) #207: Sun Feb 12 09:42:14 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17169842176 (16374MB) avail mem = 16698621952 (15925MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf06f0 (62 entries) bios0: vendor American Megatrends Inc. version 0705 date 06/29/2010 bios0: ASUSTeK Computer INC. P7F-M WS acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT acpi0: wakeup devices BR1E(S4) UAR1(S4) PS2K(S4) PS2M(S4) EUSB(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) USBE(S4) USB4(S4) USB5(S4) USB6(S4) BR21(S4) BR22(S4) BR23(S4) P0P1(S4) P0P3(S4) P0P4(S4) P0P5(S4) P0P6(S4) USB8(S4) BR20(S4) BR24(S4) BR25(S4) BR26(S4) BR27(S4) PWRB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU L3426 @ 1.87GHz, 1867.02 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 133MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU L3426 @ 1.87GHz, 1866.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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF cpu1: 256KB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Xeon(R) CPU L3426 @ 1.87GHz, 1866.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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF cpu2: 256KB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Xeon(R) CPU L3426 @ 1.87GHz, 1866.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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF cpu3: 256KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 7 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 1, remapped to apid 7 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 7 (BR1E) acpiprt2 at acpi0: bus -1 (BR21) acpiprt3 at acpi0: bus -1 (BR22) acpiprt4 at acpi0: bus -1 (BR23) acpiprt5 at acpi0: bus -1 (P0P1) acpiprt6 at acpi0: bus 1 (P0P3) acpiprt7 at acpi0: bus -1 (P0P4) acpiprt8 at acpi0: bus -1 (P0P5) acpiprt9 at acpi0: bus -1 (P0P6)
Re: OpenBSD on minimac
On 10 June 2012 16:53, Jan Stary h...@stare.cz wrote: On Jun 10 13:42:28, Martin Pieuchot wrote: On 10/06/12(Sun) 12:51, Jan Stary wrote: I got this Mac Mini on my hands, and I would like to install current/macppc on it. According to http://www.openbsd.org/macppc.html#hardware the following MicMini's are supported: Mac mini (PowerMac10,1) Mac mini (Late 2005 (PowerMac10,2)) My model number is A1103. A quick search suggests that it's the same as PowerMac10,1 - is that correct? If so, it should be supported. My problem is it won't boot from install51.iso. I hold the [c] key while booting up, but it still boots into the MacOSX 10.5.8 that is currently installed on the disk, instead of booting from the CD. Am I missing something obvious? Are you sure you burned the CD correctly? cdio -v tao install51.iso An other way to boot from the CD would be to get into the openfirmware prompt holding cmd+alt+O+F when your machine starts, then type: boot cd:,\\:tbxi I only have the minimac, not the other apple paraphernalia; in particular, I don't have an apple keyboard, so there's no way for me to press cmd+alt+o+f. According to INSTALL.macppc, it's Command + Option + O + F actually; is there a way to do that on a non-apple keyboard? I have the usual PC keyboard attached to it via USB. ANyway, even a non-apple keyborad makes it possibel, obviously, to boot while holding [C] pressed. What could be the reason it doesn't work? Jan I saw your problem is solved already, but for others with the same problem: A reason for these keys not working can be that they are blocked by a firmware password. Info about what gets blocked and how to reset the password here: http://support.apple.com/kb/HT1352
Re: Solid state disk geometry
On 06/11/12 19:25, Jens A. Griepentrog wrote: Dear Mailing Listeners, Let me know, please, whether it makes sense to modify disk geometry for solid state disks? no Which meaning have the default values of cylinders, heads, and sectors for these devices? roughly the exact same thing it has meant for IDE, SATA, and SCSI disks since..well...about 20 years or so...not a thing. All modern drives, and really anything made in probably the last 20 years (i.e., anything worth putting on an OpenBSD machine) use translation...the geometry and reality are unrelated in any recognizable way. As an example, here are my sd1 data: # fdisk sd1 Disk: sd1 geometry: 7783/255/63 [125045424 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 1 2 - 7782 254 63 [ 64: 125033831 ] OpenBSD Are there any disktab entries available more suitable for usual models of solid state disks? At least it seemed reasonable to me to take multiples of 64 blocks for the partition sizes and offsets: which, you will notice, is what OpenBSD does now. If you knew what physical block size your SSD worked with, you might -- MIGHT -- see some benefit using that, but the 4k offsets seem to work just fine. I doubt you would feel any difference... # disklabel sd1 # /dev/rsd1c: type: SCSI disk: SCSI disk label: SSDSA2SH064G1GC duid: 78faa8282eb6f8fa flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 7783 total sectors: 125045424 boundstart: 64 boundend: 125033895 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 2097152 64 4.2BSD 2048 163841 # / b: 33554432 2097216swap # none c:1250454240 unused d: 67108864 35651648 4.2BSD 2048 163841 # /home To make things complete, here is the dmesg output after upgrading to 5.1. Many thanks to the OpenBSD developers to keep the ball in play! Radeon version xf86-video-ati-6.14.3 on ATI FirePro 2270 is a big progress; it gives me a brillant digital image! Sometimes there are blackscreens after switching back from X11 to console, which can be resolved by rebooting the machine over network. Package qcad is missing but can be compiled easily from the ports collection. Best regards, Jens ... ahc0 at pci7 dev 2 function 0 vendor Adaptec, unknown product 0x0082 rev 0x02: apic 7 int 21 scsibus0 at ahc0: 8 targets, initiator 7 sd0 at scsibus0 targ 6 lun 0: FUJITSU, MCJ3230SS, 0010 SCSI2 0/direct removable holy cow. haven't seen one of those in a machine in a while. :) (ok, actually, I don't think I've ever seen one, period. Or maybe I've got one...) ... Nick.
anz online notice
Please Note, To Protect Your ANZ Online Account and Internet Banking. Please LOGIN Now.
Re: Solid state disk geometry
On Mon, Jun 11, 2012 at 8:05 PM, Nick Holland n...@holland-consulting.netwrote: On 06/11/12 19:25, Jens A. Griepentrog wrote: Dear Mailing Listeners, Let me know, please, whether it makes sense to modify disk geometry for solid state disks? no Which meaning have the default values of cylinders, heads, and sectors for these devices? roughly the exact same thing it has meant for IDE, SATA, and SCSI disks since..well...about 20 years or so...not a thing. All modern drives, and really anything made in probably the last 20 years (i.e., anything worth putting on an OpenBSD machine) use translation...the geometry and reality are unrelated in any recognizable way. Like many such generalizations, ignoring the details can cause catastrophic failures. If your systems are virtualized, particularly virtualized on NetApps which use 4096 byte block drives on the back end, that translation layer can be overwhelmed. In particular, the use of the classic msdos compatibility and the 63 blocks of 512 bytes typically assigned for MBR and parttition can have a disastrous impact, which is tied to an old, old standard for boot loaders and partition information. Whether or not OpenBSD uses such an alignment structure, ignoring it by aying oh, we just translate and we've ignored that for decads can cause catastrophic slowdowns of the NetApp when the buffer on the NetApp used for translation overflows and the NetApp goes into single CPU mode. The white paper on the problem is here: http://www.citrix.com/site/resources/dynamic/partnerDocs/BestPracticesforFileSystemAlignmentinVirtualEnvironments.pdf The burden is not as catastrophic on a local drive with a sane local controller, but that re-alignment is still an unnecessary performance hit that should be avoided in any high performance system.
Re: Solid state disk geometry
On 06/11/12 19:25, Jens A. Griepentrog wrote: Let me know, please, whether it makes sense to modify disk geometry for solid state disks? If you knew what physical block size your SSD worked with, you might -- MIGHT -- see some benefit using that, but the 4k offsets seem to work just fine. I doubt you would feel any difference... Intel's answer about X25 SSDs' erase block size on their support forums is pretty much fuck off. -- p
