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

Re: ifupdown writes to /etc... a bug?

* Arthur de Jong <arthur@tiefighter.et.tudelft.nl> [030323 22:51]:
> > Eh? passwd and useradd are part of the admin's toolset; if they need to
> > write to /etc (rather than using ldap or similar), the admin needs to
> > remount / rw. This is exactly the same as needing to mount / rw when
> > running apt-get and dpkg.
> I probably use passwd more often as a non-priviliged user (to change my
> password) than as root.

But it is definitly no state file. (I guess you want your changes to
be kept over reboots). Thus it would never end in /var/run but
somewhere under /var/lib. (Hm, perhaps I should look if my nss-module
to keep user-information out of a static admin- and systemuser
/etc/{passwd,shadow,group,gshadow} into a variable part can be extended 
to also allow changes to the user-part.)

> Also I don't think it's very easy to make a distinction between admin
> related activity and "normal" activity done by unpriviliged users (e.g.
> regularly update /etc/motd with news items, changing passwords, adding a
> virtual host to apache config, etc). I don't think it's very clear what
> should go in /run and what in /etc if you decide to make a /run.

/run is not intended to be the place of all in /etc that needs changing.
But for all one those things beloging to /var/run, that ended up in
/etc, because /etc is accessible that early.

  Bernhard R. Link

Sendmail is like emacs: A nice operating system, but missing
an editor and a MTA.

Reply to: