The Day:
* Updated lynis: Sourcecode 1.2.5
* Updated libatlas3: Added compiler_error_ger_SSE.patch
* Released Translators Version from openSUSE Weekly News Issue #65
* Fixed Section “New/updated Applications” in the Trabslators Version
The Day:
* Updated lynis: Sourcecode 1.2.5
* Updated libatlas3: Added compiler_error_ger_SSE.patch
* Released Translators Version from openSUSE Weekly News Issue #65
* Fixed Section “New/updated Applications” in the Trabslators Version
We’re pleased to announce that as of today the great team of RadioTux will include a summary of openSUSE Weekly News in their German-speaking podcast “Radiotux@HoRads”. It’s planned to make this a fixed part of the shows. Air date will be today between 18:00 CET and 19:30 CET.
So here are the links:
* http://blog.radiotux.de/ – link to RadioTux
* http://blog.radiotux.de/play LIVE
* http://blog.radiotux.de/podcasts – link to the podcasts/archive
Hello Folks,
now following an List from my last updated/worked Packages:
Have a lot of Fun 🙂
Hello Mates,
now following new/updated and published Software:
* Repo: openSUSE:Factory:Contrib:
kde4-skrooge
lynis
python-icalendar
rkhunter
* Repo: KDE/KDE4/Community
kde4-skrooge
* Repo: home:saigkill
boinctray
tktray
I’m very happy. Regularly i’m checkin the Calendar from news.opensuse.org for my work in OpenSUSE Weekly News. It is possible to Download the actual Calendar as *.ics File. But as i understand this, this is a Snapshot. The Calendar not updated himself regularly. So i tried this:
First of all we go to the KOrganizer. Click on the green Cross, left from the Calendararea. Add Calendar. Then we find an Menu similar this:
Then we klicking on “Filecalendar from Remote Computer” (I had translated this on the fly, i’m not shure, that it called so in english). After them we see the next Field:
In this Field i edited :”http://news.opensuse.org/?ec3_ical”. I choosed regularly updating, but no Saving on the Remote Computer.
Now we have the Community Entrys in our Calendar. We see:
If i have understood all right, we have an automatic Calendar. Have fun…
This blog entry is a little bit OffTopic. I’m writing not about an openSUSE Theme, but about
Linux. Last week i’ve chatted with the guys in #coreboot @ freenode and it was very
interesting. This article based on an collaborative PR Project from Carl-Daniel Hailfinger. This first Part of the Article presents Flashrom. The next Article presents Coreboot. The web site of that project is:
The flash utility is known as “Flashrom”.
Flashrom is a universal flash programming utility used to detect, read, erase, or write BIOS
chips (parallel, LPC, FWH and SPI technologies) in various packages (DIP, PLCC, SOIC).
It can be used to flash firmware images such as traditional BIOS or coreboot or to back up
the existing firmware.
Everybody who does not want to boot DOS or Windows just to perform a BIOS update can use
flashrom. It does not require a graphics card, monitor or keyboard and can even be used
over SSH on a remote machine. You do not have to reboot to run flashrom, but it is recommended
to reboot after a successful update. Many people are using flashrom as a replacement for
the various AMI/Award/Phoenix BIOS flashing tools out there.
Flashrom supports over 100 flash chips and it is really easy to add support for a new chip
if your board happens to have an unsupported chip.
Flashrom has its own home page: http://www.coreboot.org/Flashrom
It is free software released under the terms of the GNU General Public License version 2.
Flashrom is a “normal” user space application, but it requires superuser privileges.
Some hardened kernels (which deny access to physical memory) do not support flashrom, but
most distributions out there work fine.
Of course, the usual requirements for BIOS updates apply here as well. You should have a
stable power supply. Switching the machine off during flashing will make your machine
unbootable. Since flashrom treats BIOS files as opaque blobs, you usually do not get any
of the failover/dual BIOS features advertised on some boards.
Backup the current BIOS image into a file:
$ flashrom -r backup.bin
For other usage instructions, please refer to the flashrom home page or the man page.
In case something goes wrong, do NOT reboot, but join #coreboot @freenode and tell the
flashrom developers about it. As long as the machine is still running, there is a good
chance that everything can be fixed.
I’m an new Packager in OpenSUSE BuildService, and i like this work. But if i would like to package for Factory, RPMLINT gives me any Errors or warnings. But these things to fix, are very difficult. Our Wiki Side for RPMLINT doesn’t contain many Error or Warningcodes.
But yesterday i’ve found an Side, with other Errorcodes from RPMLINT. Today i imported these Codes to our Wikiside http://en.opensuse.org/Packaging/RpmLint. I think it is not possible to list all codes on the Side. But i wish, that the side includes more Codes in the future.
No i would like to make an Call for contribution. If every Packager insert the codes, that he knows, we have an good library soon.
And on this Moment i would like to make an request about helping- Thank you all for the hard Work.
Hello Folks,
today i haved an idea. If we Bloggers on lizard post an Article, and you like it, then make an vote in the head of the Article (vote with stars).
This had two effects:
1.) The Author see, that the Readers like his post.
2.) The Author can see, what are interesting for the readers. Than he can write articles, what you are interesting for.
Happy votig 🙂
Hello Folks,
in the last week i’ve build my repository (home:saigkill) for 11,1. This are the Packages:
– BOINC 6.4.5
– Mount Manager 0.2.5
– libatlas 3 – 3.8.1
– libnecpp0-1.2.6
– libqt4-4.4.3
– necpp 1.2.6
– Lynis 1.2.1
– necpp 1.2.6
– python-iCalendar 1.2
– qantenna 0.2.1
– kde4-skrooge 0.1.0 (i586 only)
Have a lot of fun 🙂
Unfortunaltely no Flashplayer for x86_64 exists. So far. Now the Adobe Labs released the libflashplayer for x86_64. It is very easy to run it on openSUSE.
First of all, you must download it. Go to http://labs.adobe.com/downloads/flashplayer10.html.
Then go to the bottom of the page, and klick on “Download 64-Bit Plugin for Linux”. Now you will see an Dialogbox. At this place you can download the tar.gz File to an Place, you wish.
After them, you go to your shell, and go into the Directory, that you have specified in the Dialogbox. Now you type: “tar xvfz libflashplayer-{insert your Version].tar.gz”. After unpacking you will see an file called “libflashplayer.so”.
Now you have two alternatives:
1.) If you are the only one on your Computer, you can move the file to: ~/.mozilla/plugins.
2.) If you have more Persons at the computer, you move the file to: /usr/lib64/mozilla/plugins/
After an Restart from Firefox you can use this new plugin.
From the Developers Side the Plugin is in unstable Status. But it works for me very fine. If you would like, try it out. …