"Anuj Srivastava""I love Fedora""Kulbir Saini""Proyecto Fedora Chile""Rafael Gomes""Rodrigo Padula"Aanjhan RanganathanAaron S. HawleyAbhishek SinghAcedip "Anirudh Singh Shekhawat"Adam JacksonAdam MillerAdam StokesAdam WilliamsonAdrian AlonsoAdrian LikinsAdrian ReberAjay KallaAlejandro AcostaAlejandro PérezAlex HudsonAlexander "dreamer" C.Alexander KurtakovAlexandru SzaszAlexey TorkhovAllisson AzevedoAmit ShahAmit ShahAndreas "ixs" ThienemannAndrew OverholtAndrew Vermilya JamisonAndy PriceAni PeterAnkur ShrivastavaAnkur Sinha - franciscodAnthony GreenArindam GhoshArmin MoradiAron XuArun SAGAsgeir FrimannssonAurélien BompardAyrton "Freeman" AraújoBalaji GBastien NoceraBehdad EsfahbodBen BoeckelBen SkeggsBen WilliamsBenjamin (tc1415) LewisBert "biertie" DesmetBrian PeppleBrian PowellBryan ClarkBryan KearneyCaius 'Kaio' ChanceCallum LerwickCamilo "Hilillos" JiménezCaolán McNamaraCarlo Raudino (piu' e meno)Carlos (casep) SepulvedaCarlos Vassalo (opossum1er)Casey DahlinCharles PengCharlie BrejChitlesh GoorahChris BallChris BrownChris TylerChristoph WickertChristopher AillonChristos BacharakisClint SavageCole RobinsonColin WaltersDale BewleyDan HorákDan WalshDan WilliamsDaniel BerrangeDaniel Berrange (Coding Tips)Daniel BrunoDaniel VeillardDanishka NavinDarren VanBurenDave AirlieDave JonesDavid CantrellDavid DuncanDavid LutterkortDavid MalcolmDavid NalleyDavid WoodhouseDebarshi RayDeepak BholeDeependra Singh ShekhawatDennis GilmoreDevan GoodwinDiaa RadwanDiana MartinDiego Búrigo ZacarãoDimitris GlezosDing-Yi ChenDodji SeketeliDouglas E. WarnerDwayne Bailey (Translate.org.za)Edward KaravakisEelko BerkenpiesElliott BaronEngels AntonioEric "Sparks" ChristensenEric KerbyErick GoesFOSS DocsFabian AffolterFedora AnnouncementsFedora ArgentinaFedora Indonesia (Fedora-Id)Fedora MexicoFedora PhilippinesFedora TunisiaFedora University TourFedora VenezuelaFedora VideosFedora-ARMFedora-NicaraguaFelix KaecheleFergatROnFernando "dib" GonzalezFrancesco CrippaFrancesco UgoliniFrederic HornainFujisanGary BensonGerard BraadGianluca SfornaGianluca VariscoGino AlaniaGiovanni P. TirloniGlauber "glommer" CostaGong HanGreg DeKoenigsbergGuillaume KulakowskiGuillermo Gómez (Gomix)Hans de GoedeHarald HoyerHarish Pillay 9v1hpHedayat VatankhahHeherson PagcaliwaganHenrik HeiglHenrique "LonelySpooky" JuniorIan WellerIarly selbir | ski0sIgnacio Vazquez-AbramsIl Cappello BluIngvar HagelundIonuț Arțăriși (mapleoin)Ismael OleaIvan Fernandez CidIzhar FirdausJack AboutboulJakub HrozekJames AntillJames BowesJames LaskaJames MorrisJared SmithJaroslav ReznikJason DobiesJasper CapelJef SpaletaJeff SandysJeff SaucierJeff SheltrenJeffrey C. OllieJeffrey C. OllieJeffrey C. OllieJeffrey TadlockJens PetersenJeremy KatzJeroen van MeeuwenJesse KeatingJesus Rodriguez (zeus)JoergSimonJohan CwiklinskiJohn (J5) PalmieriJohn BabichJohn EckersbergJohn McDonoughJohn PoelstraJohn5342Jon MastersJon StanleyJon StanleyJonRobJonathan DieterJonathan SteffanJonathan Steffan (Fedora Unity)Jorge "kad" GallegosJose M ManimalaJoseph SmidtJosh BoyerJosh BressersJuanjo MartínezJuank PradaJulian AloofiJustin M. ForbesKairo AraujoKamil PáralKarsten HoppKarsten WadeKeiran "Affix" SmithKevin FenziKevin HigginsKevin LisciottiKevin VermaKishan GoyalKomaragiri SatyaKonstantin RyabitsevKostas AntonakoglouKristian HøgsbergKushal DasKyle McMartinLarry CafieroLennart PoetteringLiang SuilongLicio FonsecaLillian AngelLorenzo VillaniLubomir RintelLuca BottiLuca FoppianoLuis VillaLuke MackenLuya TshimbalangaLydia BossersMagie AntonioMarcela MašláňováMarco Emanuel PalazzottiMarco MornatiMarek MahutMaria "tatica" LeandroMark J CoxMark J. WielaardMark McLoughlinMartin SouradaMary Ellen FosterMathieu Bridon (bochecha)Matt "LinuxKnight" McKenzieMatt DomschMatthew DanielsMatthew GarrettMatthias SummerMax SpevackMaxime CarronMel ChuaMichael BeckwithMichael DeHaanMichael FlemingMichael StahnkeMichael TiemannMichel SalimMike McGrathMirlan IpasovMohit SethiMola PahnadayanMostafa DaneshvarMurray McAllisterMáirín DuffyNate StrazNeville A. Cross - YN1VNicu BuculeiNigel JonesNihad Abbasov aka NARKOZOron PeledOwen TaylorPanu MatilainenPascal CalarcoPatrick W. BarnesPaul MellorsPaul NasratPaul W. FrieldsPavol RusnakPeter GordonPeter HuttererPeter JonesPeter LemenkovPhil MuldoonPierros PapadeasPravin SatputeProjeto Fedora BrasilRadek VokálRafael LiuRahul BhaleraoRahul SundaramRajeesh K NambiarRajesh RanjanRakesh PanditRangeen Basu Roy ChowdhuryRawhide WatchRay ChenRay StrodeRay Van DolsonRed Hat Magazine FeedRemi ColletRex DieterRia DasRichard FearnRichard HughesRichard W.M. JonesRobert 'Bob' JensenRobert TillerRodrigo MenezesRoland WoltersRoozbeh PournaderRuna BhattacharjeeRussell HarrisonRussell JohnRyan LerchRyan Rix "PhrkOnLsh"Sandro MathysSankarshanSatyajit RanjeevSayamindu DasguptaSebastian CobaledaSebastian DziallasSeth vidalShakthi KannanShawn StarrShreyank GuptaSilas SewellSimon WespStefan PosdzichStephen SmoogenSteve "Ashcrow" MilnerSteven CramerSteven MoixSteven ParrishSteven PritchardSubhodip BiswasSusan LauberSusmitTejas Dinkar (gja)Thibault NorthThierryThomas "thomasj" JanssenThomas CanniotThomas FitzsimmonsThomas Vander SticheleThorsten LeemhuisTiansworldTill MaasTim LauridsenTim NiemuellerTim WaughTom 'spot' CallawayTom TromeyToshio KuratomiTrever FischerTrond DanielsenUdit SharmaUjjwol LamichhaneValent TurkovicVenkatesh 'Venky' HariharanVille-Pekka VainioVincent DanenVivek "bonii" ShahWarren TogamiWill MorrisWill WoodsXavier LamienYaakov M. NemoyYannik StadelmaierYuan YijunYuri TimofeevZach OglesbyZoltan Hopparadliazaddinfedora daily packagefedora reloaded podcastmagjogui "El azul lo llevo dentro..."mythcatpingoupjpvwbusguy -Scott Williams-Dia is known to seduce some system level designers and is used to describe different block levels for embedded design.
Fedora has just received some additional shapes for digital blocks which will improve user documentation experience, through neat functional diagram drawn by dia. They should reach fedora repositories in a day or two.
Installation:
# yum install dia-Digital dia-CMOS dia-electronic dia-electric2
Everything went better than expected (seven attendees!).
Most of the people came from the Linux associations and LUGs of the city (there are 2 public universities in the area, plus some private), and I tried to advocate Fedora, but all of them are long time Linux users (even a Gentoo user in the house!). The Linux associations/LUGs in Valencia are quite dormant (one of the attendees used the word dead
), so I think the meeting was a big success!
We had a nice time talking about free software, programming languages, and (to some extent) the new features of Fedora (in the photo, because we were local logged users, we didn’t have to identify us to get a signed beer from a licensed repository heh, nice Fedora already fixed this).
The seventh attendee arrived a little late, but we had a big surprise because actually he was a Fedora user! I think we (the two only Fedora users in the party) deserve a photo:
So long, and thanks for all the fish.
A lot has been written about how Firefox’s stupid dialog is a big step backwards for the web.
But is there a way to disable it? Ideally I’d like it to work like ssh – give me a simple single-click warning and display the certificate the first time, and after that don’t say anything at all unless the certificate changes unexpectedly.
This paper on phishing [PDF] is excellent.
I’ve updated my laptop to Fedora 12 and to be honest it was quite painless however, when i rebooted and logged in, errrr *puke* what the hell has happened to all the icons in the gnome-panels? There is too much spacing, hmm ok not to worry i’ll just move them all, wtf, i can’t move them, is that the default? yup it is.
The panel now adds padding between applets and between icons in the notification area. The padding can be removed with the following commands
gconftool-2 –type int –set /apps/panel/toplevels/top_panel/padding 0
gconftool-2 –type int –set /apps/panel/toplevels/bottom_panel/padding 0
gconftool-2 –type int –set /apps/panel/applets/systray/prefs/padding 0
Phew back to normal 
No related posts.
Thanks for developers’ hard work. Now a new version. shutter-0.85 is available.
Here is a RPM package for shutter-0.85. Later I will build on Koji and push it to bodhi. I plan to do it on next Monday because I have no machine to run Koji client at home. Koji client needs some certifications. I have to go back to school on Monday. So, please wait for me.
RPM: http://liangsuilong.fedorapeople.org/shutter-pkg/shutter-0.85-1.fc12.noarch.rpm
The latest shutter brings a lot of new features to us. Here are some descriptions:
Image via Wikipedia
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=546fd57f-4f2d-4a02-b918-1433583f71f8)
The other day I did a quick hack using Raindrop & Jetpack to get new mail notifications from Raindrop. In total it took me less than an hour. It’s no Joe Shaw hack, so I don’t expect to get in the paper for this but I figured I’d share anyway. 
This Jetpack checks Raindrop to see if there are new messages and bubbles them up as notifications if there are. Here’s the source code:
var messages = {};
function checkMail() {
var api="http://localhost:5984/raindrop/_api/inflow/conversations/home?limit=10";
jQuery.getJSON(api,
function(data, textStatus){
jQuery.each(data, function(i,item){
if (item.unread) {
if (!messages[item.id] || messages[item.id] != item.messages.length) {
var n={title: item.subject,
body : item.messages[0].schemas["rd.msg.body"]["body_preview"],
icon : 'http://localhost:5984/raindrop/inflow/i/logo.png'};
jetpack.notifications.show(n);
}
messages[item.id] = item.messages.length;
}
});
});
}
setInterval(checkMail, 10000);
To try this out you’ll need Raindrop installed and running and Jetpack installed in Firefox.
Go to about:jetpack and copy the above code into the Develop tab, then click the try out this code link just below the Bespin editor.
If you don’t want to do all that you can just watch the video below (no sound, so you might want to play some music)
<object height="304px" width="650px"><param name="allowfullscreen" value="true"/><param name="allowscriptaccess" value="always"/><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=7733464&server=vimeo.com&show_title=1&show_byline=1&show_portrait=0&color=&fullscreen=1"/><embed allowfullscreen="true" allowscriptaccess="always" height="304px" src="http://vimeo.com/moogaloop.swf?clip_id=7733464&server=vimeo.com&show_title=1&show_byline=1&show_portrait=0&color=&fullscreen=1" type="application/x-shockwave-flash" width="650px"></embed></object>
I spent some time today writing a CD/DVD exporter for Solang using Brasero's new libbrasero-burn API. It is to be noted that we are not spawning a new Brasero process, but embedding some widgets in Solang's own ExporterDialog and making a few API calls here and there.
I wish they had exported the BraseroMediumProperties widget also.
Unfortunately, the code will not easily compile because of silly reasons like some of the libbrasero-burn headers having missing G_END_DECLS. And yes, the dialogs do have misleading titles. Will fix those soon.
[david@brick 2to3]$ ./2to3c --help
Usage: 2to3c [options] filenames...
Options:
-h, --help show this help message and exit
-w, --write Write back modified files
[david@brick 2to3]$ ./2to3c ../../python3/packaging/modules/by-hand/dbus-python/devel/dbus-python-0.83.0/_dbus_bindings/*.c > dbus-python.patch
[david@brick 2to3]$ diffstat dbus-python.patch
abstract.c | 28 ++----
bus.c | 4
bytes.c | 16 +--
conn.c | 7 -
containers.c | 21 ++--
float.c | 6 -
generic.c | 4
int.c | 31 ++-----
libdbusconn.c | 5 -
mainloop.c | 3
message-append.c | 4
message.c | 17 +--
module.c | 243 ++++++++++++++++++++++++++++++++++++++++++++-----------
pending-call.c | 3
server.c | 7 -
signature.c | 6 -
string.c | 9 --
17 files changed, 267 insertions(+), 147 deletions(-)
[david@brick 2to3]$ head -n 30 dbus-python.patch
--- ../../python3/packaging/modules/by-hand/dbus-python/devel/dbus-python-0.83.0/_dbus_bindings/abstract.c.orig
+++ ../../python3/packaging/modules/by-hand/dbus-python/devel/dbus-python-0.83.0/_dbus_bindings/abstract.c
@@ -54,7 +54,7 @@
if (!vl_obj)
return 0;
- return PyInt_AsLong(vl_obj);
+ return PyLong_AsLong(vl_obj);
}
dbus_bool_t
@@ -76,7 +76,7 @@
}
}
else {
- PyObject *vl_obj = PyInt_FromLong(variant_level);
+ PyObject *vl_obj = PyLong_FromLong(variant_level);
if (!vl_obj) {
Py_DECREF(key);
return FALSE;
@@ -127,7 +127,7 @@
Py_DECREF(key);
if (!value)
- return PyInt_FromLong(0);
+ return PyLong_FromLong(0);
Py_INCREF(value);
return value;
}
git clone git://fedorapeople.org/home/fedora/dmalcolm/public_git/2to3c.git
As the Fedora Board and larger community has discussed what we want our releases to be and who they are for–Target Audience–I’ve wondered more and more if a reworking of our Release Criteria could help make parts of our decision process clearer and easier to follow. By clearly defining our Target Audience we should be able to write more specific and accurate release criteria. The recent PackageKit controversy highlights this importance. The settings for this package made certain assumptions about a particular target audience and user of Fedora. To my knowledge this target audience isn’t documented anywhere. It makes me wonder how many other parts of our distribution make different or contradictory assumptions about our target audience–resulting in a distribution that is not as coherent and consistent as it could be.
A clear definition of our target audience might also reduce the emphasis we place on developing and testing certain areas, freeing up time to make other things better.
How do you know when testing is done? How do you know when the product is ready to release? Does the decision to release seem similar to deals done in the dark, smoke-filled rooms, or as if there are rules of the game that you don’t know? Does the release decision sometimes seem completely arbitrary? If you’re finding it difficult to make rational decisions about when to release the software, developing and using release criteria can help–Johanna Rothman
I’ve been more or less actively involved in Fedora since Fedora 7. Even though I’ve just completed my fifth release, am actively involved in creating the schedules, and lead the readiness meetings before each public test and final release, this paragraph still resonates with me. This has long been one of my frustrations of trying to understand and participate in Fedora development process. Things have definitely gotten better over the past few releases. We can still do a better job without adding layers of bureaucracy which some people fear.
To move this process forward I took a first shot at an enhanced release criteria framework for Fedora 13. Ultimately I believe we need a stronger framework to be more successful, but I’m not saying the framework I’ve proposed is the one we have to use. A lot of the information included has been in existence for a long time at the QA Release Criteria page. From it I created three separate pages–one for each public release: Alpha, Beta, and Final as well as an introductory page. I also added a few extra proposed bullets. I copied and pasted most of them from Release Criteria and adapted the ‘’shoulds” and ”musts” as specified–where ”must” was required for all releases and ‘’should” was only required for the final release.
I think a separate page for each release is helpful because in reality each release has a separate target audience. The audience and goals for the Alpha release are much different than the audience and goals for the Final release. Certainly there will be overlap in these audiences, but we sell ourselves short if we assume the audience and goals for all three releases are the same. My hunch is that some of these requirements are dated and wrong which makes reviewing everything for Fedora 13 a good thing. In light of the security discussion around PackgeKit we may also want to add a security aspect to our release criteria.
Another benefit of a clear list of release requirements is that the “Go/No-Go” meetings become more objective. There is less of a need to subjectively take everyone’s pulse and ask people how they are feeling. Instead we review the list of release requirements, which also encompasses blocker bugs. If the requirements are met we ship. If they are not met, we add a week the schedule and try again. The definition of what makes a bug a release blocker becomes clearer as well. In addition I’ve started a new blocker bug FAQ.
Check out the wiki pages and join in the discussion on fedora-test-list where I’ve started a thread on the same topic. My hope is that we can refine and discuss these pages over the next two weeks and then meet at FUDCon in Toronto to discuss and put a framework in place for Fedora 13.
Posted in Bug Triage, Fedora
Hopefully my post title has captured your attention. 
I would like to let you know about a project starting up right now that is a great opportunity for you to:
So the Fedora Board has started an initiative to create Fedora user profiles and personas to help inform decisions about Fedora policy and design in the future.
From Wikipedia:
Personas are fictional characters created to represent the different user types within a targeted demographic that might use a site or product. Personas are useful in considering the goals, desires, and limitations of the users in order to help to guide decisions about a product, such as features, interactions, and visual design. Personas are most often used as part of a user-centered design process for designing software and are also considered a part of interaction design (IxD), have been used in industrial design and more recently for online marketing purposes.
A lot of discussion about personas is available on Cooper’s blog and is a good read for getting up to speed on what they are and how they work.
Well, for example, you may recall the great panda panda-monium from early www.fedoraproject.org redesign mockups, in which about half of folks giving feedback loved the panda (“Please kill to keep that damn Panda, mairin. The thing is too cute and seems to look like a great little mascot.”), and the other half felt the panda was an insult to Fedora users (“In general i like the layouts…. for 6 year old kids. If this is the best you can come up with you might as well base it on this: http://ostiaunlobby.files.wordpress.com/2008/07/teletubbies-group2.jpg”)
Of course, everyone is entitled to their own opinion of the pandas. Those opinons may or may not have any bearing on how our target users might receive them, though. If we have a set of Fedora personas defined, we can talk about how each of the personas, designed to be representative of our target audience would feel about pandas. Discussing whether or not the Fedora panda is a good choice for our *target audience* or not will help us make decisions based on the target audience we’ve agreed upon for Fedora rather than base it on knee-jerk / personal / anecdotal reactions that merely represent the personal opinons of the folks who happened to be around at the time to give their feedback.
There’s more discussion of potential benefits of personas to Fedora in a post I made yesterday to the ‘User Profiles’ thread on fedora-advisory-board list, so please check it out for more info and please feel free to dive into the discussion with any questions / commentary / feedback you have.
We’ll build them. Well, I think there’s a lot of different methods to going about constructing personas, but to be good they need to be backed by user research data. User research data can take many forms.
The approach I’d like to propose for Fedora persona development is based on the user research process advocated for in Observing the User Experience: A Practitioner’s Guide to User Research by Mike Kuniavsky. A high-level / action-oriented summary of the approach is as follows:
SO GLAD YOU ASKED!!!! I am blocking out Tuesday, November 24th to be an interaction design hackfest. I want to run it from 3 pm – 6 pm EDT (8 PM – 11 PM UTC) on #fedora-design on irc.freenode.net. I’d like us to start working on work item #3, conducting interviews of product stakeholders, in order to get moving on the persona-building process. Depending on how far we get we may be able to dip into #4 and #5.
What concrete actions will helping involve?
You do not have to be an artist to help with design! So show up next Tuesday and find out how you can help.
p.s. for the panda-haters, how about this mascot:
So, I’ve had many annoying whines^H^H^H^H^H^H^H^H^H^H welcome requests from readers in the past for OpenID authentication for posting comments. I didn’t implement this for a long time. I told people it was because I was worried about spam but really it’s because I’m freaking lazy.
I tried to enable this a while back with the standard Wordpress OpenID plugin, but it didn’t seem to work (as many of you have noticed). I left it in this broken state for months, again because I am freaking lazy.
Today, because I’ll do almost anything to avoid writing an FWN beat, I actually got this implemented in a way that works, using a different plugin – this one. It uses an external authentication intermediary called RPX. This is slightly worrying, but I did look around a bit and read the license terms carefully and they don’t seem to be evil. Please do let me know if you know anything to the contrary.
The good bit is that it works – I tested – and it allows login with Yahoo, AOL and Google accounts as well as OpenID. So that should make it easier for people to comment in future. YOU’RE WELCOME! You can also still login with your existing account on my blog, if you like – there’s a little link down the bottom of the RPX login screen for that.
I reserve the right to disable this again if it causes me to get spam comments.
So, I’m basically a terminal user. If I could do everything from the terminal I wouldn’t bother with a DE. Anyway, out of the command line clients, rtorrent’s one I love!! I just read through the complete man page and learnt all the awesome options it has.
Here’s my .rtorrent.rc file: Read the man page to understand what I’ve done
directory = ~/Downloads/torrents/session = ~/Downloads/rtorrent_sessions/upload_rate = 20download_rate = 40peer_exchange = yesdht = autothrottle_up = low,10throttle_down = low,10throttle_up = med,20throttle_down = med,20
Probably a post on irssi next 
gst-launch filesrc location=<filename>.sln16 ! audio/x-raw-int,signed=true,rate=16000,channels=1,width=16,depth=16,endianness=1234 ! audioconvert ! vorbisenc ! oggmux ! filesink location=<filename>.ogg
gst-launch filesrc location=<filename>.ogg ! decodebin ! audioconvert ! audiorate ! audio/x-raw-int,signed=true,rate=16000,channels=1,width=16,depth=16,endianness=1234 ! filesink location=<filename>.sln16
RPM of final release of php 5.3.1 are available for Fedora and for Enterprise Linux (RHEL/CentOS) in remi repository.
Read the PHP 5.3.1 Released!
Use YUM to install : yum --enablerepo=remi update php-\* Notice : now, all extensions are provided for php-cli and php (module for apache in prefork mode) and php-zts (module for apache in worker mode). Read the entry PHP 5.3, MPM worker, zts and mysqlnd (yes I know, pecl extensions are not yet available). For all questions or help, please use... Lire PHP 5.3.1 Released!
Having followed its development for a long time now and used other video editing software I can say that PiTiVi is an awesome app that is only going to get better. Sure it isn’t perfect yet but that is software development for you. It takes time to get all the features in and make them solid.
One of the great parts of Open Source Software is you get to see it develop and grow. It is also one of the biggest misunderstood aspects of such software. In a world where people are gripped by the next best thing – a collective psychosis of product ADD – where patience is no longer a virtue but an outdated notion of an age long gone, evolution is about as exciting as watching paint dry. Just a reminder that even products that seem to just appear overnight, in reality had long periods of closed development to receive polish (and even then they aren’t always great but for some reason people tend to forgive shortcomings in something they bought as opposed to something they got for free).
Knowing the drive behind the developers working on PiTiVi I am confident that in time PiTiVi will become one of the prime examples of FOSS development. For now it is useful enough for some my basic editing needs and every time I try a new version it just gets that much more useful. Keep up the hard work!!!
Qarsh is a remote shell for testing environments.
This release includes a few new features and a few bug fixes.
Fedora 12发布有几天了，增加的的新功能还有一系列的改进非常的有吸引力。由于最近没有充分的时间折腾，所以还没有进行安装。
不过今天还是在虚拟机上安装了这个新系统。其实也是为了先熟悉一下，为过几天真正安装做些准备。
首先说下安装条件吧：
1. VirtualBox虚拟机，8G虚拟磁盘已安装Fedora 12 RC4；
2. 将Fedora 12-i386-DVD.iso复制到这个磁盘上；
3. 用iso镜像引导，执行硬盘安装，把Fedora 12安装到另一个虚拟磁盘；
下面讲过程：
1. 把校验无误的ISO镜像复制到某个分区下，或某个分区的目录下；
2. 提取ISO中的isolinux目录，并把它放到ISO所在的目录；
3. 重新启动计算机，光盘引导，在出现Fedora安装屏幕后，按Tab键编辑安装选项；在最后加上 linux askmethod；
4. 按回车键进入安装屏幕，选择安装语言和键盘后会提示选择安装方式：
4.1 本地光盘安装；(Local CD/DVD)
4.2 硬盘安装； (Hard Disk)
4.3 NFS安装； (NFS)
4.4 URL安装； (URL)
5. 选择硬盘安装
6. 在新的屏幕中会提示安装镜像所在分区，以及需要输入相应目录路径；
我把ISO放在了/home/tt/下，我的/home位于/dev/sda2；
7. 填好后确定，之后安装程序将自动寻找安装install.img文件，这个文件位于isolinux目录中。如果一切无误，那么安装过程就会继续向前了。
下面说说注意事项吧：
1.ISO存放分区格式：分区格式可以为VFAT，ext2-ext4；但是不可以为LVM卷（Fedora安装自动分区方案就会有LVM卷）；
2. 经过测试，ISO镜像文件中只需要提取出isolinux目录即可；
3. 提示安装位置时，一定要选择正确。由于我是在第二个虚拟磁盘安装，所以选择把Fedora安装到sdb。这个要根据实际情况自己确定。
参考文献：http://docs.fedoraproject.org/install-guide/f12/en-US/html/s1-begininstall-hd-x86.html
(本文仍待完善)
yum -y install gnome-commander
Loaded plugins: presto, refresh-packagekit
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package gnome-commander.i686 0:1.3-0.3.git_D20090929T1100_13dev.fc12 set to be updated
--> Processing Dependency: meld for package: gnome-commander- 1.3-0.3.git_D20090929T1100_13dev.fc12.i686
--> Processing Dependency: libexiv2.so.5 for package: gnome-commander- 1.3-0.3.git_D20090929T1100_13dev.fc12.i686
--> Running transaction check
---> Package exiv2-libs.i686 0:0.18.2-2.fc12 set to be updated
---> Package meld.noarch 0:1.3.0-2.fc12 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
========================================
Package Arch Version Repository Size
========================================
Installing:
gnome-commander i686 1.3-0.3.git_D20090929T1100_13dev.fc12 fedora 1.5 M
Installing for dependencies:
exiv2-libs i686 0.18.2-2.fc12 fedora 604 k
meld noarch 1.3.0-2.fc12 fedora 665 k
Claro, elimina el paquete seleccionado, pero no las dependencias que instaló para el mismo!yum -y remove gnome-commander
Loaded plugins: presto, refresh-packagekit
Setting up Remove Process
Resolving Dependencies
--> Running transaction check
---> Package gnome-commander.i686 0:1.3-0.3.git_D20090929T1100_13dev.fc12 set to be erased
--> Finished Dependency Resolution
Dependencies Resolved
========================================
Package Arch Version Repository Size
========================================
Removing:
gnome-commander i686 1.3-0.3.git_D20090929T1100_13dev.fc12 installed 4.7 M
history
The history command allows the user to view what has happened in past transactions (assuming the history_record config. option is set). You can use info/list/summary to view what happened, undo/redo to act on that information and new to start a new history file.
The info/list/summary commands take either a transactions id or a package (with wildcards, as in Specifying package names), all three can also be passed no arguments. list can be passed the keyword "all" to list all the transactions. undo/redo just take a transaction id.
# yum history list
Loaded plugins: presto, refresh-packagekit
ID | Login user | Date and time | Action(s) | Altered
-------------------------------------------------------------------------------
21 | Carlos ... <casep> | 2009-11-20 10:44 | Install | 3
.
.
.
</casep>
# yum history info 21
Loaded plugins: presto, refresh-packagekit
Transaction ID : 21
Begin time : Fri Nov 20 10:44:30 2009
Begin rpmdb : 1189:ba0aa90010d5d9c492556b3ff420f8940f22be12
End time : 10:44:35 2009 (5 seconds)
End rpmdb : 1192:756121f2f471a4e319c533854bab28042df46680
User : Carlos (casep) Sepulveda <casep>
Return-Code : Success
Transaction performed with:
Installed rpm-4.7.1-6.fc12.i686
Installed yum-3.2.25-1.fc12.noarch
Installed yum-metadata-parser-1.1.2-14.fc12.i686
Packages Altered:
Dep-Install exiv2-libs-0.18.2-2.fc12.i686
Install gnome-commander-1.3-0.3.git_D20090929T1100_13dev.fc12.i686
Dep-Install meld-1.3.0-2.fc12.noarch
history info
</casep>
# yum -y history undo 21
Loaded plugins: presto, refresh-packagekit
Undoing transaction 21, from Fri Nov 20 10:44:30 2009
Dep-Install exiv2-libs-0.18.2-2.fc12.i686
Install gnome-commander-1.3-0.3.git_D20090929T1100_13dev.fc12.i686
Dep-Install meld-1.3.0-2.fc12.noarch
Resolving Dependencies
--> Running transaction check
---> Package exiv2-libs.i686 0:0.18.2-2.fc12 set to be erased
---> Package gnome-commander.i686 0:1.3-0.3.git_D20090929T1100_13dev.fc12 set to be erased
---> Package meld.noarch 0:1.3.0-2.fc12 set to be erased
--> Finished Dependency Resolution
Dependencies Resolved
===================================
Package Arch Version Repository Size
===================================
Removing:
exiv2-libs i686 0.18.2-2.fc12 installed 2.4 M
gnome-commander i686 1.3-0.3.git_D20090929T1100_13dev.fc12 installed 4.7 M
meld noarch 1.3.0-2.fc12 installed 2.0 M
Transaction Summary
===================================
Remove 3 Package(s)
Reinstall 0 Package(s)
Downgrade 0 Package(s)
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Erasing : meld-1.3.0-2.fc12.noarch 1/3
Erasing : exiv2-libs-0.18.2-2.fc12.i686 2/3
Erasing : gnome-commander-1.3-0.3.git_D20090929T1100_13dev.fc12.i686 3/3
Removed:
exiv2-libs.i686 0:0.18.2-2.fc12 gnome-commander.i686 0:1.3-0.3.git_D20090929T1100_13dev.fc12 meld.noarch 0:1.3.0-2.fc12
Complete!
O lançamento oficial do Fedora 12, codinome constantine, será realizado durante o IV Congresso Catarinente de Software Livre - SOLISC, que será realizado em Florianópolis - SC durante os dias 26 e 27 de Novembro (http://www.solisc.org.br/).
Como atividades de lançamento o Projeto Fedora Brasil estará no evento com várias palestras na grade e com a participação dos membros Rodrigo Padula (Líder do Projeto Fedora na América Latina e Community and Academy Relations da Red Hat) e Wolnei Cândido Tomazelli Junior ( Embaixador Fedora e membro do Projeto de Artwork do Fedora).
Programação Fedora no SOLISC:
Confira a programação completa do evento: http://www.solisc.org.br/index.php?option=com_wrapper&view=wrapper&Itemid=27
Contamos com a presença de todos para prestigiar este evento e saber um pouco mais a fundo tudo a respeito da Distribuição Fedora e sobre o Projeto.
Participe!
Fonte: http://www.projetofedora.org/fedora_12_lancamento_oficial_solisc
Hi!
First, I’d like to introduce myself. My name is Diana and I am an anthropologist currently in the midst of attaining my Masters degree in Applied Anthropology from the University of North Texas. As a part of my studies I will be working with Fedora, and hopefully many of you, to better understand the culture that surrounds open source software development.
As an applied anthropologist I want to stress that I will be doing research FOR and with the Fedora community not ON the Fedora community. My goal is to find ways to make your lives as open source developers better! And, if by some chance it can’t get any better than it already is, find out why it is so great so other open source groups can follow your lead.
My research methods will include participant observation, which means I will be hanging out with you all as you do what you do both in an online and offline context, interviews, and surveys. I will be using this blog as my major means of communication with everyone and as a way to make my research both open and transparent.
When my research concludes I will be providing the community with a report as to the findings of my explorative study so that everyone has access to them and can hopefully find ways to use them to your benefit.
As a side note for all anthropologists aspiring to do research online, I am documenting my entire process and will be providing a side report as my contribution to open anthropology.
For those of you who will be in Toronto for the developer conference in December, I will be there as well and will be providing a topic for discussion so that we can all get to know each other a bit better.
I want to stress that participation in this study is strictly voluntary! If for some reason you do not want to participate, or would like to speak to me in confidence, I will be more than happy to oblige.
You can contact me here by leaving a comment, or by emailing me Diana [@] cyber-anthro.com.
I look forward to working with all of you and to any feedback you may have, even this early in the process!
O lançamento oficial do Fedora 12, codinome constantine, será realizado durante o IV Congresso Catarinente de Software Livre - SOLISC, que será realizado em Florianópolis - SC durante os dias 26 e 27 de Novembro (http://www.solisc.org.br/).
The LHC restarts today aiming for the first beam circulation… to be followed by the very first LHC collision in the next couple of days or so… will keep you updated 
– update –
Display of a splash event just seen online on the CMS:
Initially I thought to not run again for FAMSCO Elections, but with some important guys lefting the committee like Francesco Ugolini and several emails received requesting for my nomination, I will try again to be part of the FAMSCO, occupying one of the 7 seats available .
I believe I can contribute a little more with the Ambassadors Program, now focusing not only in LATAM, but the overall project, sharing successful experiences that I applied in Brazil and Latin America, creating a stronger project throughout the world.
Below are the details of my nomination, available at https://fedoraproject.org/wiki/Ambassadors/SteeringCommittee/Election/2009Nominations#Rodrigo_Padula_de_Oliveira_.28RodrigoPadula.29
And so, long story short, we decided to revert the change for F12.
Part of being an open source maintainer (and also my job at Red Hat) is to ignore trolls, but some of the messages I was getting yesterday were just personal attacks and abuse. That’s not cricket at all.
The post is brought to you by lekhonee v0.8
Few days back I bought a new GPS data logger from Sparc Systems Limited , GDL 3204. It comes with a nice 3 page manual. The last page explains the data format of the logs.
The device works in a very nice and easy way, it is having 32 channels.
We already had a nice python script to parse the log and create gpx files. But for me , every time “cat”ing the device and then convert the log is a difficult task.
Sparcy , which can get the data from the device and convert them into gpxfor you. If you already have the raw data, you can convert them to gpx too. People from #osm helped me a lot to understand how latitude and longitude calculations are done.
RPMs are available here.
The post is brought to you by lekhonee v0.8
Yesterday and Tuesday I pushed several updates to my experimental video acceleration repositories. Most obviously, there’s now an F11, an F12 and a Rawhide (F13) repo, all in the logical places. I also updated all components; libva is up to sds7, vdpau-video is up to 0.5.2. mplayer-accelerated is up to 20091106 and mplayer-mt is up to svn rev 29934 (basically, the latest mplayer and ffmpeg-mt checkouts as of yesterday).
Note that Splitted Desktop Systems have made xvba-video – the equivalent to vdpau-video for the ATI proprietary driver, it’s a bridge from ATI’s ‘xvba’ video acceleration system to VAAPI so you can use any VAAPI-compliant player with ATI cards – available. Unfortunately, it’s proprietary. I’m not sure whether I want to package it, due to that. I probably will at some point, but…ick. Anyway, the fact that it’s proprietary makes it very trivial to install, basically you’d just grab the latest tarball for your arch from here and extract the single file it contains to the appropriate place on your system. Then make sure you have libva and mplayer-accelerated installed and try it.
I’ll try and find some time to work on the RPM Fusion mplayer package soon. Basically I’d like to update it to a newer snapshot and enable VDPAU support.
Not a lot of people seem aware of this. This is from the announce list. Please help spread the word.
The Fedora 12 release contained changes in the default PackageKit
behavior that allow installation of packages by users in cases where:* the user is logged in on the local console, and
* is installing packages signed with a previously trusted key, and
* is using a previously configured and trusted repositoryAfter more discussion and thought, though, the package maintainers
have posted to the fedora-devel-list mailing list agreeing to provide
an update to Fedora 12's PackageKit. The update will require local
console users to enter the root password to install new software
packages. Details on the changes are found here:https://www.redhat.com/archives/fedora-devel-list/2009-November/msg01445.html
--
Paul W. Frields http://paul.frields.org/
I just want to give a short update on the broken LXDE Spin images: I (think I) fixed the bug, but we need to do some more testing to be really sure. The packages first need to go through bodhi before new images will be composed. Not sure how long it takes, I prefer adding one or two extra days for testing because I really don’t want to disappoint all the people who are interested in LXDE.
Thanks for your patience. I’ll keep you informed.
WRT This, I think there are potentially greater problems. Fedora has standards of packaging specification review, but not so much review of package content or updates (beyond, perhaps diffs to the specfile, which go to a mailing list in CVS — the tarballs are not subject to close inspection). While it is bad enough that this allows a user access to install a well-intentioned package with an unpatched vulnerability when it is not otherwise installed (requiring first some form of local access, or another exploit or bridge sufficient to talk to dbus?), what is not mentioned is it is fairly easy for a person to masquerade as a good guy, package a popular technology, and replace it with an disguised evil payload six months later. RPM scripts run as root, and are just as dangerous as the software they install.
I don’t know exactly /how/ you fix that attack vector, it is a social one. So if Fedora is thinking about reviewing security policies, also consider we don’t /really/ know everyone, and we can’t know. I would be more worried about that than the PackageKit one. With the PackageKit one, I’d just mostly be really annoyed that someone I gave an account to could fill up my hard drive space and I wouldn’t know exactly what they installed so I could clean up after.
My point is that even though the Package is signed, that doesn’t mean they are (neccessarily) safe. More reason for not allowing extra people to install packages.
I’m only bringing this up because I get tired of fighting off Ubuntu people, and such security features as PackageKit being wide open do not make it easy. With all the attention on SELinux, etc, I see no reason Fedora could not be both usuable and also a security bastion with similar reputations as OpenBSD. In the worst case, perhaps just ask the user what they want in the installer and default to some of the more secure options — or default to the most secure options and provide a setting in a configuration panel somewhere to open it up.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=286bd8ba-5d5b-4267-acdd-21012946322f)
Στόχος μας είναι η εκδήλωση να απευθύνεται τόσο σε απλούς χρήστες και άτομα που δε γνωρίζουν το ελεύθερο και ανοιχτό λογισμικό όσο και σε developers/προγραμματιστές αλλά και επαγγελματίες διαφορετικών ειδικοτήτων.
Καλούμε λοιπόν όλους εσάς που ενδιαφέρεστε να παρουσιάσετε, να στήσετε κάποιο workshop, να μας βοηθήσετε με οποιοδήποτε τρόπο (δεχόμαστε και χορηγίες) ή που απλά θέλετε να μάθετε περισσότερα, να επικοινωνήσετε μαζί μας στο thessaloniki@fosscomm.gr .
Επίσης μην ξεχνάτε και την διεύθυνση http://thessaloniki.fosscomm.gr από όπου θα μπορείτε να ενημερώνεστε για την πρόοδο της οργάνωσης (χρειαζόμαστε καινούργιο banner!).
Το Σάββατο 28 Νοεμβρίου θα υπάρξει μια πρώτη συνάντηση όλων όσων θέλουν να βοηθήσουν στην διοργάνωση. Σας περιμένουμε λοιπόν όλους στις 28/11 στις 15:00 στο stand της Ελληνικής open source κοινότητας στα περίπτερα της Infosystem 2009.
Χάρτης: http://bit.ly/48jESn
# yum clean all # yum update # preupgrade-cli "Fedora 12 (Constantine)"I had to pass intel_iommu=off to the kernel command line to boot the kernel. Otherwise, everything worked cleanly!
