VNC Server setup

This article gives you brief idea about setting up vnc server on Linux.I had setup vnc server on fedora core 3. same steps will be…

File System Structure – II

We have already discussed the directory structure in
Linux/Unix. You
are able to find files and directories that you need. But there is more
to the filesystem than just the directory structure.

Linux/Unix is a multiuser operating system. Every aspect
of
the system is
multiuser, even the filesystem. The system stores information like who
owns a file and who can read it. There are other unique parts about the
filesystems, such as links and NFS mounts. This section explains these,
as well as the multiuser aspects of the filesystem.

In Linux/Unix, all files are protected under some access
control mechanism, so
that the owner of a file can deny access of his files to other
users. The first column of the long directory list shows the access
characteristics of a file, in te form of 10 flags, e.g. drwxr-xr-x.

drwxr-xr-x? 18 gaurav
gaurav??? 784 2005-04-14 08:31 .

The meanings of the flags are shown below:

Position 1       file type: d (directory) 
- (ordinary file)
l (symbolic link)

Position 2-4 permissions for the owner: r (read)
w (write)
x (execute)

Position 5-7 permissions for other users in the same group

Position 8-10 permissions for all other users

Note that a hyphen (`-‘) denotes lack of the given permission type.
For example, r-x would mean that read and execute permission are
granted, but not write permission.

In order to remove a file, you must have write
permission for
it.

In order to view the contents of a directory, i.e. see
what
files
are there, you need read permission for that directory. In order
to actually access a file (read from it, write to it, or execute
it) in the directory, you need execute permission for the directory.

Ownership

The filesystem stores ownership information for each
file and
directory on the system. This includes what owner and group own a
particular file. The easiest way to see this information is with the ls command:

$ ls -l /usr/bin/wc

   -rwxr-xr-x   1 root     bin    7368 Jul 30  1999 /usr/bin/wc

We are interested in the third and fourth columns.
These
contain the username and group name that owns this file. We see that
the user “root” and the group “bin” own this file.

We can easily change the file owners with the chown(1) (which means “change owner”) and chgrp(1) (which means “change group”) commands. To
change the file owner to “daemon”, we would use chown:


# chown daemon /usr/bin/wc

To change the group owner to “root”, we would use chgrp:

# chgrp root /usr/bin/wc
   

We can also use chown to specify the user and group owners for
a file:

# chown daemon.root /usr/bin/wc

File ownership is a very important part of using a
Linux
system, even if you are the only user. You sometimes need to fix
ownerships on files and device nodes.

References:

http://slackware.com

http://heather.cs.ucdavis.edu/~matloff/UnixAndC/Unix/FileSyst.html

Read more

Installing 2 gnu/linux Distros

I have to install Windows ME, Fedora Core 3 and SuSe 9.1. How do I proceed

Solution :

Before install take a deep breath on how to arrange spaces for installing three distors I have used as under…

I have a 40 GB Hard Disk and I have made the following partitions…

1) 5 GB FAT 32 (C:)
2) 5 GB FAT 32 (D:)
3) 10 GB EXT3 (For SuSe 9.1)
4) 10 GB EXT3 (For Fedora 3)
5) 512 MB SWAP (Thumbrule for setting up the size of SWAP = 2 * RAM present in your computer)
6) Rest kept free (to be used according to need)

In the above I used the first 5 GB FAT for installing Win ME. The second 5 GB FAT for storage of Win data files. The first 10 GB EXT3 for SuSe 9.1 and second 10 GB EXT3 for Fedora Core 3. The 512 MB swap is for common SWAP place.

Read more

Introduction to Linux/Unix-I

Introduction to Linux/Unix-I

Here we will see what these basic terms of Linux/Unix mean to us

Multiuser

Multi-user operating systems allow multiple users to
utilise the computer and run programs at the same time. All
time-sharing
systems
are multi-user systems, but most batch processing systems for
mainframes were too, to avoid leaving the expensive CPU idle while it
waited for I/O operations to complete.

The most obvious example is a Unix server where multiple
remote users have access (via
Telnet) to the Unix shell prompt at
the same time.

More..


Read more

get help

Getting Help 1. man man (short for “manual”) is a traditional form of online documentation in Unix and Linux operating systems. Specially formatted files, “man…