Todos con Software Libre
El Software y el conocimiento debe ser Libre
El Software y el conocimiento debe ser Libre
Jan 26th
Os dejo el mensaje que Fred Patton ha publicado en su blog:
Editor’s note: Today’s blog post comes from Sam Greenblatt, the chief technology officer and head of technical strategy for the open webOS project. He guides the project’s strategy around open collaboration and is responsible for technical engineering. His focus is on the practice of developing webOS with the community, and his approach is founded on the belief that the open source development model produces great software and web technology. Sam has many years of open source experience, including being on the board of OSDL (Linux Foundation). His long career in software development includes being a CTO at HP, Chief Innovation Officer at CA Technology, and CTO at Candle Corporation (IBM).
In December, HP announced that webOS would be made available under an open source license, with continued support from HP. We’re proud of webOS and its potential to harness web standards to improve the next generation of applications, web services, and devices.
Today, we’re taking the next step on this journey by releasing Enyo, our JavaScript app framework, under open source licensing, allowing developers to distribute their Enyo-based webOS apps across other platforms. In this post, we’ll also provide a first look at our open source release roadmap.
In any large project, it’s imperative to communicate the plan for achieving the project’s goals. This plan is usually presented in the form of a roadmap, which outlines the steps necessary to achieve project goals and shows the path forward. For an open source project to be a success, that roadmap must be public so all contributors have a sense of where the project is headed.
In subsequent posts, and on the new Enyo website, we will share more details about our roadmap for webOS, including our plans for release phases, governance, tools, documentation, and more. So with that in mind, let’s step into an overview of some of the pieces of the release plan.
Our first contribution is Enyo, our lightweight, cross-platform framework aimed at mobile devices and web browsers.
This initial open source release includes Enyo 1.0, which allows current developers of Enyo apps for webOS devices to distribute their apps to other platforms. While this release is not intended to be expanded any further, there is considerable utility for our current developer base in releasing it.
Today’s release also includes the core of Enyo 2.0, which will be the foundation for Enyo going forward. It expands Enyo’s “write once, run anywhere” capability to even more platforms, from mobile devices to desktop web browsers. It works on many of the most popular web browsers, including Chrome, IE 9, Firefox, and Safari.
While 2.0 does not yet include any UI widgets, the core will support a wide variety of libraries and add-ons. A UI widget set for 2.0 will be released in the near future.
Upcoming releases include our distribution of WebKit, which will support not only HTML5, but also Silverlight and Flash through the use of plug-ins. It will enable the rendering of webpages to HTML Canvas and 3-D textures, and will support a wide range of application interfaces, including multi-touch.
We will also release a new kernel based on the Linux Foundation’s standard kernel. As we continue through the roadmap, you will see enhanced integration with JavaScript through register callbacks and custom multi-process architecture for security, load balancing, and recovery availability.
Look for us to introduce LevelDB to replace our prior database.
Along the way, we will also share our tool sets, and we expect that many of you will want to share yours as well.
In closing, I want to thank the great engineers who have worked with me on creating the open webOS roadmap and let you all know that we look forward to collaborating with the community. As my friend Eric Raymond stated as I embarked on the open source adventure, “It takes a village to create a complete solution.”
Jan 10th
The libvirt Perl binding, Sys::Virt, release 0.9.9 is now available for download:
http://search.cpan.org/CPAN/authors/id/D/DA/DANBERR/Sys-Virt-0.9.9.tar.gz
In this release 0.9.9:
The module homepage, where online documentation, and historical downloads can be found is:
http://search.cpan.org/dist/Sys-Virt/
Jan 3rd
Para extender un volumen lógico simplemente dile al comando lvextend cuánto quieres incrementar el tamaño. Puedes especificar cómo crecer el volumen, o cómo expandirlo
# lvextend -L12G /dev/vg00/homevol lvextend -- extending logical volume "/dev/vg00/homevol" to 12 GB lvextend -- doing automatic backup of volume group "vg00" lvextend -- logical volume "/dev/vg00/homevol" successfully extended
extenderá /dev/vg00/homevol a 12 Gigabytes.
# lvextend -L+1G /dev/vg00/homevol lvextend -- extending logical volume "/dev/vg00/homevol" to 13 GB lvextend -- doing automatic backup of volume group "vg00" lvextend -- logical volume "/dev/vg00/homevol" successfully extended
añadirá otro gigabyte a /dev/vg00/homevol.
Después de que hayas extendido el volumen lógico es necesario incrementar el tamaño del sistema de archivos para que coincida. Cómo hacerlo dependerá del tipo de sistema de archivos que estés usando.
Por defecto, la mayoría de las utilidades de redimensionado de sistemas de archivos incrementan el tamaño del sistema de archivos para ser el tamaño del volumen lógico subyacente por lo que no necesitas preocuparte por especificarle el mismo tamaño para cada uno de los dos comandos.
ext2/ext3A no ser que hayas parcheado tu kernel con el parche de ext2online es necesario desmontar el sistema de archivos antes de redimensionarlo. (Parece que el parche de redimensionado online es todavía peligroso, por lo que úsalo bajo tu propio riesgo)
# umount /dev/myvg/homevol/dev/myvg/homevol # resize2fs /dev/myvg/homevol # mount /dev/myvg/homevol /home
Si no tienes e2fsprogs 1.19 o posterior, puedes descargar el comando ext2resize de ext2resize.sourceforge.net y usarlo:
# umount /dev/myvg/homevol/dev/myvg/homevol # ext2resize /dev/myvg/homevol # mount /dev/myvg/homevol /home
Para ext2 hay una manera fácil. LVM 1 viene con una utilidad llamada e2fsadm que hace el lvextend y resize2fs por ti (además hace el recortado del sistema de archivo, velo en la sección siguiente).
# e2fsadm -L+1G /dev/myvg/homevol
es equivalente a los dos comandos:
# lvextend -L+1G /dev/myvg/homevol # resize2fs /dev/myvg/homevol
# resize_reiserfs -f /dev/myvg/homevol
# umount /dev/myvg/homevol # resize_reiserfs /dev/myvg/homevol # mount -treiserfs /dev/myvg/homevol /home
# xfs_growfs /home
# mount -o remount,resize /home
| Fallos conocidos del Kernel | |
|---|---|
| Algunas versiones del kernel tienen problemas con esta sintaxis (se sabe que 2.6.0 tiene este problema). En este caso tienes que especificar exactamente el nuevo tamaño del sistema de archivos en bloques. Es extremadamente una equivocación que tú debas saber el tamaño de bloque de tu sistema de archivo y calcular el nuevo tamaño basado en esas unidades.
Ejemplo: Si tuvieses que redimensionar un sistema de archivos JFS a 4 gigabytes que tienen bloques de 4k, deberías poner: # mount -o remount,resize=1048576 /home |