After my return to Debian I thought I could let you know about some of the pitfalls for returning Ubuntu users.
This is in random order, but more or less how it occurred to me.
- I used Debian testing (Codename “squeeze”) 64-bit. The installation came from a USB stick generated using Unetbootin. Unetbootin and booting the Netinstall installer worked just fine.
- The netinstall installer is not graphical at all, it’s good old text menus. I didn’t mind much because I used to be able to navigate the goddamn Debian installer blindly back in my sysadmin days. I wouldn’t recommend this for new users, though. I hear there’s a graphical installer on the full Debian CD (instead of the netinstall disc), so you’re probably better off with that.
- After installation, the machine wouldn’t boot. GRUB had fucked things up and wouldn’t even launch. This can happen sometimes if you install a new version of GRUB 2 over an old GRUB 1. I had to boot the unetbootin stick into rescue mode and do grub-install /dev/sda and update-grub to get it to work.
- Once up, WLAN wasn’t working. This is due to the Realtek 8192SE chipset in my netbook, which isn’t part of the mainline kernel yet. I downloaded some driver source from Realtek, did apt-get install build-essential and got the kernel headers. Then I could compile the driver, load it and boom, I was on the wireless LAN. Does this in any way, shape or form work for the average user? No, it doesn’t. But on the upside, Ubuntu can’t handle this WLAN chipset either.
- I didn’t have any 3D acceleration (NVIDIA) yet, and Debian is very much against non-free software so they don’t include a proprietary driver manager like Ubuntu does. On Ubuntu, NVIDIA drivers are a one click thing. On Debian, I instead downloaded the binary NVIDIA proprietary driver installer from NVIDIA, entered a text shell, killed GDM and X, installed the driver, wrote out a default xorg.conf file using Xorg –config, changed the driver to nvidia and restarted GDM. This gave me 3D acceleration. Since the NVIDIA proprietary driver detects my screen’s DPI wrong, my fonts were all too large at this point. I couldn’t find a graphical way to configure this, so I just added this to xorg.conf:
- Later I started on a quest to enable 3D window effects and all that Compiz eye candy. The official documentation says to install some compiz packages and then a simple
compiz --replacewould take care of things. This didn’t go down well on my system, no window manager comes up so I end up with X windows but without borders or decorations. I’ll have to investigate a bit more.
- Mounting my Samba-based file server’s shares didn’t work with smbfs/cifs. I usually want my Samba shares to look more or less like normal UNIX directories on my GNU/Linux machine, that’s why I normally mount them in using cifs/smbfs. I don’t want to use GNOME’s server browser and style of mounting, it’s different and breaks in a lot of situations that I’d prefer would work transparently. So I tried mounting things, using the exact same /etc/fstab as on my Ubuntu box. But on Debian I get “Operation not permitted.” Apparently the authors decided that normal users should never, not under any circumstances be able to mount CIFS filesystems, and Debian is now following these instructions. It’s sort of inconvenient to mount these shares as root. I’ll see if I get used to it.
# NVIDIA proprietary options
Option "UseEdidDpi" "FALSE"
Option "DPI" "100 x 100"
To be fair to Debian, this is still a testing release. But the nature of the problems I had doesn’t make me very optimistic that they can be fixed automatically in a final release. Maybe the graphical installer would have taken care of some of them, I don’t know. I might try out.
This is not to say that I’m unhappy with Debian. It is a stable, free (in all senses), universal operating system. It works really well. It keeps my conscience white as a flower. It’s just not for everyone, and I hope some of the examples above show why.