2) Use –export option to export your public key in text file
$ gpg –export –a > my.key
OR
$ gpg –export -a | mail -s “My key” friend@domain.com

Where
-a –armor : Create ASCII armored output.
–export : Export the key for sharing

First command write output to file my.key and second directly sends an email to your friend. Once my.key delivered to friend, he/she need to import it using the following command (aka adding keys to your keyring):
$ gpg –import my.key

It is never good practice for anyone to use root as their normal user account because simple typographical errors in entering commands can cause major damage to the system. It is recommended to create a normal user account instead and then use the su command to switch when necessary. Some use the sudo utility instead, which allows a measure of graduated access. Following script find out all root user account on system.

#!/bin/bash
# Shell script to Finding ALL Superuser Accounts
# Useful to improve system security.
# Copyright (c) 2005 nixCraft
# This script is licensed under GNU GPL version 2.0 or above
# For more info, please visit:
#            http://cyberciti.biz/shell_scripting/bmsinstall.php
# -------------------------------------------------------------------------
# This script is part of nixCraft shell script collection (NSSC)
# Visit http://bash.cyberciti.biz/ for more information.
# -------------------------------------------------------------------------
grep -v -E "^#" /etc/passwd | awk -F: '$3 == 0 { print $1}'

1) First put CDROM/DVD into drive

2) For CDROM: After few second change directory /cdrom/cdrom0 or /cdrom/VOL_NAME

# cd /cdrom/cdrom0

3) For DVDROM: After few second change directory /dvd/VOL_NAMRE

If this does not works make sure volmgt daemon is running:

# /etc/init.d/volmgt start

Scan for devices both cd or floopy using:

#volcheck

1) Boot from Solaris 1st CD

2) At Solaris Device Configuration Assistant, Press F2 key

3) Then press ENTER key twice

4) At Identified Devices, Press F2 key

5) At Boot Solaris, select CD to boot system

6) At next screen system will ask about to “Select the type of Installation”, type
the argument b –s and press ENTER key to boot system into single user mode.

7) Next at shell prompt type the following commands -:

# mount /dev/dsk/c0d0s0 /a
# TERM=ansi
# export TERM
# cd /a

You can access the system.

9) When done type as follows to reboot the system:

# cd /
# umount /a
# init 6

SPARC: To boot system for emergency mode (boot from CD), at ok prompt type:

boot cdrom -s
# mount /dev/dsk/c0t1d0s0 /a
# cd /a
# TERM=vt100
# export TERM
# cd /
# umount /a
# init 6

setuid and setgid are needed for tasks that require higher privileges than those which a common user has, such as changing his or her login password. Some of the tasks that require elevated privileges may not immediately be obvious, though — such as the ping command, which must send and listen for control packets on a network interface.

Sample Shell Script

#!/bin/bash
# Shell script to find all programs and scripts with setgid bit set on.
# If your system ever cracked (aka hacked) then system has this kind of binary
# installed; besides the normal setuuid scripts/programs
# Copyright (c) 2005 nixCraft project
# This script is licensed under GNU GPL version 2.0 or above
# For more info, please visit:
#            http://cyberciti.biz/shell_scripting/bmsinstall.php
# -------------------------------------------------------------------------
# This script is part of nixCraft shell script collection (NSSC)
# Visit http://bash.cyberciti.biz/ for more information.
# -------------------------------------------------------------------------
#SPATH="/usr/local/etc/bashmonscripts"
#INITBMS="$SPATH/defaults.conf"
#[ ! -f $INITBMS ] && exit 1 || . $INITBMS

[ $# -eq 1 ] && : || die "Usage: $($BASENAME $0) directory" 1

DIRNAME="$1"
$FIND $DIRNAME -xdev -type f -perm +g=s -print

1) To get PATH (or directories name) type command:

# sysctl kern.module_path

OR

# kldconfig -r

2) The path can modified in /boot/loader.conf file, open this file and look for entry called module_path:

# grep “modile_path” /boot/loader.conf

module_path=”/boot/kernel;/boot/modules;/modules;/new/path”

Note you must open /boot/loader.conf file to change path settings using text editor:

# vi /boot/loader.conf

And make changes to file.

3) Reboot system to take effect.

4) Or on fly, you can add/append path using kldconfig utility, read man page for more info.

When you try and rename it the following is given:

$ mv ––index.html index.html.renamed
mv: unrecognized option `––index.html’
Try `mv ––help’ for more information.

I also tried delimiting it the normal way, but it wouldn’t work either:

    mv \–\–index.html index.html.renamed

The correct way to rename it is:

    mv ./––index.html index.html.renamed

Because –– has special meaning, you can’t delimit it with a simple backslash (\), you have to put a path reference in there to delimit it. So my path working directory (pwd) was /home/user/data/ where the file was located, so I could use ./ to reference the current pwd. The other option is to put the full path in:

    mv /home/user/data/––index.html index.html.renamed

Hopefully this helps out some other Linux server administrator out there who’s mind it has slipped.

You need to use the usermod command. It can modify the system account files (such as /etc/passwd) to reflect the changes that are specified on the command line. The syntax is as follows:
usermod -l {new-login-name} {current-old-login-name}
In this example, rename login id from tom to jerry. Open a command-line terminal (select Applications > Accessories > Terminal), and then type the following command
$ sudo usermod -l jerry tom
To verify new changes, enter:
$ id jerry

Incoming search terms:

• plesk hide information_schema (2)
• ubuntu: rename an account (1)