dns:~# cat /etc/debian_version
5.0.2

dns:~# uptime
04:52:48 up 165 days, 13:20,  1 user,  load average: 0.07, 0.04, 0.00

dns:~# uname -a
Linux dns 2.6.8-3-686 #1 Tue Dec 5 21:26:38 UTC 2006 i686 GNU/Linux

dns:~# free -m
total       used       free     shared    buffers     cached
Mem:          1139        758        380          0         83        519
-/+ buffers/cache:        155        984
Swap:          360          0        360

dns:~# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 8
model name      : Pentium III (Coppermine)
stepping        : 6
cpu MHz         : 795.213
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips        : 1581.05</code>

dns:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hde1              19G  1.6G   16G  10% /
tmpfs                 570M     0  570M   0% /lib/init/rw
tmpfs                 570M     0  570M   0% /dev/shm

dns:~# pstree
init-+-apache2—10*[apache2]
|-apcupsd—{apcupsd}
|-atd
|-cron
|-events/0-+-aio/0
|          |-kacpid
|          |-kblockd/0
|          |-khelper
|          |-kmirrord/0
|          `-2*[pdflush]
|-6*[getty]
|-inetd
|-khubd
|-kjournald
|-klogd
|-kseriod
|-ksoftirqd/0
|-kswapd0
|-lpd
|-master-+-anvil
|        |-pickup
|        |-proxymap
|        |-qmgr
|        |-2*[smtpd]
|        `-trivial-rewrite
|-miniserv.pl
|-mydns
|-mysqld_safe-+-logger
|             `-mysqld—9*[{mysqld}]
|-pciehpd_event
|-portmap
|-proftpd
|-rpc.statd
|-shpchpd_event
|-sshd—sshd—bash—pstree
`-syslogd

dns:~# top -b -n1 | head -n 5
top – 04:57:06 up 165 days, 13:24,  1 user,  load average: 0.04, 0.04, 0.00
Tasks:  63 total,   1 running,  62 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.6% us,  0.1% sy,  0.0% ni, 98.2% id,  1.0% wa,  0.0% hi,  0.0% si
Mem:   1166624k total,   779448k used,   387176k free,    85804k buffers
Swap:   369452k total,        0k used,   369452k free,   532192k cached
dns:~#

lshw 🙂

description: Tower Computer
product: ProLiant ML330e
vendor: Compaq
serial: 7J15JH81FK0M
width: 32 bits
capabilities: smbios-2.3 dmi-2.3 smp-1.4 smp defhandler_coff defhandler_elf defhandler_lcall7 defha
ndler_libcso fake_utsname trace
configuration: boot=normal chassis=tower cpus=1 uuid=374A3135-4A48-3831-464B-304D20202020

3 komutumuz var unutma

1-pv – physical volume

pvdisplay

2-vg – volume group

vgdisplay

3-lv – logical volume

lvdisplay

—-

/dev/pve/data altina /dev/sdb diskimizi nasil ekliycez:

adimlar

1- fdisk /dev/sdb

varsa partitonlari ucur. p ye bas listele d ye bas sil
n ye bas yeni tek partition olustur.
w ye bas kaydet

2- dosya sistemi olustur

mkfs.ext3 /dev/sdb1

3- pv grubuna ekle

pvcreate /dev/sdb1

vg yi bunu icine alicak sekilde buyult

vgextend pve /dev/sdb1

4- hepsini lv ye dahil et

lvextend -l +100%FREE /dev/pve/data

5- son asama isletim sistemine diskin buyudugunu bildir

resize2fs /dev/pve/data

Oldu da bitti masallah!!!

Easy Update and Package Management for Slackware 13

Introduction

If you haven’t played with Slackware within the past couple of years, you may still believe that the word “easy” doesn’t go well with the words “update” and “package management”.  But, two fairly new utilities, “slackpkg” and “sbopkg”, may help to change your mind.

Initial Setup

When you first install Slackware, you’ll be given the option of installing all packages that are in the official Slackware repository.  This is recommended practice, since it will eliminate any dependency problems you may encounter if you were to just pick and choose packages.  (Besides, there’s not a whole lot in the official repository, so it won’t take up much disk space.)

