Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 03-08-2007, 04:14 PM   #1
LQ Guru
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
:( Unable to map <insert crap here> :Operation not permitted.

This is a low priority post, just incase anyone happens to have a possible answer as to what happened.

Everything was perfectly fine, until I restarted X.
Then there were no device icons on my desktop.. I figured it was a glitch of some sort, so I logged out and back in, to no avail.
I rebooted, and saw these errors, about 4 of them, during boot:

Something like for example:

Error: Shared library Unable to map shared resources <or something...> : Operation not permitted.

I couldn't run MC, or start X, or do very much of anything, because almost everything I entered into the command line returned a variation of the same message, referring to different files.
I rebooted from the CD and reinstalled some stuff, including system libraries. Same thing after reboot.
I rebooted the CD again and installed the entire system again. Same thing, no fix.
Finally I formatted the partition and reinstalled the whole ****da**ed thing from scratch, and here I am,finally, with a WHOLE LOT of reconfiguring to do to get my beloved system back to some semblance of how I had it.
YES, I have backups of MOST relevant stuff, my config files, personal files, rc.scripts, etc, and all the packages and other .tgz's that I've installed since the beginnning, so it isn't even near a total loss---no bookmarks, dented pride, and for now an ugly desktop---and a severe pain in the a$$..
I'm just wondering if anyone has an idea what **may** have led to this unexplained umm...screwup?
I literally was not doing *anything* at the time, and was logged in as me (user)
Old 03-08-2007, 06:05 PM   #2
Registered: Mar 2006
Posts: 381

Rep: Reputation: 30
just a wild guess: your kernel (or something else really low-level: glibc, bintools,etc..)
Old 03-08-2007, 07:39 PM   #3
Senior Member
Registered: May 2006
Distribution: Caldera, CTOS, Debian, FreeBSD, Mac OS X, Mandrake, Minix, OpenBSD, Slackware, SuSE
Posts: 1,757

Rep: Reputation: 80
Sounds like the shared library cache/PATH/config got corrupted. The cache is rebuilt on every boot:

# Update all the shared library links:
if [ -x /sbin/ldconfig ]; then
  echo "Updating shared library links:  /sbin/ldconfig"

I wouldn't think that restarting the X server with user priviledges would cause corruption to the system shared library settings. If you didn't add/change any software to the system before you restarted the X server, then you might have a hardware problem, possibly memory or hard drive bad spot(s)? Might have been helpful if you were able to view the system log files prior to reinstall.
Old 03-08-2007, 07:59 PM   #4
LQ Guru
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1287Reputation: 1287Reputation: 1287Reputation: 1287Reputation: 1287Reputation: 1287Reputation: 1287Reputation: 1287Reputation: 1287
It sounds like some type of filesystem corruption. I mean after you remade and re-formatted the partitions, the problem went away.
Old 03-09-2007, 07:55 PM   #5
LQ Guru
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Original Poster
Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Hmmm.. Thanks for the input guys I'm still curious too, but.. Well, I just can't say for sure.
I looked thru the logs as best I could with no facilities (mostly tail ends and cat's) and nothing stood out.

That stuff about the LD cache sounds reasonable and appropriate, and yes to all that it did indeed seem like some sort of curruption, but I can't pin down a cause.
The hard drive in question is a brand new Seagate, so for the time being I trust it. If it *is* kernel related, then it would be the first significant or obvious glitch from this kernel (2.6.20) that I have noticed. Anything is possible though.
Well, thanks again, it's a curiousity for the time being, but I'm gonna change my backup strategy ASAP, and archive my entire installation every day to the other HD and maybe to another partition on this drive too, in a 7 or 10 day rotation using cron.
Reinstalling stuff is no big deal, and I didn't lose anything other than bookmarks and personal settings, but that's the annoying part all the little fine tuning that makes everything *just* how I like it..
Anyhow take care everyone -- and BACKUP!


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
ping operation not permitted Ammad Linux - Networking 3 04-05-2006 08:23 AM
Operation not permitted jakkals Linux - General 3 09-26-2005 07:30 PM
su - operation not permitted jrtayloriv Linux - Newbie 2 06-09-2005 09:27 PM
operation not permitted jamaso Slackware 2 05-08-2004 05:55 AM
Operation not permitted FrozenShadow23 Linux - Newbie 6 10-05-2003 05:13 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:47 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration