May 2009 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] kernel patch..
by Hans Witvliet 08 May '09

08 May '09

Hi all, Just got hold of some gadgets (usb-thermometers) that internally use an usb-tty-converter. Luckily recent kernels detect the device (CH431-chip) and a ttyUSB0 device is created automagically. However, the device-driver seems to be in-complete, one can not set speed or the modem-signals. In order to use the device, there is an kernel-patch. But if a grep the kernel-code for 11.1 and apply the patch, wouldn't that mean that i have to do that every time when SuSE releases their own new kernelpatches??? The guy who wrote the patch wrote me yesterday that it _might_ be included in 2.6.29. Suggestions? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] kernel patch..
by Hans Witvliet 08 May '09

08 May '09

Hi all, Just got hold of some gadgets (usb-thermometers) that internally use an usb-tty-converter. Luckily recent kernels detect the device (CH431-chip) and a ttyUSB0 device is created automagically. However, the device-driver seems to be in-complete, one can not set speed or the modem-signals. In order to use the device, there is an kernel-patch. But if a grep the kernel-code for 11.1 and apply the patch, wouldn't that mean that i have to do that every time when SuSE releases their own new kernelpatches??? The guy who wrote the patch wrote me yesterday that it _might_ be included in 2.6.29. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] System Security Services Daemon (SSSD), extending PAM and NSS
by Ralf Haferkamp 07 May '09

07 May '09

I'd like to discuss a project that the Fedora people are currently working on. It's called System Security Services Daemon (SSSD, https://fedorahosted.org/sssd/) and tries to address some problems that exist with NSS and PAM today (mostly when using LDAP or other network based account database sources). Here's a list of problems they're trying to solve: - offline/cached authentication and name service e.g. for Laptop Users - Each application opens separate connections to the remote datastore (e.g. LDAP Server), by that way a single machine might open several dozens of network connections taking up too much resources from the server - NSS/PAM modules that can make use of authenticated connections to their backend DB need to provide the authentication token (username/password, Clientcert+Key, kerberos keytab) for that authentication be available in a world-readable place on the filesystem Most of the above problem can be solved by splitting the nss-Module into a client/server architecture (e.g. like it is done with samba-winbind). Having a small nss-Module talking through a unix domain socket to the daemon that's doing the real request against the remote database source. The problem is that you end up with a different daemon for every NSS module that you want to use. The SSSD project now tries to implement a somewhat similar but more generic approach, it provides have a daemon (sssd), NSS (nss_sss) and a PAM (pam_sss) Moduleas well. The difference now is, that this daemon doesn't talk to the remote datasource directly but acts mostly like a caching proxy i.e. it hands over incoming NSS or PAM requests to other NSS/PAM module (e.g. by calling directly into nss_ldap or nss_winbind) and caches the results for later reuse, e.g. when the machine is disconnected from the network. SSSD is also used to introduce a multi domain concept for PAM. E.g. usernames can have the from of user@DOMAINNAME and sssd allows to configure a specific PAM stack for every different domain. That should create less complex PAM configuration files. Additionally to the PAM and NSS service the daemon will provide a DBUS interface that can be used to get addtionaly user information for the underlying databases which one currently can't get through NSS. E.g. user photos for Display Managers, preferred language settings and stuff like that. I think the project took a pretty intersting approach to solve some of the issues with how NSS and PAM integrate to remote account sources. It of cause has some downsides (yet another level of indirection, another system daemon that needs to run on the machine), but as SSSD is purely optional we could live with that I guess. Does somebody alread have experiences with SSSD? What do you thing about the project? Is anybody interested in creating a Fate-Request or packages in the buildservice for testing purpose/integration into Factory? I'd also like to mention exist some alternative approaches that aim to solve the above listed problem especially for the nss_ldap/pam_ldap case: - nss-ldapd (http://ch.tudelft.nl/~arthur/nss-ldapd/) a reimplementation of nss_ldap and pam_ldap (PAM support is still in development) in a client server model. They currently don't do any caching/offline support (Packages for 11.1 and Factory are available in the buildservice) - nssov: A plugin (overlay) for the OpenLDAP server that the NSS and PAM modules from nss-ldapd can directly talk to. That means instead of running nss-ldapd on the client machine you setup a special OpenLDAP server configuration. It can e.g. just act as a (caching) proxy to the real backend server, or can be a (partial) replica. - use the original nss_ldap/pam_ldap modules talking via ldapi (LDAP over Unix Domain Socket) to a locally configured OpenLDAP proxy/replica. (BTW, running an LDAP Server on the client sounds scarier that it is, you can create pretty lightweight OpenLDAP setups ;) ) -- regards, Ralf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] Removed programs
by Donn Washburn 07 May '09

07 May '09

What the heck in SuSE keep removing programs I have installed that SuSE doesn't even offer. A good example and current one is fgfs or Flight Gear. It was working just fine in /usr/bin/fgfs. I tried it this evening and the mouse pointer just bounces. So ok, what else is not working - I went into a konsole and typed fgfs and got the following error. /usr/bin/fgfs: No such file or directory. I suspect this was caused by a update from SuSE Good news is that I made a checkinstall rpm and it is around. Which fails because SuSE Update removed OSG also. Why? -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)windstream.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] Configuration files merge
by Michal Hrusecky 07 May '09

07 May '09

Hi, If we want to make our distribution friendly even to advanced users, I think that we shouldn't touch users configuration files. Luckily this isn't problem as in spec file Ican state that this file is configuration and I don't want to replace it if user did some manual changes. Or I can say that I want to replace it and keep backup of original one. But what I'm missing is some tool to easily merge these files. In Gentoo there is etc-update [1] or dispatch-conf [2]. I'll describe more precisely what feature I'm missing and why I think it's needed. Let's say that I've got some package and there was quite big change in package default configuration file which will affect most of the users. On the other hand users can have pretty complicated constructions in their configuration files and if they did something like that, it's quite possible that they don't need to update their configuration file. So it is needed to tell users that if they are experiencing problems it is most likely because they touched default configuration. I can take care of it manually, mention it in various README and such, but more easier way would be following. User installs some packages. At the end of zypper or yast installation there will be warning "You've got 42 configuration files to merge, please run etc-update/dispatch-conf/whatever". Then user will run some easy interactive tool which will state which configuration files can use some manual merging, it will allow user to see difference between them and let him choose which one he wants or let him merge them manually somehow. Same warning about unmerged configuration files should appear each time user installs something, no matter if this installation didn't add any conflict, until all conflicts are fixed. User will be warned about possible problems, hacker can play with it and keep his changes against distribution defaults and ordinary user will just click on "use distribution default for all" if he ever encounter such a problem (shouldn't happen as ordinary user wouldn't touch configuration files). I explained basic expected work flow, so now what I think should be supported: * detect configuration files, their conflicts and allow their merge - this shouldn't be a big problem as rpm already stores conflicting files as .rpmnew/.rpmold * we probably want to keep even old versions to support three way merge to achieve even better results * if we are already storing these configuration files, maybe we should let users to backup their own changes as well, add support for versioning these configuration files * warn user that he has conflicts in configuration files - will require a little bit yast/zypper integration * merging tool should support both console and graphical interface (maybe use yast as possible frontend) * support for various formats (expandable by plugins) - ordinary diff may not be the best tool for merging XML files or ini files * ordinary user who don't change anything shouldn't need to know about this tool I already filled feature request [3] - FATE#306411 . But I'm interested in opinion of the others. What do you think about this feature? Any feature that it should have and it isn't in fate yet? [1] http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=3&chap=4#doc_… [2] http://en.gentoo-wiki.com/wiki/Dispatch-conf [3] https://features.opensuse.org/306411 -- Michal Hrusecky Package Maintainer SUSE LINUX, s.r.o e-mail: mhrusecky(a)suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] firefox 3.5b4 problems with proxy redirections
by Dominique Leuenberger 06 May '09

06 May '09

Hi everybody (and Wolfgang :) ) Since recently, Factory was blessed with Firefox 3.5b4 packages. So far it looks fine, except that I started to have one tiny (big) issue: In our corporate environment we're using a proxy. All the settings are given out with a .pac file (Proxy Autoconfiguration). FF reads the file, tries to connect to the proxy (so far so good). The proxy then sends a redirect request to a login page (border manager.. and unfortunately client trust, the single sing on solution for it, does not work without NCL. and even then, only on 32bit.. wrghl). But then, FF never reaches the login page (I get the message that the proxy refused the connection). If I then go manually to the login page (server:444/[...]) and log in, everything works fine from then on... so it's purely the redirect that does no longer work. The only thing changed in the chain was FF from 3.0.x to 3.5. This used to work fine before. Anybody with the same? Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] yauap engine
by Donn Washburn 06 May '09

06 May '09

Hey Group; Why is that SuSE insists on using "yauap" engine to run Amarok? It is defective on KDE3 and KDE4 when bring up Amarok. At that time the volume is just short of full blast. This happens anytime even when Amarok was closed down at 1/4 volume. Amarok-xine did not have this problem and worked correctly. Can someone explain why xine has become something SuSE dislikes. Also does anyone know where to get a version of amarok-xine that works with 11.2 -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)windstream.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] Czech Packagers Team Meeting minutes 2009-04-28
by Vladimir Nadvornik 04 May '09

04 May '09

Czech Packagers Team meeting 2009-04-28 ======================================= Present: anicka, mhrusecky, mseben, mvyskocil, nadvornik, pgajdos, prusnak, puzel, sbrabec Minutes: anicka Topics: (1) Community week (1) Community week Community week (11th - 17th May) is nearing, we should prepare a programme for a packaging day. We are not sure how exactly the step by step packaging session should be done. (Should everyone work on his own package and ask when not sure how to continue? Would it not be better to let everyone work on the same package and show step by step how to do it?) We are also not sure how not to spoil the first packaging experience by the necessity of learning long arcane osc commands. Anyway, everyone is expected to take a part and help with answering the questions. Status reports: mvyskocil: ========== [GREEN] - updated ant to 1.7.1 - updated gnu-jaf to 1.1.1 - new packages (build dependencies of junit4 and ant) imported to Factory: * jzlib * jsch * jakarta-commons-net * jarjar * cglib-nohook * byaccj [OUTLOOK] - add the rest packages needs for build of junit4 to Factory (jflex and java- cup, qdox, hamcrest) - work on bnc#499332: Java plugin backwards text in Firefox puzel: ====== [GREEN] - work on mcrypt and libmcrypt bugs - made some progress, but it will need more work - package gengetopt to Contrib pgajdos: ======== [GREEN] * working on build of packages for gcc44 (LabPlot, hdf5) prusnak: ======== [GREEN] - working on Packaging Guidelines - clanlib: updated to 2.0.1 mhrusecky: ========== [GREEN] - fixed some upgrade bugs in MySQL (bnc#496196 and others) - working on bnc#494061 sbrabec: ======== [GREEN] OBS multimedia:libs: Fixing backporting problems of packages. perl-Finance-Quote: Update, dependencies fix (bnc#496738). pidgin: Research on potential security crash (bnc#406416). libmodplug, xmms-plugins: Security fix (bnc#496541, bnc#498828). mseben: ======= [green] virtualbox-ose : updated to 2.2.2 virtualbox-ose : working on bnc#476050 openmotif : fixed build issues in factory doxygen : updated to 1.5.9 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] rfc/rfd: opensuse reloaded - updated interim versions of current opensuse releases - please more of this and endorsement
by cagsm 04 May '09

04 May '09

hi there, just came across <http://news.opensuse.org/2009/05/01/opensuse-111-kde4-reloaded-includes-kde…> which is basically a nice thing to get, similar to the debian Rx re-releases of their current main releases. is there any place to discuss these efforts of re-releasing or re-building current opensuse versions to include less-faulty packages? do we have a separate mailinglist, forum or anything? i would like to ask for more of these re-releases or how-to, documentation and the like on how to re-create installation cd and dvd media with the most current packages? the main problem for me is that i cannot use the most current version of the opensuse distribution obviously because of stability and bug reasons, but when re-installing or creating another system with the last stable version (current-1) then i am basically facing the same problems but on the older version as all the bug-fixes and patches that got released ever since are not included in the install media of that older build. basic idea is that the older version (current-1) is being worked on (patches/bug-fixes) for a longer time-frame than then current one so a re-build of the current-1 would likely to result in a better behaving system, both, better than the original current-1 (oldstable), and most likely also better (unknown bugs, new bugs yet to be discovered) than the stable (current) version. the main problem with releases for me is the installation time-frame when migration from even older to newer releases takes place, when systems need to get booted via the install media, need to check and recognize hardware, partitions and disks especially (raid setup and all that fancy stuff, but even standard things go awry and haywire all the time. once a system is up and running (booting and network accessible) i can most of the times make things work either from remote (ssh) or direct access. but the install and upgrade time-frame is most crucial to me. so i really do like this idea of getting newly built iso images to install from especially when they truly incorporate (didnt try this 11.1 reloaded yet) all those yast2, satsolver, kernel and related updates and patches. can we get more of this please, or some automated versions from the obs, or officially supported and acknowledged re-releases from the opensuse team? thanks for any comments. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] kde3 and kde4
by Donn Washburn 01 May '09

01 May '09

Hey Group; I would like to try KDE4 on a SuSE 11.2 system. I did find that SuSE has 4.# aliased to 3.5. And $windowmanager is not not set. So, how would I get KDE4 to come up with startx. -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)windstream.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1