Re: F18: Bind-chroot & Dovecot mount errors, how to fix?

[Tom Horsley]

On Wed, 23 Oct 2013 16:30:19 +1030
Tim wrote:

> Since Fedora likes to put removeable media into /var/run/username/media
> you might encounter that problem again, unless you put /var/run into its
> ignore database.

It is worse than that. It apparently doesn't store the
ignored info anywhere, because if a mountpoint appears
again then disappears again, it will warn you again
no matter what you might have told it previously.

This appears to be another case of butt-headed developers
since lots of users have asked for a way to eradicate
this "feature" but the requests are always rejected
as "user is wrong".

I think I put in a syslog rule to just filter out all the
messages since there is no practical way to make them
stop.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

X-Server fails to start

[Klaus-Peter Schrage]

Every once and a while, say in 5 out of 10 boot events, the boot process 
stalls and ends up in a text console
(kernel 3.11.4-201.fc19.x86_64, KDE 4.11.2-1, NVIDIA graphics card with 
nouveau driver):


[snip]
 Starting The KDE login manager...
[  OK  ] Started The KDE login manager.
 Starting Command Scheduler...
[  OK  ] Started Command Scheduler.
 Starting Job spooling tools...
[  OK  ] Started Job spooling tools.
 Starting Wait for Plymouth Boot Screen to Quit...
[  OK  ] Started Machine Check Exception Logging Daemon.
[  OK  ] Started Install ABRT coredump hook.
[  OK  ] Started LSB: VirtualBox Linux kernel module.
 Starting LSB: VirtualBox web service API...
 Starting LSB: VirtualBox autostart service...
 Starting LSB: VirtualBox balloon control daemon...
[  OK  ] Started LSB: VirtualBox web service API.
[  OK  ] Started LSB: VirtualBox balloon control daemon.
[  OK  ] Started LSB: VirtualBox autostart service.
[  OK  ] Started IPv6 firewall with ip6tables.
[  OK  ] Started IPv4 firewall with iptables.
[  OK  ] Started Login Service.
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started LSB: DKMS kernel modules installer service.
[FAILED] Failed to start Wait for Plymouth Boot Screen to Quit.
See 'systemctl status plymouth-quit-wait.service' for details.
 Starting Manage, Install and Generate Color Profiles...
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[end of output]

Sometimes there are a few more lines of output after FAILED, but the 
boot process always finishes around that line.


The last lines of Xorg.0.log are:

[snip]
[45.416] (II) NOUVEAU(0): NVLeaveVT is called.
[45.417] (II) NOUVEAU(0): Closed GPU channel 0
[45.447] (EE) Server terminated successfully (0). Closing log file.
[/snip]

I can get to another text console, but doing 'startx' only gives me a 
very rudimentary graphical desktop, not KDE.


I have searched bugzilla for the term 'Failed to start Wait for Plymouth 
Boot Screen to Quit' with no results, and even googling didn't produce 
anything to help me further.


Any help of the wise people on this list would be greatly appreciated.
KP
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F18: Bind-chroot & Dovecot mount errors, how to fix?

[J.Witvliet]

Uiteraard!


- Oorspronkelijk bericht -
Van: Tom Horsley [mailto:horsley1...@gmail.com]
Verzonden: Wednesday, October 23, 2013 12:15 PM W. Europe Standard Time
Aan: users@lists.fedoraproject.org 
Onderwerp: Re: F18: Bind-chroot & Dovecot mount errors, how to fix?

On Wed, 23 Oct 2013 16:30:19 +1030
Tim wrote:

> Since Fedora likes to put removeable media into /var/run/username/media
> you might encounter that problem again, unless you put /var/run into its
> ignore database.

It is worse than that. It apparently doesn't store the
ignored info anywhere, because if a mountpoint appears
again then disappears again, it will warn you again
no matter what you might have told it previously.

This appears to be another case of butt-headed developers
since lots of users have asked for a way to eradicate
this "feature" but the requests are always rejected
as "user is wrong".

I think I put in a syslog rule to just filter out all the
messages since there is no practical way to make them
stop.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

__
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet 
de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u 
verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat 
aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband 
houdt met risico's verbonden aan het electronisch verzenden van berichten.

This message may contain information that is not intended for you. If you are 
not the addressee or if this message was sent to you by mistake, you are 
requested to inform the sender and delete the message. The State accepts no 
liability for damage of any kind resulting from the risks inherent in the 
electronic transmission of messages.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F18: Bind-chroot & Dovecot mount errors, how to fix?

[Tim]

Tim:
>> Since Fedora likes to put removeable media into /var/run/username/media
>> you might encounter that problem again, unless you put /var/run into its
>> ignore database.

