From: IT Superhack <itsuperhack@web.de>
To: development@lists.ipfire.org
Subject: Question about Pakfire Update process
Date: Sun, 22 Mar 2015 10:43:03 +0100 [thread overview]
Message-ID: <550E8EA7.4030602@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi everybody,
I am currently working on bug #10767.
During the last week, I wrote a shell script which compares the
running kernel to the installed kernel files (/boot/...). If they are
different, it recreates the files "boot.script" and "boot.scr".
Because of that, the user doesn't have to do this after every kernel
update.
However, the script needs to be triggered after a kernel update took
place. (Of course, I could copy it into /etc/cron.hourly/, but in my
opinion, this is not a good solution.) I guess it needs to be
triggered by Pakfire after the update process is done.
Now comes my question: How do I do this? How can I tell Pakfire to run
a custom shell script after an update?
I would be very greatful if you could mail me some hints.
Best regards,
Timmothy Wilson
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCgAGBQJVDo6nAAoJEOyLa1C5EazroQUH/1qIY+m5t88g/cchlKEcSzPK
nNbwrWhNXjpxai2x/xsnDJnxKOr84336GhZv55zs7yGqddzqsCwpsBy7TMez+BcW
lYJ3v64e9uU0lex40I3kkgdbe2olEZErY3Fv8WW4Tid+R2hXkFT5DrFAKQXR9krC
VcRiYTq8msAxJ67icGq/inJdLxByBSBtV44NpAtVOh/EkqT+pzk2KFCHsdkcibJO
DJRSdMh9jRwX2dPnD2GhL2R5MV+AnIplDqcAq8BPXtQ/zPKCIKSfCGGG7zM06Djc
pC9oikUfQUDSiVeDj3DA8J5mWsqxbS3aKhiZx8es2K19KgLjbJG9hkQvNepo1Xg=
=cXOf
-----END PGP SIGNATURE-----
next reply other threads:[~2015-03-22 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 9:43 IT Superhack [this message]
2015-03-22 21:35 ` Michael Tremer
2015-03-23 17:14 IT Superhack
2015-03-24 13:41 ` Michael Tremer
2015-03-24 17:33 ` IT Superhack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=550E8EA7.4030602@web.de \
--to=itsuperhack@web.de \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox