All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aruna Hewapathirane <aruna.hewapathirane@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Dhaval Giani <dhaval.giani@gmail.com>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Kernel Compile Issue
Date: Thu, 24 Jun 2021 19:36:08 -0400	[thread overview]
Message-ID: <CAFSeFg_iNku=f8G_uEo5Rk=6GO03+gZ-qMz8QbJoJkFZ_tvSCw@mail.gmail.com> (raw)
In-Reply-To: <31879.1624576151@turing-police>

On Thu, Jun 24, 2021 at 7:09 PM Valdis Klētnieks
<valdis.kletnieks@vt.edu> wrote:
>
> On Thu, 24 Jun 2021 14:19:04 -0400, Aruna Hewapathirane said:
>
> > Could well be ... but 'locate' shows me this:
> >
> > aruna@debian:~$ locate Makefile.normal
> > /usr/src/open-vm-tools-9.4.6/vmci/Makefile.normal
> > /var/lib/dkms/open-vm-tools/9.4.6/build/vmci/Makefile.normal
>
> Note that 'locate' doesn't actually walk through the file system, it greps
> through a file created by 'updatedb' which usually gets run from a crontab
> entry.  As a result, 'locate' can report the existence of files that have actually
> been removed after the last updatedb run.

Oh dear... no wonder locate was lightning fast and I was thinking even
for linux this
is crazy fast speed. Now I know...  Thank you Valdis and any thoughts
on how I can
get my mouse to work at the graphical login screen again ?

make j$(nproc) is ok
make modules_install is ok
make install is ok

but after selecting the new kernel at the GRUB2 menu it hangs at the graphical
login and I am stumped.

Soo... that is why 'locate' is so damn fast :-)

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2021-06-24 23:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23  2:48 Kernel Compile Issue Aruna Hewapathirane
2021-06-24 10:21 ` Thomas Bracht Laumann Jespersen
2021-06-24 13:35   ` Aruna Hewapathirane
2021-06-24 16:13     ` Cindy Sue Causey
2021-06-24 17:56       ` Aruna Hewapathirane
2021-06-24 17:29     ` Thomas Bracht Laumann Jespersen
2021-06-24 18:19       ` Aruna Hewapathirane
2021-06-24 23:09         ` Valdis Klētnieks
2021-06-24 23:36           ` Aruna Hewapathirane [this message]
2021-06-25  0:51             ` Valdis Klētnieks
2021-06-25 20:05               ` Aruna Hewapathirane
2021-06-26  6:39                 ` Valdis Klētnieks
2021-06-28 11:58                   ` Aruna Hewapathirane
2021-06-29  9:25                     ` Thomas Bracht Laumann Jespersen

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='CAFSeFg_iNku=f8G_uEo5Rk=6GO03+gZ-qMz8QbJoJkFZ_tvSCw@mail.gmail.com' \
    --to=aruna.hewapathirane@gmail.com \
    --cc=dhaval.giani@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=valdis.kletnieks@vt.edu \
    /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.