Tom Horsley:
> It is worse than that. It apparently doesn't store the
> ignored info anywhere, because if a mountpoint appears
> again then disappears again, it will warn you again
> no matter what you might have told it previously.
> 
> This appears to be another case of butt-headed developers
> since lots of users have asked for a way to eradicate
> this "feature" but the requests are always rejected
> as "user is wrong".

Gawd, what were they thinking?!  And I wonder what their response will
be to a blunt, "no, YOU, are wrong"?

Why should an email server program go looking for places that you might
have mail?  Surely where mail is stored is something that the admin
person ought to be configuring.

If it were an occasional removable drive change, then I could possibly
live with just ensuring that a start script was used somewhere to add in
the parameters.  But I'll just have to make sure than either the next
server I set up doesn't get things plugging into it (though I suppose
inserting a DVD-ROM into a drive is going to send it bananas, too), or I
use another IMAP server program.

Well done Dovecot programmers, what a fucking stupid thing to do.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64

All mail to my mailbox is automatically deleted, there is no point
trying to privately email me, I will only read messages posted to the
public lists.

George Orwell's '1984' was supposed to be a warning against tyranny, not
a set of instructions for supposedly democratic governments.



-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

FC19, 3.11.6-200, and ATI video

[m . roth]

I've just updated a user's FC19 box to the latest. No X. Period. I can use
xinit to get a window, but no fonts at all. Startx from init 3 gives me a
black screen.

When I look at Xorg.0.log, no matter if I have the radeon driver
blacklisted or not, whatever driver it uses is not for this kernel. The
proprietary one fails to build - as a start, it's still using
create_proc_entry.

The box has a FirePro 2260.

What can I do to get my user up and running, other than, say, installing
CentOS...?

mark

-- 
grub2 MUST DIE!!!

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F18: Bind-chroot & Dovecot mount errors, how to fix?

[Dan Thurman]

On 10/22/2013 11:00 PM, Tim wrote:

On Tue, 2013-10-22 at 11:00 -0700, Dan Thurman wrote:

dovecot complains in maillog, the following errors:
  
dovecot: master: Warning: /var/named/chroot/etc/named.root.key is no

longer mounted. See http://wiki2.dovecot.org/Mountpoints

I notice you've resolved this, but I find the information Dovecot
provides on that link, "Dovecot wants to keep track of mountpoints that
might contain emails," to be quite disturbing.  I don't think a mail
program should be behaving like that, at all.  Imagine the mess we'd be
in all sorts of programs started ploughing through the directory tree,
without being told to, just because they thought it was a good idea.

Since Fedora likes to put removeable media into /var/run/username/media
you might encounter that problem again, unless you put /var/run into its
ignore database.


(and sub-thread replies to Tim)

After dovecot restarts and a reboot, (lazarus's) bind-chroot
mountpoints warnings has not risen from the grave. ;)

Do you think the dovecot programmers read "Fedora Community"
mailing list?  I don't think so, but I could be wrong...

Why not ask dovecot.org?

I read their site and it appears that dovecot supports clustered
filesytems, *dsync, and a myriad of different things. Then I found
this:

* http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.html
(Could replication/clustering/dsync have something to do with
  detecting disk changes?)

Since I mentioned that I installed bind-chroot, installed dovecot,
then uninstalled bind-chroot, perhaps triggering dovecot to notice
a disk change (dsync) and thus generated bind-chroot mountpoint
warnings, repeatedly?  I do recall that when I installed bind-root,
dovecot did not complain and I had this running for a week or so.
The dovecot warning came after I removed bind-root.

Just something to consider...

Dan


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Can yum resume??

[David]

On 10/23/2013 2:07 AM, Joe Zeff wrote:
> On 10/22/2013 10:21 PM, David wrote:
>> Retired and on the couch does not equate with 'need my machine'. *If
>> you* have enough time to play games for days, or weeks, help yourself.
>>
> 
> It also helps, of course, that I also have a laptop running Fedora and I
> always upgrade it first.  My desktop only gets upgraded after I'm sure
> that the laptop's working properly.
> 
>> Me? I take the 'short path' and solve the problem. Your choice.
> 
> Naturally.  I wouldn't even consider trying that on a production
> machine, or even a workstation in a Linux shop.  That's why I made a
> point of stating that I'm retired and have the time, so that nobody
> would think I was suggesting that trying to recover from a failed
> upgrade is the right move for anybody else.


I don't recall if the OP, the person with the problem, said that this
was one-of-two machines. It did not read like that.

