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


Groups > linux.debian.user > #257062

Re: update-initramfs

From davidson <davidson@freevolt.org>
Newsgroups linux.debian.user
Subject Re: update-initramfs
Date 2023-04-11 21:50 +0200
Message-ID <Gjsa5-1nsD-3@gated-at.bofh.it> (permalink)
References <Gja3v-1c3b-3@gated-at.bofh.it> <GjcoF-1dp8-1@gated-at.bofh.it> <GjnN7-1kPi-5@gated-at.bofh.it> <Gjq8h-1maM-5@gated-at.bofh.it> <GjrnH-1mVt-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Tue, 11 Apr 2023 Michel Verdier wrote:
> Le 11 avril 2023 davidson a écrit :
>
>> The first experiment simply tried to replicate your observations (as I
>> understood them). Basically, I added "-kg" suffix to all the files in
>> /boot corresponding to latest installed kernel, so that I had
>> unsuffixed copies and "*-kg" ("knowngood") copies, and then tried
>>
>>  # update-initramfs -u
>
> I don't understand a point.

Hi Michel.

To be clear, I am not the OP.

> On my system I compiled kernel and thus build a linux-image-...deb
> with a specific tag.

That is much more work than I did. I compiled no custom kernel. I just
made copies of the files in /boot installed from package
linux-image-5.10.0-21-amd64, and the corresponding initrd.

Here is a run of my Experiment #1, in full:

# knowngood=( /boot/*-$(uname -r) )
# for ((i=0; i<${#knowngood[@]}; i+=1)) ; do cp -a "${knowngood[i]}" "${knowngood[i]/%/-kg}" ; done
# ls -l "${knowngood[@]}"
-rw-r--r-- 1 root root   236452 21 janv. 09:35 /boot/config-5.10.0-21-amd64
-rw-r--r-- 1 root root 29199065 10 avril 21:58 /boot/initrd.img-5.10.0-21-amd64
-rw-r--r-- 1 root root       83 21 janv. 09:35 /boot/System.map-5.10.0-21-amd64
-rw-r--r-- 1 root root  7019136 21 janv. 09:35 /boot/vmlinuz-5.10.0-21-amd64
# ls -l "${knowngood[@]/%/-kg}"
-rw-r--r-- 1 root root   236452 21 janv. 09:35 /boot/config-5.10.0-21-amd64-kg
-rw-r--r-- 1 root root 29199065 10 avril 21:58 /boot/initrd.img-5.10.0-21-amd64-kg
-rw-r--r-- 1 root root       83 21 janv. 09:35 /boot/System.map-5.10.0-21-amd64-kg
-rw-r--r-- 1 root root  7019136 21 janv. 09:35 /boot/vmlinuz-5.10.0-21-amd64-kg

# update-initramfs -u
# update-initramfs: Generating /boot/initrd.img-5.10.0-21-amd64-kg
W: missing /lib/modules/5.10.0-21-amd64-kg
W: Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/5.10.0-21-amd64-kg: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
cat: /var/tmp/mkinitramfs_9UHxvD/lib/modules/5.10.0-21-amd64-kg/modules.builtin: Aucun fichier ou dossier de ce type
find: ‘/var/tmp/mkinitramfs_9UHxvD/lib/modules/5.10.0-21-amd64-kg/kernel’: Aucun fichier ou dossier de ce type
W: Can't find modules.builtin.modinfo (for locating built-in drivers' firmware, supported in Linux >=5.2)
depmod: WARNING: could not open modules.order at /var/tmp/mkinitramfs_9UHxvD/lib/modules/5.10.0-21-amd64-kg: No such file or directory
depmod: WARNING: could not open modules.builtin at /var/tmp/mkinitramfs_9UHxvD/lib/modules/5.10.0-21-amd64-kg: No such file or directory
# ls -l "${knowngood[@]}"
-rw-r--r-- 1 root root   236452 21 janv. 09:35 /boot/config-5.10.0-21-amd64
-rw-r--r-- 1 root root 29199065 10 avril 21:58 /boot/initrd.img-5.10.0-21-amd64
                        ^^^^^^^^
