Change the name in /etc/nodename

Inside here just replace the old name with the name that you wanted

Change the name in /etc/hostname.interface

Inside here just replace the old name with the name that you wanted

Change the name in /etc/hosts

127.0.0.1 localhost

10.0.0.1 new_hostname loghost

After this you can type

hostname new_hostname

After that you can try to reboot and check by ping to your new hostname.

Change the hostname on a running machine:

$hostname NEW_NAME

This is active right away and will remain like that until the system will be rebooted. You will most probably need to exit the current shell in order to see the change in your shell prompt.

Change the hostname permanently on Redhat based systems:

$vi /etc/sysconfig/network

edit the new Hostname in this file

Reference:

1. http://www.ducea.com/2006/08/07/how-to-change-the-hostname-of-a-linux-system/

I usually find that lots of poeple find it quite difficult to install any application made in PHP and MySQL on their Linux boxes. They find it a bit confusing how to configure the settings. How to install the LAMP stack. Where to put the PHP applications code. I was quite inspired to write to this after having I saw people facing problems on Ubuntu Forums. This is the one which I dealt with.

Sometimes spoon-feeding becomes important,but only for the first time.

Scenario:

A newbie who knows just the basics of Linux. He/She wants to run a PHP application like wordpress / phpBB / osCommerce on their computer.

The distro is assumed to be Ubuntu, though it doesn't change much for others too.

Lets Start:

Step 1: Getting the LAMP stack on your system

You first need to install LAMP on your box, Installation is quite simple. Just get the following packages using the command on your terminal ( Applications> Accessories>Terminal)

sudo apt-get install apache2 php5-mysql libapache2-mod-php5 mysql-server

While installing MySQL, it might ask for set up the root password,if it doesn't ask, then continue.

For more information check this post here .

Step 2: Download the PHP application

You need to download the PHP application which you want to run over the webserver. Examples are Wordpress, phpBB, osCommerce, MediaWiki etc

Get them and let it be in the folder where you have downloaded it.

Step 3: Moving these software to the Apache's root directory

Apache's root directory is /var/www (/var/www/html). This is owned by the user www-data which is a minimal user created just for running apache and web servers. A normal user cant write to this directory.

Now here is the solution of how to copy the data to this directory. This method can be used for any directory which the normal user does not have write access. The concept behind the method is to start an instance of nautilus ( explorer) with root (superuser) privileges. For this follow the isntructions

* Press Alt + F2

* A Run daialog box appears, over there type gksudo nautilus /var/www

* You will be asked for your password as you are elevating your privileges

* Nautilus opens up,now copy the tarball/zip file from the download location to /var/www

* Untar the archive by Right Click > Extract Archive

You may have the package in the folder say /var/www/wordpress. We are supposing wordpress as an example.

Step 4: Setting up username and accounts in database

Now you need to have a create a new database for the software you intent to work on. For this open MySQL from the terminal. If you had been asked to set up the password at time of MySQL installation then use this command

mysql -u root -p

and then enter the root password which you set up

if you were not asked to set up root password, then use this command at terminal

mysql -u root

After this is done you will be dropped to mysql prompt. Create a new database using this:

create database foo;

type quit to exit.

Step 5: Change the data in the config file.

Hunt for file which may have name such as config,settings etc etc. One you locate it,open to find the area for entering database settings. The settings should be:

Hostname: localhost

Username: root

Password: <the password you set up>

Database name: foo (or whatever you created)

Step 6: Access it via browser

Now point your browser to http://localhost/wordpress

You may get the basic installation thing or whatever stuff you need.

Additional Stuffs:

You can be asked to make some locations writable. There may be instances like the software cant write to a specific folder or file. It can be used for cache or any such temporary stuff. Then you need to change the permissions. Simply give write permissions to the user www-root. However this situation may be unlikely. e..g we have to change the permissions of folder /var/www/wordpress/cache

sudo chmod -cR u+w /var/www/wordpress/cache

