How to install Squid on FC 4.0

How to install Squid on FC 4.0

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
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

vi /etc/squid/squid.conf


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

Configure putty

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

How To Configure Hardware Mirroring on Sun T2000

How To Configure Hardware Mirroring on Sun T2000

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
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

0. c0t0d0
/[email protected]/[email protected]/[email protected]/[email protected]/[email protected],0
Specify disk (enter its number): 0
selecting c0t0d0
[disk formatted]

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
format> type

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

Procedure as below for reseting the T2000 ALOM password due to no scadm command available for the sun4v architecture in Solaris 10.

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:

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.


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

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=0x1
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=0x400000
* End tuning recommended for T2000

Enable Syslog Logging Of SSH Access

These are the steps to enable logging of sshd on Solaris 8
Will probably work on 9 and 10, though the restart of syslog in 10 is different.

Add one line to syslog configuration file
vi /etc/syslog.conf /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

Creating ZFS filesystem on Solaris 10, x86

Redid the installation of Solaris 10 on the X4200
patched everything
Here is the process for creating the filesystem
(It will be expanded when I get more disks)

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
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
pool 107K 128G 25.5K /pool
pool/home 24.5K 128G 24.5K /pool/home
bash-3.00# cd /pool/home

That was easy.