May 2007 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] openSUSE10.3alpha4 installation on power through netboot
by Mohammed Omar 23 May '07

23 May '07

Hi all, I tried to install openSUSE10.3alpha4 on power machine through netboot method. I configured boot server and NFS server in RHEL machine , I installed and configured DHCP: TFTP: followed this link :: http://www-128.ibm.com/developerworks/eserver/library/es-linux-pservers/ind… When i booted the power machine and selected boot via network thru SMS menu.... I got the following error.... BOOTP R=1 BOOTP S=2 FILE: inst64 BOOTP:TFTP transfer failed, re-trying transfer BOOTP ERROR: TFTP of rest of blocks failed, giving up !BA010005 Regards:: -Mohammed Omar ------------------------------------------------------------------------------- IBM Linux Technology Center MD2-GB-184, Manyata Embassy Outer Ring road, Nagawara Bangalore- 560045, India Phone: +91-80-402-55027 Fax: +91-80-25436902 ------------------------------------------------------------------------------- --------------------------------------------------------------------- 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] kernel update brake the boot
by jdd 23 May '07

23 May '07

You are probably already informed :-), but the last 10.2 kernel update brake the computer boot... the menu.lst of grub is badly rewriten and the previous kernel and initrd are deleted this may be related to a special config.. I have on my drive * hda1 swap * hda2 10.2 * hda3 SLES boot menu was (from memory, it's no more here) floppy 10.2 * (default) SLES new compiled kernel The new grub menu.lst is below (because not anybody needs to read it). It default to floppy boot!!! the sles boots, hopefully! but not the others. vmlinuz and initrd (in /boot) are linked to the compiled kernel 0.3 (not by me!!) so the fix wads simple: shorten the entries of openSUSE 10.2 (/dev/hdc2) but it's a chance the new kernel works (it only allows more usb debugging) jdd (must leav now, will fill a bug later if necessary) default menu.lst # Modified by YaST2. Last modification on Tue May 22 13:38:25 CEST 2007 default 0 timeout 8 gfxmenu (hd0,1)/boot/message ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: floppy### title Disquette rootnoverify (hd0,0) chainloader (fd0)+1 ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE Linux Enterprise Server 10 root (hd0,2) kernel /boot/vmlinuz root=/dev/hdc3 vga=0x317 resume=/dev/hdc1 splash=silent showopts initrd /boot/initrd ###Don't change this comment - YaST2 identifier: Original name: openSUSE 10.2 (/dev/hdc2)### title openSUSE 10.2 (/dev/hdc2) kernel (hd0,1)/boot/vmlinuz-2.6.18.2-34-default root=/dev/hdc2 vga=0x317 resume=/dev/hdc1 splash=silent showopts initrd (hd0,1)/boot/initrd-2.6.18.2-34-default title 2.6.18.8-0.3-default kernel (hd0,1)/boot/vmlinuz-2.6.18.8-0.3-default root=/dev/hdc3 vga=0x317 resume=/dev/hdc1 splash=silent showopts -- http://www.dodin.net http://gourmandises.orangeblog.fr/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 6

[opensuse-factory] What did you guys do to /etc/fstab?
by M9. 23 May '07

23 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 fstab looks realy horrible! All unnessesary info makes it difficult to see what is what.. (of course i know what is what, but it looks like...terrible..) for ntfs-3g, i had to go to 10.2 repo... Amarok works without libxine1, (which is not to find), thnx!!! (new signature shows Alpha4 btw.) - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.21-8-default x86_64 Huidige gebruiker: monkey9@tribal-sfn2 Systeem: openSUSE 10.3 (X86-64) Alpha4 KDE: 3.5.6 "release 42" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGU47DX5/X5X6LpDgRAh1GAJ9l/j9jeApNaf1wT3ucgEzmwCoOPACdGWsp Ui07t00YI4w8BxadkPsO7uE= =fAht -----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 1

[opensuse-factory] Rootmodus not possible from configpanel, in A4.
by M9. 23 May '07

23 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It is not possible to get in the root modus to change samba settings, or log-in without password, is this known, or should i file a bug? - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.21-8-default x86_64 Huidige gebruiker: monkey9@tribal-sfn2 Systeem: openSUSE 10.3 (X86-64) Alpha4 KDE: 3.5.6 "release 42" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGU4xnX5/X5X6LpDgRAmcHAJ0c6L59xw5vVY9WO2+aXfzit79v5QCeJBpJ r26THEm3oaTLCi1fSNLKVUM= =lgln -----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] Installing on SATA HDD with SATA DVD-Burner
by Keith Goggin 22 May '07

22 May '07

