From owner-freebsd-questions Tue Oct 19 12:30: 9 1999 Delivered-To: freebsd-questions@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id D677917A4F for ; Tue, 19 Oct 1999 12:30:03 -0700 (PDT) (envelope-from andrsn@ANDRSN.STANFORD.EDU) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id MAA19914; Tue, 19 Oct 1999 12:18:53 -0700 (PDT) Date: Tue, 19 Oct 1999 12:18:53 -0700 (PDT) From: Annelise Anderson To: Jean-Mark Dupoux Cc: freebsd-questions@freebsd.org Subject: Re: Installing from dos problem In-Reply-To: <380C51F9.23440996@dupx.freeserve.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that what you've done should be okay, but only the FreeBSD partition (in dos terms) should be made bootable. It made your second FreeBSD slice the bootable one (or perhaps the dos extended parition) and that didn't work. I don't know why you're wasting 160 megabytes on /. Little happens there (except installation of new kernels and saving of the old ones) and it really doesn't need to be that big. On Tue, 19 Oct 1999, Jean-Mark Dupoux wrote: > Dear Annelise > > I had a good read of your suggestions, and as I expected, there were > slight differences between your advice and the exact install > instructions at the freebsd web site, insofar as recommended sizes of > partitions (I think mostly due to general progress in hardware > available, since the install instructions referred to release 2.2 from > one or 2 years ago) but I am guessing the principle is basically the > same. > > Before re-partitioning again completely, I tried to install again with > the following configuration, to double-check I had done everything > right first time around, and also try out the "S" switch in the slice > labelling editor as you said. It's not in the labelling editor. It's in the partition (slice) editor, although I think you were doing it in the right place. This terminology really is confusing, since FreeBSD uses both its own terminology and the dos terminology. Dos is happiest booting from the first partition, but the following may work. While you redo this stuff, where are you stashing the distributions to install from dos? Or are you resizing and moving? > slice 1 = freebsd 160mb > slice2 = dos-boot partition 160mb > slice 3 = dos-extended partition 850 mb > slice4= freebsd 860mb > > > the freebsd configuration I tried was > on the entire slice 1 > 60mb slice 4 > 20 mb > remainder > > I used the "S" switch on both freebsd slices, and retained the > "minimal" install option for the time being, since this meant I could > get started immediately (without waiting for any more downloads). The > install file set was on D:\freebsd\bin and d:\freebsd\manpages as > per instructions (was on first attempt on drive c:\freebsd\ etc..) > > This time there was a different error message, but it appeared more > or less immediately after hitting "ok" to proceed. > > "error mounting /dev/wd0s3 on /dist : invalid argument (22)" > > followed by > > "user confirmation requested - unable to initialize selected media. > Would you like to adjust your media configuration and try again > YES/NO" > > I took the opportunity at this point to go back into the editing > screens, double-check the options set, and try again, but there was > no difference to the result. > > Without entering into specifics of an "ideal" set-up for a system > with this size drive, is it safe for me to assume at this stage that > more should have happened using the steps I just described than what > actually did? No, you didn't do it quite right, as explained above. The ideal sizes depend on what you intend to do with this machine-- what you're going to run on it. A larger hard drive suggests that you might want to run X or compile stuff, or run some programs simultaneously; when the ram is limited, you'd want more swap. Since /var is primarily used to log stuff (and to hold databases), when a machine isn't doing much that needs to be logged, it doesn't have to be very big; and on a machine without public access, if it gets crowded you can link to /usr. (I would assume you're not going to run a web server or anonymous ftp on this machine, except perhaps experimentally.) Annelise > > Jean-Mark > > > > Annelise Anderson wrote: > > > One other thought. Are you sure the install is finding the dos > > parititions? Sometimes there is a problem with whether or not > > the subdirectories are in c:\freebsd\bin etc. (or d:\freebsd\bin, > > which is fine); or whether they need to be in c:\bin, c:\xxxx, > > and so forth. > > > > Annelise > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message