Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!cs.utexas.edu!uunet!pipex!uknet!zaphod.axion.bt.co.uk!lessen From: lessen@axion.bt.co.uk (Lee Essen) Newsgroups: comp.os.386bsd.questions Subject: Re: Please Make the Boot Manager Go AWAY (repost) Date: 18 May 1993 10:53:17 GMT Organization: BT Laboratories Lines: 24 Distribution: world Message-ID: <1taf6t$4m4@zaphod.axion.bt.co.uk> References: <1t98hn$68c@terminator.rs.itd.umich.edu> <1ta31s$33e@lucy.ee.und.ac.za> NNTP-Posting-Host: jammy.axion.bt.co.uk In article <1ta31s$33e@lucy.ee.und.ac.za>, barrett@lucy.ee.und.ac.za (Alan Barrett) writes: |> In article <1t98hn$68c@terminator.rs.itd.umich.edu>, |> pauls@css.itd.umich.edu (Paul Southworth) writes: |> > Seriously, there must be someone reading this that knows how to make the |> > @#$% boot partition/kernel selector that gets installed with NetBSD GO AWAY. |> > If this is a RTFM question, please tell me WITFM? I want this damn beast |> > to boot wd(0,a)/386bsd forever and ever and I never want it to ask me |> > again. How else can one reboot the machine remotely? You should find that it will time out (after about 10seconds) and boot wd(0,a)/386bsd automatically. Otherwise you need to build the old boot blocks (which you might be able to find in /sys/i386/stand) and install these with... disklabel -w -r <device> <type> <title> <path_to_old_wdboot> <path_to_old_bootwd> If your existing boot blocks don't time out then you have a problem, it's probably better to fix this than go back to the old boot blocks. There are several enhancements in the new ones. Lee.