Sonja Krause-Harder
posted at
eeeSUSE II
USB stick and installation instructions are online:
OpenSUSE on the EeePC
Thanks for your patience ;-)
OpenSUSE on the EeePC
Thanks for your patience ;-)
Stanislav Visnovsky
posted at
YaST User Interface Library is now independent of YaST
Thanks to hard work of the YaST team hackers HuHa, Bubli, Ricardo and others, the YaST user interface library is now fully independent of the YaST infrastructure. What does it mean? In short, there is now a standalone C++ library that provides API independent of particular toolkit. The current backends are Qt, Gtk+ and ncurses, so the same code can have use the interface written in any of those.
The YaST UI library provides a very simple API to build rather complex but still consistent user interfaces. The particular implementation of the interface depends on the chosen backend - Qt, Gtk+ or ncurses. The primary target for this library is YaST, Yet Another Setup Tool developed for installation and configuration of SUSE products.
However, the library was very deeply tied to the rest of YaST infrastructure which made it nearly impossible to use it outside of YaST. Not anymore. Very soon, there will be packages available in openSUSE that provide the library independently of YaST, so any application that might need to provide both graphical as well as textual interface can easily do so. They provide also examples how to use the library from pure C++.
For future, I believe it makes sense to have a shiny new name for this library (YUI also means Yahoo UI) and I've tried to persuade the team on their IRC channel, but there were no good proposals for those. So, for now, we have the great functionality unleashed outside of YaST, with the old and pretty generic name YUI. Happy hacking!
The YaST UI library provides a very simple API to build rather complex but still consistent user interfaces. The particular implementation of the interface depends on the chosen backend - Qt, Gtk+ or ncurses. The primary target for this library is YaST, Yet Another Setup Tool developed for installation and configuration of SUSE products.
However, the library was very deeply tied to the rest of YaST infrastructure which made it nearly impossible to use it outside of YaST. Not anymore. Very soon, there will be packages available in openSUSE that provide the library independently of YaST, so any application that might need to provide both graphical as well as textual interface can easily do so. They provide also examples how to use the library from pure C++.
For future, I believe it makes sense to have a shiny new name for this library (YUI also means Yahoo UI) and I've tried to persuade the team on their IRC channel, but there were no good proposals for those. So, for now, we have the great functionality unleashed outside of YaST, with the old and pretty generic name YUI. Happy hacking!
Stanislav Visnovsky
posted at
First blog
OK, so this is my first blog post, so nothing really groundbreaking. I need to learn how this really works and hopefully to start posting something really interesting in a near future.
Ioan Vancea
posted at
Lunch and dinner in Bremen
This weekend we are in Bremen, so here are some images with our Saturday dinner and Sunday lunch.
The dinner to Amico restaurant:

The lunch, Sunday, was to Sailor's Inn Restaurant:
I can say that the food was great ...
If you want to see some photos during our short visit in Bremen feel free to visit my flickr page.
Sonja Krause-Harder
posted at
eeeSUSE ;-)
I could start the hackweek project I _actually_ wanted to do only a little late, and felt really lucky to catch one of these little beasts at all:

This morning I had a USB Stick that didn't get much further than that:

... and a few hours later, 10.3 minimal graphics install with a few hand selected KDE packages:

I will fine tune the image and document what I did, and make it available in the wiki later. For now, thanks to all developers of KIWI and yast2-live-installer, and to the build service user appleonkel, who had all the drivers I needed already packaged -- you rock ;-)
This morning I had a USB Stick that didn't get much further than that:
... and a few hours later, 10.3 minimal graphics install with a few hand selected KDE packages:
I will fine tune the image and document what I did, and make it available in the wiki later. For now, thanks to all developers of KIWI and yast2-live-installer, and to the build service user appleonkel, who had all the drivers I needed already packaged -- you rock ;-)
Florian Reuter
posted at
"XML Namespaces are designed to support exactly this kind of thing.
"XML Namespaces are designed to support exactly this kind of thing." (Tim Bray)
We make really good progress on our interoperability work. In our current focus area of fields we extended the OpenOffice.org Writer core for better support of MS Word-like fields. The first feature which benefits from this work are “Input fields” which now support the long wanted "tabbing" feature.
However we want all fields to benefit from the new enhanced field core --- not only "Input fields". Other areas are e.g "Mail merge fields" etc.. Since all of this fields share the same generic mechanism we decided to add support for this generic MS Word-like fields in OpenOffice.org Writer. But by doing so we faced the problem that ODF is not supporting these kind of fields.
Interestingly Tim Bray (Director of Web Technologies at Sun Microsystems) suggested a solution already in November 2005: http://www.tbray.org/ongoing/When/200x/2005/11/27/Office-XML. Unsurprisingly he suggested XML namespaces to solve this problem.
Thats what we did. MS Word-like fields are now stored in the namespace
xmlns:field="urn:openoffice:names:experimental:ooxml-odf-interop:xmlns:field:1.0"
which clearly indicates the purpose: OOXML<->ODF interoperability.
The following RelaxNG fragment enhanced the current ODF specification with the new fields:
<define name="paragraph-content" combine="choice">
<choice>
<element name="field:fieldmark">
<attribute name="text:name">
<ref name="string"/>
</attribute>
<attribute name="field:type">
<ref name="namespacedToken"/>
</attribute>
<attribute name="field:locked">
<ref name="boolean"/>
</attribute>
<sequence>
<ref name="fieldmark-parameter"/>
<zeroOrMore>
<ref name="paragraph-content"/>
</zeroOrMore>
<sequence>
</element>
<element name="field:fieldmark-start">
<attribute name="text:name">
<ref name="string"/>
</attribute>
<attribute name="field:type">
<ref name="namespacedToken"/>
</attribute>
<attribute name="field:locked">
<ref name="boolean"/>
</attribute>
<ref name="fieldmark-parameter"/>
</element>
<element name="text:fieldmark-end">
</element>
</choice>
</define>
In general fieldmarks are very similar to bookmarks, except that they need to be properly nested. This is achieved by the fact, that a field:fieldmark-end does not have a "name" attribute, but instead closes the last opened field:fieldmark-start element.
The field:fieldmark element is a short form of field:fieldmark-start and field:fieldmark-end. It SHOULD preferably be written instead of start-/end marks.
Every fieldmark can have
- a name (text:name); similar to the name of text:bookmark elements. They SHOULD be unique. (Preferably also with the bookmark names).
- a type (field:type) which allows application to define the type of the fieldmark.
- a sequence of associated (name, value) pair represented by the <field:param field:name=”string” field:value=”string”/>.
- a locked attribute which specifies whether the user can edit the content or not.
A sample. Lets take a loog at the following sample docs:

