On Thu 13 Apr 2023 at 14:39:18 (-0600), Charles Curley wrote:
> On Thu, 13 Apr 2023 13:57:04 -0500
> David Wright wrote:
>
> > https://lists.debian.org/debian-user/2023/04/msg00405.html
> >
> > I was left with a system whose Grub menu only contained entries for
> > the new system, because os-pro
On Thu, Apr 13, 2023 at 01:57:04PM -0500, David Wright wrote:
os-prober no longer scours all the other
partitions for OSes any more.¹
Which is wonderful--that was one of the most annoying misfeatures to
have ever been enabled.
On Thu, 13 Apr 2023 13:57:04 -0500
David Wright wrote:
> https://lists.debian.org/debian-user/2023/04/msg00405.html
>
> I was left with a system whose Grub menu only contained entries for
> the new system, because os-prober no longer scours all the other
> partitions for OSes any more.¹ To get b
On Thu 13 Apr 2023 at 04:14:46 (+0200), Michel Verdier wrote:
> Le 12 avril 2023 David Wright a écrit :
>
> > the menu/ is moot. I would maintain that this failure mode is rare
> > enough for a reasonable penalty of having to type a few characters
> > editing the Grub menu.
> >
> > The last time I
Le 12 avril 2023 David Wright a écrit :
> the menu/ is moot. I would maintain that this failure mode is rare
> enough for a reasonable penalty of having to type a few characters
> editing the Grub menu.
>
> The last time I booted a kernel that was on a different partition
> from my installed Grub,
On Wed 12 Apr 2023 at 07:50:33 (-0400), The Wanderer wrote:
> On 2023-04-12 at 07:44, Michel Verdier wrote:
> > Le 12 avril 2023 The Wanderer a écrit :
> >
> >> Without anything more, wouldn't that just result in an extra
> >> GRUB-menu entry pointing to the same copy of the kernel/etc.?
> >
> >
On 2023-04-12 at 07:44, Michel Verdier wrote:
> Le 12 avril 2023 The Wanderer a écrit :
>
>> Without anything more, wouldn't that just result in an extra
>> GRUB-menu entry pointing to the same copy of the kernel/etc.?
>
> Of course he can change menuentry to point to another kernel/initram
Fro
Le 12 avril 2023 The Wanderer a écrit :
> Without anything more, wouldn't that just result in an extra GRUB-menu
> entry pointing to the same copy of the kernel/etc.?
Of course he can change menuentry to point to another kernel/initram
> As I think I understand matters, the goal is to have a dup
On 2023-04-11 at 22:30, Michel Verdier wrote:
> Le 11 avril 2023 davidson a écrit :
>> 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
>> hims
On Wed, 12 Apr 2023 davidson wrote:
On Tue, 11 Apr 2023 davidson wrote:
I haven't tried booting yet with my "5.10.0-21-amd63-kg" initrd,
though. I'll leave that to you, if you want to try.
Boot went fine, but it is worth mentioning that grub-update
*update-grub
decided that the "5.10.0-21-
On Tue, 11 Apr 2023 davidson wrote:
On Tue, 11 Apr 2023 Marc Auslander wrote:
On 4/10/2023 11:00 PM, David Wright wrote:
On Mon 10 Apr 2023 at 20:17:11 (-0400), Marc Auslander wrote:
I'm on Buster.
In /boot I keep a copy of the current working linux named by appending
-knowngood to the four f
Le 11 avril 2023 davidson a écrit :
> # 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
Of course : /lib/modules/ is installed via package. You
have to do it manually to get rid of this error. And without it you
On Tue 11 Apr 2023 at 22:14:18 (+0200), zithro wrote:
> I thought :
>
> - you can install as many kernel packages as you want, whether built
> or downloaded
> - updates don't automatically remove old kernels/initrd by default
>
> So I wonder, why handling it manually ?
> What is the advantage, ex
I thought :
- you can install as many kernel packages as you want, whether built or
downloaded
- updates don't automatically remove old kernels/initrd by default
So I wonder, why handling it manually ?
What is the advantage, except for adding -confusion- ?
On Tue 11 Apr 2023 at 10:51:19 (-0400), Marc Auslander wrote:
> On 4/10/2023 11:00 PM, David Wright wrote:
> > On Mon 10 Apr 2023 at 20:17:11 (-0400), Marc Auslander wrote:
> > > I'm on Buster.
> > >
> > > In /boot I keep a copy of the current working linux named by appending
> > > -knowngood to t
On Tue, 11 Apr 2023 davidson wrote:
On Tue, 11 Apr 2023 Michel Verdier wrote:
Le 11 avril 2023 davidson a écrit :
Experiment #2: see if I could tweak OP's practice enough so that
update-grub would not care.
...and so that "update-initramfs -u" would not notice.
--
Sometimes it pays to ha
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 cop
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,
On Tue, 11 Apr 2023 Marc Auslander wrote:
On 4/10/2023 11:00 PM, David Wright wrote:
On Mon 10 Apr 2023 at 20:17:11 (-0400), Marc Auslander wrote:
I'm on Buster.
In /boot I keep a copy of the current working linux named by appending
-knowngood to the four files. My idea is that if an update f
On 11 Apr 2023 16:43, Marc Auslander wrote:
On 4/11/2023 9:30 AM, zithro wrote:
The solution is in "man update-initramfs" :
update-initramfs -c -k $KERNEL_VERSION
-c creates a new initramfs
-k specifies the version of the kernel
This breaks when package update tries to update-initramfs. My cop
On 4/10/2023 11:00 PM, David Wright wrote:
On Mon 10 Apr 2023 at 20:17:11 (-0400), Marc Auslander wrote:
I'm on Buster.
In /boot I keep a copy of the current working linux named by appending
-knowngood to the four files. My idea is that if an update fails, I
have a recent working linux. This
On 4/11/2023 9:30 AM, zithro wrote:
On 11 Apr 2023 02:17, Marc Auslander wrote:
I'm on Buster.
In /boot I keep a copy of the current working linux named by appending
-knowngood to the four files. My idea is that if an update fails, I
have a recent working linux. This is different from vmlin
On 11 Apr 2023 02:17, Marc Auslander wrote:
I'm on Buster.
In /boot I keep a copy of the current working linux named by appending
-knowngood to the four files. My idea is that if an update fails, I
have a recent working linux. This is different from vmlinuz.old which
is the previous kernel
On Mon 10 Apr 2023 at 20:17:11 (-0400), Marc Auslander wrote:
> I'm on Buster.
>
> In /boot I keep a copy of the current working linux named by appending
> -knowngood to the four files. My idea is that if an update fails, I
> have a recent working linux. This is different from vmlinuz.old which
On Sat 01 Oct 2022 at 20:07:13 +0200, Erwan David wrote:
> Le 01/10/2022 à 18:25, Felix Miata a écrit :
> > Erwan David composed on 2022-10-01 16:21 (UTC+0200):
> >
> > > My /boot is 235 MB (from deb 10 installer), however in testing I now
> > > have 56MB initramfs files and update-initramfs cann
> Le 01/10/2022 à 18:25, Felix Miata a écrit :
> > Erwan David composed on 2022-10-01 16:21 (UTC+0200):
> >
> >> My /boot is 235 MB (from deb 10 installer), however in testing I
> >> now have 56MB initramfs files and update-initramfs cannot work for
> >> the 3rd kernel to install (and apt autorem
> I alreaady have compres=zstd (should be better than lzma).
I'd be surprised if `zstd` compresses better than `lzma` (which itself
should compress about the same as `xz`). I just tested here and I get
zstd => 11049378
xz => 9989884
lzma => 9965122
Maybe with more control over t
Le 01/10/2022 à 18:25, Felix Miata a écrit :
Erwan David composed on 2022-10-01 16:21 (UTC+0200):
My /boot is 235 MB (from deb 10 installer), however in testing I now
have 56MB initramfs files and update-initramfs cannot work for the 3rd
kernel to install (and apt autoremove keeps 2 kernels, th
Erwan David composed on 2022-10-01 16:21 (UTC+0200):
> My /boot is 235 MB (from deb 10 installer), however in testing I now
> have 56MB initramfs files and update-initramfs cannot work for the 3rd
> kernel to install (and apt autoremove keeps 2 kernels, thus at upgrade
> there are temporarily 3
On 2022-10-01 17:26 +0200, Erwan David wrote:
> Le 01/10/2022 à 17:16, Stefan Monnier a écrit :
>>> My /boot is 235 MB (from deb 10 installer), however in testing I now have
>>> 56MB initramfs files and update-initramfs cannot work for the 3rd kernel to
>>> install (and apt autoremove keeps 2 kern
Le 01/10/2022 à 17:16, Stefan Monnier a écrit :
My /boot is 235 MB (from deb 10 installer), however in testing I now have
56MB initramfs files and update-initramfs cannot work for the 3rd kernel to
install (and apt autoremove keeps 2 kernels, thus at upgrade there are
temporarily 3 kernels).
> My /boot is 235 MB (from deb 10 installer), however in testing I now have
> 56MB initramfs files and update-initramfs cannot work for the 3rd kernel to
> install (and apt autoremove keeps 2 kernels, thus at upgrade there are
> temporarily 3 kernels).
MODULES=dep
and
COMPRESS=lzma
in `
On Wed, May 23, 2012 at 9:35 AM, David Baron wrote:
> On Tuesday 22 May 2012 18:32:55 David Baron wrote:
>> On Tuesday 22 May 2012 16:59:30 Pascal Hambourg wrote:
>> > David Baron a écrit :
>> > > On Tuesday 22 May 2012 02:10:06 Pascal Hambourg wrote:
>> > >> You can add the missing required modul
On Tuesday 22 May 2012 18:32:55 David Baron wrote:
> On Tuesday 22 May 2012 16:59:30 Pascal Hambourg wrote:
> > David Baron a écrit :
> > > On Tuesday 22 May 2012 02:10:06 Pascal Hambourg wrote:
> > >> You can add the missing required modules in
> > >> /etc/initramfs-tools/modules and rebuild the i
David Baron a écrit :
> On Tuesday 22 May 2012 16:59:30 Pascal Hambourg wrote:
>> You have to guess which modules are needed to mount the final root
>> filesystem, e.g. by looking at the bottom of the output of lsmod after
>> booting with a "full" initramfs.
>
> ext3 would be obvious
> jbd ? (dep
On Tuesday 22 May 2012 16:59:30 Pascal Hambourg wrote:
> David Baron a écrit :
> > On Tuesday 22 May 2012 02:10:06 Pascal Hambourg wrote:
> >> You can add the missing required modules in /etc/initramfs-tools/modules
> >> and rebuild the initramfs.
> >
> > However, with latest initramfs-tools, I do
David Baron a écrit :
> On Tuesday 22 May 2012 02:10:06 Pascal Hambourg wrote:
>>
>> You can add the missing required modules in /etc/initramfs-tools/modules
>> and rebuild the initramfs.
>
> However, with latest initramfs-tools, I do not get a list of missing
> modules,
You have to guess which mo
On Tuesday 22 May 2012 02:10:06 Pascal Hambourg wrote:
> Hello,
>
> David Baron a écrit :
> > Up until recent upgrades, it worked fine with "dep" producing initrd of
> > 3.7 meg. After recent upgrades, this no longer worked. Various errors
> > about rootfs or /root is a folder. The boot would fail
Hello,
David Baron a écrit :
> Up until recent upgrades, it worked fine with "dep" producing initrd of 3.7
> meg. After recent upgrades, this no longer worked. Various errors about
> rootfs
> or /root is a folder. The boot would fail at the tso point. Now have to use
> "most" and get 11 meg in
Hi again --
Does anyone have any post-thanksgiving suggestions for how to handle this
issue?
Thanks in advance,
-PT
On Tue, Nov 23, 2010 at 8:56 AM, Peter Tenenbaum <
peter.g.tenenb...@gmail.com> wrote:
> In my recent experiments with moving my home Debian desktop to RAID-1
> arrays, I discover
On Tue, Mar 06, 2007 at 04:48:19AM -0600, Hugo Vanwoerkom wrote:
> Chris Bannister wrote:
> >On Sun, Mar 04, 2007 at 02:19:54PM -0600, Hugo Vanwoerkom wrote:
[..]
> >>But how does he know that initrd.img-2.6.18-4-486 is the 'newest kernel'
> >>as the man-page has it?
> >
> >-uThis mode updates
Chris Bannister wrote:
On Sun, Mar 04, 2007 at 02:19:54PM -0600, Hugo Vanwoerkom wrote:
Hi,
I run this:
~Sun Mar 04-13:57:19SDA6# update-initramfs -u
and I get:
/boot/initrd.img-2.6.18-4-486 does not exist. Cannot update.
That happens to be true. (Surprise!)
But how does he know that initr
On Sun, Mar 04, 2007 at 02:19:54PM -0600, Hugo Vanwoerkom wrote:
> Hi,
>
> I run this:
>
> ~Sun Mar 04-13:57:19SDA6# update-initramfs -u
>
> and I get:
>
> /boot/initrd.img-2.6.18-4-486 does not exist. Cannot update.
>
> That happens to be true. (Surprise!)
>
> But how does he know that initr
On Sun, Mar 04, 2007 at 04:29:24PM -0600, Hugo Vanwoerkom wrote:
> Hugo Vanwoerkom wrote:
> >Hi,
> >
> >I run this:
> >
> >~Sun Mar 04-13:57:19SDA6# update-initramfs -u
> >
> >and I get:
> >
> >/boot/initrd.img-2.6.18-4-486 does not exist. Cannot update.
> >
> >That happens to be true. (Surprise!)
Hugo Vanwoerkom wrote:
Hi,
I run this:
~Sun Mar 04-13:57:19SDA6# update-initramfs -u
and I get:
/boot/initrd.img-2.6.18-4-486 does not exist. Cannot update.
That happens to be true. (Surprise!)
But how does he know that initrd.img-2.6.18-4-486 is the 'newest kernel'
as the man-page has it?
45 matches
Mail list logo