#last update 7/7/2008: δεν ξέρω τι έγινε και πως, αλλά οι διευθύνσεις με ελληνικούς χαρακτήρες φαίνεται να δουλεύουν κανονικά με τον firefox 3, οπότε αν θέλετε αγνοήστε αυτό το post#

Αυτό είναι κάτι το οποίο δυστυχώς άργησα να το καταλάβω.
Το θέμα είναι ότι δεν μπορείς να έχεις στην διεύθυνση (hostname) ενός post ελληνικούς χαρακτήρες.
Αν αποθηκεύσετε ένα post με ελληνικούς χαρακτήρες στο hostname, αυτοί θα μετατραπούν σε μια ακαταλαβίστικη συμβολοσειρά.

Και τι έγινε θα μου πείτε. Δείτε το παράδειγμα και θα καταλάβετε.

α) διεύθυνση που χρησιμοποιεί μόνο λατινικούς χαρακτήρες:
http://olamesa.wordpress.com/2008/06/17/gynaikeies-prodiagrafes/
όπως βλέπετε φαίνεται ξεκάθαρα ο τίτλος του post.

β) διεύθυνση που χρησιμοποιεί και ελληνικούς χαρακτήρες:
http://olamesa.wordpress.com/2008/06/16/%cf%80%ce%b5%ce%af%cf%84%ce%b5-%cf%84%ce%b7-%cf%83%cf%89%cf%83%cf%84%ce%ae-%ce%b1%cf%84%ce%ac%ce%ba%ce%b1/

Αν σας ικανοποιεί το β τότε δεν χρειάζεται να διαβάσετε παρακάτω.
Αν προτιμάτε το α συνεχίστε ακάθεκτοι.

Αυτό που πρέπει να κάνετε είναι να γράφετε τα hostname με λατινικούς χαρακτήρες (ακόμα επιτρέπονται η τελεία, η παύλα καθώς και τα αριθμητικά ψηφία).

Προσοχή: άλλο ο τίτλος του post και άλλο το hostname του!

Στον τίτλο (title) μπορείτε να γράψετε ότι θέλετε, ελληνικά κινέζικα ή σουαχίλι.
Όταν γράφετε ένα post, ακριβώς κάτω από τον τίτλο του, υπάρχει κάτι που λέγεται Permalink. Σε αυτή τη θέση μπαίνει αυτόματα ο τίτλος του post, και εφόσον ο τίτλος είναι στα ελληνικά, θα μετατραπεί αυτόματα σε αλαμπουρνέζικα.
Αυτή είναι η διεύθυνση του post (το hostname που λέγαμε) και αυτή πρέπει να γράψετε με λατινικούς χαρακτήρες (πατώντας το edit που βρίσκεται δίπλα του).

Με αυτό τον τρόπο θα μπορείτε να ξεχωρίζετε τις διευθύνσεις των post και να μην μπερδεύεστε (θα καταλάβετε πόσο χρήσιμο είναι μόνο αν δεν το εφαρμόσετε, αλλά πιστέψτε με!)

Αν έχετε blog στο wordpress θα έχετε καταλάβει για τι πράγμα μιλάω.
Κάτι τέτοιο:
http://olamesa.wordpress.com/2008/06/16/%cf%80%ce%b5%ce%af%cf%84%ce%b5-%cf%84%ce%b7-%cf%83%cf%89%cf%83%cf%84%ce%ae-%ce%b1%cf%84%ce%ac%ce%ba%ce%b1/

Αυτό συμβαίνει επειδή σε μια διεύθυνση (host name) επιτρέπεται να υπάρχουν μόνο οι λατινικοί χαρακτήρες, αριθμητικά ψηφία, η τελεία και η παύλα.

Ένα hostname είναι αυτό: http://olamesa.wordpress.com/2008/06/17/gynaikeies-prodiagrafes/

Αν χρησιμοποιήσετε χαρακτήρες που δεν επιτρέπονται, π.χ. ελληνικούς, τότε αυτοί θα μετατραπούν αυτόματα σε κινέζικα.

Οπότε, όταν βλέπετε κινέζικα σε διευθύνσεις να ξέρετε ότι υπάρχουν απαγορευμένοι χαρακτήρες.

Σκόρπιες γνώσεις...

Did you ever install ArcGIS Server Java first and then go ahead and change the host name of the machine only to realize now the you will have to either re-install or run post install or contact support to fix ArcGIS Server.

Did you ever have an disk image with ArcGIS Server Java installed and configured, then you go ahead and ghost the image on many machines only to realize that all the hostnames are the same.

Don't worry, In this post you will find information on what files has got the entries of the host name and for what purpose. This will also give you a good understanding of how ArcGIS Server Manager and Web Services Handler uses these configuration files.

Note: These files are for version 9.2, I will update the post shortly after the 9.3 is released.

The five files of concern are:

C:\Program Files\ArcGIS\server\system\Server.dat
C:\Program Files\ArcGIS\java\manager\service\tomcat\managerserver\webapps\arcgismanager\WEB-INF\classes\manager_client.properties
C:\Program Files\ArcGIS\java\web_output\services\WEB-INF\classes\arcgis_wshandler.properties
C:\Program Files\ArcGIS\java\manager\service\lib\manager_config.properties
C:\Program Files\ArcGIS\java\manager\config\applications\build\build.properties

1.  <ArcGIS Install Dir>\server\system\Server.dat

This files stores the actual name of the machine where the SOM is running. Also here the URL's to the virtual directories such as the arcgisjobs, arcgisoutput and arcgiscache is set. If your ArcGIS Services are not previewing correctly in ArcCatalog or if the web service end point url's are shown incorrectly than you should check this file. You can edit this file in any text editor, but once you make any changes to this file be sure to restart the ArcGIS Server processes (both ArcGIS Server Manager and  ArcGIS Server Object Manager).

2. <ArcGIS Install Dir>\java\manager\service\tomcat\managerserver\webapps\arcgismanager\WEB-INF\classes\manager_client.properties

I am not sure on the importance/functionality of this file, but this file has one hostname attribute to startup the manager web application with the correct host name.

3. <ArcGIS Install Dir>\java\web_output\services\WEB-INF\classes\arcgis_wshandler.properties

