Monday, September 14, 2009
Anyway I found these two article which might help, if you are looking for article that help you create icon that cant be deleted by user or we call it shell object.
Add Custom Folder to My Computer or the Desktop (All Windows) Popular
Shellfolders & -objects
Create and add your own folders/objects at places you're not supposed to, and make them behave like shell objects.
Manage Everything IT... for Free!
Spiceworks is the complete network management & monitoring, helpdesk, PC inventory & software reporting solution to manage Everything IT in small and medium businesses.
Powered by 750,000 IT Pros Like You
The Spiceworks IT Community is available to answer questions while you work directly in the application.
It’s 100% Free. Download Now!
Spiceworks is completely free…and you can get started in less than 5 minutes. Download now.
Monday, September 7, 2009
Few days ago, I’ve received 50 new servers without any OS preinstalled. The servers came without floppy drive and CD/DVD. I tried to connect an external CD (USB) or Disk on Key, but servers didn’t start. So, I decided to run PXE Boot. If you don't know what PXE is, here’s what is written in Wikipedia:
“The Preboot Execution Environment (PXE, aka Pre-Execution Environment, or 'pixie') is an environment to boot computers using a network interface card independently of available data storage devices (like hard disks) or installed operating systems.”
There are several solutions of PXE implementation. Microsoft has its Remote Installation Service (RIS), there are sort of HP, Symantec and Acronics. Some of them are based on Linux.
I decided not to straggle with Microsoft RIS or Linux and fortunately I found a more simple solution.
So, here is an explanation of what I did:
WHAT WE NEED:
1. Additional Computer, running Windows to act as the PXE server. I have used Windows XP.
2. Syslinux-3.51.zip (or other version) from http://www.kernel.org/pub/linux/utils/boot/syslinux/ (We need only a few files).
3. DHCP and TFTP Server software for windows (I used TFTPD32. As a DHCP server you can use a MS DHCP Server from Windows 2000/2003).
4. DOS bootable floppy. I have used a boot image with NetBoot and Boot image of clean Windows 98. Both images can be downloaded here.
Download the software above into a temporary folder on the computer that will act as the PXE Server.
1. On the future PXE server, create a following directory structure:
----- pxelinux.cfg (This is a directory, not a file)
2. Download and Unpack syslinux-3.51.zip in any Temp directory. We need only 2 file from the archive. Take a pxelinux.0 and put it in the root of C:\PXEServer\TFTPRoot\Boot . Then, from the directory memdisk take 'memdisk' file and put it same place (C:\PXEServer\TFTPRoot\Boot).
Take file menu.c32 (from \syslinux-3.51\com32\modules) and put it to the C:\PXEServer\TFTPRoot\Boot.
3. Download Tftpd32 v3.03 from http://www.jounin.net/tftpd32_download.html and extract the tftpd32.exe files to C:\PXEServer.
4. Now we need a boot disk image. You can take a boot floppy and create an image, by using the WinImage. I have downloaded Universal TCP / IP Network Boot disk from http://www.netbootdisk.com/
Created diskette, and then made an IMA image in WinImage.
NOTE : Universal TCP / IP Network Boot disk uses a boot disk which created at Windows XP. It was a problem to use this diskette for PXE boot, so I took all files from created disk and placed them in the boot disk of Windows 98. If you do not have time to create an image, you can simply download it here.
5. Inside pxelinux.cfg create a text file default. Please note that the file should be NO extension. In my file you have an option to select which boot image to use, image with network Support (Universal TCP / IP Network Boot disk) or simply use a clean boot of Windows 98. Here is a content of my default file:
MENU TITLE PXE Boot System
MENU LABEL ^Network Boot
MENU LABEL ^Clean Win 98 Boot
MENU LABEL ^Boot Normal
6. Now, let’s run tftpd32.exe. In Global Settings select TFTP Server and DHCP Server. See Figure 1 for an example of my setup. After finishing settings click OK.
7. On the DHCP Server tab make settings appropriate for your network. The one of the most important settings, this is' Boot file '. Set the 'Boot file' to ' /boot/pxelinux.0 '. See Figure 2 for an example of my setup. Remember to click on SAVE button.
8. The server setup is DONE! Now, you can turn on a new server and choose at startup PXE Boot. Further installation, is a thing of technology :).
Note: If you already have any DHCP server at your network, it will be a problem. I'd like to advise to disable another DHCP server or to configure it as written above. For example Microsoft DHCP Server Boot option file is 67 (67 Bootfile Name).
Since I've published article "PXE, aka Pre-Execution Environment - Part 1" I've got a lot of emails with the same question - 'Where is a Part 2?". So, here it is.
I know many Network Administrators who work with Acronis products and i also sometime work with those good products. This week i did a project for one of my clients in Seattle, WA. The main idea was to deploy an Acronis image on new servers and configure those servers according to system requirements. So, again, those servers came without floppy drive and CD/DVD :) and as all of you know, to restore Acronis image on a new machine we have to use Bootable Rescue Media, aka Bootable CD with Acronis on it. Yes, I know, that Acronis provides a products with PXE integrated, but i don't have it :) and I've used my own PXE server.
The first step I did was create Bootable Rescue Media. Then I took 2 files, kernel.dat and ramdisk.dat from Acronis's directory and put them into C:\PXEServer\TFTPRoot\Boot directory. Well, now was the time to make a small changes to our "default" file (default file located in C:\PXEServer\TFTPRoot\Boot\pxelinux.cfg\ directory). After all those changes my "default" file now looks as follow:
MENU TITLE PXE Boot System
MENU LABEL ^Acronis Bootable
append initrd=ramdisk.dat vga=791 ramdisk_size=32768 acpi=off quiet noapic
MENU LABEL ^Network Boot
MENU LABEL ^Clean Win 98 Boot
MENU LABEL ^Memory Test
Thanks to time PXE saved me I was able to spend some time in very beautiful city Seattle.
Friday, September 4, 2009
The VI editor is a screen-based editor used by many Unix users. The VI editor has powerful features to aid programmers, but many beginning users avoid using VI because the different features overwhelm them. This tutorial is written to help beginning users get accustomed to using the VI editor, but also contains sections relevant to regular users of VI as well. Examples are provided, and the best way to learn is to try these examples, and think of your own examples as well... There's no better way than to experience things yourself.
In this tutorial, the following convention will be used:
^X denotes a control character. For example, if you see: ^d in the tutorial, that means you hold down the control key and then type the corresponding letter. For this example, you would hold down the control key and then type d.
The VI editor uses the full screen, so it needs to know what kind of terminal you have. When you log in, wiliki should ask you what terminal you have. The prompt looks like this:
TERM = (vt100)
If you know your terminal is a vt100 (or an emulator that can do vt100), just hit return for the terminal type when you log in. If you have an hp terminal, type "hp" for the terminal type and hit return. If you are not sure what kind of terminal you have, ask a lab monitor, or have someone help you set the correct terminal type.
If you make an error when you log in and type the wrong terminal type, don't panic and log out. You can type the following commands to fix the settings:
First, tell your shell what type of terminal you have. (If you're not sure what your shell is, type this command to see what shell you have: echo $SHELL.) For the examples given, the terminal type is "vt100". Substitute it with whatever terminal type you have. For C shell (/bin/csh), the command is this:
set term=vt100For Bourne Shell (/bin/sh) or Korn Shell (/bin/ksh), the commands are the following:
export TERMNext, reset your terminal with this command:
Now that the terminal type is (hopefully) correctly set, you are ready to get started with VI.
The VI editor lets a user create new files or edit existing files. The command to start the VI editor is vi, followed by the filename. For example to edit a file called temporary, you would type vi temporary and then return. You can start VI without a filename, but when you want to save your work, you will have to tell VI which filename to save it into later.
When you start VI for the first time, you will see a screen filled with tildes (A tilde looks like this: ~) on the left side of the screen. Any blank lines beyond the end of the file are shown this way. At the bottom of your screen, the filename should be shown, if you specified an existing file, and the size of the file will be shown as well, like this:
"filename" 21 lines, 385 charactersIf the file you specified does not exist, then it will tell you that it is a new file, like this:
"newfile" [New file]If you started VI without a filename, the bottom line of the screen will just be blank when VI starts. If the screen does not show you these expected results, your terminal type may be set wrong. Just type :q and return to get out of VI, and fix your terminal type. If you don't know how, ask a lab monitor.
Now that you know how to get into VI, it would be a good idea to know how to get out of it. The VI editor has two modes and in order to get out of VI, you have to be in command mode. Hit the key labeled "Escape" or "Esc" (If your terminal does not have such a key, then try ^[, or control-[.) to get into command mode. If you were already in the command mode when you hit "Escape", don't worry. It might beep, but you will still be in the command mode.
The command to quit out of VI is :q. Once in command mode, type colon, and 'q', followed by return. If your file has been modified in any way, the editor will warn you of this, and not let you quit. To ignore this message, the command to quit out of VI without saving is :q!. This lets you exit VI without saving any of the changes.
Of course, normally in an editor, you would want to save the changes you have made. The command to save the contents of the editor is :w. You can combine the above command with the quit command, or :wq. You can specify a different file name to save to by specifying the name after the :w. For example, if you wanted to save the file you were working as another filename called filename2, you would type: w filename2 and return.
Another way to save your changes and exit out of VI is the ZZ command. When in command mode, type ZZ and it will do the equivalent of :wq. If any changes were made to the file, it will be saved. This is the easiest way to leave the editor, with only two keystrokes.
The first thing most users learn about the VI editor is that it has two modes: command and insert. The command mode allows the entry of commands to manipulate text. These commands are usually one or two characters long, and can be entered with few keystrokes. The insert mode puts anything typed on the keyboard into the current file.
VI starts out in command mode. There are several commands that put the VI editor into insert mode. The most commonly used commands to get into insert mode are a and i. These two commands are described below. Once you are in insert mode, you get out of it by hitting the escape key. If your terminal does not have an escape key, ^[ should work (control-[). You can hit escape two times in a row and VI would definitely be in command mode. Hitting escape while you are already in command mode doesn't take the editor out of command mode. It may beep to tell you that you are already in that mode.
The command mode commands are normally in this format: (Optional arguments are given in the brackets)
- [count] command [where]
The count is entered as a number beginning with any character from 1 to 9. For example, the x command deletes a character under the cursor. If you type 23x while in command mode, it will delete 23 characters.
Some commands use an optional where parameter, where you can specify how many lines or how much of the document the command affects, the where parameter can also be any command that moves the cursor.
Here is a simple set of commands to get a beginning VI user started. There are many other convenient commands, which will be discussed in later sections.
- enter insert mode, the characters typed in will be inserted after the current cursor position. If you specify a count, all the text that had been inserted will be repeated that many times.
- move the cursor to the left one character position.
- enter insert mode, the characters typed in will be inserted before the current cursor position. If you specify a count, all the text that had been inserted will be repeated that many times.
- move the cursor down one line.
- move the cursor up one line.
- move the cursor to the right one character position.
- replace one character under the cursor. Specify count to replace a number of characters
- undo the last change to the file. Typing u again will re-do the change.
- delete character under the cursor. Count specifies how many characters to delete. The characters will be deleted after the cursor.
The VI editor has 36 buffers for storing pieces of text, and also a general purpose buffer. Any time a block of text is deleted or yanked from the file, it gets placed into the general purpose buffer. Most users of VI rarely use the other buffers, and can get along without the other buffers. The block of text is also stored in another buffer as well, if it is specified. The buffer is specified using the " command. After typing ", a letter or digit specifying the buffer must be entered. For example, the command: "mdd uses the buffer m, and the last two characters stand for delete current line. Similarly, text can be pasted in with the p or P command. "mp pastes the contents of buffer m after the current cursor position. For any of the commands used in the next two sections, these buffers can be specified for temporary storage of words or paragraphs.
The command commonly used command for cutting is d. This command deletes text from the file. The command is preceded by an optional count and followed by a movement specification. If you double the command by typing dd, it deletes the current line. Here are some combinations of these:
- deletes from current cursor position to the beginning of the line.
- deletes from current cursor position to the end of the line.
- deletes from current cursor position to the end of the word.
- deletes three lines from current cursor position downwards.
There is also the y command which operates similarly to the d command which take text from the file without deleting the text.
The commands to paste are p and P. The only differ in the position relative to the cursor where they paste. p pastes the specified or general buffer after the cursor position, while P pastes the specified or general buffer before the cursor position. Specifying count before the paste command pastes text the specified number of times.
The VI editor has features to help programmers format their code neatly. There is a variable that to set up the indentation for each level of nesting in code. In order to set it up, see the customization section of this tutorial. For example, the command to set the shift width to 4 characters is :set sw=4.
The following commands indent your lines or remove the indentation, and can be specified with count:
- Shifts the current line to the left by one shift width.
- Shifts the current line to the right by one shift width.
The VI editor also has a helpful feature which checks your source code for any hanging parentheses or braces. The % command will look for the left parenthesis or brace corresponding to a particular right parenthesis or brace and vice versa. Place the cursor onto a parenthesis or brace and type % to move the cursor to the corresponding parenthesis or brace. This is useful to check for unclosed parentheses or braces. If a parenthesis or brace exists without a matching parenthesis or brace, VI will beep at you to indicate that no matching symbol was found.
The VI editor has two kinds of searches: string and character. For a string search, the / and ? commands are used. When you start these commands, the command just typed will be shown on the bottom line, where you type the particular string to look for. These two commands differ only in the direction where the search takes place. The / command searches forwards (downwards) in the file, while the ? command searches backwards (upwards) in the file. The n and N commands repeat the previous search command in the same or opposite direction, respectively. Some characters have special meanings to VI, so they must be preceded by a backslash (\) to be included as part of the search expression.
- Beginning of the line. (At the beginning of a search expression.)
- Matches a single character.
- Matches zero or more of the previous character.
- End of the line (At the end of the search expression.)
- Starts a set of matching, or non-matching expressions... For example: /f[iae]t matches either of these: fit fat fet In this form, it matches anything except these: /a[^bcd] will not match any of these, but anything with an a and another letter: ab ac ad
- Put in an expression escaped with the backslash to find the ending or beginning of a word. For example: /\
should find only word the, but not words like these: there and other.
- See the '<' character description above.
The character search searches within one line to find a character entered after the command. The f and F commands search for a character on the current line only. f searches forwards and F searches backwards and the cursor moves to the position of the found character.
The t and T commands search for a character on the current line only, but for t, the cursor moves to the position before the character, and T searches the line backwards to the position after the character.
These two sets of commands can be repeated using the ; or , command, where ; repeats the last character search command in the same direction, while , repeats the command in the reverse direction.
You can customize the way VI behaves upon start up. There are several edit options which are available using the :set command, these are the VI and EX editor options available on Wiliki: (You can get this list by typing :set all and then return in command mode)
autoprint mesg noshowmode
noautowrite nomodelines noslowopen
nobeautify nonumber tabstop=8
directory=/tmp nonovice taglength=0
nodoubleescape nooptimize tags=tags /usr/lib/tags
noedcompatible paragraphs=IPLPPPQPP LIpplpipnpbp term=xterm
noerrorbells prompt noterse
noexrc noreadonly timeout
flash redraw timeoutlen=500
hardtabs=8 remap ttytype=xterm
noignorecase report=5 warn
keyboardedit scroll=11 window=23
keyboardedit! sections=NHSHH HUuhsh+c wrapscan
nolisp shell=/bin/csh wrapmargin=0
nolist shiftwidth=8 nowriteany
Some of these options have values set with the equals sign '=' in it, while others are either set or not set. (These on or off type of options are called Boolean, and have "no" in front of them to indicate that they are not set.) The options shown here are the options that are set without any customization. Descriptions of some of these are given below, with an abbreviation. For example, the command set autoindent, you can type :set autoindent or :set ai. To unset it, you can type :set noautoindent or :set noai.
One EX editor command that is useful in the VI editor is the abbreviate command. This lets you set up abbreviations for specific strings. The command looks like this: :ab string thing to substitute for. For example, if you had to type the name, "Humuhumunukunukuapua`a" but you didn't want to type the whole name, you could use an abbreviation for it. For this example, the command is entered like this:
To remove a previously defined abbreviation, the command is unabbreviate. To remove the previous example, the command would be ":una 9u" To get your listing of abbreviations, simply just type :ab without any definitions.
Another EX editor command that is useful for customization is the mapping command. There are two kinds of mapping commands. One for command mode, and the other for insert mode. These two commands are :map and :map! respectively. The mapping works similarly to the abbreviation, and you give it a key sequence and give it another key sequence to substitute it with. (The substituted key sequences are usually VI commands.)
There are two ways to customize the VI editor. If you create a file called .exrc in your home directory, all the commands in there will be read when VI starts up. The other method is to set an environment variable called EXINIT. The options will be set in your shell's setup file. If you use /bin/csh (C-Shell), the command is as follows, and is put in the .cshrc file:
setenv EXINIT '...'If you use /bin/sh or /bin/ksh, the command is as follows, and is put into the .profile file:
export EXINITDon't put in ... as the example says. In this space put the commands that you want to set up. For example, if you want to have auto indent, line numbering, and the wrap margin of three characters, then the setenv command (for C shell) looks like this:
setenv EXINIT 'set ai nu wm=3'
If you want to put more than one command in the setenv EXINIT thing, separate the commands with a vertical bar (|). For example, to map the 'g' command to the 'G' character in command mode, the command is :map g G, and combined with the above command, you get this:
setenv EXINIT 'set ai nu wm=3|map g G'
If you want to create the file called .exrc, you can put exactly the same things in the file as shown in the quotes after the EXINIT.
The VI editor edits a temporary copy of your file, and after the editing is complete, or when you tell it to save, it puts the contents of the temporary copy into the original file. If something goes wrong while you are editing your file, the VI editor will attempt to save whatever work you had in progress, and store it for later recovery. (Note: If VI dies while you were working on any file, it sends you an email message on how to recover it. The -r option stands for recovery. If you were editing the file vitalinfo, and you accidentally got logged out, then the -r option of the 'vi' editor should help. The command would look somewhat like this: vi -r vitalinfo After using the -r option once, though, you MUST save what you have recovered to the actual file... The -r option only works once per failed VI session.
There are two things to be aware of when using the workstations: Editing the same file many times at once, and changing the size of the screen.
Because VI edits a copy of your original file and saves the contents of that copy into the original file, if you are logged on more than once and are editing the same file more than once using VI, if you save on one window and then you save on the other window, the changes made to the file on the first save would be overwritten. Make sure that you only run one copy of VI per file.
If you use a terminal program from a workstation, you can change the size of the screen by dragging the sides of the window. If the size is not working properly, the command to type is this:
eval `resize`If that doesn't work the command would be this:
eval `/usr/bin/X11/resize`If the size is wrong, the editor will not operate correctly. If you have any problems with the screen size, ask the monitors in the computer lab for help setting the sizes correctly.
This list is a summary of VI commands, categorized by function. There may be other commands available, so check the on-line manual on VI. For easy reference, you can save this file as text and delete any commands you don't think you would use and print out the resulting shorter file.
The VI editor is built upon another editor, called EX. The EX editor only edits by line. From the VI editor you use the : command to start entering an EX command. This list given here is not complete, but the commands given are the more commonly used. If more than one line is to be modified by certain commands (such as ":s" and ":w" ) the range must be specified before the command. For example, to substitute lines 3 through 15, the command is ":3,15s/from/this/g".
Thursday, September 3, 2009
SSH Automatic Login
Of course this is not the right phrase for it. It should be something like “key-based authorization with SSH”. Or simply “publickey authorization”. Or “unattended ssh login”. But I guess you know what I mean.
Here are the steps:
1. Create a public ssh key, if you haven’t one already.
Look at ~/.ssh. If you see a file named id_dsa.pub then you obviously already have a public key. If not, simply create one. ssh-keygen -t dsa should do the trick.
Please note that there are other types of keys, e.g. RSA instead of DSA. I simply recomend DSA, but keep that in mind if you run into errors.
2. Make sure your .ssh dir is 700:
chmod 700 ~/.ssh
3. Get your public ssh key on the server you want to login automatically.
A simple scp ~/.ssh/id_dsa.pub firstname.lastname@example.org: is ok.
4. Append the contents of your public key to the ~/.ssh/authorized_keys and remove it.
Important: This must be done on the server you just copied your public key to. Otherwise you wouldn’t have had to copy it on your server.
Simply issue something like cat id_dsa.pub >> .ssh/authorized_keys while at your home directory.
5. Instead of steps 3 and 4, you can issue something like this:
cat ~/.ssh/id_dsa.pub | ssh -l remoteuser remoteserver.com 'cat >> ~/.ssh/authorized_keys'
6. Remove your public key from the home directory on the server.
You can now login:
ssh -l remoteuser remoteserver.com or ssh email@example.com without getting asked for a password.
That’s all you need to do.
I found these steps from : http://wp.uberdose.com/2006/10/16/ssh-automatic-login/
If you working with Solaris, may be this guide will help you.
Setting Up SSH For No Password
Peter Cvar, April 2006
This setup will allow you to log in to another account without having to provide the password.
man ssh-keygen is a start, but it might need some clarifying for beginners.
This Tech Tip concentrates on SSH2, the second version of SSH. Don't use the first version any longer; it contains security bugs. Also, older versions of the second version might contain security bugs. Check with ssh -V that your version matches the latest one available from OpenSSH.
If you can't find any of the SSH commands (ssh and scp, for instance) on your system, get the SSH package first and install it. This suite should also install the ssh-keygen command on your machine. Make sure that SSH is installed on every system that you want to access. Starting from the Solaris 9 OS, SSH is included in the distribution.
If you can't find a package suitable for your version, refer to the OpenSSH web site for the source, and then download, unpack, read the README, compile, and install. Systems missing OpenSSL have to add that package as well for SSH to work. Test, for example, ssh localserver; this will create a .ssh subdirectory in your home directory.
In your ~/.ssh directory, create your personal SSH key:
server1:~/.ssh> ssh-keygen -t dsa
This creates id_dsa and id_dsa.pub in ~/.ssh.
If you want to enable remote connections that don't require a password, do not enter a passphrase. If you do enter a non-empty passphrase, when connecting to the remote server you will be asked for the passphrase instead of the password!
Append the public key to the file authorized_keys2:
server1:~/.ssh> cat id_dsa.pub >> authorized_keys2
Don't worry if authorized_keys2 does not yet exist before you execute this command.
Sun provides SSH in the Solaris OS starting from release 9, but uses SSH version 1 naming conventions. On the Solaris 9 OS, use the authorized_keys file instead of authorized_keys2.
Now you should already be able to make a secure connection to your own machine, using this account, without having to provide a password.
Check permissions on your keys and refer to the man page. The id_dsa file should be private, the other keys world readable. On the remote server, generate keys in the same way for your account on that server.
Copy your public key into ~/.ssh/ on the remote server.
server1:~/.ssh> scp id_dsa.pub server2:/your/remote/home/.ssh/server1.key.pub
id_dsa.pub 100% |*****************************| 236 00:00
Do the same thing for the remote key; copy it into your local ~/.ssh directory:
server1:~/.ssh> scp server2:/your/remote/home/.ssh/id_dsa.pub ./server2.key.pub
id_dsa.pub 100% |*****************************| 236 00:00
On both servers, append the key from the other server to the file authorized_keys2:
server1:~/.ssh> cat server2.key.pub >> authorized_keys2
And also for the second server:
user@server2:~/.ssh> cat server1.key.pub >> authorized_keys2
That's it! Try to connect to the remote server now. It should do something similar to this:
server1:~/.ssh> ssh server2
Last login: Mon Nov 21 16:23:26 2005 from :0
If things don't work, check the logs, possibly in /var/log/secure. This file contains useful information, such as:
Nov 21 10:24:41 ocean sshd: Authentication refused: bad ownership or
modes for file /home/name/.ssh/authorized_keys
Most likely, the problem is too many permissions.
By default, the Solaris OS doesn't allow ssh as root. Edit /etc/ssh/sshd_config and change the PermitRootLogin directive. Restart sshd for these changes to take effect.
Also on the Solaris OS, make sure that you use the file ~/.ssh/authorized_keys, without the two suffixes. The Solaris OS uses version 2 of ssh but without the version 2 naming convention.
A typical entry in ~/.ssh/authorized_keys(2) looks like this:
Line broken at the '\' for readability.
If you can't connect to a remote server using a particular user name on that server, check that the appropriate key is in your authorized_keys(2) file, and that the remote server name, encryption method, and user name exist.
Use ssh -v, scp -v or sftp -v to display verbose output and analyze any other problems that you might come across.
This guide is from : http://www.sun.com/bigadmin/content/submitted/ssh_setting.html