List the bootable devices with the devalias command,

ok devalias
cdrom /pci@0,600000/pci@0/pci@0/scsi@0/disk@4,0:f
net /pci@0,600000/pci@0/pci@1/pci@0/network@4
disk /pci@0,600000/pci@0/pci@0/scsi@0/disk@0
name aliases

List the current boot device.

ok printenv boot-device
boot-device = disk

Change the boot device from disk to network.

ok setenv boot-device net
boot-device = net

Verify the change.

ok printenv boot-device
boot-device = net

Save the change.

ok reset-all

After the server rests, boot from he device

ok boot

# swap -l
swapfile dev swaplo blocks free
dev/dsk/c0t0d0s1 32,9 16 8425712 8425712

The output has five columns:
path
The path name for the swap area.

dev
The major/minor device number in decimal if it is a block special device; zeroes otherwise.

swaplo
The swaplow value for the area in 512-byte blocks.

blocks
The swaplen value for the area in 512-byte blocks.

free
The number of 512-byte blocks in this area that are not currently allocated.

To find the status of total swap usage use the -s option.

# swap -s
total: 180928k bytes allocated + 28456k reserved = 209384k used, 10691424k available

List the status of all the swap areas. The output has five columns:

path
The path name for the swap area.

dev
The major/minor device number in decimal if it is a block special device; zeroes otherwise.

swaplo
The swaplow value for the area in 512-byte blocks.

blocks
The swaplen value for the area in 512-byte blocks.

free
The number of 512-byte blocks in this area that are not currently allocated.

The total amount of swap space in bytes currently allocated for use as backing store.

reserved
The total amount of swap space in bytes not currently allocated, but claimed by memory mappings for possible future use.

used
The total amount of swap space in bytes that is either allocated or reserved.

available
The total swap space in bytes that is currently available for future reservation and allocation.

These numbers include swap space from all configured swap areas as listed by the -l option, as well swap space in the form of physical memory.

Add the ip address and server name to the host file.

vi /etc/hosts
10.0.0.10 server-name

Select the interface you want, your server may have more than one network interfaces.

vi /etc/hostname.bge0
10.0.0.10 netmask 255.255.255.0

Change the node name

vi /etc/nodename
server-name

Add the gateway ip address

vi /etc/defaultrouter
10.0.0.1

Add the DNS servers ip addresses

vi /etc/resolv.conf
nameserver 168.20.0.10
nameserver 168.20.10.22

Add the network address

vi /etc/netmasks
10.0.0.0 255.255.255.0

Now reboot the server.

Samba version 3.0.35
PID Username Group Machine
——————————————————————-
1962 andrew users mypc (162.10.21.100)

Service pid machine Connected at
——————————————————-
IPC$ 1962 mypc Thu Feb 11 15:06:31 2010
andrew 1962 mypc Thu Feb 11 15:06:46 2010

I needed to configure Samba installed on my Solaris 10 server and came across this great article that was posted on support.moonpoint.com/os/unix/solaris/samba-solaris10-docusp.php. Below is a copy of the instructions.

If you need to share files between a Windows and a Unix or Linux system, you can use Samba, which is free software that implements the same networking protocol that Microsoft Windows use to share files between systems. If you don’t already have it on your system, you can download it from Samba – opening windows to a wider world.
If you have a Solaris 10 system, the Samba software is likely already on the system and you will likely just need to configure it. If you type ls /usr/sfw/bin/smb* and see smblicent, smbstatus, etc. then you already have it on the system. If not, try find / -name smbclient to look for it.

If you have an account already on the Solaris system from which you wish to share files or folders you can use it and can skip to Configuring Samba support for account. But supposing you wish to create a new account specifically for sharing files to a Windows system, then follow the steps below. This explanation was written specifically for sharing files from a Xerox DocuSP system, but is generally applicable to setting up Samba on any Sun Solaris 10 system.

Adding a New Account

While logged into the system from another account, right-click somewhere on the desktop and choose Hosts then Terminal Console.

Switch to the root account, if you aren’t already logged into that account with su – root.

Add a new user account with the useradd command.

# useradd -u 40022 -g staff -c “DocuSP folder sharing” -m -s /usr/bin/bash docusp01

-u specifies the userid. It should be one not already used on the system. You can type cat /etc/passwd to see all of the accounts on the system. The UID value is the number after the second colon in each line.

-g specifies the group the account belongs to and can be staff, if you don’t have another group you wish to use.

-c allows you to put a comment in the entry.

-m specifies that a home directory be created for the new user. In this case it will be /export/home/docusp01. It is in the form base_dir/account_name where base_dir is the base directory for the new home directories and account_name is the name for the new account.

