Balanced Scorecard - Sistema de Información Gerencial
Balanced Scorecard - Sistema de Información Gerencial Integral Panama este 19 de Septiembre de 2012 Sheraton Panama Hotel & Convention Center Los altos Ejecutivos de las empresas globales dirigen organizaciones de proporciones enormes y utilizan el Balanced Scorecard para planear, evaluar y balancear estratégicamente la visión con los objetivos de la empresa, integrando equipos gerenciales capaces de lograr resultados sobresalientes. Esta revolucionaria metodología ayudará a los Directores y Ejecutivos a pensar más ampliamente sobre lo que significa hoy el verdadero liderazgo en los negocios... Un experto en Alta Dirección de Empresas presentará este seminario práctico y efectivo donde se discutirán las mejores prácticas del Balanced Scorecard, incluyendo: - Cómo traducir la visión en objetivos concretos - Trazo y ejecución de planes - - Implementar controles de desempeño gerencial - Remuneración por resultados - - Establecer sistemas de información de los medidores Balanced Scorecard - Mejorar la rentabilidad de la empresa, conservar clientes leales y empleados de talento - Ingredientes esenciales para crear valor en la nueva economía- Adquiera la información completa y sin compromiso, solo responda este correo con asunto -Deseo Folleto Balanced o Comuníquese al (507) 279-1083 / 279-0258 / 279-0887 - y a la brevedad lo recibirá! ESTE CORREO NO PUEDE SER CONSIDERADO INTRUSIVO YA QUE CUMPLE CON LAS POLÍTICAS ANTISPAM INTERNACIONALES Y LOCALES: Responda este correo con el Asunto borrar y automáticamente quedará fuera de nuestras listas. Este correo ha sido enviado a: =[Email]
tell mii where bge(4)s phy is up front
bge(4)s traditionally only have a phy at address 1, which is enforced
by the mii_read backend by failing reads at any other address.
why not just tell mii up front that the phy is at address 1?
why not avoid a conditional in an io path?
also, this is necessary to support recent chips which have phys at
different locations. 5717s through 5720s (and maybe chips in the
future) have phys at addresses relative to the pci function number
and whether theyre serdes capable. to support them we'll have to
be able to support phys at locations other than 1.
tested on this:
bge0 at pci3 dev 4 function 0 "Broadcom BCM5714" rev 0xa3, BCM5715 A3 (0x9003):
ivec 0x795, address 00:14:4f:a9:34:90
brgphy0 at bge0 phy 1: BCM5714 10/100/1000baseT/SX PHY, rev. 0
so at least one old thing still works. ok?
Index: if_bge.c
===
RCS file: /cvs/src/sys/dev/pci/if_bge.c,v
retrieving revision 1.311
diff -u -p -r1.311 if_bge.c
--- if_bge.c4 Jul 2012 13:24:41 - 1.311
+++ if_bge.c13 Sep 2012 01:16:19 -
@@ -586,18 +586,6 @@ bge_miibus_readreg(struct device *dev, i
u_int32_t val, autopoll;
int i;
- /*
-* Broadcom's own driver always assumes the internal
-* PHY is at GMII address 1. On some chips, the PHY responds
-* to accesses at all addresses, which could cause us to
-* bogusly attach the PHY 32 times at probe type. Always
-* restricting the lookup to address 1 is simpler than
-* trying to figure out which chips revisions should be
-* special-cased.
-*/
- if (phy != 1)
- return (0);
-
/* Reading with autopolling on may trigger PCI errors */
autopoll = CSR_READ_4(sc, BGE_MI_MODE);
if (autopoll & BGE_MIMODE_AUTOPOLL) {
@@ -2253,8 +2241,8 @@ bge_attach(struct device *parent, struct
if (sc->bge_flags & BGE_PHY_FIBER_MII)
mii_flags |= MIIF_HAVEFIBER;
mii_attach(&sc->bge_dev, &sc->bge_mii, 0x,
- MII_PHY_ANY, MII_OFFSET_ANY, mii_flags);
-
+ 1, MII_OFFSET_ANY, mii_flags);
+
if (LIST_FIRST(&sc->bge_mii.mii_phys) == NULL) {
printf("%s: no PHY found!\n", sc->bge_dev.dv_xname);
ifmedia_add(&sc->bge_mii.mii_media,
Guía de Comprensión de Estados Financieros para Direct
Guía de Comprensión de Estados Financieros para Directores No Financieros SEMINARIO ONLINE EN VIVO este 18 de Septiembre de 2012. La habilidad de revisar estados financieros y tomar decisiones inteligentes es esencial para los Directores y Gerentes que dirigen el rumbo de sus compañías, sin embargo, para muchos de ellos el mundo de las finanzas y sus términos son a menudo ¡ confusos, poco claros y frustrantes! Descubra los diferentes reportes financieros que usted necesita para dirigir con éxito su organización, incluyendo: ¿Qué tipo de reportes e información financiera necesita y cómo puede usted saber si su departamento financiero está actuando debidamente? ¿Cómo identificar los problemas de la empresa en las fases de INGRESOS, COSTOS, GASTOS O UTILIDADES? ¿Cómo requiere los reportes? * Modelos prácticos, comprensibles y efectivos. ¿Cuál es la aportación estratégica de los balances, estados de resultados, flujos de efectivo y otros reportes financieros ¿Cómo identificar indicadores claves que prevengan del peligro a su organización? ¿Cómo reconocer los problemas del flujo de caja antes de que sea demasiado tarde? ¡Una mejor Formación Financiera mejorará su carrera empresarial! Adquiera la información completa y sin compromiso, solo responda este correo con asunto -Deseo Folleto Financiero o Comuníquese al (507) 279-1083 / 279-0258 / 279-0887 - y a la brevedad lo recibirá! ESTE CORREO NO PUEDE SER CONSIDERADO INTRUSIVO YA QUE CUMPLE CON LAS POLÍTICAS ANTISPAM INTERNACIONALES Y LOCALES: Responda este correo con el Asunto borrar y automáticamente quedará fuera de nuestras listas. Este correo ha sido enviado a: tech@openbsd.org
Re: ld.so pre-install sanity check
On Wed, Sep 12, 2012 at 10:33:24AM -0700, Matthew Dempsky wrote:
> This diff is super hacky and just mailed out for proof-of-concept, but
> it's something that's been handy for me while hacking on ld.so.
> Basically before installing a new version of ld.so, it just runs a
> simple test program to double check that ld.so isn't completely hosed.
>
> There's plenty of issues with this diff as is (e.g., doesn't work for
> cross builds, assumes "make obj", "make clean" doesn't work), but I'm
> curious what people think of the concept and whether anyone has
> suggestions how to improve it.
Use beforeinstall instead of adding another target.
'make clean' should be easy to do, just add what you built to CLEANFILES...
you may wish to move the building part of sanitycheckprog to build, not
beforeinstall...
oh, and use .OBJDIR, then it doesn't matter if you forgot to run obj.
e.g.,
test a fragment like that:
OBJ2= sanitycheckprog.o
P2= sanitycheckprog
# XXX native build only
.if !defined(HOSTCC)
all: ${P2}
${P2}: ${OBJ2}
$(CC) -o $@ ${OBJ2} -Wl,--dynamic-linker,${.OBJDIR}/$(PROG)
beforeinstall:
./${P2}
.endif
CLEANFILES += ${P2} ${OBJ2}
Your receipt #16201702652048
Billed To: tech@openbsd.org Order Number: M1V072336511 Receipt Date: 12/09/2012 Order Total: $699.99 Billed To: Credit card Item NumberDescriptionUnit Price 1Postcard (View\Download ) Cancel order Not your order?Report a Problem $699.99 Subtotal:$699.99 Tax:$0.00 Order Total:$699.99 Please retain for your records. Please See Below For Terms And Conditions Pertaining To This Order. Apple Inc. You can find the iTunes Store Terms of Sale and Sales Policies by launching your iTunes application and clicking on Terms of Sale or Sales Policies FBI ANTI-PIRACY WARNING UNAUTHORIZED COPYING IS PUNISHABLE UNDER FEDERAL LAW. Answers to frequently asked questions regarding the iTunes Store can be found at http://www.apple.com/support/itunes/store/ Apple ID Summary ??¬??? Detailed invoice Apple respects your privacy. Copyright ???© 2011 Apple Inc. All rights reserved
ld.so pre-install sanity check
This diff is super hacky and just mailed out for proof-of-concept, but
it's something that's been handy for me while hacking on ld.so.
Basically before installing a new version of ld.so, it just runs a
simple test program to double check that ld.so isn't completely hosed.
There's plenty of issues with this diff as is (e.g., doesn't work for
cross builds, assumes "make obj", "make clean" doesn't work), but I'm
curious what people think of the concept and whether anyone has
suggestions how to improve it.
Index: Makefile
===
RCS file: /cvs/src/libexec/ld.so/Makefile,v
retrieving revision 1.37
diff -u -p -r1.37 Makefile
--- Makefile3 Feb 2010 20:49:00 - 1.37
+++ Makefile12 Sep 2012 17:26:32 -
@@ -35,4 +35,13 @@ ELF_LDFLAGS+=--shared -Bsymbolic --no-un
$(PROG):
$(LD) -x -e _dl_start $(ELF_LDFLAGS) -o $(PROG) $(OBJS) $(LDADD)
+# XXX: Only for native builds
+realinstall: sanitycheck
+
+.PHONY: sanitycheck
+sanitycheck: sanitycheckprog $(PROG)
+ ./sanitycheckprog
+sanitycheckprog: sanitycheckprog.o
+ $(CC) -o sanitycheckprog sanitycheckprog.o
-Wl,--dynamic-linker,${.CURDIR}/obj/$(PROG)
+
.include
Index: sanitycheckprog.c
===
RCS file: sanitycheckprog.c
diff -N sanitycheckprog.c
--- /dev/null 1 Jan 1970 00:00:00 -
+++ sanitycheckprog.c 12 Sep 2012 17:26:32 -
@@ -0,0 +1,7 @@
+#include
+
+int main()
+{
+ puts("ld.so works");
+ return 0;
+}
Switch to -fstack-protector-all by default
The diff below changes GCC's default behavior to -fstack-protector-all
(i.e., add stack protection code to every function instead of just
some based on heuristics), but you can still revert to the heuristic
behavior by passing -fstack-protector on the command line.
Beware this diff has only received very light testing so far, so
expect things to break and to need to rollback or reinstall. Please
report back to the list what breaks so we can take a look and figure
out how to address it.
For most things that break, it should be possible to just add
CFLAGS+=-fstack-protector to an appropriate Makefile to at least get
the old behavior. Expect at least ld.so on sparc, sparc64, and
powerpc to need -fstack-protector. The kernel is likely to need this
too.
To apply the patch:
$ cd /usr/src/gnu/gcc/gcc
$ patch < /path/to/diff
$ cd /usr/src/gnu/usr.bin/cc
$ make depend
$ make
$ make install
You can now try building things as usual.
Thanks!
Index: toplev.c
===
RCS file: /cvs/src/gnu/gcc/gcc/toplev.c,v
retrieving revision 1.2
diff -u -p -r1.2 toplev.c
--- toplev.c30 May 2010 22:04:10 - 1.2
+++ toplev.c12 Sep 2012 17:03:45 -
@@ -1834,7 +1834,7 @@ process_options (void)
/* Targets must be able to place spill slots at lower addresses. If the
target already uses a soft frame pointer, the transition is trivial. */
if (flag_stack_protect == -1)
-flag_stack_protect = FRAME_GROWS_DOWNWARD ? 1 : 0;
+flag_stack_protect = FRAME_GROWS_DOWNWARD ? 2 : 0;
if (!FRAME_GROWS_DOWNWARD && flag_stack_protect)
{
warning (0, "-fstack-protector not supported for this target");
Re: a question concerning make and the shell
todd@leveno/q2 ~?3$ # $(echo hi > /dev/tty) todd@leveno/q2 ~?4$ I can't say as though I am aware of anything that can be done after a # that starts the line on the shell. As a corilary, ':' is different: todd@leveno/q2 ~?4$ : $(echo hi > /dev/tty) hi todd@leveno/q2 ~?5$ Penned by Marc Espie on 20120912 10:48.51, we have: | Consider the common makefile idiom: | | a: | # cmd that builds a | @cmd | | The # line is actually a comment for the shell, that will be echo'd, | and then passed to a new shell... which does nothing with it. | | I'm wondering if there are any ways (possibly using \ or stuff like that) | that there could be an actual command that starts with a #, and then | would be passed to a shell, and actually get the shell to do something. | | Baring that, the job executor in make can simply echo those #lines and | skip the expensive "fork a shell to do nothing" part... | | (I mostly know what our make does, I'm wondering if posix has some ways | where this could start things, or some other make like solaris/free/net. | and if we want it.) -- Todd Fries .. t...@fries.net _ | \ 1.636.410.0632 (voice) | Free Daemon Consulting, LLC \ 1.405.227.9094 (voice) | http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX) | 2525 NW Expy #525, Oklahoma City, OK 73112 \ sip:freedae...@ekiga.net | "..in support of free software solutions." \ sip:4052279...@ekiga.net \\ 37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A http://todd.fries.net/pgp.txt
Re: a question concerning make and the shell
On 09/12/12 17:48, Marc Espie wrote:
Consider the common makefile idiom:
a:
# cmd that builds a
@cmd
The # line is actually a comment for the shell, that will be echo'd,
and then passed to a new shell... which does nothing with it.
I'm wondering if there are any ways (possibly using \ or stuff like that)
that there could be an actual command that starts with a #, and then
would be passed to a shell, and actually get the shell to do something.
Baring that, the job executor in make can simply echo those #lines and
skip the expensive "fork a shell to do nothing" part...
(I mostly know what our make does, I'm wondering if posix has some ways
where this could start things, or some other make like solaris/free/net.
and if we want it.)
$ cat Makefile
comment:
# ${COMMENT}
$ make COMMENT="$(echo "comment\necho and a sneaky command")" comment
# comment
echo and a sneaky command
and a sneaky command
/Alexander
a question concerning make and the shell
Consider the common makefile idiom: a: # cmd that builds a @cmd The # line is actually a comment for the shell, that will be echo'd, and then passed to a new shell... which does nothing with it. I'm wondering if there are any ways (possibly using \ or stuff like that) that there could be an actual command that starts with a #, and then would be passed to a shell, and actually get the shell to do something. Baring that, the job executor in make can simply echo those #lines and skip the expensive "fork a shell to do nothing" part... (I mostly know what our make does, I'm wondering if posix has some ways where this could start things, or some other make like solaris/free/net. and if we want it.)
Re: Use ACPI to detect secondary PCI root segments on x86
Hi,
On Mon, Sep 10, 2012 at 01:22:35PM +0200, Christian Ehrhardt wrote:
> > Yup. Since we have code to detect additional host bridges some of
> > them may already have been attached. And it would be a good way to
> > defend against ACPI lying to us. However, please keep the ACPI hooks
> > out of the MI PCI code. It'd be better if you used pci_attach_hook(),
> > which lives in arch/pci/pci_machdep.c.
>
> Ok, will do that.
Updated version of the patch is below. regards Christian
Index: arch/i386/i386/mainbus.c
===
RCS file: /cvs/src/sys/arch/i386/i386/mainbus.c,v
retrieving revision 1.48
diff -u -r1.48 mainbus.c
--- arch/i386/i386/mainbus.c3 Nov 2010 10:15:23 - 1.48
+++ arch/i386/i386/mainbus.c12 Sep 2012 13:39:19 -
@@ -244,6 +244,9 @@
mba.mba_pba.pba_domain = pci_ndomains++;
mba.mba_pba.pba_bus = 0;
config_found(self, &mba.mba_pba, mainbus_print);
+#if NACPI > 0
+ acpi_pciroots_attach(self, &mba.mba_pba, mainbus_print);
+#endif
}
#endif
Index: arch/i386/pci/pci_machdep.c
===
RCS file: /cvs/src/sys/arch/i386/pci/pci_machdep.c,v
retrieving revision 1.68
diff -u -r1.68 pci_machdep.c
--- arch/i386/pci/pci_machdep.c 4 Dec 2011 20:08:09 - 1.68
+++ arch/i386/pci/pci_machdep.c 12 Sep 2012 13:39:19 -
@@ -208,6 +208,9 @@
printf(": configuration mode %d", pci_mode);
#endif
+#if NACPI > 0
+ acpi_pciroot_match(self, pba->pba_bus);
+#endif
if (pba->pba_bus != 0)
return;
Index: dev/acpi/acpi.c
===
RCS file: /cvs/src/sys/dev/acpi/acpi.c,v
retrieving revision 1.238
diff -u -r1.238 acpi.c
--- dev/acpi/acpi.c 13 Jul 2012 11:51:41 - 1.238
+++ dev/acpi/acpi.c 12 Sep 2012 13:39:20 -
@@ -392,6 +392,8 @@
TAILQ_HEAD(, acpi_pci) acpi_pcidevs =
TAILQ_HEAD_INITIALIZER(acpi_pcidevs);
+TAILQ_HEAD(, acpi_pci) acpi_pcirootdevs =
+TAILQ_HEAD_INITIALIZER(acpi_pcirootdevs);
int acpi_getpci(struct aml_node *node, void *arg);
int acpi_getminbus(union acpi_resource *crs, void *arg);
@@ -480,6 +482,7 @@
node->pci = pci;
dnprintf(10, "found PCI root: %s %d\n",
aml_nodename(node), pci->bus);
+ TAILQ_INSERT_TAIL(&acpi_pcirootdevs, pci, next);
}
aml_freevalue(&res);
return 0;
@@ -548,6 +551,31 @@
dev->dv_xname, aml_nodename(pdev->node));
pdev->device = dev;
}
+ }
+}
+
+void
+acpi_pciroot_match(struct device *dev, int bus)
+{
+ struct acpi_pci *pdev;
+
+ TAILQ_FOREACH(pdev, &acpi_pcirootdevs, next) {
+ if (pdev->bus == bus)
+ pdev->device = dev;
+ }
+}
+
+void
+acpi_pciroots_attach(struct device *dev, void *aux, cfprint_t pr)
+{
+ struct acpi_pci *pdev;
+ struct pcibus_attach_args *pba = aux;
+
+ TAILQ_FOREACH(pdev, &acpi_pcirootdevs, next) {
+ if (pdev->device) /* Already attached */
+ continue;
+ pba->pba_bus = pdev->bus;
+ config_found(dev, pba, pr);
}
}
Index: dev/acpi/acpivar.h
===
RCS file: /cvs/src/sys/dev/acpi/acpivar.h,v
retrieving revision 1.71
diff -u -r1.71 acpivar.h
--- dev/acpi/acpivar.h 15 Apr 2011 17:34:51 - 1.71
+++ dev/acpi/acpivar.h 12 Sep 2012 13:39:20 -
@@ -322,6 +322,9 @@
void acpi_powerdown_task(void *, int);
void acpi_sleep_task(void *, int);
+void acpi_pciroot_match(struct device *, int);
+void acpi_pciroots_attach(struct device *, void *, cfprint_t);
+
#endif
#endif /* !_ACPI_WAKECODE */
Cómo Ser un Gran Negociador
Cómo Ser un Gran Negociador SEMINARIO ONLINE EN VIVO este 18 de Septiembre de 2012. Negociar es estresante, usted sabe ahora que eso requiere de ceder y mantenerse firme, pero ¿Cuándo debería ceder y cuándo debería ser firme? La única diferencia entre aquellos que están seguros de su habilidad para lograr grandes tratos y aquellos que no, es que los negociadores más fuertes han dominado LOS SECRETOS PARA MANTENERSE FIRMES en obtener los acuerdos que ellos quieren. ¡Usted puede aprender a ser un negociador fuerte sin dejar de ser justo! Conocerá aspectos relevantes incluyendo: Blindaje invisible- La estrategia maestra que podrá utilizar en contra de las amenazas de adversarios, de las contraofertas y de las justificaciones Cómo detectar una actitud honesta o falsa de su adversario Cómo crear las armas secretas que le darán la posición que usted quiere Cómo evitar ser arrinconado en la negociación y qué puede hacer al respecto Las tácticas que usan los mejores negociadores para debilitar a un oponente 3 recomendaciones de tiempo para saber cuándo ejercer presión, cuándo ceder y cuándo mantenerse firme Cómo mantener las emociones bajo control, después de una prolongada negociación Cómo estar seguro que no está presionando demasiado a su adversario, al punto de que pueda poner en riesgo el trato y qué hacer si accidentalmente esto sucede. Adquiera la información completa y sin compromiso, solo responda este correo con asunto -Deseo Folleto Negociador o Comuníquese al (507) 279-1083 / 279-0258 / 279-0887 - y a la brevedad lo recibirá! ESTE CORREO NO PUEDE SER CONSIDERADO INTRUSIVO YA QUE CUMPLE CON LAS POLÍTICAS ANTISPAM INTERNACIONALES Y LOCALES: Responda este correo con el Asunto borrar y automáticamente quedará fuera de nuestras listas. Este correo ha sido enviado a: tech@openbsd.org
Re: script to make installable disk image
On 09/06/12 12:01, Thomas Jeunet wrote: On Wed, Sep 5, 2012 at 9:36 AM, Ted Unangst wrote: We provide many forms of installation media, but neither floppy nor iso images are "best" suited for usb drives. It's pretty easy to make a hard drive image containing the installer bsd.rd. I tested this on i386, it should work on amd64 too. It's just a bunch of shell commands, save it to makeimage.sh or whatever. Maybe we could integrate this into the distrib build makefiles, but I wanted to get a procedure done first. I don't know what the best way to get a disklabel on is, I just dumped a tiny bit of text into a file. It's actually very similar to what builds the install.iso, but I didn't do it as a makefile for now so it's easier for standalone users to run. It assumes you have a working bsd.rd in /. If you wanted to build amd64 on i386, or vice versa, you'll have to fiddle with the files. #!/bin/sh set -e cp /bsd.rd . gzip -9 bsd.rd dd if=/dev/zero bs=1k count=3584 of=disk.img sudo vnconfig vnd0 disk.img sudo fdisk -y -i vnd0 echo "16 partitions:" > disklabel.txt echo "#size offset fstype [fsize bsize cpg]" >> disklabel.txt echo " a: 6944 128 4.2BSD 2048 163841" >> disklabel.txt echo " c: 71680 unused" >> disklabel.txt disklabel -R vnd0 disklabel.txt newfs -i 512000 vnd0a mount /dev/vnd0a /mnt cp bsd.rd.gz /mnt/bsd cp /usr/mdec/boot /mnt/boot /usr/mdec/installboot /mnt/boot /usr/mdec/biosboot vnd0 umount /mnt vnconfig -u vnd0 rm bsd.rd.gz rm disklabel.txt Here's a version without the disklabel file, using EXAMPLES section from softraid(4). I modified gzip invocation to avoid handling temporary files, but I end up wondering if it's worth it... I also added missing sudo invocation #!/bin/sh set -e dd if=/dev/zero bs=1k count=3584 of=disk.img sudo vnconfig vnd0 disk.img sudo fdisk -y -i vnd0 printf "a\n\n\n\n\nw\nq\n\n" | sudo disklabel -E vnd0 sudo newfs -i 512000 vnd0a sudo mount /dev/vnd0a /mnt gzip -9 -c /bsd.rd | sudo tee /mnt/bsd >/dev/null sudo cp /usr/mdec/boot /mnt/boot sudo /usr/mdec/installboot /mnt/boot /usr/mdec/biosboot vnd0 sudo umount /mnt sudo vnconfig -u vnd0 All this sudo'ing makes my head spin. Just run the script as root and remove the tee workaround. /Alexander
Diseño web y Posicionamiento web Desarrollo Hosting Dominio
Estimados Sres /as, Tenemos el agrado de comunicarnos para ofrecerles nuestros servicios de Diseño Web, programación, Posicionamiento Web Dominios y Hosting. Contamos con la experiencia de 11 años en el mercado. - Diseño Web - Rediseño Web - Posicionamiento en buscadores. - Alojamiento Web - Registros de Dominios - Programación de Intranet y Extranet - Tiendas Virtuales con Pasarela de Pagos - Catálogos de Productos - E-learnings - Social Media - Adecuación a la LSSI y LOPD. - Chats (Istalación gratis por 14 dias) - Y más… Desarrollamos sitios administrables por el usuario, logrando que usted tenga el total dominio y libertad del uso de su Web. Junto con cada Página desarrollada entregamos un Administrador para que pueda cargar datos, fotos, videos y todo el contenido necesario para mantener su Web actualizada. Atendemos agencias para reventa de productos y/o servicios / Marca Blanca / Distribuidores Estos son algunos de los clientes que han confiado en nosotros de "Madrid, Valencia, Burgos, Sevilla, Barcelona, Galicia, Tenerife" - WürdModyf - Universidad Politécnica de Madrid - Repsol - Clínicas Svenson - Remax Real State - Telefónica España Visite nuestra Web: www.vedcor.es, 1300 desarrollos, sabemos que es lo que necesita, Webs Rentables con alta calidad y tarifas razonables. Si desea ver otros trabajos realizados puede solicitarlo sin compromiso. Envíenos sus datos y nos comunicaremos para atender su consulta sin compromiso y elaborarle un presupuesto acorde a sus necesidades. Reciba un cordial saludo Departamento de Markenting 91 15 16 306 www.vedcor.es Responda con eliminar para no recibir mas correos
