* libselinux.so: cannot open shared object file
@ 2003-09-04 0:59 max barwell
2003-09-04 4:53 ` Russell Coker
2003-09-04 15:41 ` Colin Walters
0 siblings, 2 replies; 5+ messages in thread
From: max barwell @ 2003-09-04 0:59 UTC (permalink / raw)
To: SELinux
I am using debian sid, I compiled a 2.6.0-test4 kernel ready for use,
and downloaded Colin Walters SElinux packages, during their install, and
I'm not sure when as I wasn't watching, the install borked, and now when
I try to do anything ie type ls, I get the error message
error while loading shared libraries: libselinux.so: cannot open shared
object file: No such file or directory
what happened? can I fix this? anyone encountered this before?
would love to get this sorted.
regards Max
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: libselinux.so: cannot open shared object file
2003-09-04 0:59 libselinux.so: cannot open shared object file max barwell
@ 2003-09-04 4:53 ` Russell Coker
2003-09-04 15:41 ` Colin Walters
1 sibling, 0 replies; 5+ messages in thread
From: Russell Coker @ 2003-09-04 4:53 UTC (permalink / raw)
To: max barwell, SELinux
On Thu, 4 Sep 2003 10:59, max barwell wrote:
> I am using debian sid, I compiled a 2.6.0-test4 kernel ready for use,
> and downloaded Colin Walters SElinux packages, during their install, and
> I'm not sure when as I wasn't watching, the install borked, and now when
> I try to do anything ie type ls, I get the error message
>
> error while loading shared libraries: libselinux.so: cannot open shared
> object file: No such file or directory
>
> what happened? can I fix this? anyone encountered this before?
It sounds like one of two things happened:
1) The dependencies were not correct and you managed to install a coreutils
package without the library package it should depend on.
2) You are running SE Linux in enforcing mode and libselinux.so got the wrong
type (can occur when an apt installation aborts).
For 1 you have to install the necessary package.
For 2 you have to relabel the file in question with a command like the
following:
find /lib /usr/lib | setfiles -s -v /etc/selinux/file_contexts/file_contexts
Anyway your system is not as broken as you think. If you have busybox-static
installed (or can install it) then it will work fine.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: libselinux.so: cannot open shared object file
2003-09-04 0:59 libselinux.so: cannot open shared object file max barwell
2003-09-04 4:53 ` Russell Coker
@ 2003-09-04 15:41 ` Colin Walters
2003-09-04 21:00 ` Diyab
1 sibling, 1 reply; 5+ messages in thread
From: Colin Walters @ 2003-09-04 15:41 UTC (permalink / raw)
To: max barwell; +Cc: SELinux
On Wed, 2003-09-03 at 20:59, max barwell wrote:
> I am using debian sid, I compiled a 2.6.0-test4 kernel ready for use,
> and downloaded Colin Walters SElinux packages, during their install, and
> I'm not sure when as I wasn't watching, the install borked, and now when
> I try to do anything ie type ls, I get the error message
>
> error while loading shared libraries: libselinux.so: cannot open shared
> object file: No such file or directory
Hm, for some reason the binaries are getting linked against
libselinux.so instead of libselinux.so.1. I'll investigate this. In
the meantime it should be sufficient to install libselinux1-dev.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: libselinux.so: cannot open shared object file
2003-09-04 15:41 ` Colin Walters
@ 2003-09-04 21:00 ` Diyab
2003-09-05 0:32 ` Brian May
0 siblings, 1 reply; 5+ messages in thread
From: Diyab @ 2003-09-04 21:00 UTC (permalink / raw)
To: Colin Walters; +Cc: max barwell, SELinux
Colin Walters wrote:
> On Wed, 2003-09-03 at 20:59, max barwell wrote:
>
>>I am using debian sid, I compiled a 2.6.0-test4 kernel ready for use,
>>and downloaded Colin Walters SElinux packages, during their install, and
>>I'm not sure when as I wasn't watching, the install borked, and now when
>>I try to do anything ie type ls, I get the error message
>>
>>error while loading shared libraries: libselinux.so: cannot open shared
>>object file: No such file or directory
>
>
> Hm, for some reason the binaries are getting linked against
> libselinux.so instead of libselinux.so.1. I'll investigate this. In
> the meantime it should be sufficient to install libselinux1-dev.
>
>
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
> the words "unsubscribe selinux" without quotes as the message.
>
> .
>
Why not just link libselinux.so to libselinux.so.1 ? That would at
least temporarily fix the problem would it not?
Timothy,
--
I put instant coffee in a microwave and almost went back in time.
-- Steven Wright
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: libselinux.so: cannot open shared object file
2003-09-04 21:00 ` Diyab
@ 2003-09-05 0:32 ` Brian May
0 siblings, 0 replies; 5+ messages in thread
From: Brian May @ 2003-09-05 0:32 UTC (permalink / raw)
To: Diyab; +Cc: Colin Walters, max barwell, SELinux
On Thu, Sep 04, 2003 at 05:00:42PM -0400, Diyab wrote:
> >Hm, for some reason the binaries are getting linked against
> >libselinux.so instead of libselinux.so.1. I'll investigate this. In
> >the meantime it should be sufficient to install libselinux1-dev.
>
> Why not just link libselinux.so to libselinux.so.1 ? That would at
> least temporarily fix the problem would it not?
I would assume that this is what the libselinux1-dev package does?
(otherwise that might be the problem).
I haven't seen the packages in question, but what normally happens
(assuming this hasn't changed, I don't think it has):
libselinux.so ---> libselinux.so.1 (symlink, for development)
libselinux.so.1 (shared library).
You link against libselinux.so; The linker realizes that this points
to libselinux.so.1, and encodes libselinux.so.1 into the resultant
executable (and not libselinux.so).
So you can run the programs with only libselinux.so.1 present, and
libselinux.so is only needed for initial linking.
What is the output of "ldd filename"?
--
Brian May <bam@snoopy.apana.org.au>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-09-05 0:32 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-09-04 0:59 libselinux.so: cannot open shared object file max barwell
2003-09-04 4:53 ` Russell Coker
2003-09-04 15:41 ` Colin Walters
2003-09-04 21:00 ` Diyab
2003-09-05 0:32 ` Brian May
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.