> Sorry for that. I know it's a sleazy way of learning -- spewing out some
> nonsense, being corrected and caching that for the next time.
You're describing the scientific method,
Stefan
On 2020-11-24, Greg Wooledge wrote:
> On Tue, Nov 24, 2020 at 10:09:51AM +0100, to...@tuxteam.de wrote:
>> Sorry for that. I know it's a sleazy way of learning -- spewing out some
>> nonsense, being corrected and caching that for the next time.
>
> It's only sleazy if you do it on purpose.
If
On Tue, Nov 24, 2020 at 10:09:51AM +0100, to...@tuxteam.de wrote:
> Sorry for that. I know it's a sleazy way of learning -- spewing out some
> nonsense, being corrected and caching that for the next time.
It's only sleazy if you do it on purpose.
On Mon, Nov 23, 2020 at 06:30:46PM -0500, Stefan Monnier wrote:
> > Use unmkinitramfs. It appears you've only looked at the first archive,
> > the early one, which gets the kernel into shape. The second, main one
> > is the big one.
>
> OK, for those interested I tracked it down: indeed the
> Use unmkinitramfs. It appears you've only looked at the first archive,
> the early one, which gets the kernel into shape. The second, main one
> is the big one.
OK, for those interested I tracked it down: indeed the machine with the
larger initrd had MODULES=most instead of MODULES=dep.
It
Curt composed on 2020-11-23 12:39 (UTC):
> tomas wrote:
>> The initramfs is a compressed cpio archive (of the initial file
>> system at boot time). You can inspect it like so:
>> gunzip < /boot/initrd.img-4.19.0-10-amd64 | cpio -it | less
> lsinitramfs /boot/initrd.img-4.19.0-10-amd64
On Mon, Nov 23, 2020 at 08:15:47AM -0500, Greg Wooledge wrote:
> On Sat, Nov 21, 2020 at 10:03:06PM +0100, to...@tuxteam.de wrote:
> > The initramfs is a compressed cpio archive (of the initial file
> > system at boot time). You can inspect it like so:
> >
> > gunzip <
On 2020-11-23, Curt wrote:
> On 2020-11-21, wrote:
>>
>> The initramfs is a compressed cpio archive (of the initial file
>> system at boot time). You can inspect it like so:
>>
>> gunzip < /boot/initrd.img-4.19.0-10-amd64 | cpio -it | less
>
> lsinitramfs /boot/initrd.img-4.19.0-10-amd64
On Sat, Nov 21, 2020 at 10:03:06PM +0100, to...@tuxteam.de wrote:
> The initramfs is a compressed cpio archive (of the initial file
> system at boot time). You can inspect it like so:
>
> gunzip < /boot/initrd.img-4.19.0-10-amd64 | cpio -it | less
Debian's initrd images are actually multiple
On 2020-11-21, wrote:
>
> The initramfs is a compressed cpio archive (of the initial file
> system at boot time). You can inspect it like so:
>
> gunzip < /boot/initrd.img-4.19.0-10-amd64 | cpio -it | less
lsinitramfs /boot/initrd.img-4.19.0-10-amd64
On Mon, Nov 23, 2020 at 01:36:05AM -0500, Felix Miata wrote:
> Tomas composed on 2020-11-21 22:46 (UTC+0100):
>
> > You can inspect it like so:
>
> > gunzip < /boot/initrd.img-4.19.0-10-amd64 | cpio -it | less
>
> That was shortened to 'lsinitrd | less' in 2008 in openSUSE[1],
> which
>
Tomas composed on 2020-11-21 22:46 (UTC+0100):
> You can inspect it like so:
> gunzip < /boot/initrd.img-4.19.0-10-amd64 | cpio -it | less
That was shortened to 'lsinitrd | less' in 2008 in openSUSE[1],
which
Mandriva already had, eventually upstream'd to dracut, I'm guessing well over 5
On Sun 22 Nov 2020 at 23:46:54 (-0500), Stefan Monnier wrote:
> >> I have two machines with very similar setups: both running Debian i386
> >> testing, they actually come from the same install done years ago
> >> and were cloned at some point in time.
> >>
> >> One of the has /boot/initrd.img
>> I have two machines with very similar setups: both running Debian i386
>> testing, they actually come from the same install done years ago
>> and were cloned at some point in time.
>>
>> One of the has /boot/initrd.img files that take about 15MB while the
>> other has /boot/initrd.img files
On Sat 21 Nov 2020 at 21:47:02 (+), Andy Smith wrote:
>
> On Sat, Nov 21, 2020 at 02:52:49PM -0500, Stefan Monnier wrote:
> > One of the has /boot/initrd.img files that take about 15MB while the
> > other has /boot/initrd.img files that take about 30MB (in both cases,
> > they are compressed
Hi Stefan,
On Sat, Nov 21, 2020 at 02:52:49PM -0500, Stefan Monnier wrote:
> One of the has /boot/initrd.img files that take about 15MB while the
> other has /boot/initrd.img files that take about 30MB (in both cases,
> they are compressed with `lzma`).
>
> Any idea what this difference could
On Sat 21 Nov 2020 at 14:52:49 (-0500), Stefan Monnier wrote:
> I have two machines with very similar setups: both running Debian i386
> testing, they actually come from the same install done years ago
> and were cloned at some point in time.
>
> One of the has /boot/initrd.img files that take
On Sat, Nov 21, 2020 at 02:52:49PM -0500, Stefan Monnier wrote:
> I have two machines with very similar setups: both running Debian i386
> testing, they actually come from the same install done years ago
> and were cloned at some point in time.
>
> One of the has /boot/initrd.img files that take
I have two machines with very similar setups: both running Debian i386
testing, they actually come from the same install done years ago
and were cloned at some point in time.
One of the has /boot/initrd.img files that take about 15MB while the
other has /boot/initrd.img files that take about 30MB
19 matches
Mail list logo
