|
Bugzilla – Full Text Bug Listing |
| Summary: | "yast2 foo_module" doesn't check for root user | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Stephan Binner <binner> |
| Component: | YaST2 | Assignee: | Arvin Schnell <aschnell> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | yast2-maintainers |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Stephan Binner
2005-08-18 12:45:09 UTC
That's why yast2 is not in the search path of the non-root user. Try "you" for a user (hint: defaults to "/usr/bin/yast online_update in Beta 2). So a proper fix for this is not to be expected? Joking? The alias is in fact stupid for non-root users. Rudi, I would suggest to add the alias only for root. Dumb question for better understanding: Why does "yast2" as user only show the modules not requiring root access and why do the YaST modules shown within KDE control center offer to switch to administrator mode? Couldn't they also show a non-helping error dialog if any to the user at run time? ;-) changing to "su - -c /sbin/yast2 online_update" back to arvin for the rest of the story I don't see any need for further actions. Honestly, how much time would it take to implement such a check (maybe not for 10.0 anymore but 10.1 then) or whom would it hurt? |