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!
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 accidentally edited the /etc/fstab file which has made my arch box unbootable. Now I want to edit it but the editor says "read-only" file. Tried chmod but no use. How to release the "sticky bit" of the file ?
Tried using arch (older version 0.8) but again the partition / file is mounted as read-only .
I could login as root but I could not chnage the file permissions. Tried chmod u+rwx, chown , umask command but in vain.
mount and remount commands didn't work since they rely on /etc/fstab which is read-only.
Launch the operating system up into single user mode, do umount on the partition containing /etc/fstab then do mount -rw on the partition that contains /etc/fstab and this should restore the ability to write to /etc/fstab...? I don't get why people go around roundabout methods of having to download things to try and fix things when the tools already exist their to fix them o.O?
Last edited by r3sistance; 02-01-2009 at 09:53 AM.
The entire OS is one single partition and so I am afraid to try umount.
The command mount -o remount,rw didn't work with error msg not found in /etc/fstab or mtab.
Tried puppy in live mode but it threw some error msg and didn't boot at all. (Perhaps some problem with my new SATA Moser BAer DVD writer !)
Look at what is mounted and where the current root (/) directory is. If you couldn't boot your system root directory, you may still be running with the system directory in ram (the initrd filesystem) and can try remounting the root system as rw. The system may have bailed out into a root shell before performing the pivot to the system directory (your normal /) and remounting as r/w.
What change did you make to /etc/fstab before rebooting? Was it for you root filesystem partition or another one?
Another possibility is that there was a problem with the filesystem detected and so it was mounted ro as a result. This could have been that you made a mistake editing the root filesystem's fstab entry, or an actual problem was detected. The the boot processes launches fsck, the filesystem isn't mounted r/w yet.
When working as a normal user , I sudoed and edited the /etc/fstab file and commented out the lines starting with UUID.... representing the / and swap file systems. Upon restart the system took a long while to boot throwing out a lot of error messages.And finally hanging for a long time at HAL I was logged into a shell . Since I had to edit the fstab file I logged in as root but found the fstab file mounted as read-only. Since I could not edit the file the problem persisted .
Now I have edited the fstab file by using Nimblex live Cd and I Could boot Arch the normal way. Yet my problem of making the file attribute of fstab file as rw from read-only remains unsolved.
I would have been happier if I had edited the file within Arch.
Anyhow thanks to all of you friends for your help and support.