Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Congratulations. This browser is configured to use Tor.
Your IP address appears to be: [xxxxxxxxx]
However, it does not appear to be Tor Browser.
Click here to go to the download page
That's great to hear, Rosika, although it's not yet working in all the cases where you want it to.
Let me return to a previous topic if I may, i.e. Install-Recommends (*I'm* doing some housekeeping now ). It turns out that there is a good reason that 99synaptic exists - it's the configuration that Synaptic Package Manager uses to change's APT's behaviour and, lo and behold, Synaptic allows you to decide whether or not to treat recommended packages as dependencies (Settings->Preferences->Consider recommended packages as dependencies). I don't use Synaptic which is why I didn't know about this.
So, when you choose that option, Synaptic inserts APT::Install-Recommends "1"; into /etc/apt/apt.conf.d/99synaptic. At some point, you must have chosen this setting.
The upshot is that now you have 99znorecommend in place, this will always override the APT::Install-Recommends setting in 99synaptic (not the other settings as priority is given on a setting by setting basis). So, checking or unchecking this option in Synaptic will have no effect.
The solution is therefore to remove /etc/apt/apt.conf.d/99znorecommend as root and then control the Install-Recommends setting through Synaptic.
thanks you so much for letting me be part of your insights. Thatīs very thoughtful of you.
As Iīm very keen on learning as much as possible about how Linux works Iīm very interested in this.
And yes, that makes perfect sense.
The thing is: in most cases I install packages via terminal-commands, too. Rather seldom do I use sysnaptic either.
Well, I removed the respective file with
Code:
sudo rm /etc/apt/apt.conf.d/99znorecommend
and
Quote:
ls -la /etc/apt/apt.conf.d
is back to the state of post #10.
Fine, now I understand how I can synaptic get to work the way I want. Tnx a lot.
I got it. I checked the torsocks debug message, I see the following.
[listen] Non localhost inbound connection are not allowed. (in tsocks_listen() at listen.c:64)
And I changed my code to listen on localhost only, problem resolved.
Well, I wonder if thatīs the case with me, too.
Because when trying to open a file with audacious, vlc or rhythmbox I get
Code:
[Jun 13 13:46:57] WARNING torsocks[5]: [syscall] Unsupported syscall number 204. Denying the call (in tsocks_syscall() at syscall.c:465)
To be clear:
Rhythmbox now plays radio-stations. I.e. internet-connection is working.
But trying to play a locally installed musc-file results in that never-ending loop of error-messages.
Therefore I was thinking along the lines of localhost inbound connection
Iīd rather not do that.
Remember what Turbocapitalist said in the beginning:
Quote:
If you use a bare 'make all && sudo make install' approach, you will eventually mess up your system enough that a fresh re-installatino of the whole OS is needed.
(post #4).
Iīm glad I could uninstall that one and replace it with the apt-installation.
Better safe than sorry.
Well, at least some things work.
So Iīd say letīs give up for now. I learned a lot and we achieved a lot, it has to be said.
I cannot thank you enough. Thinking of all the time and effort you spent helping me.
Iīd rather not do that.
Remember what Turbocapitalist said in the beginning:
(post #4).
Iīm glad I could uninstall that one and replace it with the apt-installation.
Better safe than sorry.
Well, at least some things work.
So Iīd say letīs give up for now. I learned a lot and we achieved a lot, it has to be said.
I cannot thank you enough. Thinking of all the time and effort you spent helping me.
So thanks again.
Greetings
Rosika
Ok, your decision. I think you're wrong about the manual installation though. Some people think that you should restrict yourself to software in the repos or in packages - I'm not one of them. And, if you're going to be one of them, I would highly recommend that you upgrade to Ubuntu 18.04 so that you can avail yourself of the more up-to-date software it provides, including one torsocks 2.2.0.
If you are compiling it from the git repository, run ./autogen.sh before the
configure script.[/CODE]
was given in the readme-file. Running that sequence shouldnīt be dangerous.
That got me thinking.
I'd second the recommendation to try 18.04 if you want a newer version of torsocks because there is nothing in the backports repository for 16.04.
Again, if you do not use the repository's version, at least roll your own package so that the files involved can be tracked and removed or updated when needed. By not updating via the repository you are also committing to following the security announcements daily and re-compiling when alerts are published. It's more time effective, IMHO, to use the repositories. Usually the packagers get a heads up and the update is ready to go by the time the information embargo is lifted and the general public (that's us) finally get informed that it's time to update.
I have to add: Prsonally I really donīt care much about how a package is installed. Be it manually, via apt, or if itīs a snap or an appimage.
Yet Turbocapitalistīs warning really frightened me.
Why on earth would I
I mean the instruction
Code:
$ ./configure
$ make
$ sudo make install
If you are compiling it from the git repository, run ./autogen.sh before the
configure script.
was given in the readme-file. Running that sequence shouldnīt be dangerous.
That got me thinking.
Without wanting to get into a argument with TC, you shouldn't be frightened. All you need to do is exercise some common sense, as with everything in life, and it isn't dangerous. Especially if you make a system image/backup/snapshot before you do a significant amount of fiddling about, which I assume you're doing already (if not, do it). In the rare case that something goes wrong, you can just roll back to where you were beforehand.
My priority list for new software is as follows:
. Install from the repos.
. Install from a PPA.
. Install from a deb package.
. Run a portable program.
. Use an installer script.
. Build and install.
There is a place for all of these, and in fact if you run an LTS and you want to keep abreast of the game then you can't depend purely on software from the repos.
Thanks for your recommendations. Iīll look into the whole matter.
@ hydrurga:
Tnx.
Yes, I perform a backup on a regular basis. Once a month (mostly ) I make a system-backup using clonezilla.
Your priority list looks very reasonable.
As already said, Iīll look into the various ways of updating programmes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
). It turns out that there is a good reason that 99synaptic exists - it's the configuration that Synaptic Package Manager uses to change's APT's behaviour and, lo and behold, Synaptic allows you to decide whether or not to treat recommended packages as dependencies (Settings->Preferences->Consider recommended packages as dependencies). I don't use Synaptic which is why I didn't know about this.
