August 2012 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] OS 12.1 i586 TW - kernel 3.5 - s2ram does not work
by Vladimir Malast 11 Aug '12

11 Aug '12

Opensuse 12.1 Tumbleweed - after upgrade kernel from 3.4 to 3.5 command s2ram does not not work. It looks that there is a problem with the graphic driver - the card is GeForce 8600 GT, driver nouveau Gallium (7.11). The computer goes to sleep, but after wake-up it is frozen after while or after next command s2ram restarts. Downgrade to 3.1 or 3.4 solved the problem. Thanks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

Re: Fwd: [opensuse-factory] Re: Secure Boot for openSUSE - a proposal
by Vojtech Pavlik 10 Aug '12

10 Aug '12

On Fri, 10 Aug 2012 08:01:44 -0500, Malcolm Lewis wrote: > Sounds all good to me :) > > My only queries are; > > 1. Will alternative bootloaders eg gummiboot be implemented? > 2. Will efi booting be added to the Live CD's? These are both good goals. But I'd like to get the whole thing working first, with a more limited feature set. So not in the first iteration, later, of course. And anyone will be able to contribute to the development. > 3. Can we use openSUSE for the boot/efi/efi instead of SuSE (for a > multibooter like me with SLE and openSUSE) I don't see a reason why not. -- Vojtech Pavlik Director SuSE Labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] Secure Boot for openSUSE - a proposal
by Greg Freemyer 10 Aug '12

10 Aug '12

plain text this time On Fri, Aug 10, 2012 at 9:08 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: > On Fri, Aug 10, 2012 at 6:40 AM, Andreas Jaeger <aj(a)suse.com> wrote: >> >> As a followup to discussions on opensuse-project and here on >> opensuse-factory about secure boot, here's a proposal: >> >> Vojtech Pavlik and Olaf Kirch have written three blog posts explaing >> SUSE's approach to secure boot: >> >> http://www.suse.com/blogs/uefi-secure-boot-overview/ >> http://www.suse.com/blogs/uefi-secure-boot-plan/ >> http://www.suse.com/blogs/uefi-secure-boot-details/ >> >> They basically propose to enhance Fedora's solution with a way >> that Matthew Garrett - the Red Hat developer working on this - summarized >> at http://mjg59.dreamwidth.org/15818.html with >> >> "There's a post here describing SUSE's approach to implementing Secure >> Boot support. In summary, it's pretty similar to the approach we're >> taking in Fedora - a first stage shim loader is signed with a key in >> db, it loads a second stage bootloader (grub 2) that's signed with a >> key that's in shim, the second stage bootloader loads a signed >> kernel. The main difference between the approaches is the use of a >> separate key database in shim, whereas we are currently planning on >> using a built-in key and the contents of the firmware key database. >> ... >> "It's a wonderfully elegant solution. We've been planning on supporting >> user keys by trusting the contents of db, and the Windows 8 requirements >> specify that it must be possible for a physically present user to add keys >> to it. The problem there has been that different vendors offer different UI >> for this, in some cases even requiring that the keys be in different >> formats. Using an entirely separate database and offering support for >> enrolment in the early boot phase means that the UI and formats can be kept >> consistent, which makes it much easier for users to manage their own keys. >> >> I suspect that we'll adopt this approach in Fedora as well - it >> doesn't allow anything that our solution wouldn't have, but it does >> make some of them easier. Full marks to SUSE on this." >> >> >> What shall we do for openSUSE? Vojtech and Olaf make the proposal to >> use the proposed SUSE solution for openSUSE as well. >> >> Do you see any problems or enhancements for the proposal? >> >> I would love to tell them the openSUSE community looks forward to the >> SUSE implementation for the next release (12.3). May I? >> >> Andreas >> -- >> Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi >> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >> GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) >> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 >> -- >> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org >> To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org >> I think there are 2 questions. 1) Is the SUSE approach with a standalone database of MOKs necessary for openSUSE. I argue it is. 2) Is the functionality defined for using that database of MOKs sufficient for openSUSE needs. I argue it is not. The prime examples relate to OBS and SuseStudio. If each of those is provisioned with a unique MOK key and the validation key is made well known, then the SUSE approach will I'm sure include a relatively simple way for a user to install the validation key into the MOK database. But what if OBS and/or SuseStudio is used to create a kernel that gets designated as malware. I would like to see the openSUSE solution provide a way to black ball that kernel. === Thus I think openSUSE should use the SUSE UEFI approach as a foundation, but should add a black ball mechanism to it somehow. I admit that I don't have a methodology in mind to accomplish that. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] nouveau, plymouth and grub2?
by Alin M Elena 08 Aug '12

08 Aug '12

2 1

[opensuse-factory] new package - ssdeep
by Greg Freemyer 07 Aug '12

07 Aug '12

