From owner-freebsd-bugs Wed Aug 21 06:22:41 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA14617 for bugs-outgoing; Wed, 21 Aug 1996 06:22:41 -0700 (PDT) Received: from vse.vse.cz (vse.vse.cz [146.102.16.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA14584 for ; Wed, 21 Aug 1996 06:22:28 -0700 (PDT) Received: by vse.vse.cz id AA12250 (5.67a8/IDA-1.5 for bugs@freebsd.org); Wed, 21 Aug 1996 15:22:12 +0200 Date: Wed, 21 Aug 1996 15:22:12 +0200 From: Eduard Vopicka Message-Id: <199608211322.AA12250@vse.vse.cz> Reply-To: Eduard Vopicka X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: bugs@freebsd.org Subject: sysinstall problem - 960801-SNAP X-Charset: ASCII X-Char-Esc: 29 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello FreeBSD developers, this is to report post-installation problem with 2.2-960801-SNAP /stand/sysinstall. I have my system installed over NFS and reconfigured kernel to satisfy my needs, especially to include the ccd driver. My system uses SCSI drive connected to Adaptec 1542B. Now I am about to play with ccd. So I have connected the second SCSI disk (everything properly terminated etc, this is not the problem). Then I am trying to use /stand/sysinstall to add sd1, actually sd1s1e and sd1s1f. I need these two to play with the ccd driver. In sysinstall, I am going through the following menu: custom installation partition -> sd1 -> W # create single partition here bootmgr -> standard # of course, none should be also OK for sd1 label -> create sd1s1e and sd1s1f, each of them being about 1/2 of disk capacity Write the label - getting coredump due to signal 11 Note that I already have /dev/sd1* made with /dev/MAKEDEV. Another problem is that when I decide to leave both Partition and Label menus with Q, then the later Commit (which is supposed to to write everything) requires the Installation source and Distribution sets to be set up, which does not make much sense when I am just adding the second disk to installed system. Also, if sd1 is already partitioned and I am going directly to Label w/o changing already existing partition configuration, Label refuses to do anything, saying something about that I *must* first partition disk ... which is already partitioned. Yes, I know, this logic is required during installation, but seems to cause problems during post-installation. Please is there any chance to get around these limitations, except for using fdisk/disklabel directly? Thanks in advance, Eduard Vopicka -- "Eduard Vopicka, Computing Centre, Prague University of Economics, W. Churchill Square 4, CZ 130 67 Prague 3"