Tag Archives: Linux

SDU m-drive Personal Network Folder on Linux Machines

I’ve written this guide before somewhere, but always fails to find it when I need it, so here is again. A guide for students and employees at University of Southern Denmark SDU for mounting their personal folder, the m-drive, on a Linux machine.

First step is to figure out what the path to your m-drive is… on a Windows machine find the folder, right click and select properties. On the tab “DFS” there is a full path to the folder. The path displayed in the title bar, which includes something like “\dfs\data” in it, is not the right one. For employees of the Technical Faculty the path currently is: “\\tek-data0a.tek.c.sdu.dk\tekansatte”

You need “smbfs” and “cifs-utils” installed on your machine. On an Ubuntu machine write: “sudo apt-get install smbfs” in a terminal and you’ll get all the necessary components.

You can now mount the m-drive from a terminal with the following command:

sudo mount -t cifs -o username=<username>,domain=<domain>,password=<password>,iocharset=utf8,codepage=unicode,uid=1000,gid=1000 //tek-data0a.tek.c.sdu.dk/tekansatte/<username> /mnt

where you need to change <username>, <password> and <domain> to reflect your information. Also the path, in this case “//tek-data0a.tek.c.sdu.dk/tekansatte/<username>” should be changed to what you were seeing in the properties of the m-drive. Notice the backslashes have been changed into forward slashes.

For a permanent mount add the following to fstab:

//tek-data0a.tek.c.sdu.dk/tekansatte/<username>       /var/m-drive    cifs    credentials=/root/.smbpasswd_mdrive,_netdev,iocharset=utf8,codepage=unicode,uid=1000,gid=1000

where the credentials are stored in a file in the /root folder.

See here, here and here for more information, including credentials, _netdev and isocharset.

Kernel Panic

Recovering encrypted home folders in Ubuntu

Yesterday was my first day back in the office after a 6-months stay at UCSC and some leave and obviously my computer insisted on having a number of updates installed immediately when I got it started. A distribution upgrade to Ubuntu 11.04 was available, so I decided to go with that. After the download was done, and about halfway through the installation of the updates the computer ran out of disk space… and got completely stuck. Lots of I/O errors flooding the consoles, the installation process not getting anywhere, unable to open and close programs etc. I left the computer running, but eventually it crashed completely and rebooted. Next step was kernel panic… so it was time for a reinstall.

I booted into Ubuntu 11.04 Live from a CD and got access to the machine. Next step was to get the files out of my encrypted home folder. The home folder contained two files, a .desktop file and a readme file. The desktop file did nothing but make Nautilus complain about something untrusted and the readme tells you to run ecryptf-mount-private. That resulted in an error, basically saying that the home folder is not set up correctly, but no information on what is wrong, or how to correct that. Instead your left on your own. After googeling and trying several suggested solutions I found a method to get access to the encrypted folder. All you need is your old username and login password. No need for the encryption key / mount password.

First mount the partition with your home folder somewhere, for example in /mnt:

sudo mount /dev/sdXXX /mnt

Then move the existing home folder of the live system to somewhere else:

sudo mv /home /cdhome

Now make a symbolic link from the old home folder in the mount you did and to the root of the live system:

sudo ln -s /mnt/home /home

Then create a new user with the username that matches the username you had on the system with the encrypted home folder:

sudo adduser xyzw

and go through all the questions. Finally, su into that username:

sudo su xyzw

and with a little luck, you will be asked for the login password that matches the encrypted folder. That password is the last login password you had on the system the folder came from, not the password you just made when you created the user in the previous step.

First impressions: Hardy Heron (beta) and VMware Workstation 6.5 (also beta)

I just read a blog post on the Planet Gnome RSS feed by a guy who calls him self ChipX86 who said the new beta of VMware Workstation 6.5 was out. Being a major fan of Workstation since version 5.5 i decided it had to try it out immediately.

The new killer feature is obviously the Unity feature, which some might have seen in Fusion, which is VMware’s Workstation edition for MacOS X. Unity allows applications running in the guest operating system, to be accessed in the host operating system. So you could start Internet Explorer (if for example your workplace insists on using an intranet web-application that will only work in IE6… bastards), minimize the whole Windows OS, and enjoy your normal favorite flavor of Linux only slightly marred by the sight of IE6 running.

There’s lots of new stuff in version 6.5 as well, apart from just Unity. You can read them all at VMware’s documentation, but the most important ones are probably:

  • support for 3D acceleration in Windows XP – good when your developing code using Delta3D for your master thesis :-)
  • GUI for manipulating virtual network settings on Linux hosts

There’s plenty of other new stuff as well. The blog post has a pretty good walk-through of the best features of Unity.

Installation and Configuration

The download is the usual 200+ MB .tar.gz file. Un-packaging the file results in the expected vmware-install.pl script which must be run as super user. Starting the installation process the first message received was a warning that my existing Workstation 6.0 installation would be removed first. Not exactly unexpectedly but still kind of annoying. It would have been nice to have been able to keep a non-beta version installed along the beta.

Graphical installation... sort of.

The installation ran smooth, and soon asked for permission to run the vmware-config.pl script. I can’t remember when I last installed a version of VMware that didn’t require the infamous vmware-any-any patch to work on my machine, so I was actually expecting this would prove problematic. But to my surprise everything ran quietly and perfectly.

Starting Workstation after the installation gave another pleasant surprise, when the program informed me that I had to run is as super user, to load some modules into my running kernel. Much better that the “thinking-for-while-and-then-not-starting” thing that happened in version 6 when there was a problem with the modules. After aborting and restarting the program with sudo, I got a very handy graphical window showing the loading of the modules. Nice touch.

But all is not well… because right after that a new dialoge informed me that the program would be running in debug mode, which could not be turned off, and that debug mode would result in significant performance loss. To bad… it was probably to be expected, but I would actually have liked a warning before installation, especially since I had to un-install my Workstation version 6 first. I’m pretty sure the documentation says something about this some where, but a bit more prominent warning would have been nice.

Debug mode... blast!

Running Workstation 6.5 beta 1

I have just been running this new version for an hour or two, so it’s hard to come with a solid conclusion about Workstation 6.5 beta 1. Most stuff seem to be working. Programs, networking etc. I can definitely say that I didn’t get any performance improvement, but that was to be expected with all this debugging stuff. But to be fair, I didn’t really get a huge loss of performance, so I guess I’m going to have some more testing to get a qualified opinion on that.

Working as expected

So… what about Unity? Well, it works. Sort of… It’s definitely not perfect, but it can be used. Lots of times moving around the windows will result in them not getting updated/redrawn, and other strange things. But it will mostly work. I used Visual Studio, which is one of my primary reasons for using Workstation in the first place, with unity on my normal desktop for a while, and it worked fine. No real problems using the programs, and you get used to using your normal Linux productivity tools along side of the Windows apps really fast. It’s fantastic to finally be able to use Windows programs on multiple desktops, for example. That’s one the features is miss the most, when I’m finally using Windows.

Mmmm Unity

Using Unity

Unity seems to be working quite good, event though it seems to suck a lot of resources from the machine when running programs. I managed to crash it a couple of times, and at one time it actually took down Ubuntu with it. But it’s almost worth it, being able to use those few essential Windows apps, without seeing that nasty little Start button.

Rendering errors...

Further Testing

So that was just the very first and very few impression from using Workstation 6.5 beta 1 for about one and a half hour. I’ll probably give some more work tomorrow, where I need to do some .NET development, and see where it leads. I have another machine running Workstation as well, so should the need arise to use version 6.0, I’m going to be able to use that one. If you’re not so lucky, and you need a stable Workstation, you should probably wait a little while before going 6.5. But don’t miss out on trying Unity if you get the chance. I’m already looking forward to enabling some of my desktop effects, and seeing what Unity are going to do about that.