Home Home > Uncategorized
Sign up | Login

Archive for the ‘Uncategorized’ Category

How to filter a certain class of hardware in dhcpd.conf

March 19th, 2014 by

To prepare the end of the XP world

Atfer 8th April 2014, Windows XP system will be Like children in the lions’ den, if connected to internet

In a network around, all the still running XP are all vmware virtual machine, and none of the end-users are the right to modify the settings of the virtual machine, nor has administrative right under XP

The idea is the simply to just suppress the gateway of the network.

Playing with dhcpd.conf

There’s lot of way to handle this classification, but I discover that you need to find the right syntax, and understand how the binary-to-ascii function of dhcpd work.

First binary-to-ascii remove any leading 0, then we will just readd them :-)

Extract of the dhcpd.conf

# binary-to-ascii remove leading 0 rebuild the complete MAC
set testmac = concat ( suffix (concat ("0", binary-to-ascii (16, 8, "", substring(hardware,1,1))),2), ":", suffix (concat ("0", binary-to-ascii (16, 8, "", substring(hardware,2,1))),2), ":", suffix (concat ("0", binary-to-ascii (16, 8, "", substring(hardware,3,1))),2), ":", suffix (concat ("0", binary-to-ascii (16, 8, "", substring(hardware,4,1))),2), ":",  suffix (concat ("0", binary-to-ascii (16, 8, "", substring(hardware,5,1))),2), ":", suffix (concat ("0", binary-to-ascii (16, 8, "", substring(hardware,6,1))),2) );

# Extract the only first 8 chars 
set testclass = substring(testmac, 0, 8);
# You will find a lot of this on internet but doesn't work
# set testmac = binary-to-ascii(16, 8, ":", substring(hardware, 1, 6));

# All our VMware VM use the same prefix
if ( testclass = "00:0c:29" ){
  # put dummy router
  option routers 127.0.0.1;
  # useful debug log
  log (info, "xp32 lease");
}else{
  # Default gateway for anyone else
  option routers 192.168.1.254;
  log (info, "standard lease");
}

That’s all for today

osc build with kvm on an encrypted volume group

March 15th, 2014 by

How-to build a initrd-virtio on a fully encrypted volume group

If like me you care about your data stored on your laptop, you certainly use a fully encrypted (excepted /boot) configuration based on lvm.

In my case I also like to create, build, fix packages locally with our tool osc. I’ve plenty of power, beefy ssd, so I dedicate a logical lvm for building cleanly package with qemu-kvm configuration, like obs does

Prepare the kvm building system

As root you create 2 lvm volume with lvcreate, one will be the build root, the other one will be the additional swap

In ~/.oscrc I enable the following parameters

build-type = kvm
build-device = /dev/mapper/vg0-lvobsbuild
build-swap = /dev/mapper/vg1-lvobsswap
build-memory = 4096
build-vmdisk-rootsize = 16000
build-vmdisk-swapsize = 4000
build-vmdisk-filesystem = ext4

You just have to adjust the Memory quantity and the device to what you create for your own environment.

(more…)

Trying to add some light

February 3rd, 2014 by

Lately there was some confusion regarding our communication. We, at the openSUSE Team@SUSE are deeply aware that our communication needs to be improved. So in the hope to make everything clear again, here is the summary to clear up what is really going on and what was not happening.

Long story short:

  • There WILL be openSUSE 13.2 in November 2014
  • 13.2 WILL have security and maintenance support provided by SUSE
  • We WILL have coolo as release manager for 13.2
  • SUSE is NOT decreasing manpower put into openSUSE
  • Everybody from the community is welcome and encouraged to be involved with, and if they want to, take over some parts of the release process and we will support you the best we can in doing that

Now for the long story.

Our team and only our team – openSUSE@SUSE – is going to work on improving ‘tooling’ side of the openSUSE project until August. These changes will benefit openSUSE by making it easier to produce better releases in the future.

Nothing changes for the rest of SUSE. SUSE is not abandoning openSUSE. The rest of SUSE will still do the same things they were doing until now and continue to keep openSUSE awesome. This includes Maintenance, Security, Infrastructure, and many other teams besides the openSUSE Team at SUSE who actively support the openSUSE project.

What is our plan?

Our plan is to make sure that future openSUSE releases are easier for everyone to produce. As we grow we could keep putting in more and more full-time release managers (if we find them somewhere), but this approach is probably unsustainable and, more importantly, goes against our desire to empower the community to do more as part of openSUSE.

Therefore, we decided to improve our tools to ensure that making a release is much more straightforward and reliable and we can reduce and distribute the workload needed for integration and release. To make this happen we need time and everyone from the team to work on adapting the tooling side. We also would welcome volunteers to help us with tools and with the following release(s).

