- Grml - lists.mur.at

***SPAM*** yay useful stuff
by Michael Hekel 30 Sep '17

30 Sep '17

Hello, I've lately seen some nice items that might be helpful for you, just take a look http://www.akritisethi.com/suggestion.php?UE9ncm1sQG1sLmdybWwub3Jn Warmly, Michael Hekel - The content of the pages of this website is for your general information and use only. It is subject to change without notice. This website uses cookies to monitor browsing preferences. If you do allow cookies to be used, the following personal information may be stored by us for use by third parties.

1 0

Cannot build grml from within grml
by Marc Haber 26 Sep '17

26 Sep '17

Hi, here is my "real" problem. (1) Using Debian sid, try building grml64-full using the command line: sudo grml-live -A -V -u -e ~/grml-remaster/grml64-full_2017.05.iso -s stable -c DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT -r "test20170830" -g grml64 -o ~/grml-remaster/tmp This results in tmp/grml_isos/grml64_0.0.1.iso being generated. (2) dd this iso to a LV. Configure a new VM with a CDROM drive and connect this drive to the LV containing the ISO. Boot. Boot works. (3) Try to re-build the grml .iso from within grml using: grml-live -V -e /dev/cdrom -o output/ this emits warnings during the build process about missing EFI files, ending in "xorriso : FAILURE : Cannot find path '/boot/efi.img' in loaded ISO image" (full log in exhibit A). (4) configure the same VM to boot from a released grml64-full.2017.05 iso (5) try rebuilding the grml.iso file with the same command line: grml-live -V -e /dev/cdrom -o output/ (6) see the build succeed (exhibit B). What am I doing wrong when building grml64_0.0.1.iso so that it cannot self-reproduce, while the released grml64-full.2017.05.iso can? Any hints? Greetings Marc Exhibit A: root@grml ~ # grml-live -V -e /dev/cdrom -o output/ [ OK ] Sourcing configuration file /etc/grml/grml-live.conf grml-live [0.30.1]: check your configuration (or use -F to force execution): FAI classes: GRMLBASE,GRML_FULL,AMD64 Config directory: /etc/grml/fai main directory: /root/output Extract ISO: /dev/sr0 Chroot target: /root/output/grml_chroot Build target: /root/output/grml_cd ISO target: /root/output/grml_isos Grml name: grml Release name: grml-live rocks Build date: 2017-09-04 Grml version: 0.0.1 Debian suite: testing Architecture: amd64 Boot method: isolinux Hybrid method: isohybrid Template files: /usr/share/grml-live/templates Using VERBOSE mode. Is this ok for you? [y/N] y [ OK ] Logging actions to logfile /root/output/grml_logs/grml-live.log [ OK ] Unpacking ISO from /dev/sr0 Parallel unsquashfs: Using 4 processors 63157 inodes (67071 blocks) to write [===========================================================|] 67071/67071 100% created 57652 files created 6646 directories created 5464 symlinks created 7 devices created 0 fifos [ WARN ] Skipping stage 'fai dirinstall' as /root/output/grml_chroot exists already. [ OK ] No missing packages found, generating empty junit report. [ WARN ] No EFI boot files found, skipping. [ WARN ] Boot addons not found, skipping therefore. (Consider installing package grml-live-addons) [ OK ] Generating /conf/bootid.txt with entry grml001. [ WARN ] /var/log/fai/grml/last/dpkg.list could not be read, ignoring to store package information on ISO therefore. [ OK ] Finished execution of stage 'boot' [ OK ] Using mksquashfs binary mksquashfs [ OK ] Squashfs build information: running binary mksquashfs using options: -b 256k -comp xz -ef /etc/grml/fai/config/grml/squashfs-excludes -wildcards Parallel mksquashfs: Using 4 processors Creating 4.0 filesystem on /root/output/grml_cd/live/grml/grml.squashfs, block size 262144. [===========================================================|] 61600/61600 100% Exportable Squashfs 4.0 filesystem, xz compressed, data block size 262144 compressed data, compressed metadata, compressed fragments, compressed xattrs duplicates are removed Filesystem size 561646.83 Kbytes (548.48 Mbytes) 32.08% of uncompressed filesystem size (1750975.00 Kbytes) Inode table size 556890 bytes (543.84 Kbytes) 24.01% of uncompressed inode table size (2318970 bytes) Directory table size 618535 bytes (604.04 Kbytes) 37.93% of uncompressed directory table size (1630631 bytes) Number of duplicate files found 3586 Number of inodes 69769 Number of files 57652 Number of fragments 2589 Number of symbolic links 5464 Number of device nodes 7 Number of fifo nodes 0 Number of socket nodes 0 Number of directories 6646 Number of ids (unique uids + gids) 28 Number of uids 12 root (0) ntp (109) bacula (105) clamav (108) mail (8) partimag (110) grml (1000) nobody (65534) _apt (104) man (6) puppet (117) statd (113) Number of gids 23 root (0) bacula (109) dip (30) adm (4) shadow (42) mail (8) partimag (115) uucp (10) grml (1000) nogroup (65534) tty (5) crontab (107) utmp (43) ssh (118) uml-net (111) messagebus (116) staff (50) disk (6) man (12) puppet (122) clamav (113) ntp (114) sambashare (121) [ OK ] Finished execution of stage 'squashfs' [ OK ] Forcing rebuild of ISO because files on ISO have been modified. [ OK ] Using xorriso -as mkisofs to build ISO. [ WARN ] Disabling (U)EFI boot support because /boot/efi.img is missing. xorriso 1.4.6 : RockRidge filesystem manipulator, libburnia project. Drive current: -outdev 'stdio:/root/output/grml_isos/grml_0.0.1.iso' Media current: stdio file, overwriteable Media status : is blank Media summary: 0 sessions, 0 data blocks, 0 data, 1564m free xorriso : WARNING : -volid text problematic as automatic mount point name xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules Added to ISO image: directory '/'='/root/output/grml_cd' xorriso : UPDATE : 947 files added in 1 seconds xorriso : UPDATE : 947 files added in 1 seconds xorriso : NOTE : Copying to System Area: 432 bytes from file '/usr/lib/ISOLINUX/isohdpfx.bin' xorriso : FAILURE : Cannot find path '/boot/efi.img' in loaded ISO image xorriso : NOTE : -return_with SORRY 32 triggered by problem severity FAILURE stat: cannot stat '/root/output/grml_isos/grml_0.0.1.iso': No such file or directory [ FAIL ] Error: there was a critical error executing stage 'iso build' grml-live -V -e /dev/cdrom -o output/ 595.04s user 7.83s system 385% cpu 2:36.40 total Exhibit B: root@grml ~ # grml-live -V -e /dev/cdrom -o output/ [ OK ] Sourcing configuration file /etc/grml/grml-live.conf grml-live [0.29.7]: check your configuration (or use -F to force execution): FAI classes: GRMLBASE,GRML_FULL,AMD64 Config directory: /etc/grml/fai main directory: /root/output Extract ISO: /dev/sr0 Chroot target: /root/output/grml_chroot Build target: /root/output/grml_cd ISO target: /root/output/grml_isos Grml name: grml Release name: grml-live rocks Build date: 2017-09-04 Grml version: 0.0.1 Debian suite: testing Architecture: amd64 Boot method: isolinux Hybrid method: isohybrid Template files: /usr/share/grml-live/templates Using VERBOSE mode. Is this ok for you? [y/N] y [ OK ] Logging actions to logfile /root/output/grml_logs/grml-live.log [ OK ] Unpacking ISO from /dev/sr0 Parallel unsquashfs: Using 4 processors 69110 inodes (72966 blocks) to write [===========================================================\] 72966/72966 100% created 59674 files created 6713 directories created 9365 symlinks created 37 devices created 0 fifos [ WARN ] Skipping stage 'fai dirinstall' as /root/output/grml_chroot exists already. [ OK ] No missing packages found, generating empty junit report. [ WARN ] Boot addons not found, skipping therefore. (Consider installing package grml-live-addons) [ OK ] Generating /conf/bootid.txt with entry grml001. [ WARN ] /var/log/fai/grml/last/dpkg.list could not be read, ignoring to store package information on ISO therefore. [ OK ] Finished execution of stage 'boot' [ OK ] Using mksquashfs binary mksquashfs [ OK ] Squashfs build information: running binary mksquashfs using options: -b 256k -comp xz -ef /etc/grml/fai/config/grml/squashfs-excludes -wildcards Parallel mksquashfs: Using 4 processors Creating 4.0 filesystem on /root/output/grml_cd/live/grml/grml.squashfs, block size 262144. [===========================================================|] 63564/63564 100% Exportable Squashfs 4.0 filesystem, xz compressed, data block size 262144 compressed data, compressed metadata, compressed fragments, compressed xattrs duplicates are removed Filesystem size 558346.95 Kbytes (545.26 Mbytes) 31.89% of uncompressed filesystem size (1750974.64 Kbytes) Inode table size 605922 bytes (591.72 Kbytes) 23.69% of uncompressed inode table size (2557395 bytes) Directory table size 683038 bytes (667.03 Kbytes) 37.86% of uncompressed directory table size (1804190 bytes) Number of duplicate files found 5355 Number of inodes 75789 Number of files 59674 Number of fragments 2588 Number of symbolic links 9365 Number of device nodes 37 Number of fifo nodes 0 Number of socket nodes 0 Number of directories 6713 Number of ids (unique uids + gids) 29 Number of uids 12 root (0) man (6) ntp (109) bacula (105) clamav (108) mail (8) partimag (110) grml (1000) nobody (65534) _apt (104) puppet (117) statd (113) Number of gids 24 root (0) tty (5) kmem (15) disk (6) bacula (109) dip (30) adm (4) shadow (42) mail (8) partimag (115) uucp (10) grml (1000) nogroup (65534) crontab (107) utmp (43) ssh (118) uml-net (111) messagebus (116) staff (50) man (12) puppet (122) clamav (113) ntp (114) sambashare (121) [ OK ] Finished execution of stage 'squashfs' [ OK ] Forcing rebuild of ISO because files on ISO have been modified. [ OK ] Using xorriso -as mkisofs to build ISO. [ WARN ] Disabling (U)EFI boot support because /boot/efi.img is missing. xorriso 1.4.6 : RockRidge filesystem manipulator, libburnia project. Drive current: -outdev 'stdio:/root/output/grml_isos/grml_0.0.1.iso' Media current: stdio file, overwriteable Media status : is blank Media summary: 0 sessions, 0 data blocks, 0 data, 1565m free xorriso : WARNING : -volid text problematic as automatic mount point name xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules Added to ISO image: directory '/'='/root/output/grml_cd' xorriso : UPDATE : 681 files added in 1 seconds xorriso : UPDATE : 681 files added in 1 seconds xorriso : UPDATE : 9.90% done ISO image produced: 296581 sectors Written to medium : 296581 sectors at LBA 0 Writing to 'stdio:/root/output/grml_isos/grml_0.0.1.iso' completed successfully. [ OK ] Creating hybrid ISO file with isohybrid method [ OK ] Detected uefi support for isohybrid, enabling isohybrid: /root/output/grml_isos/grml_0.0.1.iso: unable to find efi image [ OK ] Finished execution of stage 'iso build' [ OK ] Generated netboot package /root/output/netboot//grml_netboot_package_grml_0.0.1.tar.bz2 [ OK ] Successfully finished execution of grml-live [Mon Sep 4 09:49:01 UTC 2017 - running 164 seconds] grml-live -V -e /dev/cdrom -o output/ 607.59s user 9.67s system 374% cpu 2:45.04 total -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421