Before you can update your system, you’ll need to edit the “/etc/slackpkg/mirrors” file, in order to choose a download mirror.  Find the appropriate section for your version of Slackware, and un-comment the appropriate line for the mirror that you wish to use.  (Note that you can only choose one mirror at a time.  Also note that some mirrors work better than others, so you may have to try a couple to get satisfactory results.)

#—————————————————————-
# Slackware current
#—————————————————————-
# Finland,
# ftp://ftp.funet.fi/pub/mirrors/ftp.slackware.com/pub/slackware-current/
# Belgium, 2x1Gbit
# http://ftp.belnet.be/packages/slackware/slackware-current/
# ftp://ftp.belnet.be/packages/slackware/slackware-current/
# Bulgaria, 5Mbit
. . .
. . .
# USA, 155Mbps
ftp://carroll.cac.psu.edu/pub/linux/distributions/slackware/slackware-current/
# Taiwan, 1Gbit
# ftp://ftp.isu.edu.tw/pub/Linux/Slackware/slackware-current/
, , ,
, , ,

In this case, I’ve chosen a mirror for the “current” branch, which is Slackware parlance for the “testing” branch.  If you’re more conservative, or you’re running a mission critical setup where you can’t afford to experiment, you’ll probably want to use a mirror for your specific, stable version of Slackware.

#
#—————————————————————-
# Slackware 13.0
#—————————————————————-
# Finland,
ftp://ftp.funet.fi/pub/mirrors/ftp.slackware.com/pub/slackware-13.0/
# Belgium, 2x1Gbit
# http://ftp.belnet.be/packages/slackware/slackware-13.0/
# ftp://ftp.belnet.be/packages/slackware/slackware-13.0/
# Bulgaria, 5Mbit
# http://mirrors.unixsol.org/slackware/slackware-13.0/
# ftp://mirrors.unixsol.org/slackware/slackware-13.0
. . .
. . .

slackpkg

This is an official Slackware package management utility.  Enter “slackpkg” without any arguments or options, and you’ll get a list of the different available options.  But, if you’ve installed all of the official Slackware packages during initial installation, there will only be three options that you’ll normally need to worry about.

To completely update your Slackware system, enter the following three commands:

# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all

If any new or updated packages are found, you’ll see an ncurses display.  You can either hit the “Enter” key to install or update everything, or use the spacebar to deselect anything that you don’t want to install.

There’s still no automatic dependency resolution, but you’ll rarely run into problems.  The only times I’ve had a problem were when a new package compression scheme was implemented, and when a new “mirrors” file was installed.  In the first case, I just chose to install the new compression utility before trying to update anything else.  In the second case, I just needed to switch over to the new “mirrors” file and edit it appropriately.

When a new version of Slackware gets released, you’ll receive a new copy of the “mirrors” file along with your normal updates.  This new file will reference a mirror for the new version.  Upgrading to the new version is as simple as running the above three commands.  (Really, it’s the simplest version upgrade system that you’ll find anywhere.)

sbopkg

Since there aren’t a whole lot of packages in the official Slackware repository, you’ll most likely want to install a third-party repository.  One of the best is “slackbuilds.org”.

With Slackbuilds, you’ll download the source code for a package, along with an appropriate build script.  Run the script, and you’ll both compile and install the package.  The advantage, is that you can edit the script in order to optimize the compiled executable file for your machine’s processor.  The disadvantage, is that Slackbuilds doesn’t give you a centralized way to keep track of what you have installed, or to update all of your installed packages at once.

The “sbopkg” utility is a third-party utility that eliminates this disadvantage.  Even thought it’s still in beta, I’ve found it to be quite functional.

The first thing you’ll want to do after installing “sbopkg”, is to ensure that you’re plugged into the correct repository for your version of Slackware.

Next, sync your machine with the repository.

Then, either select new packages to install. . .

. . . or, choose to update the packages that you’ve already installed.

Either way, the next step will be to process the queue.

Since sbopkg is still under heavy development, expect to see it updated quite often.  Under the “Utilities” menu, you’ll find the way to get the latest version.  It won’t install it for you, but it will download it so that you can install it with the “pkgtool” utility later.

As with the official Slackware utilities, there’s no dependency resolution.  So, for example, if you choose a package that uses the gtk image libraries, which aren’t installed by default on Slackware, you’ll get an error message when you try to build the package.  You’ll then need to search for and install any packages that are needed to resolve the dependencies.

Conclusion

