Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You have not supplied enough information for anyone to be able help you.
What version of Linux are you running?
Is it running from a harddrive, a DVD, a USB stick, etc.?
Are you logged in locally or remote?
What directory or device are you trying to write to?
Please review the Site Faq again for guidance on how to ask your questions.
while create a directory or copy anything as root ,there always show "Read-only file system"
any suggestion ......................pls
Here I can help you,
GNU/Linux is GNU/Linux a UNIX base Operating System, and for this type of situation it does not matter what distro or version you have. Because this is basic system administration operations that you need to familiarize yourself with.
this is one way to take care of that, obviously you're creating as root, then trying to use as a user, if you do that as root or su or sudo and you want a user to be able to do more then read it, you have to then do,
Code:
chown user:group 'whatever you're changing ownership to goes here' -R
or change its permissions as root, or add the user to a group that if it is on the system side also has permissions to do other then just read.
what that command did was give the same permissions to the item you changed ownership to that the "new" owner has. his/her name and a group he or she belongs to.
if you are going to be creating new directories or files needed on the user side of the system. You do not have to create them as root user.
whatever user you're logged in as can create what ever directories or files he wants within his environment. they will have the same permissions as the creator.
that is likewise with everything, until such a time you change the permissions to anything by the use of what permissions the creator has to do so.
to over ride a user then you need to go into god mode to do so if you are not the creator of said item or items, or are preforming operations on the system side. ie. anything that resides on what is called the root partition.
if you need to create a file that is to be put onto the system side, you can still do this using your user permissions within the users environment. Then when you are done with whatever file or directory you are working on. (mostly done with files)
you then can use root user to move it onto the system side where ever it needs to be and its permissions will be changed to the root permissions automatically. Due to the ownership permissions relationship that preformed the operation.
There are two situations in which I commonly see this message:
When Linux is started in "single-user mode" following a serious crash, and most filesystems are purposely mounted read-only ... so that you won't fsck things up when you're using fsck to figure out what happened.
In a virtual machine or with an NFS share that has been purposely mounted in this way.
The message, "Read-only file system," means exactly what it says: that the entire file system corresponding to this mount-point prohibits all writing.
Also, notice that I referred to mounting. Unless the device is read-only, such as a CD-ROM, the read-only status is conferred when the device is mounted and can be changed by remounting it.
Last edited by sundialsvcs; 11-15-2016 at 08:13 AM.
You will notice in this output the that root file system '/' is mounted as 'ro' which is 'read-only'. If you were to want to write to this filesystem, you would want it mounted in 'rw' mode which is 'read/write' mode.
Just figured that he probably didn't list every single command or instance that causes it since the pattern is kind of obvious. Best wait for them to get back with a reply before we write out another 7 replies guessing what the issue is.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.