Once again for the solaris: How to configure FTP/Telnet to login as root .

Note# THis is just for the practice, make sure that you NEVER configure your production servers for this type of login.

Configure FTP for root logins :

1) First remove the ‘root’ line from /etc/ftpusers.

2) Also, don’t forget to edit the file /etc/ftpaccess and comment out the ‘deny-uid’ and ‘deny-gid’ lines. If the file doesn’t exist, there is no need to create it.

3) If you are using Solaris 9 or Solaris 10, the ftp* files are located in /etc/ftpd.

Configure Telnet for root logins :

Simply edit the file /etc/default/login and comment out the following line like as :

# If CONSOLE is set, root can only login on that device.
# Comment this line out to allow remote login by root.
#
# CONSOLE=/dev/console

Greetings,

Lets start with the basic.

Source: Youve probably seen this before Download Source In Linux (or unix) you will most likely be dealing with source code. This is actually the raw instructions that are written by the programmer. You can not run these! So dont try icon_smile.gif. You need to first compile them (well get to that later)

Binaries: Binaries are code that has been compiled. If you are downloading binaries you will need to insure that the binary was compiled on the same distro and chipset you are using. Most Linux users will always say it is better to compile everything from the source. In most cases this is true. But, if you are a beginner try to find binaries:-)

Compiler: This is the actual program that interprets the source into a binary format. Logically, your compiler must be for the language the source was written. The vast majority of the time it will be a C compiler, the most common is gcc.

Files you will need:
A compiler (duh) ok for this tutorial we are going to use gcc.

Redhat 8.0
ftp://rpmfind.net/linux/redhat/8.0/en/os/i386/RedHat/RPMS/gcc-3.2-7.i386.rpm
Source
ftp://rpmfind.net/linux/redhat/8.0/en/os/i386/SRPMS/gcc-3.2-7.src.rpm

Mandrake
ftp://rpmfind.net/linux/Mandrake/9.0/i586/Mandrake/RPMS/gcc-3.2-1mdk.i586.rpm
Source
ftp://rpmfind.net/linux/Mandrake/9.0/SRPMS/gcc-3.2-1mdk.src.rpm

Debian

Some more basics:

Another thing a lot of beginners get confused with is the difference between a script and the source for a program. Scripts like pearl, PHP, ASP, and VBScript are interpreted at runtime. A compiled program is interpreted when you actually compile it, and then simply run. This means respective to their complexity compiled programs run faster than scripts.

Most software for Linux and other open source platforms are distributed as source code, usually a compressed archive commonly known as the tarball. This just means the file is in a compressed format, pretty much the same thing as a ZIP file.

Usually before you compile any programs, you should be logged in is a root user. You can do this by logging in as root or by typing su at the command line.

Another common mistake people make is to not have the required libraries. Libraries are shared code, that a program needs to run. For example: most programs that use extensive references to a certain type of protocol, such as SNMP will use a common library written by another programmer. Always check the readme file to see what libraries a program might need.

OK, the start out with a simple program we could write:

Int main(){
Printf(¡§Hello, world¡¨);
}

All this program does, is print hello world, easy enough, let’s save it as test.c. Now to compile it just type:

gcc test.c

Now we should have a working binary program called a.out by default. If you want to give it a different name just type:

gcc test.c –o test1

The will output the file as test1.

Now remember how we talked about libraries, well libraries are included in source by the following:

#include

All includes will be displayed at the top of the source code to be within good programming principles. Now, when we compile our program that contains includes we need to tell GCC where the library is located, so that a permanent link can be made within the program. We do this by the following:

gcc test.c –o test1 –L/usr/lib –ISDL

OK, here’s quick English rundown of what we just did. We told GCC to compile our source test.c and output it as test1 and told it that the library SDL was located in /usr/Lib.

Now I hope this helped you guys out a little bit. The final thing I’m going to cover, is a lot of people see in the install files of a lot of programs that they need to run ./configure. Now when I was just beginning I used to get frustrated, because I would type that at the command line, and I would get file not found. The trouble you’re having is you are not in the correct shell of Linux. To fix this just type:

sh ./configure

I hope it helps out.

Enjoy..

Th Sun Ray was introduced by Sun Microsystems 1999 as a thin client (client side OS). Sun Ray clients are connected via an ethernet network to the Sun Ray Server. Sun Ray Server software is available for Sun’s solaris operating system and also for linux.

Sun’s Sun Ray thin-client platform is unlike any other, offering native Unix connectivity on the Solaris and Linux platforms, as well as providing SmartCard secondary security measures and the ability to move seamlessly between clients while maintaining active sessions. The management tools are rather sparse, however. It’s certainly a different breed, but it works quite well.