This is a pretty important configuration file. This file has all the details needed including the hostname of where the SOM is installed for the Web Services handler to initialize. So if you are unable to log into manager and also get an HTTP 503 error when you access the services wsdl (http://machinename:8399/arcgis/services?wsdl) then you need to make sure this file has the right entries. There is nice knowledge base article on this issue and here is the link.

4. <ArcGIS Install Dir>\java\manager\service\lib\manager_config.properties

This file defines a host name parameter to indicate to the manager tomcat instance as to where to start the new tomcat instance to host all the webapps (port 8399)

5. <ArcGIS Install Dir>\java\manager\config\applications\build\build.properties

This file both a URL and SERVER properties which has a hostname entry primarily used by the manager web application to deploy the web application.

Few tips to make your life easier:

• If you are creating an image to ghost then instead of using the machinename try using localhost both during the install and post-install of ArcGIS Server. This way the image is portable and no changes are needed
• If you are using Windows XP then make sure you have turned the built in firewall off (this prevents the DCOM from making the necessary connections) and also make sure the Simple File Sharing is turned off. This is enabled by default and you will have to manually turn this off, its best done i nthe image so that you will not have to do this for every ghosted machine. (How: My Computer -> Tools -> Folder Options -> View -> Advanced Settings -> All the way to the bottom)

[sourcecode language='vb']
sudo /bin/hostname mynewhostname
[/sourcecode]

Supplying the path to the binary is for security reasons, I guess, to make sure we have the right bin (eventhough it could have been replaced there, too...).

But the people at debianadmin.com forgot to mention in order to avoid "hostname: Unknown Host" you have to

[sourcecode language='vb']
sudo edit /etc/hosts
[/sourcecode]

and change it there, too!

GowTo - Instalando Nessus 3.2.0 en Ubuntu 8.04

Para empezar necesitamos cumplir las siguientes dependencias;

libc6 (>= 2.3.5-1), libssl0.9.8 (>= 0.9.8c-1), zlib1g (>= 1:1.2.1), openssl (>= 0.9.8c-1)

Todas estas dependencias se arreglarian con un simple comando

sudo apt-get install libc6 libssl zlib1g openssl

Con esto resolveriamos las dependencias de Nessus y podríamos instalarlo sin mayor problema, ahora necesitariamos el paquete para nuestra distribución, en mi caso voy a trabajar con Ubuntu 8.04 como ya dije en el título pero es casi lo mismo para las demas.
Lo primero sería ir a la web oficial de Nessus y darle a "Downloads" y insertar la información que nos pide y descargarnos el paquete que vaya acorde a nuestras necesidades.

Nessus-3.2.0-ubuntu710_i386.deb

Aunque en este caso usaremos el paquete para Ubuntu 7.10 funciona perfectamente en Ubuntu 8.04 sin problema.
Bien procedemos a la instalación, en este paso tenemos dos maneras o bien por gdebi o por dpkg;

Para instalar desde GDebi;

#~$ gdebi-gtk

Y selecionamos el paquete desde el menú de GDebi, esperamos a que termine la instalación y ya estaría, tendriamos nuestro nessus instalado.

Para instalar desde dpkg;

#~$ sudo dpkg -i Nessus-3.2.0-ubuntu710_i386.deb

Bien, una vez instalado para los amantes de un entorno más gráfico para nessus tenemos NessusClient que también se puede descargar desde la propia web de Nessus.

Para instalarlo tan simple como usar gdebi-gtk como ya he mencionado arriba seleccionando el paquete de NessusClient o bien desde dpkg;

#~$ sudo dpkg -i NessusClient-3.2.0-ubuntu710.i386.deb

Una vez termine, tendremos que entrar en nuestro email para recojer el código de Plugins que se nos ha enviado. y pondremos;

#~$ sudo /opt/nessus/bin/nessus-fetch --register el código que se te ha enviado

Luego añadiremos al usuario para poder conectarnos a nuestro servidor de Nessus;

#~$ sudo /opt/nessus/sbin/nessus-add-first-user

Y nos pedirá una serie de datos que deberemos introducir según nuestros criterios.

Si hemos llegado hasta aquí quiere decir que o bien hemos terminado satisfactoriamente o bien estaís buscando alguna solución a un fallo que os ha aparecido durante la instalación. Si es lo segundo, dejad un comentario con vuestro problema y vuestra distro para poder ayudaros. En caso de que sea lo primero continuemos;

Retomando, iniciamos Nessus con el siguiente comando;

#~$ /opt/nessus/sbin/nessus-update-plugins && /etc/init.d/nessusd stop && /etc/init.d/nessusd start

Así nos aseguramos de que dispondremos de los últimos plugins disponibles y de que si nessusd ha sido iniciado anteriormente se reinicie para que se recargen los plugins.

Ahora debemos crear nuestro primer usuario para conectarnos con el servidor nessusd.

/opt/nessus/sbin/nessus-add-first-user

Bien ya tenemos nessusd iniciado correctamente si todo ha ido bien, y ahora podremos conectar a nuestro servidor de Nessus llendo a Aplicaciones -> Internet -> NessusClient

Una vez dentro sería configurar el servidor al que vamos a conectar dandole al boton que aparece en NessusClient; Connect (Ver Imagen) nos aparecera este menú.

Una vez estemos dentro, clickearemos en Edit y nos pedirá lo siguiente:

Connection Name (Nombre de conexión): Podemos Poner lo que queramos
Host Name (Nombre del Host): aquí va la IP en caso que sea local 127.0.0.1
Port (Puerto): Por defecto 1241
Login (Usuario): GenLinux (En tu caso el que añadistes en el comando de /opt/nessus/sbin/nessus-add-first-user
Password (Contraseña): La contraseña que elejistes

Y ya estaría. podríamos conectar a nuestro servidor de Nessus sin problemas y comenzar a escanear.
Espero que este pequeño GowTo haya solventado esas pequeñas dudas que pudierais haber tenido.

]]> http://axdimensions.wordpress.com/?p=123 Thu, 10 Apr 2008 17:55:30 +0000 Em http://axdimensions.wordpress.com/?p=123 "Finding hostname from IP address" post has been moved to:
http://www.axdimensions.com/pixelnotes/2008/04/10/finding-hostname-from-ip-address/

Thanks, Em

1. Give Your Router A Name
Router(config)#HostName AnyName

2. Securing Your Privilage Mode
a. Router(config)#Enable Password AnyPassword
b. Router(config)#Enable Secret AnySecretPassword
If you configure both password and secret password, secret password will be the router privilage mode password.

3. Securing Your Console Line
Router(config)#Line Console 0
Router(config-line)#Password AnyPassword
Router(config-line)#Login

4. Securing Your Telnet Line
Router(config)#Line vty 0 4
Router(config-line)#Password AnyPassword
Router(config-line)#Login

5. Secure Your "Text Password" with Encryption
Router(config)#Service Password-Encryption

6. Describe All The Interfaces or Lines or Configuration
Examples:
Router(config-if)#description  This  Is The Link  To  HeadQuarter LAN
Router(config)#Access-List 101 Remark This List Stops Telnet Sessions To Accounting LAN
Router(config)#Banner motd #You're Entering Secure Area, Make Sure You Have Rights!#

Naturalmente non si andrà in ordine di importanza, giusto per non influenzare le vostre scelte nel settore :-D

Partiamo da Plone

Semplice, potente e standard compliant. Tre aggettivi che definiscono Plone, uno tra i migliori CMS in circolazione usato da moltissime organizzazioni tra cui (tanto per fare un esempio tra i più noti) la Free Software Foundation.
A giudicare dalle feature incluse nelle ultime versioni, Plone si candida come una tra le migliori CMS solutions di sempre.

Tra tutte le nuove caratteristiche ne voglio segnalare alcune, a mio avviso, degne di nota:

- Supporto alla Working Copy, caratteristica che permette l’editing contemporaneo di due versioni dello stesso documento

- Possibilità di vedere quali sono state le aggiunte da parte di più autori a un documento e nel caso tornare a una versione precedente

- Miglioramenti all’editor HTML e implementazione di AJAX per evitare di dover salvare un documento per vederne le modifiche.

- Indicizzazione del testo contenuto in documenti Word e PDF

Come sempre, qualunque versioni si adoperi, è facilmente installabile su Linux, Windows, Mac grazie a degli installer che permettono di avere in pochi minuti la propria istanza di Plone perfettamente funzionante.

Passiamo ora a WordPress, anche se forse dovrei evitare di parlarne per non creare conflitti di interesse [vedere dominio, please! :-D ]

Di questo CMS una cosa è certa, è di sicuro il più usato, ricchissimo di plugin (sia sul fronte amministrativo sia per le sciocchezze varie ed eventuali) e non ultimo ha dalla sua una portabilità non ndifferente (esiste un plugin per la visualizzazione e uso su nintendo wii, ds-lite, psp e iphone!)

Il rilascio delle edizioni ha una velocità impressionante e la frequenza di aggiornamento è notevole

Interessante l'utility OneClick

con la quale è possibile evitare i “vecchi metodi” dando la possibilità a chiunque di poter personalizzare facilmente il proprio blog.
Nelle precedenti versioni OneClick veniva rilasciato come plugin che consentiva l’installazione (e cancellazione) di add-on e temi grafici attraverso un form nell’area amministrativa (per precisione nella Dashboard) di Wordpress, ma con l’ultima release è stata implementata anche un’estensione per Firefox denomita OneClick Installer che si interfaccia perfettamente con il plugin.

