From jheim at math.wisc.edu Tue Aug 22 18:07:33 2017 From: jheim at math.wisc.edu (John G Heim) Date: Tue, 22 Aug 2017 11:07:33 -0500 Subject: [Grml] running a script automatically after boot Message-ID: 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 at math.wisc.edu; sip://jheim at sip.linphone.org From lupe at lupe-christoph.de Tue Aug 22 18:46:49 2017 From: lupe at lupe-christoph.de (Lupe Christoph) Date: Tue, 22 Aug 2017 18:46:49 +0200 Subject: [Grml] running a script automatically after boot In-Reply-To: References: Message-ID: <20170822164649.go4hojedracio2u6@lupe-christoph.de> On Tuesday, 2017-08-22 at 11:07:33 -0500, John G Heim wrote: > 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 Start here: https://grml.org/config/grml-autoconfig.1.html You need a USB partition with a filesystem that has the the label GRMLCFG. On that filesystem, you put a script named grml.sh in a directory named scripts. HTH, 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 | From mh+grml at zugschlus.de Thu Aug 31 15:56:48 2017 From: mh+grml at zugschlus.de (Marc Haber) Date: Thu, 31 Aug 2017 15:56:48 +0200 Subject: [Grml] How do I find out which FAI classes were used to build a Message-ID: <20170831135648.6qmscgr4jfdrpvw3@torres.zugschlus.de> 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 From mika at grml.org Thu Aug 31 21:16:38 2017 From: mika at grml.org (Michael Prokop) Date: Thu, 31 Aug 2017 21:16:38 +0200 Subject: [Grml] How do I find out which FAI classes were used to build a In-Reply-To: <20170831135648.6qmscgr4jfdrpvw3@torres.zugschlus.de> References: <20170831135648.6qmscgr4jfdrpvw3@torres.zugschlus.de> Message-ID: <2017-08-31T21-08-57@devnull.michael-prokop.at> * Marc Haber [Thu Aug 31, 2017 at 03:56:48PM +0200]: > 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? The best we currently have are the build logs, e.g. https://jenkins.grml.org/job/grml64-full_Release/32/console has the details for the grml64-full.2017.05 ISO. So it was generated using the following classes: DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT This raises an interesting issue, it might be nice to include such build information inside the ISO itself by default. What about something like: % jo build_date="$(TZ=UTC date +%s)" grml_live_classes=DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT grml_live_version=0.30.2 build_tool=grml-live debian_release=stretch grml_live_options="-F -V -A" architecture=amd64 grml_version=build2065 debian_release=autobuild-build2065 grml_name=grml64-full_sid build_host="jenkins.grml.org" | jq -S '.' { "architecture": "amd64", "build_date": 1504206859, "build_host": "jenkins.grml.org", "build_tool": "grml-live", "debian_release": "autobuild-build2065", "grml_live_classes": "DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT", "grml_live_options": "-F -V -A", "grml_live_version": "0.30.2", "grml_name": "grml64-full_sid", "grml_version": "build2065" } put into /GRML/buildinfo.json or so on the ISO? regards, -mika- -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: