Hello,
thank you for your attention and answers.
for that I have a small partition with Windows
I expected that reply - Gracias
That sounds like something which would sit better in our Linux forum.
I don't mind the moving, but I'm not interested in answers regarding to linux.
I'm using Linux/Unix for over 20 years and working with security - so you can take for granted, that I'm not a kidding window user.
The point is, that I'm working on an installer for a Swing application.
My first try was to write an installer with bash and dialog (which works fine), but that's not portable to windows.
Now some windows-guys are interested in using my app, so I'd like to create a installer, that fit's for both worlds.
Users on windows-machines are used to install apps being admin. For me (and I think most other linux users) it's not usual at all. So I'd like to work on a compromise, where the installer can be startet as ordinary user and for system tasks it asks for a password.
I don't like the idea to ask the user to open i.e. java system preferences base for installation. That directory is not popular and that's fine.
The SystemPreferences was an example, where Permission come into the play.
When I'm root, writing SystemPreferences works from my java app. Being ordinary user, that Preferences can't be written. That's totally fine and I don't wonna break that for application run.
Only for installation task
So it does not need to be easy for me, but it should be easy for the installers user and it should be clean and transparent for those guys looking at my code, cause my installer will be open source, when it is working.
I hope, that you can shine me a light on how to progress, or what to research for.
kind regards
Santi