Read-only file system error


 
Thread Tools Search this Thread
Operating Systems OS X (Apple) Read-only file system error
# 15  
Old 02-27-2011
I bet real cash money that this is an ACL issue. OSX started using ACLs a while back on the system folders.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Getting read only propmt when opening /etc/system file

root@atrcx146:/# vi /etc/system "/var/tmp/Exv9a4Rb" Read-only file system Please let me know the reason (1 Reply)
Discussion started by: Marty11
1 Replies

2. UNIX for Dummies Questions & Answers

chown: Read-only file system

Hi, I am logged in as super use and want to set owner of a root folder to a specific user. #chown -R user1:group1 /u01 This gives the message: chown: /u01: Read-only file system chown: lost+found: Read-only file system #ls -l drwxr-xr-x 3 root system 256 Mar 21 16:42... (2 Replies)
Discussion started by: shoefiend
2 Replies

3. UNIX for Dummies Questions & Answers

rm: cannot remove file: Read-only file system

I have a file on a usb stick which I cannot remove and the following error message shows: rm: cannot remove `file-name': Read-only file system The usb stick is mounted as read-only on an Ubuntu system: $ mount /dev/sda1 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw) none... (4 Replies)
Discussion started by: figaro
4 Replies

4. Infrastructure Monitoring

Nagios: How to read the Linux system file?

hi 2 all i installed nagios in my linux srvr . check_ftp file is in format of system format . i wants to see the syntax for that script how can i read that file .. ??? please help me ! (4 Replies)
Discussion started by: ponmuthu
4 Replies

5. SCO

Read and write into file system from SCO

hi Knows someone what kind of file system uses SCO Unix 5.0.6? Which linux or unix LIVE CD can read and write into file system from SCO Unix? I've tried to boot SCO using Knoppix 6.2.1 LIVE CD, but cannot mount. # mount -t sysv /dev/sda1 /mnt mount: wrong fs type, bad option, bad superblock... (2 Replies)
Discussion started by: ccc
2 Replies

6. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies

7. UNIX for Dummies Questions & Answers

/ file system mounts as read only

I have a Netra T1 server running Solaris 8, It was installed by jump start, it does not have a cdrom drive. Recetly it crashed so I rebooted it from >LOM poweron and it came to run level 3, all file systems listed in /etc/vfstab are mounted, but /dev and / root are not writeable though in... (3 Replies)
Discussion started by: Tirmazi
3 Replies

8. UNIX for Dummies Questions & Answers

read only file system

Hi, Has any one worked on IPSO operating system. I have a to add a file to /etc directory. When I create a file it comes up with read only file system. Is there any way of adding a file to this directory, without changing the etc directory parameters. Br, Eugene (1 Reply)
Discussion started by: eugene777
1 Replies

9. Solaris

WARNING: filename <not present on Read Only file system>+pkgadd error

Hi when trying to install the package initially that i have created on to the target host, i am getting error as below for all the files/directories during pkgadd. WARNING: filename <not present on Read Only file system> ........... ........... and so on. When i do the second attempt to... (1 Reply)
Discussion started by: kiran.zamre
1 Replies

10. Shell Programming and Scripting

Read through a file and Pass system commands

Hi, I have a file xyz.txt, which contains several "tar.gz" package names Eg :- Now i need to execute an rpm - ivh against all those packages in this file through a script one by one. I need a script to read through the file "xyz.txt", pick up each package name and execute rpm -ivh... (7 Replies)
Discussion started by: systemali
7 Replies
Login or Register to Ask a Question
RESCUE(8)						    BSD System Manager's Manual 						 RESCUE(8)

NAME
rescue -- rescue utilities in /rescue DESCRIPTION
The /rescue directory contains a collection of common utilities intended for use in recovering a badly damaged system. With the transition to a dynamically-linked root beginning with NetBSD 2.0, there is a real possibility that the standard tools in /bin and /sbin may become non- functional due to a failed upgrade or a disk error. The tools in /rescue are statically linked and should therefore be more resistant to damage. However, being statically linked, the tools in /rescue are also less functional than the standard utilities. In particular, they do not have full use of the locale, pam(3), and nsswitch libraries. If your system fails to boot, and it shows an error message similar to: init: not found try booting the system with the boot flag ``-a'' and supplying /rescue/init, which is the rescue init(8), as the init path. If your system fails to boot, and it shows a prompt similar to: Enter full pathname of shell or RETURN for /bin/sh: the first thing to try running is the standard shell, /bin/sh. If that fails, try running /rescue/sh, which is the rescue shell. To repair the system, the root partition must first be remounted read-write. This can be done with the following mount(8) command: /rescue/mount -uw / The next step is to double-check the contents of /bin, /lib, /libexec, and /sbin, possibly mounting a NetBSD installation CD-ROM and copying files from there. Once it is possible to successfully run /bin/sh, /bin/ls, and other standard utilities, try rebooting back into the stan- dard system. The /rescue tools are compiled using crunchgen(1), which makes them considerably more compact than the standard utilities. FILES
/rescue Root of the rescue hierarchy. SEE ALSO
crunchgen(1) HISTORY
The rescue utilities first appeared in NetBSD 2.0. AUTHORS
The rescue system was written by Luke Mewburn <lukem@NetBSD.org>. This manual page was written by Simon L. Nielsen <simon@FreeBSD.org>, based on text by Tim Kientzle <kientzle@FreeBSD.org>. BUGS
Most of the rescue tools work even in a fairly crippled system. The most egregious exception is the rescue version of vi(1), which currently requires that /usr be mounted so that it can access the termcap(5) files. Hopefully, a failsafe termcap(3) entry will eventually be added into the curses(3) library, so that /rescue/vi can be used even in a system where /usr cannot immediately be mounted. In the meantime, the rescue version of the ed(1) editor can be used from /rescue/ed if you need to edit files, but cannot mount /usr. BSD
January 20, 2009 BSD