Re: Configuration errors using tor, privoxy polipo
On 05/16/2010 03:35 AM, AG wrote: Using Iceweasel, I enable the tor button and receive a warning message Tor proxy test: local HTTP proxy is unreachable. Is polipo running properly? Well, no because polipo wasn't installed - why and when this suddenly became a necessity I don't know, but anyway I installed polipo and configured it according to the tutorial on http://wiki.archlinux.org/index.php/Polipo which, in my circumstances, required me to uncomment this line in the config file: ... From researching this on the web, I am unable to ascertain whether or not I even need polipo, but the preferences settings tab for the tor button have a check-box for using polipo, so it appears as if tor is now expecting polipo to be installed and running as default. But, I have now reached the limit of what I know what to do or can figure out. I am also conscious of the risk of screwing things up further in an effort to fix this, so before proceeding further would like to ask this list for help and advice. I think it's polipo that you need, and privoxy that you don't need. If you look here http://www.torproject.org/docs/tor-doc-unix.html.en I think you'll probably find the information you need. There's a link on that page to a polipo configuration file that you can use for replacing the one that gets created when you install polipo from the repositories. I could be mistaken about this, but I think that you need to remove privoxy from the system -- or at least make sure that it is not running. Sam -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4befdc66.7070...@comcast.net
Re: Switching from NV to Nouveau in Squeeze
On 05/11/2010 09:43 PM, Charles Kroeger wrote: Saw that xserver-xorg-video-nouveau package is now in the main repository. It does not appear to be in Sid or Squeeze as of this afternoon. (EST USA) yes. However, I notice that 'nv' is still in Squeeze-main contrib non-free: xserver-xorg-video-nv 1:2.1.17-2 Sorry. I'm not thinking or communicating well. I'm using the vesa driver on the system, not nv. My brain was tracking back to an earlier experiment in which I was using other repositories. I use only main and security for Squeeze. However, I have been showing xserver-xorg-video-nouveau in Squeeze main for a couple of days. but nv appears to be 'broken' if used in the /etc/X11/xorg.conf file, on my version of things. Perhaps this is the result of some Debian religious fanatics, but I think it's time to bid adeau to nv, alas it served me well. I installed nouveau: xserver-xorg-video-nouveau 1:0.0.15+git20100329+7858345-3 X.Org X server -- Nouveau display driver (experimental) and placed it, instead, into the /etc/X11/xorg.conf file and lo it brought forth an X session and looked just like nv. But, nv and nouveau are, no pun intended, a bit two dimensional when one still has available the nvidia-glx Xorg driver one should simply use it if one's hardware will comply. Too rich for my blood. By that I mean that nvidia-glx with this Quadro card has caused all sorts of odd breakages and unreliability issues in the DE. I have done enough experimenting with identical configurations of Xfce and Gnome on this system, with the only difference being use of different video drivers (vesa, nv, glx/restricted) under both Ubuntu and Debian to know that it's not my imagination. I'd rather have a reliable system than 3D, so glx is a no go for me. The vesa driver has been absolutely flawless, but quite slow, of course. The slowness has been worth it because absolutely nothing in the user interface has ever been broken since I went to vesa. I don't game, and I've just learned to be patient when switching workspaces. ;) I'm looking forward to seeing if nouveau will be an improvement, performance-wise, without causing reliability issues. I am, however, going to wait and install nouveau the easy way, once the upgrade to xserver-xorg-core becomes available in the repository. If this weren't my main system I might be tempted to experiment, but I just need this thing to keep working. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bea95b5.2080...@comcast.net
Re: Switching from NV to Nouveau in Squeeze
On 05/12/2010 08:08 AM, Mark Allums wrote: On 5/12/2010 6:49 AM, Snood wrote: I'm looking forward to seeing if nouveau will be an improvement, performance-wise, without causing reliability issues. I am, however, going to wait and install nouveau the easy way, once the upgrade to xserver-xorg-core becomes available in the repository. If this weren't my main system I might be tempted to experiment, but I just need this thing to keep working. People running non-stable (even squeeze) are going to run into problems now and then. It's an unavoidable certainty. nouveau is, well, new. There are going to be problems with it. Of course. But the problems I had with Gnome and Xfce on this system occurred not only in Squeeze, but also when running an Ubuntu LTS version and Debian Stable. I only saw those problems when using the restricted / glx drivers. Never with nv or vesa. I think this is, perhaps, more a measure of the card itself than the drivers. But I know a number of people with high end graphics cards from nvidia who have reported the same sorts of issues that I saw. It doesn't really matter much as these particular systems are no longer used as graphics workstations. As they've aged we stuck Linux on them and use them as admin workhorses, a job for which they are admirably suited because of all of the screen real estate. Regarding reliability of video drivers: Running many different things, hardware- and driver-wise, over time, I have learned that dpkg-reconfigure is your friend, especially dpkg-reconfigure linux-image-2.6.32-5 which regenerates the initrd.img. (I needed this recently. Substitute the package name of your kernel.) Occasionally very helpful, that, when troubleshooting drivers. Yes. In my earlier experiences I would just wipe the drive and start over when I suspected that hangovers from previous experiments with drivers were getting in the way of new configurations. But after I became comfortable with a few different methods of installation and initial configuration I started paying attention to things like dpkg-reconfigure and debconf-show. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4beab6c8.2070...@comcast.net
Switching from NV to Nouveau in Squeeze
Did some research on Nouveau drivers. Was about to download, compile, etc. Saw that xserver-xorg-video-nouveau package is now in the main repository. Does that mean that going through all the machinations is no longer necessary? If I tell aptitude (ncurses) to install the package it also indicates the need to install libdrm-nouveau1, but there's no sign that it's actually going to switch the system from nv to nouveau. I've looked for information, but I must be looking in all the wrong places. All I can find is information about how to install nouveau the old way. Can someone point me in the right direction? Thanks, Sam -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4be97290.7010...@comcast.net
Re: Re: Switching from NV to Nouveau in Squeeze
On 01/-10/-28163 02:59 PM, Sven Joachim wrote: On 2010-05-11 17:06 +0200, Snood wrote: Did some research on Nouveau drivers. Was about to download, compile, etc. Saw that xserver-xorg-video-nouveau package is now in the main repository. Does that mean that going through all the machinations is no longer necessary? Yes, that does it mean. Very nice. I love surprises like this. It's why I use Squeeze. If I tell aptitude (ncurses) to install the package it also indicates the need to install libdrm-nouveau1, but there's no sign that it's actually going to switch the system from nv to nouveau. This will happen with the next upload of xserver-xorg-core. Till then, you need a minimal xorg.conf to use nouveau. And a kernel from sid. Very interesting. I guess I'm going to be tempted to await the xserver-xorg-core package upgrade. I have been astonished at how reliable Squeeze has been -- despite the fact that I have unfailingly accepted every single upgrade offered without flinching (main and security repositories only). I'm reluctant to mix unstable and testing bits on my primary system. But I may decide to become brave if the wait is long. I've looked for information, but I must be looking in all the wrong places. All I can find is information about how to install nouveau the old way. Can someone point me in the right direction? Consult the README.Debian in the xserver-xorg-video-nouveau package, it hopefully contains all necessary information. Man, am I a dummy! For some reason I forgot that there are README files in these packages. I was looking for man pages and write-ups in the wikis and stuff. Good luck, Sven Many thanks for your extremely helpful post! Best, Sam -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4be9ac17.6090...@comcast.net
Re: Re: Switching from NV to Nouveau in Squeeze
On 01/-10/-28163 02:59 PM, Kelly Clowers wrote: I don't have Nvidia myself, but tt should be a matter of installing Nouveau, and then changing the Driver line in /etc/x11/xorg.conf from nv to Nouveau (or adding the line in the Device section if it doesn't exist). Good old /etc/X11/xorg.conf. There isn't one on this system. I used to hate fiddling around with that file. The transition to other means of controlling video has been fraught with peril for some, but a few false starts with video configuration on this system under various distributions finally convinced me that the voyage needed to be undertaken. Cheers, Kelly Clowers Many thanks for your response. Best, Sam PS: I also sent this message from a different e-mail account. I figured I'd resend it to clear up any question about who was actually responding to the thread. Sorry about the dumbness. Too much swapping of systems and info around this place. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4be9ad52.2060...@comcast.net
Re: Mailing list policy change?
On Fri, Mar 19, 2010 at 09:17:56AM -0400, Stephen Powell wrote: Does this mean that it is OK to CC people now, without a CC being requested? Or do many people read the list via the web interface to the mailing list archives without being subscribed and will still get annoyed if they are CCed? I need some guidance here. There have been a number of times that I have not CCed people because they didn't explicitly ask for it, but because they thought their problem was now solved, they were not looking at the list anymore and therefore didn't see my follow-up post offering a correction to an earlier mistake, etc. I don't want people to miss posts because they aren't looking. But neither do I want to annoy people. It is policy not to CC unless explicitly requested, but sometimes discretion is called for. If a poster is obviously a newbie (you can usually tell by the content but also if the poster has not posted before.) it shouldn't hurt, although this is fairly rare. A lot of other lists CC on principle. The argument being that it is more important that the recipent receive the message in a timely manner (they may be subscribed to several mailing lists and not read them as often as their personal mail. I'm afraid I messed up repeatedly on this when I made my first posts to this list. Between the number of different sets of preferences amongst the newsgroups to which I'm subscribing and getting used to a new mail client (went from Claws to Icedove) I'm probably causing a lot of disruption. (Hope I did it right this time.) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ba4e891.6070...@comcast.net
Re: aptitude lists linux-image-2.6.32-trunk-686 under Obsolete and Locally Created Packages?
Andrei Popescu wrote: In general I prefer to keep at least one different kernel version installed, Just In Case, but in this particular case I too did get rid of the -trunk- image ASAP because: - it shouldn't have been uploaded to unstable in the first place - it messes up the usual boot order (the most recent kernel first) - I have enough kernels installed ;) Though my reasoning was not as well-ordered as yours, the second reason you list was bouncing around in my fuzzy little brain. I figured that, if it was going to behave like that, I was going to give it the ax. Thank you for reminding me earlier to check /boot/grub/grub.cfg. That plus what I was seeing in aptitude helped me to realize how odd the situation was. At least, it was something that I had never seen before. I had basically two different odd (at least to me) scenarios going on among these four systems. Even the one that actually had the new kernel wasn't going to benefit from it if grub wasn't going to use it! Thanks and regards, Sam -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9f7652.8000...@comcast.net
aptitude lists linux-image-2.6.32-trunk-686 under Obsolete and Locally Created Packages?
Following a slew of updates in Debian testing this morning I noticed that linux-image-2.6.32-trunk-686 (2.6.32-5) is listed by aptitude as being obsolete. I suppose the update that resulted in this was probably firmware-linux-free 2.6.32-5 - 2.6.32-9 I've never seen anything like this before. (I admit I've only been using Debian for about a year.) Is this indication an unusual one? Is there any sort of corrective action I should be taking? I'm seeing it on four Squeeze installations, so I'm guessing that other people are seeing it, too. Thanks, Sam -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9e773d.4080...@comcast.net
Re: aptitude lists linux-image-2.6.32-trunk-686 under Obsolete and Locally Created Packages?
Stephen Powell wrote: Sam wrote: Maybe I don't understand how aptitude works for this case. From everything I can see, if I remove the kernel that aptitude lists as obsolete, I won't have any kernel at all. First of all, you replied to me personally instead of to the list. I'm putting this back on the list where it belongs. If you have already done the upgrade, you should have two kernel image packages installed: linux-image-2.6.32-3-arch and linux-image-2.6.32-trunk-arch. If you wish to purge the old kernel, shutdown and reboot first. This will cause the new kernel to be booted. Then you can purge the old one. aptitude will not let you purge or remove a running kernel. Oh, rats. I was in a rush to post and forgot the way the list works. I wish that all the lists to which I subscribed behaved the same. Thanks for helping me out. I made several replies the same way, darnitall. I know about rebooting and purging. I've done it lots before. It's not working that way in this case. Honestly. There's just no evidence that I can find that there's more than one kernel to select from. In fact, there's not even any evidence at all that there was any kernel upgrade on the three machines that had the initial OS installation done with the trunk kernel install option. On the other system, I can see that a new linux-image package was installed. But there's only one choice of kernels at boot time. And any attempt on any of these systems to remove the obsolete kernel results in the warning that the only kernel is being removed. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9eabc5.1000...@comcast.net
Re: aptitude lists linux-image-2.6.32-trunk-686 under Obsolete and Locally Created Packages?
Wayne wrote: Snood wrote: dpkg -l linux-image |grep ^i will show you that the version, -3, changed. The name did not. Wayne That command results in nothing at all on my system. Is that significant? No, because, stupid me, forgot to type it correctly. Try this dpkg -l linux-image* |grep ^i The wildcard * tells it to check for all the linux-image files The |grep ^i means -- only show packages that have 'i' in the first column, which means show only the installed packages. This list code of conduct discourages sending personal mail. I am including the list in the cc so other users may benefit from your question. Please ask questions on the list and not directly to members. Thank you Wayne Yes, sorry. I've got to get my head on straight today. I just joined this list and forgot about the differences. Some mung, and some don't. Output from dpkg -l linux-image* |grep ^i was: ii linux-image-2.6.32-trunk-686 2.6.32-5 Linux 2.6.32 for modern PCs -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9ebe81.3000...@comcast.net
Re: aptitude lists linux-image-2.6.32-trunk-686 under Obsolete and Locally Created Packages?
Andrei Popescu wrote:
On Mon,15.Mar.10, 17:51:01, Snood wrote:
I know about rebooting and purging. I've done it lots before. It's
not working that way in this case. Honestly. There's just no
evidence that I can find that there's more than one kernel to select
from. In fact, there's not even any evidence at all that there was
any kernel upgrade on the three machines that had the initial OS
installation done with the trunk kernel install option. On the other
system, I can see that a new linux-image package was installed. But
there's only one choice of kernels at boot time. And any attempt on
any of these systems to remove the obsolete kernel results in the
warning that the only kernel is being removed.
Please post your /boot/grub/grub.cfg
Regards,
Andrei
/boot/grub/grub.cfg contents below:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 8ccd4845-705a-4e92-98e2-7129fb7b9cda
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
set locale_dir=/boot/grub/locale
set lang=C.UTF-8
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 8ccd4845-705a-4e92-98e2-7129fb7b9cda
insmod png
if background_image
/usr/share/images/desktop-base/moreblue-orbit-grub.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, with Linux 2.6.32-trunk-686 {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 8ccd4845-705a-4e92-98e2-7129fb7b9cda
echoLoading Linux 2.6.32-trunk-686 ...
linux /boot/vmlinuz-2.6.32-trunk-686
root=UUID=8ccd4845-705a-4e92-98e2-7129fb7b9cda ro quiet
echoLoading initial ramdisk ...
initrd /boot/initrd.img-2.6.32-trunk-686
}
menuentry Debian GNU/Linux, with Linux 2.6.32-trunk-686 (recovery mode) {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 8ccd4845-705a-4e92-98e2-7129fb7b9cda
echoLoading Linux 2.6.32-trunk-686 ...
linux /boot/vmlinuz-2.6.32-trunk-686
root=UUID=8ccd4845-705a-4e92-98e2-7129fb7b9cda ro single
echoLoading initial ramdisk ...
initrd /boot/initrd.img-2.6.32-trunk-686
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply
type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4b9ebf41.4090...@comcast.net
Re: aptitude lists linux-image-2.6.32-trunk-686 under Obsolete and Locally Created Packages?
Wolodja Wentland wrote: On Mon, Mar 15, 2010 at 17:51 -0400, Snood wrote: Stephen Powell wrote: Sam wrote: First of all, you replied to me personally instead of to the list. I'm putting this back on the list where it belongs. Same happened here. If you have already done the upgrade, you should have two kernel image packages installed: linux-image-2.6.32-3-arch and linux-image-2.6.32-trunk-arch. If you wish to purge the old kernel, shutdown and reboot first. This will cause the new kernel to be booted. Then you can purge the old one. aptitude will not let you purge or remove a running kernel. I know about rebooting and purging. I've done it lots before. It's not working that way in this case. Honestly. There's just no evidence that I can find that there's more than one kernel to select from. In fact, there's not even any evidence at all that there was any kernel upgrade on the three machines that had the initial OS installation done with the trunk kernel install option. On the other system, I can see that a new linux-image package was installed. But there's only one choice of kernels at boot time. And any attempt on any of these systems to remove the obsolete kernel results in the warning that the only kernel is being removed. It would be great, if you could provide us with the output of the following commands: # aptitude search ~i~n^linux-image # apt-cache policy linux-image-2.6.32-3-686 It is quite likely that you have indeed two packages installed, namely linux-image-2.6.32-3-686 and linux-image-2.6.32-trunk-686. The latter is no longer present in the archives and therefore obsolete. We can see that linux-image-2.6.32-3-686 is in testing: $ rmadison linux-image-2.6.32-3-686 linux-image-2.6.32-3-686 | 2.6.32-9 | testing | i386 linux-image-2.6.32-3-686 | 2.6.32-9 | unstable | i386 so you should have installed it. That assumes that you have a kernel meta-package installed, which depends on the current package that provides the newest kernel. That meta-package is probably linux-image-2.6-686. It has already been pointed out in this thread that this kernel update did, in contrast to previous updates, not select the kernel provided by linux-image-2.6.32-3-686 as default kernel for grub. I therefore think that the warning you get is not due to the fact that you have only one kernel installed, but rather that you are trying to remove the kernel *you are currently using*, because you booted into the old kernel. If you really have only one kernel package installed, I would suggest to install the aforementioned meta-package or linux-image-2.6.32-3-686, reboot and remove/purge linux-image-2.6.32-trunk-686. Please provide the complete output of any command that gives errors. Output of # aptitude search ~i~n^linux-image is i linux-image-2.6.32-trunk-686- Linux 2.6.32 for modern PCs Output of # apt-cache policy linux-image-2.6.32-3-686 is linux-image-2.6.32-3-686: Installed: (none) Candidate: 2.6.32-9 Version table: 2.6.32-9 0 500 http://ftp.us.debian.org squeeze/main Packages Thank you. I'm sorry about mixing up my replies. I'm new here and have been used to working with lists which mess around with the reply to behavior. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9ec0ec.5000...@comcast.net
Re: aptitude lists linux-image-2.6.32-trunk-686 under Obsolete and Locally Created Packages?
Wolodja Wentland wrote: Ok - You really have only one linux-image-* package installed and you've installed it directly, i.e. it was not installed as a dependency of a meta-package. Yes, I think I understand. I used a netinst disc to install the operating system. In Lenny installed via netinst I got kernel updates. Does it not work that way in Squeeze? Very Good. I would suggest that you install linux-image-2.6-686 or linux-image-686, which depend on linux-image-2.6.32-3-686. That way you will get kernel updates in the future and don't run into this mess again. You can then reboot into the new kernel and remove the obsolete linux-image-2.6.32-trunk-686 package. Thank you. I did this, rebooted into the new kernel, used aptitude to remove the old one, and removed the obsolete kernel. Everything is ticking along nicely. You might also want to trim your posts and interleave your answers. Welcome to the list. :) Yes, I should have known that, too. I read it when I joined initially, and then got rushed whilst trying to do several things at once. Thank you for the welcome. And thank you for the very good advice. Best regards, Sam -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9ecbe2.1030...@comcast.net
