May 2007 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] no second root console anymore ?
by Günther J. Niederwimmer 06 May '07

06 May '07

Hello, is this a known restriction with the new Kernel (OS-10.2)? I can't login in a second root console, the message are, May 6 08:15:01 techz /usr/sbin/cron[26308]: pam_loginuid(crond:session): set_loginuid failed opening loginuid May 6 08:15:01 techz /usr/sbin/cron[26308]: pam_loginuid(crond:session): set_loginuid failed May 6 08:15:01 techz /usr/sbin/cron[26308]: Cannot make/remove an entry for the specified session May 6 08:19:05 techz smartd[3991]: Device: /dev/sdb, SMART Usage Attribute: 194 Temperature_Celsius changed from 187 to 193 May 6 08:30:01 techz /usr/sbin/cron[26345]: pam_loginuid(crond:session): set_loginuid failed opening loginuid May 6 08:30:01 techz /usr/sbin/cron[26345]: pam_loginuid(crond:session): set_loginuid failed May 6 08:30:01 techz /usr/sbin/cron[26345]: Cannot make/remove an entry for the specified session May 6 08:35:27 techz login[25432]: pam_loginuid(login:session): set_loginuid failed opening loginuid May 6 08:35:27 techz login[25432]: pam_loginuid(login:session): set_loginuid failed May 6 08:35:27 techz login[25432]: Erstellen/Entfernen eines Eintrags für die angegebene Sitzung nicht möglich -- mit freundlichen Grüssen / best Regards Günther J. Niederwimmer --------------------------------------------------------------------- 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] Linux audio foks
by Donn Washburn 05 May '07

05 May '07

Hey Group; I have the record player > phono In > line out going to the sound card Line In. Hopefully the impedance is good enough and the level is OK. It plays out of the speakers and sounds OK also. Now for the question ? I would like to save the music as a mp3, ogg or whatever. Kmix spots it as a Line Input. What is needed to capture it and put it in a file. Say like a mixer record output -- 73 de Donn Washburn 307 Savoy Street Email: " n5xwb(a)hal-pc.org " 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 Did you know? The transistor was invented by three white men. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

[opensuse-factory] ntfs-3g.
by M9. 04 May '07

04 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, http://www.ntfs-3g.org/index.html Is this also something for 10.3? - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.18.8-01-default x86_64 Huidige gebruiker: monkey9@tribal-sfn2 Systeem: openSUSE 10.2 (X86-64) KDE: 3.5.5 "release 45.4" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGOloOX5/X5X6LpDgRAgzwAJ4hmhYjOVAdWvOEug0+GAtpadBr+wCfU/wb zjDXO6V4fOji0YnBsqtIVA0= =Xj70 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 8

[opensuse-factory] Touchware-drivers under GPL.
by M9. 03 May '07

03 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Letter, as sent to 3M. > Good Day, > > The way your driver is maintained, it can not be inserted into the > openSUSE kernel. > >> The source RPM contains no sources - it contains lots of binary stuff: >> >> tar tvzf TWDrvSources.tgz >> drwxr-xr-x root/root 0 2006-04-11 21:47:06 bin/ >> -rwxr-xr-x root/root 12166 2006-04-11 21:48:39 bin/MultiMonitorTool >> -rwxr-xr-x root/root 35075 2006-04-11 21:48:40 bin/TwCalib >> drwxr-xr-x root/root 0 2006-04-11 21:48:39 common/ >> -rw-r--r-- root/root 7677 2006-04-11 21:48:39 common/tw_ioctl.h >> -rw-r--r-- root/root 1497 2006-04-11 21:48:39 common/TWEvents.h >> drwxr-xr-x root/root 0 2006-04-11 21:47:06 controlXInput/ >> -rw-r--r-- root/root 6439 2006-04-11 21:45:12 controlXInput/controlXInput.c >> -rw-r--r-- root/root 344 2006-04-11 21:45:12 controlXInput/makefile >> drwxr-xr-x root/root 0 2006-04-11 21:47:04 daemon/ >> -rwxr-xr-x root/root 19587 2006-04-11 21:48:39 daemon/TWDrvStartup >> -rwxr-xr-x root/root 554 2006-04-11 21:48:37 install >> drwxr-xr-x root/root 0 2006-04-11 21:47:06 lib/ >> -rwxr-xr-x root/root 14131 2006-04-11 21:48:39 lib/libMultiMonitor.so >> -rwxr-xr-x root/root 40709 2006-04-11 21:48:40 lib/libTwCaliblib.so >> -rwxr-xr-x root/root 461488 2006-04-11 21:48:40 lib/libTwGraphics.so >> -rw-r--r-- root/root 5887 2006-04-11 21:48:39 License.txt >> drwxr-xr-x root/root 0 2006-04-11 21:47:06 mmtool/ >> -rw-r--r-- root/root 838 2006-04-11 21:48:39 mmtool/Makefile >> -rw-r--r-- root/root 1725 2006-04-11 21:48:39 mmtool/TwMMTool.h >> -rw-r--r-- root/root 414 2006-04-11 21:48:39 mmtool/Tool.cpp >> -rw-r--r-- root/root 11376 2006-04-11 21:48:39 Readme.txt >> drwxr-xr-x root/root 0 2006-04-11 21:47:06 TWCalib/ >> -rw-r--r-- root/root 926 2006-04-11 21:48:40 TWCalib/Makefile >> -rw-r--r-- root/root 1700 2006-04-11 21:48:40 TWCalib/TwCalib.h >> -rw-r--r-- root/root 391 2006-04-11 21:48:40 TWCalib/Calib.cpp >> drwxr-xr-x root/root 0 2006-04-11 21:48:39 TwDrvKit/ >> -rw-r--r-- root/root 16894 2006-04-11 21:48:39 TwDrvKit/common.o.save >> -rw-r--r-- root/root 48754 2006-04-11 21:48:39 TwDrvKit/TWDriver.c >> -rw-r--r-- root/root 8663 2006-04-11 21:48:39 TwDrvKit/TWDriver.h >> -rw-r--r-- root/root 736 2006-04-11 21:48:39 TwDrvKit/Makefile24 >> -rw-r--r-- root/root 916 2006-04-11 21:48:39 TwDrvKit/Makefile26 >> -rw-r--r-- root/root 1031 2006-04-11 21:48:39 TwDrvKit/makefile >> -rwxr-xr-x root/root 1993 2006-04-11 21:48:37 TWDrvStartup >> -rwxr-xr-x root/root 5882 2006-04-11 21:48:37 TWXinputInstall.perl >> drwxr-xr-x root/root 0 2006-04-11 21:48:21 Xfree4.0.3/ >> -rw-r--r-- root/root 10158 2006-04-11 21:47:57 Xfree4.0.3/TWXinput_drv.o >> >> The kernel parts are: >> -rw-r--r-- root/root 16894 2006-04-11 21:48:39 TwDrvKit/common.o.save >> -rw-r--r-- root/root 48754 2006-04-11 21:48:39 TwDrvKit/TWDriver.c >> -rw-r--r-- root/root 8663 2006-04-11 21:48:39 TwDrvKit/TWDriver.h >> >> So, there's a common.o binary file. We will never add such a driver to >> our kernel. >> >> It even does have: >> #ifdef MODULE_LICENSE >> MODULE_LICENSE("Proprietary"); >> #endif >> >> So, this is not GPL compatible. >> >> Sorry, no way, 3M is not providing a real source RPM for their kernel >> driver, > > > What should 3M do, to provide a 'real' GPL compatible driver? > >> Complete source code - including sources for common.o - and everything >> licensed under the GPL. And then they should get it into the official >> Linux kernel instead of maintaining there drop in driver. > > > > > Greetings, Rob Verberne. > > > 30-04-07 20:22, us-ts-techsupport(a)mmm.com , jgmciver(a)mmm.com writes: > > > Good Afternoon: > > We do not have a binary touch driver for Suse 10.2 or 10.3, however we > do offer a source and binary kit that can be used to install the driver. > Since Linux has a vast numbers of versions available, 3M Touch Systems > provides the source and object kit to allow users to build our package > for many versions of Linux . However, with every different version of > Linux, it is possible to encountert a situation where the kernel module > will not build or will not load on a target system. When this occurs > the customer is responsible for finding the issues that prevent the > driver from building as we do not have the resources to investigate and > troubleshoot the many variations of Linux and kernels. > > You can download the source and binary kit from our webpage > www.3m.com/touch. Click on the Touch Drivers link and then click on > Linux Touchware Drivers. The source and object kit can be downloaded > from this page. > > Thank you, Technical Support > 3M Touch Systems, Methuen > 978-659-9200 - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.18.8-01-default x86_64 Huidige gebruiker: monkey9@tribal-sfn2 Systeem: openSUSE 10.2 (X86-64) KDE: 3.5.5 "release 45.4" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGOd4BX5/X5X6LpDgRApL+AJ99m+W6Dw4RSm5s+kdDTjt3thsB8wCggnw7 5xi5I9Oin3pOWeTko6yA8WE= =j6kr -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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] Answer 3M about touchscreendrivers...(touchware)
by M9. 03 May '07