The OOXML representation is:
<w:p>
<w:r><w:t xml:space="preserve">Title: </w:t></w:r>
<w:bookmarkStart w:id="0" w:name="Text1"/>
<w:r>
<w:fldChar w:fldCharType="begin">
<w:ffData>
<w:name w:val="Text1"/>
<w:statusText w:type="text" w:val="Just a sample field."/>
<w:textInput/>
</w:ffData>
</w:fldChar>
<w:instrText xml:space="preserve"> FORMTEXT </w:instrText>
<w:fldChar w:fldCharType="separate"/>
<w:t xml:space="preserve">A sample input.</w:t>
<w:fldChar w:fldCharType="end"/>
</w:r>
<w:bookmarkEnd w:id="0"/>
</w:p>
<w:p>
<w:r><w:t xml:space="preserve">Description: </w:t></w:r>
<w:bookmarkStart w:id="1" w:name="Text2"/>
<w:r w:rsidR="00FA39C2">
<w:fldChar w:fldCharType="begin">
<w:ffData>
<w:name w:val="Text2"/>
<w:statusText w:type="text" w:val="Yet another sample field..."/>
<w:textInput/>
</w:ffData>
</w:fldChar>
<w:instrText xml:space="preserve"> FORMTEXT </w:instrText>
<w:fldChar w:fldCharType="separate"/>
<w:t>A sample input.</w:t>
</w:r>
</w:p>
<w:p>
<w:r><w:t>Second sample input paragraph.</w:t></w:r>
<w:r><w:fldChar w:fldCharType="end"/></w:r>
<w:bookmarkEnd w:id="1"/>
</w:p>
<w:bookmarkStart w:id="2" w:name="Check1"/>
<w:p>
<w:r>
<w:fldChar w:fldCharType="begin">
<w:ffData>
<w:name w:val="Check1"/>
<w:statusText w:type="text" w:val="A sample checkbox..."/>
<w:checkBox>
<w:checked/>
</w:checkBox>
</w:ffData>
</w:fldChar>
<w:instrText xml:space="preserve"> FORMCHECKBOX </w:instrText>
<w:fldChar w:fldCharType="end"/>
</w:r>
<w:bookmarkEnd w:id="2"/>
<w:r><w:t xml:space="preserve"> Make sense?</w:t></w:r>
</w:p>
The ODF+Enhancement representation is:
<text:p>Title: <field:fieldmark-start text:name="Text1" field:type="ecma.office-open-xml.field.FORMTEXT"><field:param field:name="Description" field:value="Just a sample field."/></field:fieldmark-start>A sample input.<field:fieldmark-end/></text:p>
<text:p>Description: <field:fieldmark-start text:name="Text2" field:type="ecma.office-open-xml.field.FORMTEXT"><field:param field:name="Description" field:value="Yet another sample field..."/></field:fieldmark-start>A sample input.</text:p>
<text:p>Second sample input paragraph.<field:fieldmark-end/></text:p>
<text:p><field:fieldmark text:name="Check1" field:type="ecma.office-open-xml.field.FORMCHECKBOX"><field:param field:name="Description" field:value="A sample checkbox..."/><field:param field:name="Result" field:value="1"/></field:fieldmark><text:s/>Make sense?</text:p>
Cool isn't it. Or with Tim's words: "Who could possibly be against it?"
Klaus Kämpf
posted at
Open Source Meets Business - Day 3 (final)
(continued from here)
The last day of open source meets business had presentations in the morning and put a spotlight on Microsoft in the afternoon.
Systems monitoring with open source
Again, a talk about Nagios. And again, Nagios was choosen for its cost effectiveness. It seems like most commercial monitoring tools charge per monitored device - customers really dislike this. Oberschwaben Klinik uses Nagios to monitor interfaces, infrastructure, services, applications and devices distributed across 200 hosts, 500 services in 6 locations. Total deployment time for Nagios was a single month:- 3 days initial setup
- 1 week learning the tool
- 2 days adaption to infrastructure
- 3 weeks betaphase (getting the alarm thresholds right)
- 3 days finetuning
Software for knowledge worker
Peter Pfläging, working for the City of Wien, pointed out that job roles have changed over the years from being topic specific towards knowledge workers, which he characterizes as- having many tasks
- no applicable standards to approach problems
- coerced to lifetime learning
- lots of brainstorming to find solutions
- decisions makers
- Mind maps OPML: xml data format, Freemind, DeepaMetha, WikkaWiki, Pimki
- Task prioritization GtD, ThinkingRock, d3/dcubed.ca, gtd-php, (Bloggers note: Tracks)
- Wiki Personal Wiki, Moin Moin, TiddlyWiki
- Blogging Weblog with private entries, document your knowledge. WordPress, Typo, Blojsom
- Desktop search For Windows there is Google desktop and Copernic. On Linux Beagle doesn't have a real competitor.
LiMux
Here one learned about the current state of LiMux. The City of Munich choosed to develop their own 'base client' (running on Debian Linux) One thousand workstations are currently migrated (first 100 in 2006, 900 more last year) and about 5000 PCs already use OpenOffice. The base client is 'usability TUV IT certified' (Gebrauchstauglicher Basisclient) and their Linux Lernwelt learning tool won the European E-Learning award last year. The 'base client' core consist of (Debian) Linux, OpenOffice, Firefox and Gimp. Specific applications run browser-based, vintage (windows based) applications use Wine, virtualization or terminal server. The clients are managed by GOsa using FAI for deployment. GOsa itself is a set of PHP5 scripts used for deployment and configuration management (users, groups, mail, dns, dhcp, ...) using LDAP as a central CMDB. For update deployment FAI is currently used, doing inventory, license managementt, log analysis (audit) and hardware-monitoring. The upcoming version 2.6 of GOsa will support scheduled and load balanced mass deployment, replacing FAI.Nagios at Stadtwerke Amberg
The city of Amberg suffers from an understuffed IT department and outsourced monitoring. This works fine with Nagios and the external consulting company is soo great, blah, blah, blah ...How open is Microsoft after the EU ruling ?
This was mostly about the Samba/Microsoft agreement as detailed on Groklaw. Conclusion: with the current business model (public company, maximizing shareholder value), Microsoft will not open up too much.Open source and Microsoft
Sam Ramji, director Open Source and Linux Strategy at Microsoft, tried to put his employer in a good light by pointing out that 50% of all open source deployments are on Windows. Half of all sourceforge projects run on Windows, 3000 are for Windows only. He continued to outline Microsofts open source strategy with Windows at its core, surrounded by OSS applications. (see also this post) A Microsoft based infrastructure (Active Directory, Systems Center, SQL Server) will grow Windows with help of OSS applications. Microsoft will develop free software to support the interface layer between the free and the proprietary world. This is done in the Open Source Software Labs (OSSL), currently established in Redmond and Cambridge, Mass. These labs focus on strategy, technical research and development of document formats, network protocols, security&identy, systems management, virtualization and application platforms. The long term goal is "respectful relationship toproduce insights and technology to compete, interoperate and collaborate". Best quote (Ramji on Ballmer): "Its time to reset peoples perception of what he means when he talks"
Panel Discussion: Microsoft and open source
Dr Oliver Diederich (Heise Verlag) assembled Roger Levy (Novell), Jim Zemlin (Linux Foundation) , Paul Cormier (RedHat), Sam Ramji (Microsoft) and Dr Johannes Helbig (Deutsche Post) to discuss the relationship of Microsoft and the open source movement. The complete discussion was recorded and is available here.
Klaus Kämpf
posted at
Novell Brainshare registration fun
Novell Brainshare will be held March 16-21. 2008 at the Salt Palace Convention Center in Salt Lake City, UT.
Registration is open now and you can also apply for Brainshare Connect to find other conference registrants with similar interests.
The application form asks for your area of expertise, some work information, areas of interest and to choose your hobbies from a predefined list. Among this list are competitive eating and dumpster diving. I just wonder if these groups will do a BOF at Brainshare ...
Klaus Kämpf
posted at
Open Source Meets Business - Day 2
(continued from here)
Workflow management with BPEL
BPEL, the business process execution language, can be used as interface between management (defining/modeling process requirements) and IT (implementing services). Its object-oriented approach makes it possible to divide & conquer large tasks into Business/Architecture/Processes. BPEL allows to apply a consistent and repeteable processes which can be measured/monitored. The basic concept is SOA (service oriented architecture). Bpel adds a recursive aggregation model for web services and workflow mgmt. This all should allow for service orchestration and programming in the large. BPEL is standardized by OASIS as WS-BPEL). A graphical workflow designer and debugger is available through the Eclipse project. One can download an open source implementation of both the BPEL4WS 1.1 specification and the WSBPEL 2.0 standard at http://activebpel.orgOPSI - open pc server integration
OPSI is an open source desktop management system available at http://opsi.org While it is based on a Linux server its primary targets are Windows workstations. Written in Python, it provides inventory, deployment and patch & update management through a java UI. The presenter gave a short demo and highlighted the nice interface for composing database queries. Windows admins wanting to deplay opsi shouldn't be afraid of the command line, though.Complete scalability with integrated virtualization
The title gave the impression of getting some facts and the presenters title of 'Solution Architect' made me actually believe this. Boy was I wrong. I couldn't stand half an hour of marketing fluff and 'Redhat can do it all' without any proof. Had to leave early...VirtualBox
This one was nice. VirtualBox is (yet another) open source virtualization solution. Unlike Xen, it provides full virtualization and is able to run unmodified guest even without hardware (Intel-VT, AMD-V) support. So it plays in the league of VirtualPC, VMware or Parallels. VirtualBox runs on Windows, Linux, MacOS and Solaris and supports all major operating systems (Windos XP, Windows Vista, Linux, Solaris, OS/2). I downloaded a copy and installed it on my OpenSUSE 10.3 laptop during the presentation and was impressed with its nice and intuitive configuration and management interface, highly recommend. VirtualBox is mostly used for windows virtualization and supports Microsofts RDP (remote desktop) protocol, implemented directly in the virtual graphics card. Then the VirtualBox server acts as terminal server, delivering graphical content to (a less powerful) PC. In this configuration, one can even use the USB ports of the dumb terminal, impressive. Other features are snapshots of running clients and shared folders between clients.Collaborative Software Development
This talk, given by a consultant from McKinsey & Company, tried to put a spotlight on the influence open source has on traditional economies. It started to show how working in the open empowers individuals and communities through distributed co-creation, pro-sumption, firm of one / firm of one billion, interactions and collaborations It very much changes how people work and focuses on knowledge workers (see also 'Software for knowledge workers' on day 3) A couple of prominent development in the open projects were named- Linux
- Wikipedia
- we>me textbook (collaborative creation of learning material, see here for a broader scope)
- oscarproject (open car engineering)
- loncin motorcycles china (Using an open development and manufacturing process, they have huge cost savings)
- prosthetics project (prosthetics cad design)
What's next for Open Source
Given by Kim Polese, CEO of SpikeSource, a company selling 'shrink-wrapped' open source solutions, this presentation had a similar topic like the previous one. Key messages were open source is disruptive, dramatic market evolvement, huge effects on global economy. She continued to talk about here company (yes, one can make money with open source) and the usual marketing fluff. Coming trends will be- mass market devices (Google adroid)
- proprietary and o/s convergence (Novells 'mixed source' strategy came into mind)
- virtual appliances
- online marketplaces (Amazon is Linux based)
- consolidation plus proliferation
Open Source Barometer
Alfresco does open source enterprise content management based on a good deal of market analysis. The talk was a preview o the annual open source barometer focussing on the european and german open source market. Lots of graphs, trends and colorful view on the survey results. Looking at Alfresco deployments, there is Windows and Linux equality as an evaluation platform but Linux wins clearly when it comes to actual deployments. Looking more closely at Linux (for hosting Alfresco), SUSE Linux wins over RedHat by a factor of five. However, globally (looking at Linux in general) RedHat has four times more systems out there. Overall, Linux raise is undamped but the Novell/Microsoft patent agreement resulted in a clear kink for SUSE.Linux System Management at Rewe
Yeah, great title and bad content (pure RHN marketing blurb). Go here if you really want more.Nagios at Bundesstelle für Informationstechnik
Driven by ITIL, this german government agency needed- consistent monitoring, platform independent
- fast deployment, extensibility
- transparency
- acceptance by people
- Integration into HP Service Desk + HP Network Node Manager
- Support for UC4
Antje Faber
posted at
Kiss of a cangarooh
Mouse is back from travelling the world. He now looks like a fireman who survived an accident. It's all because of those lobsters. Mouse loves to see them on the barbecue.
And as if that's not enough, he nearly got swallowed by a huge cangarooh that fell in love with him. And then he fell into the sea and was attacked by a flock of fishes. I won't let him travel again.

And as if that's not enough, he nearly got swallowed by a huge cangarooh that fell in love with him. And then he fell into the sea and was attacked by a flock of fishes. I won't let him travel again.
