- Grml - lists.mur.at

grml: espeak or espeak-ng not talking
by Simon Eigeldinger 28 Dez '17

28 Dez '17

Hi all, I recently wanted to upgrade to a recent version of grml. unfortunately i have figured out that espeak or espeak-ng which is the successor of espeak doesn't speak. could someone check that? there seems to be an issue with sound. the only screenreader that works at the moment is brltty. speakup/espeakup doesn't because espeak has nothing to output. Greetings and thanks, Simon --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

1 0

grml liveCD LAN setting
by william_wu＠accton.com 01 Dez '17

01 Dez '17

Dear Sir, I had download GRML liveCD from your website, and mount it to USB disk, and I have a question here how can I change the LAN setting default to static IP, because It will reset to default after reboot I just want set DHCP to static IP, can you please advise how to change this setting, thank you. William Wu 吳繼威 Accton Technology Corporation 10694 13th Floor, No. 102, Guangfu South Road, Taipei, Taiwan Office:02-8773-8500#1079

1 0

network boot via iPXE
by ipeter88 30 Nov '17

30 Nov '17

Hi Here is example of ipxe server configuration for ipv4 network booting of grml (linux distribution only) on both BIOS and UEFI systems. IPXE server is built on grml system with IP address 192.168.101.1 What we need - installation files (grml iso image(s)) - tftp server (it is enough to use installed atftpd) - dhcp server (here isc-dhcp-server) - web server (here nginx) - ipxe binaries and scripts - DNS server (only required when we want to use dns names instead of ip addresses in configuration files) Installation files Mount iso image(s) to gain access to installation files mkdir -p /srv/tftp/dist/grml/grml32 mkdir -p /srv/tftp/dist/grml/grml64 mount -t iso9660 -o loop /srv/tftp/data/grml32-full_2017.05.iso /srv/tftp/dist/grml/grml32 mount -t iso9660 -o loop /srv/tftp/data/grml64-full_2017.05.iso /srv/tftp/dist/grml/grml64 TFTP server We will use atftps in standalone mode, so its configuration file /etc/default/atftpd should look like: USE_INETD=false OPTIONS="--port 69 --tftpd-timeout 300 --retry-timeout 5 --maxthread 100 --verbose=5 /srv/tftp" DHCP server Install ISC dhcp server apt-get update apt-get install isc-dhcp-server Create/modify configuration file /etc/dhcp/dhcpd.conf # next variables will be shown in dhcpd.leases file set vendorclass-string = option vendor-class-identifier; set userclass-string = option user-class; ddns-update-style none; allow booting; deny bootp; #default authoritative; log-facility local7; option client-arch code 93 = unsigned integer 16; # RFC4578 subnet 192.168.101.0 netmask 255.255.255.0 { default-lease-time 3600; max-lease-time 7200; option subnet-mask 255.255.255.0; option routers 192.168.101.1; option domain-name-servers 192.168.101.1; next-server 192.168.101.1; option domain-name "grml.lan"; option domain-search "grml.lan"; option router-discovery false; #flag pool { range 192.168.101.50 192.168.101.69; } pool { range 192.168.101.80 192.168.101.99; } } ## List an unused interface here # subnet 192.168.1.0 netmask 255.255.255.0 { #} option space ipxe; option ipxe-encap-opts code 175 = encapsulate ipxe; option ipxe.priority code 1 = signed integer 8; option ipxe.keep-san code 8 = unsigned integer 8; option ipxe.skip-san-boot code 9 = unsigned integer 8; option ipxe.syslogs code 85 = string; option ipxe.cert code 91 = string; option ipxe.privkey code 92 = string; option ipxe.crosscert code 93 = string; option ipxe.no-pxedhcp code 176 = unsigned integer 8; option ipxe.bus-id code 177 = string; option ipxe.san-filename code 188 = string; option ipxe.bios-drive code 189 = unsigned integer 8; option ipxe.username code 190 = string; option ipxe.password code 191 = string; option ipxe.reverse-username code 192 = string; option ipxe.reverse-password code 193 = string; option ipxe.version code 235 = string; option iscsi-initiator-iqn code 203 = string; option ipxe.pxeext code 16 = unsigned integer 8; option ipxe.iscsi code 17 = unsigned integer 8; option ipxe.aoe code 18 = unsigned integer 8; option ipxe.http code 19 = unsigned integer 8; option ipxe.https code 20 = unsigned integer 8; option ipxe.tftp code 21 = unsigned integer 8; option ipxe.ftp code 22 = unsigned integer 8; option ipxe.dns code 23 = unsigned integer 8; option ipxe.bzimage code 24 = unsigned integer 8; option ipxe.multiboot code 25 = unsigned integer 8; option ipxe.slam code 26 = unsigned integer 8; option ipxe.srp code 27 = unsigned integer 8; option ipxe.nbi code 32 = unsigned integer 8; option ipxe.pxe code 33 = unsigned integer 8; option ipxe.elf code 34 = unsigned integer 8; option ipxe.comboot code 35 = unsigned integer 8; option ipxe.efi code 36 = unsigned integer 8; option ipxe.fcoe code 37 = unsigned integer 8; option ipxe.vlan code 38 = unsigned integer 8; option ipxe.menu code 39 = unsigned integer 8; option ipxe.sdi code 40 = unsigned integer 8; option ipxe.nfs code 41 = unsigned integer 8; option ipxe.no-pxedhcp 1; if not exists client-arch { #guessing . . . filename "ipxe/bin/undionly.kpxe"; } elsif exists user-class and option user-class = "iPXE" { filename "http://192.168.101.1/tftp/dist/bootstrap.ipxe"; } elsif substring(option client-arch,0,0) = option client-arch { #guessing . . . filename "ipxe/bin/undionly.kpxe"; } elsif option client-arch = encode-int (0,16) { # 0 x86 BIOS filename "ipxe/bin/ipxe.pxe"; } elsif option client-arch = encode-int (7,16) { # 7 x64 UEFI filename "ipxe/bin-x86_64-efi/ipxe.efi"; } elsif option client-arch = encode-int (9,16) { # 9 EBC filename "ipxe/bin-x86_64-efi/ipxe.efi"; } elsif option client-arch = encode-int (16,16) { # 16 x64 uefi boot from http option vendor-class-identifier "HTTPClient"; filename "http://192.168.101.1/tftp/ipxe/bin-x86_64-efi/ipxe.efi"; } # host testpc1 { # hardware ethernet 01:02:03:04:05:06; # fixed-address 192.168.101.10; # next-server 192.168.101.1; # if exists user-class and option user-class = "iPXE" { # filename "http://192.168.101.1/tftp/dist/otherbootstrap.ipxe"; # } else { # filename "ipxe/bin-x86_64-efi/ipxe.efi"; # } # } # # host testpc2 { # hardware ethernet 01:02:03:04:05:07; # fixed-address 192.168.101.20; # next-server 192.168.101.1; # filename "lpxelinux.0"; # } Web server Install/use nginx apt-get install nginx Configure nginx - it is enough to leave default configuration in /etc/nginx/sites-available/default but change directive root. For debuging purposes you can put also 'autoindex on' directive there. Result is here. server { listen 80 default_server; root /srv; index index.html index.htm index.nginx-debian.html; server_name _; location / { autoindex on; } } IPXE There is ipxe.deb package in standard repository but better results were obtained by own compiled binaries or binaries from home web page wget http://boot.ipxe.org/ipxe.efi wget http://boot.ipxe.org/undionly.kpxe wget http://boot.ipxe.org/ipxe.pxe mkdir -p /srv/tftp/ipxe/bin mkdir -p /srv/tftp/ipxe/bin-x86_64-efi cp undionly.kpxe ipxe/bin/undionly.kpxe cp ipxe.pxe ipxe/bin/ipxe.pxe cp ipxe.efi ipxe/bin-x86_64-efi/ipxe.efi Script /srv/tftp/dist/bootstrap.ipxe #!ipxe cpuid --ext 29 && set distribution grml64 || set distribution grml32 chain http://192.168.101.1/tftp/dist/${distribution}.ipxe || shell Script /srv/tftp/dist/grml64.ipxe #!ipxe set httpserver 192.168.101.1 set httpbase http://${httpserver}/tftp set dist grml64 set httpsrc ${httpbase}/dist/${dist} echo httpsrc=${httpsrc} set kernelargs initrd=initrd.img boot=live apm=power-off vga=791 nomce fetch=${httpsrc}/live/grml64-full/grml64-full.squashfs nobeep noeject noprompt noblank keyboard=us xkeyboard=us tz=Europe/Bratislava hostname ssh=password echo 'Loading kernel...' kernel ${httpsrc}/boot/grml64full/vmlinuz ${kernelargs} echo 'Loading initrd...' initrd ${httpsrc}/boot/grml64full/initrd.img initrd.img boot # there is also possible to convert syslinux/grub menu distributed on grml installation media to ipxe menu and build this menu to this script Script /srv/tftp/dist/grml32.ipxe The same contents as /srv/tftp/dist/grml64.ipxe, only change occurrence of string 64 with 32 DNS server For this example we are using IP addresses so we will not use/configure DNS server at all Finale Start/restart all daemons systemctl stop atftpd systemctl stop nginx systemctl stop dhcpd systemctl start atftpd systemctl start nginx systemctl start dhcpd Happy booting Peter

