| Summary: | sus-2.0.1.ebuild (new ebuild) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | William Hubbs <kc5eiv> |
| Component: | New packages | Assignee: | Joshua Kinard <kumba> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | kc5eiv |
| Priority: | High | Keywords: | EBUILD |
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
This is the ebuild file.
This is a default configuration file. This is the ebuild file. This is a default configuration file. This is the ebuild (trying again w/ w3m). This is a default configuration file. |
||
|
Description
William Hubbs
2003-05-31 21:18:58 UTC
Created attachment 12624 [details]
This is the ebuild file.
This should probably go in the app-admin category.
Created attachment 12625 [details]
This is a default configuration file.
This file is set up to let users in group "wheel" run any command as root.
Created attachment 12626 [details]
This is the ebuild file.
This should probably go into the app-admin category.
Created attachment 12627 [details]
This is a default configuration file.
This sets up so that users in group wheel can run anything as root.
Created attachment 12682 [details]
This is the ebuild (trying again w/ w3m).
Created attachment 12683 [details]
This is a default configuration file.
Will take a look at the ebuild, clean it up, test, and keyword to ~arch barring any outstanding issues. btw, this program sounds s bit like 'sudo' and 'su', any major differences? One thing it is supposed to be able to do is run processes as session leaders. I guess I just like this program because the control file seems to be a little more understandable than sudo's control file, and it allows me to set up the path so I don't have to type full paths to some commands like I did with sudo. Finally getting around to this (sorry for the delay), but I have a question looking at your ebuild. You install part of the package in /var and make it executable. Is this normal behavior? All my machines mount /var as a separate partition with "noexec" to prevent executables from running from /var. This looks like it might pose a problems for this ebuild. It should not be a problem. /var/run/sus is a directory where timestamps are put similar to the way sudo works. Sudo does the same thing with the directory /var/run/sudo, so if tht doesn't causea problem on your machines this shouldn't either as far as I know. It's added. Made some minor changes to the ebuild to copy the config file to /etc (the config is stored in the files subdir of sus in the tree) and a few einfo's to tell the user to look over this config file. It's marked ~x86, ~sparc, and ~mips. |
