Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux.ubuntu > #186148 > unrolled thread

Linux History

Started byMarek Novotny <marek.novotny@marspolar.com>
First post2016-01-12 19:01 -0800
Last post2016-01-13 09:59 -0500
Articles 14 on this page of 34 — 10 participants

Back to article view | Back to alt.os.linux.ubuntu

Contents

  Linux History Marek Novotny <marek.novotny@marspolar.com> - 2016-01-12 19:01 -0800
    Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-12 22:34 -0500
    Re: Linux History Wildman <best_lay@yahoo.com> - 2016-01-12 21:51 -0600
    Re: Linux History stepore <linshine@here.now> - 2016-01-12 20:05 -0800
      Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-12 23:41 -0500
        Re: Linux History Dan C <youmustbejoking@lan.invalid> - 2016-01-17 03:19 +0000
          Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-17 06:40 +0000
            Re: Linux History Dan C <youmustbejoking@lan.invalid> - 2016-01-17 19:43 +0000
      Re: Linux History "Cybe R. Wizard" <cybe_r_wizard@WizardsTower.invalid> - 2016-01-12 23:23 -0600
        Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-13 01:08 -0500
    Re: Linux History "Cybe R. Wizard" <cybe_r_wizard@WizardsTower.invalid> - 2016-01-12 23:19 -0600
      Re: Linux History stepore <linshine@here.now> - 2016-01-12 21:56 -0800
        Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-13 01:08 -0500
        Re: Linux History "Cybe R. Wizard" <cybe_r_wizard@WizardsTower.invalid> - 2016-01-13 00:21 -0600
          Re: Linux History stepore <linshine@here.now> - 2016-01-12 23:07 -0800
            Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-13 04:47 -0500
          Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-13 07:42 -0500
            Re: Linux History "Cybe R. Wizard" <cybe_r_wizard@WizardsTower.invalid> - 2016-01-13 08:34 -0600
              Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-13 09:41 -0500
              Re: Linux History "jeff g." <jeff.g.group@att.net> - 2016-01-13 07:38 -0800
                Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-13 11:15 -0500
                  Re: Linux History "Jonathan N. Little" <lws4art@gmail.com> - 2016-01-13 11:29 -0500
                    Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-13 11:41 -0500
                      Re: Linux History "Jonathan N. Little" <lws4art@gmail.com> - 2016-01-13 11:54 -0500
                        Re: Linux History "Jonathan N. Little" <lws4art@gmail.com> - 2016-01-13 12:04 -0500
                        Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-13 12:12 -0500
                          Re: Linux History "Jonathan N. Little" <lws4art@gmail.com> - 2016-01-13 13:05 -0500
                            Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-13 17:05 -0500
                              Re: Linux History "Jonathan N. Little" <lws4art@gmail.com> - 2016-01-13 18:30 -0500
                                Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-13 21:22 -0500
              Re: Linux History Bud Frede <frede@mouse-potato.com> - 2016-01-14 16:42 -0500
                Re: Linux History DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> - 2016-01-15 08:59 -0500
    Re: Linux History mechanic <mechanic@example.net> - 2016-01-13 11:48 +0000
    Re: Linux History Bud Frede <frede@mouse-potato.com> - 2016-01-13 09:59 -0500

Page 2 of 2 — ← Prev page 1 [2]

#186193

FromDecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org>
Date2016-01-13 11:15 -0500
Message-ID<90uc9bhlbekenje8ou7u51nq92p8fncnfh@4ax.com>
In reply to#186192
On Wed, 13 Jan 2016 07:38:37 -0800, "jeff g." <jeff.g.group@att.net>
Gave us:

