December 2004 - openSUSE Users - openSUSE Mailing Lists

apt preferences
by B. Stia 31 Dec '04

31 Dec '04

Hello SuSE apt people, Don't have a preferences file in /etc/apt. Want to pin an app from downloading/installing. Is it just me ? Running 9.2 and KDE 3.3.2 Bob S.

3 2

Clean install of 9.2
by Kelly J. Morris 31 Dec '04

31 Dec '04

I have decided to do a clean install of SuSE Pro 9.2 and would like some advice on several points. Background: My current system is a P4 2.8 Mhz w/ 1 GB RAM and two 80 GB HDs. Windoze XP SP2 is on the first HD. The second HD has a 500 MB partition formatted FAT16 and the remainder is SuSE Pro 9.0 with a 1 GB Linux Swap partition and the rest a single / partition using ReiserFS. I have Ximian (GNOME) Desktop 2, Evolution 1.4.6, Ximian oOo 1.1.1, and Firefox 1.0 installed. I want to use GNOME but assume that I'll be using SuSE's version and that I'll use YaST instead of Red Carpet for my updating. 1. Does the SuSE 9.2 installation need to begin in the first 1024 cylinders, or can I install SuSE anywhere? e.g. if my SuSE partition began at the 10, 15, or 20 GB point of an 80 GB HDD, would this cause any problems? I thought that recent iterations of Linux were not required to begin within the 1024 limit, but I have heard conflicting opinions on the subject. 2. When I installed SuSe 9.0, I intended to use Boot Magic (that comes with Partition Magic) as my boot manager. However, I unintentionally chose to use grub, so I deactivated Boot Magic. I use grub and it is OK but I do prefer BM. Once I have backed-up the data and settings that I want to keep, I plan to delete the current SuSE partitions using Partition Magic. However, how do I delete whatever changes have been made to the MBR when I installed grub? How do I avoid setting grub as my boot manager at installation of SuSE 9.2? (I seem to remember with RH 7.1 that I selected lilo as the boot loader but, by opting not to make any changes to the MBR, I was able to use Boot magic as my boot manager.) 3. Will the data and especially the settings that I transfer from my 9.0 system to 9.2 run into any compatibility problems, especially in re: Evolution? Should I expect this to be able to move data and settings from Evolution 1.4.6 to 2.0.x , or might there be complications? If so, how can I avoid or otherwise deal with them? I plan to save and transfer several folders in /home/kelly, especially /Documents and /evolution. What about some of the "hidden" folders and files in /home/kelly - are any of them important to transfer? TIA Kelly Morris

2 1

specific sensors directions
by Richard 31 Dec '04

31 Dec '04

I am trying to get sensors working. I ran sensors-detect, followed all steps, up to the point where it directs to add modprobe lines to "...some /etc/rc* file." Howto directions in other places say to add lines "...to the appropriate /etc/rc.d/xxxx file." Can someone be a little more specific about the file to add these lines to? What may be appropriate to someone wiser is not so obvious to me. Thanks for your assistance. Richard

3 5

SuSE 9.2 Installed SMP kernel
by Lucky Leavell 31 Dec '04

31 Dec '04

OS: SuSE 9.2 Pro installed from DVD Hardware: Dell 1600SC with LSI SCSI Controller Just completed install and YoU but noticed kernel is 2.6.8-24.10-smp. While the 1600SC is dual CPU capable, it has only one processor installed. Is this anything to be concerned about? Thank you, Lucky Leavell

3 2

SuSE 9.2 building custom lirc error - "libtool:unrecognized option `--tag=CC'"
by Richard Mixon (qwest) 31 Dec '04

31 Dec '04

Hello (this is second attempt to trim size and get to list, hope it makes it), I am trying to use the HOWTO from: http://losdos.dyndns.org:8080/public/mythtv-info/MythTV_DISH_IR_LED_TX _via_Modified_LIRC.html I wish to have MythTV control a second instance of LIRC to control my Qwest ChoiceTV gateway box (a Next Level Communications / Motorola RG2000). My MythTV box is based on SuSE Pro 9.2. I installed the kernel sources and did the following: cat /proc/config.gz config.gz gunzip config.gz mv config .config make menuconfig (then just used the "save config" option to save) make bzImage make modules All appeard to build fine, did not see any reason to install though. After getting the lirc archive when I run the script I end up with a failure, the main error appearing to be: libtool: unrecognized option `--tag=CC' This error occurs towards the end of the console output, which I've included in its entirety below (sorry for the length). What am I missing, I've got the more recent version of libtool: mythtv1:~/myth-ledxmit # libtool --version ltmain.sh (GNU libtool) 1.5.8 (1.1220.2.118 2004/08/07 12:24:38) And my system has been updated with apt from sources provided at: http://folk.uio.no/oeysteio/apt/suse/ I am not sure if this is a SuSE kernel issue or a problem with the lirc procedure - so I have posted it to both lists> Thank you much for any ideas/suggestions on how to fix this. - Richard CONSOLE OUTPUT FROM myth-ledxmit.sh FOLLOWS: mythtv1:~/myth-ledxmit # ls -sl total 2824 0 drwxr-xr-x 3 root root 256 Dec 30 19:21 . 1 drwx------ 22 root root 968 Dec 30 19:15 .. 4 -rw-r--r-- 1 root root 2878 Dec 29 23:12 DCT2000 4 -rw-r--r-- 1 root root 2526 Dec 29 23:15 DigitalCable 60 -rw-r--r-- 1 root root 57530 Dec 30 19:15 config 16 -rw-r--r-- 1 root root 14133 Dec 29 23:35 ledxmitd.conf 1 drwxrwxrwx 8 rnmixon users 1056 Nov 7 06:40 lirc-0.7.0 2735 -rw-r--r-- 1 root root 2795520 Dec 29 18:52 lirc-0.7.0.tar 4 -rwxr-xr-x 1 root root 2479 Dec 30 00:13 myth-ledxmit.sh mythtv1:~/myth-ledxmit # ./myth-ledxmit.sh lirc-0.7.0 ./myth-ledxmit.sh: Copying lirc source directory... ./myth-ledxmit.sh: Moving lirc directories ./myth-ledxmit.sh: Moving lirc files ./myth-ledxmit.sh: Renaming lirc vars in files ./myth-ledxmit.sh: Renaming LIRC vars in files ./myth-ledxmit.sh: Restoring exec permissions ./myth-ledxmit.sh: Running configure creating cache ./config.cache checking for a BSD compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for mawk... no checking for gawk... gawk checking whether make sets ${MAKE}... yes checking for gcc... gcc checking whether the C compiler (gcc -O2 -g -Wall ) works... yes checking whether the C compiler (gcc -O2 -g -Wall ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for a BSD compatible install... /usr/bin/install -c checking whether make sets ${MAKE}... (cached) yes checking for mknod... /bin/mknod checking for mkfifo... /usr/bin/mkfifo checking for depmod... /sbin/depmod checking for libusb-config... /usr/bin/libusb-config checking whether ln -s works... yes checking for Cygwin environment... no checking for mingw32 environment... no checking how to run the C preprocessor... gcc -E checking host system type... i686-pc-linux-gnu checking build system type... i686-pc-linux-gnu checking for ld used by GCC... /usr/i586-suse-linux/bin/ld checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes checking for /usr/i586-suse-linux/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking for a sed that does not truncate output... /usr/bin/sed checking how to recognise dependent libraries... pass_all checking for object suffix... o checking for executable suffix... no checking command to parse /usr/bin/nm -B output... ok checking for dlfcn.h... yes checking for ranlib... ranlib checking for strip... strip checking for objdir... .libs checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.lo... yes checking if gcc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking dynamic linker characteristics... GNU/Linux ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether -lc should be explicitly linked in... no creating libtool checking for ANSI C header files... yes checking whether time.h and sys/time.h may both be included... yes checking for fcntl.h... yes checking for limits.h... yes checking for sys/ioctl.h... yes checking for sys/time.h... yes checking for syslog.h... yes checking for unistd.h... yes checking for working const... yes checking for inline... inline checking for off_t... yes checking for pid_t... yes checking for size_t... yes checking whether struct tm is in sys/time.h or time.h... time.h checking return type of signal handlers... void checking for vprintf... yes checking for gethostname... yes checking for gettimeofday... yes checking for mkfifo... yes checking for select... yes checking for socket... yes checking for strdup... yes checking for strerror... yes checking for strtoul... yes checking for snprintf... yes checking for strsep... yes checking for vsyslog... yes checking for daemon... yes checking for forkpty... no checking for forkpty in -lutil... yes checking for vga.h... no checking for X... no checking for getopt_long... yes checking for mktemp... yes checking for Linux kernel sources... /usr/src/linux/ checking for which drivers can be installed on this system... checking for caraca_init in -lcaraca_client... no checking for ir_strerror in -lirman... no checking for ir_strerror in -lirman_sw... no checking for portaudio.h... no checking for alsa/asoundlib.h... no updating cache ./config.cache creating ./config.status creating Makefile creating drivers/Makefile creating drivers/ledxmit_atiusb/Makefile creating drivers/ledxmit_bt829/Makefile creating drivers/ledxmit_dev/Makefile creating drivers/ledxmit_gpio/Makefile creating drivers/ledxmit_i2c/Makefile creating drivers/ledxmit_igorplugusb/Makefile creating drivers/ledxmit_it87/Makefile creating drivers/ledxmit_mceusb/Makefile creating drivers/ledxmit_parallel/Makefile creating drivers/ledxmit_sasem/Makefile creating drivers/ledxmit_serial/Makefile creating drivers/ledxmit_sir/Makefile creating daemons/Makefile creating tools/Makefile creating doc/Makefile creating doc/man/Makefile creating config.h You will have to use the ledxmit_serial kernel module. Now enter 'make' and 'make install' to compile and install the package. ./myth-ledxmit.sh: Running make cd . && /bin/sh /root/myth-ledxmit/myth-ledxmit.WIP/missing --run aclocal acinclude.m4:11: warning: underquoted definition of AC_PATH_KERNEL_SOURCE_SEARCH run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending-aclocal acinclude.m4:65: warning: underquoted definition of AC_PATH_KERNEL_SOURCE cd . && \ /bin/sh /root/myth-ledxmit/myth-ledxmit.WIP/missing --run automake --gnu Makefile cd . && /bin/sh /root/myth-ledxmit/myth-ledxmit.WIP/missing --run autoconf /bin/sh ./config.status --recheck running /bin/sh ./configure --program-prefix=ledxmit- --prefix=/usr/local/lirc-ledxmit --with-major=72 --with-port=0x3f8 --with-irq=4 --with-transmitter --enab le-sandboxed --with-driver=serial --no-create --no-recursion checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking whether make sets $(MAKE)... (cached) yes checking for mknod... /bin/mknod checking for mkfifo... /usr/bin/mkfifo checking for depmod... /sbin/depmod checking for libusb-config... /usr/bin/libusb-config checking whether ln -s works... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/i586-suse-linux/bin/ld checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes checking for /usr/i586-suse-linux/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes <SNIP - list limit is 20,000 bytes> config_file.h:26: warning: `all_flags' defined but not used if gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -g -Wall -MT dump_config.o -MD -MP -MF ".deps/dump_config.Tpo" -c -o dump_config.o dump_config.c; \ then mv -f ".deps/dump_config.Tpo" ".deps/dump_config.Po"; else rm -f ".deps/dump_config.Tpo"; exit 1; fi if gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -g -Wall -MT config_file.o -MD -MP -MF ".deps/config_file.Tpo" -c -o config_file.o config_file.c; \ then mv -f ".deps/config_file.Tpo" ".deps/config_file.Po"; else rm -f ".deps/config_file.Tpo"; exit 1; fi if gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -g -Wall -MT hw-types.o -MD -MP -MF ".deps/hw-types.Tpo" -c -o hw-types.o hw-types.c; \ then mv -f ".deps/hw-types.Tpo" ".deps/hw-types.Po"; else rm -f ".deps/hw-types.Tpo"; exit 1; fi if gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -g -Wall -MT ir_remote.o -MD -MP -MF ".deps/ir_remote.Tpo" -c -o ir_remote.o ir_remote.c; \ then mv -f ".deps/ir_remote.Tpo" ".deps/ir_remote.Po"; else rm -f ".deps/ir_remote.Tpo"; exit 1; fi if gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -g -Wall -MT hw_default.o -MD -MP -MF ".deps/hw_default.Tpo" -c -o hw_default.o hw_default.c; \ then mv -f ".deps/hw_default.Tpo" ".deps/hw_default.Po"; else rm -f ".deps/hw_default.Tpo"; exit 1; fi if gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -g -Wall -MT receive.o -MD -MP -MF ".deps/receive.Tpo" -c -o receive.o receive.c; \ then mv -f ".deps/receive.Tpo" ".deps/receive.Po"; else rm -f ".deps/receive.Tpo"; exit 1; fi if gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -g -Wall -MT transmit.o -MD -MP -MF ".deps/transmit.Tpo" -c -o transmit.o transmit.c; \ then mv -f ".deps/transmit.Tpo" ".deps/transmit.Po"; else rm -f ".deps/transmit.Tpo"; exit 1; fi /bin/sh ../libtool --tag=CC --mode=link gcc -O2 -g -Wall -o irrecord irrecord.o dump_config.o config_file.o hw-types.o ir_remote.o hw_default.o receive.o transmit.o libtool: unrecognized option `--tag=CC' Try `libtool --help' for more information. make[2]: *** [irrecord] Error 1 make[2]: Leaving directory `/root/myth-ledxmit/myth-ledxmit.WIP/daemons' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/myth-ledxmit/myth-ledxmit.WIP' make: *** [all] Error 2 mythtv1:~/myth-ledxmit # Richard Mixon >From LtoJ Software, L.L.C. Vice President, Architecture and Technology Education Software for Continuous Improvement mobile: (480) 577-6834 office: (480) 614-3442 email: rnmixon(a)FromLtoJ.com <mailto:rnmixon@FromLtoJ.com> web: http://www.FromLtoJ.com The messages and documents transmitted with this notice contain confidential information belonging to the sender. If you are not the intended recipient of this information, you are hereby notified that any disclosure, copying, distribution or use of the information is strictly prohibited. If you have received this transmission in error, please notify the sender immediately. _______________________________________________ mythtv-users mailing list mythtv-users(a)mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

