From markk@pongo.West.Sun.COM Fri May 26 20:06:43 1995 Date: Fri, 26 May 1995 20:03:40 -0700 From: markk@pongo.West.Sun.COM (Mark K.) To: psarc@Eng Subject: FASTTRACK 1995/153 ppc installboot Cc: billt@pongo.West.Sun.COM Content-Length: 1792 I am sponsoring the following for fast track approval. The timer expires 06/05/95. ================================================================ CASE: 1995/153 PPC installboot AUTHOR: Bill Taylor (bill.taylor@west) SUMMARY: /usr/sbin/installboot needs modification for PowerPC. This proposed fast-track is presented for your review. The arguments to the command, and the file names used by the installboot command are the interesting issues. A description of PowerPC booting "Disk Layouts, Booting, and Installation for Solaris on PowerPC" is provided as an attachment to this case. Also, the proposed man page is provided. PROBLEM: The PowerPC booting mechanism differs from that of SPARC and x86, thus there is the need to install boot components in a different manner. Since all PowerPC platforms we intend to support are following 1275 Open Firmware specifications, we are proposing an ISA-specific solution with the understanding that this may have to become platform-specific some day. Besides providing the ability to install the bootblk that complies with 1275 booting, there is the need of supporting machines that do not yet have Open Firmware. For these machines that have Conventional Firmware instead of Open Firmware, there is an additional feature for installboot in that it needs to install a copy of Virtual Open Firmware on the disk to make it bootable. PROPOSED SOLUTION: We propose to add a new '-f' switch (PPC only) to optionally specify the name of the Virtual Open Firmware file to be installed. For a complete description of the proposed changes the attached manual page (1995/153/materials/installboot.man) See the "Disk Layout ..." attachment for full background on PowerPC booting (1995/153/materials/instalwp.ps) From r.@jetsun Tue May 30 20:49:41 1995 Date: Tue, 30 May 1995 20:49:18 -0700 From: r.@jetsun (David R.) To: psarc@Eng, markk@pongo.West.Sun.COM Subject: Re: FASTTRACK 1995/153 ppc installboot Cc: billt@pongo.West.Sun.COM Content-Length: 527 How often will the open firmware be required to be loaded in relation to the real boot block? I am wondering if it might be worth using the syntax: installboot [-f] bootcode raw-disk-device where by default the bootcode is the normal bootblock. If -f is specified the bootcode is the open firmware code. This may add two steps but if it is rare enough it might be useful. Also, doesn't the proposed syntax of: installboot bootblk [ -f openfirmware ] raw-disk-device violate the getopts argument "standard"? -David From billt@pongo71.West.Sun.COM Wed May 31 07:11:27 1995 Date: Wed, 31 May 1995 07:07:32 -0700 From: billt@pongo71.West.Sun.COM (Bill Taylor) To: psarc@Eng, markk@pongo.West.Sun.COM, David.R.@Eng Subject: Re: FASTTRACK 1995/153 ppc installboot Cc: billt@pongo.West.Sun.COM Content-Length: 1411 > From David.R.@Eng Tue May 30 20:49 PDT 1995 > Date: Tue, 30 May 1995 20:49:18 -0700 > From: David.R.@Eng (David R.) > To: psarc@Eng, markk@pongo.West.Sun.COM > Subject: Re: FASTTRACK 1995/153 ppc installboot > Cc: billt@pongo.West.Sun.COM > > > How often will the open firmware be required to be loaded in relation > to the real boot block? > > I am wondering if it might be worth using the syntax: > > installboot [-f] bootcode raw-disk-device > > where by default the bootcode is the normal bootblock. If -f > is specified the bootcode is the open firmware code. This may > add two steps but if it is rare enough it might be useful. I think I prefer one-stop-shopping. Normally, installing the openfirmware file is only done by "install" which has to install the bootcode/bootblk too. If anyone cares to push, I will change this, but I would prefer to keep it the way it is. > Also, doesn't the proposed syntax of: > > installboot bootblk [ -f openfirmware ] raw-disk-device > > violate the getopts argument "standard"? Good point. There was evolution here. "bootblk" was the first file argument on SPARC and x86. The -f flag preceding the optional openfirmware file argument was a late addition. I believe you're saying that the following is preferred (getopt standard), and I agree. installboot [ -f openfirmware ] bootblk raw-disk-device > -David -Bill Taylor From billt@pongo71.West.Sun.COM Thu Jun 1 08:41:36 1995 Date: Thu, 1 Jun 1995 08:38:14 -0700 From: billt@pongo71.West.Sun.COM (Bill Taylor) To: psarc@Eng, markk@pongo.West.Sun.COM Subject: Re: FASTTRACK 1995/153 ppc installboot Cc: billt@pongo.West.Sun.COM Content-Length: 3519 The updated man page, reflecting the change in the order of the arguments to comply with getopt. installboot(1M) Maintenance Commands installboot(1M) NAME installboot - install bootblocks in a disk partition SPARC SYNOPSIS installboot bootblk raw-disk-device x86 SYNOPSIS installboot pboot bootblk raw-disk-device PowerPC SYNOPSIS installboot [ -f openfirmware ] bootblk raw-disk-device AVAILABILITY SUNWcsu DESCRIPTION The boot(1M) program is loaded from disk by the bootblock program which resides in the boot area of a disk partition. bootblk is the name of the bootblock code. raw-disk-device is the name of the disk device onto which the bootblock code is to be installed; it must be a character device which is readable and writable. Naming conventions for a SCSI or IPI drive are c?t?d?s? and c?d?s? for an IDE drive. pboot is the name of the partition boot file. The ufs boot objects are platform-dependent, and reside in the /usr/platform/platform-name/lib/fs/ufs directory. The platform name can be found using the -i option of uname(1). For PowerPC only, the bootblk is copied into the primary DOS partition that must exist on the raw-disk-device which is determined by reading the fdisk partition table (sector 0 of the "p0" partition of raw-disk-device). The primary DOS partition is mounted as a PCFS filesystem, and bootblk is copied into the partition as the file SOLARIS.ELF. If the "-f openfirmware" argument is given, the openfirmware file is copied into the PowerPC boot partition (type 0x41). This is needed only for systems that do not have real Open Firmware. If this argument is provided and the PowerPC boot partition does not exist or if the primary DOS partition does not exist, installboot fails. SPARC EXAMPLES To install a ufs bootblock on slice 0 of target 0 on con- troller 1, of the platform where the command is being run, use: example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk \ /dev/rdsk/c1t0d0s0 x86 EXAMPLES To install the ufs bootblock and partition boot program on slice 2 of target 0 on controller 1, of the platform where the command is being run, use: example# installboot /usr/platform/`uname -i`/lib/fs/ufs/pboot \ /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t0d0s2 PowerPC EXAMPLES To install the ufs bootblock and openfirmware programs on slice 2 of target 0 on controller 1, of the platform where the command is being run, use: example# installboot -f /platform/`uname -i`/openfirmware.x41 \ /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t0d0s2 SEE ALSO od(1), uname(1), boot(1M), init(1M), kadb(1M), kernel(1M), reboot(1M), rpc.bootparamd(1M), init.d(4) SPARC: Installing Solaris Software x86: Installing Solaris Software PowerPC: Installing Solaris Software SPARC only monitor(1M) SunOS 5.4 Last change: 19 Dec 1994 1 installboot(1M) Maintenance Commands installboot(1M) x86 and PowerPC only fmthard(1M), fdisk(1M) WARNINGS installboot will fail if the bootblk, pboot or openfirmware files don't exist or if the raw disk device isn't a character device. SunOS 5.4 Last change: 19 Dec 1994 2 From roland.mainz@nrubsig.org Wed May 6 19:54:41 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n472sd2C008114 for ; Wed, 6 May 2009 19:54:40 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n472sXGC029298; Thu, 7 May 2009 03:54:38 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KJ900E0J6QXUH00@nwk-avmta-2.sfbay.sun.com>; Wed, 06 May 2009 19:54:33 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJ900BSP6QX2670@nwk-avmta-2.sfbay.sun.com>; Wed, 06 May 2009 19:54:33 -0700 (PDT) Received: from relay15i.sun.com (ip125.net129179-4.block1.us.syntegra.com [129.179.4.125]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n472lgI1023995; Thu, 07 May 2009 02:54:32 +0000 (GMT) Received: from mmp14es.mmp.us.syntegra.com ([160.41.208.14] [160.41.208.14]) by relay15i.sun.com with ESMTP id BT-MMP-1721496; Thu, 07 May 2009 02:54:32 +0000 (Z) Received: from relay14i.sun.com (relay14i.sun.com [129.179.4.124]) by mmp14es.mmp.us.syntegra.com with ESMTP id BT-MMP-524814; Thu, 07 May 2009 02:54:32 +0000 (Z) Received: from mail-in-09.arcor-online.net ([151.189.21.49] [151.189.21.49]) by relay1i.sun.com with ESMTP id BT-MMP-5769081; Thu, 07 May 2009 02:54:32 +0000 (Z) Received: from mail-in-10-z2.arcor-online.net (mail-in-10-z2.arcor-online.net [151.189.8.27]) by mx.arcor.de (Postfix) with ESMTP id E20561AF2FA; Thu, 07 May 2009 04:16:49 +0200 (CEST) Received: from mail-in-11.arcor-online.net (mail-in-11.arcor-online.net [151.189.21.51]) by mail-in-10-z2.arcor-online.net (Postfix) with ESMTP id CA18723D2B5; Thu, 07 May 2009 04:16:49 +0200 (CEST) Received: from jupiterb48.nrubsig.org (dslb-094-219-212-156.pools.arcor-ip.net [94.219.212.156]) by mail-in-11.arcor-online.net (Postfix) with ESMTPS id 27B9EE38FE; Thu, 07 May 2009 04:16:48 +0200 (CEST) Received: from nrubsig.org (localhost [127.0.0.1]) by jupiterb48.nrubsig.org (8.13.8+Sun/8.13.8) with ESMTP id n472GkrR002190; Thu, 07 May 2009 04:16:47 +0200 (CEST) Date: Thu, 07 May 2009 04:16:46 +0200 From: Roland Mainz Subject: Requesting ARC cases 1993/685, 1994/188, 1994/196, 1994/197, 1994/302, 1995/077, 1995/082, 1995/153 Sender: gisburn@jupiterb48.nrubsig.org To: opensolaris-arc@opensolaris.org Cc: Bonnie Corwin , "PSARC-EXT@sun.com" , emerging-platforms-discuss@opensolaris.org Message-id: <4A02448E.1AC9B6BA@nrubsig.org> MIME-version: 1.0 X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.11 sun4u) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-11.arcor-online.net 27B9EE38FE X-Antispam: No, score=0.0/5.0, scanned in 0.057sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ x_sac_archived: PSARC/1993/685 x_sac_archived: PSARC/1994/188 x_sac_archived: PSARC/1994/196 x_sac_archived: PSARC/1994/197 x_sac_archived: PSARC/1994/302 x_sac_archived: PSARC/1995/077 Status: RO Content-Length: 704 hi! ---- I'd like to request to open the following ARC cases for publish access: PSARC 1993/685 PowerPC_ABI PSARC 1994/188 Solaris Kernel for PowerPC PSARC 1994/196 PowerPC Header Files PSARC 1994/197 PowerPC Commands PSARC 1994/302 PowerPC_Booting PSARC 1995/077 processor_info(2) binding for PowerPC and future ISAs PSARC 1995/082 PowerPC sysconfig parameters PSARC 1995/153 PPC installboot We need this materials as template for a set of ARC casess to specify support for a new architecture/hardware platform... ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;)