On Sun, 11 Jun 2000, Dennis Myers wrote:
> flupke wrote:
>
> > Sorry, I didn't follow this tread from the begining, so I hope I won't say
> > anything stoopid or something that has already been said.
> > If I understand, the problem here is all the dump of the stack and
> > registers caused by a page default or something at the end of a shutdown.
> >
> > I have the same problem. I think it only happens on Motherboards with VIA
> > chips. I don't mind about it since it doesn't cause any damage, but it is
> > nice to get rid of that bad stuff.
> > I solved the problem by modifying the /etc/rc.d/init.d/halt file and
> > change the line
> > eval $command -i -d -p
> > to
> > eval $command -i -d
> >
> > PS : http://www.mandrakeuser.org/troubles/tquick1.html :-)
> >
> > HTH
> > Flupke
> >
[...]
> >
>
> Well, I tried my own advise and it didn't work for me either. I see the
> suggestion to edit or modify the rc.d files but don't know how to do that. The
> last time I tried to change a file I crashed the whole config and had to
> reinstall. By the way, I am getting very good at reinstall or new install since
> there seems to be something that causes me to lose my mouse and Keyboard every
> now and then. I keep trying to find the problem but no luck so far. I am
> running an AMD K6 II - 333 with a soyo 5EMA + motherboard 64 meg ram and
> western Digital 13.6 gig ide hard drive, generic floppy and cdrom. If there is
> a man page or faq that talks about editing files I would like to know. I am not
> trained in computers just determined to learn. Thanks in advance for any help
> here.
>
>
>
OK, Dennis. Don't be afraid. To avoid problem when modifying a file that
is important for the system, you just have to save before editing :
cd /etc/rc.d/init.d/
cp halt halt.orig
vi halt
(NB : DON'T DO THAT if you never used vi... in that case, use kedit, pico
or another one that you know. But if you want to give vi a blind try,
once it is opened, just type "G$xxx" to go to the last line of the file,
go to the end of the line and erase the last 3 chars, then type ":wq" and
press enter to save the file and quit edition)
That way, if there is a problem, you simply have to boot in single-user
mode and put the files as they were before. But note that there is no
danger here, since the file that has to be edited is only invoked at
shutdown or reboot time.
There is also something that can be usefull : make an archive of /etc and
put it in a safe place, so that you can restore a file that you broke.
For doc about safe edition, maybe you could browse the HOWTOs. There is a
security-HOWTO that talks about safety in a network, maybe there is
another one about safety in your system...
For doc about edition itself, well, I must say that I'm a vi fan. So, I
would suggest you two things :
- In the man vi, I think you will find a reference to a basic
tutorial. Read that tutorial.
- Then, you take a cup of cofee, you start vi, and you type ':help'
HTH
Flupke
--
<< There's no place like ~ ! >>
