- openSUSE Factory

error: extra qualification... problems compiling differents programs with the new gcc 4.1
by Chema Ollés 20 Nov '05

20 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all: I try compiled mplayer (error on LiveMedia libs) and aMule and find the same type of error: extra qualification. I just see now that gcc 4.1 is EXPERIMENTAL: linux:/opt/aMule-Unicode/amule-cvs-20051120/src # gcc -v Using built-in specs. Target: i586-suse-linux Configured with: ../configure --enable-threads=posix --prefix=/usr - --with-local-prefix=/usr/local --infodir=/usr/share/info - --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib - --enable-languages=c,c++,objc,f95,java,ada --enable-checking - --with-gxx-include-dir=/usr/include/c++/4.1.0 --disable-libssp - --enable-java-awt=gtk --disable-libjava-multilib --with-slibdir=/lib - --with-system-zlib --enable-shared --enable-__cxa_atexit - --enable-libstdcxx-allocator=new --without-system-libunwind - --host=i586-suse-linux Thread model: posix gcc version 4.1.0 20051110 (experimental) (SUSE Linux) Oh my God!!! Any idea? cheers - -- Chema Ollés Usuario Linux: #198057 Linux 2.6.14-rc3-smp #7 SMP Thu Nov 17 01:00:40 CET 2005 i686 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDgM1v65SpD7GhbzoRAgwFAKCjAB5xqhNWIBezXfz6ZX+k1cn44QCfTjz/ Pl8FJbSSAoEG8Tmjr9pj+6Q= =Ox8y -----END PGP SIGNATURE-----

3 5

updating to alpha3
by Chema Ollés 20 Nov '05