1 0

netgear MA111 on 9.2 (or other device recomendation)
by Linux 31 Dec '04

31 Dec '04

Hi Has anyone got the Netgear MA111 USB wireless device to work. If so how? Failing that has anyone got a USB wireless device from somewhere like PC world UK to work straight out of the box ( or nearly) in case I have to buy one in a hurry tomorrow and if so what was it please. Thanks in advance. Regards Roger

1 0

Re: [SLE] 9.1 > 9.2 question
by Joe Polk 31 Dec '04

31 Dec '04

Umm...well, I have to respond now don't I. Wish denied. But seriously, I have given details in previous posts and have already outlined some of them in this thread. Look, I'm not shattering your belief system, it's just a single version of a distro. Calm down. Goto your Games menu and look for the Chess game. Aha! The menu isn't setup right. Now goto to the KDE Menu Editor and try to fix it. If you're even close to successful it will take some time and fanagling. WiFi going away? On my planet it's very popular. Not only that, the masses like it. It would behove a distro to support it. And let's try to support cards that you can actually walk in a retail store and by. For years all I heard was "My Orinoco works fine! I got it at "Obscureshit.com" for $35!" Again, it's in the best interest of all concerned to support popular hardware. I realize there are limits and obstacles, but make it a goal. For the record, as I've already said, this was a fresh install. NOT an upgrade. But what if I did? If upgrading doesn't work, then my point is given even MORE weight, no? BTW this was a stock kernel on 2 different machines. Congrats that you have had a flawless installation. I bet, however, I could find problems in your menus if they haven't been altered and I'm confident I can illustrate problems with the menu editor. And I've already said these may be more of a problem with KDE than SuSE. Though the cosmetic problems are definitely SuSE and a QA issue. I'm not angry here and in fact enjoy the discourse. I'm glad many have had a great experience with 9.2. I didn't and from what I've read many haven't. It's threads like this that I hope will make someone take notice and think about better QA, better support, better distro's in general. Please don't treat me like I'm advocating that we all give up and install XP! I consider this a friendly discussion. Though I admit, my intent is to challenge and get some attention to these issues so that version 10 is considerably better. -- <<JAV>> > I wish you'd stop top posting. > > You don't give anything like details, but I haven't seen anything > like what you mention in 9.2 yet, and I've been running it since the > week it shipped. Sounds like you tried to "upgrade" rather than do a > proper install. > > Personally, I suspect Wi-Fi is going to be another flash in the pan. > WEP will survive even a half-assed attack for a few minutes at best, > and practically no one locks their hubs down properly, which makes > for fascinating reading but lousy networks - I figure most of the people > who are trying to use it are going to be moving to hardwire in a year > or less, so I don't see a point in spending a lot of effort on it. > > The whole hotplug idea is a major paradigm shift for linux, so I can > see it taking a while to get there. > > I do wish they'd stop fooling around with sound though. OSS, Alsa, > etc., and about half of the applications work with a given sound > system. > > Mike- > > -- > If you can keep your head while those around you are losing theirs... > You may have a great career as a network administrator ahead! > -- > Please note - Due to the intense volume of spam, we have installed > site-wide spam filters at catherders.com. If email from you bounces, > try non-HTML, non-encoded, non-attachments, ------- End of Original Message -------