-s specifies the shell to use for the new account, which in this case the BASH shell, which is located in /usr/bin.

The final parameter on the line is the account name to create, i.e. docusp01 in this case. It will need to be 8 characters or less in length.

Set a password for the account.
# passwd docusp01

If you need to later change any parameters for the account, you can use the usermod command.

Now that you have created the account you wish to use, you can configure Samba support for that account.

Configuring Samba support for account

You need to edit /etc/sfw/smb.conf (You may wish to create a backup copy first), e.g. cp -p /etc/sfw/smb.conf /etc/sfw/smb.conf.old.

Change the line workgroup = WORKGROUP to match whatever workgroup or domain you use for your Windows systems, e.g. workgroup = SOMECOMPANY.

You can also change server string to be whatever you wish. I changed it from the default of server string = XXP240250 to the following:

server string = Xerox DocuColor 250

Choose which systems should have access to shared folders on the Solaris system by adding a hosts allow line. There is one in the smb.conf file to show you how to configure this line, but it is commented out.

# hosts allow = 192.168.1. 192.168.2.0./24 192.168.3.0/255.255.255.0 127.0.0.1

If my systems are on a 192.168.0.0/24 subnet, i.e. systems have an address of 192.168.0.x and use a subnet mask of 255.255.255.0, I could allow access from any system on the subnet by using 192.168.0.0/24 or 192.168.0. If I only want to allow access from two specific systems, say 192.168.0.25 and 192.168.0.36, plus the Solaris system itself for testing using the loopback address 127.0.0.1, I would add the following line:
hosts allow = 192.168.0.25 192.168.0.36 127.0.0.1

If you wish to set a maximum size for the log file that records information about Samba connections, find #max log size = 50, remove the comment character, # and change the number to whaterver you wish to use, e.g. 16384 for 16 MB.

I also uncommented the line that specifies where the log file is located, but changed the line from:

#log file = /usr/local/samba/var/log.%m

To the following line instead:

log file = /var/log/samba/log.%m

I also created a samba directory under /var/log to hold the Samba logs and then changed its protection so only root can view the logs.

# mkdir /var/log/samba
# chmod 700 /var/log/samba

At the end of the smb.conf file, you can add information about the folder you wish to share. In this case for the DocuSP system, I want to share the folder /var/spool/XRXnps/saved. I want to make it browseable from the Windows systems to which I am granting access, but I don’t want them to be able to add files or modify files in the directory. And I only want to grant acces to the new account, docusp01, that I created, so I added the following lines:

# DocuSP folder shared read-only to Windows systems
[DocuSP]
comment = DocuSP XRXnps saved
path = /var/spool/XRXnps/saved
valid users = docusp01
browseable = yes
public = yes
writable = no
printable = no

The valid users = docusp01 will limit access to only the docusp01 account I created.

I need to grant access to the /var/spool/XRXnps/saved directory. Xerox recommends granting read, write, execute access to everyone for this directory using the command below:

# chmod 777 /var/spool/XRXnps/saved

I issued that command, though I am still restricting access through /etc/smb.conf. The default permission on the directory prior to issuing that command is shown below:

# ls -ld /var/spool/XRXnps/saved
drwxr-xr-x 43 root other 2048 Mar 23 12:55 /var/spool/XRXnps/saved

When I checked while setting up the system, Samba appeared to be running, i.e., I saw smbd running and when I checkd the services on the system, I saw Samba listed:

# ps -ef | grep smb | grep -v grep
root 1005 1 0 Mar 23 ? 0:00 /usr/sfw/sbin/smbd -D
root 1007 1005 0 Mar 23 ? 0:00 /usr/sfw/sbin/smbd -D
# svcs | grep samba
legacy_run Mar_23 lrc:/etc/rc3_d/S90samba

So I stopped and restarted it.

# /etc/init.d/samba stop
# /etc/init.d/samba start

Once I did that, I saw the system appear as SIP-8 in the workgroup used by the company for whom I was setting it up, when I checked on what systems were in the workgroup. But you may not always see the system show up immediately.

C:\>net view /domain:frostinc
Server Name Remark

——————————————————————————-
\\FROSTINC26 Cindy’s Dell Dimension 3000
\\PCWORKSTATION Gateway Profile 4
\\SIP-8 Xerox DocuColor 250
The command completed successfully.

But to allow access from a Windows PC using the account I created, I needed to set a Samba password for the docusp01 account I created on the Solaris system. You can use the smbpasswd command to create a Samba password for the account that can be used to access the shared folder from a Windows system. This can be the same as the one you use for logging into the account under Solaris, but doesn’t necessarily have to be the same as the password for the account.