-rw-r--r-- 1 root root       83 21 janv. 09:35 /boot/System.map-5.10.0-21-amd64
-rw-r--r-- 1 root root  7019136 21 janv. 09:35 /boot/vmlinuz-5.10.0-21-amd64
# ls -l "${knowngood[@]/%/-kg}"
-rw-r--r-- 1 root root  236452 21 janv. 09:35 /boot/config-5.10.0-21-amd64-kg
-rw-r--r-- 1 root root 5924752 10 avril 22:07 /boot/initrd.img-5.10.0-21-amd64-kg
                        ^^^^^^^
-rw-r--r-- 1 root root      83 21 janv. 09:35 /boot/System.map-5.10.0-21-amd64-kg
-rw-r--r-- 1 root root 7019136 21 janv. 09:35 /boot/vmlinuz-5.10.0-21-amd64-kg

> I install package so I have kernel and initram in /boot with the
> tag. Same as your system I think ?

You didn't make backup copies of your most recent kernel, *give them
funny names*, and keep them in /boot. That is the distinction here, I
think.

>  And when I update-initramfs it generate right files with right
> names. And never break anything on further updates.

That makes sense, of course.

> So why change only filenames and not rebuild a package with a
> different tag ?

I believe the OP just wants an extra entry in his grub menu that will
boot a redundant copy of his latest working kernel. (But that is only
my understanding, which might be wrong. OP can speak for himself on
this point.)

It seems to me that building and packaging like you suggest is more
work than warranted, just to make a backup copy. According to OP's
report, that simple practice used to work for him.

Myself, I was only curious to do

   Experiment #1: replicate the OP's observations

and

   Experiment #2: see if I could tweak OP's practice enough so that
     update-grub would not care.

-- 
Hackers are free people. They are like artists. If they are in a good
mood, they get up in the morning and begin painting their pictures.
-- Vladimir Putin

Back to linux.debian.user | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