Hi list, I have installed openSUSE 10.3 alpha 4 on a SATA2 HDD using a SATA2 DVD-Burner. So far so good. However the mobo has Radeon Xpress 1250 integrated graphics which only runs in framebuffer mode on alpha 4. I would like to exercise the graphics chip in 3D mode but so far there are no opensource drivers for the X1250 and the ATI Proprietary Linux x86_64 Display Driver 8.36.5 does not yet support X-Org 7.2 found in alpha 4. Now openSUSE 10.2 GM is pre X-Org 7.2 so the Proprietary Driver would probably work there but sadly 10.2 does not support SATA HDDs and SATA Burners :-( Can anyone tell me how to install 10.2 GM with the necessary SATA support? Hardware: ASUS M2A-VM mobo (AMD690G chipset) Athlon 64 X2 4800+ CPU Kingston KVR667D2N5K2/2G (2GB DDR2/667 RAM) 320GB Seagate Barracuda Sata2 HDD Pioneer DVR-212 Sata2 DVD Burner --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

Re: [opensuse-factory] Meeting Minutes Dist Meeting 2007-05-10
by Stanislav Brabec 22 May '07

22 May '07

Richard Guenther wrote: > On Tue, 22 May 2007, Andreas Jaeger wrote: > > > Stanislav Brabec <sbrabec(a)suse.cz> writes: > > > > > Andreas Jaeger wrote: > > > > > >> * Shared library policy > > >> see: http://en.opensuse.org/Shared_Library_Packaging_Policy > > > 0) Static only packages > > > 1) Packages with some devel files in the main package. > > > > > > If package is static only or package provides devel files (e. g. .pc > > > file) without splitting -devel package, it must provide -devel package, > > > either as a virtual symbol or as a package (by skipping of file list of > > > the main package). > > > > > > Packages linking against the library or referring devel files from the > > > package (e. g. .pc files), must refer to foo-devel, not foo. > > > > > > It allows painless move to shared library and painless splitting in > > > future. > > > > > > Example: > > > package foo with static-only stuff: > > > Provides: %{name}-devel = %{version}-%{release} > > > > > > Real life example: > > > Package check moved from static to shared library after 10.2. > > > Several other packages were splitted. > > > Both raised need to adopt many other packages. > > > > So, what is your objection here? > > I don't get this either. Note the shared libaray naming and packaging > policy is about shared libraries, not static ones or naming a -devel > (or not -devel) package. Yes, but it's related. If package changes from static to shared library and the static package was referenced as libfoo, you are in problem: All BuildRequires are now broken. The second mentioned thing can be re-formulated as a missing item in the policy: Is it allowed to package shared library altogether with development files (.a, .pc, .so, .h)? Is it allowed to package development files to package, which does not have -devel in its name? I think that it should not be permitted, even if it causes bigger number of packages. Otherwise it introduces missing devel dependencies (see below). > Shared libraries may reside in /lib{,64} or /usr/lib{,64} only if > there are development files packages separately in a -devel package to > link against those libraries. See (1) on how to handle different > cases. This looks too strict. There are many packages, which create shared library for more binaries inside one package. What is the benefit to link say metacity binaries with /usr/lib/metacity/libmetacity-private.so.0 instead of /usr/lib/libmetacity-private.so.0? This rule will need additional wirk to change many packages and additional work even to check that all packages conform to this rule. > > > 2) Naming of devel package. > > > So my proposal: > > > > > > Shared library package should be named libgsf1_114, but devel package > > > should be named libgsf1. > > This is exactly what the policy suggests. Where do you read otherwise? > Maybe the wording can be improved. No, it suggests libgsf1_114-devel: If more than one version of a -devel package can be installed at the same time ... the -devel packages should be suffixed with the same number as the shared library package. Proposed change: If more than one version of a -devel package can be installed at the same time ... the -devel packages should be suffixed with the same number as the shared library package. If package provides a pkg-config file or another development configuration script or shared library uses epoch number, the -devel packages should be suffixed with the number of it. > > > If more than one version of a -devel package can be installed at the > > > same time (for example because includes are packaged in a versioned > > > directory and shared libraries have a versioned name like libgtk1.so.1) > > > the -devel packages should be suffixed with the same number as the > > > shared library package, lib$NAME$NUM-devel. > > I see this is a quote from the policy. The wording needs to improve here > as $NUM does not suggest a suffix different from $SONAME is allowed. But it's already part of the policy, last article "Package Naming". Andreas Jaeger wrote: > There is not yet any tool for automatic collecting of devel > > dependencies, but I am thinking about a tool collecting packages > > from .pc files and #include. > > > > Preferred way to do it: > > Requires: %{name} = %{version} > > And how can we get rid of these later again? We currently have a lot of > packages with too many dependencies ;-( We need an automatic tool for it. Missing devel dependencies introduces additional BuildRequires in other packages which are even worse to get rid. It is definitely not complicated for .pc files, but more complicated for .la files and .h files. -- 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 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

2 2

[opensuse-factory] Meeting Minutes Dist Meeting 2007-05-10
by Andreas Jaeger 22 May '07

22 May '07

Here're the minutes from the last meeting, Andreas * dbus restart Restarting of d-bus needs special handling in every package, otherwise they might crash. Upstream d-bus maintainer currently say that d-bus should not get restarted. The long-term goal is that all applications and services should handle d-bus restarts gracefully. For the short term, we will advice the user to reboot the system and not automatically restart d-bus during package updates. * Moving d-bus to / This is need for some potential changes in hal. Since we did not have enough details, we decided to stay for now with the default and rediscuss when needed. * Shared library policy see: http://en.opensuse.org/Shared_Library_Packaging_Policy If nobody raises objections, we'll move forward with it and add it to the packagers manual. Note: This is not enforced for existing packages. It should be done for major updates and must be done for new package submissions. AI: everybody to read and comment on opensuse-packaging mailing list. * Improve debuginfo packages To get a complete stack trace, we need several debuginfo packages. The simple idea would be to copy dependencies from the main package to the debuginfo package. But this would give too many dependencies since it would lead to include always the gcc-debuginfo package (currently 300 MB). Another idea is to reduce the size of debuginfo packages and mark them only for backtrace - with removing the source code. We run out of time and will discuss this further next time. Andreas -- Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 4

[opensuse-factory] Topics dist meeting 2007-05-10
by Andreas Jaeger 22 May '07

22 May '07

We'd like to discuss the following topics tomorrow. Please send your comments and suggestions as usual so that I can represent them. thanks, Andrea * Smaller systems - what can be done? Goal: A system with 128 MB of space. Challenges are especially: * Languages and localization * documentation - > some packages have documentation split up already * theming -> some packages will be split up so that only one theme is in a package. For languages we discussed previously already the following and will implement this now: The idea is to add to spec file of packages a new rpm macro so that subpackages are created and then related subpackages are repacked for each language in our build system. This way we would get e.g. basesystem-$lang and gnome-$lang packages and those can then be installed. * Shared library policy (posted some time ago on opensuse-packaging, is now in the wiki) * dbus restart Making dbus a special reboot case like the kernel when updating (like other distros - dbus is really not supposed to be restarted). -- Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

9 11

Re: [opensuse-factory] Re: Using Instlux: issues setting up SUSE from Windows
by Lars Rupp 22 May '07

22 May '07

BTW: http://build.opensuse.org/project/show?project=CrossToolchain%3Amingw speziell: cross-mingw-gcc "GCC cross-compiler for Windows targets This is the standard GCC, modified for use in cross-development. The GNU compiler collection only supports cross-compilation in C and C++, so those are the only two languages prepared. It is intended for people who want to develop for a Windows target from your desktop computer." => /opt/cross/bin/i386-mingw32msvc-gcc -o foobar.exe foobar.c --------------------------------------------------------------------- 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] VJ decompression error
by Juan Erbes 22 May '07

22 May '07

After a problems with my ISP (Timofonica), I must to go back to my old 56k sporster Robotics and my older ISP (in the absense of adsl), but I has frequently disconnections problems with it. The dmesg result is: SFW2-INext-DROP-DEFLT-INV IN=modem0 OUT= MAC= SRC=62.189.244.228 DST=200.45.208.50 LEN=457 TOS=0x00 PREC=0x00 TTL=52 ID=13266 DF PROTO=TCP SPT=80 DPT=27556 WINDOW=65535 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A6A887173000C7C18) PPP: VJ decompression error PPP: VJ decompression error SFW2-INext-DROP-DEFLT IN=modem0 OUT= MAC= SRC=221.208.208.86 DST=200.45.208.50 LEN=486 TOS=0x00 PREC=0x00 TTL=49 ID=0 DF PROTO=UDP SPT=55888 DPT=1026 LEN=466 PPP: VJ decompression error PPP: VJ decompression error PPP: VJ decompression error PPP: VJ decompression error PPP: VJ decompression error PPP: VJ decompression error PPP: VJ decompression error PPP: VJ decompression error PPP: VJ decompression error SFW2-INext-DROP-DEFLT-INV IN=modem0 OUT= MAC= SRC=62.189.244.228 DST=200.45.208.50 LEN=457 TOS=0x00 PREC=0x00 TTL=52 ID=13931 DF PROTO=TCP SPT=80 DPT=27556 WINDOW=65535 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A6A888A73000C7C18) SFW2-INext-DROP-DEFLT IN=modem0 OUT= MAC= SRC=221.208.208.96 DST=200.45.208.50 LEN=486 TOS=0x00 PREC=0x00 TTL=49 ID=0 DF PROTO=UDP SPT=47166 DPT=1026 LEN=466 PPP: VJ decompression error PPP: VJ decompression error PPP: VJ decompression error Regards --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1