Puppy Freezes after 'reboot' from Terminal session window

[halfmeg]

Open a terminal session window and enter the reboot command. You get a couple of lines about killing things and then Puppy freezes. You have to power off the computer to regain control.

This happens in 2.17 & 2.20.

Phil

[HairyWill]

this is known about use wmreboot or wmpoweroff instead

[halfmeg]

Thanks, but the command line instruction should work without having to:

Oh yea, I'm on xyz distro now and it needs 'x^2-Y^3=4-reboot' before it works or otherwise freezes when using the standard command.

Perhaps a script change or two would get it working correctly. Like:

'xwin'

if [ "$WMEXITMODE" = "reboot" ];then
exec /sbin/reboot
fi

could become:

if [ "$WMEXITMODE" = "reboot" ];then
exec /sbin/reboot GUImode
fi

and 'reboot'

#!/bin/sh
/etc/rc.d/rc.shutdown
exec /bin/busybox reboot
could become:

#!/bin/sh
if arg(1) = 'GUImode'
/etc/rc.d/rc.shutdown
exec /bin/busybox reboot
else
wmreboot

or something similiar. This might not be the correct place or method to do this and it might not be the only place the GUImode argument would need to be added. It would permit native command line statements to work and hidden GUI commands to have the unique command formats.

Phil

[halfmeg]

And after a nap and a new look at it. The below substitution for reboot seems to work without changing anything else.

#!/bin/sh
if [ $0 <> "xwin" ]
then
wmreboot
fi
/etc/rc.d/rc.shutdown

exec /bin/busybox reboot

Phil

[halfmeg]

And after a nap and a new look at it. The below substitution for reboot seems to work without changing anything else.

Ignore this last script as $0 will always be 'reboot' instead of the calling program. I was thinking about another system where we could determine the calling program.

Perhaps implementation of 'runlevel' in the next BusyBox for Puppy would provide a suficient check to see what to execute for proper shutdown.

Phil - gone until I'm off the meds