On 29/10/11 19.47, co wrote:
> After I run e2fsck -c on /var partition.I have re-emerged pam. So I
> think there is something wrong with my hard disc.
Why do you think that? Did badblocks identify any specific problems?
A failing hard disk generally shows very obvious symptoms (noises,
periodic
On Saturday 29 Oct 2011 18:47:58 co wrote:
> After I run e2fsck -c on /var partition.I have re-emerged pam. So I think
> there is something wrong with my hard disc.
This looks like a fs corruption. It may be a disk problem, or a memory
problem.
To check for the former you better install smartm
After I run e2fsck -c on /var partition.I have re-emerged pam. So I think
there is something wrong with my hard disc. And there is still something
Error and Warning on boot time,and after startx mouse can't move. So how to
fix the hard disc now? Forgive my poor EnglishThank you again
2011/
My system is amd64,and livecd is amd64 too. I always chroot.And it's exf4.
Wait a second,I will try it now.Thank you so much.
2011/10/30 Andrea Conti
> On 29/10/11 13.10, co wrote:
>
> >> # ls -l /lib/libpam.so*
>
> > lrwxrwxrwx 1 root root11 Oct 21 23:47 /lib32/libpam.so -> libpam.so.0
On 29/10/11 13.10, co wrote:
>> # ls -l /lib/libpam.so*
> lrwxrwxrwx 1 root root11 Oct 21 23:47 /lib32/libpam.so -> libpam.so.0
> lrwxrwxrwx 1 root root16 Oct 21 23:48 /lib32/libpam.so.0 ->
> libpam.so.0.83.0
> -rwxr-xr-x 1 root root 46520 Sep 28 19:37 /lib32/libpam.so.0.83.0
That's
emerge --info
Traceback (most recent call last):
File "/usr/bin/emerge", line 43, in
retval = emerge_main()
File "/usr/lib64/portage/pym/_emerge/main.py", line 1879, in emerge_main
return action_info(settings, trees, myopts, valid_atoms)
File "/usr/lib64/portage/pym/_emerge/actions.p
These are the packages that would be merged, in order:
Calculating dependencies done!
[ebuild R] sys-libs/pam-1.1.5 USE="berkdb cracklib nls vim-syntax
-audit -debug -nis (-selinux) -test" 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB
>>> Verifying ebuild manifests
#ldd /sbin/rc
linux-vdso.so.1 => (0x7fff69fff000)
libutil.so.1 => /lib64/libutil.so.1 (0x7f617f00d000)
librc.so.1 => /lib64/librc.so.1 (0x7f617ee01000)
libeinfo.so.1 => /lib64/libeinfo.so.1 (0x7f617ebfb000)
libdl.so.2 => /lib64/libdl.so.2 (0x7f617e9f7000)
libpam.so.0 => not f
> And i try to re-emerge pam,but i can't
With the old file and links there I don't understand why your system
doesn't work, but re-emerging pam it definitely worth trying. What
fails when you try to re-emerge?
Also, what about
# ldd /sbin/rc
And when i revdep-rebuild ,it still warning libpam.so.0,when finished ,it
still can't work.
And i try to re-emerge pam,but i can't
2011/10/29 co
> lrwxrwxrwx 1 root root11 Oct 21 23:47 /lib32/libpam.so -> libpam.so.0
> lrwxrwxrwx 1 root root16 Oct 21 23:48 /lib32/libpam.so.0 ->
> libpam.
lrwxrwxrwx 1 root root11 Oct 21 23:47 /lib32/libpam.so -> libpam.so.0
lrwxrwxrwx 1 root root16 Oct 21 23:48 /lib32/libpam.so.0 ->
libpam.so.0.83.0
-rwxr-xr-x 1 root root 46520 Sep 28 19:37 /lib32/libpam.so.0.83.0
2011/10/29 Adam Carter
> On Sat, Oct 29, 2011 at 8:55 PM, co wrote:
> > I
On Sat, Oct 29, 2011 at 8:55 PM, co wrote:
> I upgrade pad to 1.1.5 ,then openrc can't work,and can't login to system.
> libpam.so.0 can't open shared object file.
> please help!
I always run revdep-rebuild any time libs are updated, but in this
case the lib name stays the same.
What do you see
I upgrade pad to 1.1.5 ,then openrc can't work,and can't login to system.
libpam.so.0 can't open shared object file.
please help!
13 matches
Mail list logo