It’s not that big of a deal, but would it really be that big of a problem to deliver a proper .deb package for the driver installation? I had to let the Nvidia installer disable my Nouveau driver, I had to manually stop LightDM and I also had to correct the /usr/bin/gcc link, since Nvidia apparently doesn’t care about my CC environment variable. sudo service lightdm stop sudo rm /usr/bin/gcc sudo ln -s /usr/bin/gcc-4.6 /usr/bin/gcc What’s up with that?

Preparing your installation medium First you need to put your Debian image on a USB stick. You can do this by using the dd command; if is the input file, of is the output file. We are going to use the ISO as input and the USB device address as output. dd if=/home/orangensaft/Downloads/debian-wheezy-DI-rc1-amd64-netinst.iso of=/dev/sdb When it’s done you’ll see a new line, ready for input. At that point, you may restart your system and boot from USB. Installing Debian & initial setup I recommend keeping a second USB stick around to conveniently deliver missing firmware to the installer, although this is optional if they aren’t essential network or display drivers.

Most of these things never really bothered me on their own, but after some time it just starts to get annoying. Especially when all the mail you get is about how a file exists that you could easily and quickly delete, or how the configuration is just not right for another certain, convenient feature. How do I read mail? / Which client should I use? To read your mails, you could use the standard mail application. I suggest you try others, like mutt. It’s actually quite nice, if, like me, you just need a client to read local system mail. When it comes to more, you might want to check if your favourite E-Mail desktop application can read the system mail.

I started out with a manual installation on version 4.5.4. It was located in a /home/ folder rather than the /var/www/ directory, which gave me opportunity to think some more. So, let’s begin. Go to the folder your ownCloud installation is in and tar it, in case anything goes wrong. sudo tar -cjvf owncloud.tar.bz2 owncloud/ Since it’s now owned by root because of the sudo, make it yours now. sudo chown orangensaft:orangensaft owncloud.tar.bz2 Subscribe to the new ownCloud server repository. sudo vim /etc/apt/sources.list Add this line at the bottom: deb http://download.opensuse.org/repositories/isv:ownCloud:community/Debian_6.0/ / Then add the key, update your repositories and install owncloud.

Soo, I was told that the font I use isn’t a proper coding font and I should use Source Code Pro. Fine. But if we’re already installing fonts, let’s download Source Sans Pro aswell. Source Code Pro is obviously for development environments, while Source Sans Pro is meant for user interface usage. Installing fonts on a GNU/Linux machine is really simple; you just have to move them to a /usr/share/fonts/ folder and update the font cache. Thanks to Linux And Friends for providing me with this solution. Alright, let’s begin. Download the font packages wget http://sourceforge.net/projects/sourcecodepro.adobe/files/SourceCodePro_FontsOnly-1.017.zip wget http://sourceforge.net/projects/sourcesans.adobe/files/SourceSansPro_FontsOnly-1.038.zip Extract the files

I’ve always loved to start programmes automatically. Just boot up the computer, maybe even log in automatically if it’s a desktop at home, and start all the programmes you need. It took me quite a while, but I figured out the one and only, perfect way to do that: *.desktop files. Let’s go to our applications folder, which should contain most of the *.desktop files responsible for your Applications menu. cd /usr/share/applications/ Let’s assume you want to autostart guake. Check for folder contents with ls or find the programme you want to auto start with ls | grep guake. Then, copy that file to your autostart folder.

Wait, what’s going on? Device not managed? But I didn’t even do anything I swear! Here’s how to fix it, solution found on ask Ubuntu. Open up your NetworkManager config file and change the line managed=false to managed=true. sudo vim /etc/NetworkManager/NetworkManager.conf Then, restart the network-manager service. sudo service network-manager restart Everything should work fine now.

I know of no clean way to detect an unplugged screen, so I figured I’d force re-detection with a cron job. To detect the monitors I’m using disper, you can get it from the Wheezy and Sid repositories. Let’s open up our crontab. crontab -e If you’re doing this for other users too, you may use sudo crontab -eu username Now add a new entry: 0-59 * * * * DISPLAY=:0.0 disper -ld auto > /dev/null This will automatically detect (-d auto) and list (-l) all monitors every minute. Of course, you can also use xrandr: 0-59 * * * * DISPLAY=:0.

All you have to do is install the General Purpose Mouse interface, GPM. sudo apt-get install gpm As soon as the installation finishes you’re ready to use your mouse.

If you are using XFCE with GDM and are tortured by the “slow keys”-feature after holding down Shift, you might want to take a look at this: bugzilla.redhat.com/show_bug.cgi?id=816764 I don’t remember when I had this problem, but I feel it was sitting around as a draft long enough. I hope this can help someone out there! I can’t test it anymore, since I’ve been using MATE for some time now.