On Sat, 18 Nov 2006 02:39:53 +0000
Kerry Mayes <[EMAIL PROTECTED]> 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...

slax is a nice litle distro for making extensible/customisable bootable
cds or usb sticks.

> 
> 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;

correct, most bootable cd's set up a ramdisk, as you usually need at
least part of your filesystem to be writable, and the cd obviously
isn't.

> 
> 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.

are you saying when trying to access just that file? Why do you need to
access it once the machine is running?

By the way if you are trying to debug the filesystems you are building
with slax I find running them in a virtual machine with qemu or vmware
to be quite useful. Saves a lot of coasters and/or reboots!

> 
> 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!
> 
> Also, what would you normally use to kill a program that's stopped
> responding? Is there something like task manager in windoze?

if you are sure its the only copy running, try killall, eg assuming the
errant program is mplayer:

killall mplayer

if it still won't go try killall -9 mplayer, which gives a more
peremptory order to close down (at the risk of not shutting down as
cleanly as might be desirable).

If you want to see the running processes, try top - hit q to exit, use
k to kill programs.

To find the pid (process id) of a program use ps ax|grep mplayer - this
will give you the id of every running instance of mplayer. You can then
use kill with the pid number to kill just one instance, eg

kill 10000
kill -9 10000


> 
> Thanks
> Kerry.
> 

Reply via email to