03 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Good Afternoon: > > We do not have a binary touch driver for Suse 10.2 or 10.3, however we do offer a source and binary kit that can be used to install the driver. Since Linux has a vast numbers of versions available, 3M Touch Systems provides the source and object kit to allow users to build our package for many versions of Linux . However, with every different version of Linux, it is possible to encountert a situation where the kernel module will not build or will not load on a target system. When this occurs the customer is responsible for finding the issues that prevent the driver from building as we do not have the resources to investigate and troubleshoot the many variations of Linux and kernels. > > You can download the source and binary kit from our webpage www.3m.com/touch. Click on the Touch Drivers link and then click on Linux Touchware Drivers. The source and object kit can be downloaded from this page. > > Thank you, Technical Support > 3M Touch Systems, Methuen > 978-659-9200 - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.18.8-01-default x86_64 Huidige gebruiker: monkey9@tribal-sfn2 Systeem: openSUSE 10.2 (X86-64) KDE: 3.5.5 "release 45.4" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGOLojX5/X5X6LpDgRAuU0AJ42SEIcOkai9z/ytDMGxYV6A78EpwCgoN2s 1uW9nTUIci5+oOv95D8PfLE= =sNS8 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 6

[opensuse-factory] /etc/init.d/boot.crypto , LUKS extension, unattached devices
by Jochen Hayek 03 May '07

03 May '07

May I suggest a change to /etc/init.d/boot.crypto ? First the "real life context": I prepare my /etc/crypttab and my /etc/fstab for quite a few different external encrypted disks. And I don't attach them all at the same time, esp. not at boot time. /etc/init.d/boot.crypto shouldn't bother attempting to mount disks, that are not currently attached. Now for internals of the script: The test "cryptsetup isLuks ..." should be preceded by a test on the existence of the "device", i.e. the symlink in /dev/disk/by-id/ . So far, if "cryptsetup isLuks ..." returns false, "this is used for things like swap or other temp mappings", as the comment in the "else" branch says. So because that's used already for something meaningful, there should just be another test beforehand. And this is my suggested code: if ! test -L "$device"; then echo -e "device {$device} does not exist currently.\n" ret=1 continue elif cryptsetup isLuks "$device" &> /dev/null; then ---------- Actually there is also something else, I would like to suggest. I really prefer names like "scsi-SATA_FUJITSU_MHT2080_NN5AT43149CP-part4" over names like "sdb4" in /etc/fstab and also in /etc/crypttab . You guess why, don't you? We don't know in advance, in which order we attach / detach / re-attach ... external disks during the weeks and months. And "sdb4" assumes (somehow), that the disk is the 2nd SCSI disk. But maybe "today" we only attach it as the 3rd. And for the same reason names like "sdb4" should also not be used to create names in /dev/mapper/ . The entries with names like "sdb4" in /etc/fstab and in /etc/crypttab get created by yast's "System / Partitioner". It's not really a major effort for me, renaming "sdb4" to something more flexible, everytime we attach yet another external encrypted disk, but I guess I am not the only one doing so. So a few others around this globe might enjoy such an improvement, too. ---------- I would really enjoy seeing the suggested changes in 10.4 or so ... :-) Kind regards, J. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 5

[opensuse-factory] cryptsetup, some old, big and fat disks with encryption=twofish256, ...
by Jochen Hayek 03 May '07

03 May '07

