If you do not wish to be subscribed to this list, please simply disregard this message. If you think you are being maliciously subscribed to the list, or have any other questions, send them to fedora-devel-list-owner@redhat.com.
To confirm the subscription, click on the link or send a reply email without editing the subject line. You'll receive a confirmation emaiclass="underline"
Welcome to the fedora-devel-list@redhat.com mailing list!
To post to this list, send your email to:
fedora-devel-list@redhat.com
General information about the mailing list is at:
https://www.redhat.com/mailman/listinfo/fedora-devel-list
If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at:
https://www.redhat.com/mailman/options/fedora-devel-list/chris%40fedorabook.com
You can also make such adjustments via email by sending a message to:
fedora-devel-list-request@redhat.com
with the word \Qhelp' in the subject or body (don't include the quotes), and you will get back a message with instructions.
You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is:
superSecret
Normally, Mailman will remind you of your redhat.com mailing list passwords once every month, although you can disable this if you prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a button on your options page that will email your current password to you.
Keep this email! To unsubscribe or change your digest option, go to the link contained in this message and enter your chosen password.
9.1.1.1. Posting on the mailing list
When posting messages on the mailing list, you must send from the same address that you used to subscribe to the list, or your message will be rejected.
Since your message will be read by hundreds or even thousands of people around the world, succinct, detailed, and informative messages are highly regarded, and off-topic and time-wasting messages are disparaged. This doesn't mean that you have to be an expert to post; most lists welcome messages from community members of all skill levels. Since most list members will only ever know you by your writing, the quality of that writing plays a key role in establishing your reputation within the community.
Start your message with a clear subject line (remember that your messages are being archived by topic). "ACPI problem with Kernel 2.6.43" is a good title; "Power problem" is too vague, and "Please help!" is completely uninformative.
The body of your message should contain a concise comment, suggestion, request for help, or announcement. Write in plain text; avoid the use of HTML, which bloats the message, since that bloat will be multiplied by the hundreds or thousands of inboxes in which your message will take residence. Tiny code fragments or extracts from logfiles or configuration files that illuminate the discussion should be included; long portions of code, screenshots, logfiles, complete configuration files, or sample data should be posted on the Web with a link to them included in your message.
Be sure to review any logfiles, configuration files, or screenshots for confidential information before posting them publicly.
When replying to a previous posting in nondigest mode, leave enough of the previous poster's comments as a quotation so that the reader will know what you're replying to. Place your reply at the end of the quoted text:
Mary Eleanor wrote:
> When I change the hostname, I can't open
> new windows on the GUI display. Does anyone
> know what causes this?
It's due to the fact that the new hostname breaks the cross-reference to authorization information ("magic cookies") in the ~/.Xauthority file. Before you change the hostname, execute this command:
xhost +localhost
That will turn off authorization checking for GUI programs on the same computer as the display.
Signature blocks are welcome, but should not exceed four lines in total; one or two lines is ideal. Bear in mind that any information you post will be permanently and publicly archived, so think carefully about any personal information (phone numbers, place of employment, instant messaging IDs) revealed in your signature block.
If you are replying to a message that is part of a digest, it is important to edit your reply so that the subject line relates to the message to which you are replying and not to the entire digest. For example, here is the first part of a digest message on the fedora-devel-list :
From: fedora-devel-list-request@redhat.com
Reply-to: fedora-devel-list@redhat.com
To: fedora-devel-list@redhat.com
Subject: fedora-devel-list Digest, Vol 20, Issue 40
Date: Thu, 27 Oct 2005 08:38:38 -0400 (EDT)
Send fedora-devel-list mailing list submissions to fedora-devel-list@redhat.com
To subscribe or unsubscribe via the World Wide Web, visit https://www.redhat.com/mailman/listinfo/fedora-devel-list or, via email, send a message with subject or body 'help' to fedora-devel-list-request@redhat.com
You can reach the person managing the list at fedora-devel-list-owner@redhat.com
When replying, please edit your Subject line so it is more specific than "Re: Contents of fedora-devel-list digest..."
Today's Topics:
1. Re: Problems installing rawhide and reporting thereof
2. Re: Problems installing rawhide and reporting thereof
3. Re: Problems installing rawhide and reporting thereof
4. Re: Problems installing rawhide and reporting thereof
5. Re: Encouraging the use of multiple packaging systems on one systems, and the resulting problems
6. initrd stage: CAP_SYS_RAWIO on /dev/iscsictl fails . help
7. Re: rawhide report: 20051025 changes
8. Re: initrd stage: CAP_SYS_RAWIO on /dev/iscsictl fails . help
9. rawhide report: 20051027 changes (Build System)
10. UTF-8 & imap folder name handling
If you reply to the digest, the subject line will read "Re: fedora-devel-list Digest, Vol 20, Issue 40." Change this to the subject of the particular posting to which you are replying; for example, if you are replying to message 10, set the subject to "Re: UTF-8 & imap folder name handling."