Navigando con Firefox basta un semplice clic con il tasto destro sulla url che punta a un tema o a un plugin per installarlo.

Una comodità non da poco per i “Wordpress addicted” :-D

Altra utility di sicuro interesse, specie per i paranoici (come il sottoscritto), è EasyBan . Come tutti i plugin per WP si installa facilmente e consente in poco tempo di erigere una barriera contro i “soliti sospetti”. Possono essere bannati indirizzi IP, domini, hostname, referrer e si può decidere anche un redirect per ban, cioè di ridirezionare i visitatori molesti verso altri siti.
E’ anche possibile impostare un tempo predefinito, passato il quale il ban cesserà di essere attivo.
Il plugin è anche dotato di un pannello di controllo per gestire con semplicità i ban.

Per ultimo, ma non certo per importanza, HyperDB. Si tratta di una classe per database che consente l’utilizzo di funzioni avanzate già implementate in Wordpress.com e da ora in poi disponibile per la comunità.
In particolare HyperDB supporta:

- Replicazione
- Failover
- Network (pubblici/privati) ridondanti
- Datacenters locali e remoti
- Partizionamento
- Tabelle differenti su diversi database
- Statistiche avanzate per la profilazione degli utenti

La classe potrà essere utilizzata rimpiazzando la wpdb. L’installazione, come spiegato da Matt Mullenweg, consiste nello scaricamento dei file db-settings.php e db.php, nell’inclusione di db-settings in wp-config.php e nel caricamento di db.php in wp-content.
Per consentire la partecipazione della comunità alla sviluppo di HyperDB è stata attivata una mailing list dedicata.

Stop ai complimenti ... anche perche, come i più informati sanno, qualche tempo fa Linux.com proponeva un serrato confronto: Drupal vs WordPress. Per scoprire come si comportano questi 2colossi, Linux.com ha utilizzato i servizi di Bryght e di WordPress.com per predisporre due siti simili; sono state confrontate le interfacce ed i passi base per la personalizzarne l’aspetto, l’aggiunta di contenuti, la gestitone di commenti e spam, la lettura delle statistiche e altre funzionalità tipiche di un CMS.

I risultati? Stando a Linux.com Drupal offre maggiori possibilità di tuning e migliori strumenti per il controllo di blog multipli ma a WordPress, seppur meno configurabile (anche a fronte di tutti i plugin e gli strumenti sopra citati) dell’avversario, va la palma di CMS più "professionalmente" facile da usare e navigare.

1. SSH to the server (as the root user) and change the hostname.
2. Then run the command /usr/local/cpanel/cpkeyclt.

This will update the license file with your current hostname, and push the change to cPanel's license verification servers auth.cpanel.net and verify.cpanel.net.

The files that you need to change to change the hostname are:

• /etc/hostname.<interface>
• /etc/nodename
• /etc/hosts
• /etc/inet/ipnodes

The /etc/host file that contain the ip address and all the hostname that is resolved to that specific ip adress. Find the interface's ip address and change the old hostname to the new one.
All the other file contain just the hostname, so change the content of the files to match the new hostname. If you have multiple network interfaces, then you will have, for example, /etc/hostname.eth0, /etc/hostname.eth1 and so on.

If you are not planning to restart the machine, then you need to run the 'hostname <new hostname>' command and also rename "/var/crash/<oldhostname>" to "/var/crash/<newhostname>". But if you are planinng to restart anyway then the system will create the /var/crash/hostname and use the new hostname on startup.

edit:(22/2/08) After some more testing, it seems that some application are a little more finicky about hostname changes than others. So I would suggest you to rename the "/var/crash/<oldhostname>" and run the "hostname" command  directory regardless weather you will restart the machine or not.I had trouble with certain configurations of kerberos if those steps are not done even if I restarted the machine.

Hope you like your new hostname. :D

Mittlerweile find ich den Namen echt nicht so übel, ich glaub einer meiner nächsten Rechner wird Ubunut getauft. So stelle ich mir übrigens die Ubunuss vor ;-):