I have a few disks with fstab entries like this one: noauto,nocheck,acl,user_xattr,loop=/dev/loop0,encryption=twofish256,phash=sha512,itercountk=100 I would like to mount them under 10.3Alpha3 resp. SUSE Factory. cryptsetup's manual page says COMPATABILITY WITH OLD SUSE TWOFISH PARTITIONS To read images created with SuSE Linux 9.2's loop_fish2 use --cipher twofish-cbc-null -s 256 -h sha512, for images created with even older SuSE Linux use --cipher twofish-cbc-null -s 192 -h ripemd160:20 but if twofish-cbc-null is not listed in /proc/crypto , there is no way getting this working, right? And even after $ modprobe loop_fish2 Something like this didn't work any more $ losetup -e twofish256 -H sha512 -C 100 /dev/loop1 /dev/sdb1 but it does on 10.1 . Shall I just forget twofish256 and migrate all my encrypted disks? Cheers, Jochen P.S. Actually I really like the LUKS extensions to cryptsetup. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 3

[opensuse-factory] Permissions and security levels
by Volker Kuhlmann 03 May '07

03 May '07

SuSEconfig supports 3 different security levels for file permissions - easy, secure, paranoid. Default is easy. Is this still appropriate? The higher the security level, the more things stop working. I have considered "secure" a good choice for many years, and haven't seen any loss of functionality personally. However, suseupdater fails at "secure", displaying a yellow triangle with a bubble help of subprogram failed and mentioning suid. Is this advanced voodoo for experienced Susers only, does this want some adjustment, or a better explanation for less experienced users? Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 4

[opensuse-factory] Java packages changes for 10.3
by Daniel Bornkessel 03 May '07

03 May '07

Hi. In 10.3, regarding Java, we want to do the following changes: - tomcat5 will be replaced by tomcat55 - we have jboss and geronimo already ... our jonas package is outdated anyways ... thus, dropping: jonas jonas-client jonas-docs jonas-examples - the avalon framework does not exist anymore ... dropping: avalon-framework avalon-framework-javadoc avalon-framework-manual In order to clean openSUSE from non-oss packages, we want to do the following changes: - jai has strict licensing ... if there are no strong objections we would like to drop this package. - java-1.4.2-sun will be dropped, versions 1.5.0, 1.6.0 (DLJ licensed) and gcj-compat 1.4.2 will be included. The DLJ-license is a special lincense that was introduced by Sun in 2006 for re-distributors of Sun Java (see http://download.java.net/dlj/DLJ-FAQ.html). It's less strict and more precise on what is allowed and what is not regarding the re-distribution. Apart from that, nothing visible will change for the users -- Sun Java will still be in the openSUSE non-oss section. - the following packages will be replaced by gnu-javamail which has an open source license: javamail javamail-demo javamail-javadoc javamail-manual javamail-monolithic - the following packages will be replaced by gnu-jaf which has an open source license:: jaf jaf-demo jaf-javadoc jaf-manual - the following packages will be replaced by classpath-jta which has an open source license: jta jta-javadoc - the following packages will be replaced by mx4j which has an open source license: jmx jmx-javadoc The packages that get dropped due to their licenses are usually licensed with the Sun Binary license which is not really the type of license we want to include in openSUSE if free oss counterparts are available. Any thoughts and comments on this are very welcome :) Regards, Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

7 11

[opensuse-factory] More bugs?
by Volker Kuhlmann 02 May '07

02 May '07

Finally managed to install 10.3a3. 1) System failed to boot. The problem of using /dev/sdxxx instead of hdX in /boot/grub/menu.lst I believe is already fixed for a4. 2) A /etc/grub.conf of setup --stage2=/boot/grub/stage2 (hd0,6) (hd0,6) isn't going to work as it doesn't install an MBR loader, so it's always a boot failure. What's needed is setup --stage2=/boot/grub/stage2 (hd0) (hd0,6) At least the latter line makes is boot, the former hangs after "booting from local disk". Raid1 (/dev/mdX) for rootfs. Or is this a result of a failure caused by 1)? 3) The "list of installed drivers" (printer pppd files) is built after the printer can be configured during installation in the hardware config step. Does this constellation make sense? 4) During installation, I changed some monitor values (number of pixels, screen diagonal, Vrefresh) and tested afterwards. Worked fine. When the system goes to runlevel 5 after installation, the xorg.conf is way off the monitor and obviously running with who knows what. The configuring during installation was obviously pointless. Has someone seen this too? 5) Module ata_piix isn't good. It takes a huge amount of time during boot, showing timeouts and lowering DMA/PIO with each step. Not really useful. Setting that module as broken in the rescue system causes piix to be loaded instead; but then no /dev/sda* are created so it's useless. Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 5