# /usr/sfw/bin/smbpasswd -a docusp01
New SMB: password:

The -a specifies that you are adding a new account password rather than changing an existing one. When I first ran the command I received the error message shown below.

# /usr/sfw/bin/smbpasswd docusp01
New SMB password:

Retype new SMB password:

startsmbfilepwent_internal: file /opt/XRXnps/XRXsamba/private/smbpasswd did not exist. Couldn’t create new one. Error was: No such file or directoryUnable to open passdb database.
Failed to find entry for user docusp01.
Failed to modify password entry for user docusp01

In the /etc/sfw/smb.conf file, the lines below appeared:

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
encrypt passwords = yes

smb passwd file = /opt/XRXnps/XRXsamba/private/smbpasswd

Once I realized that the directory XRXsamba did not exist, I created it and the private subdirectory beneath it.

# ls /opt/XRXnps/XRXsamba
/opt/XRXnps/XRXsamba: No such file or directory
# mkdir /opt/XRXnps/XRXsamba
# mkdir /opt/XRXnps/XRXsamba/private

I was then able to use the smbpasswd command without the prior error occurring.

# /usr/sfw/bin/smbpasswd -a docusp01
New SMB password:

Retype new SMB password:

startsmbfilepwent_internal: file /opt/XRXnps/XRXsamba/private/smbpasswd did not
exist. File successfully created.
Added user docusp01.

And when I looked in the smbd.log file, I saw an entry indicating the encrypted password file had been created.

# cat /var/log/samba/log.smbd
[2007/03/25 22:27:58, 0] passdb/pdb_smbpasswd.c:(195)
startsmbfilepwent_internal: file /opt/XRXnps/XRXsamba/private/smbpasswd did not exist. File successfully created.

I was then able to access the shared folder from one of the Windows PCs to which I had granted access to the shared folder by listing its IP address in /etc/smb.conf. To access the shared folder on the Solaris system from the PC, I used the username of SIP-8\docusp01 and the password for that account.

C:\>net view \\sip-8
Shared resources at \\sip-8

Xerox DocuColor 250

Share name Type Used as Comment

——————————————————————————-
DocuSP Disk (UNC) DocuSP XRXnps saved
The command completed successfully.

And from the Solaris system, I could issue the smbstatus command and see the access from the Windows PC.

# /usr/sfw/bin/smbstatus
creating lame upcase table
creating lame lowcase table

Samba version 3.0.11
PID Username Group Machine
——————————————————————-
8446 docusp01 staff pcworkstation (192.168.0.26)

Service pid machine Connected at
——————————————————-
DocuSP 8446 pcworkstation Sun Mar 25 22:43:58 2007

No locked files

And I saw entries appear in /var/log/samba/log.pcworkstation for the connection from the PC.

I could also issue the smbclient command from the Solaris system to view shared directories on the Windows PC.

# /usr/sfw/bin/smbclient -L 192.168.0.25 -U Smith

For the smbclient command, the -L parameter specified the address of the PC and the -U parameter specified an account on that Windows PC, for which I received a password prompt

I also set up Samba on a second DocuSP system, SIP-3. When I created a shortcut on the Windows PC’s desktop, I had to specify the IP address of the Solaris DocuSP system instead of SIP-3, e.g. I had to use \\192.168.0.36\docusp as the location. When prompted for the userid and password, I entered \\SIP-3\docusp-1 as the username and the password for that account set up through smbpasswd on the Solaris system. It was accepted and I was able to access files on the DocuSP system through the shortcut. But the system wasn’t showing up when I entered the command net view /domain:somecompany.

You can also manage Samba via the web console, the url for this interface is http://servername:901

Many SEOs suggest that the first thing you should do is to get your site listed in DMOZ to help boot your page rank. There are just as many SEOs who claim that getting your site listed in DMOZ is worthless. Strangely there are many sites listed in the DMOZ that should have never been approved. There are broken links, links that redirect to different site, and sites that looks like crap.

Here is an example, if you wanted to find out which file in the directory /home contains the word groundhog.

