3 ms·
Sometimes finding it difficult to do something is an indication you might have a suboptimal work flow. You can get plenty of info about the health of the drive
by michaelmrose 9y ago
Sometimes finding it difficult to do something is an indication you might have a suboptimal work flow.
You can get plenty of info about the health of the drive while the system is running.
There isn't much reason to run a filesystem check unless something is wrong.
Speaking of services it's extremely easy to query which services are running and enable and disable stuff. Plus there aren't 85 different things running.
If you insist you can run something like
https://github.com/mmstick/systemd-manager https://github.com/mmstick/systemd-manager
- imtringued 9y agoHere is another gui: https://rthomsen6.wordpress.com/2016/12/18/introducing-systemdgenie/ https://rthomsen6.wordpress.com/2016/12/18/introducing-syste...
- mixmastamyk 9y agoThese look nice but the big problem is that they may not be compatible and maintained over the long term because they are not a std part of the desktop.
- michaelmrose 9y agoBecause they aren't needed. We can pretend that the intended user base is your cousin and your grandma if you want but the people that actually use Linux have no problem enabling and disabling services with the command line.
- mixmastamyk 9y agoI’m well aware of the options. The drive isn’t the problem. This thread was about usability and I did happen to need a filesytem check. I’m not a fan of Microsoft biz practices but if you think Linux has nothing to learn from windows (especially on the desktop) you are mistaken.
- michaelmrose 9y agoBasically the optimal tool for offline maintenance is a live disk which will actually work if the drive is screwed up. Basically you were holding it wrong.