So und jetzt bin ich mal gespannt wie viele das Wordpress Tag Ubunut schon verwendet haben.

I will not detail here all the configuration needed for that (or maybe later if you are nice) but I will explain a trick that can help you when the syslog-ng server does not want to create a file for a host and put its messages in the Fallback file. 

Usually, all is working fine with simple filters, like this one :

filter my_filter { host("myserver");};

Here, 'myserver' is in fact the hostname in the message header (should be in third position after the date and the hour/timestamp). Some device may send their messages without the hostname field in the message resulting the log written in the fallback file.

In this case, you can use netmask intead of host, like this:

filter my_filter { netmask("<ip address of the server>/<netmask>");};

for ex : filter my_filter { netmask("192.168.1.100/255.255.255.0");};

Which should this time make your redirection to work well and the file created for this host correctly.

Note: using /32 does not work at all, use the entire netmask instead.

gksudo gedit /etc/hostname

3 - Irá surgir um prompt, digite a senha do root e então pressione OK.
4 - O arquivo hostname será aberto, mostrando o nome atual do computador. Altere para o nome desejado
5 - Clique em salvar.
6 - Feche todas as janelas e reinicie o sistema.

Após o reinicio, sua máquina já vai estar com o novo nome.

Fonte: tech-recipes 

Seguo l'ordine cronologico degli eventi ...

Le mie prime distribuzioni:

• Red Hat 7
• Red Hat 7.3
• Red Hat 8
• Slackware 8.1

Data la mia elevata esperienza in linux, usavano il nome di default che dava la distribuzione. Sia mai che cambio qualcosa e poi non funziona più nulla. Vero?

La scoperta di Harry Potter:

Dopo aver scoperto Harry Potter, ho cominciato a distinguere il bene dal male. Così, conoscendo i varii personaggi, ho cominciato ad attribuire i nomi alle distribuzioni:

• debian -> Silente ... è uomo saggio e pieno di sapere. Un pò come la debian
• gentoo -> Hermione ... prendendo spundo dal pinguino del nome ... ho pensato ad Hermione ... piccolina e veloce con gli incantesimi :P
• slackware -> Hagrid! Amabile, dura e rozza, quale nome migliore?
• Fedora -> Ginny ... sò che Fedora ha il logo blu, ma derivando da Red Hat non riuscivo a non vederci il rosso e quindi ho pensato ai Weasley. I quattro fratelli maschi non mi ispiravano da usare come nome, così ho messo la sorella
• ubuntu -> essendo una derivata di debian, ho tenuto silente anche se non se lo merita a mio avviso. Dovrei trovare un nome migliore ma non ho voglia di pensarci.

Per info di cronaca, dalla scoperta di Harry Potter, le macchine del "sistema bandiera" hanno assunto dei nomi particolari anche loro: malfoy, voldemort, mangiamorte

In fase di creazione della rete, il dominio ve lo lascio immaginare. Indoviniamo? Bravissimo ... hogwarts :)

Magari, con tutta la possibile calma di questo mondo, un giorno cresco ... state tranquilli :P

Easy.

That is.

Simply replace the name in your /etc/hostname file as superuser (sudo) and save the file, as tech-recipes.com tells us.

Or:

gksu gedit /etc/hostname

As pie.

To see the change, restart your system.

EXTRA TIDBIT: Remember that gksu is the same as sudo, but it is the recommended command to use for graphical programs. In this case, gedit (Gnome’s Text Editor). Sudo is best suited for terminals, or command-line. You could have also typed in gksudo, but that is the same thing: it’s a symlink to gksu. And in KDE, you could have used kdesu (KDE SuperUser).

- Aprite un terminale

- ed editate questo comando molto semplice :

- vi verrà richiesta la password dell'utente amministratore dopo di che si aprirà il file e verrà visualizzato il contenuto con il nome attuale del vostro host quindi il nome del pc. Cambiatelo come desiderate e salvate il tutto!