>On 01/13/2016 06:34 AM, Cybe R. Wizard wrote:
>> On Wed, 13 Jan 2016 07:42:32 -0500
>> DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> wrote:
>>
>>>   Hey Cybe...  I have another debian question for you.
>>>
>>>    I used to know, but it has slipped my mind here lately, and I am
>>> sure you'll likely know.
>>>
>>>    When one runs apt-get upgrade and it causes a respin of Grub2 menu,
>>> where does the update-grub call get made from?
>>>
>>>    I know there is some post apt file that gets triggered after, but I
>>> cannot remember what or where the file is for the life of me.
>>
>> Well, you've stumped me.  I never have bothered to check.
>>
>> Cybe R. Wizard
>>
>etc/default/grub

  Nope.  Thanks, but I want the file that apt-get reads that then tells
it to run update-grub.

  I am then going to point it to update-burg instead.

  I already know where the files are that update-grub (and update-burg)
use are.  I am looking for the post system update trigger file that
calls to create a new initrd, etc.  That same file is the file that also
calls update-grub after a new kernel installation takes place.

  As I said... I used to know.  It was actually about three files than
can call it.

  Maybe I should become more familiar with grep.

[toc] | [prev] | [next] | [standalone]

#186194

From"Jonathan N. Little" <lws4art@gmail.com>
Date2016-01-13 11:29 -0500
Message-ID<n75trp$3dc$1@dont-email.me>
In reply to#186193
DecadentLinuxUserNumeroUno wrote:
> On Wed, 13 Jan 2016 07:38:37 -0800, "jeff g." <jeff.g.group@att.net>
> Gave us:
>
>> On 01/13/2016 06:34 AM, Cybe R. Wizard wrote:
>>> On Wed, 13 Jan 2016 07:42:32 -0500
>>> DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> wrote:
>>>
>>>>    Hey Cybe...  I have another debian question for you.
>>>>
>>>>     I used to know, but it has slipped my mind here lately, and I am
>>>> sure you'll likely know.
>>>>
>>>>     When one runs apt-get upgrade and it causes a respin of Grub2 menu,
>>>> where does the update-grub call get made from?
>>>>
>>>>     I know there is some post apt file that gets triggered after, but I
>>>> cannot remember what or where the file is for the life of me.
>>>
>>> Well, you've stumped me.  I never have bothered to check.
>>>
>>> Cybe R. Wizard
>>>
>> etc/default/grub
>
>    Nope.  Thanks, but I want the file that apt-get reads that then tells
> it to run update-grub.
>
>    I am then going to point it to update-burg instead.
>
>    I already know where the files are that update-grub (and update-burg)
> use are.  I am looking for the post system update trigger file that
> calls to create a new initrd, etc.  That same file is the file that also
> calls update-grub after a new kernel installation takes place.
>
>    As I said... I used to know.  It was actually about three files than
> can call it.
>
>    Maybe I should become more familiar with grep.
>

WAG in the kernel update package install script?

-- 
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

[toc] | [prev] | [next] | [standalone]

#186196

FromDecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org>
Date2016-01-13 11:41 -0500
Message-ID<fbvc9b9jue23his88ghjithdvqa0kt93ar@4ax.com>
In reply to#186194
On Wed, 13 Jan 2016 11:29:16 -0500, "Jonathan N. Little"
<lws4art@gmail.com> Gave us:

