Thursday, February 28. 2013Warning: broken grml96-full_2013.02.iso downloadThere was a "broken" grml96-full ISO on our mirrors for a few hours. All our checksum files as well as the signature files are OK, just the file grml96-full_2013.02.iso has a few different bits, resulting in a file which doesn't correspond to the expected checksum. Note: the broken ISO doesn't do any harm (it even boots) but you should still grab the correct one. We've updated the grml96-full_2013.02.iso file but it might take a few hours until it's propagated to all our mirrors. To check whether you're affected execute 'md5sum -c grml96-full_2013.02.iso.md5' or 'sha1sum -c grml96-full_2013.02.iso.sha1'. The broken file is: % md5sum grml96-full_2013.02.iso b2ae41161908751c4ba6ac4db0855a70 grml96-full_2013.02.iso % sha1sum grml96-full_2013.02.iso f61a87223ca02482f7f7e8d674c444c40ca91b3a grml96-full_2013.02.iso The known-to-be-good file should return: % md5sum grml96-full_2013.02.iso ceaec04b29f9263e384a54cda8c3bab0 grml96-full_2013.02.iso % sha1sum grml96-full_2013.02.iso c95df860f1c08cd7e82ddeac4918bb29cb3f0b7d grml96-full_2013.02.iso Sorry for the annoyance. Thanks to zeldor for bringing this issue to our attention. Thursday, February 28. 2013
Grml - new stable release 2013.02 ... Posted by Michael Prokop
in general at
01:42
Comments (0) Trackbacks (0) Grml - new stable release 2013.02 availableWe just released Grml 2013.02 - Grumpy Grinch. This release brings the Grml tools towards the upcoming Debian stable release (AKA wheezy), provides up2date hardware support and fixes known bugs from the previous Grml release. More information is available in the release notes of Grml 2013.02. Grab the latest Grml ISO(s) and spread the word! Thanks everyone involved and happy grml-ing! Monday, February 18. 2013First Release Candidate of Grml version 2013.02 releasedWe are proud to announce the first release candidate of the upcoming version 2013.02, code-named 'Grumpy Grinch'! This release brings the Grml tools towards the upcoming Debian stable release (AKA wheezy), provides up2date hardware support and fixes known bugs from the previous Grml release. For detailed information about the changes between 2012.05 and 2013.02 have a look at the official release announcement. Please test the ISOs and everything you usually use and report back, so we can complete the stable release soon. If no major problems come up, the next iteration will be the stable release, which is scheduled for end of February. Wednesday, June 6. 2012New Grml developer: Markus Rekkenbeil
We're proud to be able to announce that Markus 'bionix' Rekkenbeil just joined the Grml team. Welcome in the team, Markus!
Tuesday, May 29. 2012
Grml - new stable release 2012.05 ... Posted by Michael Prokop
in general at
09:52
Comment (1) Trackbacks (0) Grml - new stable release 2012.05 availableWe just released Grml 2012.05 - Ponyhof. Thanks for all the feedback we received for our 2011.12 release, we took it serious and hope that everyone finds 2012.05 such a wonderful release as we consider it to be. There were some changes between 2012.05-rc1 and the new stable release. The most important ones are:
As you might notice the grml-small flavour came back. So it's two flavours (grml-full + grml-small) and two architectures (x86 + amd64) now. The grml96 option - which provides the x86 and the amd64 version on one single ISO (grml96 = grml32 + grml64) - is available for your service as well. We want to thank all the people involved in this magnificent and awesome release. The Grml Developers, our Contributors and all the other people involved in this release. More information is available in the release notes of Grml 2012.05. Now download the latest Grml ISO and spread the word! Thursday, May 17. 2012First Release Candidate of Grml version 2012.05 releasedWe are proud to announce the first release candidate of the upcoming version 2012.05, code-named 'Ponyhof'! For detailed information about the changes between 2011.12 and 2012.05 have a look at the official release announcement. Several tools that have been reported to be missing on the downsized 2011.12 release have been re-added. This release also brings the grml-small flavour back to life. Please test the ISOs and everything you usually use and report back, so we can complete the stable release soon. If no major problems come up, the next iteration will be the stable release, which is scheduled for end of May. Wednesday, May 16. 2012
New Grml developer: Evgeni Golov Posted by Michael Prokop
in general at
09:48
Comments (0) Trackbacks (0) New Grml developer: Evgeni Golov
We're proud to be able to announce that Evgeni 'Zhenech' Golov joined the Grml team as developer. Welcome in the team, Evgeni!
Tuesday, January 17. 2012We want you!Recently two Grml developers sadly left our development team. Christian Hofstaedtler and Gerfried Fuchs, we wish you all the best - thanks for all your work within the Grml community! Now you might be wondering how you could become a Grml developer. We're happy to announce grml.github.com, a place which should get interested people ready to contribute without much headaches. Please help us making Grml an even better kick ass solution! Friday, December 23. 2011
Grml - new stable release 2011.12 ... Posted by Ulrich Dangel
in general at
13:02
Comments (0) Trackbacks (0) Grml - new stable release 2011.12 availableI am proud to announce our Christmas Gift to the community. We just released Grml 2011.12 - Knecht Rootrecht, just in time to put it under the Christmas tree. Download the latest Grml ISO and spread the word. There were quite a lot of changes between RC1 and the new stable release. The most important ones are:
One flavour, two architectures, three options (grml32, grml64, and grml96). I want to thank all the people involved in this magnificent and awesome release. The Grml Developers, our Contributors and all the other people involved in this release. Friday, December 23. 2011
Create a Grml ISO image with your ... Posted by Ulrich Dangel
in general at
13:00
Comments (0) Trackbacks (0) Create a Grml ISO image with your own ssh keys for password less loginIn this article we will show you how you can leverage grml-autoconfig to create a Grml ISO which will automatically start an ssh server and use your own ssh keys instead of the traditional password based login. This allows Grml to be used not only for interactive rescue operations but also for remote or automated setups. Starting with Grml 2009.05 we streamlined the support of hooking into our boot-process in grml-autoconfig thanks to the patches from Marc 'Zugschlus' Haber. Now it is possible to execute arbitrary scripts, unpack archives or install packages at startup not only directly from the Live CD but also from partitions. This allows you to create customized Grml Images with ease without the need to modify the squashfs image (usually known as remastering). In this example we will add the necessary files directly onto the ISO image but you can also use a USB stick instead. Please make sure you read the grml-autoconfig manpage The first step is to create a directory which will contain all the additional files to be copied onto the ISO image. In this example we use /tmp/grml_overlay/ mkdir /tmp/grml_overlay The next step is to create an archive containing the ssh keys. For this step you need either fakeroot or run the commands as root. This will create an archive named /tmp/grml_overlay/config.tbz containing all the files we created in our directory. Please make sure to replace the cp command with your own ssh keys. As we used fakeroot in this example you can manipulate file permissions without the need to run these commands as root.TMPDIR="/tmp/grml_config" cd "$TMPDIR" || mkdir "$TMPDIR" && cd "$TMPDIR" fakeroot mkdir --parent root/.ssh home/grml/.ssh chmod 0700 root/.ssh home/grml/.ssh cp /home/uli/.ssh/id_rsa.pub root/.ssh/authorized_keys cp /home/uli/.ssh/id_rsa.pub home/grml/.ssh/authorized_keys chown -R 1000:1000 home/grml tar --numeric-owner -j -c -f /tmp/grml_overlay/config.tbz . Now we have everything what's needed prepared and can just run grml2iso and specify the additional boot parameters as well as the overlay directory. grml2iso -b "config ssh" -c /tmp/grml_overlay -o my-grml.iso ./grml64_2011.12.iso ![]() During startup of Grml you will notice some additional log messages indicating the unpacking of your created archive. This shows that everything works like intended. Combining different boot parameters in Grml like config and ssh allows you to create customized and tailored distributions for your own needs without having to dig into the remastering process. With the availability of tools like grml2usb and grml2iso you can easily create customized tools based on Grml without the need to develop everything from scratch. We showed how you can leverage grml2iso to create a Rescue CD based on Grml with ssh keys for remote login. Thursday, December 22. 2011Upcoming accessibility changes for Grml 2011.12The upcoming Grml 2011.12 will have some changes in the accessibility features shipped with Grml. Until Grml 2011.12 it was possible to start brltty automatically via the bootoption brltty. The problem with this approach was that it was never clear when you had to enter the bootoptions as there was no sound to indicate boot menu. We also do not have the necessary hardware to test the releases with brltty. With that in mind and the integration of speakup in the kernel we decided to remove the additional accessibility boot-parameters for Grml 2011.12 as we never tested them anyway. But we added some important changes to improve the accessibility. Starting with Grml 2011.12 the bootloader will either beep once (if you use the default syslinux one) or will play 3 beeps (grub) to indicate the boot menu. Afterwards you can easily change the boot parameters if you press TAB (syslinux) or e (Grub). After the bootup Grml will play some tunes to indicate the finished boot. As per default Grml starts a text based menu you will have to press enter after the beep to enter the commandline We think with the additional sound indicators in the boot-menu as well as the default sound to indicate the finished boot-process, Grml 2011.12 will be more accessible then ever. I would like to thank Richard Hartmann for creating the different sound indicators for the upcoming Release Wednesday, December 21. 2011
Remastering Grml without modifying ... Posted by Ulrich Dangel
in general at
13:00
Comments (0) Trackbacks (0) Remastering Grml without modifying the squashfs or create your own customized Grml CDsIn our last Blog entry about remastering Grml 2011.12 we described a method remastering Grml with grml-live, the tool used to generate the official Grml ISOs. Often you don't need all the power and flexibility of grml-live but just want to add or change some default boot parameters and use this as your default image. For example you may want to have an ISO image which automatically starts sshd and sets the password to a specific value or downloads an executable and run it at startup. This can easily be done with grml2iso a tool based on grml2usb which allows you to create customized iso images. Grml will automatically start sshd and set the password for the grml user if you specify the ssh boot-parameter. This allows you to remotely control your Grml CD. To create such a CD just run: grml2iso -b "ssh=grml-password" -o my_grml.iso ./grml64_2011.12.isoThis will create a modified Grml ISO named my_grml.iso and add the bootparameter ssh=grml-password to all the existing boot-entries. grml2usb does not offer the same flexibility as grml-live but grml2usb/grml2iso is often good enough to help you to achieve what you want without the need to modify the squashfs file. Tuesday, December 20. 2011
Remastering Grml 2011.12 will be as ... Posted by Christian Hofstaedtler
in general at
13:00
Comments (0) Trackbacks (0) Remastering Grml 2011.12 will be as easy as never before
For the final release of Grml 2011.12 we will no longer ship the so called "release-chroots" - and this will not make it harder for you to remaster, but only easier!
grml-live, the build tool for Grml, has gained a new feature: it can now extract ISOs and use their contents as the base for your remastering needs. This feature will be released with the next grml-live release, but it's available today in grml-live git. How you'd use this:
Monday, December 19. 2011Customize grml-debootstrap with scriptsIn our latest blog entry about grml-debootstrap we described how to leverage grml-debootstrap for automated installations of Debian into virtualized systems. Unfortunately sometimes this is not enough and you need to run commands after the installation. This post will describe some customization methods of grml-debootstrap. For more information on this topic also look at the manpage of grml-debootstrap One quite common task is to execute scripts after the installation like for example gathering the ssh host key or adding your own CA to the host. grml-debootstrap supports the execution of scripts after the machine is successfully installed. To execute scripts after the installation we first need a directory containing all the scripts. This directory will be afterwards specified as a parameter to grml-debootstrap. In this example we are using ./scripts as the directory name. mkdir ./scripts After we create the directory we also need to create a script for our post-processing task. For this example we'll create a script which will examine the fingerprints of the ssh hosts keys. To be able to access and modify the image all the scripts executed by grml-debootstrap will have an environment variable specified called MNTPOINT which will point to the directory used for installing the system. Then we have to create a script inside the directory and make it executable: This script will iterate over all ssh host keys and print the fingerprint of them.$ cat >./scripts/89_print_sshkeys <<EOF #!/bin/bash set -e if [ -z "\$MNTPOINT" ] ; then echo "Please run \$0 inside grml-debootstrap or export MNTPOINT" >&2 exit 1 fi for key in "\$MNTPOINT"/etc/ssh/ssh_host_*_key.pub ; do chroot "\$MNTPOINT" ssh-keygen -l -f \${key##\$MNTPOINT} done EOF $ chmod +x ./scripts/89_print_sshkeys After we created the directory and the script we can now point grml-debootstrap to the directory and it will run all executable files in it. If we extend the command-line from our last example we have to specify the --scripts parameter and point it to the created directory: $ sudo grml-debootstrap --scripts ./scripts/ --password root-pw --vmsize 3G --vmfile --target ./qemu.img .... Finished chroot installation, exiting. * Executing script ./scripts/89_print_sshkeys 1024 9e:d9:18:1d:47:ae:26:9f:53:5e:63:3c:bd:37:ea:2b /etc/ssh/ssh_host_dsa_key.pub (DSA) 2048 c1:5e:27:a3:2f:7d:30:a0:ab:75:a2:86:e7:bb:8a:e2 /etc/ssh/ssh_host_rsa_key.pub (RSA) .... This shows how easy it is to customize and extend grml-debootstrap to your own needs. You can easily create customized scripts and run arbitrary commands on the target to do whatever you want. grml-debootstrap is of course available within Grml but also in Debian. Friday, December 16. 2011
Deploy Virtual Machines with Grml ... Posted by Ulrich Dangel
in general at
12:00
Comments (0) Trackbacks (0) Deploy Virtual Machines with Grml 2011.12 or DebianThe upcoming Grml release 2011.12 as well as Debian/testing and unstable ship an updated grml-debootstrap version supporting the installation of Debian not only into directories or hardisks but also into virtual images. grml-debootstrap is designed to help you install complete Debian Systems. Typically if you install a Debian system with debootstrap you have to install the kernel, bootloader, /etc/fstab, ssh server, … yourself. grml-debootstrap automates this boring tasks and allows you to install Debian systems from within a running system within minutes. Nowadays physical installations get less and less important but virtual installation gain importance. New servers are often run inside virtual environments like Xen, KVM or VMware. grml-debootstrap supports the automated installation of Debian into a virtualized environment without the need to use a preseeded installation medium. You can create a raw image with grml-debootstrap which boots per default with KVM and Xen. To boot the image file with other virtualization solutions you may have to convert the generated image with qemu-img To install a plain Debian System into a raw image you just have to run grml-debootstrap --password root-pw --vmfile --vmsize 3G --target ./squeeze.img This will set the root pasword to root-pw, install openssh and the latest kernel package, create /etc/fstab with the necessary entries and configure the bootloader for your virtualized system. If you want to customize or extend grml-debootstrap have a look at the manpage or look at the scripts and package definitions in /etc/debootstrap |
QuicksearchArchives |