Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!math.fu-berlin.de!tmpmbx!scuzzy!src
From: src@scuzzy.in-berlin.de (Heiko Blume)
Newsgroups: comp.unix.sysv386
Subject: Re: Rebooting Sys V/386
Keywords: shutdown reboot autoboot
Message-ID: <1991Mar29.140550.11547@scuzzy.in-berlin.de>
Date: 29 Mar 91 14:05:50 GMT
References: <419@srs.UUCP> <563@bigfoot.first.gmd.de>
Organization: Contributed Software
Lines: 24

tmh@prosun.first.gmd.de (Thomas Hoberg) writes:

>In article <419@srs.UUCP>, dlucy@srs.UUCP (Doug Lucy) writes:
>|> Is there a way to force a sys V/386 3.2 system to reboot?
>|> I need to cause a reboot from a remote login after changing
>|> the kernel with idbuild. Is there a way to do this with
>|> just shutdown? Can it be done with a call to reset the system?
>|> 
>/etc/uadmin won't help there, because it only works from the console.

if you had asked a good unix admin, you'd have learned that you can
cause any terminal to become the console (syscon) by issueing 'init s'.

>Should the new kernel and configuration fail to reach init level 3, you are out
>in the cold, but I guess you know that...

if he doesn't login via tcp/ip level 2 will suffice. if he built a new
kernel he must make sure that the new /etc/inittab makes init respawn
a getty on the port to be used, too (see idmkinit(1M)).
-- 
   Heiko Blume <-+-> src@scuzzy.in-berlin.de <-+-> (+49 30) 691 88 93 [voice!]
                  public UNIX source archive [HST V.42bis]:
        scuzzy Any ACU,f 38400 6919520 gin:--gin: nuucp sword: nuucp
                     uucp scuzzy!/src/README /your/home