Kerry Mayes wrote:
Just when I thought things were going well...
I keep having Slax hang on me. I am running slax from a usb stick on
dell laptop and had thought it was coming together nicely. But no...
What I've ascertained so far is:
- slax sets up a filesystem in memory, it is destroyed when you reboot;
- there is a subdirectory called "rootcopy" that you can put changed
system files into;
I've made a modified version of rc.inet1 and it's stored in the right
place in rootcopy. It has been correctly appearing in the /etc/rc.d
directory and running as part of startup. Now, however, when I try to
access it, either from the command line or from konqueror, the machine
freezes up. Whatever it is doing can't be stopped and I have to do a
hard reboot to get out of it.
Any ideas what I've done? I can't even think where to start. I've
searched the slax forums, but the only reference to similar behaviour
was a question that no one answered!
Perhaps that is their way of saying 'spare all of us this [EMAIL PROTECTED] pain, and
install it on your [EMAIL PROTECTED] hard drive' ;-)
Also, what would you normally use to kill a program that's stopped
responding? Is there something like task manager in windoze?
$ ps -ax (to obtain the process id) | grep 'what_ur_after ' (to filter
out the rest)
# top
k [pid]
Thanks
Kerry.
hth
--
Rik