As for a 'learning experience? Perhaps. BUT IMHO Joe/Jane User wants a
machine that works not one that needs fixing. Like your car. Or
household appliances. Tools. Etc.



  David
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Can yum resume??

[David]

On 10/23/2013 2:54 AM, Javier Perez wrote:
> I agree with Joe. Some of the best learning opportunities come with the
> system is fubar :) For as long as you have another one that is working
> and the one system down is not critical, it is real fun finding out if
> you can actually resurrect it.
> Some of the best lessons I have learned have been with systems like
> that, and they have come handy in my professional life.
> 
> 
> On Wed, Oct 23, 2013 at 1:07 AM, Joe Zeff  > wrote:
> 
> On 10/22/2013 10:21 PM, David wrote:
> 
> Retired and on the couch does not equate with 'need my machine'. *If
> you* have enough time to play games for days, or weeks, help
> yourself.
> 
> 
> It also helps, of course, that I also have a laptop running Fedora
> and I always upgrade it first.  My desktop only gets upgraded after
> I'm sure that the laptop's working properly.
> 
> 
> Me? I take the 'short path' and solve the problem. Your choice.
> 
> 
> Naturally.  I wouldn't even consider trying that on a production
> machine, or even a workstation in a Linux shop.  That's why I made a
> point of stating that I'm retired and have the time, so that nobody
> would think I was suggesting that trying to recover from a failed
> upgrade is the right move for anybody else.


As I said to Joe... Some users are that. Users. Not everyone wants to be
the repairman. Or the student.


-- 

  David
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Can yum resume??

[Beartooth]

On Tue, 22 Oct 2013 15:51:52 -0400, David wrote:
[]
> Excuse me. A question or two?
> 
> You messed up an upgrade over a week ago, maybe two(?), and you still
> have no solution.

Well, actually, since September 23. (My main question at that 
time was whether the problem was in the hard- or software; and I don't 
believe I've yet gotten a definite answer.)

> How would this time spend 'broken' compare with the time it would have
> taken to copy your important files, format the drive, and install the
> never release. Then put back your files and do the tweaks?
> 
> :-)

The immediate answer is that I concur with Joe Zeff and Javier 
Perez. I'm long retired (fifteen years next month), and little concerned 
with efficiency.

I don't know about you, but besides being an autodidact, I'm 
really too old for this; I forget things, especially when backing up, 
even if I'm not interrupted. Or worse, I give bad commands and get things 
like a big file that includes a copy of itself, which includes (... , 
etc., recursively, till the drive surrendered; that time I finally did 
give up and install afresh.) When I last spent most of my time learning 
things, the PC had not been invented.

The other approach would have taken more time, been more tedious 
as well as more prone to error, and offered no chance to discover 
something useful (nor to enjoy the intellectual company of the better-
instructed). Neither would it, afaik, have told me whether my hard- or 
software need healing.

For one thing, my trifocal fingers and arthritic eyeballs slow me 
way down. For another, my CLI-foo is minuscule -- I've probably studied 
too many languages (natural, not computer-) for too long, so that now 
those memory banks are overstuffed, whether or not the eyes and fingers 
function. (Anybody want a lecture on Old High German? Minnesang? History 
of Balto-Fennic grammar?)

Also, the problem machine is my most expendable. If I succeed 
with upgrading it (as I often do, believe it or not), then I can risk 
tackling the next more important, and so up.

Having had occasional disasters with backing up, I seldom 
relinquish an old machine, and keep several largely interchangeable, so 
that when (not if) I bollix one so badly that I can't get it online, I'll 
be able to keep up my normal activities while howling aside for help. 

What's more, with several machines I can do enough of the backing 
up with a GUI instead of a CLI so that there's a much better chance I'll 
get it right. That bottom line in my .sig is what the late Goethe would 
have called "sehr ernste Scherze."

And I learn, slowly, but I do learn. I can often read a man page 
now, and even make a stab at which one to read.

Finally, I had a hunch that the downgrade would break again, but 
respond to the completion command. Bad hunch : 