The Sun Ray thin-client computing platform is actually a combination of hardware and software. At the hardware end, there are two new clients available. The modest Sun Ray 2 offers 10/100 Ethernet, sound, and USB support. The Sun Ray 2FS is larger but adds 100FX support for greater security at the transport level, as well as the ability to run dual monitors. Both clients are outfitted with SmartCard readers to support two-factor authentication.

On the software end, the clients require the Sun Ray Software package. This includes all the server-side components that deliver a desktop to the client devices. A rather rudimentary Web management UI that can display connected clients, users, and SmartCard information is also included.

Hot Desking is one of the major features the Sun Ray provides, and it works very well. In the middle of a user session, removing the SmartCard from the front of the client will revert the client back to a log-in window. Placing the card into another client will bring up a log-in window, and with a valid password, the user’s entire session appears exactly as it was on the original client. This is similar to session disconnects on Windows Terminal Services or Citrix but with the additional security measure and ease provided by the SmartCard.

To reach the Windows market, Sun has released the Sun Ray Connector for Windows, which essentially runs a full-screen Windows Remote Desktop client on the Sun Ray client. This approach may seem like the long way around to those with a history of Windows-based thin-client implementations, but it does work.

If you are going for secure, manageable Solaris or Windows desktop is the goal, the new Sun Ray solution is worth a look. The bells and whistles are not just fluff when you need to deploy dual-monitor support or have a highly secure fiber network.

Sun Microsystems plans to debut a new line of its Sun Ray thin client terminals and shed more light on its UltraSparc T1 “Niagara” processors and other multithreaded chip plans.

The Sun Ray thin-client computing platform is actually a combination of hardware and software. At the hardware end, there are two new clients available. The modest Sun Ray 2 offers 10/100 Ethernet, sound, and USB support. The Sun Ray 2FS is larger but adds 100FX support for greater security at the transport level, as well as the ability to run dual monitors. Both clients are outfitted with SmartCard readers to support two-factor authentication.

If previous ideas from Sun come true, the new Sun Ray models will be able to connect not just by 10-megabit-per-second Ethernet networking, but also via home broadband and 802.11 wireless networks.

Sun hasn’t had much luck getting the world to scrap PCs in favor of thin clients, which Sun argues are easier to manage and more energy efficient.Sun has promised Sun Rays that come with Internet calling features using voice over Internet Protocol i.e VOIP.

On the Sun workstations, there are two types on environments, the Common Desktop Environment and Open-Windows.

1) Common Desktop Environment (CDE) :

The CDE will log in to a screen with a toolbar at the bottom of the screen. To call up a shell click with the right mouse button, go under ‘programs’, and click on terminal.

2) Open Windows :

Once you have logged onto your account, you will be brought to a screen with an open window up top and others closed on the right hand side. If you want to use the open window, you can make it larger by placing the mouse on the bottom right hand corner and pulling it down.

apropos [keyword] - locate commands in online reference manual by keyword
as -P [filename] - Assembly language compiler
cat [filename] - concatenate and display (similar to ‘type in MS-DOS) files
cc [filename] - SUN C compiler
CC [filename] - SUN C++ compiler
cd [pathname] - change working directory (as in MS-DOS)
chgrp [group] [file]- change the group ownership of a file
chmod [mode] [file] - change permission mode of a file or directory
clear - clears the screen
cp [source] [destination] - copy files (use * as wildcard) from source to destination
date - display the system date
du -k display your disk usage per directory or file
emacs [filename] - GNU’s emacs editor
find [filename] -find files or directories by name or partial matches
finger [username]- display information about a user
ftp send files to/receive files from remote sites
g++ [filename] -GNU’s C++ compiler
gcc [filename] -GNU’s C compiler
grep [string] [file]- searches file for matching string
h -display recently entered commands
kill [process #] -send a terminate signal to process
logout -logout from the system
lpq -display the queue of printer jobs
lpr [filename] -send a job to the printer
lprm [job #] -cancel a print job on the printer queue
ls -list the contents of a directory (similar to dir in MS-DOS)
lynx -text based web browser
man [command name] -access to help on commands
mkdir [dir name] -create a directory (similar to mkdir in MS-DOS)
more [filename] -displays a file one screen length at a time
mv [source] [destination] -move or rename files from source to destination
passwd [username] -change your password
pc [filename] -Pascal compiler
pico -text editor
pine -menu driven mail program
ps -display the status of current processes
quota -v [username] -display allocated disk quota to user
rlogin [machine name] -remote login from one system to another
rm [file] -remove files (similar to delete in MS-DOS)
rmdir -remove directories (similar to rmdir in MS-DOS)
script -make typescript of a file name
talk [username] -talk to another user
telnet -interface to a remote system using telnet protocol
uncompress uncompress compressed file (usually with .Z extension)
unzip uncompress compressed file (usually with .zip extension)
users -display a list of users currently logged in
vi [filename] -visual display editor
w -display information about logged on users
whoami -display effective current user name