Missing Cd Audio Player XMMS input plugin...
Deb-heads, Just installed XMMS 1.2.5 from Debian's Woody branch and everything seems to be fine EXCEPT when it comes to playing CDs. Poked around a bit and what I discovered is that I am missing the Cd Audio Player input plugin from my list of available input plugins. So...where can I find this plugin or what do I do to configure XMMS to play audio CDs? robert.a.jacobs
Re: help
* Peter Whittam [EMAIL PROTECTED] [140601 18:15]: I am trying to install Mozilla but it complains about unreachable files libstc++ - libc6.1-1.so.2 can anyone help? Try this (as root): # cd /usr/lib # ln -s libstdc++-3-libc6.2-2-2.10.0.so libstdc++-libc6.1-1.so.2 If you don't have libstdc++-3-libc6*, try one of the other libstdc++ files in its place. Mozilla is looking for libstdc++-libc6.1* but one of the others should work. also i want to connect to my LAN(other machines using windows) - all hardware is there from when I used to run Win2000. can anyone supply basic setup info or point me to a source. Check out Samba. I haven't configured it...but that is what you need. robert.a.jacobs
What happened to the task-gnome* packages in Woody?
Debian Users, What happened to the task-gnome* packages in Debian Woody? I see that the packages are still available in both Potato and Sid but Debian they are curiously absent in Woody? If a user wishes to install Gnome, which packages must he install in the absence of a single task package? As always, your help is greatly appreciated. robert.a.jacobs
Re: newbieDoc.sourceForge.net
* David Nusinow [EMAIL PROTECTED] [130601 11:03]: Not that I'm against some duplication, but isn't this basically what www.linuxnewbie.org is doing? They were absolutely critical in my early days of linux, and I still head back there every so often to search the archives to see if anyone else has had my problem. Hmmm...you might want to head over there and check it out again then. Sensei no longer works for Internet.com (he went to work for Trolltech, I think). Sooo...the fate of linuxnewbie is currently up in the air. For what its worth, I did enjoy linuxnewbie (heck, got my ISA PNP USR 56K Modem configured and running using the information at that site) but I do think that it tended towards the magical incantation side of the linux experience. robert.a.jacobs
Re: newbieDoc.sourceForge.net
* David D.W. Downey [EMAIL PROTECTED] [130601 15:17]: On Wed, 13 Jun 2001, Robert A. Jacobs wrote: Hmmm...you might want to head over there and check it out again then. Sensei no longer works for Internet.com (he went to work for Trolltech, I think). Sooo...the fate of linuxnewbie is currently up in the air. Sorry to but in, yet is this linuxnewbie.org or .com you refer to? I was one of the original helpers for linuxnewbie.com and I haven't heard anything about this disappearing. linuxnewbie.org
Re: Need help setting up SB PCI 128 sound card on potato system
* Nate Amsden [EMAIL PROTECTED] [040401 08:58]: Joe Nahmias wrote: So far, I have downloaded the latest 2.2 kernel (2.2.19) and compiled in support for the card (CONFIG_SOUND_ES1371=y), with no success. After booting the newly compiled kernel, the soundcard is recognized (see dmesg output fragment below), but it is unusable, ie. 'cat /dev/sndstat' returns: No such device. did you expect something from /dev/sndstat ? i've never used that .. i also have a ES1371(or is it a 1370 ..) it is a SB PCI 128..using kernel 2.2.18(self compiled and it works great. infact its by far my favorite soundcard to use in linux..i wouldnt use anything else. FWIW: cat /dev/sndstat used to produce a listing of information about the installed sound device. I see that it no longer does...it did, however, function that way in 2.2.17 (at least with regards to my Soundblaster AWE64). The command is referenced in the Soundblaster AWE64 HOWTO (and probably in the Sound HOWTO as well...)
Re: dist-upgrade to woody
* Patrick Mauro [EMAIL PROTECTED] [030401 12:33]: snip! I have potato installed on my machine. When I upgraded to woody I got gross problems. First, as I understand it, I did the correct upgrade steps. - modified sources.list to reflect that I want woody stuff now. - apt-get update - apt-get dist-upgrade Yep. Them's the steps. The big problem is that my X won't work! Whenever I try to run it, I now get an error saying something like unable to stat file /etc/X11/X. Well...woody and potato handle X and its configuration very differently. Woody uses X 4.02 (I think) while potato uses 3.3.6. There are a number of differences, not the least of which is that your X configuration is no longer stored in /etc/X11/XF86Config but is now stored in /etc/X11/XF86Config-4. I poked around google and so far from what I've seen, /etc/X11/X should be a symlink to /usr/X11R6/bin/XF86_SVGA. Also the file /etc/X11/Xserver should contain the lines /usr/bin/X11/XF86_SVGA and console. Make sure that when you are poking around on google you are poking around for data on XFree86 4.02 and not 3.3.6. The new X doesn't really use XF86_SVGA anymore. I believe that the preferred server and method of accessing the server in XFree86 4.02 is via a symlinking /etc/X11/X - to /usr/bin/X11/XFree86. Like I said...lots of changes where X is concerned in woody. What's everyone's thought on this. Also, why didn't the upgrade set this up automatically? I would think when it replaced the old version of X it would have done it. Keep in mind that Woody IS Testing. When it goes stable, it may do this automagically but for now it doesn't. When you play with anything other than stable you have to be prepared to diddle with the settings yourself. One last question, why did they take XF86Setup away. I always had problems with XF86Config, but not with XF86Setup. If worse comes to worse I guess I'll have to learn the art of XF86Config files (it never works after running the Config program). Not sure. The good news, however, is that the new XF86Config-4 file is a LOT easier to mess with and to understand. You shouldn't have too many problems learning the art. This issue has been discussed a lot over the last few months in the Debian User lists...I'd recommend you search the archives at http://lists.debian.org and see what you can find. robert a. jacobs
Re: removing obsolete packages
* Iwan Mouwen [EMAIL PROTECTED] [030401 19:28]: Hi, is there a way to delete packages from the cache (or from some other directory) for which a newer package exists in that directory. My /var/cache/apt/archives has several versions of lots of packages and I want to remove them. apt-get autoclean doesn't seem to do what I want. What you want is apt-get clean autoclean only removes packages that can no longer be downloaded. robert a. jacobs
Re: dist-upgrade to woody
Well...woody and potato handle X and its configuration very differently. Woody uses X 4.02 (I think) while potato uses 3.3.6. There are a number of differences, not the least of which is that your X configuration is no longer stored in /etc/X11/XF86Config but is now stored in /etc/X11/XF86Config-4. Okay! Okay! Okay! :) I goofed. Woody can ALSO run 3.3.6! I guess I'm going from memory and from the numerous postings here on Debian User that when upgrading to Woody it is not uncommon to experience problems with the X configuration and a lot of it has to do with XF 4.0X either attempting to install itself or otherwise confusing the issue with regards to how X operates. IIRC, when many users upgrade to Woody, their X configuration is jacked up and they have to take matters into their own hands to straighten it back out. robert a. jacobs
Re: removing obsolete packages
* Karsten M. Self kmself@ix.netcom.com [030401 20:30]: on Tue, Apr 03, 2001 at 07:52:02PM -0500, Robert A. Jacobs ([EMAIL PROTECTED]) wrote: * Iwan Mouwen [EMAIL PROTECTED] [030401 19:28]: Hi, is there a way to delete packages from the cache (or from some other directory) for which a newer package exists in that directory. My /var/cache/apt/archives has several versions of lots of packages and I want to remove them. apt-get autoclean doesn't seem to do what I want. What you want is apt-get clean autoclean only removes packages that can no longer be downloaded. ...which is to say, packages which have been replaced by updated versions. What he wants _is_ autoclean, why it's not working, or his understanding of its workings, is a mystery. Whoops. Shoulda read his post closer...I thought he wanted to clean out all the packages in that directory. A second read through cleared up my misconception. robert a. jacobs
SOLVED! Apache mod_perl + mod_cgi in same directory
Thanks Keith for your suggestions. In the end, I settled upon a variation of what you suggested. My goal: to allow my users to create static and dynamic HTML pages in their own home directories using both CGI and PERL as they liked. Basically, I wanted to be able to serve CGI and PERL-CGI out of the same directory. The Problem: mod_cgi and mod_perl both provide CGI services. If you attempt to set them up under the same directory, only one of them will work. The Solution: NOTE: I use only one config file: httpd.conf in accordance with current Apache configuration practices. 1. I enabled mod_userdir during installation of my Apache 1.3.17 server and set the UserDir to public_html. This means that anywhere under the user's home directory, they can create a public_html directory from which to serve web pages: IfModule mod_userdir.c UserDir public_html /IfModule 2. I disabled the UserDir for Root, per suggestion from Apache's website: UserDir disabled root 3. I set the controls on the public_html directory as follows: Directory /home/*/public_html Options +ExecCGI +Includes +Indexes AllowOverride None Order Allow,Deny Allow from All /Directory 4. CGIs are enabled in the public_html directory (+ExecCGI) and can be served from outside /usr/local/apache/cgi-bin because the following lines were enabled in the mod_mime section of the configuration file: AddHandler cgi-script .cgi Now, any file ending in .cgi will be handled by the cgi-script handler 5. I wanted something equivalent to step four for handling perl-script files. The solution was to create a LocationMatch so that any URL ending in a predefined regular expression would be handed off to the PerlHandler. The form of the expression to be matched was /somefile.pl LocationMatch \/*\.pl$ SetHandler perl-script PerlHandler Apache::Registry PerlSendHeader On /LocationMatch Caveats: This is not the most secure solution in the world. If you do not personally know your users, as I do, and/or you do not trust them, I suggest you stick with the Apache recommended approach of creating a cgi-bin and/or perl-bin directories and only allow cgi's served out of those directories. Since my webserver is for development purposes, I wanted greater flexibility. Now both .cgi and .pl files can reside in the same directory and each is handled by the appropriate Handler. robert a. jacobs
Apache mod_perl + mod_cgi in same directory
Is it possible to enable CGIs (shell scripts, C/C++ apps, etc.) and CGI perl-scripts to both operate out of the same directory? I know you can do this if you add .pl to the list of extensions approved under the handler cgi-script...what I want to be able to do is have perl-scripts handled by the PerlHandler. For example: I want to be able to load both a CGI shell script and a CGI perl-script into /home/user/public_html and have the CGI shell script handled by mod_cgi while the CGI perl-script is handled by mod_perl. Right now, I am able to have scripts handled by either the PerlHandler or the cgi-script handler but not both in the same directory. I suspect the reason is that they are both CGI handlers so, given the configuration I am currently using, Apache uses whichever handler is defined first for that directory. I know that I can separate each type of script into their own directory and handle them accordingly. I would rather avoid that if possible for the sake of flexibility. Any suggestions? robert a. jacobs
Opera Browser and Plugins
Has anyone managed to get any plugins installed while using the Opera web-browser? If so, which ones and how did you do it? I'm particularly interested in Flash and some form of media player... Thanks, robert jacobs [EMAIL PROTECTED]
SOLVED!: Upgrade Problems (Stable-Testing)
Here's how I ironed out the problems in my system after upgrading from Potato to Woody: * [EMAIL PROTECTED] [250201 21:56]: I was pretty sure everything other than my GUI and Sound was working properly based on watching the screen messages during boot and perusing dmesg. The only problem I really seemed to be having was logging into my Gnome desktop and getting sound working (error messages during boot told me this was not working) Regarding Sound: I have an Soundblaster AWE64 that was running fine prior to the upgrade. Now, for some reason, there are errors occurring when the sound modules are loaded. Loading during boot fails and when I attempt to load the modules manually I get unresolved symbol errors. Do I need to recompile my kernel? It appeared to me that the way modules were handled changed somewhat between Potato and Woody (I did not remember there being as many items in /etc/modutils/ as there appear to be now). Any suggestions? What additional information do you need to help with troubleshooting? A recompile using the 2.4.1 kernel solved this problem. Had to fiddle a bit with which modules to install, but otherwise I did not have much trouble with this one -- the unresolved symbol errors were the clue. Oh..and modutils did change significantly. If you are running the newer kernel (2.4.1), you need the modutils package with the matching version number (modutils 2.4.1). I scrubbed menuconfig pretty closely and completely redid my kernel. A few nice things were better support for the SB AWE 32/64 and 3dfx Video Cards ( both of which I needed!). Turns out that you pretty much have to recompile the 2.4.1 kernel to support a 3dfx Voodoo3 3000 card. Compiling in the necessary 3dfx video support is what creates the tdfx driver you'll use with the XFree86 server (/usr/bin/X11/XFree86). Regarding X or Gnome: I can get to the Gnome login screen and everything looks fine at that point. When I type in my user name and password, the screen flicks off and when it comes back into view I'm still at the Gnome login screen. In case it is relevant, my preferred Window Manger is Enlightenment. Suggestions? I'm not well-versed in X so I'll need you to tell me what files I should look for and provide to the forum and I will. Does this sound like it is an X problem or a Gnome/Enlightenment problem? After recompiling the kernel, fixing the sound problem and creating the tdfx driver, I still could not login to my Gnome Desktop so... I pretty much reinstalled X, a bit at a time, to get this situation resolved. I started by following the HOWTO article at http://www.debianplanet.org on how to configure X4 to run with 3dfx cards. My goal was not to do it piecemeal (I was NOT trying to troubleshoot); it just ended up that way. For what its worth, X4 seems to run faster than its predecessor! The gist of it was this: kill x by ctrl-alt-backspace or whatever your preferred method is. I got stuck in a loop with gdm bringing me back to the login screen so I had to do a kill gdm #dpkg --purge xserver-svga #apt-get update #apt-get install task-x-window-system libglide3* The apt-get will remove gdm and install xdm in its place. I figured this was okay. However, startx caused problems so I reinstalled gdm #apt-get install gdm and was able to get back to the gdm login screen. Throughout this entire adventure I noticed that approximately 6 packages were on hold and never upgraded: task-x-window-system-core and a number of xfonts. I'm guessing that having the task-x-window-system-core files on hold is what was screwing things up (though I never remember placing them on hold). After issuing an apt-get install on the core files and various fonts, I deleted /etc/X11/XF86Config-4 (leftover from previous attempts) and created a new file with xf86config. I then shutdown and restarted gdm and managed to login to my desktop! Hoo-rah. task-x-window-system should have been the complete X environment. Something was goofed on my system...hopefully its not on yours. Hope this helps someone else, rob DISCLAIMER: I spent the better part of a day fiddling with my system to get it all working again. I have to admit that much of what I was doing was poking and prodding at X. I may have missed some of the details of what I did so please do not take this account of my activities as gospel truth. Hopefully it will give you ideas of your own to use in solving your problem.
Re: Upgared stable to testing, and I broke X, help please.
* Stan Brown [EMAIL PROTECTED] [260201 15:27]: I am trying to upgarde a fairly important production machien from stabel to testing. I built a test machine at home this weekend and tried this, and all went well. I wish I could have said all went well with my recent upgrade from Stable to Testing! However that machine had a smallish disk, and I did not install all the packages, big mistake! During the configuration step, I was prompted to choose, what I vaugely remember as a X server, but after I chose that later I swa some messages that made me think I might have picked XFree86 4, which was not what I intended to do! In any case, X was working great on this machine, untill I did this, so what's the best way to figure out what I have dome to create this mess, and get back to my working config? Well...I did a dist-upgrade to Testing yesterday (and managed to straighten out the mess after about 10 hours or so). These may be overkill, but their the only suggestions I have based upon my own experience: 1. Roll your own kernel from the 2.4.1 kernel sources. 2. Be sure your modutils is upgraded. 3. purge your old xserver (dpkg --purge xserver_yourXServer) 4. Install task-x-window-system I also had to install libglide3* for my Voodoo3 3000 and a few other X related packages that were held back on my system for some reason (task-x-window-system-core and a number of font packages) 5. Create an XF86Config-4 file using xf86config (I've heard dexter is really good, but I have no idea where to find that. Could it be dexconf?) 6. If you use gnome, install gdm (task-x-window-system removes gdm in favor of 'xdm') Anyways...there's a few places to start. robert jacobs [EMAIL PROTECTED]
Upgrade Problems (Stable-Testing)
Good evening everyone, This is my first experience with upgrading from one version to another. I love the debian apt-get tool; for routine upgrades and keeping my system in top order with security updates it has been the greatest help. The upgrade from stable to testing has not been fun so far. Here's the low-down: I upgraded my Potato 2.2r2 system, running a custom compiled 2.2.17 kernel, to Woody via apt-get dist-upgrade today and I've been frustrated ever since; seems that in the process of upgrading I broke or otherwise mangled both my X|Gnome and sound configurations (everything else APPEARS to be working based on Startup and Kill messages when changing between runlevels i.e. I can still get out to the Internet via lynx and my mail still flows! :] ). Regarding X or Gnome: I can get to the Gnome login screen and everything looks fine at that point. When I type in my user name and password, the screen flicks off and when it comes back into view I'm still at the Gnome login screen. In case it is relevant, my preferred Window Manger is Enlightenment. Suggestions? I'm not well-versed in X so I'll need you to tell me what files I should look for and provide to the forum and I will. Does this sound like it is an X problem or a Gnome/Enlightenment problem? Regarding Sound: I have an Soundblaster AWE64 that was running fine prior to the upgrade. Now, for some reason, there are errors occurring when the sound modules are loaded. Loading during boot fails and when I attempt to load the modules manually I get unresolved symbol errors. Do I need to recompile my kernel? It appeared to me that the way modules were handled changed somewhat between Potato and Woody (I did not remember there being as many items in /etc/modutils/ as there appear to be now). Any suggestions? What additional information do you need to help with troubleshooting? Help is greatly appreciated, rob
LAMP Question -- Perl AND PHP
Running a Debian 2.2r2 system with a little bit of Woodage (nothing extreme) and still using the 2.2.17pre-* kernel packaged with Potato. Am venturing into the world of LAMP (Linux Apache MySQL PHP) and would like to do the installations from source (for the experience -- so please do not recommend that I use prepackaged .deb files). I've already downloaded the sources and have been reading through the various READMEs and INSTALL docs and now I have a few questions. I have gotten the (perhaps mistaken) impression that I cannot statically link Perl and PHP to Apache together. If this is not correct, how do you build Apache so that both mod_perl and PHP 4.0 are statically linked? The Apache 'README.configure' file was not specific on how to do this or even whether it could be done at all (though it provided adequate examples for them individually). If I must dynamically load mod_perl or PHP, which offers the best performance improvement when statically linked? Does dynamic linking of mod_perl and PHP reduce performance of both/either dramatically? Any other gotchas I should watch out for? Thanks for your time and your help, rob
Re: upgrading the kernel to 2.4
* Ethan Benson [EMAIL PROTECTED] [040101 17:44]: unstable is a symlink to sid now. sid is permanent unstable it will never be released, it will never be frozen. Why is this? rob
Re: upgrade to 2.2.18
* [EMAIL PROTECTED] [EMAIL PROTECTED] [010101 13:32]: hi all i just finished upgrading my machine to the stable 2.2.18 kernel and everything seems to be working fine. i just have a bunch of little questions someone could shed light on. snip! question 1 and 2 3) update-modules /lib/modules/2.2.18 i've updated my modules.conf by turning off the following network protocols: alias net-pf-3 off # Amateur Radio AX.25 alias net-pf-4 off # IPX alias net-pf-5 off # DDP / appletalk alias net-pf-6 off # Amateur Radio NET/ROM alias net-pf-9 off # X.25 alias net-pf-11 off # ROSE / Amateur RadioX.25 PLP alias net-pf-19 off # Acorn Econet chances are i don't need these modules. i then ran update-modules but now i get this message during start-up: Dec 31 16:59:52 yakko modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.18/modules.dep is this normal? should i touch modules.dep to get rid of this warning or did i do something wrong. This is a known bug. Debian Bug Reports Logs: #53247 Title: modutils: modules.dep generated during boot has incorrect timestamp Age: 336 Days old as of 21 November 2000 Manifests as a message during boot that says: insmod: Note: /etc/modules.conf is more recent than /lib/modules/2.2.17/ modules.dep Suggested workaround: as root, issue depmod -a following boot. It was a problem in 2.2.17 and, given the age of the bug report, it appears the maintainer is not in any hurry to fix it (because it is not a catastrophic problem) or that it is something that will be difficult to fix. Hope this helps. rob
Re: Perl's default include path
* Neil Booth [EMAIL PROTECTED] [251100 21:42]: I get these messages trying to install recent versions of debconf: monkey:/usr/src/gcc/build# dpkg -i /var/cache/apt/archives/debconf_0.5.22_i386.deb (Reading database ... 36741 files and directories currently installed.) Preparing to replace debconf 0.5.25 (using .../debconf_0.5.22_i386.deb) ... Unpacking replacement debconf ... Setting up debconf (0.5.22) ... Can't locate lib.pm in @INC (@INC contains: /usr/lib/perl5/5.005/i386-linux /usr/lib/perl5/5.005 /usr/local/lib/site_perl/i386-linux /usr/local/lib/site_perl /usr/lib/perl5 .) at /usr/share/debconf/frontend line 21. I have 5.6 installed as the default, but as you can see it's still looking in the 5.005 directory for stuff. How do I change the @INC default path to the correct one? I'm not sure how this is done...but have you searched the debian-user archives yet? There was a discussion within the past month or two about EXACTLY this same problem...almost with the same Subject: line. I'm sure you'll find the solution there. rob.jacobs [EMAIL PROTECTED]
Re: fetchmail not communicating with exim.
* Phil Brutsche [EMAIL PROTECTED] [241100 09:16]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A long time ago, in a galaxy far, far way, someone said... I'm working on it. Just recompiled my kernel the other day to support firewalling but haven't had time to work on the iptables and other configuration issues. I find it easier to configure exim to listen only on 127.0.0.1 (with the local_interfaces setting) - it's all fetchmail needs - than fudge with firewalling. Much cleaner that way, I think. But that's just me :) Good suggestion. I'll look into that. Thanks. @home is way too broad in their description of server. I understand that their intent is to limit bandwidth since it is a shared resource but their one-size-fits-all policy is ridiculous. Tell me about it. Why doesn't anyone consider special cases like hobbyists any more? I would willingly pay a small premium to be able to run servers as a private person. They would not go for it. They were especially not helpful after I, point blank, told them that their policy only served to conserve bandwidth for use by teenagers pirating software, stolen music and porn. Hmmm...maybe I shouldn't have told them that, huh? :) :) Back to your problem with fetchmail: would it help to see a working config? I realize you are trying to be helpful but...I don't have a problem with my mail configuration. We've kind of taken a side trip off the main thread. The person with the mail problems is John-Mark [EMAIL PROTECTED], the guy who started the main thread that lead us here. :) But thanks anyways! rob.jacobs [EMAIL PROTECTED]
Re: how to keep portmap from running?
* Peter Jay Salzman [EMAIL PROTECTED] [231100 09:16]: bleah. how do i keep this program from starting on boot? i looked in /etc/init.d. can't even find a startup script for this thing! it's not in inetd.conf either. how does this thing get started? This is more of a question to the readers of this thread than directly to you Pete, but: What are the ramifications of turning portmapper on or off? I've gotten the (perhaps mistaken) impression that portmapper presents some security risks but it almost seems like I have to have it running to get other services to work properly. Is there an alternative to running portmapper? Any discussion is welcome, rob.jacobs (r.a.jacobs) ~one of these days I'll put this into my mutt .sig file :)~
Re: fetchmail not communicating with exim.
* John-Mark [EMAIL PROTECTED] [231100 09:38]: Hello all I have been battling with exim, fetchmail and mutt now for what seems like eons! I'm using *basically* the same configuration (MTA: exim, MDA: procmail, MUA: mutt POP3-GET-MY-MAIL-WHEN-I-NEED-IT-APP-:] : fetchmail). Maybe I can help? However when trying to connect receive mail from my remote server fetchmail does not seem to be passing the mail to exim and therefore I am receiving no mail in the jmj mail box. My understanding of fetchmail is that it does not really hand mail over to exim; it injects mail into the SMTP stream heading to exim. Fetchmail is really a separate application from the rest of your mail setup. Does nay one have any idea a how I can rectify this problem? Also if fetchmail is not transferring mail to exim where is it putting it? Again, my understanding is that fetchmail does not put mail anywhere; it just makes sure that mail it is grabbing is placed into the SMTP stream for exim to pick up. I do not know how much experience you have, etc., etc. so I'm going to ask you to answer a few newbie questions (besides, as a programmer, I've found that it always helps to run the checklist from time to time :) ) 1. Do you have a mailbox in /var/spool/mail/user I'm pretty sure that exim, by default, delivers mail to /var/spool/mail/user. Verify you have a local mailbox. 2. Are you using a smarthost (i.e. you chose option 2 when setting up eximconfig)? If not, what options did you choose? 3. What is your local_hosts variable set to in /etc/exim.conf? I had a goofy problem here; I set my local_hosts var to home.com (the domain my email address is part of) and then could not get any mail out to user's with the same domain because my system thought it was the mailserver for them! Doh! 4. Could you show me/us what your .fetchmailrc file looks like. Don't forget to hide your password when you do! 5. Is you .fetchmailrc file permissions set to 600 (i.e. chmod 600 .fetchmailrc) 6. Do you have procmail set up? Are you using a .procmailrc file? If you use procmail, which many mutt users do for filtering and distributing email, exim will use the rules (procmail calls them recipes) in .procmailrc for handling your mail. 7. Setting up mutt is a whole 'nuther situation...let's get you through retrieving your mail from the server, then we can worry about mutt. rob.jacobs [EMAIL PROTECTED] ~no witty sig required~
Re: fetchmail not communicating with exim.
* Timmy Douglas [EMAIL PROTECTED] [231100 17:08]: I'm using *basically* the same configuration (MTA: exim, MDA: procmail, MUA: mutt POP3-GET-MY-MAIL-WHEN-I-NEED-IT-APP-:] : fetchmail). Maybe I can help? i would use iptables to block port 25 from all but localhost, @home almost killed me for that. they don't allow any ``servers'' i think in their aup thing. I'm working on it. Just recompiled my kernel the other day to support firewalling but haven't had time to work on the iptables and other configuration issues. @home is way too broad in their description of server. I understand that their intent is to limit bandwidth since it is a shared resource but their one-size-fits-all policy is ridiculous. I must have spent the better part of an hour arguing with them and explaining that I wasn't a home business and did not need their @work services but that I had some unusual needs as a programmer -- like wanting to run a webserver on my own machine for use by myself and a small group of others for development only! Before anyone says it, I would have gone DSL but I can't get it where I am... the switches are setup for it yet. Sucks. They would not go for it. They were especially not helpful after I, point blank, told them that their policy only served to conserve bandwidth for use by teenagers pirating software, stolen music and porn. Hmmm...maybe I shouldn't have told them that, huh? :) Does nay one have any idea a how I can rectify this problem? Also if fetchmail is not transferring mail to exim where is it putting it? Again, my understanding is that fetchmail does not put mail anywhere; it just makes sure that mail it is grabbing is placed into the SMTP stream for exim to pick up. 6. Do you have procmail set up? Are you using a .procmailrc file? If you use procmail, which many mutt users do for filtering and distributing email, exim will use the rules (procmail calls them recipes) in .procmailrc for handling your mail. 7. Setting up mutt is a whole 'nuther situation...let's get you through retrieving your mail from the server, then we can worry about mutt. you can set up mutt to use pop3 even though the pop3 support isn't great---but it might save you the trouble from getting fetchmail to work. Mutt does have pop3 support, but it isn't very good. I actually found it surprisingly easy to set up fetchmail. I think the issue may be a faulty exim configuration here. rob.jacobs ([EMAIL PROTECTED]) ~no witty sig required~
Re: xinetd and fetchmail
* Robin Collins [EMAIL PROTECTED] [221100 13:54]:
[snip salutations]
RAJ My xinetd.conf only contains one stanza. Here it is:
RAJ service smtp
RAJ {
RAJ socket_type = stream
RAJ protocol= tcp
RAJ wait= no
RAJ user= mail
RAJ server = /usr/sbin/exim
RAJ server_args = -bs
RAJ }
RAJ My inetd.conf file, before I began trying to use xinetd, only
had one
RAJ entry in it. It was:
RAJ smtpstream tcp nowait mail /usr/sbin/exim exim -bs
If this is indeed the contents then you've made a subtle error setting
up the xinetd config, I think you need
server_args = exim -bs
notice the 2nd exim on the line you noted from inetd.
I'm no expert, this may be nothing, but I thought I'd mention it, just
in case :)
Wasn't the problem. I had noticed that yesterday, when I started working on
this issue,
but figured it was nothing; just one of the foibles of how the inetd daemon
reads the
inetd.conf file. Upon your suggestion, I gave it a try and the end result was
still the
same.
Hope you get it working. BTW, I'd be interested to know if you
succeed, I myself am just planning to implement fetchmail and probable
exim, using xinetd would you believe.
This is what I've found out so far...I believe the problem may have something
to do
with RPC services.
First, I noticed that whenever I install or remove inetd, the portmap daemon is
started or stopped, respectively.
The whole reason I got on this xinetd trip was to improve security, so I then
ran
nmap -v localhost with inetd as the internet super-server to see what ports
were
open and I got the following output:
The TCP connect scan took 0 seconds to scan 1511 ports.
Interesting ports on localhost (127.0.0.1):
PortState Protocol Service
22 opentcpssh
25 opentcpsmtp
111 opentcpsunrpc
515 opentcpprinter
793 opentcpunknown
1026opentcpnterm
6000opentcpX11
I confirmed that portmapper was, in fact, up and running by executing a
tidbit from the inetd script in /etc/init.d/inetd.
~$ rpcinfo -u localhost portmapper
portmapper 10 version 2 ready and waiting
Second, I noticed that when I installed or removed xinetd, there was no mention
of
the portmap daemon.
Running nmap -v localhost with the xinetd daemon as the superserver produces
this
listing:
The TCP connect scan took 0 seconds to scan 1511 ports.
Interesting ports on localhost (127.0.0.1):
PortState Protocol Service
22 opentcpssh
25 opentcpsmtp
515 opentcpprinter
793 opentcpunknown
1026opentcpnterm
6000opentcpX11
Note that sunrpc is missing and that the portmapper is not active:
~$ rpcinfo -u localhost portmapper
rpcinfo: RPC: Port mapper failure - RPC: unable to receive
program 10 is not available
Documentation I've looked at seems to indicate that xinetd and portmapper
should
play well together. Oh well...I'll keep you posted.
Suggestions are welcome.
rob jacobs [EMAIL PROTECTED]
~no witty sig required~
SOLVED! Was: (Re: xinetd and fetchmail)
* Me [EMAIL PROTECTED] [221100 12:12]:
Debian Users,
I'm trying to be security conscious. I've heard xinetd is the way to
go when it comes to an internet super-server so I apt-get installed it. Only
problem is that I can't get it to work with fetchmail.
My xinetd.conf only contains one stanza. Here it is:
service smtp
{
socket_type = stream
protocol= tcp
wait= no
user= mail
server = /usr/sbin/exim
server_args = -bs
}
My inetd.conf file, before I began trying to use xinetd, only had one
entry in it. It was:
smtpstream tcp nowait mail /usr/sbin/exim exim -bs
Fetchmail operates fine with inetd. However, whenever I attempt to run
Fetchmail under xinetd, this is the error I get:
16 messages for r.a.jacobs at mail (195121 octets).
reading message 1 of 16 (4048 octets) ..fetchmail:SMTP connect
to localhost failed
fetchmail: SMTP transaction error while fetching from mail
fetchmail: Query Status=10 (smtp)
So...why won't xinetd allow me to fetch my mail? Does this have
anything to do with RPC and how do I fix it?
Your help is greatly appreciated,
robert [EMAIL PROTECTED]
~no witty sig required~
After a lot of swapping back and forth between inetd and xinetd and a lot of
reading on xinetd, I was finally able to solve this problem thanks to a
tidbit in the article What's that, xinetd? by Frederic Raynal.
You can find this article referenced on http://www.xinetd.org homepage or go
directly to http://www.linuxfocus.org/English/November2000/article175.shtml
At the bottom of the Starting with a Riddle section, Mr. Raynal provides the
following warning about combing tcp_wrappers type security (via inetd) and
security the way xinetd handles it.
(This is a direct quote -- Mr. Raynal is French...so his English is not
perfect...but I'm sure you'll get the meaning)
...Since the request is accepted by xinetd, it's sent to the specified
server (here tcpd). Nevertheless, tcpd rejects this connection. Then, we
must have a look at hosts.{allow,deny}. The /etc/hosts.deny file only
contains ALL:[EMAIL PROTECTED], what explains why the request has been
rejected by
the wrapper!
According to the way the server and server_args service lines have been
defined, the wrapper features are still accessible (banner - there's a
banner attribute in xinetd-, spawn, twist, ...). Remember that the
--with-libwrap compilation option only adds access rights control (with
the help of hosts.{allow,deny} files), before xinetd process starts. In
this example we saw that this configuration allows us to continue using
the tcp wrapper features.
This overlapping of features, if it can work, may as well lead to stange
behaviors. To use xinetd together with inetd and portmap, it's much
better to manage a service with only one of these super-daemons.
As soon as I turned off the ALL:ALL entry in my /etc/hosts.deny file, my
problem disappeared. For the meantime, until I read a little more on xinetd,
I'm going to continue using inetd. Hopefully, within a few days, I'll be up
on xinetd.
Here's a summary of my journey with this problem -- (if you care to see it):
=
Problem: Fetchmail refused to get my mail after installing xinetd in place
of inetd
Analysis: Running nmap -v localhost and rcpinfo -u localhost portmap
showed that when inetd was in control the portmapper was
active, ready and waiting. However, when xinetd was in
control, the portmapper was not available.
nmap -v localhost for inetd contained an entry for
sunrpc while xinetd did not. Both super-servers contained
entries for smtp.
Actions: I compared the output of nmap for each superserver.
I compared the output of rcpinfo for each superserver.
I compared the output of running inetd with the
portmapper disabled to running xinetd as is and saw
that the results were the same.
I tried turning the portmapper on (/etc/init.d/portmap start)
while xinetd was running but it failed anyways.
I tried changing the xidentd script in /etc/init.d/ to mirror
the inetd script, replacing direct references to inetd with
xinetd (I was getting desperate! :) )
I read a LOT on xinetd.
Solution: Remove the ALL:ALL entry from /etc/hosts.deny
Reason:Not quite sure (can anyone explain?) but xinetd and inetd
do not like to play
xinetd and fetchmail
Debian Users,
I'm trying to be security conscious. I've heard xinetd is the way to
go when it comes to an internet super-server so I apt-get installed it. Only
problem is that I can't get it to work with fetchmail.
My xinetd.conf only contains one stanza. Here it is:
service smtp
{
socket_type = stream
protocol= tcp
wait= no
user= mail
server = /usr/sbin/exim
server_args = -bs
}
My inetd.conf file, before I began trying to use xinetd, only had one
entry in it. It was:
smtpstream tcp nowait mail /usr/sbin/exim exim -bs
Fetchmail operates fine with inetd. However, whenever I attempt to run
Fetchmail under xinetd, this is the error I get:
16 messages for r.a.jacobs at mail (195121 octets).
reading message 1 of 16 (4048 octets) ..fetchmail:SMTP connect
to localhost failed
fetchmail: SMTP transaction error while fetching from mail
fetchmail: Query Status=10 (smtp)
So...why won't xinetd allow me to fetch my mail? Does this have
anything to do with RPC and how do I fix it?
Your help is greatly appreciated,
robert [EMAIL PROTECTED]
~no witty sig required~
Re: Couple of questions from a recent convert
* Willy Lee [EMAIL PROTECTED] [201100 17:01]: Robert == Robert A Jacobs [EMAIL PROTECTED] writes: * JD Kitch [EMAIL PROTECTED] [181100 14:17]: Does the default install support an SB AWE32 for sound without recompiling the kernel? No the default install does not support SB AWE32. You need to patch the kernel and recompile. If your SB AWE32 is a pnp card, you will need to configure it using the isapnp tools. Hm. When I installed from the CD (potato), I saw and installed the awe_drv module when browsing packages. This apparently placed an awedrv directory in /usr/src, and when I later compiled a kernel, there were the appropriate options in the config step for awe32. The way I did MY install was to select tasks. I didn't browse the packages so I never installed the awe-drv package initially...I had to add the package later. No biggie. Also, the awe_midi module was loaded at boot time from the beginning. And the config.2.2.17 file in /boot seemed to imply that the default kernel had AWE32 module support. I believe it does have AWE32 support...I don't think it is enabled (i.e. the AWE32 module is not compiled and installed unless you choose it from the various selections when you make [menu|x]config Well, let me try running install.sh in the awedrv directory anyway. Shouldn't hurt anything Note that the docs in the awe_drv directory state that one should run make config for the kernel at least once before running install.sh from the awedrv patch directory. These are the instructions I wrote for myself for configuring my own SB AWE32 sound card. Ignore the references to the USR modem. :) Hope they are helpful. Very helpful, thanks. Following compilation, the following modules should be available in the misc category when executing modconf: adlib_card awe_wave opl3 sb sound soundcore soundlow uart401 Now this is very interesting. When I run 'modconf', everything mentioned above shows up, except 'soundcore'! I wonder if this is the reason why everything looks ok in /dev/sndstat with the exception of Installed drivers and Card config: Okay. If it makes you feel any better, I don't have any values in those sections (despite what the Sound and Soundblaster AWE32 HOWTOs show) and my card runs fine. I remember reading those sections and becoming frustrated with my card as well and not knowing what to trust. My card works fine though. Don't go off of the values in those HOWTOs...I would recommend that you locate and attempt to play a few files as specified in the Soundblaster AWE32 HOWTO. If you can play the files, then you've got sound. Here's the kicker. Even though sound may work from the console, it may NOT work from your window manager. In my case, I could play sounds but I had to change a setting in Enlightenment to get it to play sounds for me. 5. Configure the sound modules for use with the kernel: a. modconf b. Configure awe_wave from the misc category with no parameters. c. Configure sb from the misc category and provide the following parameters: io=0x280 irq=9 dma=0 dma16=7 mpu_io=0x300 Won't the particular values here be system-dependent? Yes. They will be system dependent. These are the values for MY system. I got these values from my /etc/isapnp.conf. Check yours...I thought I attached the sound portions of my isapnp.conf file in an earlier post. IIRC, the AWE32 docs mention the fact that the isapnptools do not catch all of the correct values for the WAVETABLE portion generated by pnpdump. Use the values I supplied...they are taken directly from the docs. Ok, I'm recompiling the kernel as I type this. Hopefully soundcore will be available in modconf after it's done and a reboot. Let me know if it works...we'll get you through this! :) rob.jacobs ([EMAIL PROTECTED]) ~no witty sig required~
Re: System.map
* Philipp Schulte [EMAIL PROTECTED] [181100 19:25]: On Fri, Nov 17, 2000 at 10:48:29AM -0600, Jason Holland wrote: You can recreate your System.map by running make install in /usr/src/linux, or wherever your kernel source is that you recently recompiled. Sure he can recreate it this way but he still needs to copy it to the right place. #cp /usr/src/linux/System.map /boot/System.map-your.kernel (same as vmlinuz-your.kernel) Just kinda curious...how important is it to place the new System.map file (created when you compiled a new kernel) in the /boot directory? I have compiled a number of kernels and, after looking at this discussion, I checked my /boot directory to see if I had moved my System.map file after the last compile. I have not. I have noticed no ill effects. What potential problems am I opening myself up to here? rob jacobs r.a.jacobs ~no witty sig required~
Re: Couple of questions from a recent convert
* JD Kitch [EMAIL PROTECTED] [181100 14:17]:
Does the default install support an SB AWE32 for sound without
recompiling the kernel?
No the default install does not support SB AWE32. You need to
patch the kernel and recompile. If your SB AWE32 is a pnp card,
you will need to configure it using the isapnp tools.
References: Sound HOWTO
Soundblaster AWE HOWTO
These are the instructions I wrote for myself for configuring my own
SB AWE32 sound card. Ignore the references to the USR modem. :)
Hope they are helpful.
Kernel Configuration Notes:
Make sure the following kernel modules are selected when you make menuconfig
Prior to configuring the kernel be sure to patch it with the awe-drv package:
apt-get install awe-drv
cd /usr/src/awedrv
./install.sh
Sound
m Sound Card Support
m OSS Sound Modules
m 100% Soundblaster Compatibles
m FM Synthesizer (YM3812/OPL-3) Support
Additional Low-Level Sound Drivers --
m AWE32 Synth
##
## Sound Notes
##
Note 1: The Kernel must be compiled with the appropriate sound modules
selected. Prior to compiling the kernel, be sure to patch it
with the awedrv source code.
Following compilation, the following modules should be available
in the misc category when executing modconf:
adlib_card
awe_wave
opl3
sb
sound
soundcore
soundlow
uart401
Configuring (i.e. starting) the sb module will start sound,
soundcore, soundlow, and uart401 (see Step 5).
Configuring the adlib_card module will start opl3 (see Step 5).
Note 2: Save yourself a lot of headaches and create (pnpdump) and modify
/etc/isapnp.conf once. That is, modify it for all your ISA PNP
devices at the same time. Right now, that means your USR modem, if
it is installed.
1. Become Root
2. mv /etc/isapnp.conf /etc/isapnp.conf.old (see Note 2)
3. pnpdump /etc/isapnp.conf (see Note 2)
4. modify /etc/isapnp.conf sound card entries to read (see Note 2):
#SB AWE64 16-Bit Audio Configuration
(CONFIGURE CTL00c5/18864389 (LD 0
(INT 0 (IRQ 9 (MODE +E)))
(DMA 0 (CHANNEL 0))
(DMA 1 (CHANNEL 7))
(IO 0 (SIZE 16) (BASE 0x0280))
(IO 1 (SIZE 2) (BASE 0x0300))
(IO 2 (SIZE 4) (BASE 0x0388))
(NAME CTL00c5/18864389[0]{AUDIO })
(ACT Y)
))
#SB AWE64 Gameport Configuration
(CONFIGURE CTL00c5/18864389 (LD 1
(IO 0 (SIZE 8) (BASE 0x0200))
(NAME CTL00c5/18864389[1]{GAME })
(ACT Y)
))
#SB AWE64 Wavetable Configuration
(CONFIGURE CTL00c5/18864389 (LD 2
(IO 0 (SIZE 4) (BASE 0x0620))
(IO 1 (SIZE 4) (BASE 0x0A20))
(IO 2 (SIZE 4) (BASE 0x0E20))
(NAME CTL00c5/18864389[2]{WAVETABLE })
(ACT Y)
))
5. Configure the sound modules for use with the kernel:
a. modconf
b. Configure awe_wave from the misc category with no parameters.
c. Configure sb from the misc category and provide
the following parameters:
io=0x280 irq=9 dma=0 dma16=7 mpu_io=0x300
When sb is loaded, it will call sound, soundlow,
soundcore and uart401
d. select adlib_card from the misc category and provide
the following parameters:
io=0x388
When adlib_card is loaded, it will call opl3
6. Add users to the audio group
adduser username audio
7. Reboot
rob jacobs [EMAIL PROTECTED]
~no witty sig required~
Re: Simple apt-get question
* Sean 'Shaleh' Perry [EMAIL PROTECTED] [171100 17:16]: I installed PostgreSQL to work with, and I noticed that it said that it was version 6.5 or so, and to just grab the newer package from the unstable tree. So my question is, how do I go about grabbing just _one_ package, and of course, any dependencies (as few as possible, I hope. I have a very slow dial-up connection) from the unstable branch when my /etc/apt.sources.list is set up for the stable tree? you don't. If you want an unstable package you either: a) upgrade to unstable b) grab the source from unstable and compile it yourself. This is fairly painless these days. grab the orig.tar.gz, the dsc and the diff.gz file. do dpkg-source -x foo.dsc. cd foo-ver. Look in debian/control. If there is a Build-Depends line, install any packages listed there. Make sure you have fakeroot installed. Then do dpkg-buildpackage -rfakeroot -us -uc -tc. I'm fairly new to Debian as well...but I run a few packages from unstable and I did not upgrade to unstable. All I did was add the following line to my sources.list: deb ftp://ftp.debian.org/debian unstable main contrib non-free I only use this line when I want to get one or two packages. Most of the time I keep it commented out so Apt ignores it. Do: apt-get update apt-get -s install the package you want -s simulates an install so you can see what apt is gonna do. If you are okay with its actions, re-run the command without the -s apt-get install the package you want rob jacobs [EMAIL PROTECTED] ~no witty sig required~
Re: SB AWE64 configuration problem
* Willy Lee [EMAIL PROTECTED] [181100 10:43]: Willy == Willy Lee [EMAIL PROTECTED] writes: Regarding the problems I'm having with getting sound to work, I found a clue. Now if I only knew what it meant! This is what syslog says after attempting to modprobe to load the sound modules: Nov 18 03:07:16 geldar modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.17/modules.dep Not sure what this problem is but I've seen a lot of people who have had it. Type: depmod -a to fix it. See my reply to JD Kitch in the Couple of questions from a recent convert thread for detailed instructions on how I got my SB AWE64 working. Maybe you can glean some solutions from there. rob jacobs [EMAIL PROTECTED] ~no witty sig required~
Re: insmod: Note: /etc/modules.conf is more recent than /lib/modules/2.2.17/modules.dep
* Erik Steffl [EMAIL PROTECTED] [251000 18:09]: tjm wrote: Hello, I have had the same problem although it doesn't seem to cause any adverse condition with the machine. The startup script /etc/rcS.d/S20modutils (/etc/init.d/modutils) runs depmod -a when the machine boots, but it seems that the time stamp that results from the new modules.dep file being made is incorrect. It appears that the date is ok but the time is not, making it appear the modules.dep file may be older than modules.conf. If I run depmod -a after the machine is up and running, the time/date stamp on the modules.dep file is correct. Maybe the system time that is used when the startup script is run is not correct until later in the boot process, but I don't know enough of this to make changes safely. Try changing the time/date of the modules.conf back a couple days by using 'touch' or remaking the file (update-modules) after turning the system time back temporarily to see if it makes a difference. A proper solution would be much nicer, though. I tried that but the problem seems to be that the modules.conf is updated during boot process (looking and date/time of the file), and modules.dep is not (or is updated sooner)... well, at least I see I am not alone... does this look like a bug? last time I checked there was no bug filed, but I have hard time to figure out which package the bug would be filed for... I've had the same problem as well...same effect (i.e. none) I am also running Debian 2.2 (Potato) with the 2.2.17. I have also witnessed at least 1 person coming into #debian on IRC complaining about this problem In addition to the suggestions already put forth for fixing this error, I attempted to fix this error by recompiling my kernel and modules using make (not kernel-package) and clearing my /lib/modules/2.2.17 directory before issuing make modules-install. That didn't really solve the problem and since there appeared to be no problems I gave up for the time being and figured I would look into the situation at a later time. Then, magically, the problem went away. I stopped getting the error messages and everything seemed to work. I filed it away, again, as a mystery I would explore later. Good to see that there seems to be a pattern out there, though.
Delete Me -- Just a Test sorry
Just a test message...had some problems with my procmail recipes and this post is just to see if I've got them straightened out. Sorry for any inconvenience. Thanks. rob jacobs
Re: insmod: Note: /etc/modules.conf is more recent than /lib/modules/2.2.17/modules.dep
* Erik Steffl [EMAIL PROTECTED] [251000 18:09]: tjm wrote: Hello, I have had the same problem although it doesn't seem to cause any adverse condition with the machine. The startup script /etc/rcS.d/S20modutils (/etc/init.d/modutils) runs depmod -a when the machine boots, but it seems that the time stamp that results from the new modules.dep file being made is incorrect. It appears that the date is ok but the time is not, making it appear the modules.dep file may be older than modules.conf. If I run depmod -a after the machine is up and running, the time/date stamp on the modules.dep file is correct. Maybe the system time that is used when the startup script is run is not correct until later in the boot process, but I don't know enough of this to make changes safely. Try changing the time/date of the modules.conf back a couple days by using 'touch' or remaking the file (update-modules) after turning the system time back temporarily to see if it makes a difference. A proper solution would be much nicer, though. I tried that but the problem seems to be that the modules.conf is updated during boot process (looking and date/time of the file), and modules.dep is not (or is updated sooner)... well, at least I see I am not alone... does this look like a bug? last time I checked there was no bug filed, but I have hard time to figure out which package the bug would be filed for... I've had the same problem as well...same effect (i.e. none) I am also running Debian 2.2 (Potato) with the 2.2.17. I have also witnessed at least 1 person coming into #debian on IRC complaining about this problem In addition to the suggestions already put forth for fixing this error, I attempted to fix this error by recompiling my kernel and modules using make (not kernel-package) and clearing my /lib/modules/2.2.17 directory before issuing make modules-install. That didn't really solve the problem and since there appeared to be no problems I gave up for the time being and figured I would look into the situation at a later time. Then, magically, the problem went away. I stopped getting the error messages and everything seemed to work. I filed it away, again, as a mystery I would explore later. Good to see that there seems to be a pattern out there, though. rob jacobs
Re: Problem with desktop icons
This is probably an obvious question, but: Did you save your session after making changes to it? * Casey Henderson [EMAIL PROTECTED] [241000 17:22]: I have a weird problem in GNOME. The icons for my desktop shortcuts keep changing back to the default icon (a piece of paper) for no reason. I didn't do anything (that I'm aware of) to change the icons, they just all got reset by themselves. When I try to change them, it won't work. I right click an icon, go to Properties, and choose an icon and hit OK, and it doesn't work. This is not the first time this has happened. I have done a clean reinstall of Debian 2.2 from the CD's, and I still get the problem. Is this a bug in the version of GNOME that comes on the CD's? Does anybody know how to fix this?? Thanks.