update-initramfs Marc Auslander <marcslists@gmail.com> - 2023-04-11 02:30 +0200
  Re: update-initramfs David Wright <deblis@lionunicorn.co.uk> - 2023-04-11 05:00 +0200
    Re: update-initramfs Marc Auslander <marcslists@gmail.com> - 2023-04-11 17:10 +0200
      Re: update-initramfs davidson <davidson@freevolt.org> - 2023-04-11 19:40 +0200
        Re: update-initramfs Michel Verdier <mv524@free.fr> - 2023-04-11 21:00 +0200
          Re: update-initramfs davidson <davidson@freevolt.org> - 2023-04-11 21:50 +0200
            Re: update-initramfs davidson@freevolt.org - 2023-04-11 22:00 +0200
              Re: update-initramfs zithro <slack@rabbit.lu> - 2023-04-11 22:20 +0200
                Re: update-initramfs David Wright <deblis@lionunicorn.co.uk> - 2023-04-12 04:10 +0200
            Re: update-initramfs Michel Verdier <mv524@free.fr> - 2023-04-12 04:40 +0200
              Re: update-initramfs The Wanderer <wanderer@fastmail.fm> - 2023-04-12 13:40 +0200
                Re: update-initramfs Michel Verdier <mv524@free.fr> - 2023-04-12 13:50 +0200
                Re: update-initramfs The Wanderer <wanderer@fastmail.fm> - 2023-04-12 14:00 +0200
                Re: update-initramfs David Wright <deblis@lionunicorn.co.uk> - 2023-04-12 22:50 +0200
                Re: update-initramfs Michel Verdier <mv524@free.fr> - 2023-04-13 04:20 +0200
                Re: update-initramfs David Wright <deblis@lionunicorn.co.uk> - 2023-04-13 21:00 +0200
                Re: update-initramfs Charles Curley <charlescurley@charlescurley.com> - 2023-04-13 22:40 +0200
                Re: update-initramfs David Wright <david@lionunicorn.co.uk> - 2023-04-15 00:50 +0200
                Re: update-initramfs Michael Stone <mstone@debian.org> - 2023-04-13 22:50 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are  using the wrong driver David <curmudgeon@telaman.net.au> - 2023-04-14 23:40 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are  using the wrong driver Brian <ad44@cityscape.co.uk> - 2023-04-15 00:20 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are  using the wrong driver The Wanderer <wanderer@fastmail.fm> - 2023-04-15 00:30 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver Jeremy Ardley <jeremy@ardley.org> - 2023-04-15 00:40 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are  using the wrong driver Charles Curley <charlescurley@charlescurley.com> - 2023-04-15 01:00 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are  using the wrong driver Brian <ad44@cityscape.co.uk> - 2023-04-15 01:00 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are  using the wrong driver The Wanderer <wanderer@fastmail.fm> - 2023-04-15 01:10 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are  using the wrong driver Brian <ad44@cityscape.co.uk> - 2023-04-15 01:20 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are  using the wrong driver The Wanderer <wanderer@fastmail.fm> - 2023-04-15 01:30 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are  using the wrong driver Brian <ad44@cityscape.co.uk> - 2023-04-15 13:40 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver Jeremy Ardley <jeremy@ardley.org> - 2023-04-15 01:10 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver Brian <ad44@cityscape.co.uk> - 2023-04-15 01:20 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver Bret Busby <bret@busby.net> - 2023-04-15 01:50 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are  using the wrong driver David <curmudgeon@telaman.net.au> - 2023-04-15 01:50 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver "Andrew M.A. Cater" <amacater@einval.com> - 2023-04-15 12:10 +0200
                Pillow fight [was: EPSON ET M 1120 ...] <tomas@tuxteam.de> - 2023-04-15 12:20 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver "Thomas Schmitt" <scdbackup@gmx.net> - 2023-04-15 13:00 +0200
                On strange threads [was: EPSON ET M 1120 new printer...] <tomas@tuxteam.de> - 2023-04-15 15:40 +0200
                Re: On strange threads [was: EPSON ET M 1120 new printer...] Brian <ad44@cityscape.co.uk> - 2023-04-15 21:50 +0200
                Re: On strange threads [was: EPSON ET M 1120 new printer...] <tomas@tuxteam.de> - 2023-04-16 07:40 +0200
                Re: On strange threads [was: EPSON ET M 1120 new printer...] davidson <davidson@freevolt.org> - 2023-04-16 09:10 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver Brian <ad44@cityscape.co.uk> - 2023-04-15 13:50 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver Bret Busby <bret@busby.net> - 2023-04-15 22:00 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver Bret Busby <bret@busby.net> - 2023-04-15 22:30 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver Jeffrey Walton <noloader@gmail.com> - 2023-04-16 00:20 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver Bret Busby <bret@busby.net> - 2023-04-16 01:40 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are  using the wrong driver Curt <curty@free.fr> - 2023-04-22 16:30 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver chris <tknchris@gmail.com> - 2023-04-22 16:40 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are  using the wrong driver David <curmudgeon@telaman.net.au> - 2023-04-15 01:30 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are  using the wrong driver <tomas@tuxteam.de> - 2023-04-23 11:20 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are  using the wrong driver <tomas@tuxteam.de> - 2023-04-23 11:50 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are using the wrong driver Stefan Monnier <monnier@iro.umontreal.ca> - 2023-04-15 00:40 +0200
                Re: EPSON ET M 1120   new printer: If You can read this, you are  using the wrong driver Brian <ad44@cityscape.co.uk> - 2023-04-15 14:00 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver Jeffrey Walton <noloader@gmail.com> - 2023-04-29 13:50 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver Greg Wooledge <greg@wooledge.org> - 2023-05-01 13:40 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver Thomas Hochstein <thh@thh.name> - 2023-05-01 14:40 +0200
                Re: EPSON ET M 1120 new printer: If You can read this, you are using  the wrong driver gene heskett <gheskett@shentel.net> - 2023-05-01 15:30 +0200
        Re: update-initramfs davidson <davidson@freevolt.org> - 2023-04-12 13:00 +0200
          Re: update-initramfs davidson@freevolt.org - 2023-04-12 13:00 +0200
      Re: update-initramfs David Wright <deblis@lionunicorn.co.uk> - 2023-04-11 22:10 +0200
  Re: update-initramfs zithro <slack@rabbit.lu> - 2023-04-11 15:30 +0200
    Re: update-initramfs Marc Auslander <marcslists@gmail.com> - 2023-04-11 17:00 +0200
      Re: update-initramfs zithro <slack@rabbit.lu> - 2023-04-11 18:10 +0200

csiph-web