example-tutorial/figs fedora-logo-sprite.eps, NONE, 1.1 fedora-logo-sprite.gif, NONE, 1.1 fedora-logo-sprite.jpg, NONE, 1.1 fedora-logo-sprite.png, NONE, 1.1 fedora-logo-sprite.svg, NONE, 1.1 fedora-logo-sprite.tif, NONE, 1.1
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/example-tutorial/figs
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17234
Added Files:
fedora-logo-sprite.eps fedora-logo-sprite.gif
fedora-logo-sprite.jpg fedora-logo-sprite.png
fedora-logo-sprite.svg fedora-logo-sprite.tif
Log Message:
Added some image types. Don't get attached to them.
I'll take them out later but I was playing around with some PDF
generation and wanted to see how some file references were generated
via the XML.
I forgot I'd done them when I commited the "LOCAL-ENT" change, so to
keep everything from breaking, I'm compounding the error ;-)
--- NEW FILE fedora-logo-sprite.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%Creator: (ImageMagick)
%%Title: (fedora-logo-sprite.eps)
%%CreationDate: (Sun Apr 2 12:48:10 2006)
%%BoundingBox: 0 0 64 64
%%HiResBoundingBox: 0 0 64 64
%%DocumentData: Clean7Bit
%%LanguageLevel: 1
%%Pages: 1
%%EndComments
%%BeginDefaults
%%EndDefaults
%%BeginProlog
%
% Display a color image. The image is displayed in color on
% Postscript viewers or printers that support color, otherwise
% it is displayed as grayscale.
%
/DirectClassPacket
{
%
% Get a DirectClass packet.
%
% Parameters:
% red.
% green.
% blue.
% length: number of pixels minus one of this color (optional).
%
currentfile color_packet readhexstring pop pop
compression 0 eq
{
/number_pixels 3 def
}
{
currentfile byte readhexstring pop 0 get
/number_pixels exch 1 add 3 mul def
} ifelse
0 3 number_pixels 1 sub
{
pixels exch color_packet putinterval
} for
pixels 0 number_pixels getinterval
} bind def
/DirectClassImage
{
%
% Display a DirectClass image.
%
systemdict /colorimage known
{
columns rows 8
[
columns 0 0
rows neg 0 rows
]
{ DirectClassPacket } false 3 colorimage
}
{
%
% No colorimage operator; convert to grayscale.
%
columns rows 8
[
columns 0 0
rows neg 0 rows
]
{ GrayDirectClassPacket } image
} ifelse
} bind def
/GrayDirectClassPacket
{
%
% Get a DirectClass packet; convert to grayscale.
%
% Parameters:
% red
% green
% blue
% length: number of pixels minus one of this color (optional).
%
currentfile color_packet readhexstring pop pop
color_packet 0 get 0.299 mul
color_packet 1 get 0.587 mul add
color_packet 2 get 0.114 mul add
cvi
/gray_packet exch def
compression 0 eq
{
/number_pixels 1 def
}
{
currentfile byte readhexstring pop 0 get
/number_pixels exch 1 add def
} ifelse
0 1 number_pixels 1 sub
{
pixels exch gray_packet put
} for
pixels 0 number_pixels getinterval
} bind def
/GrayPseudoClassPacket
{
%
% Get a PseudoClass packet; convert to grayscale.
%
% Parameters:
% index: index into the colormap.
% length: number of pixels minus one of this color (optional).
%
currentfile byte readhexstring pop 0 get
/offset exch 3 mul def
/color_packet colormap offset 3 getinterval def
color_packet 0 get 0.299 mul
color_packet 1 get 0.587 mul add
color_packet 2 get 0.114 mul add
cvi
/gray_packet exch def
compression 0 eq
{
/number_pixels 1 def
}
{
currentfile byte readhexstring pop 0 get
/number_pixels exch 1 add def
} ifelse
0 1 number_pixels 1 sub
{
pixels exch gray_packet put
} for
pixels 0 number_pixels getinterval
} bind def
/PseudoClassPacket
{
%
% Get a PseudoClass packet.
%
% Parameters:
% index: index into the colormap.
% length: number of pixels minus one of this color (optional).
%
currentfile byte readhexstring pop 0 get
/offset exch 3 mul def
/color_packet colormap offset 3 getinterval def
compression 0 eq
{
/number_pixels 3 def
}
{
currentfile byte readhexstring pop 0 get
/number_pixels exch 1 add 3 mul def
} ifelse
0 3 number_pixels 1 sub
{
pixels exch color_packet putinterval
} for
pixels 0 number_pixels getinterval
} bind def
/PseudoClassImage
{
%
% Display a PseudoClass image.
%
% Parameters:
% class: 0-PseudoClass or 1-Grayscale.
%
currentfile buffer readline pop
token pop /class exch def pop
class 0 gt
{
currentfile buffer readline pop
token pop /depth exch def pop
/grays columns 8 add depth sub depth mul 8 idiv string def
columns rows depth
[
columns 0 0
rows neg 0 rows
]
{ currentfile grays readhexstring pop } image
}
{
%
% Parameters:
% colors: number of colors in the colormap.
% colormap: red, green, blue color packets.
%
currentfile buffer readline pop
token pop /colors exch def pop
/colors colors 3 mul def
/colormap colors string def
currentfile colormap readhexstring pop pop
systemdict /colorimage known
{
columns rows 8
[
columns 0 0
rows neg 0 rows
]
{ PseudoClassPacket } false 3 colorimage
}
{
%
% No colorimage operator; convert to grayscale.
%
columns rows 8
[
columns 0 0
rows neg 0 rows
]
{ GrayPseudoClassPacket } image
} ifelse
} ifelse
} bind def
/DisplayImage
{
%
% Display a DirectClass or PseudoClass image.
%
% Parameters:
% x & y translation.
% x & y scale.
% label pointsize.
% image label.
% image columns & rows.
% class: 0-DirectClass or 1-PseudoClass.
% compression: 0-none or 1-RunlengthEncoded.
% hex color packets.
%
gsave
/buffer 512 string def
/byte 1 string def
/color_packet 3 string def
/pixels 768 string def
currentfile buffer readline pop
token pop /x exch def
token pop /y exch def pop
x y translate
currentfile buffer readline pop
token pop /x exch def
token pop /y exch def pop
currentfile buffer readline pop
token pop /pointsize exch def pop
/Times-Roman findfont pointsize scalefont setfont
x y scale
currentfile buffer readline pop
token pop /columns exch def
token pop /rows exch def pop
currentfile buffer readline pop
token pop /class exch def pop
currentfile buffer readline pop
token pop /compression exch def pop
class 0 gt { PseudoClassImage } { DirectClassImage } ifelse
grestore
} bind def
%%EndProlog
%%Page: 1 1
%%PageBoundingBox: 0 0 64 64
userdict begin
DisplayImage
0 0
64 64
12.000000
64 64
0
0
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFEFEF3F3F3
D3D3D3A7A7A77777774F4F4F2F2F2F2020200F0F0F0303030101010B0B0B1B1B1B2B2B2B
4545456D6D6D9A9A9AC8C8C8EDEDEDFDFDFDFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
F3F3F3C6C6C68484844545451C1C1C070707000000000000000000000000000000000000
000000000000000000000000000000000000040404151515393939727272B6B6B6EBEBEB
FEFEFEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFEFEFEE5E5E59A9A9A454545101010000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000090909333333838383D6D6D6FCFCFCFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFE6E6E68D8D8D2E2E2E030303000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000101011D1D1D727272D5D5D5
FDFDFDFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF5F5F5A4A4A4343434020202000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000202020868686E9E9E9FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFD6D6D65B5B5B090909
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000202023D3D3DBCBCBCFCFCFC
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFBFBFB
ADADAD292929000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000001515158A8A8AF2F2F2FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFF5F5F58B8B8B101010000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000D0E0F292B2C45484B5F61626565665F6062424649
22252806080B000000000000000000000000000000050505636363E7E7E7FFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF1F1F1707070070707000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000050506343638828487C3C5C6E7E8EAF6F7F8
FEFEFEFFFFFFFDFEFEF5F6F7E0E3E6A6B0BA3B526A011223000204000000000000000000
010101494949DCDCDCFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF1F1F16A6A6A030303000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000001012F31329C9EA0EAEBEC
FEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFE0EAF4487BAF
033566021120000000000000000000000000424242DBDBDBFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF5F5F5
707070030303000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000080809
67696CE0E1E2FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFB7CEE5145FAA084D92042546000306000000000000000000454545
E3E3E3FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFCFCFC8A8A8A070707000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000C0E0F888B8EF6F7F7FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFE1EAF3266AAE0856A40955A005305C
0005090000000000000000005C5C5CEFEFEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFADADAD101010000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000090A0A8B8E91FAFAFBFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFCFDEED
1C63AA0856A30A57A40956A305325E0004070000000000000303037E7E7EFBFBFBFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFD5D5D52A2A2A000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000010101717476F8F8F9FFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFBFCFD7CA5CE0956A30956A30A56A30A57A40955A104294E000001000000
0000000F0F0FAEAEAEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
F5F5F55C5C5C000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
3B3D3FE6E7E8FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFEFEF0F1F2
DCDDDED0D3D6D8DADCE2E6EAE6EEF6D4E2F07EA6CF165FA80956A30A57A40A57A40A56A3
0A57A509509702162B000000000000000000313131DEDEDEFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFA4A4A4080808000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000A0B0CAEB0B2FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FEFEFFDADBDD808285393B3D1B1C1D14151718191B22292F29435D1D57910957A40956A3
0A57A40A57A40A57A40A57A40A56A30A58A6073E75000408000000000000000000717171
FCFCFCFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFE5E5E5353535000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000494B4DF3F4F5FFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFCFCFDA9ABAD27292B000000000000000000000000000000000000
000000000B150637670956A20A57A40A56A30A57A40A57A40A57A40A57A409549F031C34
000000000000000000151515C3C3C3FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF8D8D8D
010101000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000203039EA0A2
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA4A6A8121314000000000000000000
0000000000000000000000000000000000000004090634620A57A40A57A40A57A40A57A4
0A57A40A56A30A58A606396C000103000000000000000000595959F7F7F7FFFFFFFFFFFF
FFFFFFFFFFFFE5E5E52F2F2F000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000001D1F20DADCDDFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFCECFD1202123
000000000000000000000000000000000000000000000000000000000000000000000810
07427E0A58A50A56A30A57A40A57A40A57A40A57A5084C90010C16000000000000000000
101010C0C0C0FFFFFFFFFFFFFFFFFFFFFFFF9A9A9A030303000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000046484AF6F7F7FFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFCFCFD686A6C000000000000000000000000000000000000000000000000000000
000000000000000000000000031E3A0955A00A57A40A57A40A57A40A57A40A57A40955A0
031A32000000000000000000000000656565FCFCFCFFFFFFFFFFFFF3F3F3464646000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000006A6D6FFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFDFE1E2232526000000000000000000000000000000
0000000000000000000000000000000000000000000000000108100848890A57A50A57A4
0A57A40A57A40A57A30A57A504274A0000000000000000000000001E1E1ED8D8D8FFFFFF
FFFFFFC6C6C6101010000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000008A8C8EFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFBEBFC1090A0A000000
000000000000000000000000000000000000000000000000000000000000000000000000
000102063B700A58A60A57A40A57A40A57A40A57A40A58A605325E000000000000000000
000000000000949494FFFFFFFFFFFF848484000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000949494FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFABAEB2030405000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000533610A58A60A57A40A57A40A57A40A57A40A58A7
0636660000000000000000000000000000004F4F4FF6F6F6F3F3F3464646000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000949495FFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA6AAAE020304000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000637680A58A60A57A4
0A57A40A57A40A57A40A58A60635640000000000000000000000000000001E1E1ED4D4D4
D3D3D31D1D1D000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000949495FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA6AAAE020304000000
000000000000000000000000000000000000000000000000000000000000000000000000
00040707427C0A58A60A57A40A57A40A57A40A56A30A58A6052C54000000000000000000
000000000000060606A0A0A0A7A7A7070707000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000949495FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFA6AAAE020304000000000000000000000000000000000000000000000000000000
0000000000000000000000000212220950970A57A40A57A40A57A40A57A40A57A40956A3
03213E000000000000000000000000000000000000696969777777000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000949495FFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA6AAAE020304000000000000000000000000000000
00000000000000000000000000000000000000000000010105315D0A57A50A57A40A57A4
0A57A40A57A40A57A4095199021223000000000000000000000000000000000000393939
505050000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000949495FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA6AAAE020304000000
000000000000000000000000000000000000000000000000000000000000000000031B33
0951990A57A40A57A30A57A40A57A40A56A30A58A607437F00050A000000000000000000
0000000000000000001818182F2F2F000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000949495FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFA6AAAE020304000000000000000000000000000000000000000000000000000000
00000000000102192F084B8E0A57A50A56A30A57A40A57A40A57A40A57A40A57A504294E
000000000000000000000000000000000000000000010101202020000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000939494FFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFAFB2B5050606000000000000000000000000000000
000000000000000000000001010B15042B51094F960A57A50A56A30A57A40A57A40A57A4
0A56A30A57A5084B8E010D18000000000000000000000000000000000000000000000000
0F0F0F000000000000000000000000000000000000000000000000000000000000000000
000000000000000409010E1B02192F021E3920354A535A6164696D65696D65696D65696D
65696D64686CBEC0C2FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEAEAEB80848764686C
65696D65696D65696D65696D575D64273B4E04294D063768084B8D0A57A40A57A40956A3
0A57A40A57A40A57A40A57A40A57A40956A304284C000000000000000000000000000000
000000000000000000000000030303000000000000000000000000000000000000000000
000000000000000000000103021121052C5407437E094F9508549F4F85BCD3E1EEFBFCFD
FEFFFFFEFFFFFEFFFFFEFFFFFEFFFFFEFFFFFEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFEFFFFFEFFFFFEFFFFFEFFFFFEFFFFFEFFFFFCFDFEDDE7F26093C50A58A6
0957A50A57A40A56A30A57A40A57A40A57A40A57A40A57A40A58A6073E7500060C000000
0000000000000000000000000000000000000000000000000A0A0A000000000000000000
000000000000000000000000000000000000010F1D063463094F960A57A50A58A60856A4
286CAFD4E2EFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFE2EBF43675B40755A30A57A40A57A40A57A40A57A40A57A40A57A40A58A6
084787010F1D000000000000000000000000000000000000000000000000000000000000
010101000000000000000000000000000000000000000000000205032241084C8F0A58A6
0A57A40A57A40A57A30654A25E91C3FBFCFDFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF729ECA0654A20956A30A57A40A57A4
0A56A30A57A40A58A6084787021324000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000407
052D5609549F0A57A50A57A40A57A40A57A40A57A40654A26A99C7FEFEFEFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF7DA5CE
0654A20956A30A57A30A57A40A57A50A57A407407801101F000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000205052E570955A10A57A40A56A30A57A40A57A40A57A40A57A40754A2
3F7BB7EDF2F8FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFF5F8FB5187BE0654A20A57A40A57A50A57A5084D92042B5100070E000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000425460954A00A57A40A56A30A57A40A57A4
0A57A40A57A40A56A30956A30E5AA688AED5F8FAFDFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFBFDFE9BBBDC135EAA0957A509549E084888052E57
010F1D000001000000000000000000000000000000000000000000000000000000000000
000000000000000000101010000000000000000000000000000000021223084E930A57A5
0A56A30A57A40A57A40A57A40A56A30A57A40A57A50956A3084D93104A85607D9BA7AFB7
BBBEC1BCBFC1BCBFC1BCBFC1BBBEC1C9CACCF6F7F7FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFE6E8EABCBFC2BCBEC1BCBEC1BCBEC1BCBFC1BBBEC1AAB1B868829C144576043463
04294E02182E00080F000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000002F2F2F000000000000000000000000
00020506396C0A58A60A56A30A57A40A57A40A57A40A56A30A57A40A57A4084685042546
010E1A00040900010403050708090A08090A08090A08090A080909101112ADAFB0FFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA9ADB10B0D0E08090A08090A08090A08090A08090A
040507000004000103000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000005B5B5B
00000000000000000000000002162A09529B0A57A40A57A40A57A40A57A40A56A30A57A4
0955A2063565010A13000000000000000000000000000000000000000000000000000000
000000000000939494FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA6AAAE020304000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000303039191910000000000000000000000000533610A58A60A56A30A57A4
0A57A40A57A40A57A40A57A4063565000409000000000000000000000000000000000000
000000000000000000000000000000000000949495FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFA6AAAE020304000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000151515C8C8C800000000000000000000080F
0848880A57A50A57A40A57A40A57A40A56A30A57A5084583010A13000000000000000000
000000000000000000000000000000000000000000000000000000000000949495FFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA6AAAE020304000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000404040F0F0F0
00000000000000000002152709539C0A57A40A57A40A57A40A57A40A57A40956A2042342
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000949495FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA6AAAE020304000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000828282FFFFFF0000000000000000000321400956A30A57A40A57A40A57A4
0A57A40A57A5084C90010C17000000000000000000000000000000000000000000000000
000000000000000000000000000000000000949495FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFA6AAAE020304000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000121212C8C8C8FFFFFF00000000000000000004294D
0A58A60A57A30A57A40A57A40A57A40A58A6074079000306000000000000000000000000
000000000000000000000000000000000000000000000000000000000000949495FFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA6AAAE020304000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000004F4F4FF6F6F6FFFFFF
000000000000000000042B510A58A60A57A40A57A40A57A40A57A40A58A6063A6D000001
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000949495FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA6AAAE020304000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
070707AAAAAAFFFFFFFFFFFF000000000000000000042A4F0A58A60A57A30A57A40A57A4
0A57A40A58A6073D73000204000000000000000000000000000000000000000000000000
0000000000000000000000000000000000009B9D9FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFF9EA2A6010202000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000414141EEEEEEFFFFFFFFFFFF000000000000000000042547
0A57A50A57A40A57A40A57A40A57A40A57A508488800080F000000000000000000000000
0000000000000000000000000000000000000000000000000000000B0C0DBFC1C3FFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF8C8E90000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000090909A9A9A9FFFFFFFFFFFFFFFFFF
00000000000000000002193009549F0A57A40A57A40A57A40A57A40A57A409539D021930
000000000000000000000000000000000000000000000000000000000000000000000000
000000343638EAEBECFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF6C6E70000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000545454
F4F4F4FFFFFFFFFFFFFFFFFF000000000000000000010C17084D910A57A50A57A40A57A4
0A57A40A56A30A58A6063A6F000306000000000000000000000000000000000000000000
000000000000000000000000030404919497FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
F2F3F43E4041000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000001B1B1BC8C8C8FFFFFFFFFFFFFFFFFFFFFFFF000000000000000000000204
063C710A58A60A56A30A57A40A57A40A57A40A57A409549F042444000000000000000000
000000000000000000000000000000000000000000000000545658EEEFF0FFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFCCCECF131516000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000404048D8D8DFEFEFEFFFFFFFFFFFFFFFFFFFFFFFF
00000000000000000000000003213F0956A20A57A40A57A40A57A40A57A40A56A30A57A5
095198032241000204000000000000000000000000000000000000000000020303515355
E1E2E3FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF818386000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000005A5A5AF1F1F1FFFFFF
FFFFFFFFFFFFFFFFFFFFFFFF00000000000000000000000000080F0745820A58A60A56A3
0A57A40A57A40A57A40A56A30A57A507519C033262021221000305000000000000000000
0506062A2C2D8A8C8EECEDEEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFE0E1E3
2B2D2F000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
3A3A3ADDDDDDFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF000000000000000000000000
00000003203D0954A00A57A40A56A30A57A40A57A40956A30856A32F71B280A8D1A7BCD1
A0A8AF83888E777B7E878B8EB1B3B5E4E5E6FEFEFEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFDFEFE7D8082000001000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000262626C9C9C9FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0000000000000000000000000000000003060636670A57A50A57A40A57A40A57A40755A3
3C79B6D6E2EFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFBBBDBF161718000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000222222BCBCBCFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFF000000000000000000000000000000000000010B1407427D
0A58A60A57A40956A30D59A5A4C0DDFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFD4D6D8333436000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000262626BCBCBCFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF000000000000000000000000
000000000000000000010E1B07437E0A58A60956A31861A9CCDCECFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
D5D7D93E4043000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
393939CACACAFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0D0D0D000000000000000000000000000000000000000000010C17063A6E0955A2135EA9
BED2E7FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFDFDFEC0C2C4343638000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000505055A5A5ADDDDDDFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFF313131000000000000000000000000000000000000000000
00000000050A04264906498D6898C8F5F9FCFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFE6E7E885878A181A1B000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000001B1B1B8D8D8DF1F1F1FFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF797979010101000000000000
000000000000000000000000000000000000000000000C180B2F547491ADE2E8EEFDFEFE
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFF8F8F9D7D8DA8D9092313335020303000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000090909535353C9C9C9FDFDFDFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
D7D7D72B2B2B000000000000000000000000000000000000000000000000000000000000
00000002070D2A323A676D72989B9FB1B2B3B6B8BAB2B4B5A3A5A77D7F824C4E501B1C1E
010202000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000070707414141AAAAAA
F4F4F4FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA7A7A7101010000000000000000000000000000000
000000000000000000000000000000000000000000000000000001040505060809050506
010101000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000121212
4F4F4FAAAAAAEFEFEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFBFBFB9F9F9F1F1F1F
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000030303
1515153F3F3F828282C9C9C9F6F6F6FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFDFDFDC6C6C65555550C0C0C000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000
1010102F2F2F5C5C5C929292C8C8C8F0F0F0FEFEFEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFF
end
%%PageTrailer
%%Trailer
%%EOF
--- NEW FILE fedora-logo-sprite.svg ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg xmlns="http://www.w3.org/2000/svg" version="1.0"
x="0.0000000" y="0.0000000" width="252.32" height="252.32"
viewBox="0 0 252.32 252.32" xml:space="preserve"
id="translucent-fedora-logo-with-radial-gradient">
<g id="main-group">
<g id="radial-gradient-group">
<radialGradient cx="115.89890" cy="133.10451" r="154.62019" fx="115.89890" fy="133.10451" id="radial-gradient" gradientUnits="userSpaceOnUse">
<stop style="stop-color: #000000; stop-opacity: 0.0;" offset="0.0" id="translucent-stop-color"/>
<stop style="stop-color: #0068c9; stop-opacity: 1.0;" offset="1.0" id="opaque-blue-stop-color"/>
</radialGradient>
<path d="M 252.31700,126.16300 C 252.31700,56.485000 195.83500,0.0000000 126.16000,0.0000000 C 56.517000,0.0000000 0.051000000,56.437000 0.0030000000,126.07200 L 0.0000000,126.06600 L 0.0000000,223.69600 L 0.0030000000,223.70400 C 0.041000000,239.51400 12.864000,252.31000 28.688000,252.31000 C 28.733000,252.31000 28.776000,252.30400 28.821000,252.30400 L 28.830000,252.31000 L 126.21100,252.31000 L 126.21100,252.31000 C 195.86100,252.28100 252.31700,195.82000 252.31700,126.16300 z " style="fill:url(#radial-gradient)" id="speech-bubble"/>
</g>
<g id="f-script">
<path d="M 163.20200,29.904000 C 130.49800,29.904000 103.98900,56.414000 103.98900,89.116000 C 103.98900,89.127000 103.98900,89.142000 103.98900,89.157000 L 103.98900,120.49600 L 72.746000,120.49600 C 72.741000,120.49600 72.741000,120.49600 72.738000,120.49600 C 40.035000,120.49600 13.526000,146.87700 13.526000,179.57700 C 13.526000,212.28200 40.036000,238.79100 72.738000,238.79100 C 105.43700,238.79100 131.94700,212.28200 131.94700,179.57700 C 131.94700,179.56500 131.94700,179.55400 131.94700,179.53600 L 131.94700,148.06700 L 163.18900,148.06700 C 163.19600,148.06700 163.19900,148.06700 163.20200,148.06700 C 195.90100,148.06700 222.41100,121.81600 222.41100,89.116000 C 222.41100,56.414000 195.90100,29.904000 163.20200,29.904000 z M 103.98900,179.63300 C 103.96400,196.86400 89.979000,210.83300 72.738000,210.83300 C 55.479000,210.83300 41.358000,196.84100 41.358000,179.58200 C 41.358000,162.31700 55.479000,148.06600 72.738000,148.06600 C 72.752000,148.06600 72.76!
6000,148.06600 72.779000,148.06600 L 99.558000,148.06600 C 99.567000,148.06600 99.572000,148.06600 99.578000,148.06600 C 102.01600,148.06600 103.99300,150.03900 103.99300,152.47300 C 103.99300,152.47800 103.99000,152.47800 103.99000,152.48400 L 103.99000,179.63300 L 103.98900,179.63300 z M 163.19900,120.49600 C 163.18900,120.49600 163.17900,120.49600 163.17000,120.49600 L 136.37300,120.49600 C 136.36700,120.49600 136.36000,120.49600 136.35700,120.49600 C 133.91900,120.49600 131.94700,118.52400 131.94700,116.08400 L 131.94700,116.08300 L 131.94700,89.065000 C 131.97600,71.824000 145.95700,57.860000 163.19900,57.860000 C 180.45800,57.860000 194.58200,71.853000 194.58200,89.115000 C 194.58200,106.37500 180.45800,120.49600 163.19900,120.49600 z " style="fill:#0a57a4" id="f-script-path"/>
</g>
<path d="M 103.98900,120.49600 L 103.98900,89.156000 C 103.98900,89.142000 103.98900,89.127000 103.98900,89.115000 C 103.98900,56.413000 130.49800,29.903000 163.20200,29.903000 C 168.16300,29.903000 171.68800,30.462000 176.28000,31.664000 C 182.97700,33.420000 188.44600,38.906000 188.44900,45.292000 C 188.45200,53.012000 182.84800,58.624000 174.47300,58.624000 C 170.48300,58.624000 169.04100,57.860000 163.19900,57.860000 C 145.95700,57.860000 131.97600,71.824000 131.94700,89.065000 L 131.94700,116.08200 L 131.94700,116.08300 C 131.94700,118.52300 133.91900,120.49500 136.35700,120.49500 C 136.36000,120.49500 136.36700,120.49500 136.37300,120.49500 L 156.89500,120.49500 C 164.54300,120.49500 170.71900,126.61800 170.72500,134.28600 C 170.72500,141.95700 164.54000,148.06600 156.89500,148.06600 L 131.94700,148.06600 L 131.94700,179.53500 C 131.94700,179.55300 131.94700,179.56400 131.94700,179.58200 C 131.94700,212.28100 105.43700,238.79000 72.738000,238.79000 C 67.776000!
,238.79000 64.251000,238.23100 59.659000,237.02800 C 52.962000,235.27300 47.491000,229.78400 47.488000,223.40000 C 47.488000,215.68200 53.088000,210.06800 61.467000,210.06800 C 65.453000,210.06800 66.899000,210.83300 72.738000,210.83300 C 89.980000,210.83300 103.96500,196.86800 103.99200,179.63300 C 103.99200,179.63300 103.99200,152.47900 103.99200,152.47400 C 103.99200,150.03900 102.01500,148.06700 99.577000,148.06700 C 99.574000,148.06700 99.571000,148.06700 99.566000,148.06700 L 79.045000,148.06700 C 71.395000,148.06700 65.214000,141.96400 65.214000,134.29100 C 65.212000,126.57500 71.459000,120.49700 79.190000,120.49700 L 103.98900,120.49700 L 103.98900,120.49600 z " style="fill:#ffffff" id="blue-inifity-connectors"/>
</g>
</svg>
18 years
example-tutorial/figs - New directory
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/example-tutorial/figs
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17121/figs
Log Message:
Directory /cvs/docs/example-tutorial/figs added to the repository
18 years
example-tutorial/en_US example-tutorial.xml,1.3,1.4
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/example-tutorial/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16813
Modified Files:
example-tutorial.xml
Log Message:
Show an example of using a per-document entity "&LOCAL-ENT;" to help
test the translation process.
Index: example-tutorial.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/en_US/example-tutorial.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- example-tutorial.xml 6 Mar 2006 02:14:10 -0000 1.3
+++ example-tutorial.xml 27 Apr 2006 20:24:51 -0000 1.4
@@ -16,10 +16,6 @@
<xi:fallback>WHERE IS MY FDP-INFO, DUDE</xi:fallback>
</xi:include>
- <para>
- This phrase uses the local entity &LOCAL-ENT;.
- </para>
-
<section id="sn-some-section">
<title>Some Section</title>
<indexterm>
@@ -39,6 +35,13 @@
</xi:fallback>
</xi:include>
<para>
+ This is how we can use an <filename>doc_entities.xml</filename>
+ file to define document-specific entities that can be referenced
+ from any XML file of the document using a
+ <wordasword>&LOCAL-ENT;</wordasword>: "&LOCAL-ENT;".
+ </para>
+
+ <para>
Keep text within the <command>title</command> tags on the same
line as the tags. Nesting the title on a separate line from the
enclosing tags results in extra spaces in HTML rendering.
@@ -166,6 +169,25 @@
</procedure>
</section>
+ <section id="sn-images">
+ <title>Using images</title>
+
+ <para>
+ FIXME
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="../figs/fedora-logo-sprite.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>FDP Logo</phrase>
+ </textobject>
+ </mediaobject>
+ <para>
+ FIXME
+ </para>
+ </section>
+
<index id="generated-index"></index>
</article>
18 years
example-tutorial/de para.xml,1.1,NONE
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/example-tutorial/de
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16567
Removed Files:
para.xml
Log Message:
Deleted from CVS what is now a generated file.
--- para.xml DELETED ---
18 years
example-tutorial Makefile,1.33,1.34
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16327
Modified Files:
Makefile
Log Message:
Changed "${DOCNAME}" to "${DOCBASE}" because we never had one.
Index: Makefile
===================================================================
RCS file: /cvs/docs/example-tutorial/Makefile,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- Makefile 2 Mar 2006 22:33:24 -0000 1.33
+++ Makefile 27 Apr 2006 20:22:28 -0000 1.34
@@ -44,6 +44,6 @@
# print the message "FINISHED AT LAST" after building
# the HTML document version, uncomment the following
# line:
-#${DOCNAME}/index.html::
+#${DOCBASE}/index.html::
# echo FINISHED AT LAST
########################################################################
18 years
docs-common Makefile.common,1.111,1.112
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15417
Modified Files:
Makefile.common
Log Message:
Removed the po/${DOC_ENTITIES}.pot rules.
Now, all translatable strings should be in the "po/${DOC_BASE}.pot" file.
If you have a "po/${DOC_ENTITIES}.pot" file, DELETE IT YOURSELF
because we will just ignore it from now on ;-)
Replaced the XML2PO "-k" (keep entities) switch with the "-e" (expand
all entities) because "-k" was the default behavior. Maybe we'll
like this better.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -r1.111 -r1.112
--- Makefile.common 24 Apr 2006 01:52:18 -0000 1.111
+++ Makefile.common 27 Apr 2006 20:20:27 -0000 1.112
@@ -63,6 +63,7 @@
HTMLCSS = ${FDPDIR}/docs-common/css/fedora-draft.css
endif
ifeq "${DRAFT}" ""
+#DRAFT = no
DRAFT = yes
endif
ifeq "${PRI_LANG}" ""
@@ -93,6 +94,7 @@
XMLFOPTS=-f $(FDPDIR)/docs-common/bin/xmlformat-fdp.conf
XMLLINT =xmllint
XML2PO =xml2po
+XML2POFLAGS=-e
MSGMERGE=msgmerge
LN =ln
MEINPROC=meinproc
@@ -105,9 +107,9 @@
#########################################################################
# Rules to produce .po files from .xml files. Get the tools to do this
# from the gnome-doc-utils RPM.
-.SUFFIXES: .po .pot .ent .xml
+.SUFFIXES: .po .pot .fo .ent .xml
%.po: %.xml
- ${XML2PO} -k $< >$@
+ ${XML2PO} ${XML2POFLAGS} $< >$@
%.ent: %.xml
${XSLTPROC} -o $@ --stringparam FDPCOMMONDIR "NONE" \
@@ -223,29 +225,30 @@
# Rules to generate the "${LANG}/${DOC_ENTITIES}.ent" file, if used
define DOC_ENTITIES_template
-po/${DOC_ENTITIES}.pot:: ${1}/${FDP_ENTITIES} ${PRI_LANG}/${DOC_ENTITIES}.xml
- ${XML2PO} -o $$@ -k ${PRI_LANG}/${DOC_ENTITIES}.xml
-clean::
- ${RM} po/${DOC_ENTITIES}.pot
-
-help::
- @printf ${TFMT} 'po/${DOC_ENTITIES}.pot' 'Create .POT file for per-doc entities'
-
-po/${1}.po:: ${1}/${FDP_ENTITIES} po/${DOC_ENTITIES}.pot
- if [ ! -f $$@ ]; then \
- mkdir -p ${1}; \
- cp -f po/${DOC_ENTITIES}.pot $$@; \
- fi
- ${MSGMERGE} -U -q $$@ po/${DOC_ENTITIES}.pot
- touch $$@
+#po/${DOC_ENTITIES}.pot:: ${1}/${FDP_ENTITIES} ${PRI_LANG}/${DOC_ENTITIES}.xml
+# ${XML2PO} -o $$@ ${XML2POFLAGS} ${PRI_LANG}/${DOC_ENTITIES}.xml
+#clean::
+# ${RM} po/${DOC_ENTITIES}.pot
+#
+#help::
+# @printf ${TFMT} 'po/${DOC_ENTITIES}.pot' 'Create .POT file for per-doc entities'
+
+#po/${1}.po:: ${1}/${FDP_ENTITIES} po/${DOC_ENTITIES}.pot
+# if [ ! -f $$@ ]; then \
+# mkdir -p ${1}; \
+# cp -f po/${DOC_ENTITIES}.pot $$@; \
+# fi
+# ${MSGMERGE} -U -q $$@ po/${DOC_ENTITIES}.pot
+# touch $$@
${1}/${DOC_ENTITIES}.xml:: ${1}/${FDP_ENTITIES} po/${1}.po ${PRI_LANG}/${DOC_ENTITIES}.xml
- ${XML2PO} -p po/${1}.po ${PRI_LANG}/${DOC_ENTITIES}.xml >$$@
+ ${XML2PO} ${XML2POFLAGS} -p po/${1}.po \
+ ${PRI_LANG}/${DOC_ENTITIES}.xml >$$@
clean::
${RM} ${1}/${DOC_ENTITIES}.xml
-# ${1}/${DOC_ENTITIES}.ent:: ${1}/${DOC_ENTITIES}.xml
+${1}/${DOC_ENTITIES}.ent:: ${1}/${DOC_ENTITIES}.xml
help::
@printf ${TFMT} '${1}/${DOC_ENTITIES}.ent' 'Per-doc entities for locale "${1}"'
@@ -265,12 +268,12 @@
#########################################################################
#########################################################################
-po/${DOCBASE}.pot:: ${DOC_ENTITIES_ENT-${PRI_LANG}} \
+po/${DOCBASE}.pot:: ${DOC_ENTITIES_XML-${PRI_LANG}} \
${PRI_LANG}/${FDP_ENTITIES} ${XMLFILES-${PRI_LANG}}
[ -d po/CVS ] || (echo ADD po/ TO CVS >&2; exit 1)
- ${XML2PO} -k -o $@ ${XMLFILES-${PRI_LANG}}
+ ${XML2PO} ${XML2POFLAGS} -o $@ ${XMLFILES-${PRI_LANG}} ${DOC_ENTITIES_XML-${PRI_LANG}}
help::
- @printf ${TFMT} 'po/${DOCBASE}.pot' 'Writes one PO file for all XML'
+ @printf ${TFMT} 'po/${DOCBASE}.pot' 'Writes one POT file for all XML'
.PHONY: pot
pot:: po/${DOCBASE}.pot
@@ -322,7 +325,7 @@
${DOC_ENTITIES_ENT-${1}}
mkdir -p ${1}
ln -s -f ../${2} $$@.in
- cd po && ${XML2PO} -e -p ${1}.po ../$$@.in >../$$@
+ cd po && ${XML2PO} ${XML2POFLAGS} -p ${1}.po ../$$@.in >../$$@
${RM} $$@.in
endef
@@ -386,7 +389,7 @@
mkdir -p $(DOCBASE)-$(1)/stylesheet-images/
cp ${FDPDIR}/docs-common/stylesheet-images/*.png $(DOCBASE)-$(1)/stylesheet-images
cp ${HTMLCSS} $(DOCBASE)-$(1)/fedora.css
-ifeq "${DRAFT}" "yes"
+ifneq "${DRAFT}" "no"
cp ${FDPDIR}/docs-common/images/watermark-$(1).png \
$(DOCBASE)-$(1)/watermark.png
endif
@@ -422,7 +425,7 @@
mkdir -p stylesheet-images/
cp ${FDPDIR}/docs-common/stylesheet-images/*.png stylesheet-images/
cp ${HTMLCSS} fedora.css
-ifeq "${DRAFT}" "yes"
+ifneq "${DRAFT}" "no"
cp ${FDPDIR}/docs-common/images/watermark-$(1).png watermark.png
endif
@@ -476,7 +479,9 @@
fo-${1}:: ${1}/${DOCBASE}.fo
${1}/${DOCBASE}.fo:: ${XMLFILES-${1}} ${XMLDEPFILES-${1}} set-locale-${1}
LANG=${1}.UTF-8 xsltproc --xinclude \
- --stringparam FDPDIR ${FDPDIR} \
+ --stringparam FDPDIR ${FDPDIR} \
+ --stringparam IMGROOT ${PWD} \
+ --stringparam RENDEREDBY fop-0.20.5 \
${XSLPDF} ${1}/${DOCBASE}.xml | ${XMLLINT} --format -o $$@ -
clean::
${RM} ${1}/${DOCBASE}.fo
18 years
selinux-faq/po it.po,1.1,1.2
by fedora-docs-commits@redhat.com
Author: tombo
Update of /cvs/docs/selinux-faq/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22843
Modified Files:
it.po
Log Message:
completed part two
Index: it.po
===================================================================
RCS file: /cvs/docs/selinux-faq/po/it.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- it.po 1 Apr 2006 13:27:15 -0000 1.1
+++ it.po 25 Apr 2006 20:33:31 -0000 1.2
@@ -3,14 +3,14 @@
msgid ""
msgstr ""
"Project-Id-Version: it\n"
-"POT-Creation-Date: 2006-03-31 19:26+0200\n"
-"PO-Revision-Date: 2006-04-01 15:09+0200\n"
+"POT-Creation-Date: 2006-04-12 07:28+0200\n"
+"PO-Revision-Date: 2006-04-25 22:32+0200\n"
"Last-Translator: Francesco Tombolini <tombo(a)adamantio.net>\n"
"Language-Team: Italiano <fedora-trans-it(a)redhat.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Generator: KBabel 1.11.1\n"
+"X-Generator: KBabel 1.11.2\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: en_US/selinux-faq.xml:16(fallback)
@@ -1087,11 +1087,12 @@
"information about &APACHE; and &SEL;, refer to <ulink url=\"http://fedora."
"redhat.com/docs/selinux-apache-fc3/\"/>."
msgstr ""
-"Questo processo presume che avete abilitato le directories HTML pubbliche per "
-"gli utenti nel file di configurazione di Apache, <filename>/etc/httpd/conf/httpd.conf</"
-"filename>. Questo processo concerne solo il servizio di contenuti Web statici. Per "
-"maggiori informazioni su &APACHE; e &SEL;, fate riferimento a <ulink url=\"http://fedora."
-"redhat.com/docs/selinux-apache-fc3/\"/>."
+"Questo processo presume che avete abilitato le directories HTML pubbliche "
+"per gli utenti nel file di configurazione di Apache, <filename>/etc/httpd/"
+"conf/httpd.conf</filename>. Questo processo concerne solo il servizio di "
+"contenuti Web statici. Per maggiori informazioni su &APACHE; e &SEL;, fate "
+"riferimento a <ulink url=\"http://fedora.redhat.com/docs/selinux-apache-fc3/"
+"\"/>."
#: en_US/selinux-faq.xml:876(para)
msgid ""
@@ -1122,13 +1123,13 @@
"context of the folder and its contents recursively using the <option>-R</"
"option> option:"
msgstr ""
-"A questo punto, <command>httpd</command> �� configurato per servire i contenuti, "
-"ma continuerete a ricevere un errore <computeroutput>403\n"
+"A questo punto, <command>httpd</command> �� configurato per servire i "
+"contenuti, ma continuerete a ricevere un errore <computeroutput>403\n"
"\t\t forbidden</computeroutput>. Questo poich�� ad <command>httpd</"
-"command> non �� consentito leggere il tipo di sicurezza per la directory ed "
-"i files che vengono creati nelle directory home degli utenti. Cambiate i contesti di "
-"sicurezza della cartella e dei suoi contenuti ricorsivamente usando l'opzione "
-"<option>-R</option>:"
+"command> non �� consentito leggere il tipo di sicurezza per la directory ed i "
+"files che vengono creati nelle directory home degli utenti. Cambiate i "
+"contesti di sicurezza della cartella e dei suoi contenuti ricorsivamente "
+"usando l'opzione <option>-R</option>:"
#: en_US/selinux-faq.xml:899(userinput)
#, no-wrap
@@ -1192,13 +1193,15 @@
"HTTPD to read home\n"
"\t\t directories</computeroutput>. The changes take effect immediately."
msgstr ""
-"Le vostre pagine statiche potranno ora essere servite correttamente. Se continuerete "
-"ad avere errori, controllate che la Booleana che abilita le home directories utente sia "
-"abilitata. Potete impostarla usando <command>system-config-securitylevel</"
-"command>. Selezionate il tab <guilabel>&SEL;</guilabel>, quindi selezionate l'area "
-"<guilabel>Modifica la Policy &SEL;</guilabel>. Selezionate <computeroutput>Permetti "
-"ad HTTPD di leggere le home\n"
-"\t\t directories</computeroutput>. I cambiamenti avranno effetto immediato."
+"Le vostre pagine statiche potranno ora essere servite correttamente. Se "
+"continuerete ad avere errori, controllate che la Booleana che abilita le "
+"home directories utente sia abilitata. Potete impostarla usando "
+"<command>system-config-securitylevel</command>. Selezionate il tab "
+"<guilabel>&SEL;</guilabel>, quindi selezionate l'area <guilabel>Modifica la "
+"Policy &SEL;</guilabel>. Selezionate <computeroutput>Permetti ad HTTPD di "
+"leggere le home\n"
+"\t\t directories</computeroutput>. I cambiamenti avranno effetto "
+"immediato."
#: en_US/selinux-faq.xml:935(para)
msgid "How do I turn &SEL; off at boot?"
@@ -1209,16 +1212,16 @@
"Set <computeroutput>SELINUX=disabled</computeroutput> in <filename>/etc/"
"selinux/config</filename>."
msgstr ""
-"Impostate <computeroutput>SELINUX=disabled</computeroutput> in <filename>/etc/"
-"selinux/config</filename>."
+"Impostate <computeroutput>SELINUX=disabled</computeroutput> in <filename>/"
+"etc/selinux/config</filename>."
#: en_US/selinux-faq.xml:944(para)
msgid ""
"Alternatively, you can add <option>selinux=0</option> to your kernel boot "
"parameters. However, this option is not recommended."
msgstr ""
-"In alternativa, potete aggiungere <option>selinux=0</option> ai parametri del "
-"kernel. Comunque questa opzione non �� raccomandata."
+"In alternativa, potete aggiungere <option>selinux=0</option> ai parametri "
+"del kernel. Comunque questa opzione non �� raccomandata."
#: en_US/selinux-faq.xml:949(title)
msgid "Be careful when disabling &SEL;"
@@ -1234,11 +1237,11 @@
"parameters."
msgstr ""
"Se avviate con <option>selinux=0</option>, qualsiasi file creato mentre "
-"&SEL; �� disabilitato non ha le informazioni di contesto &SEL;. Il file system �� "
-"segnato per la rietichettatura al prossimo avvio. Se un problema imprevisto vi "
-"impedisce di riavviare normalmente, potreste aver bisogno di avviare in modalit�� "
-"single-user per il ripristino. Aggiungete l'opzione <option>emergency</option> ai "
-"parametri di avvio del kernel."
+"&SEL; �� disabilitato non ha le informazioni di contesto &SEL;. Il file "
+"system �� segnato per la rietichettatura al prossimo avvio. Se un problema "
+"imprevisto vi impedisce di riavviare normalmente, potreste aver bisogno di "
+"avviare in modalit�� single-user per il ripristino. Aggiungete l'opzione "
+"<option>emergency</option> ai parametri di avvio del kernel."
#: en_US/selinux-faq.xml:964(para)
msgid "How do I turn enforcing on/off at boot?"
@@ -1249,8 +1252,8 @@
"You can specify the &SEL; mode using the configuration file <filename>/etc/"
"sysconfig/selinux</filename>."
msgstr ""
-"Potete specificare la modalit�� &SEL; usando il file di configurazione <filename>/etc/"
-"sysconfig/selinux</filename>."
+"Potete specificare la modalit�� &SEL; usando il file di configurazione "
+"<filename>/etc/sysconfig/selinux</filename>."
#: en_US/selinux-faq.xml:974(computeroutput)
#, no-wrap
@@ -1321,10 +1324,11 @@
"computeroutput> setting instead turns enforcing off and skips loading a "
"policy."
msgstr ""
-"Comunque, impostare il valore a <computeroutput>disabled</computeroutput> non "
-"�� lo stesso di <option>selinux=0</option> nei parametri di avvio del kernel. Invece "
-"di disabilitare pienamente &SEL; nel kernel, l'impostazione <computeroutput>disabled</"
-"computeroutput> disattiva l'enforcing e salta il caricamento della policy. "
+"Comunque, impostare il valore a <computeroutput>disabled</computeroutput> "
+"non �� lo stesso di <option>selinux=0</option> nei parametri di avvio del "
+"kernel. Invece di disabilitare pienamente &SEL; nel kernel, l'impostazione "
+"<computeroutput>disabled</computeroutput> disattiva l'enforcing e salta il "
+"caricamento della policy. "
#: en_US/selinux-faq.xml:1001(title)
msgid "&SEL; Configuration Precedence"
@@ -1332,11 +1336,15 @@
#: en_US/selinux-faq.xml:1002(para)
msgid "The command line kernel parameter overrides the configuration file."
-msgstr "I parametri della linea di comando del kernel prevaricano il file di configurazione."
+msgstr ""
+"I parametri della linea di comando del kernel prevaricano il file di "
+"configurazione."
#: en_US/selinux-faq.xml:1011(para)
msgid "How do I temporarily turn off enforcing mode without having to reboot?"
-msgstr "Come disabilito temporaneamente la modalit�� di enforcing senza dover riavviare?"
+msgstr ""
+"Come disabilito temporaneamente la modalit�� di enforcing senza dover "
+"riavviare?"
#: en_US/selinux-faq.xml:1017(para)
msgid ""
@@ -1345,14 +1353,17 @@
"enforcing mode in real time. When you are finished, run <command>setenforce "
"1</command> to turn enforcing back on."
msgstr ""
-"Occasionalmente potreste aver necessit�� di eseguire un operazione non permessa dalla "
-"policy. Eseguite il comando <command>setenforce 0</command> per disabilitare la "
-"modalit�� di enforcing in tempo reale. Quando avete terminato, eseguite <command>setenforce "
-"1</command> per riattivare l'enforcing."
+"Occasionalmente potreste aver necessit�� di eseguire un operazione non "
+"permessa dalla policy. Eseguite il comando <command>setenforce 0</command> "
+"per disabilitare la modalit�� di enforcing in tempo reale. Quando avete "
+"terminato, eseguite <command>setenforce 1</command> per riattivare "
+"l'enforcing."
#: en_US/selinux-faq.xml:1025(title)
msgid "<computeroutput>sysadm_r</computeroutput> Role Required for strict policy"
-msgstr "Il ruolo <computeroutput>sysadm_r</computeroutput> �� necessario per la policy strict"
+msgstr ""
+"Il ruolo <computeroutput>sysadm_r</computeroutput> �� necessario per la "
+"policy strict"
#: en_US/selinux-faq.xml:1027(para)
msgid ""
@@ -1362,9 +1373,9 @@
"necessary. Use the <command>newrole</command> command to assume this role."
msgstr ""
"Dovete lanciare il comando <command>setenforce</command> con il ruolo "
-"<computeroutput>sysadm_r</computeroutput> se state usando la policy "
-"strict. Se state usando la policy targeted standard, allora non �� necessario. "
-"Usate il comando <command>newrole</command> per assumere questo ruolo."
+"<computeroutput>sysadm_r</computeroutput> se state usando la policy strict. "
+"Se state usando la policy targeted standard, allora non �� necessario. Usate "
+"il comando <command>newrole</command> per assumere questo ruolo."
#: en_US/selinux-faq.xml:1039(para)
msgid "How do I turn system call auditing on/off at boot?"
@@ -1376,9 +1387,10 @@
"auditing on. Add <option>audit=0</option> to your kernel command line to "
"turn system call auditing off."
msgstr ""
-"Aggiungete <option>audit=1</option> alla linea di comando del kernel per attivare "
-"l'auditing delle chiamate di sistema. Aggiungete <option>audit=0</option> alla linea di "
-"comando del kernel per disattivare l'auditing delle chiamate di sistema."
+"Aggiungete <option>audit=1</option> alla linea di comando del kernel per "
+"attivare l'auditing delle chiamate di sistema. Aggiungete <option>audit=0</"
+"option> alla linea di comando del kernel per disattivare l'auditing delle "
+"chiamate di sistema."
#: en_US/selinux-faq.xml:1049(para)
msgid ""
@@ -1387,22 +1399,25 @@
"generated a <computeroutput>denied</computeroutput> message. The error "
"message is helpful when debugging policy."
msgstr ""
-"L'auditing delle chiamate di sistema �� <emphasis>on</emphasis> per impostazione "
-"predefinita. Quando �� attivo, fornisce informazioni sulle chiamate di sistema che erano in "
-"esecuzione quando &SEL; ha generato un messaggio <computeroutput>denied</computeroutput>. "
-"Il messaggio d'errore �� d'aiuto quando si esegue il debugging della policy."
+"L'auditing delle chiamate di sistema �� <emphasis>on</emphasis> per "
+"impostazione predefinita. Quando �� attivo, fornisce informazioni sulle "
+"chiamate di sistema che erano in esecuzione quando &SEL; ha generato un "
+"messaggio <computeroutput>denied</computeroutput>. Il messaggio d'errore �� "
+"d'aiuto quando si esegue il debugging della policy."
#: en_US/selinux-faq.xml:1060(para)
msgid "How do I temporarily turn off system-call auditing without having to reboot?"
-msgstr "Come disabilito temporaneamente l'auditing alle system-call senza dover riavviare?"
+msgstr ""
+"Come disabilito temporaneamente l'auditing alle system-call senza dover "
+"riavviare?"
#: en_US/selinux-faq.xml:1066(para)
msgid ""
"Run <command>auditctl -e 0</command>. Note that this command does not affect "
"auditing of SELinux AVC denials."
msgstr ""
-"Per farlo, eseguite <command>auditctl -e 0</command>. Notate che questo comando non "
-"avr�� effetto sull'auditing dei dinieghi &SEL; AVC."
+"Per farlo, eseguite <command>auditctl -e 0</command>. Notate che questo "
+"comando non avr�� effetto sull'auditing dei dinieghi &SEL; AVC."
#: en_US/selinux-faq.xml:1074(para)
msgid "How do I get status info about my &SEL; installation?"
@@ -1414,7 +1429,8 @@
"more information, refer to the <filename>sestatus(8)</filename> manual page."
msgstr ""
"Come root, eseguite il comando <command>/usr/sbin/sestatus -v</command>. Per "
-"maggiori informazioni, fate riferimento alla pagina di manuale di <filename>sestatus(8)</filename>."
+"maggiori informazioni, fate riferimento alla pagina di manuale di "
+"<filename>sestatus(8)</filename>."
#: en_US/selinux-faq.xml:1088(para)
msgid "How do I write policy to allow a domain to use pam_unix.so?"
@@ -1426,9 +1442,9 @@
"shadow</filename> file. There are constraint rules that prevent policy "
"writers from writing code like"
msgstr ""
-"A pochissimi domini nel mondo &SEL; �� permesso di leggere il file <filename>/etc/"
-"shadow</filename>. Ci sono delle regole restrittive che prevengono gli scrittori di policy "
-"dallo scrivere codice come"
+"A pochissimi domini nel mondo &SEL; �� permesso di leggere il file <filename>/"
+"etc/shadow</filename>. Ci sono delle regole restrittive che prevengono gli "
+"scrittori di policy dallo scrivere codice come"
#: en_US/selinux-faq.xml:1099(command)
msgid "allow mydomain_t shadow_t:file read;"
@@ -1441,10 +1457,10 @@
"attribute. So if you were writing policy for an ftpd daemon you would write "
"something like"
msgstr ""
-"In RHEL4 potete impostare il vostro dominio per usare il comando <command>unix_chkpwd"
-"</command>. Il modo pi�� semplice �� usare l'attributo <command>unix_chkpwd</command>. "
-"Cos�� se state scrivendo una policy per un demone ftpd dovrete scrivere "
-"qualcosa come"
+"In RHEL4 potete impostare il vostro dominio per usare il comando "
+"<command>unix_chkpwd</command>. Il modo pi�� semplice �� usare l'attributo "
+"<command>unix_chkpwd</command>. Cos�� se state scrivendo una policy per un "
+"demone ftpd dovrete scrivere qualcosa come"
#: en_US/selinux-faq.xml:1108(command)
msgid "daemon_domain(vsftpd, `auth_chkpwd')"
@@ -1456,30 +1472,39 @@
"system_chkpwd_t which can read <filename>/etc/shadow</filename>, while "
"vsftpd_t is not able to read it."
msgstr ""
+"Questo creer�� un contesto dove vsftpd_t -> chkpwd_exec_t -> "
+"system_chkpwd_t potr�� leggere <filename>/etc/shadow</filename>, mentre "
+"vsftpd_t non sar�� capace di leggerlo."
#: en_US/selinux-faq.xml:1116(para)
msgid "In &FC;&LOCALVER;/RHEL5, add the rule"
-msgstr ""
+msgstr "In &FC;&LOCALVER;/RHEL5, aggiungete la regola"
#: en_US/selinux-faq.xml:1120(command)
msgid "auth_domtrans_chk_passwd(vsftpd_t)"
-msgstr ""
+msgstr "auth_domtrans_chk_passwd(vsftpd_t)"
#: en_US/selinux-faq.xml:1126(para)
msgid ""
"In the past I have written local.te file in policy sources for my own local "
"customization to policy, how do I do this with Reference Policy?"
msgstr ""
+"In passato ho scritto il file local.te nei sorgenti della policy per la mia "
+"locale personalizzazione della policy, come lo far�� con la nuova Reference "
+"Policy?"
#: en_US/selinux-faq.xml:1133(para)
msgid ""
"If you have specific AVC messages you can use <command>audit2allow</command> "
"to generate a Type Enforcement file that is ready to load as a policy module."
msgstr ""
+"Se avete specifici messaggi AVC potete usare <command>audit2allow</command> "
+"per generare un file Type Enforcement che sia pronto ad essere caricato come "
+"modulo della policy."
#: en_US/selinux-faq.xml:1140(command)
msgid "audit2allow -M local < /tmp/avcs"
-msgstr ""
+msgstr "audit2allow -M local < /tmp/avcs"
#: en_US/selinux-faq.xml:1142(para)
msgid ""
@@ -1487,6 +1512,9 @@
"the kernel using <command>semodule -i local.pp</command>. You can also edit "
"the <filename>local.te</filename> to make additional customizations."
msgstr ""
+"Questo crea un <filename>local.pp</filename> che potrete caricare nel kernel "
+"usando <command>semodule -i local.pp</command>. Potete anche editare il "
+"<filename>local.te</filename> per eseguire ulteriori personalizzazioni."
#: en_US/selinux-faq.xml:1150(computeroutput)
#, no-wrap
@@ -1504,6 +1532,18 @@
"\n"
"semodule -i local.pp"
msgstr ""
+"audit2allow -M local -l -i /var/log/messages\n"
+"Generating type enforcement file: local.te\n"
+"Compiling policy\n"
+"checkmodule -M -m -o local.mod local.te\n"
+"semodule_package -o local.pp -m local.mod\n"
+"\n"
+"******************** IMPORTANT ***********************\n"
+"\n"
+"In order to load this newly created policy package into the kernel,\n"
+"you are required to execute\n"
+"\n"
+"semodule -i local.pp"
#: en_US/selinux-faq.xml:1163(para)
msgid ""
@@ -1513,6 +1553,11 @@
"file. This generates a <filename>local.te</filename> file, that looks "
"similar to the following:"
msgstr ""
+"Notate che quanto riportato sopra assume che voi non stiate usando il demone "
+"audit. Se state usando il demone audit, allora dovete usare <filename>/var/"
+"log/audit/audit.log</filename> invece di <filename>/var/log/messages</"
+"filename> come vostro file di log. Questo genera un file <filename>local.te</"
+"filename>, che �� simile al seguente:"
#: en_US/selinux-faq.xml:1172(computeroutput)
#, no-wrap
@@ -1528,38 +1573,54 @@
"\n"
"allow httpd_t httpd_w3c_script_exec_t:file { execute execute_no_trans getattr ioctl read };"
msgstr ""
+"module local 1.0;\n"
+"\n"
+"require {\n"
+" class file { append execute execute_no_trans getattr ioctl read write };\n"
+" type httpd_t;\n"
+" type httpd_w3c_script_exec_t;\n"
+" };\n"
+"\n"
+"\n"
+"allow httpd_t httpd_w3c_script_exec_t:file { execute execute_no_trans getattr ioctl read };"
#: en_US/selinux-faq.xml:1183(para)
msgid "You can hand edit this file and then recompile and reload it using"
-msgstr ""
+msgstr "Potete editare a mano questo file e poi ricompilarlo usando"
#: en_US/selinux-faq.xml:1189(para)
msgid "<command>checkmodule</command> to compile the te file"
-msgstr ""
+msgstr "<command>checkmodule</command> per compilare il file"
#: en_US/selinux-faq.xml:1194(para)
msgid "<command>semodule_package</command> to create a policy package"
-msgstr ""
+msgstr "<command>semodule_package</command> per creare un pacchetto di policy"
#: en_US/selinux-faq.xml:1199(para)
msgid "<command>semodule</command> to add it to the current machines running policy"
msgstr ""
+"<command>semodule</command> per aggiungerlo alla macchina che sta eseguendo "
+"la policy corrente"
#: en_US/selinux-faq.xml:1205(title)
msgid "Important"
-msgstr ""
+msgstr "Importante"
#: en_US/selinux-faq.xml:1206(para)
msgid ""
"In order to load this newly created policy package into the kernel, you are "
"required to execute <command>semodule -i local.pp</command>"
msgstr ""
+"Per poter caricare questo pacchetto di policy appena creato nel kernel, "
+"dovrete necessariamente eseguire <command>semodule -i local.pp</command>"
#: en_US/selinux-faq.xml:1216(para)
msgid ""
"I created a new Policy Package, where do I put it to make sure that it gets "
"loaded into the kernel?"
msgstr ""
+"Ho creato un nuovo pacchetto di policy, dove devo metterlo per essere sicuro "
+"che verr�� caricato nel kernel?"
#: en_US/selinux-faq.xml:1222(para)
msgid ""
@@ -1568,10 +1629,14 @@
"now is loaded with the rest of the policy. You can even remove the pp file "
"from the system."
msgstr ""
+"Dovete eseguire il comando <command>semodule -i myapp.pp</command>. Questo "
+"modifica la policy registrata sulla vostra macchina. Il vostro modulo di "
+"policy �� ora caricato con il resto della policy. Potete anche rimuovere il "
+"file pp dal sistema."
#: en_US/selinux-faq.xml:1228(para)
msgid "<command>semodule -l</command> lists the currently loaded modules."
-msgstr ""
+msgstr "<command>semodule -l</command> elenca i moduli attualmente caricati."
#: en_US/selinux-faq.xml:1233(computeroutput)
#, no-wrap
@@ -1579,28 +1644,37 @@
"#semodule -i \n"
"myapp 1.2.1"
msgstr ""
+"#semodule -i \n"
+"myapp 1.2.1"
#: en_US/selinux-faq.xml:1236(para)
msgid ""
"If you later would like to remove the policy package, you can execute "
"<command>semodule -r myapp</command>."
msgstr ""
+"Se successivamente volete rimuovere il pacchetto della policy, potete "
+"eseguire <command>semodule -r myapp</command>."
#: en_US/selinux-faq.xml:1244(title)
msgid "Resolving Problems"
-msgstr ""
+msgstr "Risolvere i problemi"
#: en_US/selinux-faq.xml:1247(para)
msgid ""
"My application isn't working as expected and I am seeing "
"<computeroutput>avc: denied</computeroutput> messages. How do I fix this?"
msgstr ""
+"La mia applicazione non funziona come mi aspetto e sto vedendo messaggi "
+"<computeroutput>avc: denied</computeroutput>. Come risolvo?"
#: en_US/selinux-faq.xml:1254(para)
msgid ""
"This message means that the current SELinux policy is not allowing the "
"application to do something. There are a number of reasons this could happen."
msgstr ""
+"Questo messaggio significa che la policy SELinux attuale non permette "
+"all'applicazione di fare qualcosa. Ci sono un certo numero di ragioni per "
+"cui ci�� pu�� accadere."
#: en_US/selinux-faq.xml:1259(para)
msgid ""
@@ -1614,6 +1688,16 @@
"or run <command>restorecon -R <replaceable>/path</replaceable></command> to "
"recursively relabel a directory path."
msgstr ""
+"Primo, uno dei files a cui l'applicazione prova ad accedere potrebbe essere "
+"etichettato male. Se il messaggio AVC si riferisce ad un file specifico, "
+"controllate la sua etichetta corrente con <command>ls -alZ <replaceable>/"
+"path/to/file</replaceable></command>. Se vi sembra sbagliata, potrete "
+"provare ad usare <command>restorecon -v <replaceable>/path/to/file</"
+"replaceable></command> per ripristinare il contesto predefinito del file. Se "
+"avete un gran numero di dinieghi relativi a files, potreste voler usare "
+"<command>fixfiles relabel</command>, o eseguire <command>restorecon -R "
+"<replaceable>/path</replaceable></command> per rietichettare recursivamente "
+"il percorso di una directory."
#: en_US/selinux-faq.xml:1272(para)
msgid ""
@@ -1623,6 +1707,12 @@
"<filename>apache.te</filename>. Refer to <xref linkend=\"external-link-list"
"\"/> for more information about writing policy."
msgstr ""
+"Delle volte, i dinieghi sono causati da un cambiamento nella configurazione "
+"del programma che fa scattare il messaggio di diniego. Per esempio, se "
+"volete che Apache ascolti anche sulla porta 8800, dovrete cambiare anche la "
+"policy di sicurezza, <filename>apache.te</filename>. Fate riferimento a "
+"<xref linkend=\"external-link-list\"/> per maggiori informazioni sulla "
+"scrittura delle policy."
#: en_US/selinux-faq.xml:1280(para)
msgid ""
@@ -1630,42 +1720,54 @@
"work, refer to <xref linkend=\"qa-using-s-c-securitylevel\"/> for "
"information on disabling enforcement just for that application."
msgstr ""
+"Se avete difficolt�� nel far funzionare un'applicazione specifica come "
+"Apache, fate riferimento a <xref linkend=\"qa-using-s-c-securitylevel\"/> "
+"per sapere come disabilitare l'enforcement solo per quell'applicazione."
#: en_US/selinux-faq.xml:1312(para)
msgid ""
"I installed &FC; on a system with an existing <filename>/home</filename> "
"partition, and now I can't log in."
msgstr ""
+"Ho installato Fedora Core su un sistema con una partizione <filename>/home</"
+"filename> gi�� esistente, ed ora non posso fare il log in."
#: en_US/selinux-faq.xml:1318(para)
msgid ""
"Your <filename>/home</filename> partition is not labeled correctly. You can "
"easily fix this two different ways."
msgstr ""
+"La vostra partizione <filename>/home</filename> non �� etichettata "
+"correttamente. Potete facilmente risolvere questo problema in due modi "
+"differenti."
#: en_US/selinux-faq.xml:1322(para)
msgid "If you just want to relabel <filename>/home</filename> recursively:"
-msgstr ""
+msgstr "Se volete solamente rietichettare <filename>/home</filename> ricorsivamente:"
#: en_US/selinux-faq.xml:1327(command)
msgid "/sbin/restorecon -v -R /home"
-msgstr ""
+msgstr "/sbin/restorecon -v -R /home"
#: en_US/selinux-faq.xml:1329(para)
msgid ""
"If you want to be sure there are no other files incorrectly labeled, you can "
"relabel the entire file system:"
msgstr ""
+"Se volete essere sicuri che non ci siano altri files non correttamente "
+"etichettati, potete rietichettare l'intero filesystem:"
#: en_US/selinux-faq.xml:1334(command)
msgid "/sbin/fixfiles relabel"
-msgstr ""
+msgstr "/sbin/fixfiles relabel"
#: en_US/selinux-faq.xml:1336(para)
msgid ""
"You must have the <filename>policycoreutils</filename> package installed to "
"use <command>fixfiles</command>."
msgstr ""
+"Dovrete avere installato il pacchetto <filename>policycoreutils</filename> "
+"per usare <command>fixfiles</command>."
#: en_US/selinux-faq.xml:1344(para)
msgid ""
@@ -1673,6 +1775,10 @@
"command> or <command>fixfiles</command>, am I still be able to read "
"<filename>/home</filename> with a non-&SEL;-enabled system?"
msgstr ""
+"Dopo aver rietichettato la mia <filename>/home</filename> usando "
+"<command>setfiles</command> o <command>fixfiles</command>, sar�� ancora in "
+"grado di leggere <filename>/home</filename> con un sistema con &SEL; non "
+"abilitato?"
#: en_US/selinux-faq.xml:1352(para)
msgid ""
@@ -1683,16 +1789,24 @@
"may have to relabel <filename>/home</filename> when you reboot the &SEL; "
"enabled &FC; system."
msgstr ""
+"Potete leggere i files da una distribuzione senza &SEL; o una con &SEL; "
+"disabilitato. Comunque, i files creati dal sistema privo di &SEL; non "
+"avranno un contesto di sicurezza, nemmeno l'avr�� qualsiasi files che "
+"rimuoverai e ricreerai. Questo potrebbe essere un problema con files tipo "
+"<filename>~/.bashrc</filename>. Dovrete rietichettare la <filename>/home</"
+"filename> quando riavvierete il sistema &FC; con &SEL; abilitato."
#: en_US/selinux-faq.xml:1365(para)
msgid "How do I share directories using NFS between &FC; and non-&SEL; systems?"
-msgstr ""
+msgstr "Come posso condividere directories usando NFS tra &FC; e sistemi non-&SEL;?"
#: en_US/selinux-faq.xml:1371(para)
msgid ""
"Just as NFS transparently supports many file system types, it can be used to "
"share directories between &SEL; and non-&SEL; systems."
msgstr ""
+"NFS supporta in modo trasparente molti tipi di file system, e pu�� essere "
+"usato per condividere directories tra sistemi &SEL; e non-&SEL;."
#: en_US/selinux-faq.xml:1375(para)
msgid ""
@@ -1703,10 +1817,17 @@
"makes the files in the NFS mounted directory appear to have a context of "
"<computeroutput>system_u:object_r:tmp_t</computeroutput> to &SEL;:"
msgstr ""
+"Quando montate un file system non-&SEL; via NFS, per impostazione "
+"predefinita &SEL; tratter�� tutti i files nella condivisione come avessero "
+"contesto <computeroutput>nfs_t</computeroutput>. Potrete prevaricare il "
+"contesto predefinito impostandolo manualmente usando l'opzione "
+"<option>context=</option>. Il seguente comando far�� apparire i files nella "
+"directory NFS montata con un contesto di <computeroutput>system_u:object_r:"
+"tmp_t</computeroutput> in &SEL;:"
#: en_US/selinux-faq.xml:1385(command)
msgid "mount -t nfs -o context=system_u:object_r:tmp_t server:/shared/foo /mnt/foo"
-msgstr ""
+msgstr "mount -t nfs -o context=system_u:object_r:tmp_t server:/shared/foo /mnt/foo"
#: en_US/selinux-faq.xml:1388(para)
msgid ""
@@ -1715,12 +1836,18 @@
"of &SEL; on the remote mounting system has no effect on the local security "
"contexts."
msgstr ""
+"Quando &SEL; esporta un file system via NFS, i files creati avranno il "
+"contesto della directory dove sono stati creati. In altre parole, la "
+"presenza di &SEL; sul sistema remoto che ha montato la condivisione non ha "
+"effetto sui contesti di sicurezza locali."
#: en_US/selinux-faq.xml:1398(para)
msgid ""
"How can I create a new Linux user account with the user's home directory "
"having the proper context?"
msgstr ""
+"Come posso creare un nuovo account utente Linux con la home directory utente "
+"avente il contesto appropriato?"
#. wtf was I trying to say here?
#. <para>
@@ -1734,17 +1861,23 @@
"systemitem>. Under the strict policy you need to change role to "
"<computeroutput>sysadm_r</computeroutput> with the following command:"
msgstr ""
+"Potete creare il nuovo utente con il comando standard <command>useradd</"
+"command>. Prima dovrete diventare <systemitem class=\"username\">root</"
+"systemitem>. Sotto la policy strict avrete bisogno di cambiare al ruolo "
+"<computeroutput>sysadm_r</computeroutput> con il seguente comando:"
#: en_US/selinux-faq.xml:1419(userinput)
#, no-wrap
msgid "newrole -r sysadm_r"
-msgstr ""
+msgstr "newrole -r sysadm_r"
#: en_US/selinux-faq.xml:1421(para)
msgid ""
"For the targeted policy you do not need to switch roles, staying in "
"<computeroutput>unconfined_t</computeroutput>:"
msgstr ""
+"Per la policy targeted non avrete bisogno di cambiare ruolo, rimanendo in "
+"<computeroutput>unconfined_t</computeroutput>:"
#: en_US/selinux-faq.xml:1427(userinput)
#, no-wrap
@@ -1752,11 +1885,13 @@
"su - root\n"
"id -Z"
msgstr ""
+"su - root\n"
+"id -Z"
#: en_US/selinux-faq.xml:1429(computeroutput)
#, no-wrap
msgid "root:system_r:unconfined_t"
-msgstr ""
+msgstr "root:system_r:unconfined_t"
#: en_US/selinux-faq.xml:1430(userinput)
#, no-wrap
@@ -1764,11 +1899,13 @@
"useradd auser\n"
"ls -Z /home"
msgstr ""
+"useradd auser\n"
+"ls -Z /home"
#: en_US/selinux-faq.xml:1432(computeroutput)
#, no-wrap
msgid "drwx------ auser auser root:object_r:user_home_dir_t /home/auser"
-msgstr ""
+msgstr "drwx------ auser auser root:object_r:user_home_dir_t /home/auser"
#: en_US/selinux-faq.xml:1434(para)
msgid ""
@@ -1778,23 +1915,33 @@
"These are functionally the same since the role and type are identical "
"(<computeroutput>object_r:user_home_dir_t</computeroutput>.)"
msgstr ""
+"Il contesto iniziale per una nuova directory utente ha un identit�� di "
+"<computeroutput>root</computeroutput>. In seguito la rietichettatura del "
+"file system cambier�� l'identit�� a <computeroutput>system_u</computeroutput>. "
+"Queste sono funzionalmente le stesse poich�� il ruolo ed il tipo sono "
+"identici (<computeroutput>object_r:user_home_dir_t</computeroutput>.)"
#: en_US/selinux-faq.xml:1475(para)
msgid ""
"I'm having troubles with <command>avc</command> errors filling my logs for a "
"particular program. How do I choose not to audit the access for it?"
msgstr ""
+"Sto avendo alcune difficolt�� con errori <command>avc</command> che riempiono "
+"i miei logs per un programma in particolare. Come scelgo escluderne l'audit "
+"d'accesso?"
#: en_US/selinux-faq.xml:1482(para)
msgid ""
"If you wanted to not audit <command>dmesg</command>, for example, you would "
"put this in your <filename>dmesg.te</filename> file:"
msgstr ""
+"Per esempio, se volevate escludere l'audit di <command>dmesg</command>, "
+"potreste inserire questo nel vostro file <filename>dmesg.te</filename>:"
#: en_US/selinux-faq.xml:1489(userinput)
#, no-wrap
msgid "dontaudit dmesg_t userdomain:fd { use };"
-msgstr ""
+msgstr "dontaudit dmesg_t userdomain:fd { use };"
#: en_US/selinux-faq.xml:1491(para)
msgid ""
@@ -1802,12 +1949,17 @@
"including <varname>user</varname>, <varname>staff</varname> and "
"<varname>sysadm</varname>."
msgstr ""
+"Questo eliminer�� l'output dell'errore dal terminale per tutti i domini "
+"utente, inclusi <varname>user</varname>, <varname>staff</varname> e "
+"<varname>sysadm</varname>."
#: en_US/selinux-faq.xml:1500(para)
msgid ""
"Even running in permissive mode, I'm getting a large number of "
"<computeroutput>avc denied</computeroutput> messages."
msgstr ""
+"Anche avviando in modalit�� permissive, ho un gran numero di messaggi "
+"<computeroutput>avc denied</computeroutput>."
#: en_US/selinux-faq.xml:1506(para)
msgid ""
@@ -1817,6 +1969,10 @@
"policy enforcement, you can perform more actions, which results in more "
"denials being logged."
msgstr ""
+"In modalit�� non-enforcing, riceverete <emphasis>pi��</emphasis> messaggi che "
+"in modalit�� enforcing. Il kernel logga ogni diniego di accesso come foste in "
+"modalit�� enforcing. Siccome non siete ristretti dalla forzosit�� della "
+"policy, potete fare pi�� azioni, che risultano in maggiori log di diniego."
#: en_US/selinux-faq.xml:1513(para)
msgid ""
@@ -1826,6 +1982,11 @@
"traversing the directory tree, and generates a denial message for each file "
"read in the directory."
msgstr ""
+"Se un applicazione eseguita in modalit�� enforcing ha il divieto di leggere "
+"un certo numero di files in una directory, essa verr�� fermata una volta "
+"cominciata l'azione. In modalit�� non-enforcing, l'applicazione non viene "
+"fermata dal traversare l'albero della directory, e generer�� un messaggio di "
+"diniego per ogni file letto nella directory."
#: en_US/selinux-faq.xml:1525(para)
msgid ""
@@ -1834,6 +1995,11 @@
"<filename>/var/log/audit/audit.log</filename> if using the audit daemon). "
"How can I identify the cause of these silent denials?"
msgstr ""
+"Ho uno specifico diniego di permesso solo quando &SEL; �� in modalit�� "
+"enforcing, ma non vedo alcun messaggio audit in <filename>/var/log/messages</"
+"filename> (o <filename>/var/log/audit/audit.log</filename> se usato il "
+"demone audit). Come posso identificare la causa di questi dinieghi "
+"silenziosi?"
#: en_US/selinux-faq.xml:1535(para)
msgid ""
@@ -1842,20 +2008,27 @@
"messages. The <computeroutput>dontaudit</computeroutput> rule is often used "
"this way when a benign denial is filling the audit logs."
msgstr ""
+"La ragione pi�� comune per un diniego silenzioso �� quando la policy contiene "
+"una regola esplicita <computeroutput>dontaudit</computeroutput> per "
+"sopprimere i messaggi audit. La regola <computeroutput>dontaudit</"
+"computeroutput> �� spesso usata in questo modo quando un diniego benigno sta "
+"riempiendo i log di audit."
#: en_US/selinux-faq.xml:1542(para)
msgid ""
"To look for your particular denial, enable auditing of all "
"<computeroutput>dontaudit</computeroutput> rules:"
msgstr ""
+"Per cercare il tuo particolare diniego, abilitate l'auditing di tutte le "
+"regole <computeroutput>dontaudit</computeroutput>:"
#: en_US/selinux-faq.xml:1547(command)
msgid "semodule -b /usr/share/selinux/targeted/enableaudit.pp"
-msgstr ""
+msgstr "semodule -b /usr/share/selinux/targeted/enableaudit.pp"
#: en_US/selinux-faq.xml:1550(title)
msgid "Enabled <computeroutput>dontaudit</computeroutput> output is verbose"
-msgstr ""
+msgstr "Abilitato <computeroutput>dontaudit</computeroutput> l'output �� verboso"
#: en_US/selinux-faq.xml:1552(para)
msgid ""
@@ -1863,6 +2036,9 @@
"likely produce a large amount of audit information, most of which is "
"irrelevant to your denial."
msgstr ""
+"Abilitando l'auditing di tutte le regole <computeroutput>dontaudit</"
+"computeroutput> produrr�� un gran numero di informazioni di audit, gran parte "
+"delle quali �� irrilevante per il tuo diniego."
#: en_US/selinux-faq.xml:1558(para)
msgid ""
@@ -1870,22 +2046,30 @@
"for a denial that seems to occur silently. You want to re-enable "
"<computeroutput>dontaudit</computeroutput> rules as soon as possible."
msgstr ""
+"Usate questa tecnica solo se state cercando specificatamente un messaggio "
+"audit per un diniego che sembra avvenire silenziosamente. Dovete ri-"
+"abilitare le regole <computeroutput>dontaudit</computeroutput> al pi�� presto "
+"possibile."
#: en_US/selinux-faq.xml:1566(para)
msgid ""
"Once you have found your problem you can reset to the default mode by "
"executing"
msgstr ""
+"Una volta trovato il vostro problema potrete resettare alle impostazioni "
+"predefinite eseguendo"
#: en_US/selinux-faq.xml:1571(command)
msgid "semodule -b /usr/share/selinux/targeted/base.pp"
-msgstr ""
+msgstr "semodule -b /usr/share/selinux/targeted/base.pp"
#: en_US/selinux-faq.xml:1601(para)
msgid ""
"Why do I not see the output when I run certain daemons in debug or "
"interactive mode?"
msgstr ""
+"Perch�� non vedo l'output quando eseguo certi demoni in modalit�� debug o "
+"interattiva?"
#: en_US/selinux-faq.xml:1607(para)
msgid ""
@@ -1895,16 +2079,23 @@
"controlling terminal. A broken or compromised program could use this hole to "
"cause serious problems."
msgstr ""
+"&SEL; disabilita intenzionalmente l'accesso ai dispositivi tty per impedire "
+"ai demoni la comunicazione verso il terminale di controllo. Questa "
+"comunicazione �� un potenziale buco nella sicurezza poich�� questi demoni "
+"possono inserire comandi nei terminali di controllo. Un programma bacato o "
+"compromesso potrebbe usare questo buco causando seri problemi."
#: en_US/selinux-faq.xml:1615(para)
msgid ""
"There are a few ways you can capture standard output from daemons. One "
"method is to pipe the output to the cat command."
msgstr ""
+"Ci sono un po di altri modi per catturare lo standard output dai demoni. Un "
+"metodo �� quello di eseguire il pipe dell'output al comando cat."
#: en_US/selinux-faq.xml:1620(command)
msgid "snmpd -v | cat"
-msgstr ""
+msgstr "snmpd -v | cat"
#: en_US/selinux-faq.xml:1622(para)
msgid ""
@@ -1912,6 +2103,10 @@
"daemon to its specific domain. You can do this using <command>system-config-"
"securitylevel</command> or <command>setsebool</command> on the command line."
msgstr ""
+"Quando fate il debug di un demone, potreste voler disattivare la transizione "
+"del demone al suo dominio specifico. Potete farlo usando <command>system-"
+"config-securitylevel</command> o <command>setsebool</command> dalla linea di "
+"comando."
#: en_US/selinux-faq.xml:1628(para)
msgid ""
@@ -1920,18 +2115,27 @@
"the command <command>setenforce 1</command> to re-enable &SEL; when you are "
"finished debugging."
msgstr ""
+"Un opzione finale �� quella di disabilitare la modalit�� enforcing durante il "
+"debugging. Impartite il seguente comando <command>setenforce 0</command> per "
+"disabilitare la modalit�� enforcing ed usate il comando <command>setenforce "
+"1</command> per riabilitare &SEL; quando avete terminato il debugging."
#: en_US/selinux-faq.xml:1638(para)
msgid ""
"When I do an upgrade of the policy package (for example, using <command>yum</"
"command>), what happens with the policy? Is it updated automatically?"
msgstr ""
+"Quando eseguo un upgrade del pacchetto delle policy (per esempio, usando "
+"<command>yum</command>), cosa succede con la policy? E' automaticamente "
+"aggiornata?"
#: en_US/selinux-faq.xml:1645(para)
msgid ""
"Policy reloads itself when the package is updated. This behavior replaces "
"the manual <command>make load</command>."
msgstr ""
+"La policy si ricarica da sola quando il pacchetto �� aggiornato. Questo "
+"comportamento sostituisce il comando manuale <command>make load</command>."
#: en_US/selinux-faq.xml:1649(para)
msgid ""
@@ -1940,6 +2144,11 @@
"when the policy update makes changes to the file <filename>/etc/selinux/"
"targeted/contexts/files/file_contexts</filename>."
msgstr ""
+"In certe situazioni, potreste dover rietichettare il file system. Questo "
+"potrebbe accadere per fissare gli errori di &SEL; qualora i contesti dei "
+"files divenissero non validi, o quando l'aggiornamento della policy fa dei "
+"cambiamenti al file <filename>/etc/selinux/targeted/contexts/files/"
+"file_contexts</filename>."
#: en_US/selinux-faq.xml:1656(para)
msgid ""
@@ -1948,25 +2157,30 @@
"the proper domain. This is highly dependent on the changes in the updated "
"policy."
msgstr ""
+"Dopo aver rietichettato il filesystem, un <command>reboot</command> non �� "
+"necessario, ma �� utile per assicurare che ogni processo e programma venga "
+"eseguito nel dominio appropriato. Questo �� altamente dipendente dai cambiamenti "
+"nella policy aggiornata."
#: en_US/selinux-faq.xml:1662(para)
msgid ""
"To relabel, you have several options. You may use the <command>fixfiles</"
"command> command:"
msgstr ""
+"Per rietichettare, avete diverse opzioni. Potreste usare il comando <command>fixfiles</"
+"command>:"
#: en_US/selinux-faq.xml:1667(command)
msgid "fixfiles relabel reboot"
-msgstr ""
+msgstr "fixfiles relabel reboot"
#: en_US/selinux-faq.xml:1670(para)
msgid "Alternately, use the <filename>/.autorelabel</filename> mechanism:"
-msgstr ""
+msgstr "In alternativa, usate il meccanismo <filename>/.autorelabel</filename>:"
#: en_US/selinux-faq.xml:1674(command)
-#, fuzzy
msgid "touch /.autorelabel reboot"
-msgstr "touch /.autorelabel"
+msgstr "touch /.autorelabel reboot"
#: en_US/selinux-faq.xml:1681(para)
msgid ""
@@ -1974,6 +2188,9 @@
"requires relabeling, will RPM handle relabeling the files owned by the "
"package?"
msgstr ""
+"Se la policy rilasciata con il pacchetto di un applicazione cambia in modo "
+"da richiedere la rietichettatura, potr�� RPM gestire la rietichettatura dei files "
+"posseduti dal pacchetto?"
#: en_US/selinux-faq.xml:1688(para)
msgid ""
@@ -1982,6 +2199,10 @@
"the <command>cpio</command> copy, as the package files are being put on the "
"disk."
msgstr ""
+"Si. I contesti di sicurezza per i files posseduti dal pacchetto sono immagazzinati "
+"nei dati dell'header del pacchetto. I contesti dei files sono impostati direttamente "
+"dopo la copia <command>cpio</command>, appena i files del pacchetto sono "
+"messi su disco."
#: en_US/selinux-faq.xml:1773(para)
msgid ""
@@ -1990,6 +2211,10 @@
"<replaceable><version></replaceable></filename>, and those I compile "
"myself have different sizes and MD5 checksums?"
msgstr ""
+"Perch�� le policy binarie distribuite con Fedora, tipo <filename>/etc/"
+"selinux/<replaceable><policyname></replaceable>/policy/policy."
+"<replaceable><version></replaceable></filename>, e quelle compilate "
+"da me hanno differenti dimensioni e MD5 checksums?"
#: en_US/selinux-faq.xml:1780(para)
msgid ""
@@ -1998,10 +2223,14 @@
"environments will make target files that have different sizes and MD5 "
"checksums."
msgstr ""
+"Quando installate un pacchetto policy, i files binari pre-compilati della policy sono "
+"inseriti direttamente in <filename>/etc/selinux</filename>. I differenti ambienti "
+"di compilazione creeranno files finali che hanno differenti dimensioni ed MD5 "
+"checksums."
#: en_US/selinux-faq.xml:1790(para)
msgid "Will new policy packages disable my system?"
-msgstr ""
+msgstr "I nuovi pacchetti policy potranno disabilitare il mio sistema?"
#: en_US/selinux-faq.xml:1795(para)
msgid ""
@@ -2015,45 +2244,53 @@
"to help you work through your problem. If you are able, write or fix policy "
"to resolve your problem."
msgstr ""
+"C'�� la possibilit�� che cambiamenti nei pacchetti della policy o nella policy "
+"rilasciata con un pacchetto applicativo possano causare errori, pi�� dinieghi, o "
+"altri comportamenti sconosciuti. Potete scoprire quale pacchetto causa il problema "
+"ripristinando policy e pacchetti applicativi uno alla volta. Se non volete tornare "
+"ad una pacchetto precedente, i files di configurazione della vecchia versione "
+"sono salvati con l'estensione <filename class="
+"\"extension\">.rpmsave</filename>. Usate le mailing lists, bugzilla, ed IRC "
+"per aiutarvi a lavorare al problema. Se ne siete capaci, scrivete o fissate la policy "
+"per risolvere il problema."
#: en_US/selinux-faq.xml:1812(para)
msgid "How can I help write policy?"
-msgstr ""
+msgstr "Come posso aiutare a scrivere una policy?"
#: en_US/selinux-faq.xml:1817(para)
msgid "Your help is definitely appreciated."
-msgstr ""
+msgstr "Il tuo aiuto �� veramente apprezzato."
#: en_US/selinux-faq.xml:1822(para)
-#, fuzzy
msgid ""
"You can start by joining the &FED;&SEL; mailing list. You can subscribe and "
"read the archives at <ulink url=\"http://www.redhat.com/mailman/listinfo/"
"fedora-selinux-list\"/>."
msgstr ""
-"&FED; mailing list —<ulink url=\"mailto:fedora-selinux-list@redhat.com"
-"\"/>; leggete gli archivi o sottoscrivetevi su <ulink url=\"http://www."
-"redhat.com/mailman/listinfo/fedora-selinux-list\"/>"
+"Potete cominciare iscrivendovi alla &FED;&SEL; mailing list. Potete "
+"sottoscrivervi e leggere gli archivi su <ulink url=\"http://www.redhat.com/"
+"mailman/listinfo/fedora-selinux-list\"/>."
#: en_US/selinux-faq.xml:1829(para)
-#, fuzzy
msgid ""
"The Unofficial FAQ has some generic policy writing HOWTO information. Refer "
"to <ulink url=\"http://sourceforge.net/docman/display_doc.php?"
"docid=14882&group_id=21266#BSP.1\"/> for more information."
msgstr ""
-"Scrivere tradizionali SE Linux policy HOWTO —<ulink url=\"https://"
-"sourceforge.net/docman/display_doc.php?docid=21959&group_id=21266\"/>"
+"Le Unofficial FAQ hanno alcune informazioni generiche policy writing HOWTO. "
+"Fate riferimento a <ulink url=\"http://sourceforge.net/docman/display_doc."
+"php?docid=14882&group_id=21266#BSP.1\"/> per maggiori informazioni."
#: en_US/selinux-faq.xml:1837(para)
-#, fuzzy
msgid ""
"Another new resource is the Writing SE Linux policy HOWTO, located online at "
"<ulink url=\"https://sourceforge.net/docman/display_doc.php?docid=21959&"
"group_id=21266\"/>."
msgstr ""
-"Scrivere tradizionali SE Linux policy HOWTO —<ulink url=\"https://"
-"sourceforge.net/docman/display_doc.php?docid=21959&group_id=21266\"/>"
+"Un altra nuova risorsa �� la Writing SE Linux policy HOWTO, reperibile online "
+"su <ulink url=\"https://sourceforge.net/docman/display_doc.php?"
+"docid=21959&group_id=21266\"/>."
#: en_US/selinux-faq.xml:1844(para)
msgid ""
@@ -2063,6 +2300,11 @@
"<filename>/usr/share/doc/selinux-policy-<replaceable>>version<</"
"replaceable></filename> which shows examples of policy."
msgstr ""
+"Inoltre, da &FC;&LOCALVER; la policy �� basata sulla <xref linkend=\"faq-"
+"entry-whatis-refpolicy\"/>, potreste dare un occhiata alla documentazione sulla "
+"sua pagina di progetto. Un'altra sorgente di informazione eccellente sono i files della policy in "
+"<filename>/usr/share/doc/selinux-policy-<replaceable>>version<</"
+"replaceable></filename> che mostrano esempi di policy."
#: en_US/selinux-faq.xml:1852(para)
msgid ""
@@ -2071,6 +2313,10 @@
"There is also a tool there to help you get started. The following procedure "
"is an example:"
msgstr ""
+"Se volete creare un nuovo dominio di policy, potete guardare ai files di "
+"interfaccia nelle sub-directory <filename>/usr/share/selinux/devel</filename>. "
+"Li c'�� anche uno strumento per aiutarvi a cominciare. La seguente procedura "
+"�� un esempio:"
#: en_US/selinux-faq.xml:1861(para)
msgid ""
@@ -2080,15 +2326,19 @@
"the name of the policy module and the full path to the executable. The "
"following command gives a usage example:"
msgstr ""
+"Usate il comando <command>policygentool</command> per generare i vostri files "
+"<filename>te</filename>, <filename>fc</filename> e <filename>if</filename>. Il "
+"comando <command>policygentool</command> necessita di due parametri: "
+"il nome del modulo della policy ed il percorso completo dell'eseguibile. Il seguente "
+"comando vi dar�� un esempio d'uso:"
#: en_US/selinux-faq.xml:1870(replaceable)
msgid "mydaemon /usr/sbin/mydaemon"
-msgstr ""
+msgstr "mydaemon /usr/sbin/mydaemon"
#: en_US/selinux-faq.xml:1870(command)
-#, fuzzy
msgid "policygentool <placeholder-1/>"
-msgstr "selinux-policy-targeted-<placeholder-1/>.noarch.rpm"
+msgstr "policygentool <placeholder-1/>"
#: en_US/selinux-faq.xml:1872(para)
msgid ""
@@ -2096,6 +2346,9 @@
"three files: <filename>mydaemon.te</filename>, <filename>mydaemon.fc</"
"filename> and <filename>mydaemon.if</filename>."
msgstr ""
+"Vi richieder�� un minimo di caratteristiche di dominio comuni, e creer�� tre "
+"files: <filename>mydaemon.te</filename>, <filename>mydaemon.fc</"
+"filename> e <filename>mydaemon.if</filename>."
#: en_US/selinux-faq.xml:1881(para)
msgid ""
@@ -2103,33 +2356,37 @@
"usr/share/selinux/devel/Makefile</filename>, to build a policy package "
"(<filename>mydaemon.pp</filename>):"
msgstr ""
+"Dopo aver generato i files di policy, usate il Makefile fornito, <filename>/"
+"usr/share/selinux/devel/Makefile</filename>, per compilare un pacchetto di policy "
+"(<filename>mydaemon.pp</filename>):"
#: en_US/selinux-faq.xml:1889(command)
msgid "make -f /usr/share/selinux/refpolicy/Makefile"
-msgstr ""
+msgstr "make -f /usr/share/selinux/refpolicy/Makefile"
#: en_US/selinux-faq.xml:1893(para)
msgid ""
"Now you can load the policy module, using <command>semodule</command>, and "
"relabel the executable using <command>restorecon</command>:"
msgstr ""
+"Ora potete caricare il modulo della policy, usando <command>semodule</command>, e "
+"rietichettare l'eseguibile usando <command>restorecon</command>:"
#: en_US/selinux-faq.xml:1899(replaceable)
msgid "mydaemon.pp"
-msgstr ""
+msgstr "mydaemon.pp"
#: en_US/selinux-faq.xml:1899(command)
-#, fuzzy
msgid "semodule -i <placeholder-1/>"
-msgstr "ls -alZ <placeholder-1/> id -Z ps -eZ"
+msgstr "semodule -i <placeholder-1/>"
#: en_US/selinux-faq.xml:1900(replaceable)
msgid "/usr/sbin/mydaemon"
-msgstr ""
+msgstr "/usr/sbin/mydaemon"
#: en_US/selinux-faq.xml:1900(command)
msgid "restorecon -v <placeholder-1/>"
-msgstr ""
+msgstr "restorecon -v <placeholder-1/>"
#: en_US/selinux-faq.xml:1904(para)
msgid ""
@@ -2137,18 +2394,21 @@
"it from doing much. Turn on permissive mode and then use the init script to "
"start your daemon:"
msgstr ""
+"Poich�� avete una policy molto limitata per il vostro eseguibile, SELinux preverr�� "
+"che faccia molto. Passate in modalit�� permissive e poi usate l'init script per "
+"avviare il vostro demone:"
#: en_US/selinux-faq.xml:1910(command)
msgid "setenforce 0"
-msgstr ""
+msgstr "setenforce 0"
#: en_US/selinux-faq.xml:1911(replaceable)
msgid "mydaemon"
-msgstr ""
+msgstr "mydaemon"
#: en_US/selinux-faq.xml:1911(command)
msgid "service <placeholder-1/> restart"
-msgstr ""
+msgstr "service <placeholder-1/> restart"
#: en_US/selinux-faq.xml:1915(para)
msgid ""
@@ -2162,24 +2422,34 @@
"always install the selinux-policy src rpm, which contains all of the policy "
"te files for the reference policy."
msgstr ""
+"Ora potrete cominciare a collezionare messaggi avc. Potrete usare <command>audit2allow</command> "
+"per tradurre i messaggi avc in regole allow e cominciare ad aggiornare il vostro "
+"file <filename>mydaemon.te</filename>. Dovrete cercare quindi le macro di "
+"interfaccia nella directory <filename>/usr/share/selinux/devel/include</filename> "
+"ed usarle direttamente, <command>audit2allow -R</command> tenter�� di trovare "
+"le interfacce che coincidano con la regola allow. Se volete pi�� esempi di policy, potete "
+"sempre installare l'rpm src selinux-policy, che contiene tutti i files policy "
+"te per la policy reference."
#: en_US/selinux-faq.xml:1933(para)
msgid "My console is being flooded with messages. How do I turn them off?"
-msgstr ""
+msgstr "La mia console �� inondata da messaggi. Come li fermo?"
#: en_US/selinux-faq.xml:1939(para)
msgid ""
"To regain useful control, turn off kernel messages to the console with this "
"command:"
msgstr ""
+"Per riottenere il controllo, disattivate i messaggi del kernel alla console con questo "
+"comando:"
#: en_US/selinux-faq.xml:1944(command)
msgid "dmesg -n 1"
-msgstr ""
+msgstr "dmesg -n 1"
#: en_US/selinux-faq.xml:1950(para)
msgid "Can I test the default policy without installing the policy source?"
-msgstr ""
+msgstr "Posso provare la policy predefinita senza installare il pacchetto di sorgenti della policy?"
#: en_US/selinux-faq.xml:1956(para)
msgid ""
@@ -2189,6 +2459,11 @@
"installed, the <command>fixfiles</command> command automates the file system "
"relabeling."
msgstr ""
+"Potete provare la policy predefinita di &SEL; installando solamente i pacchetti <filename>selinux-"
+"policy-<replaceable>policyname</replaceable></filename> e "
+"<filename>policycoreutils</filename>. Senza i sorgenti della policy "
+"installati, il comando <command>fixfiles</command> automatizzer�� la rietichettatura "
+"del file system."
#: en_US/selinux-faq.xml:1963(para)
msgid ""
@@ -2197,6 +2472,10 @@
"of the files in <filename>/tmp</filename>, cleaning up files which may have "
"old file context labels."
msgstr ""
+"Il comando <command>fixfiles relabel</command> �� l'equivalente di "
+"<command>make relabel</command>. Durante la rietichettatura, canceller�� tutti "
+"i files in <filename>/tmp</filename>, ripulendo i files che potrebbero avere "
+"vecchie etichette di contesto."
#: en_US/selinux-faq.xml:1969(para)
msgid ""
@@ -2207,10 +2486,16 @@
"as an argument, because it relabels the entire file system. If you need to "
"relabel a specific directory path, use <command>restorecon</command>."
msgstr ""
+"Altri comandi sono <command>fixfiles check</command>, che controlla i "
+"files con etichette errate, e <command>fixfiles restore</command>, che fissa i "
+"files mal etichettati ma non cancella i files in <filename>/tmp</filename>. "
+"Il comando <command>fixfiles</command> non accetta una lista di directories "
+"come argomento, poich�� il suo scopo �� rietichettare l'intero filesystem. Se avete bisogno "
+"di rietichettare una specifica directory, usate <command>restorecon</command>."
#: en_US/selinux-faq.xml:1983(para)
msgid "Why are some of my KDE applications having trouble under &SEL;?"
-msgstr ""
+msgstr "Perch�� alcune applicazioni KDE hanno probemi sotto &SEL;?"
#: en_US/selinux-faq.xml:1988(para)
msgid ""
@@ -2218,6 +2503,9 @@
"what can be done with &SEL; policy. This is because every KDE application "
"runs in the domain for <command>kdeinit</command>."
msgstr ""
+"Gli eseguibili KDE appaiono sempre come <command>kdeinit</command>, che limita "
+"ci�� che pu�� essere fatto con la policy &SEL;. Questo perch�� ogni applicazione KDE "
+"viene eseguita nel dominio per <command>kdeinit</command>."
#: en_US/selinux-faq.xml:1993(para)
msgid ""
@@ -2225,43 +2513,49 @@
"relabel <filename>/tmp</filename> and <filename>/var/tmp</filename>. There "
"is no good method of determining which file should have which context."
msgstr ""
+"I problemi spesso insorgono quando si installa &SEL; perch�� non �� possibile "
+"rietichettare /<filename>/tmp</filename> e <filename>/var/tmp</filename>. Non c'�� "
+"un buon metodo di determinare quale file dovrebbe avere quale contesto."
#: en_US/selinux-faq.xml:1999(para)
msgid "The solution is to fully log out of KDE and remove all KDE temporary files:"
-msgstr ""
+msgstr "La soluzione �� quella di eseguire un pieno log out da KDE e rimuovere tutti i files temporanei di KDE:"
#: en_US/selinux-faq.xml:2004(replaceable)
-#, fuzzy
msgid "<username>"
-msgstr "<versione>"
+msgstr "<username>"
#: en_US/selinux-faq.xml:2005(replaceable)
msgid "<other_kde_files>"
-msgstr ""
+msgstr "<other_kde_files>"
#: en_US/selinux-faq.xml:2004(command)
msgid "rm -rf /var/tmp/kdecache-<placeholder-1/> rm -rf /var/tmp/<placeholder-2/>"
-msgstr ""
+msgstr "rm -rf /var/tmp/kdecache-<placeholder-1/> rm -rf /var/tmp/<placeholder-2/>"
#: en_US/selinux-faq.xml:2007(para)
msgid "At your next login, your problem should be fixed."
-msgstr ""
+msgstr "Al prossimo login, il problema dovrebbe essere risolto."
#: en_US/selinux-faq.xml:2014(para)
msgid "Why does <option>SELINUX=disabled</option> not work for me?"
-msgstr ""
+msgstr "Perch�� <option>SELINUX=disabled</option> non funziona per me?"
#: en_US/selinux-faq.xml:2019(para)
msgid ""
"Be careful of white space in the file <filename>/etc/sysconfig/selinux</"
"filename>. The code is very sensitive to white space, even trailing space."
msgstr ""
+"Fate attenzione agli spazi vuoti nel file <filename>/etc/sysconfig/selinux</"
+"filename>. Il codice �� molto sensibile agli spazi vuoti, anche ai tabulatori."
#: en_US/selinux-faq.xml:2028(para)
msgid ""
"I have a process running as <computeroutput>unconfined_t</computeroutput>, "
"and &SEL; is still preventing my application from running."
msgstr ""
+"Ho un processo eseguito come <computeroutput>unconfined_t</computeroutput>, "
+"e &SEL; previene ancora l'esecuzione della mia applicazione."
#: en_US/selinux-faq.xml:2035(para)
msgid ""
@@ -2271,11 +2565,16 @@
"solutions for those denials. For more information on these restrictions, see "
"<ulink url=\"http://people.redhat.com/drepper/selinux-mem.html\"/>."
msgstr ""
+"Abbiamo cominciato a confinare il dominio <computeroutput>unconfined_t</computeroutput> "
+"domain somewhat. SELinux restricts certain memory protection operation. "
+"Following is a list of those denials, as well as possible reasons and "
+"solutions for those denials. For more information on these restrictions, see "
+"<ulink url=\"http://people.redhat.com/drepper/selinux-mem.html\"/>."
#: en_US/selinux-faq.xml:2046(computeroutput)
#, no-wrap
msgid "execmod"
-msgstr ""
+msgstr "execmod"
#: en_US/selinux-faq.xml:2048(para)
msgid ""
@@ -2284,11 +2583,15 @@
"replaceable></command>. Now your application can run. Please report this as "
"a bugzilla."
msgstr ""
+"Questo �� di solito basato su un'etichetta di libreria. Potete cambiare il contesto sulla "
+"libreria con <command>chcon -t textrel_shlib_t <replaceable>LIBRARY</"
+"replaceable></command>. Ora la vostra applicazione potr�� essere eseguita. Siete pregati di "
+"segnalare questo su bugzilla."
#: en_US/selinux-faq.xml:2058(computeroutput)
#, no-wrap
msgid "execstack"
-msgstr ""
+msgstr "execstack"
#: en_US/selinux-faq.xml:2060(para)
msgid ""
@@ -2297,11 +2600,15 @@
"library was mistakenly marked as requiring <computeroutput>execstack</"
"computeroutput>. Please report this as a bugzilla."
msgstr ""
+"Tentate <command>execstack -c <replaceable>LIBRARY</replaceable></"
+"command>. Ora provate nuovamente la vostra applicazione. Se l'applicazione funziona, la "
+"libreria era stata per errore contrassegnata come richiedente <computeroutput>execstack</"
+"computeroutput>. Segnalate questo in bugzilla."
#: en_US/selinux-faq.xml:2071(computeroutput)
#, no-wrap
msgid "execmem, execheap"
-msgstr ""
+msgstr "execmem, execheap"
#: en_US/selinux-faq.xml:2073(para)
msgid ""
@@ -2312,14 +2619,20 @@
"<computeroutput>execstack</computeroutput> failure. You can set the boolean "
"with"
msgstr ""
+"E' stata fornita una booleana per ognuno di questi controlli sugli errori della memoria. Cos�� "
+"se avete bisogno di eseguire un applicazione che necessiti entrambe i permessi, potete "
+"impostare la booleana allow_exec* per fissare il problema. Per esempio se provate "
+"ad eseguire un applicazione ed ottenete un messaggio AVC contenente un "
+"fallimento <computeroutput>execstack</computeroutput>. Potete impostare la booleana "
+"con"
#: en_US/selinux-faq.xml:2083(command)
msgid "setsebool -P allow_execstack=1"
-msgstr ""
+msgstr "setsebool -P allow_execstack=1"
#: en_US/selinux-faq.xml:2092(para)
msgid "What do these rpm errors mean?"
-msgstr ""
+msgstr "Cosa vogliono dire questi errori rpm?"
#: en_US/selinux-faq.xml:2098(computeroutput)
#, no-wrap
@@ -2327,6 +2640,8 @@
"genhomedircon: Warning! No support yet for expanding ROLE macros in the /etc/selinux/mls/contexts/files/homedir_template file when using libsemanage. \n"
"genhomedircon: You must manually update file_contexts.homedirs for any non-user_r users (including root)."
msgstr ""
+"genhomedircon: Warning! No support yet for expanding ROLE macros in the /etc/selinux/mls/contexts/files/homedir_template file when using libsemanage. \n"
+"genhomedircon: You must manually update file_contexts.homedirs for any non-user_r users (including root)."
#: en_US/selinux-faq.xml:2101(para)
msgid ""
@@ -2335,6 +2650,10 @@
"policy package that is reporting the problem and have non standard SELinux "
"role/user combinations. IE You are using some custom policy."
msgstr ""
+"Alcune delle interfacce non sono ancora complete per selinux. Molti utenti non dovrebbero "
+"preoccuparsi riguardo a questo avvertimento. Esso vi affligger�� solo se state eseguendo il "
+"pacchetto della policy che riporta il problema e non ha combinazioni SELinux "
+"ruolo/utente standard. Es. Se state usando alcune policy personalizzate."
#: en_US/selinux-faq.xml:2109(computeroutput)
#, no-wrap
@@ -2342,6 +2661,8 @@
"restorecon reset /etc/modprobe.conf context system_u:object_r:etc_runtime_t->system_u:object_r:modules_conf_t\n"
"restorecon reset /etc/cups/ppd/homehp.ppd context user_u:object_r:cupsd_etc_t->system_u:object_r:cupsd_rw_etc_t"
msgstr ""
+"restorecon reset /etc/modprobe.conf context system_u:object_r:etc_runtime_t->system_u:object_r:modules_conf_t\n"
+"restorecon reset /etc/cups/ppd/homehp.ppd context user_u:object_r:cupsd_etc_t->system_u:object_r:cupsd_rw_etc_t"
#: en_US/selinux-faq.xml:2112(para)
msgid ""
@@ -2349,21 +2670,26 @@
"difference between the previously install policy file_context and the newly "
"install policy context. This maintains the correct file context on disk."
msgstr ""
+"Durante il processo di aggiornamento, il pacchetto selinux esegue restorecon sulle "
+"differenze fra il file_context della policy installata in precedenza ed il nuovo "
+"contesto della policy installata. Questo mantiene la correttezza dei contesti dei file su disco."
#: en_US/selinux-faq.xml:2119(computeroutput)
#, no-wrap
msgid "libsepol.sepol_genbools_array: boolean hidd_disable_trans no longer in policy"
-msgstr ""
+msgstr "libsepol.sepol_genbools_array: boolean hidd_disable_trans no longer in policy"
#: en_US/selinux-faq.xml:2121(para)
msgid "This indicates that the updated policy has removed the boolean from policy."
-msgstr ""
+msgstr "Questo indica che la policy aggiornata ha rimosso la booleana dalla policy."
#: en_US/selinux-faq.xml:2129(para)
msgid ""
"I want to run a daemon on a non standard port but &SEL; will not allow me. "
"How do get this to work?"
msgstr ""
+"Voglio eseguire un demone su una porta non standard ma &SEL; non me lo permette. "
+"Come lo faccio funzionare?"
#: en_US/selinux-faq.xml:2135(para)
msgid ""
@@ -2371,20 +2697,25 @@
"ports. So say you want httpd to be able to listen on port 8082. You could "
"enter the command."
msgstr ""
+"Potete usare il comando <command>semanage</command> per definire porte "
+"aggiuntive. Diciamo ad esempio che volete consentire ad httpd di ascoltare sulla porta 8082. "
+"Potreste inserire il comando."
#: en_US/selinux-faq.xml:2141(command)
msgid "semanage port -a -p tcp -t http_port_t 8082"
-msgstr ""
+msgstr "semanage port -a -p tcp -t http_port_t 8082"
#: en_US/selinux-faq.xml:2147(para)
msgid "How do I add additional translations to my MCS/MLS system?"
-msgstr ""
+msgstr "Come aggiungo traduzioni aggiuntive nel mio sistema MCS/MLS?"
#: en_US/selinux-faq.xml:2152(para)
msgid ""
"Translations are handled through libsemanage. Use <command>semanage "
"translation -l</command> to list all current translations."
msgstr ""
+"Le traduzioni sono gestite attraverso libsemanage. Usate <command>semanage "
+"translation -l</command> per elencare alcune delle traduzioni correnti."
#: en_US/selinux-faq.xml:2158(computeroutput)
#, no-wrap
@@ -2396,12 +2727,20 @@
"s0-s0:c0.c255 SystemLow-SystemHigh\n"
"s0:c0.c255 SystemHigh"
msgstr ""
+"# semanage translation -l\n"
+"Level Translation\n"
+"\n"
+"s0\n"
+"s0-s0:c0.c255 SystemLow-SystemHigh\n"
+"s0:c0.c255 SystemHigh"
#: en_US/selinux-faq.xml:2165(para)
msgid ""
"Now pick an unused category. Say you wanted to add Payroll as a translation, "
"and s0:c6 is unused."
msgstr ""
+"Ora selezionate una categoria non utilizzata. Diciamo che volete aggiungere Payroll come traduzione, "
+"e s0:c6 non �� utilizzato."
#: en_US/selinux-faq.xml:2170(computeroutput)
#, no-wrap
@@ -2415,18 +2754,28 @@
"s0:c0.c255 SystemHigh\n"
"s0:c6 Payroll"
msgstr ""
+"# semanage translation -a -T Payroll s0:c6\n"
+"# semanage translation -l\n"
+"Level Translation\n"
+"\n"
+"s0\n"
+"s0-s0:c0.c255 SystemLow-SystemHigh\n"
+"s0:c0.c255 SystemHigh\n"
+"s0:c6 Payroll"
#: en_US/selinux-faq.xml:2183(para)
msgid ""
"I have setup my MCS/MLS translations, now I want to designate which users "
"can read a given category?"
-msgstr ""
+msgstr "Ho impostato le mie traduzioni MCS/MLS, adesso vorrei designare quali utenti possono leggere una data categoria?"
#: en_US/selinux-faq.xml:2189(para)
msgid ""
"You can modify the range of categories a user can login with by using "
"<command>semanage</command>, as seen in this example."
msgstr ""
+"Potete modificare la gamma delle categorie con cui un utente pu�� loggarsi usando "
+"<command>semanage</command>, come si vede in questo esempio."
#: en_US/selinux-faq.xml:2194(computeroutput)
#, no-wrap
@@ -2440,6 +2789,14 @@
"csellers user_u s0-Payroll \n"
"root root SystemLow-SystemHigh"
msgstr ""
+"# semanage login -a -r s0-Payroll csellers\n"
+"# semanage login -l\n"
+"\n"
+"Login Name SELinux User MLS/MCS Range \n"
+"\n"
+"__default__ user_u s0 \n"
+"csellers user_u s0-Payroll \n"
+"root root SystemLow-SystemHigh"
#: en_US/selinux-faq.xml:2203(para)
msgid ""
@@ -2447,6 +2804,9 @@
"<computeroutput>Payroll</computeroutput> category with the first command, as "
"indicated in the listing output from the second command."
msgstr ""
+"Nel precedente esempio, all'utente csellers �� stato dato accesso alla "
+"categoria <computeroutput>Payroll</computeroutput> con il primo comando, come "
+"indicato nell'elenco dell'output dal secondo comando."
#: en_US/selinux-faq.xml:2213(para)
msgid ""
@@ -2454,6 +2814,9 @@
"<filename>/tmp</filename> and then execute them, SELinux policy is "
"preventing this. What should I do?"
msgstr ""
+"Sto scrivendo uno script php che necessita di creare files temporanei in "
+"<filename>/tmp</filename> quindi deve eseguirli, la policy SELinux lo "
+"previene. Che devo fare?"
#: en_US/selinux-faq.xml:2220(para)
msgid ""
@@ -2464,32 +2827,42 @@
"You should label the directory <computeroutput>httpd_sys_script_rw_t</"
"computeroutput>."
msgstr ""
+"Dovreste evitare di avere applicazioni di sistema che scrivono nella directory <filename>/tmp</"
+"filename>, poich�� anche gli utenti tendono ad usare la directory <filename>/tmp</filename>. "
+"Sarebbe meglio creare una directory altrove che possa essere posseduta dal processo apache "
+"e permettere al vostro script di scriverci. "
+"Dovreste etichettare la directory <computeroutput>httpd_sys_script_rw_t</"
+"computeroutput>."
#: en_US/selinux-faq.xml:2232(para)
msgid ""
"I am setting up swapping to a file, but I am seeing AVC messages in my log "
"files?"
-msgstr ""
+msgstr "Sto impostando lo swapping su un file, ma vedo messaggi AVC nei miei file di log?"
#: en_US/selinux-faq.xml:2238(para)
msgid ""
"You need to identify the swapfile to SELinux by setting its file context to "
"<computeroutput>swapfile_t</computeroutput>."
msgstr ""
+"Avete bisogno di far identificare lo swapfile a SELinux impostando il suco contesto di file a "
+"<computeroutput>swapfile_t</computeroutput>."
#: en_US/selinux-faq.xml:2243(replaceable)
msgid "SWAPFILE"
-msgstr ""
+msgstr "SWAPFILE"
#: en_US/selinux-faq.xml:2243(command)
msgid "chcon -t swapfile_t <placeholder-1/>"
-msgstr ""
+msgstr "chcon -t swapfile_t <placeholder-1/>"
#: en_US/selinux-faq.xml:2249(para)
msgid ""
"Please explain the <computeroutput>relabelto</computeroutput>/"
"<computeroutput>relabelfrom</computeroutput> permissions?"
msgstr ""
+"Potete spiegarmi i permessi <computeroutput>relabelto</computeroutput>/"
+"<computeroutput>relabelfrom</computeroutput>?"
#: en_US/selinux-faq.xml:2256(para)
msgid ""
@@ -2500,18 +2873,22 @@
"T1 is the original type of the type and T2 is the new type specified by the "
"program."
msgstr ""
+"Per i files, <computeroutput>relabelfrom</computeroutput> significa \"Pu�� il dominio D "
+"rietichettare un file da (es. attualmente in) tipo T1?\" e "
+"<computeroutput>relabelto</computeroutput> significa \"Pu�� il dominio D rietichettare un "
+"file al tipo T2?\", cos�� entrambe i controlli sono applicati sula rietichettatura di un file, dove "
+"T1 �� il tipo originale e T2 �� il nuovo tipo specificato dal programma."
#: en_US/selinux-faq.xml:2264(para)
msgid "Useful documents to look at:"
-msgstr ""
+msgstr "Documentazione utile da vedere:"
#: en_US/selinux-faq.xml:2269(para)
-#, fuzzy
msgid ""
"Object class and permission summary by Tresys <ulink url=\"http://tresys.com/"
"selinux/obj_perms_help.shtml\"/>"
msgstr ""
-"Elenchi di classi di oggetti SELinux e permessi —<ulink url=\"http://"
+"Un sommario da Tresys di classi di oggetti e permessi <ulink url=\"http://"
"tresys.com/selinux/obj_perms_help.shtml\"/>"
#: en_US/selinux-faq.xml:2275(para)
@@ -2521,6 +2898,10 @@
"abs.cfm\"/>. This is also available in the selinux-doc package (and more up-"
"to-date there)."
msgstr ""
+"Rapporto tecnico - Implementing SELinux as an LSM (descrive i controlli sui permessi "
+"su una base per-hook) <ulink url=\"http://www.nsa.gov/selinux/papers/module-"
+"abs.cfm\"/>. Questo �� anche disponibile nel pacchetto selinux-doc (e in modo pi�� "
+"aggiornato qui)."
#: en_US/selinux-faq.xml:2284(para)
msgid ""
@@ -2531,10 +2912,16 @@
"implementation, but a good resource nonetheless). <ulink url=\"http://www."
"nsa.gov/selinux/papers/slinux-abs.cfm\"/>"
msgstr ""
+"Rapporto tecnico - Integrating Flexible Support for Security Policies into the "
+"Linux Operating System (descrive implementazioni e disegni originali, "
+"includendo tavole sinottiche delle classi, permessi, e quali controlli di permessi "
+"sono applicati a quali chiamate di sistema. Non �� completamente aggiornato con "
+"l'implementazione attuale, ma ci�� nonostante �� una buona risorsa). <ulink url=\"http://www."
+"nsa.gov/selinux/papers/slinux-abs.cfm\"/>"
#: en_US/selinux-faq.xml:2300(para)
msgid "Where are &SEL; AVC messages (denial logs, etc.) stored?"
-msgstr ""
+msgstr "Dove sono conservati i messaggi AVC di &SEL; (dinieghi logs, etc.)?"
#: en_US/selinux-faq.xml:2305(para)
msgid ""
@@ -2546,15 +2933,21 @@
"choose to install the audit daemon, in which case AVC messages will be in "
"<filename>/var/log/audit/audit.log</filename>."
msgstr ""
+"In &FC; 2 e 3, i messaggi AVC di SELinux si potevano trovare in <filename>/var/log/"
+"messages</filename>. In &FC; 4, �� stato aggiunto il demone audit, e questi "
+"messaggi sono stati spostati in <filename>/var/log/audit/audit.log</filename>. In &FC; 5, "
+"il demone audit non �� installato per impostazione predefinita, di conseguenza questi "
+"messaggi si trovano in <filename>/var/log/messages</filename> a meno che "
+"non abbiate scelto di installare il demone audit, nel qual caso i messaggi AVC si troveranno in "
+"<filename>/var/log/audit/audit.log</filename>."
#: en_US/selinux-faq.xml:2321(title)
-#, fuzzy
msgid "Deploying &SEL;"
-msgstr "Controllare &SEL;"
+msgstr "Implementare &SEL;"
#: en_US/selinux-faq.xml:2324(para)
msgid "What file systems can I use for &SEL;?"
-msgstr ""
+msgstr "Che file systems posso usare per &SEL;?"
#: en_US/selinux-faq.xml:2329(para)
msgid ""
@@ -2562,6 +2955,9 @@
"in the right <parameter>security.*</parameter> namespace. In addition to "
"ext2/ext3, XFS has recently added support for the necessary labels."
msgstr ""
+"Il file system deve supportare le etichette <computeroutput>xattr</computeroutput> "
+"nel giusto <parameter>security.*</parameter>namespace. Oltre a ext2/ext3, XFS "
+"ha recentemente aggiunto il supporto per le necessarie etichette."
#: en_US/selinux-faq.xml:2336(para)
msgid ""
@@ -2569,10 +2965,13 @@
"2.6.15, but fixed (worked around) in 2.6.16. Your kernel must include this "
"fix if you choose to use XFS with &SEL;."
msgstr ""
+"Notate che il supporto SELinux XFS non funziona nella serie di kernel 2.6.14 e "
+"2.6.15, ma �� stato fissato (aggirando il problema) nella 2.6.16. Il vostro kernel "
+"dovr�� includere questo fix se scegliete di usare XFS."
#: en_US/selinux-faq.xml:2346(para)
msgid "How does &SEL; impact system performance?"
-msgstr ""
+msgstr "Come incide SELinux sulle prestazioni del sistema?"
#: en_US/selinux-faq.xml:2351(para)
msgid ""
@@ -2583,12 +2982,20 @@
"worse in some cases. &SEL; performance tuning continues to be a priority of "
"the development team."
msgstr ""
+"Questa �� una variabile difficile da quantificare, ed �� pesantemente dipendente "
+"dall'affinamento e dall'uso del sistema su cui &SEL; sta girando. L'ultima volta che "
+"le prestazioni sono state misurate, l'incidenza era circa del 7% per codice "
+"completamente non affinato. Successivi cambiamenti in componenti di sistema come "
+"il networking sembrerebbero aver peggiorato la situazione in alcuni casi. Le prestazioni "
+"e l'affinamento di &SEL; continuano ad essere una priorit�� del team di sviluppo."
#: en_US/selinux-faq.xml:2364(para)
msgid ""
"What types of deployments, applications, and systems should I leverage &SEL; "
"in?"
msgstr ""
+"Di che tipo di implementazioni, applicazioni, sistemi, etc. dovr�� tener conto per l'uso "
+"con &SEL;?"
#: en_US/selinux-faq.xml:2370(para)
msgid ""
@@ -2598,6 +3005,11 @@
"extra software and services, and run a very small, focused set of services. "
"A Web server or mail server is a good example."
msgstr ""
+"Inizialmente, &SEL; �� stato usato per i server affacciati su Internet che "
+"eseguono poche, funzioni specializzate, dove �� critico mantenere "
+"una sicurezza estremamente stretta. Gli amministratori tipicamente privano una "
+"simile macchina di software e servizi extra, ed eseguono un gruppo di servizi "
+"ristrettissimo, molto mirato. Un Web server o un mail server sono un buon esempio."
#: en_US/selinux-faq.xml:2378(para)
msgid ""
@@ -2606,6 +3018,10 @@
"easier. A dedicated system running a specialized third-party application "
"would also be a good candidate."
msgstr ""
+"In questi servers di nicchia, potrete bloccare la policy molto strettamente. "
+"Questo sar�� facilitato dal piccolo numero di interazioni con gli altri componenti. "
+"Una macchina dedicata che esegue un applicazione specialistica di terze parti sar�� "
+"anch'essa un buon candidato."
#: en_US/selinux-faq.xml:2384(para)
msgid ""
@@ -2617,16 +3033,24 @@
"<firstterm>targeted policy</firstterm> that focuses on specific, vulnerable "
"daemons."
msgstr ""
+"In futuro, &SEL; sar�� indirizzato a tutti gli ambienti. Per poter raggiungere "
+"questo obbiettivo, la comunit�� e gli <firstterm>independent software "
+"vendors</firstterm> (<abbrev>ISV</abbrev>s) dovranno lavorare con gli sviluppatori "
+"&SEL; per produrre le policy necessarie. Finora, sono state scritte una "
+"<firstterm>strict policy</firstterm> molto restrittiva, ed una <firstterm>targeted policy</firstterm> "
+"che mira a specifici, demoni vulnerabili."
#: en_US/selinux-faq.xml:2394(para)
msgid ""
"For more information about these policies, refer to <xref linkend=\"qa-"
"whatis-policy\"/> and <xref linkend=\"qa-whatis-targeted-policy\"/>."
msgstr ""
+"Per maggiori informazioni su queste policies, fate riferimento a <xref linkend=\"qa-"
+"whatis-policy\"/> e <xref linkend=\"qa-whatis-targeted-policy\"/>."
#: en_US/selinux-faq.xml:2402(para)
msgid "How does &SEL; affect third-party applications?"
-msgstr ""
+msgstr "Che effetto ha &SEL; sulle applicazioni di terze parti?"
#: en_US/selinux-faq.xml:2407(para)
msgid ""
@@ -2637,6 +3061,12 @@
"extra-secure manner. You or another provider must write policy to protect "
"these applications with MAC security."
msgstr ""
+"Uno degli scopi nell'implementare la policy targeted di &SEL; in &FC; �� quello "
+"di permettere ad applicazioni di terze parti di funzionare senza modifiche. La targeted "
+"policy �� trasparente a quelle applicazioni che non prova a controllare e che ricadono "
+"nella sicurezza di Linux standard. Queste applicazioni non saranno eseguite in maniera "
+"extra sicura. Voi od un altro fornitore dovrete scrivere una policy per proteggere queste "
+"applicazioni con la sicurezza MAC."
#: en_US/selinux-faq.xml:2416(para)
msgid ""
@@ -2646,6 +3076,11 @@
"previously unknown security issues with your application. You may have to "
"modify the application to work under &SEL;."
msgstr ""
+"E' impossibile predire come si comporterebbe ogni applicazione di terze parti "
+"con &SEL;, anche eseguendo la targeted policy. Potreste essere in grado di risolvere "
+"problematiche insorgenti cambiando la policy. Potreste trovare che &SEL; esponga "
+"problemi di sicurezza sconosciuti con la vostra applicazione. Potreste dover modificare "
+"l'applicazione per farla funzionare sotto &SEL;."
#: en_US/selinux-faq.xml:2424(para)
msgid ""
@@ -2656,6 +3091,13 @@
"package. This will allow you to secure the behavior of your application with "
"the power of &SEL; for any user installing your package."
msgstr ""
+"Notate che con l'aggiunta di <xref linkend=\"faq-entry-whatare-policy-"
+"modules\"/>, �� ora possibile per gli sviluppatori di terze parti includere "
+"moduli di policy con le loro applicazioni. Se siete uno sviluppatore si "
+"terze pari o un manutentore di pacchetti, siete pregati di considerare l'inclusione di "
+"un modulo di policy nel vostro pacchetto. Questo permetter�� di rendere sicuro il "
+"comportamento della vostra applicazione con la potenza di &SEL; per ogni "
+"utente che installa il pacchetto."
#: en_US/selinux-faq.xml:2434(para)
msgid ""
@@ -2665,9 +3107,14 @@
"selinux list, for discussion. For more information about that list, refer to "
"<ulink url=\"http://www.redhat.com/mailman/listinfo/fedora-selinux-list/\"/>."
msgstr ""
+"Un valore importante che i testers e gli utenti di &FC; portano alla comunit�� �� "
+"l'estensivo prova di applicativi di terze parti. Con questo a mente, siete pregati "
+"di portare le vostre esperienze alla mailing list appropriata per le discussioni, come "
+"la mailing list fedora-selinux. Per maggiori informazioni su questa lista, fate riferimento a "
+"<ulink url=\"http://www.redhat.com/mailman/listinfo/fedora-selinux-list/\"/>."
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
#: en_US/selinux-faq.xml:0(None)
msgid "translator-credits"
-msgstr ""
+msgstr "Francesco Tombolini <tombo(a)adamantio.net> 2005, 2006"
18 years
docs-common Makefile.common,1.110,1.111
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32057
Modified Files:
Makefile.common
Log Message:
Back out silly attempt to retain entities while serializing document. Instead, we should and will parse these entities normally when the POT file is created, so they can be translated like other text.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.110
retrieving revision 1.111
diff -u -r1.110 -r1.111
--- Makefile.common 11 Apr 2006 20:18:03 -0000 1.110
+++ Makefile.common 24 Apr 2006 01:52:18 -0000 1.111
@@ -382,9 +382,7 @@
.PHONY: html-${1}
html-$(1):: ${DOCBASE}-$(1)/index.html
${DOCBASE}-$(1)/index.html:: ${XMLFILES-${1}} ${XMLDEPFILES-${1}} set-locale-${1}
- LANG=$(1).UTF-8 ${XMLLINT} --noent --xinclude $(1)/$(DOCBASE).xml 2>/dev/null >$(1)/$(DOCBASE).xml-parsed
- LANG=$(1).UTF-8 ${XMLTO} html -x $(XSLHTML) -o $(DOCBASE)-$(1) $(1)/$(DOCBASE).xml-parsed
- ${RM} -f $(1)/$(DOCBASE).xml-parsed
+ LANG=$(1).UTF-8 ${XMLTO} html -x $(XSLHTML) -o $(DOCBASE)-$(1) $(1)/$(DOCBASE).xml
mkdir -p $(DOCBASE)-$(1)/stylesheet-images/
cp ${FDPDIR}/docs-common/stylesheet-images/*.png $(DOCBASE)-$(1)/stylesheet-images
cp ${HTMLCSS} $(DOCBASE)-$(1)/fedora.css
@@ -419,9 +417,7 @@
html-nochunks-$(1):: ${DOCBASE}-$(1).html
${DOCBASE}-$(1).html:: ${XMLFILES-${1}} ${XMLDEPFILES-${1}} set-locale-${1}
- LANG=$(1).UTF-8 ${XMLLINT} --noent --xinclude $(1)/$(DOCBASE).xml 2>/dev/null > $(1)/$(DOCBASE).xml-parsed
- LANG=${1}.UTF-8 ${XMLTO} html-nochunks -x $(XSLHTMLNOCHUNKS) $(1)/$(DOCBASE).xml-parsed
- ${RM} -f $(1)/$(DOCBASE).xml-parsed
+ LANG=${1}.UTF-8 ${XMLTO} html-nochunks -x $(XSLHTMLNOCHUNKS) $(1)/$(DOCBASE).xml
mv $(DOCBASE).html $(DOCBASE)-$(1).html
mkdir -p stylesheet-images/
cp ${FDPDIR}/docs-common/stylesheet-images/*.png stylesheet-images/
18 years
selinux-faq/en_US selinux-faq.xml,1.10,1.11
by fedora-docs-commits@redhat.com
Author: csellers
Update of /cvs/docs/selinux-faq/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26901
Modified Files:
selinux-faq.xml
Log Message:
rephrased php FAQ entry to address bz#139744
Index: selinux-faq.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/en_US/selinux-faq.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- selinux-faq.xml 19 Apr 2006 18:36:49 -0000 1.10
+++ selinux-faq.xml 20 Apr 2006 20:16:03 -0000 1.11
@@ -2406,8 +2406,8 @@
<qandaentry>
<question>
<para>
- I am writing an php script that needs to create temporary files in
- <filename>/tmp</filename> and possibly execute them, SELinux
+ I am writing a php script that needs to create files
+ and possibly execute them. SELinux
policy is preventing this. What should I do?
</para>
</question>
@@ -2419,7 +2419,7 @@
is something we want to prevent.
</para>
<para>
- If you merely need to allow your script to create tempory
+ If you merely need to allow your script to create
(non-executable) files, this is possible. That said,
you should avoid having system applications writing to the
<filename>/tmp</filename> directory, since users tend to use the
@@ -2427,8 +2427,9 @@
create a directory elsewhere which could be owned by the apache
process and allow your script to write to it. You should label the
directory <computeroutput>httpd_sys_script_rw_t</computeroutput>,
- which will allow apache to write the temporary files to that
- directory.
+ which will allow apache to read and write files to that
+ directory. This directory could be located anywhere that apache
+ can get to (even <filename>$HOME/public_html/</filename>).
</para>
</answer>
</qandaentry>
18 years
selinux-faq/en_US selinux-faq.xml,1.9,1.10
by fedora-docs-commits@redhat.com
Author: csellers
Update of /cvs/docs/selinux-faq/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26256
Modified Files:
selinux-faq.xml
Log Message:
moved key FAQs up, per bug in bz#18727
Index: selinux-faq.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/en_US/selinux-faq.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- selinux-faq.xml 19 Apr 2006 18:20:37 -0000 1.9
+++ selinux-faq.xml 19 Apr 2006 18:36:49 -0000 1.10
@@ -714,6 +714,159 @@
</para>
</answer>
</qandaentry>
+ <qandaentry id="qa-using-s-c-securitylevel" xreflabel="How to use system-config-securitylevel">
+ <question>
+ <para>
+ How do I enable/disable &SEL; protection on specific daemons under
+ the targeted policy?
+ </para>
+ </question>
+ <answer>
+ <para>
+ Use <command>system-config-securitylevel</command>, also known as
+ the <application>Security Level Configuration</application>
+ graphical tool, to control the
+ Boolean values of specific daemons. For example, if you need to
+ disable &SEL; for Apache to run correctly in your environment, you
+ can disable the value in
+ <command>system-config-securitylevel</command>. This change
+ disables the transition to the policy defined in
+ <filename>apache.te</filename>, allowing <command>httpd</command>
+ to remain under regular Linux DAC security.
+ </para>
+ </answer>
+ </qandaentry>
+ <qandaentry id="faq-entry-local.te" xreflabel="Local Policy Customizations">
+ <question>
+ <para>
+ In the past I have written local.te file in policy sources for my
+ own local customization to policy, how do I do this
+ in &FC; 5?
+ </para>
+ </question>
+ <answer>
+ <para>
+ Since &FC; 5 uses a modular policy, you don't have to have the
+ complete policy source any more. Now, you can just create a local
+ policy module for your local policy customizations. To do this,
+ follow these steps.
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Create a temporary directory, and change into it.
+ </para>
+<screen>
+<computeroutput>$ mkdir foo
+$ cd foo</computeroutput>
+</screen>
+ </step>
+ <step>
+ <para>
+ Create empty te, if, and fc files.
+ </para>
+<screen>
+<computeroutput>$ touch local.te local.if local.fc</computeroutput>
+</screen>
+ </step>
+ <step>
+ <para>
+ Edit the local.te file, adding appropriate content.
+ For example:
+ </para>
+<screen>
+<computeroutput>policy_module(local, 1.0)
+
+require {
+ attribute httpdcontent;
+ type smbd_t;
+}
+
+allow smbd_t httpdcontent:dir create_dir_perms;
+allow smbd_t httpdcontent:{ file lnk_file } create_file_perms;</computeroutput>
+</screen>
+ <para>
+ There are 3 parts to this file.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The <computeroutput>policy_module</computeroutput> call
+ inserts statements to make the module work, including
+ declaring the module and requiring system roles, classes,
+ and permissions. Make sure the name declared here (local
+ in this case) matches the name you gave the file
+ (local.te).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <computeroutput>require</computeroutput> block
+ lists the symbols that this module uses that must be
+ declared in other modules. In this case, we require the
+ attribute <computeroutput>httpdcontent</computeroutput>
+ and the type <computeroutput>smbd_t</computeroutput>.
+ Note that all types and attributes you use in rules
+ must be required here unless you are declaring them
+ yourself below.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The rest of the file is the policy, in this case
+ consisting only of a couple of allow rules. You could
+ also place type declarations, dontaudit statements,
+ interface calls, or most things that can go in a normal
+ te file here.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </step>
+ <step>
+ <para>
+ Build the policy module.
+ </para>
+<screen>
+<computeroutput>$ make -f /usr/share/selinux/devel/Makefile
+Compliling targeted local module
+/usr/bin/checkmodule: loading policy configuration from tmp/local.tmp
+/usr/bin/checkmodule: policy configuration loaded
+/usr/bin/checkmodule: writing binary representation (version 5) to tmp/local.mod
+Creating targeted local.pp policy package
+rm tmp/local.mod.fc tmp/local.mod</computeroutput>
+</screen>
+ <para>
+ Note that this uses <command>checkmodule</command>, which is
+ part of the checkpolicy rpm. So, make sure you install this
+ rpm before doing this.
+ </para>
+ </step>
+ <step>
+ <para>
+ Become root, and install the policy module with
+ <command>semodule</command>.
+ </para>
+<screen>
+<computeroutput>$ su
+Password:
+# semodule -i local.pp</computeroutput>
+</screen>
+ </step>
+ </procedure>
+ <note>
+ <title>Module are uniquely identified by name</title>
+ <para>
+ This means that if you later insert another
+ <filename>local.pp</filename>, it will
+ replace the one you just loaded. So, you should keep this
+ <filename>local.te</filename> around, and just add to it if you
+ need to make later policy customizations. If you lose it, but
+ want to keep your previous policy around, just call the new
+ local policy module something else (say local2.te).
+ </para>
+ </note>
+ </answer>
+ </qandaentry>
<qandaentry>
<question>
<para>
@@ -810,6 +963,127 @@
<qandaentry>
<question>
<para>
+ How can I help write policy?
+ </para>
+ </question>
+ <answer>
+ <para>
+ Your help is definitely appreciated.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ You can start by joining the &FED; &SEL; mailing list. You can
+ subscribe and read the archives at <ulink
+ url="http://www.redhat.com/mailman/listinfo/fedora-selinux-list"/>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Unofficial FAQ has some generic policy writing HOWTO
+ information. Refer to <ulink
+ url="http://sourceforge.net/docman/display_doc.php?docid=14882&group_id=21..."/>
+ for more information.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Another new resource is the Writing SE Linux policy HOWTO,
+ located online at <ulink
+ url="https://sourceforge.net/docman/display_doc.php?docid=21959&group_id=2..."/>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Also, since the &FC; &LOCALVER; policy is based on the <xref
+ linkend="faq-entry-whatis-refpolicy"/>, you should look at the
+ documentation on its project page. Another excellent source of
+ information is the example policy files in
+ <filename>/usr/share/doc/selinux-policy-<replaceable>>version<</replaceable></filename>
+ and <filename>/usr/share/selinux/devel</filename>.
+ </para>
+ <para>
+ If you want to create a new policy domain, you can look at the
+ interface files in the
+ <filename>/usr/share/selinux/devel</filename> sub-directories.
+ There is also a tool there to help you get started.
+ The following procedure is an example:
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Use the <command>policygentool</command> command to generate
+ your own <filename>te</filename>, <filename>fc</filename> and
+ <filename>if</filename> files. The
+ <command>policygentool</command> command takes two parameters:
+ the name of the policy module and the full path to the
+ executable. The following command gives a usage example:
+ </para>
+<screen>
+<command>policygentool <replaceable>mydaemon /usr/sbin/mydaemon</replaceable></command>
+</screen>
+ <para>
+ It will prompt you for a few common domain characteristics,
+ and will create three files:
+ <filename>mydaemon.te</filename>,
+ <filename>mydaemon.fc</filename> and
+ <filename>mydaemon.if</filename>.
+ </para>
+ </step>
+ <step>
+ <para>
+ After you generate the policy files, use the supplied
+ Makefile,
+ <filename>/usr/share/selinux/devel/Makefile</filename>, to
+ build a policy package
+ (<filename>mydaemon.pp</filename>):
+ </para>
+<screen>
+<command>make -f /usr/share/selinux/refpolicy/Makefile</command>
+</screen>
+ </step>
+ <step>
+ <para>
+ Now you can load the policy module, using
+ <command>semodule</command>, and relabel the executable using
+ <command>restorecon</command>:
+ </para>
+<screen>
+<command>semodule -i <replaceable>mydaemon.pp</replaceable></command>
+<command>restorecon -v <replaceable>/usr/sbin/mydaemon</replaceable></command>
+</screen>
+ </step>
+ <step>
+ <para>
+ Since you have very limited policy for your executable,
+ SELinux will prevent it from doing much. Turn on permissive
+ mode and then use the init script to start your daemon:
+ </para>
+<screen>
+<command>setenforce 0</command>
+<command>service <replaceable>mydaemon</replaceable> restart</command>
+</screen>
+ </step>
+ </procedure>
+ <para>
+ Now you can collect avc messages. You can use
+ <command>audit2allow</command> to translate the avc messages to
+ allow rules and begin updating your
+ <filename>mydaemon.te</filename> file. You should search for
+ interface macros in the
+ <filename>/usr/share/selinux/devel/include</filename> directory and
+ use these instead of using the allow rules directly, whenever
+ possible. <command>audit2allow -R</command> will attempt to find
+ interfaces that match the allow rule.
+ If you want more examples of policy, you could always
+ install the selinux-policy src rpm, which contains all of the
+ policy te files for the reference policy.
+ </para>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
How do I switch the policy I am currently using?
</para>
</question>
@@ -965,28 +1239,6 @@
</procedure>
</answer>
</qandaentry>
- <qandaentry id="qa-using-s-c-securitylevel" xreflabel="How to use system-config-securitylevel">
- <question>
- <para>
- How do I enable/disable &SEL; protection on specific daemons under
- the targeted policy?
- </para>
- </question>
- <answer>
- <para>
- Use <command>system-config-securitylevel</command>, also known as
- the <application>Security Level Configuration</application>
- graphical tool, to control the
- Boolean values of specific daemons. For example, if you need to
- disable &SEL; for Apache to run correctly in your environment, you
- can disable the value in
- <command>system-config-securitylevel</command>. This change
- disables the transition to the policy defined in
- <filename>apache.te</filename>, allowing <command>httpd</command>
- to remain under regular Linux DAC security.
- </para>
- </answer>
- </qandaentry>
<qandaentry>
<question>
<para>
@@ -1195,195 +1447,64 @@
</para>
</question>
<answer>
- <para>
- Run <command>auditctl -e 0</command>. Note that this command
- does not affect auditing of SELinux AVC denials.
- </para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>
- How do I get status info about my &SEL; installation?
- </para>
- </question>
- <answer>
- <para>
- As root, execute the command <command>/usr/sbin/sestatus
- -v</command>. For more information, refer to the
- <filename>sestatus(8)</filename> manual page.
- </para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>
- How do I write policy to allow a domain to use pam_unix.so?
- </para>
- </question>
- <answer>
- <para>
- Very few domains in the SELinux world are allowed to read the
- <filename>/etc/shadow</filename> file. There are constraint rules
- that prevent policy writers from writing code like
- </para>
-<screen>
-<command>allow mydomain_t shadow_t:file read;</command>
-</screen>
- <para>
- In RHEL4 you can setup your domain to use the
- <command>unix_chkpwd</command> command. The easiest way is to use
- the <command>unix_chkpwd</command> attribute. So if you were
- writing policy for an ftpd daemon you would write something like
- </para>
-<screen>
-<command>daemon_domain(vsftpd, `auth_chkpwd')</command>
-</screen>
- <para>
- This would create a context where
- vsftpd_t -> chkpwd_exec_t -> system_chkpwd_t which can read
- <filename>/etc/shadow</filename>, while vsftpd_t is not able to
- read it.
- </para>
- <para>
- In &FC; &LOCALVER;/RHEL5, add the rule
- </para>
-<screen>
-<command>auth_domtrans_chk_passwd(vsftpd_t)</command>
-</screen>
- </answer>
- </qandaentry>
- <qandaentry id="faq-entry-local.te" xreflabel="Local Policy Customizations">
- <question>
- <para>
- In the past I have written local.te file in policy sources for my
- own local customization to policy, how do I do this
- in &FC; 5?
- </para>
- </question>
- <answer>
- <para>
- Since &FC; 5 uses a modular policy, you don't have to have the
- complete policy source any more. Now, you can just create a local
- policy module for your local policy customizations. To do this,
- follow these steps.
- </para>
- <procedure>
- <step>
- <para>
- Create a temporary directory, and change into it.
- </para>
-<screen>
-<computeroutput>$ mkdir foo
-$ cd foo</computeroutput>
-</screen>
- </step>
- <step>
- <para>
- Create empty te, if, and fc files.
- </para>
-<screen>
-<computeroutput>$ touch local.te local.if local.fc</computeroutput>
-</screen>
- </step>
- <step>
- <para>
- Edit the local.te file, adding appropriate content.
- For example:
- </para>
-<screen>
-<computeroutput>policy_module(local, 1.0)
-
-require {
- attribute httpdcontent;
- type smbd_t;
-}
-
-allow smbd_t httpdcontent:dir create_dir_perms;
-allow smbd_t httpdcontent:{ file lnk_file } create_file_perms;</computeroutput>
-</screen>
- <para>
- There are 3 parts to this file.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- The <computeroutput>policy_module</computeroutput> call
- inserts statements to make the module work, including
- declaring the module and requiring system roles, classes,
- and permissions. Make sure the name declared here (local
- in this case) matches the name you gave the file
- (local.te).
- </para>
- </listitem>
- <listitem>
- <para>
- The <computeroutput>require</computeroutput> block
- lists the symbols that this module uses that must be
- declared in other modules. In this case, we require the
- attribute <computeroutput>httpdcontent</computeroutput>
- and the type <computeroutput>smbd_t</computeroutput>.
- Note that all types and attributes you use in rules
- must be required here unless you are declaring them
- yourself below.
- </para>
- </listitem>
- <listitem>
- <para>
- The rest of the file is the policy, in this case
- consisting only of a couple of allow rules. You could
- also place type declarations, dontaudit statements,
- interface calls, or most things that can go in a normal
- te file here.
- </para>
- </listitem>
- </itemizedlist>
- </step>
- <step>
- <para>
- Build the policy module.
- </para>
+ <para>
+ Run <command>auditctl -e 0</command>. Note that this command
+ does not affect auditing of SELinux AVC denials.
+ </para>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ How do I get status info about my &SEL; installation?
+ </para>
+ </question>
+ <answer>
+ <para>
+ As root, execute the command <command>/usr/sbin/sestatus
+ -v</command>. For more information, refer to the
+ <filename>sestatus(8)</filename> manual page.
+ </para>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ How do I write policy to allow a domain to use pam_unix.so?
+ </para>
+ </question>
+ <answer>
+ <para>
+ Very few domains in the SELinux world are allowed to read the
+ <filename>/etc/shadow</filename> file. There are constraint rules
+ that prevent policy writers from writing code like
+ </para>
<screen>
-<computeroutput>$ make -f /usr/share/selinux/devel/Makefile
-Compliling targeted local module
-/usr/bin/checkmodule: loading policy configuration from tmp/local.tmp
-/usr/bin/checkmodule: policy configuration loaded
-/usr/bin/checkmodule: writing binary representation (version 5) to tmp/local.mod
-Creating targeted local.pp policy package
-rm tmp/local.mod.fc tmp/local.mod</computeroutput>
+<command>allow mydomain_t shadow_t:file read;</command>
</screen>
- <para>
- Note that this uses <command>checkmodule</command>, which is
- part of the checkpolicy rpm. So, make sure you install this
- rpm before doing this.
- </para>
- </step>
- <step>
- <para>
- Become root, and install the policy module with
- <command>semodule</command>.
- </para>
+ <para>
+ In RHEL4 you can setup your domain to use the
+ <command>unix_chkpwd</command> command. The easiest way is to use
+ the <command>unix_chkpwd</command> attribute. So if you were
+ writing policy for an ftpd daemon you would write something like
+ </para>
<screen>
-<computeroutput>$ su
-Password:
-# semodule -i local.pp</computeroutput>
+<command>daemon_domain(vsftpd, `auth_chkpwd')</command>
</screen>
- </step>
- </procedure>
- <note>
- <title>Module are uniquely identified by name</title>
- <para>
- This means that if you later insert another
- <filename>local.pp</filename>, it will
- replace the one you just loaded. So, you should keep this
- <filename>local.te</filename> around, and just add to it if you
- need to make later policy customizations. If you lose it, but
- want to keep your previous policy around, just call the new
- local policy module something else (say local2.te).
- </para>
- </note>
- </answer>
- </qandaentry>
+ <para>
+ This would create a context where
+ vsftpd_t -> chkpwd_exec_t -> system_chkpwd_t which can read
+ <filename>/etc/shadow</filename>, while vsftpd_t is not able to
+ read it.
+ </para>
+ <para>
+ In &FC; &LOCALVER;/RHEL5, add the rule
+ </para>
+<screen>
+<command>auth_domtrans_chk_passwd(vsftpd_t)</command>
+</screen>
+ </answer>
+ </qandaentry>
<qandaentry>
<question>
<para>
@@ -1418,6 +1539,28 @@
<qandaentry>
<question>
<para>
+ Where are &SEL; AVC messages (denial logs, etc.) stored?
+ </para>
+ </question>
+ <answer>
+ <para>
+ In &FC; 2 and 3, SELinux AVC messages could be found in
+ <filename>/var/log/messages</filename>.
+ In &FC; 4, the audit daemon was added, and these messages
+ moved to
+ <filename>/var/log/audit/audit.log</filename>.
+ In &FC; 5, the audit daemon is not installed by default, and
+ consequently these messages can be found in
+ <filename>/var/log/messages</filename> unless you choose to
+ install and enable the audit daemon, in which case AVC
+ messages will be in
+ <filename>/var/log/audit/audit.log</filename>.
+ </para>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
My application isn't working as expected and I am seeing
<computeroutput>avc: denied</computeroutput> messages. How do I
fix this?
@@ -1980,127 +2123,6 @@
<qandaentry>
<question>
<para>
- How can I help write policy?
- </para>
- </question>
- <answer>
- <para>
- Your help is definitely appreciated.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- You can start by joining the &FED; &SEL; mailing list. You can
- subscribe and read the archives at <ulink
- url="http://www.redhat.com/mailman/listinfo/fedora-selinux-list"/>.
- </para>
- </listitem>
- <listitem>
- <para>
- The Unofficial FAQ has some generic policy writing HOWTO
- information. Refer to <ulink
- url="http://sourceforge.net/docman/display_doc.php?docid=14882&group_id=21..."/>
- for more information.
- </para>
- </listitem>
- <listitem>
- <para>
- Another new resource is the Writing SE Linux policy HOWTO,
- located online at <ulink
- url="https://sourceforge.net/docman/display_doc.php?docid=21959&group_id=2..."/>.
- </para>
- </listitem>
- </itemizedlist>
- <para>
- Also, since the &FC; &LOCALVER; policy is based on the <xref
- linkend="faq-entry-whatis-refpolicy"/>, you should look at the
- documentation on its project page. Another excellent source of
- information is the example policy files in
- <filename>/usr/share/doc/selinux-policy-<replaceable>>version<</replaceable></filename>
- and <filename>/usr/share/selinux/devel</filename>.
- </para>
- <para>
- If you want to create a new policy domain, you can look at the
- interface files in the
- <filename>/usr/share/selinux/devel</filename> sub-directories.
- There is also a tool there to help you get started.
- The following procedure is an example:
- </para>
- <procedure>
- <step>
- <para>
- Use the <command>policygentool</command> command to generate
- your own <filename>te</filename>, <filename>fc</filename> and
- <filename>if</filename> files. The
- <command>policygentool</command> command takes two parameters:
- the name of the policy module and the full path to the
- executable. The following command gives a usage example:
- </para>
-<screen>
-<command>policygentool <replaceable>mydaemon /usr/sbin/mydaemon</replaceable></command>
-</screen>
- <para>
- It will prompt you for a few common domain characteristics,
- and will create three files:
- <filename>mydaemon.te</filename>,
- <filename>mydaemon.fc</filename> and
- <filename>mydaemon.if</filename>.
- </para>
- </step>
- <step>
- <para>
- After you generate the policy files, use the supplied
- Makefile,
- <filename>/usr/share/selinux/devel/Makefile</filename>, to
- build a policy package
- (<filename>mydaemon.pp</filename>):
- </para>
-<screen>
-<command>make -f /usr/share/selinux/refpolicy/Makefile</command>
-</screen>
- </step>
- <step>
- <para>
- Now you can load the policy module, using
- <command>semodule</command>, and relabel the executable using
- <command>restorecon</command>:
- </para>
-<screen>
-<command>semodule -i <replaceable>mydaemon.pp</replaceable></command>
-<command>restorecon -v <replaceable>/usr/sbin/mydaemon</replaceable></command>
-</screen>
- </step>
- <step>
- <para>
- Since you have very limited policy for your executable,
- SELinux will prevent it from doing much. Turn on permissive
- mode and then use the init script to start your daemon:
- </para>
-<screen>
-<command>setenforce 0</command>
-<command>service <replaceable>mydaemon</replaceable> restart</command>
-</screen>
- </step>
- </procedure>
- <para>
- Now you can collect avc messages. You can use
- <command>audit2allow</command> to translate the avc messages to
- allow rules and begin updating your
- <filename>mydaemon.te</filename> file. You should search for
- interface macros in the
- <filename>/usr/share/selinux/devel/include</filename> directory and
- use these instead of using the allow rules directly, whenever
- possible. <command>audit2allow -R</command> will attempt to find
- interfaces that match the allow rule.
- If you want more examples of policy, you could always
- install the selinux-policy src rpm, which contains all of the
- policy te files for the reference policy.
- </para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>
My console is being flooded with messages. How do I turn them
off?
</para>
@@ -2478,28 +2500,6 @@
</itemizedlist>
</answer>
</qandaentry>
- <qandaentry>
- <question>
- <para>
- Where are &SEL; AVC messages (denial logs, etc.) stored?
- </para>
- </question>
- <answer>
- <para>
- In &FC; 2 and 3, SELinux AVC messages could be found in
- <filename>/var/log/messages</filename>.
- In &FC; 4, the audit daemon was added, and these messages
- moved to
- <filename>/var/log/audit/audit.log</filename>.
- In &FC; 5, the audit daemon is not installed by default, and
- consequently these messages can be found in
- <filename>/var/log/messages</filename> unless you choose to
- install and enable the audit daemon, in which case AVC
- messages will be in
- <filename>/var/log/audit/audit.log</filename>.
- </para>
- </answer>
- </qandaentry>
</qandadiv>
<qandadiv id="faq-div-deploying-selinux">
<title>Deploying &SEL;</title>
18 years