4 5

Memory Leak - poss. gkrellm?
by Mark Crean 30 Dec '04

30 Dec '04

Is anyone else experiencing a memory leak on SuSe 9.2, possibly while running gkrellm (2.2.4-1 here)? When it occurs, I've had free -m plunge by 350 megs in a few minutes before I stopped it by logging out and back in again. I can't find the cause. The leak occurs intermittently under both kde and gnome, but gkrellm seems in the frame as I noticed when running top that it kept popping up towards the top of the list with another 18 megs of memory taken up. Last night my machine, idling unattended, and with suseplugger, susewatcher and artsd (isn't the most recent iternation duff?) all turned off, still managed to eat up nearly another 400 megs of ram for no obvious reason when I came back to it this morning, so something isn't right. Anyway, I've now turned gkrellm off so we'll see. :) Fish

1 0

Mailserver setup procedure
by Hylton Conacher (ZR1HPC) 30 Dec '04

30 Dec '04

Tnx again to all for helping me understand the mail process and what does what. I have completed the MTA configuration, (does SuSE use Postfix?), under Yast->Network Services->MTA. What is the next step in incorporating Clamav and SA into it, as the packages are installed? -- The Little Helper ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ========================================================================

3 2

Evolution icon move
by Linux 30 Dec '04

30 Dec '04

For anyone upgrading from 9.1 to 9.2 by the clean install method running KDE and adding Evolution. The icon has moved from the Internet>email to the office menu. Regards Roger

1 0