forked from igosnusantara/fedorautils
-
Notifications
You must be signed in to change notification settings - Fork 0
/
fedy.1
53 lines (39 loc) · 2 KB
/
fedy.1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
.TH "fedy" 1 "28 June 2012" Fedora "User Manual"
.SH NAME
Fedy - Tweak your Fedora
.SH SYNOPSIS
.B fedy
[options...]
.SH DESCRIPTION
Fedy lets you install multimedia codecs and additional software that Fedora doesn't want to ship, like mp3 support, Adobe Flash, Oracle Java etc., and much more with just a few clicks.
.PP
After installation, search for
.B Fedy
in the menu/overview or type
.B fedy
in the terminal.
.PP
Fedy requires root permissions to perform various tasks.
.SH OPTIONS
Fedy supports specifying options for temporarily changing different configuration variables and executing various commands, helpful in case you don't want to change a configuration permanently and want to enable/disable some features just for the session, or execute certain commands without launching the full interface. You can get a list of supported arguments with
.B fedy --help
.SH FILES
.SS Configuration files
Fedy supports use of configuration files. The global configuration file is usually
.B /etc/fedyrc
and user-specific configuration file is usually
.B ~/.fedyrc
(unless overriden in the global configuration file). The user specific configurations will be given higher priority than the global configurations. Arguments can override values in configuration files.
.PP
Configuration files can be used for changing configurations, setting value of shell variables (for example setting the proxy), or running any command before starting the GUI.
.SS Plugins
Fedy supports plugins for adding more functionality. You can write your own custom plugins for Fedy. The plugin files are usually located under
.B /usr/share/fedy/plugins
.SH BUGS
You can report bugs at http://github.com/satya164/fedy/issues
Before reporting a bug, please run Fedy at least once with logging enabled (See
.B fedy --help
to know how to enable logging) and repeat the actions which cause an error. Submitting the logged information might be helpful for identifying the problem quickly.
.SH SEE ALSO
curl(1), rpm(8), yum(8)
http://github.com/satya164/fedy/wiki