Since I know you're new to Ubuntu, here's a few general comments.
1. Put that partition in your /etc/fstab
First off, in your script you use the line sudo mount -U 80EA3F58EA3F49A4 /media/ubuntu/LENOVO to mount your NTFS partition. I would suggest to add that partition to your /etc/fstab and map it to the UID of your partition there. Since you're on a single-user system, you may want to have an entry similar to this in your /etc/fstab:
UUID=80EA3F58EA3F49A4 /media/ubuntu/LENOVO ntfs rw,exec,uid=1000,gid=1000,umask=0002,nls=utf8,noauto 0 0
Most importantly, this tells the system to bind the mount point /media/ubuntu/LENOVO to the UID 80EA3F58EA3F49A4. That way, in the future (and thus in your script) you can simply use sudo mount /media/ubuntu/LENOVO instead of sudo mount -U 80EA3F58EA3F49A4 /media/ubuntu/LENOVO. If the UID changes in the future (because you reformat the partition), it's better to have only one central place, /etc/fstab, to edit rather than 20 scripts you may have lying around.
This also mounts the filesystem with various common options for NTFS partitions: read-write mode (rw), permit the execution of binaries (exec), make all files and directories on the file system belong to the user 1000 and group 1000 (uid=1000,gid=1000) (that's your normal user), set the permissions bits for all files and directories to 775 (umask=0002), set the character set for filenames to UTF-8 (nls=utf8), and do not mount the partition automatically (noauto). Refer to fstab(5) and mount(8) for more information. I personally find it convenient on my single-user system to be able to access all files on my NTFS partitions without having to use sudo, but of course your mileage may vary.
You may also want to drop the noauto option. Then, the partition will be mounted whenever the command mount -a is run, and in particular, at boot time (and thus, it would typically be mounted the whole time). Then you wouldn't even have to use the mount and umount commands in your script at all, but I don't know if you want that.
2. Don't use umount with -l
From umount(8):
The recommended use-case for umount -l is to prevent hangs on shutdown due to an unreachable network share where a normal umount will hang due to a downed server or a network partition.
So this option is at least rather unusual to use in your case.
Whether you run umount with or without -l, a partition will not be force-unmounted (there's the -f option for that). Rather, when you don't use -l and the partition is still busy, the unmount will simply fail and return an error message; when using -l and the partition is still busy, it will be detached from the filesystem hiearchy now (meaning you cannot access it anymore), but pending I/O operations will be silently completed in the background.
Since there shouldn't be any pending I/O operations after you've run swapoff, by not using -l you would at least notice if something is odd, because if the partition is unexpectedly still busy then the unmount command would output an error message.
3. Add error handling
You execute all commands in sequence, but don't check whether the previous command worked. So, e.g., if the mounting fails, then the swapon command will be nevertheless attempted but fail, and then your game will start even though the swap was not activated.
Try this:
#!/bin/bash
echo "Mounting partition..."
sudo mount /media/ubuntu/LENOVO
if [ $? -ne 0 ]; then
echo "Could not mount partition, mission aborted." >&2
exit 1
fi
echo "Opening swapfile..."
sudo swapon /media/ubuntu/LENOVO/swapfile.img
if [ $? -ne 0 ]; then
echo "Could not activate swap, mission aborted." >&2
exit 1
fi
steam steam://open/minigameslist
echo "Closing swapfile..."
sudo swapoff /media/ubuntu/LENOVO/swapfile.img
echo "Unmounting partition..."
sudo umount /media/ubuntu/LENOVO
echo "Mission accomplished!"
Best Answer
I'm not quite sure whether a swap file on an NTFS partition is the best solution for you. You may be better off creating an actual swap partition on your hard drive and use that. You could use a tool such as
gpartedto resize your NTFS partition, reducing it by the size you want your swap file to be, say, 2 GB. Then you could allocate a 2 GB swap partition on the newly freed space on your hard drive.(Of course that assumes you have at least 2 GB of free space on your NTFS partition. But that's just the same space a swap file would consume as well.)
The reason I'm saying that a swap file on your NTFS partition may not be the right solution is because it may impact performance significantly, for two reasons:
Your NTFS partition is not fresh, it's been used for a long time, and your 2 GB swap file will likely be fragmented. Hence, reading and writing to that swap file may be much slower since it is not a contiguous memory region (as opposed to a swap partition). See this excellent answer on Server Fault for some more information.
On top of that, the NTFS drivers are rather slow, as mentioned in the Arch Linux forums in the thread that you linked to yourself.
If you are nevertheless determined to create a swap file on your NTFS partition, that's easy. All you have to do is this:
Ensure your NTFS partition is mounted somewhere. For the sake of example, let's assume the mountpoint for your NTFS partition is
/media/windows.Create a swap file with 2 GB on your NTFS partition like so:
That's it really. Those are exactly the instructions from that Arch Linux thread, I merely changed the size of the swap file to 2 GB.
The whole rest of the Arch Linux thread only deals with the issue that the OP wants to have his swap file enabled automatically at boot, so that they don't have to run that
swaponcommand every time after rebooting the system. For that to work, you have to somehow make sure that the NTFS partition is mounted before the swap is enabled, since the swap file is on the NTFS partition, and that can get a bit messy, which is why someone there suggests creating asystemdservice to enable the swap after the NTFS partition is mounted.But if you only want to test how a swap file on your NTFS partition solves the problems with your game, you don't need to worry about that right now. You can just go ahead with the above steps. It simply means that, every time you reboot your system, you have to re-run steps (1) and (3) above, i.e., make sure your NTFS partition is mounted (hint: put it in your
/etc/fstaband have it mounted at boot time) and run thatswaponcommand. Note that you only have to perform step (2) once: Once the swap file is created, you don't need to create it anew. Unless you want to change its size.Then, if that works for you and you're really happy with the results and you can play your game and one day you're annoyed that you have to run that
swaponcommand every time you reboot your system, then you can worry about writing asystemdservice to run thatswaponcommand every time automatically at boot. And then, if you have trouble with that, you're welcome to ask another specific question about that problem here. Or perhaps, by then you will like Ubuntu so much that you decide to get rid of Windows 7 and install Ubuntu for good. ;)