openSUSE Factory August 2010

factory@lists.opensuse.org

83 participants
41 discussions

[opensuse-factory] Restructuring /usr/bin, etc. [WAS: sles? ]
by Greg Freemyer 10 Aug '10

10 Aug '10

On Fri, Aug 6, 2010 at 10:00 AM, Kay Sievers <kay.sievers(a)suse.de> wrote: > On Fri, 2010-08-06 at 15:27 +0200, Guido Berhoerster wrote: >> * Kay Sievers <kay.sievers(a)suse.de> [2010-08-06 13:36]: >> > On Fri, 2010-08-06 at 09:42 +0200, Stefan Seyfried wrote: >> > > On Fri, 06 Aug 2010 03:03:22 +0200 >> > > Kay Sievers <kay.sievers(a)suse.de> wrote: >> > > >> > > > I think that /usr on nfs, or even on a different disk should just get a >> > > > reality check, and be finally dropped. >> > > >> > > Having /usr, /var, /opt and /tmp on different partitions / disks is >> > > basically a standard setup for lots of real-world corporate installations. >> > > >> > > The people who break such standard setups (or even think about breaking >> > > them) all the time should just get a reality check... >> > >> > /usr not on the rootfs is broken since ages for anything that isn't a >> > simple server. It does not make any sense to do that, and that's why >> > nobody really cares. >> > >> > Many things plugging into udev/hotplug break if /usr is not available at >> > early boot. I stopped asking people to fix such things. >> >> Unfortunately an all too common attitude in Linuxland. Anyway, >> can we then just be honest and officially abandon the now >> arbitrary /bin /sbin -- /usr/bin /usr/sbin separation by moving >> stuff and symlinking /bin and /sbin to /usr? >> It's nothing uncommon, Solaris/OpenSolaris, HP-UX, and AIX for >> example all don't have a separate /bin any more. It would >> certainly ease the pain with linking libraries which are in /usr. > > Anything like this sounds good to me. It's just a pretty useless > exercise with this artificial split. I would understand to have 'the > desktop' split out into /usr, but everything else is just crazy. An it > seems entirely random what we do here today. The 'maybe needed at boot' > thing just does not mean anything today. > > The real fix is a properly working read-only /, for people who use /usr > on a separate filesystem, anyway. > > Kay I'm not clear what exactly is being proposed, but any significant shuffling of /usr/bin, /usr/sbin, /usr/lib will potentially impact a lot of existing installs. I have machines (low-end servers) I setup 7 or 8 years ago and have simply been upgrading over the years. One I just checked has a 2GB / (root) and a 5 GB /usr. Neither have enough freespace to absorb the other, so I'd likely have to re-install the OS from scratch on those. (I know, 7 years later, it's about time anyway.) Regardless, I'm not saying my setup of a few machines is enough to drive the future, but I do think it begs the question as to how common setups like mine are. Is there a way to know? Does smolt collect that sort of info? Can smolt be extended to collect it. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

9 14

[opensuse-factory] wireless - iwlagn Microcode SW error
by Juergen Orschiedt 09 Aug '10

09 Aug '10

I repeatedly see "Microcode SW error detected. Restarting" in /var/log/messages when I connect to a 802.11n network. As side effect, connection speed drops to 1MBit/sec. Problem doesn't show up when connecting against 802.11ab. Hardware is Latitude E6500 with 2.6.34-9-desktop x86_64 kernel. Jun 10 08:13:40 .. iwlagn 0000:0c:00.0: Microcode SW error detected. Restarting 0x2000000. Jun 10 09:17:50 .. iwlagn 0000:0c:00.0: Microcode SW error detected. Restarting 0x82000000. Jun 10 09:17:50 .. iwlagn 0000:0c:00.0: Microcode SW error detected. Restarting 0x82000000. Jun 10 09:23:53 .. iwlagn 0000:0c:00.0: Microcode SW error detected. Restarting 0x2000000. cheers, Jürgen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

Moving /bin, /sbin, and /lib to /usr (was Re: [opensuse-factory]) sles?
by Guido Berhoerster 09 Aug '10

09 Aug '10

