tag:blogger.com,1999:blog-49398758142844717272024-03-13T16:34:53.224+01:00Frederic Crozat blogFredhttp://www.blogger.com/profile/11945939947279163927noreply@blogger.comBlogger163125tag:blogger.com,1999:blog-4939875814284471727.post-6841585226714406782017-06-09T17:48:00.000+02:002017-06-13T16:36:09.103+02:00Synology PhotoStation password vulnerabilityOn <a href="https://www.synology.com/">Synology</a> NAS, <span style="font-family: "courier new" , "courier" , monospace;">synophoto_dsm_user</span> executable, part of <a href="https://www.synology.com/dsm/app_packages/PhotoStation">PhotoStation</a> package, was leaking NAS user password on the command line.<br />
<br />
Using a simple shell loop to run "<span style="font-family: "courier new" , "courier" , monospace;">ps ax | grep synophoto_dsm_use</span>r", it was possible to get user and password credentials for user on the NAS who had PhotoStation enabled with their DSM credentials.<br />
<br />
Fortunately, by default, shell access on the NAS is not available (by ssh or telnet), it has to be enabled by the admin.<br />
<br />
Still, it is a bad practise to pass credentials to process using command line, which can be intercepted.<br />
<br />
<a href="https://www.synology.com/releaseNote/PhotoStation">PhotoStation version 6.7.1-3419</a> or earlier is vulnerable. I've contacted Synology and they should release a security fix really shortly, as well as a CVE for it.<br />
<br />
Update (June 13, 2017): Synology has released a <a href="https://www.synology.com/en-global/support/security/Photo_Station_CVE_2017_9552">CVE</a> and the vulnerability is fixed in PhotoStation 6.7.2-3429 or later. Remember to update this package on your NAS !Anonymoushttp://www.blogger.com/profile/03724661663218761139noreply@blogger.com0tag:blogger.com,1999:blog-4939875814284471727.post-56781922437589963542017-02-27T18:04:00.001+01:002017-02-27T18:04:17.972+01:00Hackweek projet: Let's Encrypt DNS-01 validation for acme.sh with Gandi LiveDNSLast week was <a href="https://hackweek.suse.com/">SUSE Hackweek </a>and one of my projects was to get Let's Encrypt configured and working on my NAS.<br />
<br />
<a href="https://letsencrypt.org/">Let's Encrypt </a>is a project aimed at providing SSL certificates for free, in an automated way.<br />
<br />
I wanted to get a SSL certificate for my <a href="https://www.synology.com/">Synology</a> NAS. Synology now supports natively Let's Encrypt but only if the NAS accepts incoming HTTP / HTTPS connections (which is not always what you want).<br />
<br />
Fortunately, the protocol used by Let's Encrypt to validate a hostname (and generate a certificate), Automatic Certificate Management Environment (<a href="https://ietf-wg-acme.github.io/acme/">ACME</a>) has a alternative validation path, DNS-01, based on DNS.<br />
<br />
DNS-01 requires access to your DNS server, so you can add a validation token used by Let's Encrypt server, to ensure you own the domain name you are requesting a certificate for.<br />
<br />
There is a lot of ACME implementations, but very few supports DNS-01 validation with my DNS provider (<a href="https://www.gandi.net/">gandi.net</a>).<br />
<br />
I ended-up using <a href="https://github.com/Neilpang/acme.sh">acme.sh</a>, fully written in shell script and tried to plug Gandi DNS support in it.<br />
<br />
After some tests, I discovered Gandi current DNS service is not allowing fast changing DNS zone informations (which is somehow a requirement for DNS-01 validation). Fortunately, Gandi is now providing a new <a href="https://www.gandi.net/news/en/2015-12-29/6536-livedns_beta_first_glimpse_into_our_new_dns_platform/">LiveDNS</a> server, available in beta, with a RESTful HTTP <a href="http://doc.livedns.gandi.net/">API</a>.<br />
<br />
I was able to get it working quite rapidly with curl, and once the prototype was working, I've cleaned everything and created a <a href="https://github.com/Neilpang/acme.sh/pull/680">pull request</a> for integrating the support in acme.sh.<br />
<br />
Now, my NAS has its own Let's Encrypt certificate and will update it every 90 days automatically. Getting and installing a certificate for another server (running <a href="https://www.opensuse.org/#Leap">openSUSE Leap</a>) only took me 5 minutes.<br />
<br />
This was a pretty productive hackweek !<br />
Anonymoushttp://www.blogger.com/profile/03724661663218761139noreply@blogger.com0tag:blogger.com,1999:blog-4939875814284471727.post-38567479440933747592015-10-07T18:23:00.000+02:002015-10-07T18:23:56.775+02:00We are hiring !Did you knew <a href="https://www.suse.com/">SUSE</a> is hiring ? <br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://www.suse.com/home/img/banners/sle11sp4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="320" src="https://www.suse.com/home/img/banners/sle11sp4.png" width="314" /></a></div>
<br />
<br />
I've just looked at our counter today (October 7, 2015) and we have <a href="https://attachmatehr.silkroad.com/epostings/index.cfm?fuseaction=app.allpositions&company_id=15495&version=6">68 opened positions</a>.<br />
<br />
Moreover, we have two positions which might interest people who are reading this blog through Planet GNOME(-FR):<br />
<div class="cssDspJobTitle" id="jobTitleDiv">
<ul>
<li>Xorg is your thing : <a href="https://attachmatehr.silkroad.com/epostings/index.cfm?fuseaction=app.jobinfo&jobid=306893&company_id=15495&version=6&source=ONLINE&jobOwner=1013811&aid=1">Linux Graphics Developer</a> </li>
<li>you are more a GNOME desktop guy : <a href="https://attachmatehr.silkroad.com/epostings/index.cfm?fuseaction=app.jobinfo&jobid=307389&company_id=15495&version=6&source=ONLINE&jobOwner=1014217&aid=1">SUSE Linux Desktop Engineer</a> </li>
</ul>
</div>
<div class="cssDspJobTitle" id="jobTitleDiv">
Interested ? Apply !</div>
Anonymoushttp://www.blogger.com/profile/03724661663218761139noreply@blogger.com0tag:blogger.com,1999:blog-4939875814284471727.post-1227557460196548932015-04-14T13:54:00.000+02:002015-04-14T14:23:05.395+02:00Hackweek 12: improving GNOME password management, day 1This week is <a href="https://hackweek.suse.com/">Hackweek 12</a> at <a href="https://www.suse.com/">SUSE</a><br />
<br />
My hackweek <a href="https://hackweek.suse.com/12/projects/746">project</a> is improving GNOME password management, by investigating password manager integration in GNOME.<br />
<br />
Currently, I'm using <a href="https://www.lastpass.com/">LastPass</a> which is a cloud-based password management system.<br />
<br />
It has a lot of very nice features, such as:<br />
<ul>
<li>2 factor authentication</li>
<li>Firefox and Chrome integration</li>
<li>Linux support</li>
<li>JS web client with no install required, when logging from a unknown system (I never needed it myself)</li>
<li>Android integration (including automatic password selection for applications)</li>
<li>cli open-source client (lastpass-cli), allowing to extract account specific information </li>
<li>encrypted data (nothing is stored unencrypted server side)</li>
<li>strong-password generator</li>
<li>support encrypted notes (not only password) </li>
<li>server based (clients sync) with offline operations supported<br />
</li>
</ul>
However, it also has several drawbacks:<br />
<ul>
<li>closed-source</li>
<li>subscription based (required for Android support)</li>
<li>can't be hosted on my own server</li>
<li>doesn't integrate at all with GNOME desktop</li>
</ul>
I don't want to reinvent the wheel (unless it is really needed), which is why I spend my first day at searching the various password managers available on Linux and compare their features (and test them a bit).<br />
<br />
So far, I found the following programs:<br />
<ul>
<li><a href="http://keepass.info/">KeePass</a> (GPL): </li>
<ul>
<li>version 1.x written in Java, still supported, not actively developed </li>
<li>version 2.x written in C# (Windows oriented), works with Mono under Linux</li>
<li>UI feels really Windows-like </li>
<li>DB format change between v1 and v2 </li>
<li>supports encrypted notes</li>
<li>password generator</li>
<li>supports plugins ( a lot are available)</li>
<li>support OTP (keeotp plugin, provide 2factor auth through TOTP, HTOP built-in)</li>
<li>shared db editing </li>
<li>support yubikey (static or hotp)</li>
<li>2 Firefox extension available(keefox, passifox) </li>
<li>3 android applications available (one application
<a href="https://play.google.com/store/apps/details?id=keepass2android.keepass2android" target="_blank">KeePass2Android</a> supports alternative keyboard, <a href="https://play.google.com/store/apps/details?id=com.hanhuy.android.keepshare" target="_blank">KeepShare</a> supports alternative keyboard + a11y framework to fill android application forms, like LastPass)</li>
<li>Chrome extension available</li>
<li>JS application available</li>
<li><a href="http://kpcli.sourceforge.net/">CLI</a> available </li>
<li>big ecosystem of plugins and other applications able to process file format</li>
</ul>
<br />
<li><a href="https://www.keepassx.org/">KeePassX</a> (GPL)</li>
<ul>
<li>Qt4 "port" of KeePass (feels more a Linux application than KeePass)</li>
<li>alpha version for DB v2 support</li>
<li>missing support for OTP</li>
<li>missing support for <a href="https://github.com/pfn/keepasshttp/">keypasshttp</a> (required by firefox extensions to discuss with main application), support is being done in a separate branch by a contributor, not merged</li>
<li>release are very scarse (latest release is April 2014, despite commits on git, very few people are contributing, according to git)</li>
<li>libsecret dbus support is being started by a contributor</li>
</ul>
<br />
<li><a href="https://github.com/mitro-co/mitro">Mitro</a>: </li>
<ul>
<li>company developped it was bought by Twitter last year, project released under GPL, no development since January.</li>
</ul>
<br />
<li><a href="http://pwsafe.org/">Password Safe</a> (Artistic license): </li>
<ul>
<li>initially written by Bruce Schneier </li>
<li>beta version available on Linux</li>
<li>written in wxWidgets 3.0 / C++ </li>
<li>yubikey supported</li>
<li>android application available, no keyboard nor a11y framework usage, only use copy/paste (but allows sync of db with owncloud and other cloud platforms)</li>
<li>CLI available</li>
<li>3 different DB formats (pre-2.0, 2.0, 3.0)</li>
<li>password history</li>
<li>no firefox extension and the "auto-type" built-in function is all but intuitive</li>
<li>support merge of various db</li>
</ul>
<br />
<li><a href="https://github.com/devgeeks/Encryptr">Encrypt</a>:</li>
<ul>
<li>same 0 knowledge framework as SpiderOak</li>
<li>node-js based</li>
</ul>
<br />
<li><a href="http://www.passwordstore.org/">Pass</a>: </li>
<ul>
<li>simple script on top of text files / gnupg and optionnally git (used for history and can also be used to manage hosting the file)</li>
<li>not easy learning curve (CLI mostly), need gnupg to be setup before usage</li>
<li>one file per password entry, should make </li>
<li>very basic Qt GUI available</li>
<li>basic FF extension available</li>
<li>basic android application available</li>
</ul>
</ul>
Unfortunately, none of those applications properly integrates (yet) in GNOME (master password prompt, locking keyring when desktop is locked, etc..). <br />
<br />
I've also looked at gnome-keyring integration with the various browsers:<br />
<ul>
<li>Several extensions already exist, <a href="https://addons.mozilla.org/fr/firefox/addon/gnome-keyring-integration-1/">one</a> is fully written in Javascript and is working nicely (port to libsecret is being investigated)</li>
<li>Chrome has already gnome-keyring and libsecret integration </li>
<li>Epiphany already works nicely with gnome-keyring</li>
<li>No password generator is available in Firefox / Chrome / Epiphany (nor GTK+ on a more generic basis) </li>
</ul>
Unfortunately, each browser is storing metadata in gnome-keyring for password entries in a slightly different format (fields name), causing password entries duplication and not allowing sharing keyring data across browsers.<br />
<br />
Conclusions for this first day of hackweek:<br />
<ul>
<li>Keepass file format seems to be the format of choice for password manager (a lot of applications written around it)</li>
<li>Password manager which would fit my requirement is KeePass but is written in Mono (I don't want Mono stack to come back on my desktops) and too Windows oriented, so not an option.</li>
<li>KeePassX seems to be the way to go (even if it is Qt based) but it lacks a lot of features and I'm not sure if it worth spending effort in adding those missing features there.</li>
<li>Pass is extremely simple (which would make hacking around it pretty straightforward) but requires a lot of work around it (android, GUI) to make it nicely integrated in GNOME.</li>
</ul>
I haven't yet made up my mind which solution is the best, but I'll probably spend the following days hacking around KeePassX (or a new program to wrap KP db into libsecret) and Firefox gnome-keyring integration.<br />
<br />
Comments welcome, of course.Anonymoushttp://www.blogger.com/profile/03724661663218761139noreply@blogger.com0tag:blogger.com,1999:blog-4939875814284471727.post-58126118103531928112014-05-11T17:24:00.000+02:002015-04-10T15:34:42.485+02:00Coffee: my personal historyAs always, long time no blog. These days, I don't have enough energy (nor content, IMO) to write blog posts, mostly on Free Software, which would relevant for other people.<br />
<br />
Why, would you ask ? Mostly because with my not-so-new-anymore position at <a href="http://www.suse.com/">SUSE</a> (Enterprise Desktop Release Manager), I'm mostly working behind the scene (discovery the joy of <a href="http://build.opensuse.org/">OBS</a> to create ISO images and lot of crazy similar stuff) which might not be that sexy to describe but still need to be done ;)<br />
<br />
So, instead of closing this blog for new posts, I'm trying something new to me: writing about things which aren't Free Software but might still interest people:<br />
<br />
My new thing these days (asks my wife ;) is coffee.<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="http://upload.wikimedia.org/wikipedia/commons/thumb/5/53/Tux_Paint_expresso.svg/200px-Tux_Paint_expresso.svg.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://upload.wikimedia.org/wikipedia/commons/thumb/5/53/Tux_Paint_expresso.svg/200px-Tux_Paint_expresso.svg.png" /></a></div>
<br />
I've always been fond of coffee (and tea, they aren't mutually exclusive, fortunately), probably because when I was a child, my parents loved good coffee and I was happy to be the one taking care of both electric grinder and Expresso machine we had. And I remember how difficult it was to find good coffee, even more when you were living in a very rural area of France and when the only online services were accessible with a <a href="http://en.wikipedia.org/wiki/Minitel">Minitel</a> and were definitively not selling coffee ;)<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="http://upload.wikimedia.org/wikipedia/commons/thumb/7/70/CNAM-IMG_0572.jpg/240px-CNAM-IMG_0572.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://upload.wikimedia.org/wikipedia/commons/thumb/7/70/CNAM-IMG_0572.jpg/240px-CNAM-IMG_0572.jpg" /></a></div>
Fast forward ten years, when I started to work in Paris, I was still into coffee and I discovered something which wasn't known at all at that time (it was in 2002 and George was still working in ER ;): Nespresso. This was a great thing (even if I was a bit worried by the closed system around it) because I was able to get a expresso at home which was always good (IMO at that time) and which also allowed me to switch between various coffees without any hassle (try that with several ground opened coffee bags when you are single and only drink one expresso per day ;)<br />
<br />
And then started my love story with Nespresso, which has not ended (yet), with its ups (being part of a customer panel once, including UI designers, very interesting) and downs. I often skipped coffee in cafés and restaurants because I knew it wouldn't be good!<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://www.flickr.com/photos/joeshlabotnik/503217589/" style="margin-left: 1em; margin-right: 1em;" title="Nespresso Drinker de Joe Shlabotnik, sur Flickr"><img alt="Nespresso Drinker" height="240" src="https://farm1.staticflickr.com/190/503217589_4484d98665_m.jpg" width="180" /></a></div>
Fast forward again 10 years. We are in 2014. Caps war is on for few years in France, since some of Nespresso patents are in public domain and competitors are trying to get a share of this huge market (France is apparently one of the biggest markets for Nespresso). I've tried various alternative caps and most of them are just cheaper and not as good as the original caps, except one or two caps done by some "small" roasters (<a href="http://www.terresdecafe.com/">Terre de Café</a> for instance). I ended up sticky with the original, until something better "happens".<br />
<br />
And it has happened these days, somehow unexpectedly: for a few years, I was reading about strange devices (Aeropress being cited often) and tasty filter coffee (which, for me, as always been synonym of bad coffee) and I also heared some radio shows on coffee which make me think: let's try.<br />
I ordered an <a href="http://www.amazon.fr/gp/product/B000GXZ2GS/ref=as_li_ss_tl?ie=UTF8&camp=1642&creative=19458&creativeASIN=B000GXZ2GS&linkCode=as2&tag=freblo0e-21">Aeropress</a> and tried it (with some fair trade coffee from my supermarket since I don't have any grinded coffee at home and opening caps wasn't really a good idea). Result: not bad, compared to the consistency of Nespresso but not that great. I knew I wasn't using great coffee.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://www.flickr.com/photos/97311086@N00/296877647/" style="margin-left: 1em; margin-right: 1em;" title="The Aeropress de Ldiggity, sur Flickr"><img alt="The Aeropress" height="180" src="https://farm1.staticflickr.com/99/296877647_811a717b89_m.jpg" width="240" /></a></div>
So, I decided to expand a bit more and searched for good coffee roasters in Paris. And one of those which was often mentionned is <a href="http://www.coutumecafe.com/fr/">Coutume Café</a> (their main website is not great ATM, better to look at their <a href="https://www.facebook.com/Coutume">FB account</a>), who also have a coffee shop. I went there, tried one of their coffee and I was astonished. This was the best ever coffee I ever tasted, with flavor like red fruits and chocolate. This was incredible and it wasn't even an expresso (which has been my reference for coffee) but filter coffee which looks like dishwater ;)<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="http://www.coutumecafe.com/" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://www.coutumecafe.com/img/logo.jpg" height="174" width="320" /></a></div>
<br />
<br />
So, I'm now with this exact same coffee at home, waiting for delivery of a freshly ordered <a href="http://www.amazon.fr/gp/product/B0044ZA066/ref=as_li_ss_tl?ie=UTF8&camp=1642&creative=19458&creativeASIN=B0044ZA066&linkCode=as2&tag=freblo0e-21">manual grinder</a> to try to duplicate this coffee experience, because I try other coffee and other Paris roasters.<br />
<br />
Let's see if I succeed :)Anonymoushttp://www.blogger.com/profile/03724661663218761139noreply@blogger.com3tag:blogger.com,1999:blog-4939875814284471727.post-15036593547526069002013-02-02T15:13:00.001+01:002013-02-02T15:13:41.294+01:00Secure Boot on openSUSE talk at FOSDEM cancelledHi folks,<br />
<br />
for those of you who are attending FOSDEM this year and were planning to attend my talk about Secure Boot on openSUSE on Sunday, I'm sorry to announce I had to cancel my travel to Brussels (and my talk) for family reasons.<br />
<br />
Since my <a href="https://docs.google.com/file/d/0B9-rayO7YPaZSTdneEFMcTBUb28/edit?usp=sharing">slides</a> were already written, I thought I could still share them with you Feel free to ask questions / comments on this blog post.Anonymoushttp://www.blogger.com/profile/03724661663218761139noreply@blogger.com2tag:blogger.com,1999:blog-4939875814284471727.post-75977049597699868922012-11-23T17:51:00.000+01:002012-11-23T17:51:02.555+01:00Secure Boot on openSUSE, a battleplanAt <a href="http://conference.opensuse.org/">openSUSE Conference</a> in Prague last month, we had a BoF about Secure Boot, where I describe the various tasks which are needed to ensure openSUSE can support Secure Boot. They are listed on my <a href="https://docs.google.com/open?id=0B9-rayO7YPaZckdJQjhsSnV3X00">slides</a>, but I thought it would be more useful to describe them here.<br />
<br />
Before we begin, if you need some refresh about Secure Boot, I suggest the blog posts from <span class="author vcard"><a class="url fn n" href="https://www.suse.com/blogs/author/okir/" title="View all posts by Olaf Kirch">Olaf Kirch</a></span> and <span class="author vcard"><a class="url fn n" href="https://www.suse.com/blogs/author/vojtech_pavlik/" title="View all posts by Vojtěch Pavlík">Vojtěch Pavlík</a></span> on <a href="https://www.suse.com/blogs/tag/secure-boot/">SUSE Blog</a> (<a href="https://www.suse.com/blogs/uefi-secure-boot-overview/">overview</a>, <a href="https://www.suse.com/blogs/uefi-secure-boot-details/">details</a> and <a href="https://www.suse.com/blogs/uefi-secure-boot-plan/">approach to it</a>) and of course, <a href="http://mjg59.dreamwidth.org/tag/fedora">all the war stories</a> of Matthew Garrett on this topic ;)<br />
<br />
To have openSUSE installable (and runnable) on a Secure Boot enabled system, without any additional user intervention (like adding your own key in UEFI firmware or disabling Secure Boot), we need to do the following to the distribution :<br />
<ul>
<li>to the kernel (many of those features are in 3.7 or in upcoming 3.8): </li>
</ul>
<ul><ul>
<li>convert the kernel as a EFI executable (it will be used to store kernel signature) </li>
<li>UEFI variable access </li>
<li>UEFI clock support (nice to have)</li>
<li>UEFI getvideomode (if we want flicker-free boot)</li>
<li>UEFI reboot (we already have 4 other way to reboot a system, why not add yet another one ;)</li>
<li>KMS drivers (for old chipsets like Matrox, AST).</li>
<li>sign main kernel</li>
<li>sign all in-tree kernel modules</li>
<li>generate a private/public key pair to be used out of tree modules</li>
<li>add Secure Boot support in KExec / KDump and Xen (optional)</li>
<li>disable hibernation in Secure Boot mode (or have a secure way to save / restore suspended system)</li>
<li>add signature check in kernel</li>
</ul>
<li>to bootloader:</li>
<ul>
<li>package shim loader</li>
<li>modify grub2 so it uses shim loader to check kernel signature at boot</li>
</ul>
<li>to Build Service:</li>
<ul>
<li>to be able to build external kernel modules (think KMP) using the private/public key generated at kernel build</li>
<li>but do not allow this key to be used for any random KMP build (otherwise, you defeat the purpose of signing the module)</li>
</ul>
<li>to userspace tools:</li>
<ul>
<li>package xf86-video-modesettings, for graphics chipset with non-accelerated KMS drivers</li>
<li>add support for signature check in modutils / kmod</li>
<li>package tools to sign kernel / modules</li>
<li>package tools to manage UEFI variables and keys</li>
</ul>
<li>to the installer / DVD image</li>
<ul>
<li>maybe display some warnings about installing a system in Secure Boot mode (not 100% sure we should do this)</li>
<li>maybe signing the initial installer (and make sure it can't load non-signed modules)</li>
<li>ensure the DVD image has shim + grub2 as bootloader when booting on UEFI system</li>
</ul>
<li>and we also need to do the signing part:</li>
<ul>
<li>if we want Secure Boot to be transparent to users, we need our shim loader to be signed by the authority handling UEFI key, ie Microsoft</li>
<li>this requires some legal paperwork (getting MS developer account, getting a Authenticode certificate, etc..), some obligation (making sure you can't circumvent Secure Boot once Linux is booted) and once it is done, sending shim loader to be signed by MS and package the result.</li>
</ul>
</ul>
As you can see, this is a lot of work but I think we will be able to have everything in order for next openSUSE release !<br />
Anonymoushttp://www.blogger.com/profile/03724661663218761139noreply@blogger.com0tag:blogger.com,1999:blog-4939875814284471727.post-26189977134546117852012-11-20T16:30:00.001+01:002012-11-20T16:30:54.271+01:00systemd (and dracut) in next openSUSESome weeks ago, I had the pleasure to do a talk at the <a href="http://conference.opensuse.org/">openSUSE conference</a> in Prague, about <a href="http://www.freedesktop.org/wiki/Software/systemd/">systemd</a> (its current state in openSUSE and what we plan for the future) and <a href="https://dracut.wiki.kernel.org/index.php/Main_Page">dracut</a> (mkinitrd replacement).<br />
<br />
For those of you who didn't attend the conference, you can watch my talk on <a href="http://www.youtube.com/watch?v=aUmmaQGYnVo">YouTube</a> or <a href="http://blip.tv/openSUSEtv/riker-tue-3-6414327">Blip.tv</a> (thanks to openSUSE awesome video team for the recording): <br />
<div class="separator" style="clear: both; text-align: center;">
<iframe allowfullscreen='allowfullscreen' webkitallowfullscreen='webkitallowfullscreen' mozallowfullscreen='mozallowfullscreen' width='320' height='266' src='https://www.youtube.com/embed/aUmmaQGYnVo?feature=player_embedded' frameborder='0'></iframe></div>
<br />And you can even get my <a href="https://docs.google.com/open?id=0B9-rayO7YPaZYnlab2RaVkl2S0E">slides</a> ;)Anonymoushttp://www.blogger.com/profile/03724661663218761139noreply@blogger.com0tag:blogger.com,1999:blog-4939875814284471727.post-44926320548490732682012-07-30T11:53:00.000+02:002012-08-21T13:50:24.229+02:00My hackweek8 project: dracutNow that SUSE Hackweek 8 is over, here is recap of my own project and how it went:<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="http://1.bp.blogspot.com/-KH-Ck35hTCw/UAkPptAJ90I/AAAAAAAAAvI/FBzlkn1qTm8/s1600/IMG_20120720_095649.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="320" src="http://1.bp.blogspot.com/-KH-Ck35hTCw/UAkPptAJ90I/AAAAAAAAAvI/FBzlkn1qTm8/s320/IMG_20120720_095649.jpg" width="240" /></a></div>
<br />
I've worked on <a href="https://dracut.wiki.kernel.org/index.php/Main_Page">dracut</a> (a mkinitrd replacement), to see if it works nicely on openSUSE (with the hope to replace the three different initrd we have in openSUSE, main one created by mkinitrd, the one used by YaST installer and a third one in kiwi).<br />
<br />
Fortunately, I was not alone working on dracut for openSUSE. Thomas Renniger had started packaging dracut for openSUSE and I was able to reuse his work and improve it. Moreover, Mike Gorse uses his hackweek to also improve dracut (adding support for CIFS for instance).<br />
<br />
<ul>
<li>Day 1:</li>
</ul>
<ul><ul>
<li>cleaned up dracut package (done by trenn), to meet openSUSE standard, remove any Fedora specific stuff in it and update it to latest dracut package, available <strike>at <a href="https://build.opensuse.org/package/show?package=dracut&project=home%3Afcrozat%3Abranches%3ABase%3ASystem%20">https://build.opensuse.org/package/show?package=dracut&project=home%3Afcrozat%3Abranches%3ABase%3ASystem</a></strike> in openSUSE:Factory.<strike><br /></strike></li>
</ul>
</ul>
<ul><ul>
<li>update hardlink package (available atm in Java:base, will move it to Base:System), needed for dracut at runtime. Available <strike>at <a href="https://build.opensuse.org/package/show?package=hardlink&project=home%3Afcrozat%3Abranches%3AJava%3Abase">https://build.opensuse.org/package/show?package=hardlink&project=home%3Afcrozat%3Abranches%3AJava%3Abase</a></strike> in openSUSE:Factory too<strike>.</strike></li>
</ul>
</ul>
<ul><ul>
<li>modified my own grub2 configuration to add a additional dracut menu entry (hard coded atm)</li>
<li>succesfully booted a 12.2 VM with dracut image ! </li>
</ul>
<li>Day 2:</li>
<ul>
<li>discussed with upstream if they would accept "compatibility" patches to team dracut about openSUSE / SLE own initrd command line and got no as an answer, because they don't want to maintain compability cruft on their own side.</li>
<li>worked on a separate module which is able to convert at boot time SUSE initrd commands into dracut one (when they are available). Works fine for "shell=1" "linuxrc=trace" and "sysrq". Upstream proposed to review the module for mistake when we are done with it</li>
<li>asked upstream if they were interested in "sysrq" feature for dracut. No response yet</li>
<li>worked on separate journal (reiserfs / XFS). Need to create VM to test it and ask upstream if they want to integrate it</li>
</ul>
<li>Day 3:</li>
<ul>
<li>got trenn cflags patch merged upstream</li>
<li>continue digging into dracut internals</li>
<li>journaldev is working on boot command line (tested with XFS)</li>
<li>need improvement to configure initrd with system fstab value, when available and try to use a more generic term (root.journaldev)</li>
</ul>
<li>Day 4:</li>
<ul>
<li>subscribed to initramfs mailing list</li>
<li>got my first patch merged upstream (journaldev support)</li>
<li>added cmdline support for mduuid and isci (TargetAddress / TargetPort / TargetName), untested (don't have the right setup)</li>
<li>ran test suite, found some issues: some in dracut upstream (fixed immediatly by upstream), some in our package (fixed mdadm and device-mapper to not call blkid binary but use udev builtin-blkid, will be faster and we save some fork ;)</li>
</ul>
<li>Day 5:</li>
<ul>
<li>sr mdadm and device-mapper fixes</li>
</ul>
<ul>
<li>tried to get all test suite to pass</li>
<ul>
<li>some fixes were made to dracut, with more test passing</li>
<li>still getting issue with network based test (NFS, iSCSI, etc..). Partially working (DHCP server is working now in test suite), partially not (impossible to mount stuff in server test image, getting "EUID=1000" for root, even when booting the image with init=/bin/sh .. No clue to fix that and upstream never got this issue either, if you have an idea, I'm all ears..)</li>
</ul>
</ul>
</ul>
<br />
<br />
In short, this hackweek worked well for me, even if I didn't finished all I wanted to do. I'll make sure everything is pushed in Factory soon, so we could try (maybe) to switch openSUSE 12.3 to dracut.Anonymoushttp://www.blogger.com/profile/03724661663218761139noreply@blogger.com6tag:blogger.com,1999:blog-4939875814284471727.post-3481020231874255882011-08-23T17:53:00.001+02:002011-08-23T17:53:34.328+02:00GNOME 3.0 Live image release 1.5.0 availableHi all,<br />
<a href="http://www.flickr.com/photos/fcrozat/6055381155/" title="Geeko from the inside de fcrozat, sur Flickr"><img alt="Geeko from the inside" height="180" src="http://farm7.static.flickr.com/6085/6055381155_344f265207_m.jpg" width="240" /></a>
<br />
I just push a new GNOME 3.0 live image labelled as 1.5.0 (yes, I forgot to push 1.4.0 after I built it, so we are at 1.5.0 now ;)<br />
<br />
No big changes, it is based on GNOME 3.0.2 + some additional fixes.<br />
<br />
As always, it can be downloaded from <a href="http://www.gnome.org/getting-gnome/">http://www.gnome.org/getting-gnome/</a><br />
<br />
For people interested, here are some download hits (it doesn't include SUSE Studio appliance nor promo dvd which is also available from GNOME ftp) :<br />
<br />
on GNOME 3.0 release day : 4526 hits<br />
April : 145904 hits<br />
May : 46551 hits <br />
June : 24747 hits <br />
July : 23611 hits <br />
August (from 1 to 15) : 13063 hits<br />
<br />
Enjoy !Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com14Paris, France48.856614 2.352221948.773036 2.1942934 48.940192 2.5101504tag:blogger.com,1999:blog-4939875814284471727.post-51415920056746391812011-08-04T15:38:00.004+02:002011-08-04T16:50:12.620+02:00Map for Desktop Summit 2011I've cooked with other people from #gnomefr channel a Google Map with the various useful addresses for Desktop Summit 2011.<br />
<br />
It is available <a href="http://maps.google.com/maps/ms?msa=0&msid=205409213360271391765.0004a9ad04e73d10f3d32">here</a>, you can also get <a href="http://maps.google.com/maps/ms?authuser=0&vps=2&ie=UTF8&msa=0&output=kml&msid=205409213360271391765.0004a9ad04e73d10f3d32">KML</a> file or import this map in your favorite software (for Android users, I suggest using <a href="https://market.android.com/details?id=menion.android.locus">Locus Free </a>which can download offline OpenStreetMap data and merge our map on it, no roaming data needed !).Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com0tag:blogger.com,1999:blog-4939875814284471727.post-89681652725546707632011-08-03T18:32:00.000+02:002011-08-03T18:32:08.799+02:00Berlin, Berlin<div class="separator" style="clear: both; text-align: center;">
<a href="https://desktopsummit.org/" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="105" src="https://www.desktopsummit.org/sites/www.desktopsummit.org/files/DS2011banner.png" width="320" /></a></div>
I've just finish slides for my talk <a href="https://www.desktopsummit.org/program/sessions/git-full-insert-your-desktop-here-os-image-few-click">From GIT to your custom OS image</a> which will be on<a href="https://www.desktopsummit.org/program/item/7-august-1510-1540"> Sunday 7 August 15:10 - 15:40</a> at <a href="https://www.desktopsummit.org/program/rooms/rm3038">Rm3038</a>. I'll explain how GNOME 3 Live images were built and how you can easily do the same for your project.<br />
<br />
I'll also be on <a href="http://opensuse.org/">openSUSE</a> booth and helping for <a href="https://www.desktopsummit.org/program/football">Football event</a> which is sponsored by<br />
<a href="http://www.suse.com/" imageanchor="1"><img alt="SUSE" border="0" src="http://www.suse.com/common/img/logo.png" /></a><br />
<br />
See you in Berlin !<br />
<div class="fieldgroup group-schedule">
<div class="content">
<div class="field field-type-nodereference field-field-session-room">
<div class="field-items">
<div class="field-item odd">
</div>
</div>
</div>
</div>
</div>
Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com0Paris, France48.856614 2.352221948.773036 2.1942934 48.940192 2.5101504tag:blogger.com,1999:blog-4939875814284471727.post-53576431632353016392011-07-01T18:11:00.001+02:002011-07-01T18:13:35.203+02:00Status update on systemd for openSUSE FactoryHi all, <br />
<br />
here is a update on the work done on systemd for Factory :<br />
<br />
(beware, post is long !)<br />
<br />
<a href="http://www.flickr.com/photos/fcrozat/5873372668/" title="Escargot de fcrozat, sur Flickr"><img alt="Escargot" height="240" src="http://farm6.static.flickr.com/5157/5873372668_0a0bb10b71_m.jpg" width="160" /></a><br />
<br />
<ul><li>basic support for systemctl in chkconfig and insserv is done : it is pending review by maintainer before integration</li>
<li>support for --root in systemctl was merged upstream and will be used by chkconfig/insserv patches above.</li>
<li>a patch has been submitted to upstream systemd to parse insserv.conf : this patch only handles the "system facility" part of insserv.conf and automatically adds depencies specified in the file</li>
<li>quick investigation on Yast2 to adapt runlevel editor for systemctl support : we really need help from other people, as I don't have any knowledge of Yast internal and it seems the yast dbus client part might be missing some parts, needed for runlevel editor to talk with systemd.</li>
<li>no work done on /usr as separate partition : it is not a systemd issue in itself but from other programs which might be using data from /usr before /usr is available. The best solution would be to mount /usr from initrd => help needed !!</li>
<li>(open)SUSE is using unofficial LSB target named $ALL which is supposed to put services requiring it at the end of the boot sequence (or at the beginning of shutdown sequence); After discussing with upstream : on a static boot system (sysvinit), it is easy to resolve such dependencies, but it isn't on a dynamic system (systemd). There is a ugly hack to handle that (creating a ALL.target file which is starting after default.target is done) but it would be probably better to just fix the 4 initscripts which are still using $ALL ( amazon-late, stoppreload, Susefirewall2_setup and vboxes). I'll open bug for them.</li>
<li>X-Interactive support in systemd is not working properly : it will only work before getty is started and is broken if you try to start a service after boot. We need to transition packages which are still using X-Interactive to systemd-ask-password (which takes care of the async conversation). Only two packages need to be ported :</li>
<ul><li>apache2, when querying password for SSL certificate : apache allows to start a script to handle the password request. We only need to plug the script and configuration part in our package<br />
and get it used when booting with systemd.</li>
<li>openvpn : this one is a bit complex because we can either write a daemon which would do the interface between systemd and openvpn management interface or we can try to patch openvpn to have a similar feature as apache and get this patch upstreamed. The latter has the preference of systemd upstream.</li>
<li>For both packages, help is welcome.</li>
<li>For compability with sysvinit, support for <interactive> from /etc/insserv.conf in systemd was not added, so we could remove X-Interactive from openvpn/httpd sysvinit scripts but still have the function when booting from /sbin/init, thanks to /etc/insserv.conf list.</interactive></li>
</ul><li>/etc/init.d/kbd was not handled properly : this should be fixed inFactory today or tomorrow, with systemd taking care of setting up keyboard properly. However, we might need to improve /etc/sysconfig/keyboard parsing in systemd. More tests are needed (and of course, help is welcome).</li>
<li>discussion in progress on opensuse-packaging mailing list and upstream on a set of cross distribution RPM macros to handle systemd unit files. </li>
</ul>As you can see, we still have some work to do, but we need everybody help : either on the issues I mentioned (feel free to say "I want to help on this" here) or to do more tests or even to start creating .service files (but we still need to fix the issues listed above). <br />
<br />
Thanks everybody for your attention.<br />
<br />
I would be great if we could get the ball moving and maybe get one of<br />
the next Factory milestone be a "systemd" test release but to reach this<br />
point, we need YOU !Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com0tag:blogger.com,1999:blog-4939875814284471727.post-20807315415797523172011-06-10T18:57:00.002+02:002011-06-10T19:02:17.624+02:00The road to systemd for openSUSE 12.1Hi all,<br />
<br />
<a href="http://www.flickr.com/photos/fcrozat/23066134/" title="img_2326 de fcrozat, sur Flickr"><img alt="img_2326" height="180" src="http://farm1.static.flickr.com/19/23066134_43bdfd7b1a_m.jpg" width="240" /></a><br />
<br />
<a href="http://www.freedesktop.org/wiki/Software/systemd">systemd</a> is coming for next openSUSE (12.1) scheduled next fall.<br />
<br />
I'll help for <a href="http://en.opensuse.org/SDB:Systemd">systemd integration in openSUSE Factory</a> and will act as an interface between you (openSUSE testers, packagers, developers) and systemd upstream.<br />
<br />
As you might guess, switching boot manager is not a trivial task and issues will be found. So, we want to have as much feedback and testing as possible, to try to tackle as much (if not all) issues in time for 12.1.<br />
<br />
Here is our action plan, in several phases: <br />
<ul><li>phase 1: <i>detecting current issues with systemd</i>. Install systemd package and "manually" boot with it, by adding "init=/bin/systemd" at you kernel boot command line. In this setup, we want to find ALL the issues caused by switching to systemd, so please, check <a href="http://en.opensuse.org/openSUSE:Systemd_status">systemd on Factory status </a>page and follow the instructions there to fill bug reports. We also want to ensure there is no regression, when using legacy sysvinit initscripts with systemd as boot manager.</li>
<li>phase 2: <i>systemd-sysvinit package installed by default and replace sysvinit. </i></li>
<li> phase 3: <i>providing systemd unit files to replace legacy sysvinit initscripts</i>: this is a huge task which won't be completed before openSUSE 12.1, but it can be parallelized among a lot of people (ideally, each packager should be able to create unit systemd file). And we should also split this effort in manageable milestones :</li>
<ul><li>phase 3.1: GNOME and KDE live CDs should only use "native" systemd, without any sysvinit involved</li>
<li>phase 3.2: installed system using GNOME and KDE live CDs be a "native" systemd (this involves testing additional paths in live installer)</li>
<li>phase 3.3: install from DVD for GNOME and KDE should be "native" systemd</li>
</ul></ul>Of course, providing systemd unit file should not be a pure "openSUSE" task, because the ultimate goal for those files is to be cross-distribution and merged in relevant upstream projects. And we also don't want to duplicate effort which is starting in other distributions like Fedora, so, collaboration is key. I strongly recommend reading <a href="http://0pointer.de/blog/projects/systemd-for-admins-3.html">systemd for Administrators, Part III</a> post about the conversion (and also all other posts : <a class="http" href="http://0pointer.de/blog/projects/systemd-for-admins-1.html">systemd for Administrators #1</a>, <a class="http" href="http://0pointer.de/blog/projects/systemd-for-admins-2.html">#2</a>, <a class="http" href="http://0pointer.de/blog/projects/systemd-for-admins-3.html">#3</a>, <a class="http" href="http://0pointer.de/blog/projects/systemd-for-admins-4.html">#4</a>, <a class="http" href="http://0pointer.de/blog/projects/three-levels-of-off">#5</a>, <a class="http" href="http://0pointer.de/blog/projects/changing-roots.html">#6</a>, <a class="http" href="http://0pointer.de/blog/projects/blame-game.html">#7</a>,<a class="http" href="http://0pointer.de/blog/projects/the-new-configuration-files">#8</a> they are highly instructive). <br />
<br />
For discussing / helping with systemd integration for Factory, please use <a href="http://lists.opensuse.org/opensuse-factory/">opensuse-factory</a> mailing list or go to #opensuse-factory IRC channel on Freenode.<br />
<br />
We need your help to make sure openSUSE 12.1 will use systemd at 200% ;)Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com2Paris, France48.856614 2.352221900000017748.813328 2.2293609000000179 48.8999 2.4750829000000176tag:blogger.com,1999:blog-4939875814284471727.post-91223819740741756242011-05-23T14:56:00.000+02:002011-05-23T14:56:33.562+02:00GNOME 3 Live image release 1.3.0 - VirtualBox, here we comeHi all,<br />
<br />
<a href="http://www.flickr.com/photos/fcrozat/2872854561/" title="Génie de la Bastille de fcrozat, sur Flickr"><img alt="Génie de la Bastille" height="240" src="http://farm4.static.flickr.com/3279/2872854561_f15c703713_m.jpg" width="160" /></a><br />
<br />
good news for Virtual Machine addicts : <a href="http://virtualbox.org/">VirtualBox</a> team has fixed issues which were preventing VirtualBox to work properly with GNOME Shell. You need VirtualBox release 4.0.8 (minimum) and GNOME 3 live image release 1.3.0 (it contains updated VirtualBox guest additions, required for openGL).<br />
<br />
To download the image : <a href="http://www.gnome.org/getting-gnome/">http://www.gnome.org/getting-gnome/</a><br />
<br />
Enjoy.Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com3tag:blogger.com,1999:blog-4939875814284471727.post-68785158038086606302011-05-15T17:34:00.000+02:002011-05-15T17:34:44.108+02:00ISO image for GNOME3 promo DVD available for downloadHi all,<br />
<br />
<a href="http://www.flickr.com/photos/fcrozat/5656931259/" title="GNOME 3 promo DVD de fcrozat, sur Flickr"><img alt="GNOME 3 promo DVD" height="180" src="http://farm6.static.flickr.com/5147/5656931259_afc09b080a_m.jpg" width="240" /></a><br />
<br />
a quick post for people who want the GNOME 3 promo DVD iso image (it is based on 1.1.0 image, combining both x86 and x86-64 images and some demo video and music).<br />
<br />
You can download it at : <a href="http://ftp.gnome.org/pub/GNOME/misc/promo-dvd/">http://ftp.gnome.org/pub/GNOME/misc/promo-dvd/</a><br />
<br />
Beware this image will not be updated, it is just there for archiving purpose.Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com0Paris, France48.8566667 2.350987099999997648.813364199999995 2.2280825999999974 48.8999692 2.4738915999999977tag:blogger.com,1999:blog-4939875814284471727.post-80835297417459484932011-04-30T11:35:00.000+02:002011-04-30T11:35:56.639+02:00GNOME 3 Live image 1.2.0 released / GNOME 3.0.1 for openSUSE 11.4Hi everyone,<br />
<a href="http://www.flickr.com/photos/fcrozat/5656931259/" title="GNOME 3 promo DVD de fcrozat, sur Flickr"><img alt="GNOME 3 promo DVD" height="180" src="http://farm6.static.flickr.com/5147/5656931259_afc09b080a_m.jpg" width="240" /></a><br />
<br />
two news for this week-end :<br />
<ul><li>GNOME 3.0.1 is now available for openSUSE 11.4, in GNOME:STABLE:3.0 repository. See <a href="http://en.opensuse.org/openSUSE:GNOME_3.0">http://en.opensuse.org/openSUSE:GNOME_3.0</a> on how to use this repository.</li>
<li>Live image has been regenerated to use GNOME 3.0.1. It is available at <a href="http://www.gnome.org/getting-gnome/">http://www.gnome.org/getting-gnome/</a> (version 1.2.0)</li>
</ul>Oh, I forgot : GNOME3 promo DVDs have been delivered to GNOME Foundation ;)<br />
<br />
Enjoy !Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com2Paris, France48.8566667 2.350987099999997648.813364199999995 2.2280825999999974 48.8999692 2.4738915999999977tag:blogger.com,1999:blog-4939875814284471727.post-63047235626168897742011-04-22T22:02:00.000+02:002011-04-22T22:02:26.057+02:00GNOME 3 Live image version 1.1.0 releasedHi everyone, it is me again (yes, I know two posts in two days, incredible ;)<br />
<br />
<a href="http://www.flickr.com/photos/fcrozat/3438569005/" title="Boat over sunset de fcrozat, sur Flickr"><img alt="Boat over sunset" height="125" src="http://farm4.static.flickr.com/3315/3438569005_e871548ef0_m.jpg" width="240" /></a><br />
<br />
In the past week, we have been working on both GNOME:STABLE:3.0 repository and on creating a GNOME 3 Promo DVD, based on this live image, but with more content on it (LibreOffice, Banshee 2.0, etc..). Because of this, image size has increased a bit (950MB)<br />
<br />
Good news too, we fixed KMS issues with some Radeon cards people reported when using live image (problem was fixed once the image was installed).<br />
<br />
This new image (1.1.0) is now based on GNOME:STABLE:3.0 repository and contains all security and bugfix updates for openSUSE 11.4.<br />
<br />
To download the image, go to <a href="http://www.gnome.org/getting-gnome/">http://www.gnome.org/getting-gnome/</a><br />
<br />
Enjoy !Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com5Paris, France48.8566667 2.350987099999997648.813364199999995 2.2280825999999974 48.8999692 2.4738915999999977tag:blogger.com,1999:blog-4939875814284471727.post-63109357927628659052011-04-21T19:07:00.000+02:002011-04-21T19:07:43.684+02:00GNOME 3.0 available for openSUSE 11.4Hi everyone,<br />
<br />
<a href="http://www.flickr.com/photos/fcrozat/3282596856/" title="Asterix by fcrozat, on Flickr"><img alt="Asterix" height="160" src="http://farm4.static.flickr.com/3392/3282596856_5301aa2c05_m.jpg" width="240" /></a><br />
<br />
openSUSE GNOME team has been busy polishing GNOME 3.0 packages for openSUSE 11.4 but here they are, for your pleasure<br />
<br />
<br />
Everything is explained at : <a href="http://en.opensuse.org/openSUSE:GNOME_3.0">http://en.opensuse.org/openSUSE:GNOME_3.0</a><br />
including : <br />
<ul><li>how to install GNOME 3 using 1-click install from your favorite Web browser,</li>
<li>how to switch from my previous repository (home:fcrozat:gnome3, which will be soon phased out) to the new repository. This is important to continue receiving updates, for instance, if you installed live image on your system.</li>
</ul><br />
A new live image will be available shortly, based on this new repository (but this will be for another blog post).<br />
<br />
Enjoy !Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com10Paris, France48.8566667 2.350987099999997648.813364199999995 2.2280825999999974 48.8999692 2.4738915999999977tag:blogger.com,1999:blog-4939875814284471727.post-8620601673270754662011-04-07T07:11:00.002+02:002011-04-07T07:11:46.023+02:00GNOME3 Live image 1.0.0 released - It is about timeHi everybody,<br />
<a href="http://www.flickr.com/photos/fcrozat/2872854561/" title="Génie de la Bastille de fcrozat, sur Flickr"><img alt="Génie de la Bastille" height="240" src="http://farm4.static.flickr.com/3279/2872854561_f15c703713_m.jpg" width="160" /></a><br />
just in time for GNOME 3.0 release, I'm please to announce GNOME 3 Live Image version 1.0.0 release.<br />
<br />
As you might expect, this release is built with GNOME 3.0.0. Other features, compared to latest image release :<br />
<ul><li>radeon KMS should be fixed (it was preventing GNOME Shell to start since version 0.3.1)</li>
<li>speech-dispatcher is used for speech synthesis (ie Orca)</li>
<li>tracker is installed on the image</li>
<li>more fonts are installed by default</li>
</ul>Live installer is also available from the running image, just search for "live" in GNOME-Shell overview panel (or you can still start the live install by adding liveinstall to boot command line).<br />
<br />
As always, you can download the image from <a href="http://gnome3.org/tryit.html">http://gnome3.org/tryit.html</a><br />
<br />
For openSUSE 11.4 users, we will soon make a stable repository available with GNOME 3.0, watch this space for more info ;)<br />
<br />
<a href="https://live.gnome.org/ThreePointZero/Promote" title="Help promote GNOME 3!"><img alt="I am GNOME" border="0" src="http://www.gnome.org/wp-content/uploads/2011/04/iamgnome.png" /></a><br />
As a side note, I'd like to thanks my employer (<a href="http://www.novell.com/">Novell</a>) and my managers who allowed me to work on GNOME 3 for weeks fulltime.<br />
<br />
Enjoy.Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com6tag:blogger.com,1999:blog-4939875814284471727.post-18889624479169829012011-03-30T18:24:00.000+02:002011-03-30T18:24:51.613+02:00GNOME3 live image 0.3.1 releasedHello again,<br />
<a href="http://www.flickr.com/photos/fcrozat/3006345420/" title="Yak & Yeti logo de fcrozat, sur Flickr"><img alt="Yak & Yeti logo" height="160" src="http://farm4.static.flickr.com/3219/3006345420_db1138784e_m.jpg" width="240" /></a><br />
<br />
I just did a quick update to GNOME 3 live image, to fix some issues people discovered in previous images :<br />
<ul><li>radeon / r600g openGL drivers have been switched to use gallium : they should be more stable with GNOME-Shell</li>
<li>GNOME Control Center system information correctly detects graphics card on your system</li>
<li>Empathy accounts panel is back in GNOME Control Center</li>
</ul>As always, you can download it from <a href="http://gnome3.org/tryit.html">http://gnome3.org/tryit.html</a>. If you want to install this image on a system, just add "liveinstall" on the boot command line.<br />
<br />
Enjoy !Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com15Paris, France48.8566667 2.350987099999997648.813364199999995 2.2280825999999974 48.8999692 2.4738915999999977tag:blogger.com,1999:blog-4939875814284471727.post-69464800873055003922011-03-29T23:01:00.001+02:002011-03-30T07:14:39.686+02:00GNOME3 Live Image version 0.3.0 releasedYou know the drill, another week, another release.<br />
<br />
<a href="http://www.flickr.com/photos/fcrozat/2521598602/" title="Want some colors ? de fcrozat, sur Flickr"><img alt="Want some colors ?" height="240" src="http://farm3.static.flickr.com/2130/2521598602_41b3401d3a_m.jpg" width="160" /></a><br />
<br />
Release team decided to do another call for tarballs to fix some bugs across the entire GNOME3 platform, so 2.91.93 was released yesterday.<br />
<br />
And today, you can download GNOME Live Image 0.3.0, which contains all the fixes from 2.91.93 tarballs.<br />
<br />
Url to download it hasn't changed : <a href="http://gnome3.org/tryit.html">http://gnome3.org/tryit.html </a><br />
<br />
Enjoy !Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com11Paris, France48.8566667 2.350987099999997648.813364199999995 2.2280825999999974 48.8999692 2.4738915999999977tag:blogger.com,1999:blog-4939875814284471727.post-71268656866610594742011-03-25T21:41:00.000+01:002011-03-25T21:41:51.182+01:00GNOME 3 live image release 0.2.0 is outAnother week, another release<br />
<br />
<a href="http://www.flickr.com/photos/fcrozat/3740738702/" title="Cat looking at the sea de fcrozat, sur Flickr"><img alt="Cat looking at the sea" height="240" src="http://farm3.static.flickr.com/2424/3740738702_4b88377577_m.jpg" width="160" /></a><br />
<br />
This week release is version 0.2.0. It features GNOME 2.91.92, including :<br />
<ul><li>soon to be released Network Manager 0.9 and new UI integrated in GNOME Shell and GNOME Control Center (be careful, it has still rough edges)</li>
<li>a11y support should be improved</li>
</ul><br />
If you have installed this image or if you use the <a href="http://draft.blogger.com/">home:fcrozat:gnome3</a> openSUSE and want to upgrade to 2.91.92, you can update using <i>zypper up</i> (if you still want to keep Network Manager 0.8) or <i>zypper dup</i> (if you want to switch to NM 0.9). Some packages might be uninstalled in the process.<br />
<br />
Image is, as always, available at <a href="http://gnome3.org/tryit.html">http://gnome3.org/tryit.html</a><br />
<br />
Enjoy !Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com13Paris, France48.8566667 2.350987148.7437227 2.1175276000000003 48.9696107 2.5844466tag:blogger.com,1999:blog-4939875814284471727.post-58644575928739685632011-03-20T21:00:00.000+01:002011-03-20T21:00:20.791+01:00GNOME 3 Live image, release 0.1.1As always, another week, another release, aka 0.1.1<br />
<a href="http://www.flickr.com/photos/fcrozat/3777290817/" title="Burano Cats de fcrozat, sur Flickr"><img alt="Burano Cats" height="160" src="http://farm3.static.flickr.com/2628/3777290817_9d3513c85f_m.jpg" width="240" /></a><br />
This week release is a polish release : <br />
<ul><li>very few package changes</li>
<li>many services are disabled when booting live CD, improving its loading speed</li>
<li>password is no longer asked at all in live CD for root or standard (tux) user</li>
<li>when installing the image on a system (add liveinstall parameter on bootloader), some services are enabled back (apparmor, preload, firewall), thanks to Chris comments</li>
</ul>Another service announcement :<br />
my GNOME3 openSUSE 11.3 repository will soon be removed ; packages will be only available for openSUSE 11.4 (same <a href="https://build.opensuse.org/project/show?project=home%3Afcrozat%3Agnome3">OBS project</a>). Therefore, I strongly suggest to upgrading your system to openSUSE 11.4.<br />
<br />
You know the url to fetch the latest release : <a href="http://gnome3.org/tryit.html">http://gnome3.org/tryit.html</a><br />
<br />
Enjoy !Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com4Paris, France48.8566667 2.350987148.7437227 2.1175276000000003 48.9696107 2.5844466tag:blogger.com,1999:blog-4939875814284471727.post-79462175026658306542011-03-11T20:22:00.000+01:002011-03-11T20:22:51.191+01:00GNOME 3 Live image 0.1.0 released - Geeko strikes backAnother week, another release.<br />
<br />
<br />
<a bitly="BITLY_PROCESSED" href="http://www.flickr.com/photos/fcrozat/18537394/" title="add.jpg de fcrozat, sur Flickr"><img alt="add.jpg" height="180" src="http://farm1.static.flickr.com/14/18537394_1e76d46aa5_m.jpg" width="240" /></a><br />
<br />
This week has been a busy week : GNOME people worked really hard on 2.91.91 release and openSUSE people worked really hard on release <a bitly="BITLY_PROCESSED" href="http://news.opensuse.org/2011/03/10/opensuse-11-4/">openSUSE 11.4</a>.<br />
<br />
So, let's please everybody with this week GNOME 3 Live image 0.1.0 : it features GNOME 2.91.91 on top of the brand new openSUSE 11.4.<br />
<br />
If you tested previous live image, you'll notice a lot of changes, so don't be surprised :<br />
- image is no longer persistent when installed on USB stick : it was slowly first boot a lot (and we don't want to give people testing the image it is slowww) and sometime, if shutdown wasn't done properly, the persistent partition could become corrupted and you had to either remove it completely or redump the key<br />
- language / keyboard / timezone selection at startup is gone : again, it was slowing the boot and the experience was completely different from GNOME3 experience. But you can still choose the language (as well as keyboard / timezone) : either in the boot menu at startup or later, in GNOME Control Center (in GNOME Shell, top right menu then System Settings and Regions / Language)<br />
- no more password for demo user (named 'tux' ) nor root user : again, simplicity prevaled. If you get asked a password at any time, just press <i>enter</i>.<br />
- virtualbox guest support is not available (temporary issue for this image and we still don't support GNOME Shell in virtualbox)<br />
- a lot of translations have been added<br />
- many GNOME packages have been ported to GNOME 3 platform and are preinstalled in the image<br />
- since we rebased the image on openSUSE 11.4, we will try to stick to kernel and X11 drivers shipped with it.<br />
<br />
As always, you'll find the image at <a bitly="BITLY_PROCESSED" href="http://gnome3.org/tryit.html">http://gnome3.org/tryit.html</a> <br />
<br />
<br />
Enjoy.<br />
<br />
(Yes, I know above photo isn't a gecko but I only had iguane in my photo albums :)Fredhttp://www.blogger.com/profile/05183076812550842311noreply@blogger.com7