|
ru.linux- RU.LINUX --------------------------------------------------------------------- From : Leschinsky Oleg 2:5020/400 12 Jun 2003 12:39:49 To : All Subject : Просто дурдом. --------------------------------------------------------------------------------
Добрый день!
Жалко человека до слез. Вот к чему приводит политика использования
графических конфигурялок компании Red Hat. :) Просто дурдом. :(
[ This is a repost of the following article: ]
[ From: jhardy012003@yahoo.com.au (Luis) ]
[ Subject: help, server is down and cannot edit rc.sysinit.d ]
[ Newsgroups: comp.os.linux.setup ]
[ Message-ID: <e12ed29.0306100439.3c67a421@posting.google.com> ]
Hi
i was running red hat 8 server with web and mail hosting.
I accidentally edited the rc.sysinit.d file and now it will not boot
up. it stops with bash. If i type vi /etc/rc.d/rc.sysinit the file
comes up but it cannot be edited because it is a read only file. It
tells me to try ! when i try to edit using vi to change the
permissions. Also i cannot edit rc.sysinit.d file anymore as it is not
there but the file rc.sysinit looks exactly the same as rc.sysinit.d
How can i change the permissions and edit the file in the state it is
in? Am i doomed???? If not, i am going to cry!!!!
The line i edited before all of this happened was !/bin/bash (line1)
and the reason was because when i was booting up the system, it came
up with an error saying that it did not recognise line 1. So i edited
and got rid of the ! because i thought it was a mistake. What should
line 1 have in this file?
Can i edit this file and bring it back online again or not?
I have tried using chmod on the file and it still says it is a read
only file. I typed chmod a -rw rc.sysinit and it said that it was
changing permissions and that the file is read only. So no changes
occured.
The permissions on the file are -rwxr-xr-x root.
when i try to use the text editor vi it comes up and says it is a read
only file and to use ! to override this. I do not know how to override
or what command to type. I have tried chmod at this point but nothing
seems to work. Comes up with can't get temp file name.
Point where system stops is bash -2 05b#. What does this mean?
if i do use the cdrom, do i just boot using it and then what do i need
to do?
What happended to rc.sysinit.d?
also, the error comes up as well if i try to edit the file - "can't
get temp file name"
tried to boot with linux boot disk and no success, it still stops at
that same point.
am i correct in typing linux params when the disk boots up?
What does this mean?
--- ifmail v.2.15dev5
* Origin: user from ELVISTI (2:5020/400)
Вернуться к списку тем, сортированных по: возрастание даты уменьшение даты тема автор
Архивное /ru.linux/35769620f02e.html, оценка из 5, голосов 10
|