With the release date now set in November (mirroring roadmap for 13.1), first milestone should be released in May. That is a perfect oportunity to go to openSUSE Conference in Croatia where we can meet up, gather volunteers to help and discuss how to work. Remember that openSUSE Travel Support is in place to sponsor everyone who needs financial help to get to the event.

Hopefully now we cleared things up a little and we are really sorry again for our poor communication – We’re going to work on it.

Your truely confused openSUSE Team

No forgotten patch to YaST anymore

January 17th, 2014 by

As I wrote in the last blog post, we try try to open YaST development as much as possible. When I thought what is the most annoying thing for me when contributing to an open source project, then it is when my contribution is ignored. So if I send a patch and do not get any response or I get response, but my patch is not merged without any reason, then I do not contribute again as I see it as a waste of time. To prevent such situation in YaST I’ve created an automatic reminder of pending pull requests for the YaST repos at GitHub.

How it is done? I want to have it transparent, reusable and automatic. The core component is a small ruby script I wrote to fetch pending requests for an organization on GitHub. It uses the GitHub API and tries to find any pull request without activity for three working days.

This script is handled by our public Jenkins server where it pulls the latest version of the script every working day and if there is any pending pull request it will send an email with its result to the YaST mailing list.

After a month of sending emails we have handled all longer running pull requests we have for YaST, so none of them have gone without activity longer than a month. I hope it encourages developers to create more pull requests as they will not be forgotten. We plan also to deploy such reminder for the libyui organization.

Waouh, Thank you, Merci, Danke, etc

December 16th, 2013 by

Thanks you!
I really & sincerely thank all of our members who not only took the risk of being recognized as active members, but also cast their vote to myself.

Thank you, Merci, Danke etc..

Thank you, Merci, Danke etc..

I’m deeply touched, now the time of let’s begin the fun has come.
Be assured to my strong commitment in our project and community.

See you on earth!

AMD flgrx status

November 12th, 2013 by

Just a quick note before openSUSE 13.1 hit the street.

Sebastian Siebert is trying to build and fix issues (essentially with 32bits) founded in the beta6 version of fglrx. Once that will be done, I should be able to deliver a new version of the fglrx drivers in the beta repository.

He also ask, like several of us AMD when they would like to release it: there’s no answer to that. So what does that mean.

The old 13.4 stable version from April, will NOT work with openSUSE 13.1. That’s why you will not find any driver in the stable repository.

For owners of old HD2xx-HD4xx, don’t dream, the legacy driver didn’t get update, so your choice is easy, use open source radeon driver.

I just hope I’m wrong in my feeling that we will have to wait until January, the launch of AMD new processor & apu.

Use the Scan to PC function on a Samsung Multifunction

October 1st, 2013 by

So I went out and bought myself a spanking new multifunction creature from Samsung called a CLX3305FN. Generally, this fits into the CLX3300 series, but it has LAN only – no wifi (that would be the CLX3305FW). One of the reasons I decided I wanted this was because of the advertised “Scan to PC” function. I figured it would be simple on Windows and that I’d be able to get it working on Linux through YaST or sane/scanimage etc – i.e. a PITA but it would work.

As it turned out, it didn’t work at all. The function is supposed to be for Windows only. However, the clever lads over at bchemnet.com reverse engineered the protocol that was used between the scanner and a windows PC and managed to hack a script together which runs as a server daemon. It just sits there twiddling its thumbs until a user presses the “Scan to PC” button on the printer/scanner. Then it kicks into action and uses sane to send scan commands to the scanner. The result of it is that the scan lands in $HOME/Scans/ – thus, the Scan To PC function is neatly implemented for Linux. There are, of course, rough edges (such as the scanner sending in RAW rather than JPEG) but nothing that couldn’t be fixed in a hackweek.

So where can you get it? The package is available at http://software.opensuse.org/package/python-samsungScannerServer – but you’ll need to install the Samsung Unified Driver for Linux first. I found it at http://www.samsung.com/us/support/owners/product/CLX-3305FN but apparently bchemnet.com has a repo for debian/ubuntu where you can download it too. Once you install that and my package, you’ll probably have to do a systemctl start samsungScannerServer (“probably” because I don’t really know how systemd worked and schustered together a .service file based on google search results).

Another nice hackweek project would be to use something like inotify to discover incoming scanned files, gpg to encrypt them and email them to the user (and then delete the unencrypted version). I also need to look into getting the unified samsung driver working on ARM so I can use my raspberry as a scan server which sends encrypted scans to my email address…

I will miss the 5th edition of openSUSE Conference

June 16th, 2013 by

no osc13 for me

I’m not going to osc13


Sunny sky, rainy heart today.

