Re: Using /home for application directories -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Using /home for application directories
From: Patrik Schindler <poc@xxxxxxxxxx>
Date: Wed, 19 Feb 2025 15:31:20 +0100
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Hello Rob,

Am 19.02.2025 um 15:23 schrieb Rob Berendt <robertowenberendt@xxxxxxxxx>:

Perhaps the underlying problem is that it takes an act of God to get a new share created and they just got into the habit of using the one created on /home?
One reason not to do it is 'security by obscurity'. If there is a share on /home, and the general public goes there to get to their directory do you want them finding special purpose directories?

I'm not looking at this regarding shares to Windows, but keeping scripts, configuration files, and possibly intermediate output files together: Solely from a machine-local viewpoint.

:wq! PoC

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.