PDA

View Full Version : Park the F14 (stuff) here.


Dan
1st August 2010, 07:33 PM
Just like it says. Due to popular demand ... an F14 forum.

mh3rn4nd3z3
1st August 2010, 10:50 PM
lol. popular demand? you mean one user? :p

bob
1st August 2010, 11:12 PM

Well sir, back when I was a pup, we had to walk up hill 5 miles to school. both ways, then hunt our food and then our women. We also did a new version sub-Forum once the Alpha was released. But that was back in the "oughts" not in the "tens". Times are changin'.

smr54
2nd August 2010, 12:01 AM
Meh, you should wait till mirrors.kernel.org has isos. Naw, get it done now, then it won't have to be done then, better idea.

It's a bit confusing right now though--rawhide *is* showing F15, I see a particular bug I ran into (selinux preventing wireless, at least if one uses wpa_supplicant rather than NM), got closed and they're saying it's in rawhide--not sure if they meant a patch or the bug. (I posted a query to the bug and will probably have an answer to that question soon.)

GoinEasy9
2nd August 2010, 01:53 AM
There's a TC1 iso for F14:
http://serverbeach1.fedoraproject.org/pub/alt/stage/
... did someone fix systemd?
BTW - fedora-release-14 is currently pointing its repos to rawhide, and I haven't been able to upgrade in rawhide for 3 days due to the python mess. If F14 TC1 installs, it would have to be a magical iso.

tox
2nd August 2010, 02:13 AM
http://serverbeach1.fedoraproject.org/pub/alt/stage/14.TC1/Fedora/i386/iso/

http://serverbeach1.fedoraproject.org/pub/alt/stage/14.TC1/Fedora/x86_64/iso/

no LiveCD :(

smr54
2nd August 2010, 03:09 AM
For what it's worth @Goingeasy, doing a minimal install of F13, then upgrading to rawhide, today, gave me no problems with systemd, at least as far as booting. After upgrading to rawhide, though, there are still several issues--I didn't stop at F14, just put in F13, added the rawhide repo, did an update, which gave me F14, did another update an hour later which put me in F15.

In F15, though systemd doesn't stop it from booting, SELinux prevents wpa_supplicant from being started as a service (don't know about NetworkManager), and the sluggish mouse is still there, though I don't see any 100% (or even especially high) CPU usage. Other things too, such as shutting down or rebooting gives errors.

So---for those of you working with F14.

If any of you are booting into text mode, or least using wpa_supplicant rather than NM or wicd, is SELinux giving you errors? Is X working well, including the mouse? Are you able to shutdown and reboot without errors?

(I may be able to give the answers myself later in the week, but probably not for a few days.)

Dan
2nd August 2010, 04:45 AM
Hmmm.

Methinks it sounds as if I hast shat in church.

I'll leave it up to Bob to re-activate this whence he is dang good and ready. <..:p..>