From owner-freebsd-hackers Thu Jan 9 15:05:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA27071 for hackers-outgoing; Thu, 9 Jan 1997 15:05:34 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA27066 for ; Thu, 9 Jan 1997 15:05:31 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id PAA04580; Thu, 9 Jan 1997 15:04:47 -0800 (PST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: mrcpu@cdsnet.net (Jaye Mathisen), hackers@freebsd.org Subject: Re: 2.2-BETA install report, minor problems. In-reply-to: Your message of "Thu, 09 Jan 1997 21:43:15 +0100." Date: Thu, 09 Jan 1997 15:04:47 -0800 Message-ID: <4576.852851087@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Remember that tzsetup is a standalone program normally. The `copied' > message is to make it clear that /etc/localtime is indeed a separate > copy now, so e.g. it won't be updated next time your /usr/share files > are renewed. This is the default. The opposite is to create a > symlink into /usr/share/zoneinfo/. tzsetup will do this if the > existing /etc/localtime happened to be a symlink already, and will > announce it then. Nonetheless, I don't think it should do this in the case where it's run from init (sysinstall) or possibly when there's no existing file there at all, e.g. the first time (I like that better). I agree that the extra message is just noise and it irked me when I first encountered the change myself. Jordan > > > 2) The box I was installing on had BSD/OS installed on it. For whatever > > BSD/OS uses a totally `weird' bootstrap if used in dedicated mode > (withouth an fdisk table). This is something like our `dangerously > dedicated' mode, and BSDi should probably warn about its dangers as > well. You just felt it... > > > I tried everything I could think of. fdisk shows totally bizarre > > numbers for the partition table, and the only way I could get the damn > > thing to install properly was to low-level format the disk from my Adaptec > > controller. > > No. I think a simple dd if=/dev/zero of=/dev/rsd0 count=100 should > have done it as well. (Substitute the actual device for rsd0 if > BSD/OS has a different one, i don't know.) The same procedure is > needed to reuse a `dangerously dedicated' FreeBSD disk e.g. for a > MicroSoft system. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-)