>DecadentLinuxUserNumeroUno wrote:
>> On Wed, 13 Jan 2016 07:38:37 -0800, "jeff g." <jeff.g.group@att.net>
>> Gave us:
>>
>>> On 01/13/2016 06:34 AM, Cybe R. Wizard wrote:
>>>> On Wed, 13 Jan 2016 07:42:32 -0500
>>>> DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> wrote:
>>>>
>>>>>    Hey Cybe...  I have another debian question for you.
>>>>>
>>>>>     I used to know, but it has slipped my mind here lately, and I am
>>>>> sure you'll likely know.
>>>>>
>>>>>     When one runs apt-get upgrade and it causes a respin of Grub2 menu,
>>>>> where does the update-grub call get made from?
>>>>>
>>>>>     I know there is some post apt file that gets triggered after, but I
>>>>> cannot remember what or where the file is for the life of me.
>>>>
>>>> Well, you've stumped me.  I never have bothered to check.
>>>>
>>>> Cybe R. Wizard
>>>>
>>> etc/default/grub
>>
>>    Nope.  Thanks, but I want the file that apt-get reads that then tells
>> it to run update-grub.
>>
>>    I am then going to point it to update-burg instead.
>>
>>    I already know where the files are that update-grub (and update-burg)
>> use are.  I am looking for the post system update trigger file that
>> calls to create a new initrd, etc.  That same file is the file that also
>> calls update-grub after a new kernel installation takes place.
>>
>>    As I said... I used to know.  It was actually about three files than
>> can call it.
>>
>>    Maybe I should become more familiar with grep.
>>
>
>WAG in the kernel update package install script?

  No, it does not come from the package you install, it comes from apt
or dpkg (more likely) and it "knows" it just updated the kernel and that
triggers it to run "update-grub".

  A simple grep for "update-grub" on your own system would find it.

  I simply do not know what the grep syntax needs to be, and thought I
would ask cybe thinking he would be familiar with what I referred to.
Starting to look like nobody is..

  I think it is even called a trigger in package mgr circles.

[toc] | [prev] | [next] | [standalone]

#186198

From"Jonathan N. Little" <lws4art@gmail.com>
Date2016-01-13 11:54 -0500
Message-ID<n75vb6$9tk$1@dont-email.me>
In reply to#186196
DecadentLinuxUserNumeroUno wrote:

>
>    A simple grep for "update-grub" on your own system would find it.
>
>    I simply do not know what the grep syntax needs to be, and thought I
> would ask cybe thinking he would be familiar with what I referred to.
> Starting to look like nobody is..
>
>    I think it is even called a trigger in package mgr circles.
>
sudo grep -r update-grub *
[sudo] password for jonathan:
grep: blkid.tab: No such file or directory
default/grub:# If you change this file, run 'update-grub' afterwards to 
update
default/grub.ucf-dist:# If you change this file, run 'update-grub' 
afterwards to update
kernel/postinst.d/zz-update-grub:which update-grub >/dev/null 2>&1 || exit 0
kernel/postinst.d/zz-update-grub:    # time by calling update-grub 
multiple times on upgrade and removal.
kernel/postinst.d/zz-update-grub:               exec update-grub
kernel/postrm.d/zz-update-grub:which update-grub >/dev/null 2>&1 || exit 0
kernel/postrm.d/zz-update-grub:    # time by calling update-grub 
multiple times on upgrade and removal.
kernel/postrm.d/zz-update-grub:         exec update-grub

-- 
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

[toc] | [prev] | [next] | [standalone]

#186199

From"Jonathan N. Little" <lws4art@gmail.com>
Date2016-01-13 12:04 -0500
Message-ID<n75vtc$boe$1@dont-email.me>
In reply to#186198
Jonathan N. Little wrote:

> sudo grep -r update-grub *
> [sudo] password for jonathan:
> grep: blkid.tab: No such file or directory
> default/grub:# If you change this file, run 'update-grub' afterwards to
> update
> default/grub.ucf-dist:# If you change this file, run 'update-grub'
> afterwards to update
> kernel/postinst.d/zz-update-grub:which update-grub >/dev/null 2>&1 ||
> exit 0
> kernel/postinst.d/zz-update-grub:    # time by calling update-grub
> multiple times on upgrade and removal.
> kernel/postinst.d/zz-update-grub:               exec update-grub
> kernel/postrm.d/zz-update-grub:which update-grub >/dev/null 2>&1 || exit 0
> kernel/postrm.d/zz-update-grub:    # time by calling update-grub
> multiple times on upgrade and removal.
> kernel/postrm.d/zz-update-grub:         exec update-grub
>