* Kay Sievers <kay.sievers(a)suse.de> [2010-08-06 16:00]: > On Fri, 2010-08-06 at 15:27 +0200, Guido Berhoerster wrote: > > * Kay Sievers <kay.sievers(a)suse.de> [2010-08-06 13:36]: > > > On Fri, 2010-08-06 at 09:42 +0200, Stefan Seyfried wrote: > > > > On Fri, 06 Aug 2010 03:03:22 +0200 > > > > Kay Sievers <kay.sievers(a)suse.de> wrote: > > > > > > > > > I think that /usr on nfs, or even on a different disk should just get a > > > > > reality check, and be finally dropped. > > > > > > > > Having /usr, /var, /opt and /tmp on different partitions / disks is > > > > basically a standard setup for lots of real-world corporate installations. > > > > > > > > The people who break such standard setups (or even think about breaking > > > > them) all the time should just get a reality check... > > > > > > /usr not on the rootfs is broken since ages for anything that isn't a > > > simple server. It does not make any sense to do that, and that's why > > > nobody really cares. > > > > > > Many things plugging into udev/hotplug break if /usr is not available at > > > early boot. I stopped asking people to fix such things. > > > > Unfortunately an all too common attitude in Linuxland. Anyway, > > can we then just be honest and officially abandon the now > > arbitrary /bin /sbin -- /usr/bin /usr/sbin separation by moving > > stuff and symlinking /bin and /sbin to /usr? > > It's nothing uncommon, Solaris/OpenSolaris, HP-UX, and AIX for > > example all don't have a separate /bin any more. It would > > certainly ease the pain with linking libraries which are in /usr. > > Anything like this sounds good to me. It's just a pretty useless > exercise with this artificial split. I would understand to have 'the > desktop' split out into /usr, but everything else is just crazy. An it That was sort of the case when X apps were still installed into /usr/{X11R6,X11,openwin} and SuSE's bad habit to install distributed packages under /opt, but those times are gone for better or worse. > seems entirely random what we do here today. The 'maybe needed at boot' > thing just does not mean anything today. Well how do we get this going, should I open a ticket on openfate to discuss this further and see if there's any objections? It shouldn't be too much work, most of the stuff is from Base:System packages. The symlinks should guarantee backwards compatibility, anything I'm missing here? > The real fix is a properly working read-only /, for people who use /usr > on a separate filesystem, anyway. Does it require anything else beside having /var and /tmp on separate partitions? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 19

[opensuse-factory] few tips for crash catching, work with core files, debuginfo installation
by Stanislav Brabec 09 Aug '10

09 Aug '10

Well, some applications in 11.3 accidentally crash. But most of them does not want to crash in a moment I am debugging them in the gdb, I searched in the documentation and found a simple solution. Collect cores: 1. Set SOFTCORELIMIT in /etc/sysconfig/ulimit to "unlimited" or do this just now by: ulimit -c unlimited 2. mkdir /cores ; chmod +t /cores ; chmod og+rw /cores 3. Add a line to /etc/sysctl.conf: kernel.core_pattern = /cores/%e-%t-%u.core or do this just now by: echo "/cores/%e-%t-%u.core" >/proc/sys/kernel/core_pattern Core files will be stacked to /cores and ordered by application name and time and will never overwrite. You can easily find a most crashing application there. Install debuginfo: gdb often complains on missing debuginfo packages. You can easily install all of them by copy and paste it to the console input of following command: eval zypper install $(sed -n 's/Try: zypper install//p') Well, you can do the same using the gdb log file and then reading it: eval zypper install $(sed -n 's/Try: zypper install//p' <gdb.log) And in gdb use: Nebo v gdb set logging file gdb.log set logging file on set pagination off attach {pid of application I want to debug} detach attach {pid of another application I want to debug} Well, and if you have a core file, do the final well known: bt or thread apply all bt Notes: Don't forget to check the backtrace in Bugzilla and submit unique crashes. If it is an accidental crash, it makes sense to submit the backtrace to the upstream Bugzilla, if the crash makes a big problem to use particular application or if you suspect that it is openSUSE specific, submit it to the Novell Bugzilla as well. Well, if the core comes from npviewer, feel free to run: rm /cores/npviewer* It does not make sense to report them anywhere. All these crashes I have seen were triggered by Adobe Flash or Adobe Reader and I have no chance to fix them. Wanted: An easy manual how to be always ready for kernel crash dumps. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 1

