RE: [gentoo-user] Re: Weird dmesg message

2005-02-05 Thread Joost van Surksum
Your swapfile is pretty heavily in use, with 182 MB. I don't know what the machine is doing, but using much swap space may slow down a system. Is your system responding well? Consider inserting more RAM memory into your system. Joost > basement robert # swapon -s > Filename

RE: [gentoo-user] Directories in /usr/src

2004-01-12 Thread Joost van Surksum
These dirs are not part of a kernel package. A command 'qpkg -v -f /usr/src/pc' will tell you that it's part of the 'rpm' package (plus version number). If you don't have that package installed any more, then you can safely remove the dirs. (If you don't have qpkg, then emerge gentoolkit). Chee

RE: [gentoo-user] smbfs and portage

2004-01-04 Thread Joost van Surksum
Hello Chris, I know a big gotcha: Over a samba connection, user permissions and ownerships are not well maintained or preserved, because a Windows file system has different file/ownership properties than a unix/linux file system. I've had the same rsync problems over a samba connections. Rsync c

RE: [gentoo-user] mad won't build

2004-01-04 Thread Joost van Surksum
Now that I look back at the messages, I may have created a little confusion: my own linker error messages were different from Bretts original messages. My linker complained about missing compress/uncompress functions from inside the libid3tag library, Bretts message was about a missing 'id3_frame_

RE: [gentoo-user] mad won't build

2004-01-04 Thread Joost van Surksum
Thanks for the tip Tom, very useful command. It found six or seven more packages on my system, that need to be refreshed. Joost > -Oorspronkelijk bericht- > Van: Tom Wesley [mailto:[EMAIL PROTECTED] > Verzonden: zondag 4 januari 2004 20:22 > Aan: [EMAIL PROTECTED] > Onderwerp: Re: [gento

RE: [gentoo-user] mad won't build

2004-01-04 Thread Joost van Surksum thuis
Problem solved for me (I was having the same problem). My solution was to emerge libid3tag again. As you can see, the linker was missing two symbols (functions) in the libid3tag.so. I had the same problem, but re-emerging libid3tag solved it. Command: emerge libid3tag On my system, it emerges m