Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm a new sysadmin in the making, have learned that I need to have /tmp and /home directories on separate partitions in order to prevent possibilities of privilege escalation through hard links based attack. Unfortunately my vps host doesn't allow partitioning at all! With that, I'm left with two options...

1) either abandon the host, 2) Ask the experts if this is a serious issue, and if it, then if there is any other way through which we can prevent hard links based attacks!

Are there any further disadvantages of not being able to create partitions in future course of vps management journey?

Looking forward for guidance in this matter. Thanks for your help.

share|improve this question
What do you mean that they don't allow partitioning? That they don't have any easy way to provide it, or explicitly don't allow it? If your VPS has some kind of console access you should if nothing else be able to do a manual reinstall, setting up the partitions the way you want it. – andol Mar 7 '14 at 6:09
You might be able to setup a loopback file system for those mount points. – toppledwagon Mar 7 '14 at 6:17
@toppledwagon, is it ok to put the tmp directory on a ssd storage backed vps on a loopback file system? – Vishal Mar 7 '14 at 6:23
Thanks folks for replying, but Digitalocean doesn't allow partitioning! – Vishal Mar 7 '14 at 6:35
@Vishal then don't do a separate partition, but file and mount it using loopback. – neutrinus Mar 7 '14 at 6:38

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.