Changing Permissions With Numbers

Each permission setting can be represented by a numerical value:

• r = 4
  

• w = 2
  

• x = 1
  

• - = 0

When these values are added together, the total is used to set specific permissions.

For sneakers.txt, here are the numerical permissions settings:

- (rw-) (rw-) (r--) | | | 4+2+0 4+2+0 4+0+0

The total for the user is six, the total for the group is six and the total for others is four. The permissions setting, then, is read as 664.

If you want to change sneakers.txt so those in your group will not have write access, but can still read the file, remove the access by subtracting 2 from that set of numbers.

The numerical values, then, would become six, four, and four — or 644.

So type:

chmod 644 sneakers.txt

-- snapped from Changing permisions with Numbers

Installing RPM packages

Installing RPM packages:
# rpm -ivh filename.rpm : to install a new package, or
# rpm -Uvh filename.rpm : to upgrade an installed package

Configuring KMLDonkey and mlnet

I struggled with this for quite a while, not really knowing what to do.. finally figured it out..

SUSE 10.0 came installed with KMLDonkey.. But for it to work the mlnet core is required so i downloaded the latest version from:
Followed the installation instructions from MLdonkey World
But after running ./mlnet it spewed this

wraith@Sorceress:~/mldonkey-2.7.0> ./mlnet
2005/11/19 20:35:41 Starting MLDonkey 2.7.0 ...
2005/11/19 20:35:41 Language EN, locale UTF-8
2005/11/19 20:35:41 MLDonkey is working in /home/wraith/.mldonkey
2005/11/19 20:35:41 [DNS] Resolving [Sorceress] ...
2005/11/19 20:35:41 [DNS] Resolving [www.mldonkey.net] ...
2005/11/19 20:35:42 Logging in /home/wraith/.mldonkey/mlnet.log

it would shutdown.. I was quite lost till i read the bit that said Logging in /home/wraith/.mldonkey/mlnet.log and checked the log file mentioned and found

2005/11/19 20:35:42 enabling networks: Exception: bind failed: Address already in use at port 4662
This is normally caused by another application currently using this port.
Close that application and restart MLDonkey, exiting...

so now I had to figure out what was blocking or running on port 4462.. Googled it and seems eMule runs on the same port and eMule was running everytime I tried to start the mlnet core.. So i changed the settings in eMule to use a different port and restarted eMule.

Tried the code again and it started fine. I ran KMLDonkey and changed the settings to point to the mlnet file for the core and it connected to the servers fine..

Installing Limewire

The rpm on limewire.com didnt seem to work.. so i followed the instructions at: http://www.susewiki.org/index.php?title=Installing_LimeWire with some changes..

1. i got an error for the gedit line:
sudo: gedit: command not found
I guess gedit is some kinda text editor tool.. so i manually went to the folder and created the file and pasted the text in it..

2. The instructions seem to be for a Gnome system.. i run KDE.. so instead of creating a .desktop file in the gnome directory.. it created it in the kde directory...

Seems to work now... hmmmm.... DOWNLOAD!!!!!!

Perfecting the Samba!!

Once again... reinstalled... put Suse 10.0 and learnt more abt configuring my box..
In my previous post abt samba I was unsure abt how I got Samba to start..

... So I guess the key is to coax the smbd, nmbd & winbindd services to run after making all the required changes.
-from Samba... Lets Dance!!!

Well.. it should have been obvious but being a newbie it didnt strike me...
When installed, Samba isnt initialized by default.. So basically Samba isnt started when the machine boots.. it needs to be manually started..
The way to get it to startup at boot is to go to the Samba Server tool in YaST and choose the 'start-at-boot' option.
To start SWAT change the line in the file 'swat' located in /etc/xinetd.d/ to
disable = no from the default 'yes'.

And thats it.. Initilize Samba and SWAT.. Configure the (/etc/samba/) smb.conf file... Create a user smbpasswd -a username and you're good to go!