Subject: Re: "su" in rescue?
To: None <tech-userlevel@NetBSD.org>
From: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
List: tech-userlevel
Date: 06/29/2004 10:03:50
--98e8jtXdkpgskNou
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jun 29, 2004 at 05:57:43PM +1000, Luke Mewburn wrote:
> On Thu, Jun 24, 2004 at 02:30:13PM -0400, Perry E. Metzger wrote:
> | itojun@itojun.org (Jun-ichiro itojun Hagino) writes:
> | > ok, i got enough comment. so new proposal: could you please make
> | > /usr/bin/su a static binary? it's a one-line Makefile change.
> |=20
> | The problem with that is that it will mean that /usr/bin/su can't
> | handle things like dynamically linked database modules, for dealing
> | with things like hesiod and such.
> |=20
> | I would suggest that the "right" thing is to create a statically
> | linked su *in addition* to the normal /usr/bin/su, and copy that into
> | /rescue. We could easily do the makefile machinery to handle that.
>=20
> I still haven't seen a justification why this would be necessary.
> What is wrong with "boot -as" (or the platform equivalent), and
> repairing the problem with /rescue/init && /rescue/* ?
I think the person in question (I lost track of the origin of this thread) =
wants
to repair a system while remotely logged in as a non-root (when e.g. NFS /u=
sr has
gone away for some reason) without using a remote console.
Regards,
-is
--98e8jtXdkpgskNou
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: 2.6.i
iQEVAgUBQOEiZDCn4om+4LhpAQGEawgAv3PeqIaf3GuA3j9weJcW5WO75toKeQyv
fH5Mf9BcT+k8fvkeBX7SM0vdc56hf526CKjP+GeuIaDKa/3erbVePwOpbAtMpzmS
4ZoKMvdY4+JZm7nxFhG7zT7LSCVNVBpAOmIouz2CpKbTWhfw8BSX61ndeFQJU5Vu
29i+ZkEWaRs3TQ7HGM+36YjogbxVxTeuWikS7joDJj+xJrDzlo7hxUsyg3Bm3FfW
vDN07hkPr/sy/qTTIz/dD7Z9n/9Ljme7Mr1jkDHQ3oATxdI6EarTHu8P6OpvzzpB
z53NShn9qiCUux64Ed2jzjARrbctvNh0SxvCiZuwSPNk60T7VeMalQ==
=y0Ur
-----END PGP SIGNATURE-----
--98e8jtXdkpgskNou--