Looking for comments on a replacement for /home

Can-ned Food · 11-25-2015, 04:03 PM

Sure, you can just go and keep mounting to '/home/.', but as I'm expanding the definition to include all files related to usage data — i.e., files which would need special attention when migrating to a different system —, which features stuff previously contained in '/home/.' but also would include some content previously placed in '/etc/.' or '/var/.'.

My best choice thus far is '/uden/.', which refers to ‘usage den’, but I wonder what others would think of that.
What do you think of that, or what would you suggest?

MensaWater · 11-25-2015, 04:13 PM

A common location used for many application installations has been /opt. Some 3rd party apps put things there by default. Typically you'd want to make that a separate filesystem so application data doesn't fill up your root filesystem.

However, you really can make your own directory structure for applications.

Be sure you know what your app is creating though. There are some (e.g. Oracle) that will put small files in /etc or /var even though the bulk of what they do installs where you tell it.

jefro · 11-25-2015, 05:05 PM

How about /data ?

Emerson · 11-25-2015, 05:20 PM

man hier - keep your system standards compliant.

Rawcous · 11-26-2015, 08:11 AM

Hello,

Personally I currently leave /etc, /var, /home where nature originally intended and simply add an additional drive to my system and use that as a backup device. So simply put mount the secondary disk at the required location and via a weekly cron copy the files to that device, i.e.

Code:

find /etc | cpio -pdmuv /media/MountLocation (copies data to /media/MountLocation/etc/....)
find /var | cpio -pdmuv /media/MountLocation (copies data to /media/MountLocation/var/....)
find /home |cpio -pdmuv /media/MountLocation (copies data to /media/MountLocation/home/....

Using the above you have a nice simple way of maintaining your directory structure, file permissions, etc of the data on the secondary device.

Regards,

Rawcous