On Mon, Oct 22, 2001 at 01:36:53PM -0600, Matt Armstrong wrote:
> Julian Gilbey <[EMAIL PROTECTED]> writes:
>
> > On Fri, Oct 19, 2001 at 02:10:02PM -0500, Warren Turkal wrote:
> >> Why not just create a symlink to a device node /dev/flipit and just
> >> link it to the right file.
> >> Warren
> >
> > Why/how would that help?
> >
> > Julian
>
> Then /etc/flipit.conf could just always have /dev/flipit, and the
> package's maintainer scripts would control where /dev/flipit pointed
> to.
Yuck, yuck, yuck, yuck.
Let /etc/flipit.conf just be the symlink or contents directly and not
be a conffile. Where's the big problem with that?
Incidentally, this doesn't solve the problems, it only hides them:
what if the sysadmin wants to change something in the config? Then he
has to adjust -- what? /etc/flipit.conf? No, that only contains a
"#include /dev/flipit" command. /dev/flipit? No, that's only a
symlink. The target of /dev/flipit? Well, won't that be reset on the
next upgrade?
This seems a ridiculously complex way of *not* solving the problem.
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London
Debian GNU/Linux Developer, see http://people.debian.org/~jdg
NEW: Visit http://www.helpthehungry.org/ to do just that
ALSO http://www.thehungersite.com/ is back!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
