Ex/vi Error Unable To Create Temporary File Read-only File System
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and innodb error unable to create temporary file policies of this site About Us Learn more about Stack Overflow the company
Innodb Error Unable To Create Temporary File Errno 13
Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered innodb error unable to create temporary file errno 2 Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:
Freebsd Read Only File System
Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Unable to write to file on FreeBSD — read-only filesystem up vote 1 down vote favorite 1 I bought a load balancer that runs the application on of FreeBSD. I found the configuration file that has all the settings freebsd single user mode read-only file system and login information for both the admin and read-only users. I logged in as the root user, but when I try to alter any files using vi (the only editor installed) I get a read-only filesystem error. I tried chmod 777 file, and when I do ls -l I can see that root has read, write, and execute privileges, but it still won't let me write to the file. What do I need to do to make this file writable? vi share|improve this question edited Feb 20 '13 at 23:35 bahamat 18.7k3581 asked Feb 20 '13 at 20:22 user160246 migrated from serverfault.com Feb 20 '13 at 20:31 This question came from our site for system and network administrators. 1 This question is kinda vague, but it sounds like you are confusing read only file permissions with a read only file system, as mschuett implies in the answer below. –Adam Feb 20 '13 at 20:38 You should get the documentation for the load balancer and use it with the correct interface. Trying to change things on the underlying FreeBSD layer can have disastrous effects and
vi/nano the file i gave freebsd mount you the patch.With viconfig just delete the pptpd section on config and reboot and than you http://unix.stackexchange.com/questions/65523/unable-to-write-to-file-on-freebsd-read-only-filesystem can make the change i gave you in a easier environemnt. krisken: First of all, thanks for your great (and quick) help!I've tried the "viconfig" command in the single user mode, but i https://forum.pfsense.org/index.php?topic=31404.5;wap2 get some errors:ex/vi : Error : /var/tmp/vi.recover : Read-only file systemex/vi : Error : Modifications not recoverable if the session failsex/vi : Error : /cf/conf/config.xml : Read-only file systemex/vi : Error : Unable to create temporary file : Read-only file systemoverride rw-r--r-- root/wheel for /tmp/config.cache?If i just do enter, yes or y, well...i got the # promt and that's it... krisken: Anyone that can help me? :) ermal: Try fsck /and mount -u / or mount -fu / mxx: Before editing try /etc/rc.conf_mount_rw Navigation [0] Message Index [#] Next page [*] Previous page Go to full version
() kmpdc1 ! kmpdesigns ! com [Download message RAW] > -----Original Message----- > From: Dan Weeks [mailto:dan@danimal.org] > Sent: Saturday, November 22, 2003 1:40 PM > > Sampson, Warren said: > > The mobo is a VIA chipset and I'm using the onboard > controllers (channel > http://marc.info/?l=openbsd-newbies&m=107957076215250 > 1 for my "os drive" and channel 2 for my cd/dvd drive). The > card that > > was added is detected as a "Promise PDC20268" and the new drives are > > attached to that (master and slave on the primary channel). > > hmmm, strange. On that I have no idea. Maybe the Promise > has a BIOS that > it installs (similar to SCSI cards). if it flashes something about > configuring maybe you can go into error unable it and change some options. I took a pretty good look through the BIOS didn't see anything. Tried flipping a "boot other device" setting to disabled but that didn't do it. Funny thing I just noticed... after the BIOS checks and before OpenBSD boot starts... I see Updating ESCD ... Success Verifying DMI Pool Data ......... Using Drive: 0 Partition: 3 Reading boot... probing: pc0 apm mem[639K 767M a20=on] disk: hd0 hd1 hd2* >> OpenBSD/i386 BOOT 1.29 boot> booting hd0a:/bsd 4120576+122880+824736+{148428+187803}=0x62770f start=0xd0100020 error unable to ... So... it looks like the computer boots to the proper drive ("Using Drive: 0")... and OpenBSD starts from the "correct" drive number etc... but then as the detection stuff happens, OpenBSD switches around the numbers (disk: hd0 hd1 hd2*). I took a look at dmesg and I can see the add in card gets assigned "PCIIDE0" and the on board gets "PCIIDE1". So it make logical sense that the drives are numbered the way they are... > > > ahhhhhh... that's how you do it... I was running "mount -a" > or "mount > > /dev/wd2g" and not getting anything helpful. > > > > So... I just tried that (mount /dev/wd2g /usr) which was > successful, set > > my TERM and launched VI. I'm getting > > > > ex/vi: Error: /var/tmp/vi.recover: No such file or directory > > ex/vi: Modifications not recoverable if the session fails > > ex/vi: Error: /etc/fstab: Read-only file system" ?? > > ex/vi: Error: Unable to create temporary file: Read-only file system > > okay, so mount /var in the same fasion. also, remount / > (sorry, forgot to > tell you that one) with "mount -o rw /dev/wd2a / > That did it! Booted up fine now (after change to fstab). If anyone is interested I would be happy to post the dmesg output once I get it back and going again... Thanks for your help Dan. Warren _______________________________________________ openbsd-newbies mailing list openbsd-newbies@sfobug.org http://mailman.theapt.org/listinfo/openbs