So you need to replace /etc/kernel/postinst.d/zz-update-grub and 
/etc/kernel/postrm.d/zz-update-grub with your own "burg" versions 
zz-update-burg...

-- 
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

[toc] | [prev] | [next] | [standalone]

#186200

FromDecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org>
Date2016-01-13 12:12 -0500
Message-ID<cb1d9bda9vgu6ddo5pag8knosdv5mft274@4ax.com>
In reply to#186198
On Wed, 13 Jan 2016 11:54:32 -0500, "Jonathan N. Little"
<lws4art@gmail.com> Gave us:

>DecadentLinuxUserNumeroUno wrote:
>
>>
>>    A simple grep for "update-grub" on your own system would find it.
>>
>>    I simply do not know what the grep syntax needs to be, and thought I
>> would ask cybe thinking he would be familiar with what I referred to.
>> Starting to look like nobody is..
>>
>>    I think it is even called a trigger in package mgr circles.
>>
>sudo grep -r update-grub *
>[sudo] password for jonathan:
>grep: blkid.tab: No such file or directory
>default/grub:# If you change this file, run 'update-grub' afterwards to 
>update
>default/grub.ucf-dist:# If you change this file, run 'update-grub' 
>afterwards to update
>kernel/postinst.d/zz-update-grub:which update-grub >/dev/null 2>&1 || exit 0
>kernel/postinst.d/zz-update-grub:    # time by calling update-grub 
>multiple times on upgrade and removal.
>kernel/postinst.d/zz-update-grub:               exec update-grub
>kernel/postrm.d/zz-update-grub:which update-grub >/dev/null 2>&1 || exit 0
>kernel/postrm.d/zz-update-grub:    # time by calling update-grub 
>multiple times on upgrade and removal.
>kernel/postrm.d/zz-update-grub:         exec update-grub

  Yeah....  Looks like I should search "exec update-grub"

  But I see it seems to be "postinst.d" is where I want to look.

  Thanks.  After all these years I should really read up on and use
grep.  I just never did a lot of search type poking around before.

[toc] | [prev] | [next] | [standalone]

#186205

From"Jonathan N. Little" <lws4art@gmail.com>
Date2016-01-13 13:05 -0500
Message-ID<n763g7$rdv$1@dont-email.me>
In reply to#186200
DecadentLinuxUserNumeroUno wrote:
> On Wed, 13 Jan 2016 11:54:32 -0500, "Jonathan N. Little"
> <lws4art@gmail.com> Gave us:
>
>> DecadentLinuxUserNumeroUno wrote:
>>
>>>
>>>     A simple grep for "update-grub" on your own system would find it.
>>>
>>>     I simply do not know what the grep syntax needs to be, and thought I
>>> would ask cybe thinking he would be familiar with what I referred to.
>>> Starting to look like nobody is..
>>>
>>>     I think it is even called a trigger in package mgr circles.
>>>
>> sudo grep -r update-grub *
>> [sudo] password for jonathan:
>> grep: blkid.tab: No such file or directory
>> default/grub:# If you change this file, run 'update-grub' afterwards to
>> update
>> default/grub.ucf-dist:# If you change this file, run 'update-grub'
>> afterwards to update
>> kernel/postinst.d/zz-update-grub:which update-grub >/dev/null 2>&1 || exit 0
>> kernel/postinst.d/zz-update-grub:    # time by calling update-grub
>> multiple times on upgrade and removal.
>> kernel/postinst.d/zz-update-grub:               exec update-grub
>> kernel/postrm.d/zz-update-grub:which update-grub >/dev/null 2>&1 || exit 0
>> kernel/postrm.d/zz-update-grub:    # time by calling update-grub
>> multiple times on upgrade and removal.
>> kernel/postrm.d/zz-update-grub:         exec update-grub
>
>    Yeah....  Looks like I should search "exec update-grub"
>
>    But I see it seems to be "postinst.d" is where I want to look.
>
>    Thanks.  After all these years I should really read up on and use
> grep.  I just never did a lot of search type poking around before.
>