- Ora dopo aver salvato chiudete la finestra del terminale e riavviate il sistema.

cambiare, nome, computer, pc, linux, hostname, tips, truchetto

password : [enter your telnet password here]
switch> en
password : [enter your privileged exec password here]

switch # configure terminal
switch (config) # hostname MYSWITCH
MYSWITCH (config) # end

[optional] Backup your old setup
MYSWITCH # copy startup-config startup-config.bak

Save your running setup (so it will start at boot)
MYSWITCH # copy running-config startup-config

Pues me he encontrado con el siguiente problema los PC's que se conectan no pueden tener el mismo nombre (sí, el nombre que pones en la instalación de Linux). Y he tenido que cambiar el nombre de uno de los dos. Y he estado a punto de naufragar en el intento :D.

Pues bien; utilizé el comando sudo hostname nuevo_nombre para intentar arreglarlo. Pero casi jodí Ubuntu, y tuve que entrar en la terminal de reparación para arreglarlo. Pero eso ya es otra cosa, así que mejor os cuento qué hay que hacer para el cambio de nombre(es fácil y rápido, y no tiene peligro alguno):

1. Abrir una terminal.
2. Insertar sudo gedit /etc/hostname. Lo más probable es que te pida tu contraseña.
3. Modificar el nombre que te sale en pantalla (que es el de tu PC) por el que quieras.
4. Guarda y cierra.
5. Ahora poner sudo gedit /etc/hosts en la terminal. Te saldrá algo como 127.0.0.1 localhost y 127.0.1.1 nombre_de_tu_equipo. Pues bien, limítate a poner el mismo nombre que has insertado antes en el espacio indicado como nombre_de_tu_equipo.
6. Reinicia y todo listo

 Zmiana nazwy hosta

Muszę przyznać się iż podczas instalacji nazwa hosta którą wybrałem nie była zbyt ładna, stąd też niedługo poczułem potrzebę jej zmiany. ;) Teoretycznie łatwo mozna tego dokonać w Menu K -> Control Center -> Internet & Network -> Network Settings -> zakładka Domain Name Systems, jednak w praktyce na początku wszystko OK, ale po reboocie ustawienia się resetują. Poszedłem za radą użytkowników z polskiego forum Slacka i dodałem po prostu
hostname moja_nazwa
do pliku startowego rc.local. (/etc/rc.d/rc.local).

To know windows IP configuration go to command propmt and type ipconfig /all  - this shows detailed information about the IP configuration of the the server you have logged in.

To know the connection status to another IP address, use ping  ipaddress  command

To trace all the IP address that is between your current server to the destination IP address use tracert  ipaddress command

To know the hostname use hostname command, it will show the host name.

To know all the prots on the server use the following command

C:\> netstat -an
The Netstat command can list currently used ports, which might be helpful if you suspect an application is clashing with another one on an active port. The -an switch is used to show all connections and listening ports in numeric form.

- site:ipsum.ro
Permite aflarea tuturor fisierelor dintr-un domeniu sau din toate subdomeniile lui.

- hostname:ipsum.ro
Permite aflarea tuturor fisierelor dintr-un anumit domeniu.

- link:http://ipsum.ro
Permite aflarea tuturor fisierelor care au link spre un anumit URL. Spre deosebire de Google, care arata doar un procent mic din paginile care au link spre site-ul dvs., Yahoo arata majoritatea acestora.

-url:http://ipsum.ro
Permite aflarea unui anumit fisier in index.

- inurl:optimizare
Permite aflarea unui cuvant cheie parte din URL-urile indexate.

- intitle:optimizare
Permite aflarea unui cuvant cheie parte din titlurile fisierelor indexate.

Comanda link: in Yahoo va va da o idee mai buna asupra Backlink-urilor.

In Yahoo se foloseste links, iar in Google link:

link:http://ipsum.ro e incorect pentru Yahoo

corect e

links:http://ipsum.ro