[opensuse-factory] sles?
by Peter Czanik 09 Aug '10

09 Aug '10

Hello, Syslog-ng 3.1.2 was released yesterday, so I started to prepare a version update, as it will make almost all patches redundant. I did a bco, updated syslog-ng, checked in, and found, that it compiles fine on all openSUSE versions, but fails to compile on SLES 11 SP1. Actually, it compiles, but the checks fail, for details check https://build.opensuse.org/package/live_build_log?arch=i586&package=syslog-… Two questions: 1.) does it need to be able to build sles11 packages, or it is not a requirement to be able to sr it to factory? 2.) could anyone with access to SLES 11 SP1 check, why this happens? Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

14 25

[opensuse-factory] Too much Gnome for KDE
by Felix Miata 08 Aug '10

08 Aug '10

Why does gnome-control-center, needed only because certain apps are built only using gtk but never to be used here except outside of Gnome, dep to nautilus, metacity & nautilus-tracker, even with zypper's -d option? Why do I need ~17 gnome packages just to run Epiphany? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

7 7

[opensuse-factory] xml file for the current state - internationalisation
by jdd 08 Aug '10

08 Aug '10

Hello, I'm working on the way to internationalize the live cds. I noticed that is one select a language at install time, YaST is pre-setup to update all the distro with the given langage. May be simply pre-configured for fr, de, en, es. However this pre-configuration include some things like openoffice, etc... I could,in YaST, untick the not desired packages and install only the wnted ones (so I could, starting with 2.7Go get 2.9 Go with fr installed, when installing all I have 3.4GO. However, when I export the xml file, from YaST, I get all the packages originally selected, not my own selection. So is it possible to have the xml file corresponding with the running distro, not the "project" -:)? of course, I could modify directly the xml file, but I will lose the dependecy check thanks jdd -- http://www.dodin.net http://pizzanetti.fr -- 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] [notice] Moving default cursor theme out of desktop-data-openSUSE
by Vincent Untz 07 Aug '10

07 Aug '10

Hi, I'm going to fix https://bugzilla.novell.com/show_bug.cgi?id=589293 in Factory. The reason for this is that there's no reason to bundle the cursor theme in this big package, especially since it's a different source. If you have a package that somehow is affected or is configuring the default X cursor theme, you might need to change a few things: + there is no theme called "default" anymore. I don't know why we had a symlink like this, but it's a bit confusing (especially since theme selection dialogs showed the same theme twice because of this) + the default theme is called "DMZ" + you should depend on dmz-icon-theme-cursors instead of desktop-data-openSUSE to make sure this theme gets installed. Note that I'll make desktop-data-openSUSE require dmz-icon-theme-cursors because it uses it (see /etc/sysconfig/windowmanager) Note that right now, dmz-icon-theme-cursors is not in Factory (it's called icon-theme-dmz-cursors there -- I'm fixing it too). I don't expect this to affect many packages, but it might be a bit unclear which ones get affected. If you have any question about this, just ping me. Vincent -- Les gens heureux ne sont pas pressés. -- 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] Konsole colors & font not menu adjustable
by Felix Miata 07 Aug '10

07 Aug '10

I find no way in Konsole menus to escape from white on black to customary black on white or select font to be used. Where/why are these hidden in 4.4.93's menus? How can these be reached without a right click? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 10

[opensuse-factory] legacy nvidia cards and the 11.3 nvidia repo
by Greg Freemyer 07 Aug '10

07 Aug '10

Stephen (or other nvidia legacy expert), I've got an old nvidia TNT card I was having an issue with so I thought I'd try the old legacy nvidia driver with it. But the oldest nvidia driver is not in the repo. ie. x11-video-nvidiaG02 and x11-video-nvidiaG01 are both there for 11.3, but x11-video-nvidia is not. I assume that's intentional and that the older legacy driver is no longer compatible with a recent kernel? fyi: I tried to download the source and compile it. That worked, but when I tried startx, I got an error dlopen: /usr/lib/xorg/modules/drivers/nvidia_drv.so: undefined symbol: AllocateScreenPrivateIndex I found numerous references to that on the web, but no obvious solutions. Thanks Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory August 2010