public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Question about Pakfire Update process
Date: Tue, 24 Mar 2015 14:41:42 +0100	[thread overview]
Message-ID: <1427204502.14172.171.camel@ipfire.org> (raw)
In-Reply-To: <55104A02.30507@web.de>

[-- Attachment #1: Type: text/plain, Size: 2566 bytes --]

Hi,

On Mon, 2015-03-23 at 18:14 +0100, IT Superhack wrote:
> Michael Tremer:
> > Hi Timmothy,
> > 
> > On Sun, 2015-03-22 at 10:43 +0100, IT Superhack wrote:
> >> Hi everybody,
> >> 
> >> I am currently working on bug #10767.
> > 
> > thanks for looking into this.
> > 
> >> 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.
> > 
> > I do not really get what this script is supposed to do. In case of
> > an update, the boot.script file will be overwritten any way. The
> > version with the binary header can then be created at build time.
> The installation manual
> (http://wiki.ipfire.org/en/hardware/arm/wandboard/wandboardquad) says:
> "Please note, after each kernel update the boot.script needs to be
> adjusted and the convert_bootscript.sh or the containing command needs
> to be executed."
> Thereof, the steps of adjusting boot.script and running mkimage seem to
> be necessary after each kernel update. They don't seem to be done by the
> update mechanism itself at the moment.

*What* needs to be adjusted?

> > 
> > What are you exactly trying to solve here?
> > 
> This is what I'm trying to provide: A script that can be executed by
> Pakfire after an update.
> It checks wether it runs on a wandboard and if it does, it updates the
> boot.script stuff.

*What* does it "update" with *what*?

> >> 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.
> > 
> > Cron is never the solution.
> > 
> >> 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 
> >> _______________________________________________ Development
> >> mailing list Development(a)lists.ipfire.org 
> >> http://lists.ipfire.org/mailman/listinfo/development
> 
> EDIT: Sorry, I mixed up the destination addresses and send the mail to
> Michael and not into the development list.
> 
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-03-24 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 17:14 IT Superhack
2015-03-24 13:41 ` Michael Tremer [this message]
2015-03-24 17:33   ` IT Superhack
  -- strict thread matches above, loose matches on Subject: below --
2015-03-22  9:43 IT Superhack
2015-03-22 21:35 ` Michael Tremer

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=1427204502.14172.171.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --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