All, I have just submitted ssdeep to factory. It has a sub-package of libfuzzy. http://ssdeep.sourceforge.net/ It is a tool for doing piecewise hash generation. It can be used for malware and (I believe) spam detection and is another digital forensic tool in my ongoing (slow) effort to push digital forensic tools into factory. For a overview of forensic tools in openSUSE see: http://en.opensuse.org/Portal:Digital_forensics_and_incident_response Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Secret key for Secure Boot with Windows 8 and 12.2
by Roman Bysh 07 Aug '12

07 Aug '12

Hello all, I've been reading that Ubuntu is providing a secret key for the "Secure Boot" so that Ubuntu may be installed alongside Windows 8. Since 12.2 is coming out in September and Windows 8 is being released in October. What are the plans? Cheers! Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] RFC: apache2 upcoming changes
by Cristian Rodríguez 07 Aug '12

07 Aug '12

Hi: This week, I have been working giving apache2 packages some love, in particular upgrading to version 2.4. The upgrade part is done but I am now working on implementing major changes in the way it is distributed and packaged. If there are no objections it will go as follow. 1. Support for Building apache in: * Non SUSE Distros * Versions older than SLE 11 SP2 Will go away. 2, Subpackages : apache2-prefork apache2-itk apache2-worker Will go away. 2.4 supports providing MPMs as DSOs, so you can switching between prefork/itk/worker just by using a2enmod a2insmod etc.. just if they were a regular apache module. MPMs do not use more than 40k disk space, it is complete non-sense to keep the complexity of maintaining pre/post/setup scripts of subpackages around. Care has/will been taking in preserving package-side upgrade paths but trouble may arise, if so, please fill bug reports and assign them to me. Cheers! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

[opensuse-factory] PackageKit blocking Yast
by Thomas Taylor 07 Aug '12

07 Aug '12

In OS 12.2-RC2 (build 0091-DVD) in 'Yast > Software Management > Search', PackageKit is blocking the repositories from loading. I've worked around this by killing the PackageKit process, then the repos load properly. Has anyone else seen this happen? Is it a bug or expected behavior? Tom -- “What we do for ourselves dies with us. What we do for others and the world remains and is immortal.” Albert Pine -- Tom Taylor - retired penguin AMD Phenom II x4 955 -- 4GB RAM -- 2x1.5TB sata2 openSUSE 12.1x86_64 openSUSE 12.2x86_64 KDE 4.7.2, FF 7.0 KDE 4.8.4, FF 13.0 claws-mail 3.8.0 registered linux user 263467 linxt-At-comcast-DoT-net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 10

[opensuse-factory] Very slow response in kshisen
by Thomas Taylor 07 Aug '12

07 Aug '12

On OS 12.2-RC2 (build0091) x86-64, the game kshisen (shisen-sho) takes a long time responding to mouse clicks. This has only occurred with the RC2 version. The first click on a tile may or may not be indicated (color change) immediately. The second click (on matching tile) seems to think about things for 5-10 seconds. I tried running it as root with nice of -19 but that didn't change the behavior. /var/log/messages doesn't show me anything obvious (still learning about what to look for). Incidental: had to do "export $(dbus-launch)" to make kshisen run as root. I put the konsole messages and message log on pastebin as "kshisen-slowness" When I looked at the running processes, nothing was over 2% for cpu and 3% for memory (ps -ux). The only programs running were Krusader, Firefox, and Claws-Mail. Would anyone please offer suggestions of what/where to look for a remedy? Thanks, Tom -- “What we do for ourselves dies with us. What we do for others and the world remains and is immortal.” Albert Pine -- Tom Taylor - retired penguin AMD Phenom II x4 955 -- 4GB RAM -- 2x1.5TB sata2 openSUSE 12.1x86_64 openSUSE 12.2x86_64 KDE 4.7.2, FF 7.0 KDE 4.8.4, FF 13.0 claws-mail 3.8.0 registered linux user 263467 linxt-At-comcast-DoT-net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] 12.2 RC2 btrfs subvolumes
by Erwin Van de Velde 06 Aug '12

06 Aug '12

Dear all, I tried installing OpenSUSE 12.2 RC2, and all goes well, but I have a remark: Would it not be better to have a separate subvolume for /home if you do not choose a /home separate partition? Zypper + snapper can revert an update, but I do not think it is good to revert both the user documents and the system files in such a case. Also, if it is a separate subvolume, it is perhaps possible to remove the system subvolumes instead of reformatting the entire filesystem and letting the user files in place. "Why not create a separate partition if you want this?" I hear you ask. I only have a 160GB SSD disk in my laptop and since the snapper snapshots will take more place, I would need to make my root partition bigger., but I do not like shrinking my home partition. Furthermore, since you cannot estimate the filesystem usage perfectly, you always loose space and perhaps this can be a way to avoid such waste. Best regards, Erwin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0