Golfreeze.packetlove.com: Life style of Golfreeze Canon400D Family kammtan.com Jazz Freebsd Unix Linux System Admin guitar Music

#ถ้าเราจะ check mounting nfs server

#showmount -e

ครับ

###เหอๆ ทำการ recovery root password ใน freebsd 6.2

วันนี้ พอดีมีเครื่องที่ต้องลงใหม่ครับ แต่ว่าจะเปลี่ยนจาก
freebsd 6.2 ไปเป็น debian

ก็เลยลอง recovery ดูซึ่งปกติ ของ freebsd ก็คงเป็นรูปแบบเดิมครับ
ไม่ได้ยากอะไรก็เริ่มแรก boot เข้าเป็น แบบ single mode ใน menu ครับ

แล้วเมื่อมันถามว่า
When prompted Enter full pathname of shell or RETURN for /bin/sh:
เป็นการถามว่าจะใช้ shell /bin/sh หรือเปล่าก็ให้กด Enter ไปครับ

สั่งให้ mount path / ครับ
#mount -t /
#mount -a

แล้วสั่ง เปลี่ยน pass root เลยโดย
#passwd

แค่นี้ก็เรียบร้อยครับ

golfreeze[at]packetlove.com

พอดีวันนี้ ว่าจะลง debian ใหม่ เลยใช้ server linux โหลดมาครับ
#wget ftp.freedebain.com/debian-40r3-i386-CD-1.iso
ลง ตัว write packet ใน linux ผมใช้
#apt-get install cdrecord

เริ่ม write
#cdrecord dev=0,0,0 driveropts=burnfree -dao -overburn -v debian-40r3-i386-CD-1.iso

เสร็จแล้วก็ mount มาดูไฟล์ครับ
#mkdir -p /mnt/cdrom
#mount -t iso9660 /dev/cdrom /mnt/cdrom

เหอๆ เรียบร้อย อิอิ

any problems feel free to contact
golfreeze[at]packetlove.com

## ถ้ามี map port ด้วยก็

#iptables -t nat -A PREROUTING -i eth0 -j DNAT -s globalip -p tcp --dport 80 --to privateip:80

###Freebsd

portsnap fetch

portsnap extract

วันก่อนลง Debian 4.0 เพื่อไปแข่งงาน Airraid ครับ
รายละเอียดที่

http://golfreeze.packetlove.com/guyblog/?p=25#more-25

ขั้นตอนแรกก็ ใส่ sources.list ครับดังนี้

deb http://202.29.6.10/pub/debian/etch main
deb-src http://202.29.6.10/pub/debian/etch main


#deb http://mirror.in.th/debian/etch main
#deb-src http://mirror.in.th/debian/etch main

deb http://202.29.6.10/pub/debian-security/etch/updates main contrib
deb-src http://202.29.6.10/pub/debian-security/etch/updates main contrib

#deb http://ftp.psu.coe.ac.th/debianetch main
#deb-src http://ftp.psu.coe.ac.th/debianetch main

deb http://ftp.thaios.net/debian/etch main
deb-src http://ftp.thaios.net/debian/etch main

----------------------------------------------------------------------------
เริ่มลุยเลย
#apt-get install xorg*
#apt-get install gnome*
#apt-get install xserver-xorg*

เสร็จแล้ว

ถ้าใครได้ใช้ remote-desktop เพื่อจะ remote ต่อไปที่ VNC หรือ remote-desktop ของ window ก็ต้องลง

tsclient ครับ เป็น remote desktop ที่ใช้ใน gnome


#apt-get install tsclient

เลือกใช้ Protocol เป็น RDP สำหรับ remote-desktop ใน window น่ะครับ


และถ้าใครอยากลอง 3ddesktop ที่เป็นหน้าจอ หรูหน่อยก็
#apt-get install 3ddesktop
อิอิ

golfreeze[at]packetlove.com

How to Install Source RPMs

Sometimes the packages you want to install need to be compiled in order to match your kernel
version. This requires you to use source RPM files:

* Download the source RPMs or locate them on your CD collection. They usually have a file
extension ending with (.src.rpm)
* Run the following commands as root:

Compiling and installing source RPMs with Fedora can be done simply with the rpmbuild command

[root@bigboy tmp]# rpmbuild --rebuild filename.src.rpm

Here is an example in which we install the tacacs plus package.

[root@bigboy rpm]# rpmbuild --rebuild tac_plus-4.0.3-2.src.rpm
Installing tac_plus-4.0.3-2.src.rpm
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.61594
+ umask 022
+ cd /usr/src/redhat/BUILD
+ cd /usr/src/redhat/BUILD
+ rm -rf tac_plus-4.0.3
+ /usr/bin/gzip -dc /usr/src/redhat/SOURCES/tac_plus-4.0.3.tgz
+ tar -xvvf -
...
...
...
+ umask 022
+ cd /usr/src/redhat/BUILD
+ rm -rf tac_plus-4.0.3
+ exit 0
[root@bigboy rpm]#

