Run “sudo dpkg-reconfigure -phigh xserver-xorg” and select vesa as the video driver and 1440×900 and 1280×800 as extra resolutions. Then restart X (reboot or ctrl-alt-backspace).
If you're already familiar with Linux and just wonder why Ubuntu/Kubuntu uses sudo instead of root, this page isn't for you. You're really looking for https://help.ubuntu.com/community/RootSudo. It has a full explanation of why Ubuntu uses sudo instead of root and what the advantages and disadvantages of that choice are.
This page is for people who are new to Linux and Ubuntu/Kubuntu and want to know what the deal is with file permissions.
My guess is you're probably a typical ex-Windows user (as I was), used to running as Administrator and being able to edit pretty much any file you want, even system files, even the registry--at will, very little stopping you... maybe the occasional "read-only" file that you can just make read/write by checking a little box in the Properties dialogue.
You may also never have installed and configured an operating system before (especially if you bought a computer with Windows preinstalled for you).
Some idiots in the Linux camp will say "you shouldn't have to edit such-and-such a file." That's simply not true. Most Linux users aren't just users--they have to install and configure stuff themselves (as Dell or HP won't do it for them), usually configuration files and system files that normal users don't have to touch (say, in order to adjust the possible screen resolutions or install new software). You do have to edit these files from time to time. It's in your best security interests to have to go out of your way to edit them, but you should still be able to occasionally edit, move, copy, and rename files that only an Administrator (or Root) can modify.
In Linux, the only files a user can modify are the ones in her home directory. For example, if the user's name is Bronte, the files she can modify live in the /home/bronte/ folder. Anything outside the /home/bronte folder she will not be able to modify. Some of the top files new installers need to modify are:
/etc/fstab (making hard drives and partitions viewable as folders)
/boot/grub/menu.lst (controlling the boot menu that lets you choose which operating system to boot to)
/etc/apt/sources.list (the list of sources from which you can easily install software)
/etc/X11/xorg.conf (screen resolution options, among other things)
and all of these files need Root privileges to modify.
If you're like a lot of new Linux users, you probably have not yet embraced the command-line. Some people may have told you to "just" sudo rm -r /usr/share/icons/themename as if "rm" really means anything to you yet. The fact of the matter is that people recommend command lines because they're easier instructions to give than "Click on that button that looks like a purple arrow. A new dialogue will pop up with three choices. Pick the left-most choice."
Most new Linux users just want to be able to click and drag and drop. So these two new commands should be your new best friends...
If you're using Ubuntu (Gnome), press Alt-F2 and type gksudo nautilus
If you're using Kubuntu (KDE), press Alt-F2 and type kdesu konqueror
What do these commands do? They allow you to generally operate as a regular user but have a temporary window within your user account to operate as Root (just within the Nautilus or Konqueror window you've opened). Once you close the Root window, it's just as if you're a user again. You don't have to log out of user, log in as Root, make changes, log out of Root, and log back in as user again. You can be Root and user simultaneously.
Mac OS X users may be familiar with this security model (Mac uses sudo, believe it or not!). As a Mac user, you operate as a user. When you want to install something, a dialogue box comes up asking for your administrator (sudo/root) password. Once it's installed, you're a user again.
So how does this work? Let's say you want to edit the /etc/apt/sources.list file. If you want to do it command-line style, you'd sudo nano /etc/apt/sources.list and then use Nano to edit it. If you do it the graphical way we've been talking about, you'd run the gksudo nautilus or kdesu konqueror command and a file browser window will pop up (with Root/administrator privileges just in that window). You'd browse to /etc/apt and find the file called sources.list. You'd click to open it, edit it, close it, and close the browser window, and it would be done.
If you find that (especially right after the initial Ubuntu/Kubuntu install) that you're making a lot of changes as Root, create a launcher with the command gksudo nautilus or kdesu konqueror. Then, when you click on that launcher, you can type in your password, make root changes, and then close the window and be a user again.
Warning: Always make backup copies of any configuration files you modify before modifying them.
Ubuntu oficialmente sólo da soporte o apoya una cierta cantidad de programas disponibles directamente usando los programas Añadir y quitar... o Synaptic (ver: añadir aplicaciones) mediante el sistema de repositorios. No es una cantidad muy grande ni completa pero afortunadamente la comunidad de usuarios hace posible que se puedan instalar decenas de miles de programas.
Este artículo trata de activar los dos repositorios mas importantes y conocidos extraoficiales:
Universe, programas mantenidos por la comunidad
Multiverse, programas comerciales o privativos de terceras empresas o fabricantes.
Para activarlo, es muy fácil, hay que ir al menú Sistema, Administración y click en Propiedades del Software (ver Fig.1). Ahora pulsa en el botón Añadir y en la ventana que se abre ve seleccionando todos los canales y activando las casillas: Mantenido por la comunidad (universe) y Software no libre (multiverse) (ver Fig.2).
Ahora marca la casilla de activación de todos los canales universe y multiverse (ver Fig.3). Una vez hecho esto pulsa en el botón cerrar.
Fig.3 Repositorios a activar..
El sistema te mostrará un aviso indicando que la lista de paquetes esta obsoleta. Pulsa Recargar y el sistema procederá a actualizar la nueva lista de paquetes o programas disponibles desde Universe y Multiverse.
Recordar que como dice el aviso que se ve a continuación, necesitarás de internet para poder actualizar e instalar nuevos programas:
Si no usas Gnome o quieres probar un método alternativo, lo puedes hacer utilizando el programa Terminal. Para evitar posibles problemas si hubiera algún error, es recomendable hacer una copia del archivo sources.list. En este ejemplo la copia la guardamos en el mismo directorio bajo el nombre de sources.list_old:
Lo siguiente es editar el fichero encargado de administrar los repositorios con el programa Gedit por ejemplo:
$ sudo gedit /etc/apt/sources.list
Después de hacer esto cambiaremos nuestra sources.list suprimiendo las almohadillas (#) en cada línea donde aparece universe o multiverse, por ejemplo debes de tener algo muy parecido a esto:
De esa manera ya tendremos todos los repositorios activados, ahora Y SIEMPRE que cambiemos la sources.list (es imprescindible) ejecutaremos el siguiente comando:
$ sudo aptitude update
Esto nos servirá para actualizar la lista de paquetes que tenemos en nuestro repositorio. De esta manera ya tendremos los repositorios del sistema y los universe y multiverse activados.
Substitute gedit with the text editor of your choice.
Add the following to your sources.list:
NOTE: Kubuntu/Xubuntu users will need to uncomment (remove the # before the word "deb") all the additional sources as well as add the automatix repository.
After trying different Music/Media Players in Ubuntu Linux, I decided that my favorite one is Amarok. It has a lot of good functional features for music fanatics like me (over 7000 MP3s) that need good collection management. It’s Collection/Library works similar to Winamp’s Media Library, although some improvements can be made to it (that’s another post).
My problem was that if I was browsing my MP3 files and decided to start playing a song from a Nautilus window by double-clicking the file, it would open in Xine. No thanks, that’s not what I want! The file association wasn’t what I wanted. Thinking that I could simply access File Association settings like in Windows, I set out to find these settings. Of course, there wasn’t anything similar to this.
This plagued me for a couple of weeks and in the back of my mind, I knew it would be the simplest stupid setting somewhere that I just couldn’t find. So I set out to find the answer…
Although, in this post, I’m specifically talking about MP3/OGG files, these steps should work with any file-type and any application that can open those file-types.
I knew that I could simply right-click on a file, point to Open With and select an application from the list.
Amarok wouldn’t show in that list! Once I selected “Open with Other Application…” and selected Amarok, it then showed in the list of Open with applications.
So every time I wanted to open an MP3/OGG file, I would have to right-click, point to Open with and select Amarok.
That’s still not good enough. I need to double-click only!
After reading a certain post on the Ubuntu Forums, the answer was so obvious, I literally slapped my forehead!
Right-click on a file of the type you wish to set a default application to open it with
Select Properties
Select the Open With tab (all makes sense, now, doesn’t it??)
Select the application you want associated with that file-type
Click OK
Wow… that was easy! Double-click the file to see if it opens in your application. Funny thing is, I saw that tab before and used it for another file-type and for some reason, I thought that it would set the default for that file only! Doh! I didn’t notice the message at the top of that tab:
Ubuntu offers characteristics found in mature Linux
distributions. For example, in figure 8 you can see a screenshot of a
Windows Terminal Server session initiated from the Ubuntu desktop.
Ubuntu also has the ability to act as a server and client for FreeNX
and VNC.
Instalar el interface del cliente PPTP apt-get install pptpconfig
Antes de continuar necesitamos conocer los siguientes datos: La dirección ip a la que conectarnos, el nombre de usuario, la contraseña y la encriptación que usaremos.
Ejecutamos pptpconfig como root (o con sudo en su defecto)
Rellenamos las diferentes pestañas.
Pulsamos Add, la marcamos y pulsamos start
En el caso de obtener algun error podemos ver información de depuración avanzada activando la opcion Enable connection debugging facilities en la pestaña Miscellaneous
Añadir la ruta para la nueva red (como root o con sudo) route add -net 192.168.121.0 netmask 255.255.255.0 dev ppp0
It creates some Gnome menus, but it is unorganized and not run as sudo. Edit your menus by following this simple tutorial - Gnome Menu Editor
Delete the entry it created and make a new one under Applications>Internet or wherever and using the command gksudo pptpconfig
* Automatix: potente gestor de paquetes y instalador,Imprescindible para instalar aplicaciones de forma sencilla y sin muchos conocimientos del entorno Linux.
* Beagle: buscador e indexador de contenidos de vuestros discos duros tipo Spotlight para Mac OS X, es decir buscará y nos presentará resultados de forma muy rápida por entre nuestras carpetas de sistema.
* Gnome Deskbar Applet: un potente menú alternativo muy configurable que podréis descargar desde aquí y que os permitirá integración con Beagle y con vuestro sistema para lanzar aplicaciones de forma ultra-rápida.
* VLC: reproductor multimedia todoterreno
* Firefox: viene como navegador por defecto, pero es que es algo sin lo que no se puede vivir, además gracias a sus configurables extensiones lo hacen imprescindible
* amaroK: ¿Qué decir del mejor reproductor musical que podéis calzar en vuestra distro?
Si hay para linux y se llama gmailfs
sudo apt-get install gmailfs
es un pequeño script en python que monta tu cuenta de gmail en un directorio con
el comando mount.gmailfs y las opciones
none /mnt -o username=gmailuser@gmail.com,password=gmailpass,fsname=zOlRRa
y podes escribir, borrar y ejecutar cosas desde ahí.
Después de instalarlo busquen en /usr/share/doc/gmailfs/examples mas ejemplos
Suerte
Existe uan extension para firefox que te permite usarlo como disco duro, no se montara como una unidad pero por firefox te administrara el disco como ftp
For playing media files on shares, you'd be best to mount the samba shares properly rather than just view them through a browser.
e.g.
sudo mount -t smbfs -o username=***,password=*** //path/to/share /mount/point
(if you haven't already done so, install smbfs)
sudo aptitude install smbfs
Marble Station » Blog Archive » Guía de referencia rápida para la personalización de Ubuntu Edgy (6. www.marblestation.com/blog/?p=595
Extensiones para Firefox
Con la extensión Browser Sync de Google podremos centralizar nuestros bookmarks, cookies, passwords, etc… en los servidores de google, de forma que si usamos diferentes máquinas con diferentes firefox, podamos tener toda es información sincronizada.
Otras extensiones de gran utilidad para bloquear banners y publicidad en general son:
Marble Station » Blog Archive » Guía de referencia rápida para la personalización de Ubuntu Edgy (6. www.marblestation.com/blog/?p=595
Beagle, búsqueda de archivos mejorada
Beagle es una herramienta que nos permite buscar en nuestros archivos más rápidamente y eficazmente, no solo podremos buscar por nombre de fichero sino también por el contenido de los mismos.
Marble Station » Blog Archive » Guía de referencia rápida para la personalización de Ubuntu Edgy (6. www.marblestation.com/blog/?p=595
Antivirus
ClamAV es un antivirus gratuito y libre que principalmente nos ayudará a detectar virus para Windows (dado que para Linux prácticamente no hay). Nos puede servir para escanear archivos antes de pasarlos a entornos Windows:
sudo aptitude install clamtk
Las definiciones de virus se actualizan de forma periódica, si preferimos que no sea automático:
sudo update-rc.d -f clamav-freshclam remove
Desde la interfaz gráfica del antivirus podremos actualizar las definiciones cuando queramos.
If you connect to the same samba share day in and day out, you'll likely want to mount it with a more permanent arrangement so you don't have to go looking for your mount command every time you boot your computer. To do this, you'll need to modify your fstab file. This is a system critical file (your Ubuntu box will not work correctly if it has a mistake), so you'll want to make a backup in case things go haywire on you:
Code:
sudo cp /etc/fstab /etc/fstab_old
if you need to restore your backup, use the following command:
Code:
sudo mv /etc/fstab_old /etc/fstab
If your samba server requires a password to access the shared files, you should create a credentials file so the username and password are hidden from prying eyes. If you don't have password protected access to your samba share, skip this section and start with the line that says "Now we edit fstab:".
To create a credentials file, do the following:
Code:
sudo nano /root/.smbcredentials
add the following lines (change winusername and winpassword to the correct username and password for your samba server share):
Quote:
username=winusername
password=winpassword
Save the file by hitting ctrl+x, type "y" to save the buffer, and <enter> to exit.
Now, change the permissions of the file so only root can read and edit it:
Code:
sudo chmod 700 .smbpasswd
Now we edit fstab:
Code:
sudo nano /etc/fstab
and at the end of the file, insert one (1) of the following 3 lines according to your needs. Make sure you change "netbiosname" and "sharename" to the respective names on your network. (if you don't know what these are, please see the next post)
For a password protected share with read/write permission.
Save the file by hitting ctrl+x, type "y" to save the buffer, and <enter> to exit. note: if you've used a text editor other than nano, make sure that there is a blank line at the end of this file.
Finally, test your settings to make sure they work:
Code:
sudo mount -a
If you get a folder on your desktop with your server shares, then you have configured everything correctly. If not, please review the howto, or post in the thread.
Now, your samba shares will be mounted every time you start the computer. If you are not connected to your network when you boot, this will not cause problems. The share will simply not appear on your desktop.
INSTALAR y usar WINE
- lo instalo con automatix2 (los tips que he encontrado por internet dicen que hay que desinstalar versiones anteriores) - automatix lo ejecuta y dice que ejecutes winecfg para finalizar. lo hago y resulta que es una aplicación grafica para definir varios parametros de la emulación. para ejecutar una aplicación hay que añadirla a la base de datos que crea winecfg - una vez añadida la aplicación, para tularla simplemente abrimos un terminal y vamos a donde este el ejecutable y para ejecutarlo ponemos wine seguido del nombre del fichero ejecutable a rular (por ejemplo wine "Keygen.exe" para rular el keygen del vmware worktation y registrarlo
Hace años que vengo arrastrando muchos gigabytes de música de un lado a otro, y soy terriblemente obsesivo con el nombre, id3 tag y calidad de cada canción.
Siempre tuve dando vueltas en la cabeza la idea de normalizar el sonido de todos para no tener que subir y bajar el volúmen entre temas, pero siempre me pareció algo un tanto complicado cómo para invertir tiempo.
Finalmente de casualidad me encontré con la solución.
Para los que están en Ubuntu es tán simple cómo ésto:
sudo apt-get install mp3gain
Y ejecutan ésto en el directorio donde tienen sus MP3. find . -type f -iname '*.mp3' -print0 | xargs -0 mp3gain -r -k
En mi notebook toshiba con un P4 3.2ghz y 1gb de ram tarda un promedio de 3-4 segundos por tema.
In Ubuntu Edgy you can choose between two methods of installing the proprietary ATI driver. If you are new to linux you should use the first method as it is a lot easier than the second one and will work well in most cases. The second method describes how to install the very latest driver version, but requires some additional work and knowledge.
Contents (He seguido el método 1 sin problemas - SANTI !!!!!!!!!)
In Ubuntu Edgy the Composite extension is enabled by default, however, fglrx does not yet support Composite with DRI. In order to to disable Composite you have to edit the xorg.conf file:
Make sure the restricted repository is enabled in /etc/apt/sources.list or this guide will not work!
sudo apt-get update sudo apt-get install linux-restricted-modules-$(uname -r) #Okay if it is already installed sudo apt-get install xorg-driver-fglrx sudo depmod -a sudo aticonfig --initial sudo aticonfig --overlay-type=Xv
Now Reboot your system:
sudo shutdown -r now
An alternative to the aticonfig --initial command is to edit /etc/X11/xorg.conf and replace the string "ati" with "fglrx" in the "Device" section. This way you won't lose your old "Screen" and "Monitor" settings. Afterwards you can use aticonfig for setting overlay etc.
The output of dmesg | grep fglrx and /var/log/Xorg.0.log are most useful when looking for errors. You should really include this when you are asking for help somewhere.
If you used Method 2 before, you have to unblacklist fglrx again by editing /etc/default/linux-restricted-modules-common. You may have to run sudo lrm-manager afterwards.
In Ubuntu Edgy the Composite extension is enabled by default, however, fglrx does not yet support Composite with DRI. In order to to disable Composite you have to edit the xorg.conf file:
Blacklist old fglrx module from linux-restricted-modules
As ubuntu's linux-restricted-modules package includes the fglrx module from an old driver version (8.28.8), we have to blacklist this module to make sure the new kernel module which is needed by the new driver will be used instead.
Change to the download directory. Make sure that you have the universe and multiverse repositories enabled in /etc/apt/sources.list before doing these steps.
The aticonfig --initial command will not update the xorg.conf file if it already has a "fglrx" Device section.
However, you may force aticonfig to generate default Monitor, Device, and Screen sections with the following command:
If the fglrx module isn't loaded try to add fglrx to /etc/modules on a new line. See also bug 63912.
File: /etc/modules
# /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored.
However, rebooting is the easiest method to ensure that the kernel module(s) from the old driver are unloaded and the fglrx module is loaded instead. If you don't want to reboot for some reason, you may manually shut down Xorg, unload any old "drm", "radeon" or "fglrx" modules and then start Xorg again.
Note: if modprobe fglrx can't find the fglrx module, try rebuilding your kernel module dependency:
If (for any reason) the fglrx install fails, you can revert to the Xorg driver by executing
sudo dpkg-reconfigure xserver-xorg
and selecting the "ati" driver, or simply restoring the previous /etc/X11/xorg.conf file, if you made a backup.
You also need to remove the xorg-driver-fglrx or your manually installed drivers to get the 3D acceleration back, since it is provided by file /usr/lib/libGL.so.1.2 which belongs to libgl1-mesa package and which is moved to backup and replaced at the installation of xorg-driver-fglrx (or the manually built) package. In case the removal of the fglrx drivers fails to restore the file from libgl1-mesa, you have to reinstall the package by running:
Ubuntu's default desktop environment is Gnome. Sometimes people using Ubuntu want to try out KDE as well, though. If you're not sure what the differences are, you may want to read about my experiences with Gnome and KDE.
Even though these instructions are for KDE, the same principle applies for adding Gnome to Kubuntu or XFCE to Kubuntu or Ubuntu. Basically, you install the desktop environment, log out, and choose the desktop environment.
So in Gnome, go to Applications > Accessories > Terminal. This will open a terminal where you can type commands.
Then, in the terminal, type sudo aptitude update.
Please note that some people may tell you to install KDE using Synaptic Package Manager or apt-get.
Use aptitude instead, because it'll make KDE easier to remove later if you wish to do so.
Once you've updated, go ahead and install KDE with the command sudo aptitude install kubuntu-desktop.
The kubuntu-desktop metapackage will install the standard Ubuntu version of KDE with the appropriate artwork and defaults favored by Ubuntu.
If you want a lighter-weight version of KDE, do sudo aptitude install kde-core instead.
During the installation process, you should be asked whether you want to use KDM or GDM as your default display manager. If you think you'll use KDE more frequently, make KDM your default. If you think you'll use Gnome more frequently, keep GDM as your default.
The default can always be changed later by modifying the /etc/X11/default-display-manager file. For KDM, the file should read /usr/bin/kdm; for GDM, the file should read /usr/sbin/gdm
When KDE is done installing, type exit to get out of the terminal.
Then go to System and Log Out username.
To confirm the logout, click Log Out in the next dialogue box.
If you're using Dapper, once you get to the login screen, click on Options and then Select Session.
In older versions of Ubuntu (Breezy, Hoary, Warty), you would have a separate Session button instead of drilling down to Session from Options.
In the Sessions dialogue, select KDE and then Change Session.
Finally, before you log back in again, decide whether you want to change to KDE just for this session or if you want to make KDE your default desktop environment.
Then, log back in, and you should be using KDE.
To switch back to Gnome, just log out and select Gnome from the session menu.
If you later decide you don't want KDE any more, go back to the Gnome terminal and type sudo aptitude remove kubuntu-desktop.
¿PQ KDE en lugar de Gnome? Fácil, instálalo y saltará a la vista “sudo aptitude install kubuntu-desktop” (si prefieres apt-get pues con apt-get). Aprovéchate de que puedes tener todos los entornos gráficos que quieras para comprobar la usabilidad de cada uno de ellos.
Y Arkángel, bien uses Gnome o KDE, no olvides instalarte el gestor de ventanas Xgl, ¡¡¡es la releche!!!
WINE TIPS
- para desinstalar programas instalados con wine ejecutar "wine uninstaller"
- hay un gestor de ficheros en wine que sirve para ejecutar directamente desde allí los programas porque desde el gestor de archivos de linux no va muy bien. se llama "winefile". al parecer, no debe estar implementado completamente y no va muy bien.
- para configurar las aplicaciones instaladas: "winecfg"
How to restore Grub to your MBR using the Ubuntu 6.06 live cd
Posted By arsgeek On 23rd October 2006 @ 13:36 In Linux, Ubuntu, ArsGeek | 3 Comments
I’ve recently installed Vista as the third OS on my laptop. Of course, when I did, it blew away my MBR and my computer forgot all about grub. Then I couldn’t boot into Ubuntu and I was not a happy camper. Although truthfully, I expected this to happen, it being a Windows install.
Fixing this is surprisingly easy. Here’s how to do it:
Boot into the LiveCD.
Open a Terminal Session and become root by typing this:
sudo su -
Now let’s launch grub.
grub
We’re going to find out where Grub should boot from.
find /boot/grub/stage1
Your output should look something like this (it’s what I get) (hd0,2). That’s your hard drive/partition. Once we’ve got that info, we can tell grub where your root directory is, and where the MBR should be.
root (hd0,2)
setup (hd0)
Now all that’s left is to quit grub and restart
quit
shutdown -h now
Once your machine restarts, you should see the grub menu again and you can go on your merry way.
Enable The root Account
After the reboot you can login with your previously created username (e.g. admin). Because we must run all the steps from this tutorial as root user, we must enable the root account now.
Run
sudo passwd root
and give root a password. Afterwards we become root by running
su
------------------------------------------ lo anterior no me funciona en edgy eft server, pero hay otra posibilidad -----------------------------------------
Just some comments as I'm going throgh this How-To:
Sudo is
in Ubuntu for a reason and it should be used, so instead of enabling
root and setting a root password, run sudo w/ a ' -s ' argument:
sudo -s
That'll put you in as root and you won't have to prefix all of your commands with sudo.
In step #5, instead of restarting the box, you can reload the hostname via /etc/init.d/hostname.sh; faster then restarting the box.
-bdk
Alternativa más sencilla al editor de textos VI.
cuando estoy siguiendo un tutorial para instalar edgy eft server hay que hacer varias ediciones de ficheros de configuración. me gustaría poder usar el midnight commander pero no viene instalado por defecto y al principio puede no haber conectividad de red (y a lo mejor necesitamos modificar el fichero /etc/network/interfaces). en ese caso necesitamos usar un editor más sencillo y que venga en el CD de ubuntu.
He encontrado el editor "nano" que viene en el cd-rom y es sencillo de usar (al estilo del antiguo wordstar
Enviado por zizou el Jue, 05/10/2006 - 05:16Hardware
Buenas a todos, recien me acabo de actualizar mi ubuntu a Edgy Eft, me instale el nvidia-glx como normalmente se hace, y los restricted-modules que concuerden con mi kernel. me instalo los paquetes bien, pero cuando procedi a habilitar la aceleracion 3D con el comando "nvidia-glx-config enable" me sale esto...
Error: unable to load nvidia kernel driver! Be sure to have installed
the nvidia driver for your running kernel.
se supone que instalando el nvidia-glx no deberia dar este problema o no?
Mira a mi me paso lo mismo, prueba haciendo sudo dpkg-reconfigure -phigh xserver-xorg y probablemente tengas elegido el driver "vesa", cambialo por nvidia. Reinicia y listo aparece el logo de nvidia.
I always install X one package at a time. (you could
use tasksel)
# apt-get install xlibs
# apt-get install xutils
# apt-get install xbase-clients
# apt-get install rxvt
# apt-get install xterm
# apt-get install xserver-xfree86
# apt-get install fvwm
# apt-get install fvwm-icons
# apt-get install xfonts-75dpi
# apt-get install xfonts-base
# apt-get install xfonts-scalable
# apt-get install xlibs-dev
Getting X totally tuned up can sometimes be a
challenge. You may need to know the model and specs of your video card and
monitor. Run lspci to help figure out what video card
you have. Be careful when configuring XFree86. If you enter incorrect specs, your
monitor and video card could be damaged. The configure script will ask you
questions about your hardware. Below is an example of some of the answers I
gave:
autodetect= no
driver= depends on your video card
keyboard rule= xfree86
keyboard model= pc101
keyboard layout = us
mouse= /dev/psaux(for PS2 mouse on PS2 port)
mouse= /dev/ttys0(for serial mouse on "com1")
monitor setup= advanced
horizontal= from monitor spec
vertical= from monitor spec
depth= (depends on your hardware)
resolution= (depends on your hardware)
# emacs /etc/X11/XF86Config-4
mouse protocol= PS/2(yours may be different)
emulate3buttons= no(mine has 3 buttons)
The X environment and
window manager
The most personal component
of your X environment is your window manager. There are many different window
managers available, but I use fvwm, because it is versitile, fast, and
extremely efficient.
Login as user to
configure your Xinit resource configuration:
If you get stuck in X, you can usually exit immediately
by pressing the keyboard combination Ctrl+Alt+Backspace. This should take you back to the
console command prompt.
For more info and help,
read the "man pages" for XFree86:
] man XF86Config-4
] man XFree86
Customizing X
My preferences are below, (YMMV):
# emacs /etc/X11/XF86Config-4
keyboard section:
Option "AutoRepeat" "200 200"
Mouse Section:
Option "Resolution" "900"
To set the default X video mode, put it before the
others. Then restart X.
Remote display of X
applications
The coolest aspect of X is
its client-server design, which allows the remote display of
applications over a network. For example: You you can run an X-server on an old
(slow) laptop, and then run an X-client (application) on a different (fast)
computer. The application is displayed on the laptop's screen, and you interact
with the application with your laptop's mouse, and keyboard. The application
runs fast while using very little of the old laptop's RAM and CPU.
Additionally, an X-server is not needed on the computer that sends X-client
displays to other computers. The terms “server” and “client” may seem backwards
here, but they are correct. One X-server can accept connections from multiple
X-clients.
On the X-client side:
install xlibs, xutils, and xbase-clients
install the X applications that you wish
to run.
# emacs /etc/ssh/sshd_config X11Forwarding yes
restart sshd: # /etc/init.d/ssh restart
From the X-server side:
With your X-server and window-manager
running, fire up a local rxvt or xterm.
Login to the X-client machine with:ssh -X hostname
then run the X-client application (likexcalc) from hostname's command-line.
Ubuntu's default desktop environment is Gnome. Sometimes people using Ubuntu want to try out KDE as well, though. If you're not sure what the differences are, you may want to read about my experiences with Gnome and KDE.
Even though these instructions are for KDE, the same principle applies for adding Gnome to Kubuntu or XFCE to Kubuntu or Ubuntu. Basically, you install the desktop environment, log out, and choose the desktop environment.
So in Gnome, go to Applications > Accessories > Terminal. This will open a terminal where you can type commands.
Then, in the terminal, type sudo aptitude update.
Please note that some people may tell you to install KDE using Synaptic Package Manager or apt-get.
Use aptitude instead, because it'll make KDE easier to remove later if you wish to do so.
Once you've updated, go ahead and install KDE with the command sudo aptitude install kubuntu-desktop.
The kubuntu-desktop metapackage will install the standard Ubuntu version of KDE with the appropriate artwork and defaults favored by Ubuntu.
If you want a lighter-weight version of KDE, do sudo aptitude install kde-core instead.
During the installation process, you should be asked whether you want to use KDM or GDM as your default display manager. If you think you'll use KDE more frequently, make KDM your default. If you think you'll use Gnome more frequently, keep GDM as your default.
The default can always be changed later by modifying the /etc/X11/default-display-manager file. For KDM, the file should read /usr/bin/kdm; for GDM, the file should read /usr/sbin/gdm
When KDE is done installing, type exit to get out of the terminal.
Then go to System and Log Out username.
To confirm the logout, click Log Out in the next dialogue box.
If you're using Dapper, once you get to the login screen, click on Options and then Select Session.
In older versions of Ubuntu (Breezy, Hoary, Warty), you would have a separate Session button instead of drilling down to Session from Options.
In the Sessions dialogue, select KDE and then Change Session.
Finally, before you log back in again, decide whether you want to change to KDE just for this session or if you want to make KDE your default desktop environment.
Then, log back in, and you should be using KDE.
To switch back to Gnome, just log out and select Gnome from the session menu.
If you later decide you don't want KDE any more, go back to the Gnome terminal and type sudo aptitude remove kubuntu-desktop.
You want to back up that which you can't
readily restore from other sources.
You don't want to back up that which you
can readily restore from other sources. Or more importantly, should
restore from other sources to assure integrity (e.g.: following a system
security exploit).
You don't want to back up that which you
aren't interested in preserving.
My own backup script (/usr/local/sbin/system-backups) which I run weekly (or weakly).
Generally speaking, you're
not interested in:
/tmp
/usr (except for /usr/local)
bits and
pieces of /var
You absolutely want:
/home
/etc
/usr/local
You probably want:
Bits and
pieces of /var
(probably) /root (Hmmm...I should add that to
my script).
(possibly) /boot
Other local filesystems outside the FSB.
...the philosophy being
that you can reconstruct your distribution from package information (and would
probably benefit from an upgrade anyway). You can't recover localized
data and system configurations, from a generic image, CD, or net archive.
Protect what's valuable to
you.
It might also make sense to
create archives of your disk partitions (fdisk -l /dev/your-device-here) and related hardware information.
I like tar because of its universal access --
I can retrieve these archives from any system, anywhere. Not just Linux, not
just Unix. Other backup/recover tools offer greater functionality, but
generally reduce the flexibility of access.
My system backup script
follows. It backs up a series of directories using tar, verifies the archives, and shouts
frequently to all open terminals what's going on.
I'm not saying it's the
pinnacle of backup scripts, but it works for me. Typically run to 'batch' a
couple times a week, runs unattended for several hours.
The recovery strategy for
use with this script will vary on what you're recovering from. To recover a
single file or small set of files, load your backup tape, scan to the
appropriate archive (file mark), and untar the files, typically to a
"restore" directory, not directly into the target directory.
For a full system restore,
you'll want to install a base Debian system, pull your package list from
archive and restore packages to the current versions over a network or from
source media, then restore your archived partitions from backups.
You might also want to,
say, test for existence of media with "mt status", testing exit
value, and bailing if you've got no tape.
#!/bin/bash
# Create backups of /etc, /home, /usr/local, and...
We haven’t covered Debian much so far but,
although it’s quite a pain during installation and configuration, there are
some things it does particularly well. One of these is package management - the
act of adding, removing, and querying packages. You may have heard people
singing the praises of apt-get, the Debian package tool, wherever Linux users
group together. Well, when it comes to getting your computer back to a previous
state, users of most Linux distros have two choices: back-up your data and your
programs and restore everything, or back-up just your data and reinstall your
programs by hand. Both of which are quite painful no matter what distro you
use, and take more than a few minutes of your time.
For Debian users, there’s another option: back-up
your data as well as the names of your installed programs, then restore that.
Using Debian, type this command:
dpkg --get-selections > programs.txt
This will output the names of all the packages
you currently have installed and save it in programs.txt. You can now back-up
your data and ignore your programs. Once you’re ready to restore your data,
issue this command:
dpkg --set-selections < programs.txt
If you were smart enough to
partition your drive into at least three parts, this functionality means that
if you’ve broken your system, you can reformat and reinstall Debian, have it
use your untouched home
directory in the new install and run
set-selections to get the system back to where it was.
No se si os pasará a vosotros pero yo no soporto la nueva pantalla de arranque/cierre del sistema de Ubuntu Edgy. No es que no me guste sino que me oculta la información del arranque de manera que no sé lo que está ocurriendo ni si algo está fallando. Esto me parece inadmisible en una distribución de Linux así que he decidido quitar la pantallita de arranque.
Si os interesa quitarla y volver a arrancar con una interfaz de consola pero llena de mensajes informativos haced lo siguiente:
- Abrir una consola y ejecutar sudo gedit /boot/grub/menu.lst
- Buscar la cadena ## ## End Default Options ##
- Modificar la primera linea que contenga algo parecido a esto: kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/hda5 ro quiet splash
eliminando las opciones “quiet” y “splash”, de manera que quede algo como esto:
For a password protected share with read/write permission. 
No se si os pasará a vosotros pero yo no soporto la nueva pantalla de arranque/cierre del sistema de Ubuntu Edgy. No es que no me guste sino que me oculta la información del arranque de manera que no sé lo que está ocurriendo ni si algo está fallando. Esto me parece inadmisible en una distribución de Linux así que he decidido quitar la pantallita de arranque.