2 11

How do I find out which FAI classes were used to build a
by Marc Haber 06 Sep '17

06 Sep '17

certain image? Reply-To: Hi, to reproduce a bug, I would like to build a local grml image as similiar as possible to grml64-full.2017.05.iso. How do I find out which FAI classes were used to build the image to give the exact same list to grml-live's -c option? Is that information inside the ISO and/or accessible from the booted grml? Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421

2 4

running a script automatically after boot
by John G Heim 22 Aug '17

22 Aug '17

I have a thumb drive with grml on it. It has a persistant partition. What is the best way to get it to run some commands automatically upon boot? I want to simply have it do: #!/bin/bash modprobe speakup_soft espeakup # EOF -- -- John G. Heim; jheim(a)math.wisc.edu; sip://jheim@sip.linphone.org

2 1

(no subject)
by Arne de Boer 01 Jun '17

01 Jun '17

Hi, I would like to learn the technique of grml-rescueboot. Does documentation exist? Thank you for grml John Smith

2 2

Grml 2017.05 EFI problem
by Lupe Christoph 01 Jun '17

01 Jun '17

Hi! Many thanks for giving us a new version of Grml! And a new pun. I wonder what people less acquainted with Austria then me (as a child, I spent my summer vacation in Bad Goisern) are making of Freedatensuppe if they don't find the explanation... As I'm now working in Swabia, I'll eat a FlÃ¤dlesuppe to your health. And now to business ;-) First thing I tried was downloading grml96-full_2017.05.iso to put it on a USB stick. I booted an hp z640 from it. And alas! while the EFI side is seen as well as the legacy side, only the latter boots. Trying to boot EFI throws me into the "Startup Menu". If you can give me so starting point, I'll see if I can find the cause. The ISO *should* be able to boot with EFI and legacy, doesn't it? Lupe Christoph -- | "I'll never forget my government treating me like this. And I really hope | | that this will never happen to anybody else because of the way they look, | | if they look like the enemy of our country." | | Fred Toyosaburo Korematsu's last words |