The compiled RPM file can now be found in one of the architecture subdirectories under
/usr/src/redhat/RPMS directory. For example, if you compiled an i386 architecture version of the RPM
it will placed in the i386 subdirectory.

You will then have to install the compiled RPMs found in their respective subdirectories as you
normally would.


RPM Installation Errors

Sometimes the installation of RPM software doesn't go according to plan and you need to take
corrective actions. This section shows you how to recover from some of the most common errors
you'll encounter.


Failed Dependencies

Sometimes RPM installations will fail giving Failed dependencies errors which really mean that a
prerequisite RPM needs to be installed. In the next example we're attempting to install the MySQL
database server application, which fails because the mysql MySQL client RPM, on which it depends,
needs to be installed beforehand:

[root@bigboy tmp]# rpm -Uvh mysql-server-3.23.58-9.i386.rpm
error: Failed dependencies:
libmysqlclient.so.10 is needed by mysql-server-3.23.58-9
mysql = 3.23.58 is needed by mysql-server-3.23.58-9
[root@bigboy tmp]#

Installing the MySQL client also fails because it requires the perl-DBD-MySQL package.

[root@bigboy tmp]# rpm -Uvh mysql-3.23.58-9.i386.rpm
error: Failed dependencies:
perl-DBD-MySQL is needed by mysql-3.23.58-9
[root@bigboy tmp]# rpm -Uvh perl-DBD-MySQL-2.9003-4.i386.rpm
error: Failed dependencies:
libmysqlclient.so.10 is needed by perl-DBD-MySQL-2.9003-4
[root@bigboy tmp]#

Strangely enough, the installation of the perl-DBD-MySQL package fails because it needs the mysql
client package. To get around this problem you can run the rpm command with the --nodeps option to
disable dependency checks. In the next example we install the MySQL client ignoring dependencies,
followed by successful installation of perl-DBD-MySQL and mysql-server.

[root@bigboy tmp]# rpm -Uvh --nodeps mysql-3.23.58-9.i386.rpm
Preparing... ####################### [100%]
1:mysql ####################### [100%]
[root@bigboy tmp]# rpm -Uvh perl-DBD-MySQL-2.9003-4.i386.rpm
Preparing... ####################### [100%]
1:perl-DBD-MySQL ####################### [100%]
[root@bigboy tmp]# rpm -Uvh mysql-server-3.23.58-9.i386.rpm
Preparing... ####################### [100%]
1:mysql-server ####################### [100%]
[root@bigboy tmp]#

Note: If all the installation RPMs are located in the same directory, the rpm command can
automatically install all the prerequisite RPMs using the --aid option. One of the advantages of
using the yum facility is that you don't have to worry about this dependency process as much
because the dependency RPMs are always downloaded and installed automatically also.
Signature Keys

Fedora digitally signs all its RPM files, so it's best to import their public encryption key
beforehand so that the RPM installation program will be able to verify the validity of the RPM
file.

This is usually done automatically in newer versions of Fedora, but will need to be done manually in
legacy versions. The manual method uses the rpm command as seen in the next example, but locate the
key files first as their locations can vary between Fedora distributions. It is a good idea to
import both the RedHat and Fedora keys:


[root@bigboy tmp]# locate RPM-GPG-KEY
/usr/share/rhn/RPM-GPG-KEY
/usr/share/rhn/RPM-GPG-KEY-fedora
[root@bigboy tmp]# rpm --import /usr/share/rhn/RPM-GPG-KEY
[root@bigboy tmp]# rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora
[root@bigboy tmp]#

If you don't install the keys you'll get a DSA signature warning that alerts you to the fact
that the RPM file might be bogus:

[root@bigboy tmp]# rpm -Uvh dhcp-3.0pl2-6.16.i386.rpm
warning: dhcp-3.0pl2-6.16.i386.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2
Preparing... #################################### [100%]
1:dhcp #################################### [100%]
[root@bigboy tmp]#

It is always good to install the key files. If they are not there, the RPMs will install with only a
warning message. If the RPM's digital signature doesn't match that in the key file, the rpm
installation program also alerts you and fails to install the RPM package at all:

[root@bigboy tmp]# rpm -Uvh dhcp-3.0pl2-6.16.i386.rpm
error: dhcp-3.0pl2-6.16.i386.rpm: V3 DSA signature: BAD, key ID 4f2a6fd2
error: dhcp-3.0pl2-6.16.i386.rpm cannot be installed
[root@bigboy tmp]#

Signatures are therefore useful because they help protect you against tampered and otherwise
corrupted RPMs being installed.