As I replied to myself it looks like all you need to do is make your own 
zz-update-burg and replace the zz-update-grub  in both

/etc/kernel/postinst.d/
/etc/kernel/postrm.d/

Assuming the command for updating burg is 'update-burg' and the cfg file 
is in '/boot/burg/burg.cfg' then this modification of the grub script 
should work

#! /bin/sh
#################################################################
#  zz-update-burg
#+ modified zz-update-grub to use burg instead of grub bootloader
#################################################################
set -e

which update-burg >/dev/null 2>&1 || exit 0

if type running-in-container >/dev/null 2>&1 && \
    running-in-container >/dev/null; then
         exit 0
fi

set -- $DEB_MAINT_PARAMS
mode="${1#\'}"
mode="${mode%\'}"
case $0:$mode in
     # Only run on postinst configure and postrm remove, to avoid wasting
     # time by calling update-burg multiple times on upgrade and removal.
     # Also run if we have no DEB_MAINT_PARAMS, in order to work with old
     # kernel packages.
 
*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
         if [ -e /boot/burg/burg.cfg ]; then
                 exec update-burg
         fi
         ;;
esac

exit 0


-- 
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

[toc] | [prev] | [next] | [standalone]

#186218

FromDecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org>
Date2016-01-13 17:05 -0500
Message-ID<jfid9bhnlpb1hr9u50qlkf650snrve5ia2@4ax.com>
In reply to#186205
On Wed, 13 Jan 2016 13:05:29 -0500, "Jonathan N. Little"
<lws4art@gmail.com> Gave us:

snip

>As I replied to myself it looks like all you need to do is make your own 
>zz-update-burg and replace the zz-update-grub  in both
>
>/etc/kernel/postinst.d/
>/etc/kernel/postrm.d/
>
>Assuming the command for updating burg is 'update-burg' and the cfg file 
>is in '/boot/burg/burg.cfg' then this modification of the grub script 
>should work
>
>#! /bin/sh
>#################################################################
>#  zz-update-burg
>#+ modified zz-update-grub to use burg instead of grub bootloader
>#################################################################
>set -e
>
>which update-burg >/dev/null 2>&1 || exit 0
>
>if type running-in-container >/dev/null 2>&1 && \
>    running-in-container >/dev/null; then
>         exit 0
>fi
>
>set -- $DEB_MAINT_PARAMS
>mode="${1#\'}"
>mode="${mode%\'}"
>case $0:$mode in
>     # Only run on postinst configure and postrm remove, to avoid wasting
>     # time by calling update-burg multiple times on upgrade and removal.
>     # Also run if we have no DEB_MAINT_PARAMS, in order to work with old
>     # kernel packages.
> 
>*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
>         if [ -e /boot/burg/burg.cfg ]; then
>                 exec update-burg
>         fi
>         ;;
>esac
>
>exit 0

  Unless the actual call is still "zz-update-grub"

  Then, I need to change the calls within the file, but retain the
original file name.

[toc] | [prev] | [next] | [standalone]

#186223