Slackware is a good, solid, reliable distro.  These new package management utilities make it even better.

Denemedim

ama cok mantikli.

bir gun denemek icin not ediyorum. Asagidaki howto da arkadas ovh deki sunucusna vanilla centos kuruyor.

Guzel ipuclari var. Ileride lazim olabilir.

—-

2. Once the OVH install has finished log into the box via SSH using the login details they will have emailed to you.

3. Issue these commands in SSH:

4. If you are NOT running grub (All OVH bixes use LILO, not grub), you will need to install it:

5. You will now need to edit the grub ‘menu.lst’ file. As you were not already using grub the file will be empty.

In that file paste the following:

* YOURPSW = a password you want to use for VNC access
* YOURIP = The ip address of the server
* GATEWAYIP = The gateway address for your server. This is normally the same as your server IP but replace the last .xxx with .254

Hint: you can also type the following to get the gateway IP:

Once you are finished editing the menu.lst file, press CTRL+X to quit (follow the prompts to save your work!)

6. If you were not previously using grub, do the following:

Note, it seems that all Kimsufi servers use ‘sda’.

7. Reboot your server:

8. As soon as your box is responding to pings, fire up your favourite VNC viewer (i like UltraVNC) and connect to:

YOURIP:1

Use the password you set as YOURPSW

You will now be presented with the CentOS install screen – go ahead and install a base CentOS but make sure you use the standard disk layout.

Web sayfa veya sitemizi yönlendirmek için 301 redirect kodunu kullanıyoruz.

SEO için en iyisi ve güzeli budur.

IIS Redirect

• In internet services manager, right click on the file or folder you wish to redirect
• Select the radio titled “a redirection to a URL”.
• Enter the redirection page
• Check “The exact url entered above” and the “A permanent redirection for this resource”
• Click on ‘Apply’

ColdFusion Redirect

<.cfheader statuscode=”301″ statustext=”Moved permanently”>
<.cfheader name=”Location” value=”http://www.new-url.com”>

PHP Redirect

<?
Header( “HTTP/1.1 301 Moved Permanently” );
Header( “Location: http://www.new-url.com” );
?>

ASP Redirect

<%@ Language=VBScript %>
<%
Response.Status=”301 Moved Permanently”
Response.AddHeader “Location”,”http://www.new-url.com/”
%>

ASP .NET Redirect

<script runat=”server”>
private void Page_Load(object sender, System.EventArgs e)
{
Response.Status = “301 Moved Permanently”;
Response.AddHeader(“Location”,”http://www.new-url.com”);
}
</script>

JSP (Java) Redirect

<%
response.setStatus(301);
response.setHeader( “Location”, “http://www.new-url.com/” );
response.setHeader( “Connection”, “close” );
%>

CGI PERL Redirect

$q = new CGI;
print $q->redirect(“http://www.new-url.com/”);

Ruby on Rails Redirect

def old_action
headers[“Status”] = “301 Moved Permanently”
redirect_to “http://www.new-url.com/”
end

Redirect Old domain to New domain (htaccess redirect)

Create a .htaccess file with the below code, it will ensure that all your directories and pages of your old domain will get correctly redirected to your new domain.
The .htaccess file needs to be placed in the root directory of your old website (i.e the same directory where your index file is placed)

Options +FollowSymLinks
RewriteEngine on
RewriteRule (.*) http://www.newdomain.com/$1 [R=301,L]

Please REPLACE www.newdomain.com in the above code with your actual domain name.

In addition to the redirect I would suggest that you contact every backlinking site to modify their backlink to point to your new website.

Note* This .htaccess method of redirection works ONLY on Linux servers having the Apache Mod-Rewrite moduled enabled.

Redirect to www (htaccess redirect)

Create a .htaccess file with the below code, it will ensure that all requests coming in to domain.com will get redirected to www.domain.com
The .htaccess file needs to be placed in the root directory of your old website (i.e the same directory where your index file is placed)

Options +FollowSymlinks
RewriteEngine on
rewritecond %{http_host} ^domain.com [nc]
rewriterule ^(.*)$ http://www.domain.com/$1 [r=301,nc]

Please REPLACE domain.com and www.newdomain.com with your actual domain name.

Note* This .htaccess method of redirection works ONLY on Linux servers having the Apache Mod-Rewrite moduled enabled.

Z

W

V

U

T