[]
--> Processing Dependency: libcrypto.so.10(libcrypto.so.10) for package: 
fetchmail-6.3.22-2.fc18.i686
--> Processing Dependency: libcrypto.so.10(libcrypto.so.10) for package: 
python-libs-2.7.3-13.fc18.i686
--> Processing Dependency: libssl.so.10 for package: wget-1.14-5.fc18.i686
--> Processing Dependency: libssl.so.10 for package: 
1:qt-4.8.5-10.fc18.i686
--> Processing Dependency: libssl.so.10 for package: 2:nmap-
ncat-6.40-1.fc18.i686
--> Processing Dependency: libssl.so.10 for package: 
socat-1.7.2.2-1.fc18.i686
--> Processing Dependency: libssl.so.10 for package: 
dillo-3.0.3-1.fc18.i686
--> Processing Dependency: libssl.so.10 for package: 
stunnel-4.56-1.fc18.i686
Killed
[root@T30 ~]# yum-complete-transaction
BDB2053 Freeing read locks for locker 0x7c: 8855/3078112960
BDB2053 Freeing read locks for locker 0x7e: 8855/3078112960
BDB2053 Freeing read locks for locker 0x7f: 8855/3078112960
BDB2053 Freeing read locks for locker 0x80: 8855/3078112960
Loaded plugins: langpacks, refresh-packagekit
rpmfusion-free-
updates  | 3.3 
kB  00:00:00 
rpmfusion-nonfree-
updates   | 3.3 kB  
00:00:00 
updates/19/i386/
metalink|  18 kB  
00:00:00 
updates 
| 4.6 kB  00:00:00 
updates/19/i386/
primary_db  | 7.7 MB  
00:00:03 
(1/2): updates/19/i386/
pkgtags  | 624 kB  
00:00:01 
(2/2): updates/19/i386/
updateinfo   | 822 kB  
00:00:01 
No unfinished transactions left.
[root@T30 ~]#

Hitting it with one more hammer also failed : 

[root@T30 ~]# yum-complete-transaction --skip-broken
Loaded plugins: langpacks, refresh-packagekit
No unfinished transactions left.
[root@T30 ~]#

At this point I began trying install disks. Oddly enough, the 
first

Re: Can yum resume??

[David]

On 10/23/2013 1:12 PM, Beartooth wrote:
> On Tue, 22 Oct 2013 15:51:52 -0400, David wrote: []
>> Excuse me. A question or two?
>> 
>> You messed up an upgrade over a week ago, maybe two(?), and you 
>> still have no solution.
> 
> Well, actually, since September 23. (My main question at that time 
> was whether the problem was in the hard- or software; and I don't 
> believe I've yet gotten a definite answer.)
> 
>> How would this time spend 'broken' compare with the time it would 
>> have taken to copy your important files, format the drive, and 
>> install the never release. Then put back your files and do the 
>> tweaks?
>> 
>> :-)
> 
> The immediate answer is that I concur with Joe Zeff and Javier
> Perez. I'm long retired (fifteen years next month), and little
> concerned with efficiency.
> 
> I don't know about you, but besides being an autodidact, I'm really 
> too old for this; I forget things, especially when backing up, even 
> if I'm not interrupted. Or worse, I give bad commands and get things 
> like a big file that includes a copy of itself, which includes (... ,
> etc., recursively, till the drive surrendered; that time I finally 
> did give up and install afresh.) When I last spent most of my time 
> learning things, the PC had not been invented.
> 
> The other approach would have taken more time, been more tedious as 
> well as more prone to error, and offered no chance to discover 
> something useful (nor to enjoy the intellectual company of the 
> better- instructed). Neither would it, afaik, have told me whether
> my hard- or software need healing.
> 
> For one thing, my trifocal fingers and arthritic eyeballs slow me
> way down. For another, my CLI-foo is minuscule -- I've probably
> studied too many languages (natural, not computer-) for too long, so
> that now those memory banks are overstuffed, whether or not the eyes
> and fingers function. (Anybody want a lecture on Old High German? 
> Minnesang? History of Balto-Fennic grammar?)
> 
> Also, the problem machine is my most expendable. If I succeed with 
> upgrading it (as I often do, believe it or not), then I can risk 
> tackling the next more important, and so up.
> 
> Having had occasional disasters with backing up, I seldom relinquish 
> an old machine, and keep several largely interchangeable, so that 
> when (not if) I bollix one so badly that I can't get it online, I'll 
> be able to keep up my normal activities while howling aside for 
> help.
> 
> What's more, with several machines I can do enough of the backing up 
> with a GUI instead of a CLI so that there's a much better chance
> I'll get it right. That bottom line in my .sig is what the late
> Goethe would have called "sehr ernste Scherze."
> 
> And I learn, slowly, but I do learn. I can often read a man page
> now, and even make a stab at which one to read.
> 
> Finally, I had a hunch that the downgrade would break again, but 
> respond to the completion command. Bad hunch :
> 
> [] --> Processing Dependency: libcrypto.so.10(libcrypto.so.10) 
> for package: fetchmail-6.3.22-2.fc18.i686 --> Processing Dependency: 
> libcrypto.so.10(libcrypto.so.10) for package: 
> python-libs-2.7.3-13.fc18.i686 --> Processing Dependency: 
> libssl.so.10 for package: wget-1.14-5.fc18.i686 --> Processing 
> Dependency: libssl.so.10 for package: 1:qt-4.8.5-10.fc18.i686 --> 
> Processing Dependency: libssl.so.10 for package: 2:nmap- 
> ncat-6.40-1.fc18.i686 --> Processing Dependency: libssl.so.10 for 
> package: socat-1.7.2.2-1.fc18.i686 --> Processing Dependency: 
> libssl.so.10 for package: dillo-3.0.3-1.fc18.i686 --> Processing 
> Dependency: libssl.so.10 for package: stunnel-4.56-1.fc18.i686 Killed
> [root@T30 ~]# yum-complete-transaction BDB2053 Freeing read locks for
> locker 0x7c: 8855/3078112960 BDB2053 Freeing read locks for locker
> 0x7e: 8855/3078112960 BDB2053 Freeing read locks for locker 0x7f:
> 8855/3078112960 BDB2053 Freeing read locks for locker 0x80: 
> 8855/3078112960 Loaded plugins: langpacks, refresh-packagekit 
> rpmfusion-free- updates | 3.3 kB  00:00:00 rpmfusion-nonfree-
> updates | 3.3 kB 00:00:00 updates/19/i386/ metalink |  18 kB 00:00:00
> updates | 4.6 kB  00:00:00 updates/19/i386/ primary_db | 7.7 MB
> 00:00:03 (1/2): updates/19/i386/ pkgtags | 624 kB 00:00:01 (2/2):
> updates/19/i386/ updateinfo | 822 kB 00:00:01 No unfinished
> transactions left. [root@T30 ~]#
> 
> Hitting it with one more hammer also failed :
> 
> [root@T30 ~]# yum-complete-transaction --skip-broken Loaded plugins: 
> langpacks, refresh-packagekit No unfinished transactions left. 
> [root@T30 ~]#
> 
> At this point I began trying install disks. Oddly enough, the first 
> one enabled the brightness control; so meseems the hardware is not 
> broken yet. I'm in process of downloading a fresh DVD of CentOS 6.4; 
> this thread can be filed away. Having been through it, I plan to
> wait for F20 for my other machines, skipping F19 or perhaps running
> FedUp twice in short order 


The

Re: Can yum resume??

[Joe Zeff]

On 10/23/2013 08:40 AM, David wrote:

As for a 'learning experience? Perhaps. BUT IMHO Joe/Jane User wants a
machine that works not one that needs fixing. Like your car. Or
household appliances. Tools. Etc.


I would never suggest that J. Random User do what I did.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Can yum resume??

[Joe Zeff]

On 10/23/2013 08:44 AM, David wrote:

As I said to Joe... Some users are that. Users. Not everyone wants to be
the repairman. Or the student.


And, to repeat myself, I never said that J. Random User should do what I 
did.


Now, I have a question: what made you think that I thought that regular 
users should have to spend the time to recover from a bad upgrade 
instead of reinstalling?

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

New install, No Dual boot With Windows Vista

[Jim]

Fedora 18 new install.

Fedora didn't setup Windows Vista in boot Menu.

How do I get windows in Boot Menu.

Windows is still on Hard Drive at sda1 .

Below is /boot/grub2/grub.cfg.


#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  
c96f7e74-f54e-4399-8956-202ea476ecd9

else
  search --no-floppy --fs-uuid --set=root 
c96f7e74-f54e-4399-8956-202ea476ecd9

fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  
c96f7e74-f54e-4399-8956-202ea476ecd9

else
  search --no-floppy --fs-uuid --set=root 
c96f7e74-f54e-4399-8956-202ea476ecd9

fi
insmod gfxmenu
loadfont ($root)/boot/grub2/themes/system/DejaVuSans-10.pf2
loadfont ($root)/boot/grub2/themes/system/DejaVuSans-12.pf2
loadfont ($root)/boot/grub2/themes/system/DejaVuSans-Bold-14.pf2
loadfont ($root)/boot/grub2/fonts/unicode.pf2
insmod png
set theme=($root)/boot/grub2/themes/system/theme.txt
export theme
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora (3.11.4-101.fc18.i686)' --class fedora --class 
gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-simple-c96f7e74-f54e-4399-8956-202ea476ecd9' {

load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  
c96f7e74-f54e-4399-8956-202ea476ecd9

else
  search --no-floppy --fs-uuid --set=root 
c96f7e74-f54e-4399-8956-202ea476ecd9

fi
echo 'Loading Fedora (3.11.4-101.fc18.i686)'
linux/boot/vmlinuz-3.11.4-101.fc18.i686 
root=UUID=c96f7e74-f54e-4399-8956-202ea476ecd9 ro rd.md=0 rd.lvm=0 
rd.dm=0  rd.luks=0 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8

echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-3.11.4-101.fc18.i686.img
}
menuentry 'Fedora' --class fedora --class gnu-linux --class gnu --class 
os $menuentry_id_option 
'gnulinux-simple-c96f7e74-f54e-4399-8956-202ea476ecd9' {

load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  
c96f7e74-f54e-4399-8956-202ea476ecd9

else
  search --no-floppy --fs-uuid --set=root 
c96f7e74-f54e-4399-8956-202ea476ecd9

fi
echo'Loading Linux 3.6.10-4.fc18.i686 ...'
linux/boot/vmlinuz-3.6.10-4.fc18.i686 
root=UUID=c96f7e74-f54e-4399-8956-202ea476ecd9 ro rd.md=0 rd.lvm=0 
rd.dm=0  rd.luks=0 vconsole.keymap=us rhgb quiet

echo'Loading initial ramdisk ...'
initrd/boot/initramfs-3.6.10-4.fc18.i686.img
}
submenu 'Advanced options for Fedora' $menuentry_id_option 
'gnulinux-advanced-c96f7e74-f54e-4399-8956-202ea476ecd9' {
menuentry 'Fedora, with Linux 3.6.10-4.fc18.i686' --class fedora 
--class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-3.6.10-4.fc18.i686-advanced-c96f7e74-f54e-4399-8956-202ea476ecd9' 
{

load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root 
--hi

Fedora 19 screensaver

[Roger]

Since updating last week the Fedora 19 screensaver is causing me grief.
I have it off and time delay set to never but it blanks the screen and 
defaults to a time display after 30+ minutes , on any key press it gives 
the login dialog which cannot be accessed either by tab key or mouse so 
there is no way to log in.
Ctrl Alt F2 gives me a new user I log in as me and startx to bring up 
gnome then shut down and restart.


Googling shows it's difficult to get rid of the screensaver.

That's half the problem and raises a peripheral question.

I am developing an app on Heroku. Have had access until Tuesday evening 
at which time starting heroku produces 30 of the below errors. Same in 
accessing Heroku logs.


Error:   SSL_connect returned=1 errno=0 state=SSLv3 read server key 
exchange B: EC lib (OpenSSL::SSL::SSLError) (Excon::Errors::SocketError)
Backtrace: 
/home/Desktop/.rvm/gems/ruby-2.0.0-p0/gems/excon-0.16.10/lib/excon/ssl_socket.rb:60:in 
`connect'
/home/Desktop/.rvm/gems/ruby-2.0.0-p0/gems/excon-0.16.10/lib/excon/ssl_socket.rb:60:in 
`initialize'

 
/home/Desktop/.rvm/gems/ruby-2.0.0-p0/gems/excon-0.16.10/lib/excon/connection.rb:364:in
 `new'

To the question:
Because access to desktop fails due to faulty screensaver, I did a Crtl 
Alt F2 to a fresh login, startx to bring up the desktop.

In a terminal  typed the commands to start heroku and got the above error/s.

Can it be that in starting a new login and desktop it messed up access 
to ssh keys and could this be the cause of the heroku error regime.

If so what can be done to resolve the issue?
If not, what then? I have posted on Github as heroku requires.
I note on Github there are an increasing number of similar complaints 
and google is rife with these also.


What's the difference if any between my pc's ssh keys and the rsa-keygen 
keys? in the .ssh directory?
I generated a new rsa.pub key and entered that in Heroku but it did not 
resolve the issue.


I'm most curious about this and how to guard against it for the future.

Thank you in advance
Roger
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

SOLVED: New install, No Dual boot With Windows Vista

[Jim]

On 10/23/2013 06:44 PM, Jim wrote:

Fedora 18 new install.

Fedora didn't setup Windows Vista in boot Menu.

How do I get windows in Boot Menu.

Windows is still on Hard Drive at sda1 .

Below is /boot/grub2/grub.cfg.


#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 
--hint='hd0,msdos2'  c96f7e74-f54e-4399-8956-202ea476ecd9

else
  search --no-floppy --fs-uuid --set=root 
c96f7e74-f54e-4399-8956-202ea476ecd9

fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 
--hint='hd0,msdos2'  c96f7e74-f54e-4399-8956-202ea476ecd9

else
  search --no-floppy --fs-uuid --set=root 
c96f7e74-f54e-4399-8956-202ea476ecd9

fi
insmod gfxmenu
loadfont ($root)/boot/grub2/themes/system/DejaVuSans-10.pf2
loadfont ($root)/boot/grub2/themes/system/DejaVuSans-12.pf2
loadfont ($root)/boot/grub2/themes/system/DejaVuSans-Bold-14.pf2
loadfont ($root)/boot/grub2/fonts/unicode.pf2
insmod png
set theme=($root)/boot/grub2/themes/system/theme.txt
export theme
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora (3.11.4-101.fc18.i686)' --class fedora --class 
gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-simple-c96f7e74-f54e-4399-8956-202ea476ecd9' {

load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 
--hint='hd0,msdos2' c96f7e74-f54e-4399-8956-202ea476ecd9

else
  search --no-floppy --fs-uuid --set=root 
c96f7e74-f54e-4399-8956-202ea476ecd9

fi
echo 'Loading Fedora (3.11.4-101.fc18.i686)'
linux/boot/vmlinuz-3.11.4-101.fc18.i686 
root=UUID=c96f7e74-f54e-4399-8956-202ea476ecd9 ro rd.md=0 rd.lvm=0 
rd.dm=0  rd.luks=0 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8

echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-3.11.4-101.fc18.i686.img
}
menuentry 'Fedora' --class fedora --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-c96f7e74-f54e-4399-8956-202ea476ecd9' {

load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 
--hint='hd0,msdos2' c96f7e74-f54e-4399-8956-202ea476ecd9

else
  search --no-floppy --fs-uuid --set=root 
c96f7e74-f54e-4399-8956-202ea476ecd9

fi
echo'Loading Linux 3.6.10-4.fc18.i686 ...'
linux/boot/vmlinuz-3.6.10-4.fc18.i686 
root=UUID=c96f7e74-f54e-4399-8956-202ea476ecd9 ro rd.md=0 rd.lvm=0 
rd.dm=0  rd.luks=0 vconsole.keymap=us rhgb quiet

echo'Loading initial ramdisk ...'
initrd/boot/initramfs-3.6.10-4.fc18.i686.img
}
submenu 'Advanced options for Fedora' $menuentry_id_option 
'gnulinux-advanced-c96f7e74-f54e-4399-8956-202ea476ecd9' {
menuentry 'Fedora, with Linux 3.6.10-4.fc18.i686' --class fedora 
--class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-3.6.10-4.fc18.i686-advanced-c96f7e74-f54e-4399-8956-202ea476ecd9' 
{

load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no

Re: Fedora 19 screensaver

[Joe Zeff]

On 10/23/2013 03:44 PM, Roger wrote:


Googling shows it's difficult to get rid of the screensaver.


Back when I used Gnome 2, I preferred xscreensaver to gnome-screensaver. 
 It took a while, but I finally learned that there was only one way to 
stop gnome-screensaver from starting:


yum remove gnome-screensaver
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Can yum resume??

[David]

On 10/23/2013 3:22 PM, Joe Zeff wrote:
> On 10/23/2013 08:44 AM, David wrote:
>> As I said to Joe... Some users are that. Users. Not everyone wants to be
>> the repairman. Or the student.
> 
> And, to repeat myself, I never said that J. Random User should do what I
> did.
> 
> Now, I have a question: what made you think that I thought that regular
> users should have to spend the time to recover from a bad upgrade
> instead of reinstalling?


You are in this thread where almost everyone is telling this older
gentleman all of these cryptic, CLI, commands. Blasting him with 'this
command' and 'that command' that he has already said that he has a
problems with understanding and typing. It's normally called "solving a
problem with a shotgun".

Not saying that you did ... but I have always had a problem with advice
that starts out with "try this" and ends with "it might work".  :-)

And as *I* said it takes me 15-20 minutes to download the DVD and maybe
20-30 minutes to format and install it. And yes it does take some time
to reconfigure 'things' to get everything back.

The OP said 'since Sept 23. That is 28-29 days. What do you think?
minutes? Or days?
-- 

  David
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Can yum resume??

[Joe Zeff]

On 10/23/2013 06:10 PM, David wrote:

Not saying that you did ... but I have always had a problem with advice
that starts out with "try this" and ends with "it might work".  :-)


When it comes to fixing upgrades that don't work, the first piece of 
advice should be to make sure that you have a recent backup, and if you 
don't, do what you can to preserve as much of your data as possible. 
(If you can't, that too is a learning experience, but one we'd rather 
you don't go through.)  And, the whole idea of "it might work" 
suggestions is that if they do work, it's faster than a reinstall and if 
it doesn't, all you've lost is time.  And of course, if this is a 
production machine and time is the one thing you don't have, a clean 
install may well be your only choice.


One of the problems with this type of support is that those of us 
offering help only have a limited knowledge of your situation and in 
many cases, it's hard to narrow things down enough to be sure that what 
you tell somebody to do is the right thing.  Thus, you sometimes have to 
tell them how to recover, provided that you've guessed right about what 
happened, and hope that your guess wasn't too far off.  That's why I'll 
sometimes ask questions about odd possibilities: I'm trying to narrow 
down the choices.  (As an example, I'll often ask questions about 
hardware because it can save lots of time if that turns out to be the 
issue, and doesn't really waste any if it isn't.)

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Can yum resume??

[David]

On 10/23/2013 9:49 PM, Joe Zeff wrote:
> On 10/23/2013 06:10 PM, David wrote:
>> Not saying that you did ... but I have always had a problem with advice
>> that starts out with "try this" and ends with "it might work".  :-)
> 
> When it comes to fixing upgrades that don't work, the first piece of
> advice should be to make sure that you have a recent backup, and if you
> don't, do what you can to preserve as much of your data as possible. (If
> you can't, that too is a learning experience, but one we'd rather you
> don't go through.)  And, the whole idea of "it might work" suggestions
> is that if they do work, it's faster than a reinstall and if it doesn't,
> all you've lost is time.  And of course, if this is a production machine
> and time is the one thing you don't have, a clean install may well be
> your only choice.



Agree. The problem with "it might work" you answered yourself in the
next paragraph. As for 'saving your data'? Whatever happened to backups
and 'other places'? I have some valubal 'stuff' on my computer. Valuable
enough that I also hat it in three other places.



> One of the problems with this type of support is that those of us
> offering help only have a limited knowledge of your situation and in
> many cases, it's hard to narrow things down enough to be sure that what
> you tell somebody to do is the right thing.  Thus, you sometimes have to
> tell them how to recover, provided that you've guessed right about what
> happened, and hope that your guess wasn't too far off.  That's why I'll
> sometimes ask questions about odd possibilities: I'm trying to narrow
> down the choices.  (As an example, I'll often ask questions about
> hardware because it can save lots of time if that turns out to be the
> issue, and doesn't really waste any if it isn't.)


As I said. It is *much, much faster* for me to download the new release
DVD and format and reinstall and then reconfigure than to roll the dice
and hope for a successful upgrade.

As for stuff like 'my sound doesn't work'? Yeah work on that.

But the problem there is that are thousands and thousands of computers
out there. And the 'same computer' bought from 'the same store' might
not be exactly the same as the the same computer that you have bought at
a different time from a different store.

As for laptops? The same two on the same shelf in the same store could
very well be different from the one next to it.

An honest observation? My point of view?

Grandma/pa want to email the grand kids. To view the web for news
perhaps. Then use Skype. Other things. They do not, IMO, want to type
'stuff' to get things to 'just work'.

Which is what I see from that base disto whose name begins with a 'U'.
Really? Yeah. I had an old friend from almost 25 years ago beg me to
join their user list. I won't name the distros but I see people that I
have not seen 'around' for years.

IMHO? If 'you' want Linux to be accepted as a 'real' OS/Desktop by the
general public? It has to work without all of the really cool Linux
geeky crap that Linux zealots love so much.

You have a great day.

-- 

  David
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedora 19 screensaver

[Andre Robatino]

Roger  bigpond.com> writes:

> Since updating last week the Fedora 19 screensaver is causing me grief.
> I have it off and time delay set to never but it blanks the screen and 
> defaults to a time display after 30+ minutes , on any key press it gives 
> the login dialog which cannot be accessed either by tab key or mouse so 
> there is no way to log in.

If you have both GNOME and Cinnamon installed and are seeing this in GNOME,
it's already fixed in the latest F19 updates. It was discussed in
https://lists.fedoraproject.org/pipermail/users/2013-October/441728.html .





-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

F19: rendering blender images

[Hiisi]

Hi, list!
Having problem rendering images in blender on F19 desktop.
Following the tutorial [1] I'm trying to achieve this:
http://www.blenderguru.com/wp-content/uploads/2010/08/71-withambient-540x337.png
But got only this:
http://imageshack.us/photo/my-images/541/pfl1.jpg/
Whatever I render I get the same result - ugly pictures. Is there something
wrong with fedora blender build? How do I fix it?
System information:
$ rpm -q blender
blender-2.68a-5.fc19.x86_64
$ uname -r
3.11.4-201.fc19.x86_64

TIA

REFERENCES:
1. http://www.blenderguru.com/create-a-shiny-new-wallpaper/

-- 
Hiisi.
Registered Linux User #487982. Be counted at: https://linuxcounter.net/
--
Spandex is a privilege, not a right.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org