From"Jonathan N. Little" <lws4art@gmail.com>
Date2016-01-13 18:30 -0500
Message-ID<n76mh6$cvp$1@dont-email.me>
In reply to#186218
DecadentLinuxUserNumeroUno wrote:
> On Wed, 13 Jan 2016 13:05:29 -0500, "Jonathan N. Little"
> <lws4art@gmail.com> Gave us:
>
> snip
>
>> As I replied to myself it looks like all you need to do is make your own
>> zz-update-burg and replace the zz-update-grub  in both
>>
>> /etc/kernel/postinst.d/
>> /etc/kernel/postrm.d/
>>
>> Assuming the command for updating burg is 'update-burg' and the cfg file
>> is in '/boot/burg/burg.cfg' then this modification of the grub script
>> should work
>>
>> #! /bin/sh
>> #################################################################
>> #  zz-update-burg
>> #+ modified zz-update-grub to use burg instead of grub bootloader
>> #################################################################
>> set -e
>>
>> which update-burg >/dev/null 2>&1 || exit 0
>>
>> if type running-in-container >/dev/null 2>&1 && \
>>     running-in-container >/dev/null; then
>>          exit 0
>> fi
>>
>> set -- $DEB_MAINT_PARAMS
>> mode="${1#\'}"
>> mode="${mode%\'}"
>> case $0:$mode in
>>      # Only run on postinst configure and postrm remove, to avoid wasting
>>      # time by calling update-burg multiple times on upgrade and removal.
>>      # Also run if we have no DEB_MAINT_PARAMS, in order to work with old
>>      # kernel packages.
>>
>> */postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
>>          if [ -e /boot/burg/burg.cfg ]; then
>>                  exec update-burg
>>          fi
>>          ;;
>> esac
>>
>> exit 0
>
>    Unless the actual call is still "zz-update-grub"
>
>    Then, I need to change the calls within the file, but retain the
> original file name.
>

No you don't that is a standard partials include. Any script in the 
WHATEVER.d directory is included in order that is why the prefix "zz-" 
to make sure the script runs LAST. You can remove the "zz-update-grub", 
put in your "zz-update-burg", make sure it is executable and it will run.

-- 
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

[toc] | [prev] | [next] | [standalone]

#186227

FromDecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org>
Date2016-01-13 21:22 -0500
Message-ID<3f1e9b5k7keoi2n9g3b4dtvg4jievpe5n3@4ax.com>
In reply to#186223
On Wed, 13 Jan 2016 18:30:16 -0500, "Jonathan N. Little"
<lws4art@gmail.com> Gave us:

>DecadentLinuxUserNumeroUno wrote:
>> On Wed, 13 Jan 2016 13:05:29 -0500, "Jonathan N. Little"
>> <lws4art@gmail.com> Gave us:
>>
>> snip
>>
>>> As I replied to myself it looks like all you need to do is make your own
>>> zz-update-burg and replace the zz-update-grub  in both
>>>
>>> /etc/kernel/postinst.d/
>>> /etc/kernel/postrm.d/
>>>
>>> Assuming the command for updating burg is 'update-burg' and the cfg file
>>> is in '/boot/burg/burg.cfg' then this modification of the grub script
>>> should work
>>>
>>> #! /bin/sh
>>> #################################################################
>>> #  zz-update-burg
>>> #+ modified zz-update-grub to use burg instead of grub bootloader
>>> #################################################################
>>> set -e
>>>
>>> which update-burg >/dev/null 2>&1 || exit 0
>>>
>>> if type running-in-container >/dev/null 2>&1 && \
>>>     running-in-container >/dev/null; then
>>>          exit 0
>>> fi
>>>
>>> set -- $DEB_MAINT_PARAMS
>>> mode="${1#\'}"
>>> mode="${mode%\'}"
>>> case $0:$mode in
>>>      # Only run on postinst configure and postrm remove, to avoid wasting
>>>      # time by calling update-burg multiple times on upgrade and removal.
>>>      # Also run if we have no DEB_MAINT_PARAMS, in order to work with old
>>>      # kernel packages.
>>>
>>> */postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
>>>          if [ -e /boot/burg/burg.cfg ]; then
>>>                  exec update-burg
>>>          fi
>>>          ;;
>>> esac
>>>
>>> exit 0
>>
>>    Unless the actual call is still "zz-update-grub"
>>
>>    Then, I need to change the calls within the file, but retain the
>> original file name.
>>
>
>No you don't that is a standard partials include. Any script in the 
>WHATEVER.d directory is included in order that is why the prefix "zz-" 
>to make sure the script runs LAST. You can remove the "zz-update-grub", 
>put in your "zz-update-burg", make sure it is executable and it will run.

  Ahh.... I see now said the blind man.

  So my debian install matches this.

  I seem to remember finding it in a couple or even three places in one
