All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Gilbert Adikankwu <gilbertadikankwu@gmail.com>
Cc: Andi Shyti <andi.shyti@linux.intel.com>,
	Julia Lawall <julia.lawall@inria.fr>,
	"andi.shyti@kernel.org" <andi.shyti@kernel.org>,
	"outreachy@lists.linux.dev" <outreachy@lists.linux.dev>
Subject: Re: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS
Date: Tue, 10 Oct 2023 19:03:18 +0200	[thread overview]
Message-ID: <ZSWD1rtmLLWS++RH@ashyti-mobl2.lan> (raw)
In-Reply-To: <CAKrXSsZSb35yvwvMm_sa9+Xk6V01ZA_2LSzd9Lbufjsifr7kKw@mail.gmail.com>

Hi Gilbert,

first of all... good to see that your good e-mail style :-)

> > > > I have another issue, I tried compiling after modifying and it compiled
> > > > successfully. But when I tried to install so I can reboot, I got this
> > > > error:
> > > >
> > > > zstd: error 25 : Write error : No space left on device (cannot write
> > > > compressed block)
> > > > E: mkinitramfs failure zstd -q -1 -T0 25
> > > > update-initramfs: failed for /boot/initrd.img-6.6.0-rc1gilbert+ with 1.
> > > > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
> > > > make[2]: *** [arch/x86/Makefile:292: install] Error 1
> > > > make[1]: *** [/home/functionguyy/git/kernels/staging/Makefile:359:
> > > > __build_one_by_one] Error 2
> > > > make: *** [Makefile:234: __sub-make] Error 2
> > >
> > > You have too little space in the partition that contains /boot?
> >
> > What does "df -h" say?
> >
> > Andi
> 
> This is what df -h returned:
> 
> Filesystem      Size  Used Avail Use% Mounted on
> tmpfs           784M  2.0M  782M   1% /run
> /dev/sda9        23G   17G  5.6G  75% /
> tmpfs           3.9G   45M  3.8G   2% /dev/shm
> tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> /dev/sda7       944M  761M  119M  87% /boot

I wonder why your boot directory is so packed, even though 119M
should be enough.

You could try to reove some older kernels.

> /dev/sda11       60G   28G   30G  49% /home

BTW, are you working in your home directory?

Andi

> /dev/sda2        96M   32M   65M  33% /boot/efi
> tmpfs           784M  120K  784M   1% /run/user/1000

  reply	other threads:[~2023-10-10 17:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10  4:20 [Outreachy Applicant] NEEDS SOME CLARIFICATIONS Gilbert Adikankwu
2023-10-10  6:20 ` Deepak R Varma
2023-10-10  7:15 ` Andi Shyti
     [not found]   ` <CAKrXSsZe4w-K7kzGu=8_R_h1TSVtJWL1_TmFX-S-A1jCrPeCrg@mail.gmail.com>
2023-10-10 16:36     ` Julia Lawall
2023-10-10 16:42       ` Gilbert Adikankwu
2023-10-10 16:43       ` Andi Shyti
2023-10-10 16:45         ` Gilbert Adikankwu
2023-10-10 17:03           ` Andi Shyti [this message]
2023-10-10 17:34             ` Gilbert Adikankwu
2023-10-10 20:54               ` Andi Shyti
2023-10-11  6:15                 ` Gilbert Adikankwu
2023-10-11  6:26                   ` Julia Lawall
2023-10-11  6:37                     ` Gilbert Adikankwu
2023-10-11  7:10                     ` Andi Shyti
2023-10-13  7:59                       ` Gilbert Adikankwu
2023-10-13  8:17                         ` Julia Lawall
  -- strict thread matches above, loose matches on Subject: below --
2023-10-10  6:59 Gilbert Adikankwu
2023-10-10  7:06 Gilbert Adikankwu

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=ZSWD1rtmLLWS++RH@ashyti-mobl2.lan \
    --to=andi.shyti@linux.intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=gilbertadikankwu@gmail.com \
    --cc=julia.lawall@inria.fr \
    --cc=outreachy@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.