From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: difference between /usr/lib/modules and /lib/modules
Date: Sat, 21 Mar 2020 23:36:45 -0400 [thread overview]
Message-ID: <13356.1584848205@turing-police> (raw)
In-Reply-To: <20200320111152.GN19325@valentin-vidic.from.hr>
[-- Attachment #1.1: Type: text/plain, Size: 788 bytes --]
On Fri, 20 Mar 2020 12:11:52 +0100, Valentin VidiD <vvidic@valentin-vidic.from.hr> said:
> On Fri, Mar 20, 2020 at 10:56:15AM +0000, Bernd Petrovitsch wrote:
> > Are you sure they are actually different (and don't have e.g.
> > the same inode number)?
>
> Looks like that to me (on Debian):
>
> $ ls -lid /usr/lib/modules /lib/modules
> 9804 drwxr-xr-x 4 root root 4096 Feb 15 11:31 /lib/modules
> 9804 drwxr-xr-x 4 root root 4096 Feb 15 11:31 /usr/lib/modules
>
> $ ls -lid /usr/lib /lib
> 29 lrwxrwxrwx 1 root root 7 Jul 27 2019 /lib -> usr/lib
> 30 drwxr-xr-x 79 root root 4096 Feb 15 11:27 /usr/lib
So /lib is a symlink to /usr/lib. Fairly common on many distros.
(Try 'ls -Lid' instead - the -L option makes it show the target of a symlink
rather than the symlink itself...)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-03-22 3:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 10:24 difference between /usr/lib/modules and /lib/modules Fabien R
2020-03-20 10:56 ` Bernd Petrovitsch
2020-03-20 11:11 ` Valentin Vidić
2020-03-20 11:23 ` Fabien R
2020-03-22 3:36 ` Valdis Klētnieks [this message]
2020-03-20 11:14 ` Fabien R
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=13356.1584848205@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).