20 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all: I just update from alpha2 to alpha3. I see a lot of errors on devices creation. I must create by hand devices for my mouse,sound and also,change permission for more of the normal devices like ptys,pcm,mixer.... :-( Is it a bug or I do something wrong? regards - -- Chema Ollés Usuario Linux: #198057 Linux 2.6.14-rc3-smp #7 SMP Thu Nov 17 01:00:40 CET 2005 i686 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDf7RD65SpD7GhbzoRAidJAJ9qRbI+w7yCt3hQsgCwFFYZvTwr8QCgjGk5 U5HHSLHNX8tzAkdbEgKY4u4= =KShS -----END PGP SIGNATURE-----

2 3

todays factory on PPC
by Peter Czanik 17 Nov '05

17 Nov '05

Hello, I wanted to install todays (Sunday) openSUSE factory on my PPC machine (a Pegasos2), but I ran into troubles with package selection. Rough translation from Hungarian on the YaST summary screen: "package selection trouble must be manually resolved". So I choose "packages" to solve the problem. Half of the world was waiting to be deselected, as there is a missing dependency: libGL.so.1 (or so, I rebooted to a working openSUSE 10.0 installation...) was missing. Bye, Peter

2 2

Problems after update alpha2 from apt servers
by jmolles＠vodafone.es 16 Nov '05

16 Nov '05

Hi all: I can't use thunderbird,openoffice,firefox and alsa doesn't works fine.I upgradealpha2 with smart. Anybody could explain me why this programs crash? for example: firefox -> /usr/bin/firefox: line 251: 27598 Violación de segmento $MOZ_PROGRAM $MOZ_LANG thunderbird -> ./run-mozilla.sh: line 131: 27655 Violación de segmento "$prog" ${1+"$@"} sorry for this mail,I write it with mail and there are many years ago I didn't use it... ;-) cheers -- Chema Ollés

1 0

Another stupid question, I suspect, how do I build packageinfo.xml.gz
by Ian S. Nelson 16 Nov '05

16 Nov '05

Is there a tool? I'm a Suse newbie still.. Converting from the Redhat empire. Ian

2 1

Is there a way to add installation sources to yast automatically?
by Ian S. Nelson 14 Nov '05

14 Nov '05

This might not be the right place to ask this but it there a programmatic way to add software installation sources? thanks, Ian -- *Ian S. Nelson PGP/GPG <http://www.gnupg.org/%28en%29/documentation/faqs.html#q1.1> email preferred. Public Key: 00D3D983 <http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x00D3D983> Fingerprint: 3EFD7B86B888D7E229B69E97576F1B9700D3D983 *

2 2

apt for 10.1?
by Chema Ollés 13 Nov '05

13 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all: I'm sorry but I can't find a right server to download last updates for openSuse 10.1 alpha2. I try with: ftp://mirrors.mathematik.uni-bielefeld.de/pub/linux/suse/apt/SuSE/10.1-i386 ftp://ftp.gwdg.de/pub/linux/suse/apt/SuSE/10.1-i386 ftp://ftp4.gwdg.de/pub/linux/suse/apt/SuSE/10.1-i386/ The same result-> The files I can see on -> http://linux01.gwdg.de/apt4rpm/freshrpms/suse101.html doesn't exist on that servers :-( cheers - -- Chema Ollés Usuario Linux: #198057 Linux 2.6.14-rc3-g82984114 #1 SMP Sat Oct 8 15:39:19 CEST 2005 i686 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDdi/C65SpD7GhbzoRAr54AJ9h07cdbugovz8v387xq75M1lkcjACePN7Y jFjpzTUPBwprXcwV0CEPQsI= =QOR/ -----END PGP SIGNATURE-----

1 1

Re: [opensuse-edge] Edge -> Factory
by James Ogley 11 Nov '05

11 Nov '05

> as written before we are in the need of relabeling Edge into something else. > We do rename it to Factory according to the discussion on this list. Yay! Glad to see my idea was thought worthy of this, I'm really honoured - thanks guys. Welcome to the new list :) -- James Ogley james(a)usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org

1 0

Suggestions for ext3 filesystem in the YAST2 installer
by jsiebert＠arcor.de 11 Nov '05

11 Nov '05

Hi there, i've been using ext3 as my favorite filesystem for all of my systems for some time now because of stability reasons (had some problems with xfs, reiserfs burns to many cpu cycles). Performance of ext3 in it's standard configuration on openSUSE/SUSE Linux 10 is not that good compared to reiserfs or xfs especially when it comes to write operations. So I've investigated the issue myself and found some things that could be improved in the future. 1. data=ordered vs. data=writeback on / filesystems. In ordered jounalling mode of ext3 data is always written to disk prior to the metadata (journal data). This ensures data consistency in most cases. However the performance of this option is not that well. In writeback journalling mode the metadata might get comitted to the journal before the data is actually written to the disk. This might lead to data corruption in some cases (e.g. power-off before the data could be written to disk but the journal data already has been commited). But on the other hand performance of this option is considerably better. The YAST2 installer allows to set the writeback journalling mode but not in the / filesystem. I one specifies the data=writeback option in /etc/fstab the / filesystem is mounted in ordered journalling mode although. To get around this one can use the tune2fs tools with the option '-o journal_data_writeback'. This sets the default mount option for the filesystem with which it gets mounted in writeback journalling mode. The same applies to the 'journal' journalling mode. So my first suggestion for the YAST2 installer is to call' tune2fs -o journal_data_writeback' for the respective device if a user selects the writeback journalling mode on ext3 for the / filesystem. I've tested this on three different machines without any problems. 2. Enable dir_index feature ext3 has a feature called 'dir_index' which enables faster lookups in large filesystems by using a technique called hashed b-trees. Currently a user which wants to use this feature has to manually convert the filesystem by using 'tune2fs -O dir_index <device>' and 'fsck.ext3 -fD <device>' which takes a long time to complete on large filesystems. This feature can also be enabled by using 'mkfs.ext3 -O dir_index <device>' at filesystem creation time. The YAST2 installer doesn't offer an option for this. So my second suggestion is to add an option to the YAST2 installer to enable the dir_index feature at filesystem creation time. I've also tested this option on three different system and noticed some speedups especially on slower systems (my notebook). That's all for today ;-) Maybe these suggestions could be considered for future openSUSE/SUSE Linux releases. Greetings, Machen Sie aus 14 Cent spielend bis zu 100 Euro! Die neue Gaming-Area von Arcor - über 50 Onlinespiele im Angebot. http://www.arcor.de/rd/emf-gaming-1

2 2

problem with eject and cdrecorder
by Chema Ollés 08 Nov '05

08 Nov '05

Hi all: Ever since I updated same files for alpha2 I have problem with /dev/cdrecorder (/dev/hdd).I don't know if is a problem related with permission but: 1- I can't eject it .I eject /dev/dvd (/dev/hdc) normaly. 2- I can't use cdrecord 3- I can mount it and 4- I can eject it if I use /media/cdrecorder Why this change? And How can I burn cds now? Thanks -- Chema Ollés Usuario Linux: #198057 Linux 2.6.14-rc3-g82984114 #1 SMP Sat Oct 8 15:39:19 CEST 2005 i686

1 1