grep –i “groundhog” /home/*
/home/shadow:Today is groundhog day

The –i option means grep will ignore upper/lower case distinction during comparisons.
The word to search for is enclosed in double quotes, “groundhog”.
/home is the directory to search in and the * signifies all files.
The file /home/shadow contains the word groundhog, the content of the line containing the word groundhog is displayed on screen.

But what if you wanted to search for a string of words. Grep only searches for a single word. Egrep will search all files for a string of words. Here is an excerpt from the man pages of Solaris 10.

The egrep (expression grep) utility searches files for a
pattern of characters and prints all lines that contain that
pattern. egrep uses full regular expressions (expressions
that has string values that use the full set of
alphanumeric and special characters) to match the patterns.
It uses a fast deterministic algorithm that sometimes needs
exponential space.

Below is an example of egrep.

egrep –i “Apple announces the release of the ipad” /home/*
/home/obama: Today Apple announces the release of the ipad

#!/bin/sh
# This script archive directories and create a log file with the time and date stamp.
# Andrew Lin
# www.GamesCheat.ca
# 27 January, 2010

cd /backup/archive
echo “Backup start: ” > backup.log 2>&1
date >> backup.log 2>&1

cd /export/home

# tar cvf /backup/archive/backup.tar dir1 dir2 >> /backup/archive/backup.log 2>&1

tar cvf /backup/archive/backup.tar dir1 dir2 2>>/backup/archive/backup.log

echo “Backup Stop: ” >> /backup/archive/backup.log 2>&1
date >> /backup/archive/backup.log 2>&1

#!/bin/sh
This indicates that the script is written to be executed in the Bash shell.

The # sign indicates the line is a comment.

cd /backup/archive
Change the path /backup/archive to where this script is located on your machine.

echo “Backup start: ” > backup.log 2>&1
Create a file backup.log. The text Backup start: is inserted into this file. The file will be created in the directory
/backup/archive.

date >> backup.log 2>&1
The date will be appended into the file backup.log. This is useful if you wanted to determine the time of execution of the script.

cd /export/home
Go to the directory /export/home. This directory contains the files or directories you wish to backup.

# tar cvf /backup/archive/backup.tar dir1 dir2 >> /backup/archive/backup.log 2>&1
This line is commented out with the # sign. Uncomment this line if you want a detailed log of the tar command. Success and failure will be recorded in the log. Depending on the amount of files being archived this log could become very long.

tar cvf /backup/archive/backup.tar dir1 dir2 2>>/backup/archive/backup.log
This command will copy the directories dir1 and dir2. The copies will be stored in /backup/archive/backup.tar. Any error will be recorded in the file backup.log. If you wanted both error and success recorded then comment this line out and uncomment the line above it.

echo “Backup Stop: ” >> /backup/archive/backup.log 2>&1
After the completion of the tar command, insert the line Backup Stop: into the file backup.log.

date >> /backup/archive/backup.log 2>&1
Insert the date and time into the file backup.log. This is useful for determining the completion time/date of the script.

Save this file with the name of backup-script. Make sure that you make the file executable, with the chmod command, e.g.
chmod 777 backup-script.log

ls –b
scritps010/010/010/010

I tried every command I could think of, rmdir “scripts”, rmdir “scripts010/010/010/010”. The only way to remove this directory was to delete it using the inode number.

To determine the inode use the -i option with the ls command.
ls –i
184538 scritps

Below is the command syntax to delete the directory.
find . –inum 184538 –exec rmdir {} \;

If you wanted to delete a stubborn file then simply substitute rmdir with rm.
find . –inum 184538 –exec rm {} \;

sharpandshiny – Upgrade Everything 1 Level
WarpTen – expedite construction of buildings and units
IocainePowder – Die real fast
itvexesme Cannot Win
riseandshine – Automatic Daylight
WhosYourDaddy – God mode (reminds me of Doom, I have not played that in a long time)
KeyserSoze [amount] – Get gold without having to mine it
LeafitToMe [amount] – Get lumber wihout having to do any work
GreedIsGood [amount] – My favourite, I give myself plenty of resourzes
PointBreak – No food limit
ThereIsNoSpoon – infinite amount of Mana
StrengthAndHonor – No defeat mode.
Motherland [race] [level] – skip to whatever level you wish to
SomebodySetUpUsTheBomb – Instant defeat, like Japenese soldiers committing sucide when close to defeat, during World War II
AllYourBaseAreBelongToUs – Instant victory, what’s the point ? might as wll not play
WhoIsJohnGalt – Research enabled
SharpAndShiny – Research upgrades
IseeDeadPeople – Remove fog of war, funny sense of humor
Synergy – Disable tech tree requirements
RiseAndShine – change time of day to dawn
LightsOut – change time of day to dusk
DaylightSavings [hour] – Reset the time to the hour specificed (without a number, this toggle the day/night cycle on/off)
TheDudeAbides

/etc/inet/hosts this file is a hard link to /etc/inet/ipnodes. You will need to make /etc/inet/ipnodes writable before editing it. To enable write use the command chmod 744 /etc/inet/ipnodes.

Finally rename directory /var/crash, the system will automatically recreate this after rebooting.
# cd /var
# mv crash crash.old

Now reboot the server.