| |  | | | |  | |
May 22nd, 2006, 08:16 AM
|
#11 | | Professional Member | where can i getan ad blocker like that?
it sounds great
__________________ no matter what you'll ask of me - all you'll get is a Zubi |
| |
May 22nd, 2006, 09:00 AM
|
#13 | | Professional Member | it don't have a linux version 
__________________ no matter what you'll ask of me - all you'll get is a Zubi |
| |
May 22nd, 2006, 11:57 AM
|
#14 | | Banned | doesn't linux have a host file? |
| |
May 22nd, 2006, 12:18 PM
|
#15 | | Banned | apparently it does.
search in the system32/driver/ect/ folders or equivalent |
| |
May 22nd, 2006, 12:22 PM
|
#16 | | Professional Member | i don't have any clue where it might be
__________________ no matter what you'll ask of me - all you'll get is a Zubi |
| |
May 22nd, 2006, 12:23 PM
|
#17 | | Banned | look in /etc |
| |
May 22nd, 2006, 12:32 PM
|
#18 | | Banned | Quote:
How to use the hosts file to block ads in Linux or Unix:
Linux users can use the same hosts file that Windows users currently enjoy. Many of you may have known this all along, but for those of you who don't, the Windows and Unix/Linux operating systems use the same format for their hosts files.
Background information on hosts files in Linux and Unix environments:
The hosts file in Linux (/etc/hosts) is a simple list of IP addresses and the hostnames that they correspond to. Every hosts file in Linux should have an entry for the IP address "127.0.0.1", with the name "localhost" following it. This is also known as the loopback address. That same file may also have an entry for your system name, unless you did not provide one during installation.
This hosts file in Linux can store your system's name and IP address, and it is important that you do not delete this information from your computer. Deleting this information will damage your networking capabilities, which means that you may not be able to access either your local network or the Internet.
So unlike Windows, you will probably not want to simply copy the ad-blocking hosts file directly over your existing hosts file. Instead, you should follow these directions:
(1.) Download the hosts.zip file from the Get Hosts File page (or click here) and uncompress it. Be sure the Hosts file is extracted or saved as "hosts", without any file extensions, and not as something like "hosts.txt".
(2.) Find the Hosts file in the appropriate directory on your system.
For most Linux, Unix, Solaris, and BSD users, this will be in the /etc directory, and you will need root access to do anything with it. (For BeOS use: /boot/beos/etc/)
If this is not the case on your system, you will need to locate the existing hosts file. If it is completely empty, you can replace it with the ad-blocking file. If it is not empty, which should be the case, you will want to be sure to save any information that is in there and/or make a backup copy of your current hosts file.
If there are currently entries in your existing hosts file, then open the ad-blocking hosts file. Copy the text from it to add to the bottom of any existing text in your current hosts file. This will ensure that your current entries will still work for you, and that you do not corrupt your network properties.
Note: Be sure that your new Hosts file has the same localhost entry (usually found on the first line) as the existing Hosts file on your system, or you could have some problems. I would advise all users to backup their existing files before switching to the new one. Be sure that you transfer all other entries in your existing hosts file into the new file, unless you are sure that you do not need them.
Do not change any other files you may find that have the name "hosts" in them (such as hosts.deny or hosts.allow). You should not need to change them for the ad-blocking to work.
(3.) Try one of these solutions to begin using Hosts, or reboot if necessary:
(1.) Try logging out and logging back in first, which seems to work on a redhat 7.1 test system at GDS.
(2.) Do a "killall -hup inetd" (without the quotes) while having root privileges, which will restart the inetd process and should not require a reboot.
(3.) In redhat, SuSE, and Mandrake, you can try opening a console window and issuing these commands (without quotes):
"telinit 3", to switch from runlevel 5 to runlevel 3
"telinit 5", which will restart many daemones en route to putting you back in runlevel 5 and the GUI
(4.) If none of those work, then you may have to reboot for the file to take effect.
Many thanks to our readers for pointing some of these methods out.
(4.) Consider using eDexterJavaDog.
If you are experiencing browser slowdowns while using the Hosts file, consider using eDexterJavaDog. It works in a similar manner to the Windows version of eDexter. Visit the eDexter page on this site for more information.
| it will work fine in linux then even if its the windows one :P
just rename it to hosts.conf and place it in the etc directory |
| |  | | |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | | | | Thread Tools | Search this Thread | | | | | Rate This Thread | | |
Posting Rules
| You may not post new threads You may not post replies You may not post attachments You may not edit your posts HTML code is Off | | | |
Copyright © NGOHQ.com - All rights reserved Reproduction in whole or in part in any form or medium without written permission of the site's owners is prohibited.
Powered by vBadvanced and vBulletin from Jelsoft
Copyright © 2000-2007 Jelsoft Enterprises Limited Search Engine Friendly URLs by vBSEO 3.3.2 | | |