observations on "Managing Software with yum"
by Robert P. J. Day
might as well collect my observations on
http://docs.fedoraproject.org/yum/en/index.html
section 1.3: might mention that "tsclient" can also be invoked just
from the command line, not only from the menus
section 2.2: "To view a list of all of the available package groups
for your Fedora system, run the command su -c 'yum grouplist'. "
- i don't believe just getting a yum grouplist requires root access,
and i'd avoid typing "su -c" where it's technically not required.
section 4.1: if you're going to mention "yum groupinstall", it might
be useful to also mention "yum groupinfo", unless you cover that
later. (i notice you do cover "yum groupupdate" and "yum groupremove"
just a bit farther down the page.)
section 5.1: again, i would avoid prefixing commands with "su -c"
that don't require it.
i also don't see any mention of "yum info" on that page, which i find
handy, particularly with wildcard patterns.
section 5.2: the example of "yum provides libneon" might emphasize
that that search covers only installed packages, no?
more later, possibly.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca
Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook
========================================================================
16 years, 2 months
FDSCo results
by Karsten Wade
With a slight delay for the holidays to get the results :), the
following persons will be staying or joining the Fedora Documentation
Steering Committee (FDSCo):
Bart Couvreur
John Babich
Jared Smith
Congratulations to those chosen. All candidates are doing great work in
Fedora Docs, and by virtue of that are already leaders within the
project. When we next have a round of formal elections, I hope you all
consider running again.
We'll have our first FDSCo meeting after the new year.
Members - let's work out a meeting time. To start, we need to refresh
our matrix:
http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/MeetingTimeMa...
You can refer to the old one[1] for what you put in last time. Our goal
is to pick a meeting time or two; we can alternate between then, if that
works. Another option is to have two meetings a month and do more
preparation and work in them. Open for discussion!
Thanks - Karsten
[1] http://fedoraproject.org/wiki/BobJensen/MeetingTimes
--
Karsten Wade, Developer Community Mgr.
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org
gpg key : AD0E0C41
16 years, 2 months
Delineation: document vs application
by George (Skip) VerDuin
I have run into an issue needing an assignment to the most appropriate
group for resolution -- it may be an application or documentation issue.
As a matter of background, I've been following this reflector for many
months but have not submitted a formal self intro... I'm sorry that I
don't already know the answer to my question.
Specific to the task of hooking up klamav to evolution while in the KDE
desktop environment [to filter out virus laden incoming mail] I ran into
an ambiguity that hinders my administrative work. The reference
document I used is provided as a text window by klamav that is specific
to this task. My resultant setup in evolution leaves me wondering if I
have correctly set up the interface and quite frankly I suspect I have
done it wrong... I am reserving the detail of the issue, it is in the
form of two screen shots plus my narrative.
Rather than resolving the problem here on the reflector, I am asking
whether this qualifies as a bug for the application or if this fits
within the documentation domain. After watching this reflector, I am
not clear which team on-line pop-up window material falls into.
I would be pleased to collaborate with the author of the window text to
remove the ambiguity no matter which group takes the lead.
Warmest regards from here, thanks up front for your consideration.
George
16 years, 2 months
RE: Request for Review: Using FireGPG
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I submitted this document for review on 03 Jan 2008. Thanks to the help of couf and mwiriadi on IRC this morning I was able to structure the document a bit better and feel it is ready for the main stream.
Please look over the document and see if everything flows. I'd also like for someone to try the steps and validate the procedure.
This page should be linked from http://fedoraproject.org/wiki/DocsProject/UsingGpg which hopefully will put my document into better context.
Thanks,
Eric
>http://fedoraproject.org/wiki/Docs/Drafts/WithFireGPG
>
>I started this page yesterday before finding all the information on joining
>the documentation team and how to PROPERLY submit a work. Sorry...
>
>I have started a page with instructions on installing and setting up FireGPG
>which is a Firefox extension that allows users to sign and encrypt e-mail
>messages when using a webmail client. It was actually specifically designed
>to integrate with Gmail but also works with other webmail products (really any
>time you need to sign and/or encrypt text you can use the extension).
>
>I haven't added the information for using it with webmail clients other than
>Gmail but what is there should be correct. I'd appreciate someone verifying
>the information.
>
>Thanks,
>Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: http://firegpg.tuxfamily.org
iD8DBQFHhjl0L5V8yddJCO0RAt5ZAJ0WmRGpNtk+DHvHZB5KgYmMMWnvzQCeNPlr
tuANIgm8qOO/biF7kvnNTbA=
=0NWu
-----END PGP SIGNATURE-----
16 years, 2 months
DUG
by dan@new2linux.com
Hello all,
It's been a busy couple weeks and I haven't had much time to get much
work done on the DUG. I'm going on a business trip for a couple days and
had planned on spending the weekend catching up on the DUG. IIRC there
was talk of having the DUG complete by sometime next week? What needs to
be done?
Regards,
Dan O'Brien
16 years, 2 months
nfs section /etc/sysconfig/nfs
by Murray McAllister
Hi,
I was taking a look at the NFS section, and found at the start
"Firewall rules are configured to allow for the proper port access".
The section is marked edit ready, which is why I'm asking before
doing, but would it be worthwhile documenting /etc/sysconfig/nfs?
Otherwise it is hard to configure firewall rules since portmap assigns
ports dynamically. I have recently done the content for work, so it
wouldn't be hard to add some of the details into the wiki...
Thanks,
Murray.
------------------------------------------------------------------------------------------------
pub 1024D/81B3FDEB 2007-09-19 [expires: 2008-09-18]
Key fingerprint = 4ED9 9907 5BF0 4132 2B46 20D1 C0C6 362D 81B3 FDEB
Murray McAllister (Fedora Docs Project / mdious) <murray.mcallister(a)gmail.com>
sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]
16 years, 2 months
Re: SELinux in guides [was: Self-Introduction: Eric Christensen]
by Murray McAllister
On Jan 5, 2008 3:39 AM, Karsten Wade <kwade(a)redhat.com> wrote:
> On Thu, 2008-01-03 at 17:01 -0500, Eric Christensen wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Eric H. Christensen
> > Newport News, VA USA
> > Information Assurance Analyst
> > Honeywell Technology Solutions Inc
>
> Welcome Eric.
>
> Let us know (via this list) if you run into any issues with getting
> signed up for accounts or figuring out what to do or where to go.
>
> The carpenter's roof is leaking a bit, but we're working on it. :)
>
> > * Your goals in the Fedora Project
> > o What do you want to write about? Security mostly but I'll write
> > about anything because it helps me learn!
>
> That is very true. You should have seen my security knowledge when I
> started tracking SELinux development as a tech writer. :)
>
> If you are interested, I think our in-progress Fedora Administration
> Guide (AG) could use a fresh look at these two areas:
>
> * Big view -- make sure that overall the document is consistent and
> promotes good security practices that use Fedora-packaged solutions.
>
> * Focused view -- what is missing? Can we merge the SELinux content
> into the AG? What about all those blog posts from Dan Walsh? What
> other security content can we cover?
Hi,
I am trying to fix the dns section I wrote so it reflects using an RPM
instead of a tarball. I have only gotten around to one little section
regarding selinux, but I am going to include how to set the correct
context for each file/folder created.
I think it would be good to merge selinux into each section (if
applicable), considering it is shipped and enabled by default, instead
of making people look all over the place.
Regards,
Murray.
------------------------------------------------------------------------------------------------------------------
pub 1024D/81B3FDEB 2007-09-19 [expires: 2008-09-18]
Key fingerprint = 4ED9 9907 5BF0 4132 2B46 20D1 C0C6 362D 81B3 FDEB
Murray McAllister (Fedora Docs Project / mdious) <murray.mcallister(a)gmail.com>
sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]
16 years, 2 months
KDE critique (DUG)
by Marc Wiriadisastra
Hey All,
I had a quick chat to Rex about the DUG and he's going to post to the
KDE SIG to see if someone is willing to work with us to make sure the
KDE parts are all correct.
Since with F-9 XFCE will actually be a spin we will need to consider the
default XFCE settings etc. Can someone email whoever takes care of the
package or if there is a SIG the SIG so we can liase with them.
I'm hoping to make the DUG more inclusive so users won't have to try and
figure out whats going on.
[offtopic] The selinux guide I will work on but my main priority right
now is the DUG unless someone wants to finish it off reasonably quick so
I can start work on the selinux guide. :) [/offtopic]
Cheers,
Marc
P.S. Dan I also said they could contact you if needed. If I receive
anything I'll forward it to the mailing list. I did advise them to try
and mail to the mailing list and use us as a backup option. (probably
the wrong thing to do)
16 years, 2 months