1 0

how to recognize each RAID member separately
by josefh.maier＠hushmail.com 11 Okt '17

11 Okt '17

Hello I tried to make a backup of a HP DL380 G5 (W28K) with a HP Smart Array P400 controller with 4 RAID-members (4 75GB SAS drives) The Linux Live DVD's and Acronis TrueImage i' am unsing, do show that 4 disks as a singe LUN :-( To my knowledge such "Single-LUN backups" can make problem if they should be restored if a harddisk is changed before... Therefore i would feel much more comfortable, if from each harddirve could be made a separate DD-image. Question: Is there a way to have GRML seen that 4 disks as separate disks (and NOT as a single LUN)? Thank you very much for every feedback! Joe

2 1

minimal changes needed to have non-graphical startup
by Marc Haber 03 Okt '17

03 Okt '17

Hi, recent HP servers do have an SD card slot which is suitable to host a rescue system. The same approach also applies ot an USB stick that can be pushed into a port and selected from the remote console. Of course, the easiest way to have this is just dd'ing an grml iso to the medium and then plugging it in without more ado. In the HP case, one needs a special license to have access to the graphical console. Some systems (for example the rather common MicroServer Gen8) also need a license to get access to the text console. The only thing that one gets on the Microserver Gen8 without inserting more coins is a virtual serial console, which is suitable to access the BIOS and boot an OS that can use a serial console. With grub, one can even boot a regular Linux OS with seeing the boot manager on the virtual serial port. Unfortunately, grml has a graphical selection screen for the choice of boot option. This makes it impossible to select a boot option or give additional parameters without the "big", expensive license. Is there a possibility to remaster grml without the graphical boot screen? Having a classical text oriented ISOLINUX screen is fine, having ISOLINUX present that option on ttyS0 instead of a console would be perfect. Actually, I would love to have the possibility to do a simple patch in an otherwise unchanged grml image so that my ProLiant grml is as close to "release" grml as possible. I would appreciate a hint if that is already possible. While I do understand that having a nice-looking selection screen is nice and important for user acceptance, this severely reduces grml's attractivity for the server jockey who usually doesn't have graphical access to the systems. 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

1 0

Remastering docs updated, help needed
by Marc Haber 03 Okt '17

03 Okt '17

Hi, the remastering docs on http://wiki.grml.org/doku.php?id=remastering started to bitrot a way a bit, so I took a dive in removing historic information to the appropriate place on the page. I think that the documentation is much more clearer now. I need somebody with better knowledge about the build process fill the FAI table in the web page and also to give the information where future images will hold the information about how they were built. Is there still a supported way to remaster the image without actually touching the squashfs, for example if one wants to build a local .iso file with a grml.sh file on it or a non-graphical boot screen? If there is, I think this should be on the remastering page as well. I have prepared the page to host this information. Please either edit the wiki page directly, or give this information here so that I can incorporate the information myself. Thanks for helping with updating the docs! 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

1 0

***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