Two days ago, I took the decision to not assist the certainly most fabulous openSUSE Conference next July in Thessaloniki.


A conjunction of several factors lead to that decision.
First what I regret was the chosen date. Damn July is the only expensive period to travel to Thessaloniki. The plane ticket never drop below the 800€ (hey! for sure I want to have Françoise with me), especially with the late announce of precise days. May, June, September would have been so cheaper…
I can understand the choice main sponsor SUSE do, and their need to spread osc and SUSECON at a 6 month delay in the year’s schedule, but sadly does not work for me this year.

Thessaloniki port

Thessaloniki port


Secondly after February marketing hack-fest, I missed (I still don’t know how) the opportunity to get my travel reimbursed by the TSP and then loose half of the budget for osc. Before TSP get improved, and send a bounce email to ask you to send back your forms. So if you are sponsored for osc, fill and send back your expenses quickly after the event. Don’t believe you do it, check twice you really do it! Don’t suppose, be sure!

Another side, I already knew that a customer project will happen during that time-frame. As it concerns a lot of partner’s I’ve to take in account the availability of each of them. Unfortunately, after believing that it could be doable to free-up time for osc I decide to stop persecuting myself, and make a deal to live in peace and go ahead: no osc this year.

Maths have their say: statistically, more osc will be, more the chance to miss one will increase :-) ( I know still not a real excuses)

I would like to share my deep apologizes to the whole Greek Community in charge of OSC13. You all know, how I was and still am a big found of your commitment and really appreciate each of you.
I will all miss you!

I really hope osc13 will stay in history as one of the ever greatest conference organized.

Don’t worry Thessaloniki, I know how great the place is, kind the people are, etc..
I’ll be back soon!

Αχ Θεσσαλονικη – Αντωνης Βαρδης

openQA in openSUSE

June 6th, 2013 by

factory-testedToday, we’ve got for you an introduction of the teams’ work on openQA by Alberto Planas Domínguez.

The last 12.3 release was important for the openSUSE team for a number of reasons. One reason is that we wanted to integrate QA (Quality Assurance) into the release process in an early stage. You might remember that this release had UEFI and Secure Boot support coming and everybody had read the scary reports about badly broken machines that can only be fixed replacing the firmware. Obviously openSUSE can’t allow such things to happen to our user base, so we wanted to do more testing. (more…)

bareos an interesting replacement to bacula

June 2nd, 2013 by

Bareos logo
Dear community, I would like to present and get your feedback about a new project called bareos [1]

I discovered it 6 months ago, after starting to be more and more annoyed by the way the bacula’s community edition was driven and developed. Even if I was using it since version 1.32 … First of all, I wish to be clear and shout out my respect to all the work done by Kern on Bacula or any other contributor. We have a really nice working software. We even have a nice build packages for it on OBS.
But it’s stalled …

My personal frustration started with the creation of Bacula Enterprise, which has until now never (from what I’ve seen) reversed an Enterprise feature back to the community. Which in my sense would have been a clear statement & commitment from the Bacula Enterprise to the community.
A Free Software is free once it has been paid once. And more the time pass, more the community edition look like abandoned (windows client binary, bweb, …) Okay I can understand the enterprise’s edition arguments, the point is not there according to me.

So at the end of last year, I’ve started looking what else could replace Bacula for my own usage, and the small/medium customers I serve. Digging on github (my favorite source forge) I discovered bareos project. Basically Bareos is a fork of bacula community edition. With active contribution, and look like what I was looking for. Bareos is a compatible (at the time of writing) drop’in replacement which offers a bunch of nice feature I was waiting for. Especially high quality windows clients. The whole being cooked on a private obs instances, tested with jenkins, travis …

Okay I was disappointed about the fact it was a fork, but their website explains the why for those who wish to know.

I’ve then started to use it (easy to try with the number of supported platforms) and ready to use package. (Thanks to open build service [2]) Some installations were kept in a compatible way, other in native bareos way. The transition was really easy for anybody knowing how bacula works. After 3 months of production, including full restore, virtual machine backup, etc, I qualified it to be really production ready. Hey the base code and the way patches have been handled certainly explain those results. I also appreciate the effort to make bareos almost ready to use after installation. Trying to reduce the entry level ticket.

The remaining concerns I’ve found:
- The community behind will have to grow and success in a truly transparent way.
- Get new contributors (challenge is the same for bacula, but forking and propose request merge on github is really more cool than email patches)
- The full remake of the documentation (work in progress)
- Get a perfect web bconsole
My best hope:
- Make sustainable, the business plan associated with bareos.com and thus continue to produce quality community software

So did some of you already test it?
What’s your own feedback, your thoughts about it?

Regards.
[1] http://www.bareos.org
[2] http://openbuildservice.org