>> I can definately say that making hardlinks to files in other
>> directories (not owned by the linking user) is a handy feature.
> For what exactly is it an handy feature? I never needed to
> hardlink to a file that I don't own, so you would convince me if
> you would raise good points.
I regularly use this to permit a small group of users access to
certain large programs that insist on being run from ~/bin without
filling up the disk space with multiple copies thereof. Some of them
can detect that they were called via symlinks and refuse to run if so,
but they have no problems with hard links.
Personally, I don't like programs that check where they were run from,
but as an employee, I don't get to choose the programs, only to
install them...
Best wishes from Riley.
* Copyright (C) 1999, Memory Alpha Systems.
* All rights and wrongs reserved.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* http://www.memalpha.cx/Linux/Kernel/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/