[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#282067: yes!



On Fri, 2004-12-17 at 22:19 -0800, Karsten M. Self wrote:
> on Fri, Nov 19, 2004 at 06:12:28PM +0100, Gergely Nagy (algernon@bonehunter.rulez.org) wrote:
> > On Fri, 2004-11-19 at 18:05 +0100, martin f krafft wrote:
> > > also sprach Gergely Nagy <algernon@bonehunter.rulez.org> [2004.11.19.1802 +0100]:
> > > > Umm.. So if I have an NFS-shared $HOME, that I share between
> > > > Debian, various BSDs and commercial Unixes, I'll have to resort to
> > > > black magic to get some of my dotfiles appear where they need to,
> > > > on all of the systems I'm using them?
> > > 
> > > Use symlinks.
> > 
> > That's butt ugly, and I'll have even more files than normally. 
> 
> For a transitional period, it's damned useful.

For a transitional period, I suggest you create $HOME/etc, move your
dotfiles there and symlink them back. Then try to put your $HOME in CVS
or use it on a system that still thinks that the status-quo is perfectly
fine.

> > Throw in some inode quotas and boom, my $HOME is broken (and yes, I
> > regularly work on a system with ridiculously low inode quotas).
> 
> Pardon?  Could you expand on this?

Inode quotas. The number of files (that includes directories and
symlinks) is limited, and for my work there, I need quite a few files,
so I'm already near my limit. Were I forced to place a hundred symlinks,
I'd overrun my quota. That means, that either I can't work on that box,
or I need to change my habits, and stop managing my $HOME in CVS.

Neither option seems reasonable.

> > There are also some - arguably broken - software out there that scream
> > if the dotfile is a symlink. Even if I can fix those, I can't force
> > the Solaris sysadmin to install that version.
> 
> As another post suggested, the standard, if it's implemented, should be
> managed on a package-by-package basis.  Which if ported back upstream
> means that cross-distro compatibility should be maximized.  Not wholly
> problem-free, but headed there.

It should be done upstream first, if done at all. And in such a way,
that the old location is searched first, then the new one.

-- 
Gergely Nagy



Reply to: