Re: [RFC] User Accesable Filesystem Hierarchy Standard

On Monday 29 March 2004 17.57, Zackary Deems wrote:
> /home
> typically is not created with enough space to support application

Don't know about typically. But it's often enough the case, I guess. Also: the 
backup system gets loaded with lots of application binaries which probably 
don't need to be backupped, really.

> installs, for one;  two, the average desktop user is not going to know
> enough to watch the available space, potentially creating a DoS for
> himself

Agree, but this is already the case (and to a much bigger extent) with .mp3 
files and such things. As long as the user doesn't install the whole KDE 
locally, things should stay relatively small (Ok, lessens my concerns  above 
about backup systems)

> and everyone else on that machine when /home fills up (this is 

Then the admin is to blame. Set up disk quotas.

> not quite as much of an issue for distributions which use flat partition
> structures).  Administering a machine with software installed in ~/
> would also be far more difficult and would require much larger changes
> to the package managers currently in use.. or it would require keeping
> multiple package databases.. which would be even uglier for administration.

Isn't the whole idea that the admin has got nothing to do with all that. It's 
the users' home directories, and the idea is exactly that users can install 
software without bothering the admin.

So the only thing the admin will have to care about is changing libraries the 
software installed in ~/... uses. But this is already the case, sophisticated 
users already have local stuff installed.

cheers
-- vbi


-- 
A Nuoro quattro pastori sardi sono stati arrestati da quattro pastori
tedeschi.
		-- Notizie dall'interno - Il TG di Max Cipollino
		   (Massimo Boldi)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iKcEABECAGcFAkBoeoVgGmh0dHA6Ly9mb3J0eXR3by5jaC9sZWdhbC9ncGcvZW1h
aWwuMjAwMjA4MjI/dmVyc2lvbj0xLjUmbWQ1c3VtPTVkZmY4NjhkMTE4NDMyNzYw
NzFiMjVlYjcwMDZkYTNlAAoJEIukMYvlp/fW2p8AoJBrgEgQkHEMTC9v2EKWQmeL
o1e6AKCMNeBu+PLdYP3LcRvyRCZ8QXPYag==
=dO+2
-----END PGP SIGNATURE-----