Historically, in my minimal experience with linux, etc, 'uninstall…, removal, deals well enough with the actual program, even dependencies, but is crap all when dealing with the many config files that are created throughout. The samba reset does work in the few times I’ve used it for just that, but not when the setup is truly broken.
However, it’s still a bug. And if you want NethServer to be full-fledged Small Business Server that competes with Microsoft (like I want) it’s should be fixed.
NethServer, I think, is trying not be the off-the-wall Linux distro that only Linux professional ( or geeks ) know how to get it work. It should work the way is suppose to do and not the “need to do that or this and that AND this” to get it to work.
Uninstalling the user provider is not a supported scenario, because it’s much complicated to restore the machine in the previous state: you need to follow many steps from command line (and I don’t even know which ones).
To do a good job, we shouldn’t allow to uninstall nethserver-dc and nethserver-directory packages from the web interface.
But I think the effort doesn’t worth it (@davidep am I right?).
In a real server, why a user should really uninstall the user provider?
In reality I think this is a tail chaser… anyone seriously setting up an AD server shouldn’t have a use case for later uninstalling the underlying architecture of their whole network other than spinning up a new server install.
The instruction set seems to me to be for an instance of setting up a new environment and oops… I messed up the fqdn or something.
I think we should save ourselves grief by simply not even allowing an uninstall… I know it was a ridiculous proposition in zentyal.
For testing, you should be spinning up fresh installs for whatever you may be testing… or at least using snapshots.
They’re a lot of possibilities why you might take if off. Say you decided you don’t need an AD anymore and so you want to take it off, especially you have very small company. To me it’s good that Microsoft allow you take if off, if you don’t never want to.
Also since NS does not with AD installed by default (Microsoft SBS servers has the AD by default but not the regular standard servers), you should be able to uninstall it.
If you can’t fix it, I agree either block it or showing a big warning. But if you do block it or showing a big warning when trying to remove the AD, when someone installs AD if should have another big warning that you can’t take it off before you actually install it.
Do you an additional developer(s)? Or not enough time to get it done for the expected release? It’s the time of the release, will you have time to work on the bug after it’s release? You like you been thinking about it though
This is also true: I would like to release a new rc2 as soon as possible (also probably CentOS 7.3 will be released soon).
We could do it, but honestly this isn’t a priority for two main reasons.
The web interface now works quite well and it’s stable enough. If we want to add such warning, we should add a full new feature which takes care of a “bad list of packages”.
This list needs to be configurable by the developers because we could add/removed packages during the development cycle.
Also, I give you an insider information (): we totally removed the uninstall button inside the Enterprise release.
I always stood for having the “Remove package” feature, but during the years this feature raised more problems (and support tickets) then benefits.
This is why I would like to spend time implementing more important features (at least from my point of view), and replace code with documentation whenever possible
Um- just for other people who might find this page - not me, you understand - assume I know nothing. Do I need to be in a special directory to run the command or using a special shell or something? I get command not found. A path variable, maybe?