Skip to content
This repository has been archived by the owner on Jan 24, 2018. It is now read-only.

on uninstall, run "Stop Debian" #139

Closed
eighthave opened this issue Oct 24, 2014 · 3 comments · May be fixed by #156
Closed

on uninstall, run "Stop Debian" #139

eighthave opened this issue Oct 24, 2014 · 3 comments · May be fixed by #156
Assignees

Comments

@eighthave
Copy link
Member

run "stop debian" on Lil' Debi uninstall to make sure things are left in a sane state. Also, on fresh install, Lil' Debi will not properly detect a running install on internal storage, and instead thinks there is no install.

@eighthave eighthave added this to the 0.5.3 milestone Oct 24, 2014
@eighthave
Copy link
Member Author

since the "delete all" script already runs stop-debian.sh and tries to force-umount /data/debian, it seems that it is doing all the current tricks. Perhaps there needs to be a force kill of all Debian processes as part of this, even more so than what stop-debian.sh does.

@eighthave eighthave removed this from the 0.5.3 milestone Dec 1, 2014
@SDkie
Copy link
Collaborator

SDkie commented Feb 13, 2015

How about a kill-debian.sh script ?

@eighthave
Copy link
Member Author

yeah, sounds like that might be necessary.

@SDkie SDkie self-assigned this Feb 13, 2015
SDkie added a commit to SDkie/lildebi that referenced this issue Feb 15, 2015
kill-debian.sh is similar to stop-debian.sh, except it will not check for open-files.
It will just unmount the system after killing the running processes.

fix guardianproject#139 guardianproject#139
@SDkie SDkie closed this as completed Feb 15, 2015
SDkie added a commit to SDkie/lildebi that referenced this issue Feb 18, 2015
kill-debian.sh is similar to stop-debian.sh, except it will not check for open-files.
It will just unmount the system after killing the running processes.

fix guardianproject#139 guardianproject#139
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants