SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a USB card reader with my camera card. It mounts read only, and I have no idea how to write to it. It worked fine on my old system (arch) before reformatting, and I am new to Slackware. Running as root doesn't make any difference.
I haven't done anything to configure how it mounts. If I plug it in, it mounts automatically and shows up read only. I suppose I could try to use the 'mount' command to mount it differently to a different path, but that seems like the wrong solution. I assume 'root' being unable to write to the drive rules out permission issues.
You could try (of course replacing /media/dir with the actual):
mount -o remount,rw /media/dir
Also note that some filesystems (ext2 and jfs I think) support the mount option "errors=remount-ro". This causes, as you might guess, the filesystem to be remounted read-only when there's any error. I believe the device itself can be marked to default with this option, which the manufacturer may have done (assuming you didn't reformat it).
If that's the case, I think you can change the default to "errors=continue" with the tune2fs program. Or you can add a line to /etc/fstab to explicitly mount it the way you want.
2 more things to try 1)this one almost stumped me until I realized one USB drive gad a sliding lock on it or 2) this often works when the mount issue is screwed up takes a few minutes
sudo killall udisks
Both the mount command and the /etc/fstab mount a device as read/write unless specified as read only. Therefore, if you are having trouble reading and writing to a mounted device, you will want to check you fstab file to ensure that you have the correct permissions specified.
I note that running as root doesn't`t help., which I assume means that even as root you can't write to the automounted filesystem... but have you actually tried a command-line mount as root? I think it's
mount -t vfat /dev/(your card) /media/(mountpoint)
. I have seen a usb device mounted read-only , in this case because the filesystem was damaged. Post again if this is unclear.