I am trying out the great new Fedora 7 now, with the Gnome desktop.
I wanted to remove the desktop icons / launchers that were on the desktop (Computer, adder1972's home og Trash).
It turned out I had to install "gconf-editor" (not installed by default apparently). As root I ran:
yum install gconf-editor
Then, in Configuration Editor under System Tools in Applications, I chose "apps" "nautilus" and "desktop". Then I could just remove the icons / launchers that I wanted to remove.
[gconf-editor is a part of Gnome, and works in i.e. Ubuntu as well]
Thursday, June 14, 2007
Sunday, June 10, 2007
Linux Mint 3.0 Cassandra
Linux Mint 3.0 is out. I downloaded the Ubuntu based distro and tried it in Virtualbox. I just used the same virtual machine as I have installed Ubuntu Feisty on, and just booted it from the CD ISO.
The distro looked great and supports lots of media files right out of the box. The LiveCD I tried was based on Gnome, but did only have one panel on the bottom part of the screen.
The virtual machine I used has just a 5GB virtual hard drive allocated. I have already installed Feisty on it, which filled about 2.5GB and I have allocated 512MB to swap (a bit much). A bit more than 2GB was free. Using the Mint installer, I made a new partition of the free space in the "Feisty partition", so I got an approximately 2.3GB partition that Mint could use for root. I set the installer to use the same swap-partition as Feisty does.
The installation went quick and without any problems.
When I rebooted, GRUB now had the Mint and Ubuntu Feisty boot options. I tried Mint. Then, when I wanted to log in, I got the error message: "GDM could not write your authorization file." etc. I have gotten this message one before (I don't remember when) when my root partition was full.
I decided to delete OpenOffice and then try to log in. I rebooted and started Mint in safe mode. At the command line (Ctrl+Alt+F1), as root, I typed:
apt-get remove --purge openoffice.org-*
This removed about 230MB of files. After it had finished, I typed "reboot", and started Mint the normal way.
The distro looked great and supports lots of media files right out of the box. The LiveCD I tried was based on Gnome, but did only have one panel on the bottom part of the screen.
The virtual machine I used has just a 5GB virtual hard drive allocated. I have already installed Feisty on it, which filled about 2.5GB and I have allocated 512MB to swap (a bit much). A bit more than 2GB was free. Using the Mint installer, I made a new partition of the free space in the "Feisty partition", so I got an approximately 2.3GB partition that Mint could use for root. I set the installer to use the same swap-partition as Feisty does.
The installation went quick and without any problems.
When I rebooted, GRUB now had the Mint and Ubuntu Feisty boot options. I tried Mint. Then, when I wanted to log in, I got the error message: "GDM could not write your authorization file." etc. I have gotten this message one before (I don't remember when) when my root partition was full.
I decided to delete OpenOffice and then try to log in. I rebooted and started Mint in safe mode. At the command line (Ctrl+Alt+F1), as root, I typed:
apt-get remove --purge openoffice.org-*
This removed about 230MB of files. After it had finished, I typed "reboot", and started Mint the normal way.
Wednesday, April 25, 2007
Installation of Ubuntu 7.04, Feisty Fawn (10 easy steps to success)
Just found a good site with tips for installing Ubuntu 7.04:
Essential Ubuntu
Also, check out this site for compatibility tests:
Linspire Compatibility Tests
Essential Ubuntu
Also, check out this site for compatibility tests:
Linspire Compatibility Tests
Sunday, April 22, 2007
Installed KDE on Debian
Decided to try to install KDE. Debian comes with Gnome as default.
Used "Synaptic Package Manager" and chose "KDE-desktop environment". Ran through the list of included programs, and deselected some applications. When I pressed "Apply" I was prompted for a install CD. I only had the first install CD-iso.
Then I remembered what we used to do in earlier versions of Ubuntu - edit the "sources.list". This list specifies which repositories the system shall fetch its packages from. It is located in /etc/apt. In order to edit this system file, I needed root privileges. As I have discussed earlier, I have installed the "sudo" command that I am used to use under Ubuntu.
sudo gedit /etc/apt/sources.list
enabled me to edit the list.
It read:
deb cdrom:[Debian GNU/Linux 4.0 r0 _Etch_ - Official i386 CD Binary-1 20070407-11:55]/ etch contrib main
deb http://debian.savoirfairelinux.net/debian/ etch main
deb-src http://debian.savoirfairelinux.net/debian/ etch main
deb http://security.debian.org/ etch/updates main contrib
deb-src http://security.debian.org/ etch/updates main contrib
I commented out the CD-rom and saved the file, modified file reading:
# deb cdrom:[Debian GNU/Linux 4.0 r0 _Etch_ - Official i386 CD Binary-1 20070407-11:55]/ etch contrib main
deb http://debian.savoirfairelinux.net/debian/ etch main
deb-src http://debian.savoirfairelinux.net/debian/ etch main
deb http://security.debian.org/ etch/updates main contrib
deb-src http://security.debian.org/ etch/updates main contrib
Then, I pressed "Apply" again, and then the install started downloading files from the net without prompting me for the CD.
After the install was completed, I logged out of Gnome, and chose KDE... and it worked!
Used "Synaptic Package Manager" and chose "KDE-desktop environment". Ran through the list of included programs, and deselected some applications. When I pressed "Apply" I was prompted for a install CD. I only had the first install CD-iso.
Then I remembered what we used to do in earlier versions of Ubuntu - edit the "sources.list". This list specifies which repositories the system shall fetch its packages from. It is located in /etc/apt. In order to edit this system file, I needed root privileges. As I have discussed earlier, I have installed the "sudo" command that I am used to use under Ubuntu.
sudo gedit /etc/apt/sources.list
enabled me to edit the list.
It read:
deb cdrom:[Debian GNU/Linux 4.0 r0 _Etch_ - Official i386 CD Binary-1 20070407-11:55]/ etch contrib main
deb http://debian.savoirfairelinux.net/debian/ etch main
deb-src http://debian.savoirfairelinux.net/debian/ etch main
deb http://security.debian.org/ etch/updates main contrib
deb-src http://security.debian.org/ etch/updates main contrib
I commented out the CD-rom and saved the file, modified file reading:
# deb cdrom:[Debian GNU/Linux 4.0 r0 _Etch_ - Official i386 CD Binary-1 20070407-11:55]/ etch contrib main
deb http://debian.savoirfairelinux.net/debian/ etch main
deb-src http://debian.savoirfairelinux.net/debian/ etch main
deb http://security.debian.org/ etch/updates main contrib
deb-src http://security.debian.org/ etch/updates main contrib
Then, I pressed "Apply" again, and then the install started downloading files from the net without prompting me for the CD.
After the install was completed, I logged out of Gnome, and chose KDE... and it worked!
Installing Debian
I decided to give Debian a try. I have heard so much about it, and since I have been using the Debian-based Ubuntu for a while, I wanted to check it out.
Debian has just been released in ver 4.0. Debian is released on 21 CDs, but with a broadband Interweb connection, you will only need the first.
After preparing a system in Virtualbox, and preparing the partitions, I was ready for the install. Debian uses an installer like the older versions of Ubuntu. It is quite easy to use (except for the formating issues described earlier). In addition to the first install CD, some packages where fetched from the net.
Booting and starting my new system, was very much like Ubuntu (not surprising). The Gnome desktop is default for Debian, and it looked more or less like Ubuntu (but was not brown).
I decided to check if my system was up to date, using the " sudo aptitude update" command. To my surprise, that didn't work. In fact I got a lot of error messages.
After searching on the Interweb, I discovered that the "sudo" command isn't activated or installed by default in Debian. Also, Debian uses root-account (disabled in Ubuntu) and user-accounts. In order to get sudo-to work I needed to switch to root:
su -
And then install sudo:
aptitude install sudo
Then I needed to give my user privileges to run "sudo". Running visudo as root, I edited the line reading
root ALL=(ALL) ALL
and substituded "root" with my username
adder1972 ALL=(ALL) ALL
After quiting the terminal and restarting it (since I don't know how to log out as root yet ....), I was now able to run "sudo" as my regular user (+ password, of course)
To test that everything worked, I typed
whoami (answer: adder1972)
and
sudo whoami (answer: root)
Debian has just been released in ver 4.0. Debian is released on 21 CDs, but with a broadband Interweb connection, you will only need the first.
After preparing a system in Virtualbox, and preparing the partitions, I was ready for the install. Debian uses an installer like the older versions of Ubuntu. It is quite easy to use (except for the formating issues described earlier). In addition to the first install CD, some packages where fetched from the net.
Booting and starting my new system, was very much like Ubuntu (not surprising). The Gnome desktop is default for Debian, and it looked more or less like Ubuntu (but was not brown).
I decided to check if my system was up to date, using the " sudo aptitude update" command. To my surprise, that didn't work. In fact I got a lot of error messages.
After searching on the Interweb, I discovered that the "sudo" command isn't activated or installed by default in Debian. Also, Debian uses root-account (disabled in Ubuntu) and user-accounts. In order to get sudo-to work I needed to switch to root:
su -
And then install sudo:
aptitude install sudo
Then I needed to give my user privileges to run "sudo". Running visudo as root, I edited the line reading
root ALL=(ALL) ALL
and substituded "root" with my username
adder1972 ALL=(ALL) ALL
After quiting the terminal and restarting it (since I don't know how to log out as root yet ....), I was now able to run "sudo" as my regular user (+ password, of course)
To test that everything worked, I typed
whoami (answer: adder1972)
and
sudo whoami (answer: root)
Subscribe to:
Posts (Atom)