of my ubu installs a long time ago though (which is why I do not
remember..  But my grep result matched yours on my debian system.

  Thanks.

[toc] | [prev] | [next] | [standalone]

#186249

FromBud Frede <frede@mouse-potato.com>
Date2016-01-14 16:42 -0500
Message-ID<dvqdndLdfbnOiwXLnZ2dnUU7-KOdnZ2d@supernews.com>
In reply to#186183
"Cybe R. Wizard" <cybe_r_wizard@WizardsTower.invalid> writes:

> On Wed, 13 Jan 2016 07:42:32 -0500
> DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> wrote:
>
>>  Hey Cybe...  I have another debian question for you.
>> 
>>   I used to know, but it has slipped my mind here lately, and I am
>> sure you'll likely know.
>> 
>>   When one runs apt-get upgrade and it causes a respin of Grub2 menu,
>> where does the update-grub call get made from?
>> 
>>   I know there is some post apt file that gets triggered after, but I
>> cannot remember what or where the file is for the life of me.
>
> Well, you've stumped me.  I never have bothered to check.

.deb packages can contain pre-intall and post-install scripts, so it's
probably post-install.

https://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.html

[toc] | [prev] | [next] | [standalone]

#186256

FromDecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org>
Date2016-01-15 08:59 -0500
Message-ID<vouh9b93vd49upo2c0b5h7559rbgo493pa@4ax.com>
In reply to#186249
On Thu, 14 Jan 2016 16:42:42 -0500, Bud Frede <frede@mouse-potato.com>
Gave us:

>"Cybe R. Wizard" <cybe_r_wizard@WizardsTower.invalid> writes:
>
>> On Wed, 13 Jan 2016 07:42:32 -0500
>> DecadentLinuxUserNumeroUno <DLU1@DecadentLinuxUser.org> wrote:
>>
>>>  Hey Cybe...  I have another debian question for you.
>>> 
>>>   I used to know, but it has slipped my mind here lately, and I am
>>> sure you'll likely know.
>>> 
>>>   When one runs apt-get upgrade and it causes a respin of Grub2 menu,
>>> where does the update-grub call get made from?
>>> 
>>>   I know there is some post apt file that gets triggered after, but I
>>> cannot remember what or where the file is for the life of me.
>>
>> Well, you've stumped me.  I never have bothered to check.
>
>.deb packages can contain pre-intall and post-install scripts, so it's
>probably post-install.
>
>https://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.html

  Of course it is post install..  Why would an app run a bootloader
update *before* a new kernel install?  Doh!

[toc] | [prev] | [next] | [standalone]

#186166

Frommechanic <mechanic@example.net>
Date2016-01-13 11:48 +0000
Message-ID<l8trpl0bg4bb.dlg@example1357.net>
In reply to#186148
On Tue, 12 Jan 2016 19:01:44 -0800, Marek Novotny wrote:

> Stupid test... I had to guess on a few of them and only got 15/18
> correct.
> 
> http://fossforce.com/2016/01/how-well-do-you-know-your-linux-history/

14/18
"We'd have to give you an A. You obviously know your Linux history."

[toc] | [prev] | [next] | [standalone]

#186191

FromBud Frede <frede@mouse-potato.com>
Date2016-01-13 09:59 -0500
Message-ID<vsudnXiyeZve-wvLnZ2dnUU7-RmdnZ2d@supernews.com>
In reply to#186148
Marek Novotny <marek.novotny@marspolar.com> writes:

> Stupid test... I had to guess on a few of them and only got 15/18
> correct.
>
> http://fossforce.com/2016/01/how-well-do-you-know-your-linux-history/

I got all of them right except the one about suing Mandrake. I guess I never
paid much attention to it.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | alt.os.linux.ubuntu

csiph-web