Re: Suggested new user link command

Tony Wallace writes: > On 02/05/18 01:35, Bernd Petrovitsch wrote: >> Hi all! >> >> Top-quoting is evil BTW. >> >> On Wed, 2018-05-02 at 00:17 +1200, Tony Wallace wrote: >>> Two issues here: >>> 1) Use case (which I have) >>> 2) Permissions >>> >>> 1) Use case >>> >>> I am

Re: Suggested new user link command

Tony Wallace writes: > On 02/05/18 01:35, Bernd Petrovitsch wrote: >> Hi all! >> >> Top-quoting is evil BTW. >> >> On Wed, 2018-05-02 at 00:17 +1200, Tony Wallace wrote: >>> Two issues here: >>> 1) Use case (which I have) >>> 2) Permissions >>> >>> 1) Use case >>> >>> I am trying to build a

Re: Suggested new user link command

On 02/05/18 01:35, Bernd Petrovitsch wrote: > Hi all! > > Top-quoting is evil BTW. > > On Wed, 2018-05-02 at 00:17 +1200, Tony Wallace wrote: >> Two issues here: >> 1) Use case (which I have) >> 2) Permissions >> >> 1) Use case >> >> I am trying to build a backup system. To avoid duplication of

Re: Suggested new user link command

On 02/05/18 01:35, Bernd Petrovitsch wrote: > Hi all! > > Top-quoting is evil BTW. > > On Wed, 2018-05-02 at 00:17 +1200, Tony Wallace wrote: >> Two issues here: >> 1) Use case (which I have) >> 2) Permissions >> >> 1) Use case >> >> I am trying to build a backup system. To avoid duplication of

Re: Suggested new user link command

Hi all! Top-quoting is evil BTW. On Wed, 2018-05-02 at 00:17 +1200, Tony Wallace wrote: > Two issues here: > 1) Use case (which I have) > 2) Permissions > > 1) Use case > > I am trying to build a backup system. To avoid duplication of files > over multiple backups I take an Md5 check sum of

Re: Suggested new user link command

Hi all! Top-quoting is evil BTW. On Wed, 2018-05-02 at 00:17 +1200, Tony Wallace wrote: > Two issues here: > 1) Use case (which I have) > 2) Permissions > > 1) Use case > > I am trying to build a backup system. To avoid duplication of files > over multiple backups I take an Md5 check sum of

Re: Suggested new user link command

Two issues here: 1) Use case (which I have) 2) Permissions 1) Use case I am trying to build a backup system.  To avoid duplication of files over multiple backups I take an Md5 check sum of file contents.  Files with the same sum are hardlinked together.   Files are linked in to a standard

Re: Suggested new user link command

Two issues here: 1) Use case (which I have) 2) Permissions 1) Use case I am trying to build a backup system.  To avoid duplication of files over multiple backups I take an Md5 check sum of file contents.  Files with the same sum are hardlinked together.   Files are linked in to a standard

Re: Suggested new user link command

On Tue, May 1, 2018 at 12:58 PM, Tony Wallace wrote: > Good point. But there are gid and uid fields in inode disc record. > > https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Inode_Table > > I assume these can be use to ensure that the directory in which it is to > be

Re: Suggested new user link command

On Tue, May 1, 2018 at 12:58 PM, Tony Wallace wrote: > Good point. But there are gid and uid fields in inode disc record. > > https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Inode_Table > > I assume these can be use to ensure that the directory in which it is to > be placed has

Re: Suggested new user link command

Good point.  But there are gid and uid fields in inode disc record. https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Inode_Table I assume these can be use to ensure that the directory in which it is to be placed has permissions to accept the inode.  If that is not the case then it would

Re: Suggested new user link command

Good point.  But there are gid and uid fields in inode disc record. https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Inode_Table I assume these can be use to ensure that the directory in which it is to be placed has permissions to accept the inode.  If that is not the case then it would

Re: Suggested new user link command

Hi On Tue, 2018-05-01 at 20:03 +1200, Tony Wallace wrote: > I am suggesting a new command for linking files. Currently there is > no > easy way to link a file with a known inode number to its correct > position in the directory tree. > > > int ilink(const int inode, const char *newpath)

Re: Suggested new user link command

Hi On Tue, 2018-05-01 at 20:03 +1200, Tony Wallace wrote: > I am suggesting a new command for linking files. Currently there is > no > easy way to link a file with a known inode number to its correct > position in the directory tree. > > > int ilink(const int inode, const char *newpath)

Suggested new user link command

I am suggesting a new command for linking files.  Currently there is no easy way to link a file with a known inode number to its correct position in the directory tree.   int ilink(const int inode, const char *newpath) The current alternative to this command is to find the file path associated

Suggested new user link command

I am suggesting a new command for linking files.  Currently there is no easy way to link a file with a known inode number to its correct position in the directory tree.   int ilink(const int inode, const char *newpath) The current alternative to this command is to find the file path associated