Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!uc!cs.umn.edu!quest!viper!dave
From: dave@viper.Lynx.MN.Org (David Messer)
Newsgroups: comp.unix.misc
Subject: Re: Brain Teaser
Message-ID: <3974@viper.Lynx.MN.Org>
Date: 11 Oct 90 14:48:18 GMT
References: <Oct90.150551.3649@x.co.uk>
Reply-To: dave@viper.Lynx.MN.Org (David Messer)
Organization: Lynx Data Systems, Eagan, MN
Lines: 16

In article <Oct90.150551.3649@x.co.uk> mike@x.co.uk (Mike Moore) writes:
 >
 > [Description of replacing /bin/sh with a script deleted]
 >
 >you can't [login] (can't exec a shell of course).
 >
 >now assume that *everyone* is set to use /bin/sh (including root), how
 >do you get out of this without rebuilding the operating system?

I think the only way out of this is to reboot from your
distribution media (floppies or whatever) and mv the
executable sh back to /bin/sh.  You shouldn't have to rebuild
the operating system though.
-- 
Spelling is for computers.           | David Messer       dave@Lynx.MN.Org -or-
                                     | Lynx Data Systems  ...!bungia!viper!dave