Message-ID: <3A56F3A3.5EF0F36B@racal-survey.co.uk> Date: Sat, 06 Jan 2001 10:29:55 +0000 From: Barry Roberts <RobertsB@racal-survey.co.uk> Subject: Re: [suse-sparc] Installing a Sun Ultra 1 with Suse 7.0 Sparc version
Wayne Ringling wrote:
> I have read on the archives about a problem with SILO and YAST2. They seem
> to recommend using YAST1 to do part of the install then use YAST2 to finish
> it. Well I am setting up a new ultra 1 with a pair of new 18gb drives in
> it. I presume that I have to make the boot partition less than 2 gb (no
> problem there) are there any other limitations I should consider? How do I
> go from YAST1 to YAST2? Or is the current version of SuSe 7.0 for sparc
> installing properly now?
>
> Wayne
Wayne,
I have installed SuSE 7.0 on my UltraSparc 60 which has dual 18Gb LVD SCSI
disks, therefore my setup is likely to be similar. Linux is installed on
partition 7 of the second disk drive, the partition size is 6Gb. Therefore you
do not need to bother with a 2Gb boot partition limit etc on the UltraSparc. I
had one specific problem when trying to install SuSE 7.0 with Yast2, basically
the installation of SILO was all screwed up. However after checking the various
E-mails on the subject I re-installed the system using Yast1 (I am very
familiar with this to be fair as I have been using SuSE Linux on x86 for a long
time), this time everything was installed correctly including SILO. Also the
graphics system was correctly auto-configured by SAX to 1280 x 1024 x 85Hz, so
no problems there then either. Therefore, until Yast2 has had the SILO issue
resolved I would only use Yast1 for installations. Once a system is installed
you can easily start up Yast2 and configure various stuff if you prefer the
Yast2 interface.
You should also insert an alias into the boot prom for your system once
everything is done, this will make booting between Solaris and Linux really
easy. On my system at the boot prompt you now enter "boot" for a Solaris system
or "boot linux" for a Linux system. The entry I use in the prom can be seen at
a terminial using "eeprom", and is as shown below:
nvramrc=devalias linux /pci@1f,4000/scsi@3/disk@1,0:h
A printout of the second disk's partition table is as follows:
partition> pri
Volume: DISK2
Current partition table (original):
Total disk cylinders available: 7506 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 0 0 (0/0/0) 0
1 unassigned wm 0 0 (0/0/0) 0
2 backup wu 0 - 7505 16.86GB (7506/0/0) 35368272
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 alternates wm 2894 - 7505 10.36GB (4612/0/0) 21731744
6 swap wm 2671 - 2893 513.07MB (223/0/0) 1050776
7 unassigned wm 0 - 2670 6.00GB (2671/0/0) 12585752
Partition 5 is formatted as UFS for the Solaris install, and is also mounted in
fstab under Linux - no problems so far.
Partition 6 is a swap partition that is used by Linux.
Partition 7 is the Linux installation partition.
Various other drives on remote machines are auto-mounted via NFS as necessary.
The whole Linux system has proved to be very stable and reliable, with
performance similar to my Solaris 8 installation.
I hope the above is of some use to you.
Regards,
Barry Roberts.
This archive was generated by hypermail 2.1.0 : Wed Jun 06 2001 - 11:08:32 PDT