2 1

Grml - new stable release 2017.05 available
by Michael Prokop 31 Mai '17

31 Mai '17

Hi, we said we'll release by the end of May, and here we are! The stable release of Grml version 2017.05 with codename 'Freedatensuppe' is available and just hitting our mirrors. More information about this release is available in the release notes of Grml 2017.05: https://grml.org/changelogs/README-grml-2017.05/ The (lots(!) of) changes between the release candidate version (2017.05-rc1) and the stable release are documented at: https://grml.org/changelogs/README-grml-2017.05/#changes-between-rc-and-sta… Grab the latest Grml ISO(s) and spread the word: https://grml.org/download/ If you should notice any bugs please let us know: https://grml.org/bugs/ We welcome constructive feedback, suggestions for improvement and your contributions, please just reach out to us: https://grml.org/contact/ Thanks to everyone contributing to Grml and this release! Happy Grml-ing, -mika-

1 0

First Release Candidate of Grml version 2017.05 available
by Michael Prokop 19 Mai '17

19 Mai '17

Hi, so *finally* we did it again, jey! The first release candidate of the upcoming Grml version 2017.05, code-named 'Freedatensuppe' is available. This Grml release provides fresh software packages from Debian testing (AKA stretch). As usual it also incorporates current hardware support and fixes known bugs from the previous Grml release. For detailed information about the changes between 2014.11 and 2017.05 have a look at the official release announcement: http://grml.org/changelogs/README-grml-2017.05-rc1/ Please test the ISOs and everything you usually use and rely on, 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 the end of May (2017 *cough* :)). Thanks to all contributors! regards, -mika- - for the Grml.org project

3 5

How to verify daily snapshot downloads
by Bernhard Reiter 19 Apr '17

19 Apr '17

Hello, today I've taken a look at a daily image for grml.org and found no way to verify that the image I'm downloading actually is from your build machines. http://grml.org/daily/ leads me to something like http://daily.grml.org/grml64-full_testing/2017-04-19_05-31-21/ where there are no OpenPGP signatures available. and the https variant or the url does not show the files. This is a problem because a downloader like can be attacked by serving a different iso file and the corresponding checksums. To prevent this attack you could a) also use https on the daily.grml.org server b) Use a new OpenPGP build-key without password, publish the pubkey on the https mainsite and use the key in the automatic building process to generate the detached signatures. Best Regards, Bernhard ps.: if you have a flattr account, I would have flattred you. :) Thanks for grml. -- www.intevation.de/~bernhard Â +49 541 33 508 3-3 Intevation GmbH, OsnabrÃ¼ck, DE; Amtsgericht OsnabrÃ¼ck, HRB 18998 GeschÃ¤ftsfÃ¼hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

2 2

Grml via ipxe's sanboot
by Jens Mueller 31 Mär '17

31 Mär '17

Dear list, I'm trying to boot GRML over ipxe's sanboot. It fails when mounting root: Begin: Mounting root file system ... (initramfs) Unable to find a medium containing a live file system This is probably no surprise because sanboot is similar to booting using memdisk but without a download delay. mika wrote in "Booting ISO images from within GRUB2" (http://michael-prokop.at/blog/page/3/) "The good news is that Grml supports the memdiskfind/phram/mtdblock approach out-of-the-box." Meaning you do something like modprobe phram phram=memdisk,$(memdiskfind) modprobe mtdblock as mentioned here http://www.syslinux.org/wiki/index.php/MEMDISK#Linux. But memdiskfind returns nothing. My ipxe config contains :grmlsan sanboot ${url}/iso/grml32-small_2014.03.iso || goto failed Any hints to boot Grml over sanboot? Jens

2 1