user1@server1> ssh-keygen –t rsa

Generating public/private rsa key pair.
Enter file in which to save the key (/home/user1/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/user1/.ssh/id_rsa.
Your public key has been saved in /home/user1/.ssh/id_rsa.pub.
The key fingerprint is:
31:a1:c2:d7:a6:9f:27:cd:84:1f:f2:7a:e8:7c:34:80

user1@server1> cd /home/user1/.ssh
user1@server1> cp id_rsa.pub authorized_keys

Copy the file authorized_keys to server2 and it is now possible to login without password.

user1@server1> cd /home/user1/.ssh
user1@server1> scp authorized_keys server2:/home/user1/.ssh

RPM is a package management system like Solaris packages.

To create packages from source code some or all of the following steps would be needed.

To set it up a build environment and number of configuration files are needed.

First the build environment.

cd /home/asbjorn
mkdir myrpm
cd rpm
mkdir -p BUILD RPMS/i386 SOURCES SPECS SRPMS

In earlier releases of RedHat a file .rpmrc was used.

Now rpmbuild uses the .rpmmacros for default values.

In the first two lines, information about the package creator is provided.

The _topdir line is included, so the package can be build as a user rather than as root.
Do not build packages as root if you can avoid it.

The following lines provide references to the build environment.

cd /home/asbjorn

vi .rpmmacros

%packager      Asbjorn Riedel <asbjorn@SOMEWEBSITE.com>
%vendor        The name of the project

%_topdir       /home/asbjorn/myrpm

%{_topdir}/BUILD
%{_topdir}/RPMS
%{_topdir}/RPMS/i386
%{_topdir}/SOURCES
%{_topdir}/SPECS
%{_topdir}/SRPMS

By defining the .spec file we can set up all the parameters needed for building packages of software delivered as tar files.

The %{_prefix} definition can be changed depending on the location where you want your package to be installed, example /opt, /usr or /usr/local. Just change the line with Prefix:  in it.

 vi myrpm/SPECS/testpackage.spec

%define name testpackage
%define version 0.0.1
%define release 1

Summary: A test package for RedHat Linux
Name: %{name}
Version: %{version}
Release: %{release}
Source: http://www.picourl.com/testpackage/%{name}-%{version}.tar.gz
Vendor: Guess It Must Be Me
URL: http://www.picourl.com/
License: None
Group: System
Prefix: %{_prefix}

%description
This is a testpackage , specially made for testing

%package devel
Summary: package with stuff to develop %{name}.
Group: System
Requires: %{name} = %{version}

%description devel
The %{name}-devel testpackage contains stuff for building %{name}.

%prep
%setup -q

%build
make

%install
rm -rf $RPM_BUILD_ROOT
make DESTDIR=$RPM_BUILD_ROOT install

%clean
rm -rf $RPM_BUILD_ROOT

%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig

%files
%defattr(-,root,root)
%doc ReadMe
%{_prefix}/lib/lib*.so.*

%files devel
%defattr(-,root,root)
%doc ReadMe
%{_prefix}/bin/*
%{_prefix}/include/*

%changelog
* Thu Mar 27 2008 Asbjorn Riedel <asbjorn@localhost>
- Initial spec file

The %install part contains the actual commands to build the software and it may need to be changed in your case.

How to finally do the build …

rpmbuild -ba SPECS/testpackage.specs

log in on box

become root

get the squid package

yum install squid.i386

Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
Resolving Dependencies
–> Populating transaction set with selected packages. Please wait.
—> Downloading header for squid to pack into transaction set.
squid-2.5.STABLE13-1.FC4. 100% |=========================| 164 kB 00:00
—> Package squid.i386 7:2.5.STABLE13-1.FC4 set to be updated
–> Running transaction check

Dependencies Resolved

==========================================================
Package Arch Version Repository Size
==========================================================
Installing:
squid i386 7:2.5.STABLE13-1.FC4 updates-released 1.2 M

Transaction Summary
==========================================================
Install 1 Package(s)
Update 0 Package(s)
Remove 0 Package(s)
Total download size: 1.2 M
Is this ok [y/N]: y
Downloading Packages:
(1/1): squid-2.5.STABLE13 100% |===========| 1.2 MB 00:01
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing: squid ########## [1/1]

Installed: squid.i386 7:2.5.STABLE13-1.FC4
Complete!

vi /etc/squid/squid.conf

http_port 127.0.0.1:3128

Configure firefox. Set the proxy to 127.0.0.1 + set the port to 3128

Configure putty

set up a tunnel which will be setup when connecting with ssh to the server

You need a boot server or boot of a CDrom

boot net -s

After the client has booted, run the following command:

bash; export NOINUSE_CHECK=1

Run the following command to create the RAID volumes:

raidctl -c c0t0d0 c0t1d0

Answer “yes” to the prompt.

Wait for the disks to complete syncing. To verify success, the raidctl command with no options should return the following:

# raidctl
RAID Volume RAID RAID Disk
Volume Type Status Disk Status
——————————————————
c0t0d0 IM OK c0t0d0 OK
c0t1d0 OK

Using the format utility, select the volume, define the type as ⮮Auto configure⮝, and label the volume as follows:

# format
Searching for disks…done

AVAILABLE DISK SELECTIONS:
0. c0t0d0
/pci@780/pci@0/pci@9/scsi@0/sd@0,0
Specify disk (enter its number): 0
selecting c0t0d0
[disk formatted]

FORMAT MENU:
disk – select a disk
type – select (define) a disk type
partition – select (define) a partition table
current – describe the current disk
format – format and analyze the disk
repair – repair a defective sector
label – write label to the disk
analyze – surface analysis
defect – defect list management
backup – search for backup labels
verify – read and display labels
save – save new disk/partition definitions
inquiry – show vendor, product and revision
volname – set 8-character volume name
! – execute , then return
quit
format> type

AVAILABLE DRIVE TYPES:
0. Auto configure
1. Quantum ProDrive 80S
2. Quantum ProDrive 105S
3. CDC Wren IV 94171-344
4. SUN0104
5. SUN0207
6. SUN0327
7. SUN0340
8. SUN0424
9. SUN0535
10. SUN0669
11. SUN1.0G
12. SUN1.05
13. SUN1.3G
14. SUN2.1G
15. SUN2.9G
16. Zip 100
17. Zip 250
18. Peerless 10GB
19. SUN72G
20. other
Specify disk type (enter its number)[19]: 0
c0t0d0: configured with capacity of 68.00GB

selecting c0t0d0
[disk formatted]
format> label
Ready to label disk, continue? y

format> quit
#

Now build the server

Recovering T2000 ALOM Passwords

For security reasons, this procedure is available only while accessing the system
directly through the serial port. The procedure resets all ALOM NVRAM settings.

To Recover Your ALOM Passwords:
1. Connect to the ALOM serial port.

2. Power down the Sun Fire T2000 Server.

Remove the power cords from both power supplies. Wait several seconds for power
to discharge before reinserting the cords.

3. Press the Escape key during ALOM boot when the following text is displayed on
the console:

Boot Sector FLASH CRC Test
Boot Sector FLASH CRC Test, PASSED.

Return to Boot Monitor for Handshake
After pressing the Escape key, the ALOM boot escape menu is printed:
ALOM Menu

e – Erase ALOM NVRAM.
m – Run POST Menu.
R – Reset ALOM.
r – Return to bootmon.
Your selection:

4. Enter e to erase the ALOM NVRAM.

Your selection: e
ALOM NVRAM erased.

ALOM Menu

e – Erase ALOM NVRAM.
m – Run POST Menu.
R – Reset ALOM.
r – Return to bootmon.
Your selection:
5. Enter r to return to the ALOM boot process.
Your selection: r

ALOM POST 1.0
Status = 00007fff

ALOM then boots and resets all NVRAM settings. You are automatically logged on
as user admin with no password and no permissions. All ALOM NVRAM settings
are reset to the factory defaults.

BTW: Make sure place the following lines in your /etc/system file for Solaris 10 which is for mandatory T2000 support.

* Begin tuning recommended for T2000
*
set pcie:pcie_aer_ce_mask=0×1
*
set autoup=900
set tune_t_fsflushr=1
set rlim_fd_max=260000
set rlim_fd_cur=260000
set sq_max_size=100
set ipge:ipge_tx_ring_size=2048
set ipge:ipge_srv_fifo_depth=16000
set ipge:ipge_reclaim_pending=32
set ipge:ipge_bcopy_thresh=512
set ipge:ipge_dvma_thresh=1
set ip:ip_squeue_fanout=1
set ipge:ipge_tx_syncq=1
*
set segkmem_lpsize=0×400000
* End tuning recommended for T2000

Add one line to syslog configuration file
vi /etc/syslog.conf

auth.info /var/log/sshd.log

Create the log file
touch /var/log/sshd.log

Enable syslog in the sshd_config (uncomment line)
vi /etc/ssh/sshd_config

SyslogFacility AUTH
LogLevel INFO

Restart syslogd

/etc/init.d/syslog stop
/etc/init.d/syslog start

Login and check that there is a new entry in /var/log/sshd.log

bash-3.00# zpool create pool c0t0d0s7 c0t1d0s7
invalid vdev specification
use ‘-f’ to override the following errors:
/dev/dsk/c0t0d0s7 is currently mounted on /export/home. Please see umount(1M).
bash-3.00# zpool create pool c0t0d0s7 c0t1d0s7
bash-3.00# umount /export/home
“/etc/vfstab” 12 lines, 424 characters
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
fd – /dev/fd fd – no -
/proc – /proc proc – no -
/dev/dsk/c0t0d0s1 – – swap – no -
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no
-
#/dev/dsk/c0t0d0s7 /dev/rdsk/c0t0d0s7 /export/home ufs 2
yes -
/devices – /devices devfs – no -
ctfs – /system/contract ctfs – no -
objfs – /system/object objfs – no -
swap – /tmp tmpfs – yes -
~
“/etc/vfstab” 12 lines, 425 characters
bash-3.00# zpool create pool c0t0d0s7 c0t1d0s7
invalid vdev specification
use ‘-f’ to override the following errors:
/dev/dsk/c0t0d0s7 contains a ufs filesystem.
bash-3.00# zpool create -f pool c0t0d0s7 c0t1d0s7
bash-3.00# zpool list
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
pool 130G 80K 130G 0% ONLINE -

bash-3.00# zfs create export/home
cannot create ‘export/home’: no such pool ‘export’
bash-3.00# zfs create pool/home
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
pool 107K 128G 25.5K /pool
pool/home 24.5K 128G 24.5K /pool/home
bash-3.00# cd /pool/home

That was easy.

The machine is a X4200 with (for now) two internal disks.

I need to use this server for Perforce (versioning control) software and need a lot more diskspace.

Create first a pool of all available diskspace. In this case the existing /export/home which was created during installation will be used as well.

bash-3.00# umount /export/home
bash-3.00# zpool create -f perforcepool c0t0d0s7
invalid vdev specification
the following errors must be manually repaired:
/dev/dsk/c0t0d0s7 is normally mounted on /export/home according to /etc/vfstab. Please remove this entry to use this device.

So remove the entry in /etc/vfstab and try again

bash-3.00# zpool create -f perforcepool c0t0d0s7
bash-3.00#

Success!!!

There is one extra disk, so lets add that one.

Here is the outputr from the format command.

bash-3.00# format
Searching for disks…done

AVAILABLE DISK SELECTIONS:
0. c0t0d0
/pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@0,0
1. c0t1d0
/pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@1,0
Specify disk (enter its number): 0
selecting c0t0d0
[disk formatted]
Warning: Current Disk has mounted partitions.
/dev/dsk/c0t0d0s0 is currently mounted on /. Please see umount(1M).
/dev/dsk/c0t0d0s1 is currently used by swap. Please see swap(1M).
/dev/dsk/c0t0d0s3 is currently mounted on /metadb1. Please see umount(1M).
q/dev/dsk/c0t0d0s4 is currently mounted on /metadb2. Please see umount(1M).
/dev/dsk/c0t0d0s7 is part of active ZFS pool perforcepool. Please see zpool(1M).

So the second disk is c0t1d0

Can we just add the s2 (whole disk) ?

bash-3.00# zpool add perforcepool c0t1d0s2
invalid vdev specification
use ‘-f’ to override the following errors:
/dev/dsk/c0t1d0s2 overlaps with /dev/dsk/c0t1d0s7

Argh! so during installation the hardware RAID was choosen.
My bad! But it was first time I installed a X4200. Well, thats my excuse anyway.

So back to the drawing board. Maybe I have to install again, which is a pain since I can not set up a jumpstart server and have to install everything with the CD’s.

Whatever.

More to some in later posts.

Asbjorn