I would like sdb2 (/backup) to be used for an expanded owncloud setup.
However I can only write as root to that drive ( ie when copying and pasting files)
I have to assume I borked fstab, but since I never mess with I am unsure what I am doing and need expert advice:
here is a copy of what it currently is:
I would recommend that you add “noexec” to the fstab options, if this is only for backups. That prevents programs from being run directly from that file system.
And of course that advice is poerfectly vallid. As setting all permissions to any dirctory/file will make it readable, writebal, executable by all the users. But those permission are not invented for nothing. Thus understanding them and apply them correctly may be a good idea.
I know that you know. It is allways difficult to give detailed advice on such a theme because the word “backup” does not explain much. Is it a backup the system manager makes, will the users maintain their own backups there, etc.
The only thing I wanted to stress to the OP the beside following your advice, it would be better to think over what he wants and then how to achieve that.
First off thank you for your quick responses, it is appreciated.
I am a home user putzing around with the using owncloud to get away from samba file sharing. This would also allow me to bail from dropbox and take control of my data (killing 2 birds with one stone)…
The files would be accessible on all of the linux boxes via webdavs in dolphin (or the android app for all of the other devices used by the family).
I was planning on using dev/sdb2 for the following:
(1) a subfolder called /dev/sdb2/backup/share for expanding the local external storage in owncloud.
maybe I am naive but wouldn’t owncloud generally control permissions?
(2) a subfolder called /dev/sdb2/backup/back_in_time/ for using an application called back in time to act as an automated backup of important files on that computer.
You can not use it like that. /dev/sdb2 et al are device special files, notdirtors where you can cre file/sub-dirctories. These device special files represent the file systems. File systems must be mounted somewhere in your directory tree to mmk the directriees/files n them aivalable.
I’m not familiar with owncloud, but unless it’s doing something really weird, your disk /dev/sdb2 is mounted as the DIRECTORY ‘/backup’, just as /dev/sda1 is mounted as ‘/’ (the root directory), /dev/sda2 is mounted as ‘/home’, and so on. So you could make subdirectories called ‘share’ &c under that…