Permission Denied
 

How can I get a "Permission Denied" in KDE if I am logged in as root? It won't let me mount or access my Linux drive. Oddly enough it will let me access my NTFS (C) drive.

Thanks
Ace

I don't understand your question. If you're logged into KDE, your Linux drive is already mounted. For your own protection, some parts of the drive are only accessible to the system... depends on what you're trying to do.

I know its weird. If I click on storage, it shows the drive as not being mounted. If I click it to access it, or right click to mount it. I get Permission denied. However, I can type the address directly in the address bar and then use the up button or click directly the folder i want. So it's not that I can't get to the information, it's just frustrating that I can't just initially click it. Also while I can't remember off the top of my head, I have had issues before where a software package or program configuration reconizes the drive as not being mounted.

If I try to mount from the prompt I get, "Already Mounted"

Lastly , while I have the ear of an old schooler. Does Linux have an autoexec.bat equivilant? I keep having to type modprobe ndiswrapper and dhcpcd wlan0 every start up to get my networking to work.

Thanks Again
Ace

I noticed that you're running two distros- Mint and Slackware. Are you trying to access one distro's files from the other distro? If not, then I'm clueless as to why the drive would be listed as "Not Mounted".

As for your second question, I'm not sure about Slack or Mint, but in Ubuntu, you simply open Sessions and add the package(s) to Startup. But no, there is no "Autoexec.bat" equivalent in Linux.

Cheers

I have the same thing. As root I still can't click on the drive icon without getting permission denied. And as ace said I also get the already mounded when trying to mount the drive. I fiddled with the fstab but still things are the same.

I figure since I have access to all of the files, it really did not matter.

Closest thing to autoexec.bat would be rc.local

You can put startup commands/scripts in there and have them execute after the other startup scripts

Otherwise, you can run boot command from any user's crontab with @reboot directive.

There are a couple of options for you.