- PC

- SMS/MMS Engine

- Koneksi ke Telecommunication Provider

- Software Aplikasi

Untuk Engine, bisa dipergunakan yang komersial ataupun bisa yg opensource seperti http://www.kannel.org yang komersial itu kebanyakan di buat untuk dijalankan pada operating system windows/UNIX.

Mengenai software aplikasi itu bermacam-macam model dan jenisnya. Untuk lebih jelasnya mungkin bisa dibantu dengan googling di http://www.google.com dengan keywords SMS application atau MMS application.

Kalau untuk script PHP yang bisa mendukung SMS/MMS bisa di cari di http://www.hotscripts.com (Wiko Budianto)

..nah kalo mau mencobanya yg sederhana di komputer sendiri juga bisa.

Untuk membuat aplikasi SMS dikomputer kita,dibutuhkan peralatan sbb:
1. Sebuah Komputer
2 SMS Gateway (Card Moduler) bisa diganti dengan ponsel sebagai alternatif gateway.
3. Kabel data, untuk menghubungkan komputer dan sms gateway

Sistimkerja SMS
Dibalik tampilan menu messages pada ponsel sebenarnya adalah AT Command yg bertugas mengirim/menerima data ke/dari SMS-center.

AT Command mirip perintah > pada dos. Untuk mengetes AT Command kita bisa menggunakan windows HyperTerminal yang biasanya terdapat pada windows installer. Dengannya kita bisa membuka koneksi melalui port dengan SMS gateway.

AT Command untuk SMS biasanya diikuti oleh data I/O yg diwakili oleh unit-unit PDU.
Data yang mengalir ke/dari SMS-Center harus berbentuk PDU (Protocol Data Unit). PDU berisi bilangan-bilangan heksadesimal yang mencerminkan bahasa I/O. PDU terdiri dari beberapa header.
Misalnya untuk mengirim SMS ada 8 header yang didalamnya terdapat lagi subheader-subheader. Yakni:
1. No SMS-Center
2. Type SMS (misalnya send atau recieve)
3. No Referensi SMS
4. No ponsel penerima
5. Bentuk SMS (sebagai sms atau fax?)
6. Skema encoding data I/O
7. Jangka waktu (expired)
8. Isi SMS

Nah kedelapan header (berikut subheadernya) tersebut kita gabungkan menjadi sebuah PDU yang lengkap.

Untuk memudahkan membaca bahasa PDU kita bisa menggunakan software untuk meng encode dan men decode PDU dari dan menjadi text biasa. Salah satunya adalah PDUSpy.

Untuk meng atomatisasikan proses diatas kita bisa membuat aplikasinya dengan Visual Basic misalnya yang kemudian bisa dikembangkan lagi untuk aplikasi web.

Saat ini sudah ada beberapa buku yang membahas aplikasi SMS ini yang sudah delingkapi dengan contoh-contoh aplikasinya, misalnya karangan Ir Bustam Khang cetakan elexmedia dengan judul “Trik pemograman Aplikasi berbasis SMS” disana terdapat contoh aplikasi menggunakan VB dan ASP ntuk web

Discussion forum

Contents

1) How to send SMS using Aspicore SMS gateway? SQL examples.

2) How to send SMS from a Visual Basic program?

3) How do I install SMS Gateway to use an existing SQL Server 7 database (or MSDE) that is located in another computer?

4) One of the following messages appears in the operating system’s event log

4.1) “Error: ProcessSendQueue: Problem polling database”
4.2) “Error: PollSIM: Problem with phone SIM card polling”
“Error: Framing Error”

5) Error message dialog box “Problem polling database. Check your database connection and make sure that the SMSQLServer service is running.” when selecting “File…Connect GSM Device

6) “+CMS ERROR:28″ or similar when trying to send SMS messages

7) Cannot receive SMS messages.

My evaluation software sends empty SMS messages.

9) Cannot use infrared interface to connect the phone with Aspicore SMS Gateway.

10) Cannot connect to Nokia 5110 or Nokia 6110.

11) Database polling stops with Nokia Data Suite.

12) Example of using database triggers.

13) Error at the command line “AT+CMGF=1″.

14) Aspicore SMS Gateway version history

15) Aspicore SMS Gateway sends the same message over and over again

16) Using Nokia 9210 Communicator

17) Beware of the Slammer Worm

18) SMS Gateway stops receiving SMS messages. 7 Aug 2003

19) Allowed COM port range 17 Mar 2005
Questions and Answers

1) How to send SMS using Aspicore SMS gateway? SQL examples.

To test sending SMS messages with SQL you can try AdeptSQL software (a free 30-day evaluation version is available via Internet) or using MSDE’s own osql-program.

You can find a more detailed document of using AdeptSQL from here in DOC format or from here in PDF format, if you decide to use that.

Some hints of using osql-program here
1. Open command prompt.
2. Type ‘osql -E -e’ and press enter
(parameters indicate that Windows Integrated security is
used to connect to database). If osql does not work in
the root directory, go to e.g. C:\MSSQL7\Binn\
directory first.
3. Type ‘use GSMSGW’ and press enter.
4. Type ‘go’ and press enter (go-command executes
previously given sql-clause).
5. Type “INSERT INTO SEND_QUEUE (TO_PHONE, MESSAGE) VALUES
(‘+358407335153′, ‘Test sending SMS’)” and press enter.
6. Type ‘go’ and press enter. If SMS Gateway is running an
SMS message should be sent to given phone. Phone numbers
have to be in international format.
7. You can exit osql by typing ‘exit’.

There is a PDF manual included in the evaluation version download. In the manual you can see examples how to access the database from e.g. a Visual Basic program or VB Script ASP pages by using ADO.

2) How to send SMS from a Visual Basic program?

Aspicore SMS Gateway uses a logical database called GSMSGW within MSSQL service. You need to insert your text messages into the SEND_QUEUE table in the database GSMSGW. You can do this from your application by executing an SQL “INSERT” statement as you execute any other MSSQL statements or queries. Example (if you have an active connection to the database GSMSGW):
INSERT INTO SEND_QUEUE (USER_ID, TO_PHONE, MESSAGE) VALUES (‘Demo App’, ‘+358401234567′, ‘Sample Message’)

Source code of a small VB 6 sample application is here.

Aspicore SMS Gateway takes care of sending the inserted message to the recipient via the connected GSM phone. No connection to a SMSC is required. You only need a compatible GSM phone, a data cable and a SIM card to the phone. The SIM card must have the SMS service activated, in some cases you need to make one voice call with a new SIM card before the SMS service gets activated.

3) How do I install SMS Gateway to use an existing SQL Server 7 database (or MSDE) that is located in another computer?

3.1) Choose custom setup intead of typical setup in the installation program. Uncheck MSDE component. Otherwise install normally.

3.2) When the setup program has finished, do not start Aspicore SMS Gateway yet. Go to folder C:\Program Files\Aspicore SMSGW\DB_Scripts\ (or the corresponding folder in your machine according to your setup). You should have a SQL script file named GSMSGW.sql in that folder. Run the script in the SQL server computer with osql.exe or with the Query Analyzer of the MS SQL Server.

3.3) Adjust the ConnectString in C:\Program Files\Aspicore SMSGW\Bin\GSMSGW.ini (or in the corresponding folder in your machine according to your setup). You should change the word “(local)” in the SERVER=(local) setting with the network name of the computer where your SQL database is running. E.g. SERVER=COMPANY_SERVER.

3.4) Now you can launch Aspicore SMS Gateway Interactive to finalize your configuration settings as described in the user’s manual.

4) One of the following messages appears in the operating system’s event log:

4.1) “Error: ProcessSendQueue: Problem polling database”
Action: Check that your SQL engine is running. (The service MSSQLServer status is “Started”.)
Check ConnectString in C:\Program Files\Aspicore SMSGW\Bin\GSMSGW.ini. Run the database creation script GSMSGW.sql again, if necessary. (It deletes all old data from the database GSMSGW.)

4.2) “Error: PollSIM: Problem with phone SIM card polling”
or
“Error: Framing Error”
The phone cable has probably been disconnected.

Action: Check that the phone is powered up and the cable is connected.
If the Aspicore SMS Gateway is running as a service: Stop the SMSGW service and start it again e.g. with the SMS Service Manager.
If you are using Aspicore SMS Gateway Interactive: Exit the application and start it again. Ensure that the GSM Device connection has been activated.

5) Error message dialog box “Problem polling database. Check your database connection and make sure that the SMSQLServer service is running.” when selecting “File…Connect GSM Device”

Possible cause: The standard Aspicore GSMSGW.ini file assumes that your security settings in Microsoft SQL Server are as follows: Authentication: “SQL Server and Windows”

If you are using the MSDE that was included in our package, there should not be a problem. However, if you are using an existing Microsoft SQL Server, you should check your security settings. Right click your SQL server in the Enterprise Manager tree view. Choose Properties. Choose tab “Security”.

Action: If your setting is “Windows only”, you need to modify the ConnectString in GSMSGW.ini as follows:
BEFORE CHANGES:
ConnectString=DRIVER=SQL Server; UID=SMS_GW; PWD=SMS_GW; DATABASE=GSMSGW; APP=Global SMS Gateway; SERVER=(local)

AFTER CHANGES:
ConnectString=DRIVER=SQL Server; UID=Administrator; Trusted_Connection=Yes; DATABASE=GSMSGW; APP=Global SMS Gateway; SERVER=(local)

Change the word Administrator above to the Windows user name, which you used for Windows login.

Or simpy delete the UID and PWD fields from the ConnectString as follows:
ConnectString=DRIVER=SQL Server; DATABASE=GSMSGW; APP=Global SMS Gateway; SERVER=(local)

6) “+CMS ERROR:28″ or similar when trying to send SMS messages:

Action: Check your SMS Service Center number in the Aspicore SMS Gateway configuration.

7) Cannot receive SMS messages.

Action: Send one message first with the SIM card you are using for receiving. Sending one message may be necessary to activate the SMS service on your SIM card.

My evaluation software sends empty SMS messages.

Earlier evaluation versions used to add advertisement text starting with *Aspicore to every sent message. Some GSM operators treat messages starting with an asterisk (*) in a special way, which may cause the receiver to get an empty message.
Action: Download newer evaluation version. Version 1.2.27 (28.3.2002) does not any more add an asterisk (*) to the beginning of the sent messages.

9) Cannot use infrared interface to connect the phone with Aspicore SMS Gateway.

For serious use we recommend a GSM phone with serial cable or a GSM modem with serial cable. However, you can evaluate Aspicore SMS Gateway with a GSM phone, which only has an infrared interface. To do this, you need drivers, which make your PC’s infrared port to be seen as a virtual COM port. This is a bit tricky in Windows 2000. There are non-Microsoft Windows 2000 IrCOMM drivers around, which cause our software to hang. If your infrared port is not yet mapped as a virtual COM port, we recommend IrCOMM2k from from Jan Kiszka for Windows 2000 and Windows XP. Alternative try: Microsoft Knowledge Base Q252795.

10) Cannot connect to Nokia 5110 or Nokia 6110.

Have you got Nokia Data Suite 3.0 installed?

Make sure that you are using the correct COM port number in SMS Gateway Settings. You can check, which is the correct COM port number as follows:
Open the Windows Control Panel. Double-click the System applet. Activate the Hardware tab. Press the Device Manager button. Open the Modems node in the tree view. Double-click Nokia GSM Data 3.0. Activate the Modem tab. Now you see the COM port number, which Nokia Data Suite 3.0 is using for its virtual COM port. E.g. “Port: COM3″. You must use the same COM port number in Aspicore SMS Gateway settings. You must not use directly the physical COM port.

Make also sure, that neither the Hyperterminal nor any of the Nokia Data Suite 3.0 programs are running, when you are using the Aspicore SMS Gateway.

11) Database polling stops with Nokia Data Suite.

Normally there is a blinking message “Database: Polling” in the status panel of SMS Gateway Interactive. In the version 1.2.29 this message stops blinking in certain cases with Nokia phones and says instead: “Database: Not polling”. At the same time, a new message appears in the application event log. The end of the event message says: “OnComm: GSM device was unplugged or power was switched off. Please check your GSM device.”

This issue concerns you, if your version of AspicoreSMSGW.exe is 1.2.0.29 and you are using a Nokia phone or especially Nokia Data Suite. The cause of the error is, that version 1.2.29 monitors the COM port handshake signals trying to detect low battery or cable disconnection/reconnection situations. Especially Nokia Data Suite seems to generate short peaks to the DSR handshake signal level causing SMS Gateway to stop database polling.
Action: Download newer evaluation version. Version 1.2.30 (14.5.2002) does not halt database polling based on the handshake signal levels.

12) Example of using database triggers.

Here is an example of using triggers in SQL. This example simply sends an autoreply message to the same GSM number from which it received an SMS containing the keyword ‘TEST’ in the beginning of the message.

Aspicore SMS Gateway stores the incoming message first to RECEIVE_QUEUE and then it copies the same information to the RECEIVE_HISTORY table. The trigger should be created to the RECEIVE_HISTORY table instead of RECEIVE_QUEUE, because otherwise the trigger will interfere the copying process done by Aspicore SMS Gateway.

Here is the script:

USE GSMSGW
GO

CREATE TRIGGER [TEST_TRIGGER] ON [RECEIVE_HISTORY] FOR INSERT AS
IF EXISTS (SELECT * FROM INSERTED WHERE MESSAGE LIKE ‘TEST%’)
BEGIN
INSERT INTO SEND_QUEUE (USER_ID, TO_PHONE, MESSAGE)
SELECT ‘AutoReply’, INSERTED.FROM_PHONE,
‘Thank you for using Aspicore SMS Gateway.’ FROM INSERTED
END
GO

Save this to a file and run it from command prompt with osql-program:

osql -E -e -i C:\temp\CreateTestTrigger.sql

The example is rather simple, but you’ll get the idea of using triggers. You can easily add e.g. some SELECT-clauses instead of the automated autoreply ‘Thank you for…’-message to fetch some data from other database table and then send this data back with sms (you just have to make sure that SMS_GW database user has all the necessary permissions to access these tables).

WARNING: If an error occurs in your trigger code, the database engine does automatically a rollback for the whole enclosing transaction. This means, that the INSERT INTO RECEIVE_HISTORY statement, which Aspicore SMS Gateway internally tries to execute, will be cancelled. Keep you trigger routine as simple and fail-safe as possible! A failure in the trigger code can affect the normal operation of Aspicore SMS Gateway.

13) Error at the command line “AT+CMGF=1″.

Symptoms: When you press the “Test” button on the “GSM Settings” page, the modem replies with an error to the command “AT+CMGF=1″.

Cause: The SMS Gateway uses “Text Mode” message format when it communicates with the GSM modem. You must use a GSM phone or modem supporting “Text mode” (According to the GSM standard 07.05) to be able to successfully execute the “AT+CMGF=1″ command. Some GSM phones support only “PDU mode”.

You can list the modes your phone supports by giving the command “AT+CMGF=?” e.g. with HyperTerminal or with SMS Gateway menu option File / Diagnostics. The GSM modem replies with a list of supported modes. The value 0 represents PDU mode and the value 1 text mode. The list must contain the value 1, if the phone is going to be used with Aspicore SMS Gateway.

14) Aspicore SMS Gateway version history

You can find Aspicore SMS Gateway version history from here.

15) Aspicore SMS Gateway sends the same message over and over again

This is a known problem in version 1.2.33 and earlier, when something causes a primary key violation in the SEND_HISTORY table.

Symptoms: Aspicore SMS Gateway isn’t deleting the messages in the SEND_QUEUE table, and as a result, it sends the same message over and over again until someone manually deletes the message from the database.

Cause: If there for some reason already exists a duplicate record with the same ID in the SEND_HISTORY table, then the procedure within the gateway, which tries to delete the already sent message from the SEND_QUEUE, might fail. (The procedure first tries to add the record into SEND_HISTORY and then delete it from SEND_QUEUE.)

Solution: Delete all the records from the SEND_HISTORY table.

16) Using Nokia 9210 Communicator

You must activate the Fax modem application behind the Extras button of Nokia 9210, before you can use the Communicator with Aspicore SMS Gateway.

We have used 9210 with the following settings in the 9210 Fax modem application:
Connection type: Cable 19200
Status: Active

Note, that status must be ACTIVE! (In the Fax modem main view, press ACTIVATE button.) (There is an inactivity timeout of 20 minutes in the Nokia 9210 Fax modem activation.)

(Further settings in our Nokia Fax modem application:
8 data bits,
Operating system: Windows 2000 > No
Note, that we have Windows 2000 setting as NO in our Nokia 9210, although in fact our PC is running Windows 2000.)

17) Beware of the Slammer Worm

Aspicore SMS Gateway installs MSDE 1.0 into your computer by default. This database engine is vulnerable to the very aggressively spreading W32.Slammer virus, if you have a direct connection to the Internet and do not apply protective measures.

The Slammer virus does not destroy your data, but it blocks your network with a denial of service attack and starts immediately spreading itself to the neighboring unprotected systems. Luckily the virus can be removed relatively easily.

To protect your system against worm attacks, it is highly recommended to use a firewall between your SMS Gateway computer and the Internet. To isolate Slammer attacks, you should block incoming and outgoing UDP port 1434 packets at your firewall.

It is also recommended to install the security patch for Microsoft SQL Server 7.0 as instructed in Microsoft Security Bulletin MS02-061. This patch makes the system immune to the Slammer worm.

How to know, if a MSSQL system has been patched against the Slammer virus? You can resolve, whether your system is up to date by executing the following SQL statement:
SELECT @@VERSION
You can execute this e.g. either with the MS SQL Server Query Analyzer or with the osql.exe utility. The latter is included with MSDE 1.0.

The MSSQL7 engine, which has been fixed with MS02-061 responds with version number 7.00.1077. On the other hand, the SQL Server 2000 with SP3 (including Slammer protection) responds with version number 8.00.760.

More information about Slammer worm can be found at PSS Security Response Team Alert – New Worm: W32.Slammer

You do not need to worry about Slammer even without any extra measures, if

* you are constantly disconnected from the Internet or if
* you are connected to a LAN, which is properly protected by a firewall.

18) SMS Gateway stops receiving SMS messages.

Symptoms:

*

When started, SMS Gateway stores received SMS messages into the RECEIVE_QUEUE table, as it should. After the program has been running for some time, receiving stops working while sending out messages still work.

You can resume the receiving function by giving command “File”/”Disconnect GSM Device”, turning the power off from your GSM device and back on again and then giving command “File”/”Connect GSM Device”
* Occassionally SMS Gateway inserts AT commands into sent messages

Cause:

An SMS message has been received at the same time as another SMS message was being sent. This occassionally caused lost messages or corrupted sent messages with the default settings of version 1.2.33 and earlier.

If the value of the New Message Indication paramater in the GSM Settings tab of the Settings window is 1, then the GSM device rejects received message, if it is received exactly the same time while another message is being sent by the SMS Gateway. Afterwards, the operator’s SMSC starts buffering the subsequent received messages and does not send them to your GSM device until you make the “Disconnect” and “Connect” maneuver described above.

SMS Gateway version 1.2.33 and earlier had a bug, which in some rare cases caused corruption of the message being sent, if another message was received almost the same time.
Action:

Set the value of 2 to the New Message Indication paramater in the GSM Settings tab of the Settings window. (You can also change this value by editing the file GSMSGW.ini with a text editor like Notepad. Edit the row “Mode=1″ to be “Mode=2″.) Check that your GSM device accepts the new value by observing the Receive History window during the “Connect GSM Device” function. The GSM device should answer OK to the AT+CNMI command

Make note of your SMS Gateway registration info from the register menu. Uninstall your current version. Download version 1.2.44 or above from Aspicore web site. Install the new version and enter the same registration data as in the previous version.

19) Allowed COM port range.

If you cannot see your USB cellular modem COM port in the Aspicore SMS Gateway communications settings drop-down list box, check the COM port number from Windows Device Manager / Modems node, double-click your cellular modem name, activate the Modem tab. If the COM port number is greater than 16, try uninstalling your cellular modem driver and reinstalling the driver so that the COM port number becomes between COM 1 and COM 16.

Only COM port numbers between 1 and 16 are supported by Aspicore SMS Gateway.

If none of the above points helped, you can send us the following three files:

* C:\Program Files\Aspicore SMSGW\DB_Scripts\Create_SMSGW_Database.log
* C:\WINNT\SMSGW_SETUP.log
* C:\Program Files\Aspicore SMSGW\Bin\GSMSGW.ini

they may contain some information, which helps us detecting further your problem.

Discussion forum

Contact:
support@aspicore.com

www.aspicore.com

vi mysql.php

TYPE: "pkg_add mysql-server-4.0.20.tgz"

Note the instructions on the screen. You will return to this after you install PHP.

Install PHP4:

TYPE pkg_add php4-core-4.3.10.tgz Enable the PHP4 module:

TYPE /usr/local/sbin/phpxs -s TYPE cp /usr/local/share/doc/php4/php.ini-recommended /var/www/conf/php.ini Install PHP4_MySQL4 connectivity:

TYPE pkg_add php4-mysql-4.3.10.tgz TYPE /usr/local/sbin/phpxs -a mysql Enable MCRYPT:

TYPE pkg_add php4-mcrypt-4.3.10.tgz TYPE /usr/local/sbin/phpxs –a mcrypt Enable MHASH:

TYPE pkg_add php4-mhash-4.3.10 TYPE /usr/loca./sbin/phpxs –a mhash Enable IMAP:

TYPE pkg_add php4-imap-4.3.10.tgz TYPE /usr/local/sbin/phpxs –a imap Enable DOMXML:

TYPE pkg_add php4-domxml-4.3.10.tgz TYPE /usr/local/sbin/phpxs –a domxml Enable PEAR libraries:

TYPE pkg_add php4-pear-4.3.10.tgz Use PHP to manipulate graphics:

TYPE pkg_add php4-gd-4.3.10-no_x11.tgz TYPE /usr/local/sbin/phpxs –a gd Enable CURL:

TYPE pkg_add php4-curl-4.3.10.tgz TYPE /usr/local/sbin/phpxs –a curl Create MYSQL passwords and user:

TYPE /usr/local/bin/mysqld_safe & TYPE /usr/local/bin/mysqladmin -u root password mypassword Access the server with your new password:

TYPE /usr/local/bin/mysql -u root –p Enter your password at the prompt. You should see the mysql prompt. A problem with MySQL is it ships with two anonymous users who have no passwords. Change this within MySQL by entering the following (Note: the ” marks are two single quotation marks in a row):

mysql> TYPE SELECT Host, User FROM mysql.user; mysql> TYPE SET PASSWORD FOR ''@'localhost' = PASSWORD('newpwd'); mysql> TYPE SET PASSWORD FOR ''@'host_name' = PASSWORD('newpwd'); Change ”@’host_name’ to the value that corresponds to the name you gave your system, displayed on your screen under Host where User = root (e.g., lockdown.cyborgspiders.com):

mysql> TYPE exit Now that you are back at the ‘#’ prompt, TYPE ps to verify that mysqld_safe is still running.

Edit APACHE httpd.conf file:

1. vi /var/www/conf/httpd.conf
2. Change the email address for ServerAdmin to you@youraddress.com.
3. Change your ServerName to a valid DNS entry. If you do not have a valid DNS name for your host, enter the IP address associated with your LAN.
4. TYPE ifconfig –a to find the INET address associated with your working Ethernet card.
5. Find the line that says inet 192.168.1.106 or some similar value.
6. AddType application/x-httpd-php .php and delete the comment tag ‘#’.
7. Also, you must add php to the Apache Directory Index: DirectoryIndex index.html index.php (Optionally, add index.phtml, index.php4, and index.php3.).
8. Exit VI and save forced.
9. Press ESC and TYPE “:wq!” ENTER.

Starting and Stopping APACHE as the SuperUser

To start Apache: TYPE apachectl start (c as in current, t as in table, l as in linux) To stop Apache:

TYPE apachectl stop (c as in current, t as in table, l as in linux) Start Apache now. Then navigate to the htdocs directory to test PHP:

TYPE cd /var/www/htdocs TYPE ls You are now viewing the htdocs directory. This is the directory from which Apache serves files to the world:

TYPE lynx 127.0.0.1 This should show you a congratulations screen. Apache is running with the index.html file.

For PHP to work, you must create an index.php file:

TYPE vi index.html Remember, press i for insert mode. Beneath the tag, add . Press ESC:wq index.php. This saves the file as index.php with your changes. Test this out:

TYPE lynx 127.0.0.1/index.php You should see a very detailed display about your new PHP-enabled Apache Web server. Read through it. Notice how the variables in the httpd.conf file and the php.ini file affect the output. Depending on your purposes, you will want to make configuration changes to these files. (Note: the Apache documentation is installed by default. To avoid embarrassment (and death threats) on the mailing lists, RTFM.)

1. ftp ftp://ftp.openbsd.org/pub/OpenBSD/3.6/ports.tar.gz
2. mv ports.tar.gz /usr
3. cd /usr
4. tar -xzf ports.tar.gz

Pop back into your open root console:

TYPE: CTRL-ALT-F1.

Notice that true root keeps track of all uses of su. Press ENTER to get your prompt back, and type “login”. Log in as the user you created. Type “su”, enter the root password, and voila!

Using Ports: Invoking the tcsh Shell

All of the ports work in a similar fashion. Navigate to the port directory you want and type “make && make install” within the port directory that includes the Makefile. For example, to install the tcsh shell:

1. TYPE: “cd /usr/ports/shells/tcsh”.
2. TYPE: “make && make install”.

And that is the basic formula for installing ports. Many ports, like tcsh, have special instructions that appear during or following the install. In this case:

1. TYPE: “vi /etc/shells”.
2. Add the line /bin/tcsh to this file.
3. Save and quit (ESC, :wq).

At the root prompt, type “/usr/local/bin/tcsh” to invoke the tcsh shell. I like this shell for its up-arrow command history function (never type the same thing twice). You can perform subsequent invocations of this shell by typing tcsh at the command prompt. I suggest continuing to use the tcsh shell for the rest of the tutorial.

Packages Collection

The packages collection is the preferred way of installing software onto your OpenBSD system. Packages “automagically” install the required dependencies. As with the Ports system, you must be logged in as the SuperUser (root). You can browse the packages online. (Note: Intel architecture is i386.) Tell pkg_add where to find the packages via FTP. Do not attempt to install packages from an older or a newer release number of OpenBSD. Because this tutorial builds OpenBSD version 3.6, make sure you get the packages from the version 3.6 folder (setenv as seen below): TYPE setenv PKG_PATH ftp://ftp.openbsd.org/pub/OpenBSD/3.6/packages/i386/

z a. ENTER.

The “z” command zeroes the partitions, leaving only C. Author Note: Thanks to Joel Dinel for the partition zeroing hint.

Now you can add the file structure. This consists of /(root), /var, /swap, /usr, and /home. File size is an important consideration:

• The root / must be at least 150m; 500m is recommended.
• /tmp can be as small as 150m. Performance can increase if this is larger.
• /var should be larger for a server because /var/www and /var/mail can fill up quickly (especially if you expect to handle larger mail attachments).
• swap should be twice the size of the RAM you have or twice the size of the RAM you expect to have.
• 512MB of RAM makes a swap space of 1,024MB ideal. One gig of RAM makes two gigs of swap space.
• /usr and /home need to be larger if you are creating a desktop workstation with X Windows.

I am using a 10GB hard drive. You should use values that make sense for your situation. Keep in mind that the values for offset will differ depending on the size of your hard drive. The following instructions create the basic file structure for the operating system:

TYPE: a a. ENTER. offset:[63]. ENTER. size:500m. ENTER. FS type: [4.2BSD]. ENTER. mount point:[none] /. ENTER. TYPE: a b. ENTER. offset:[614880]. ENTER. size: [19386045] 1024m. ENTER. FS type: [swap]. ENTER. TYPE: a d. ENTER. offset: [2712528]. ENTER. size: [17288397] 500m. ENTER. FS type: [4.2BSD]. ENTER. mount point: [none] /tmp. ENTER. TYPE: a e. ENTER. offset: [3327408]. ENTER. size: [16673517] 3g. ENTER. FS type: [4.2BSD]. ENTER. mount point: [none] /var. ENTER. TYPE: a f. ENTER. offset:[5425056]. ENTER. size: [14575869] 2g. ENTER. FS type: [4.2BSD]. ENTER. mount point: [none] /usr. ENTER. TYPE: a g. ENTER. offset: [9619344]. ENTER. size: [10381581] 2g. ENTER. FS type: [4.2BSD]. ENTER. mount point: [none] /home. ENTER. Now that you have created the file structure, write the changes:

TYPE: p. ENTER. This shows the partitions you are about to create. Leave a little extra space for future changes (like RAM upgrades, or log files filling /var) or leave the size of the g partition unspecified and g will use up the rest of your hard disk:

TYPE: q. ENTER. Write new label? Choose y. ENTER. Now, cycle through the options you have created. Hit ENTER until the /home directory appears, then type “done”.

The next step destroys all existing data on these partitions:

Are you sure that you're ready to proceed? TYPE: y. ENTER. You will be prompted for a system hostname. Use any name you like. I used the name ftknox.

The following steps guide you through configuring the network using DHCP:

• Configure the network? Choose yes. ENTER.
• If you are using an Ethernet card that is supported by OpenBSD, then you should be prompted to initialize an interface. Press ENTER.
• Symbolic (host) name for vr0? TYPE: “([ftknox] dlink530TX)”. ENTER. You should see the speed options for your Ethernet card.
• Do you want to change the media options? Choose no. ENTER.
• IPv4 address for vr0? (or ‘none’ or ‘dhcp’) TYPE: dhcp. ENTER.
• Enter your DNS domain name and the address of your DNS nameserver.
• Default IPv4 route? Choose dhcp. ENTER.
• Edit hosts with ed? Choose no. ENTER.
• Do you want to do any manual network configuration? Choose no. ENTER.
• Password for root account? Do not use any word in any language. Numbers and letters and special characters are best in combination.

Now that the network and file structure configuration is done, it is time to access an (F)TP server to install the operating system:

Where are the install sets? (or 'done') TYPE: f ENTER. HTTP/FTP proxy URL? (e.g., 'http://proxy:8080'. or 'none') Choose none. ENTER. Display the list of known FTP servers? Choose yes. ENTER. Find the server that is closest to you (heeding the warnings from the introduction regarding international distribution):

• Server? (IP address, hostname, list#, ‘done’ or ‘?’) TYPE: “ftp.openbsd.org”. ENTER.
• Does the server support passive mode FTP? Choose yes. ENTER.
• Server directory? Choose pub/OpenBSD/3.6/i386. ENTER.
• Login? Choose anonymous. ENTER.

The following sets are available:

• File name? (or ‘done’) [bsd.mp] TYPE all. ENTER.
• File name? (or ‘done’) TYPE: “-game36.tgz”. ENTER.
• File name? (or ‘done’) TYPE: “done”. ENTER.
• Ready to install sets? TYPE: “yes” ENTER.

And away you go. You are now installing the entire OpenBSD operating system over the Internet to your host (server) computer. So depending on your connection speed, this could take minutes or hours. If it works, you will see various messages about getting somefile.tgz, followed by a percentage. Of course, 100 percent is the target.

Then you will be prompted with the following questions:

• Where are the install sets? (or ‘done’) TYPE: done ENTER.
• Start sshd(8) by default? Choose yes. ENTER.
• Do you expect to run the X window System? Choose either yes or no. ENTER. (*/ I personally believe that X Windows has no place on a server, but you may think differently.\*)
• Change the default console to com0? Choose no ENTER.
• Set your time zone. This one’s self-explanatory.

You should now have a congratulations screen and a root prompt. Take your boot floppy out of the a: drive and TYPE halt. Reboot your machine to start using OpenBSD. You will notice that because you started sshd by default that it will have generated a new dsa and rsa host key. This is excellent. OpenSSH runs seamlessly with OpenBSD because the same people make both. For further information, read the OpenSSH FAQ. The afterboot section of the man pages offers a wealth of information that you should read as well:

TYPE: "man afterboot". One of the strengths of OpenBSD is the high quality of its man pages. Make sure you read these before attempting to post a question on any OpenBSD forum. (Browsing Hint: Page Up and Page Down move you through the man pages; ENTER scrolls one line; TYPE “q” to quit.)

Set Up SU

To use SU, you must first create a regular user, which you will regularly log in as:

1. Log in as root.
2. TYPE: “adduser”.
3. Choose your favorite shell. I use the default [sh].
4. Use the default login class.
5. Use the default Home partition: [/home].

Continue using the defaults, unless you have a special situation. I choose not to send a message to myself and to be prompted for passwords by default. One thing I do change is the password encryption method. Blowfish is my algorithm of choice (and is likely the default). Enter username and full name when prompted.

Now continue as root:

1. TYPE: “vi /etc/group”.
2. The top line should read: “wheel:*0:root”.
3. TYPE “i” to enter vi insert mode.
4. Move to the end of the first line using the right arrow.
5. Add a comma and the username of the user you just created. (e.g., wheel:*0:root,user1)
6. Press ESC and TYPE “:wq” to write the file and exit vi.

Test this out:

1. Press CTRL-ALT-F2 to open a new login screen.
2. Log in as the new user you just created.
3. TYPE “su”.
4. Enter your root password.

You should once again have a root prompt ‘#’. Use this prompt to install the ports and package collections. The following section shows you how.

         ]]>
			http://brightside.wordpress.com/2006/01/13/instal-openbsd-to-secure-web-server-part-configure-the-file-structure-and-the-network/feed/
		0
	
		
			brightside
		
	
		
		
		http://brightside.wordpress.com/2006/01/13/install-openbsd-to-secure-web-server-part-introduction/
		http://brightside.wordpress.com/2006/01/13/install-openbsd-to-secure-web-server-part-introduction/#comments
		Fri, 13 Jan 2006 07:05:55 +0000
		brightside
				

		http://brightside.wordpress.com/2006/01/13/install-openbsd-to-secure-web-server-part-introduction/
		Continue reading →]]>
			he OpenBSD team prides itself on producing one of the most—if not the most—secure operating systems in the world. If you are concerned about keeping the sensitive data within your organization protected, consider OpenBSD. As a member of the 4.4BSD-lite family of operating systems, OpenBSD sets itself apart by claiming to be “secure by default”. The basis for this claim is the diligence of the OpenBSD code auditing team and the inclusion of military grade cryptography in the base system (including Kerbos, OpenSSH, and IPSec). OpenSSH runs best with this OpenBSD (as it was developed by the OpenBSD team).You can install OpenBSD in a couple of ways. The easiest method is to order the OpenBSD CD-ROM from the OpenBSD ordering page. The OpenBSD team, headed by Theo de Raadt, relies on the sale of these CD-ROM packages for its financial survival, so it prefers that users choose this method. Installation via CD-ROM is outlined in detail inside the CD case.

The second—and faster—way of installing OpenBSD is over the Internet via FTP or HTTP. Though this install is free, a post-installation courtesy is to order the CD-ROM anyway, make a donation to OpenBSD, and / or buy a limited edition OpenBSD T-shirt or poster.
This tutorial demonstrates a network install of the OpenBSD operating system, along with PHP4 and MySQL. It presents an advanced system administrator build, which assumes basic knowledge of the VI editor.
[Author's Note: Because OpenBSD is a Canadian-made product, export of the security suite and source code is not restricted in any way. However, while U.S. readers can download (import) OpenBSD, exporting or re-exporting cryptographic software from the US is still a serious criminal offence. For those of you living in the US, do not attempt to export the OpenBSD operating system once you've downloaded it. If you are an American citizen located outside the US, do not download OpenBSD from an American site. You have been warned! Of course, downloading OpenBSD from an American site to an American location is fine. Always choose the server nearest you.]
Create OpenBSD Boot Floppy
OpenBSD runs on a number of hardware platforms. The following directions are somewhat specific to “IBM PC” aka “Intel/AMD” architecture machines. To install OpenBSD over the network, your host computer needs either a floppy or a CD-ROM drive and an Ethernet card that OpenBSD can recognize. So check your hardware first. If you use an Intel-based system, your information is under i386.To create a bootable CD-ROM, you need a CD burner and CD creation software. To simplify the multi-step process of creating the floppy boot install disk on Windows, which is somewhat involved, I developed an installer package. I did not alter the boot installer in any way, but if you prefer to receive the software directly from the OpenBSD site, you’ll find it in the tools section of the 3.6 release site. Navigate to your relevant hardware and download the necessary files.
To complete the example install, you need 1-3 floppy disks and a standard 1.44M floppy drive on your Windows computer. For a standard build, you need only the first disk. The second disk is for special RAID and SCUSI situations, and the third is for laptops. This tutorial uses Windows 2000, but floppy disk creation should work seamlessly with Windows NT and XP as well. If you use an older DOS system or Windows 95/98, then you must use the fdimage.exe file included in the downloadable openbsd36_floppy_install.zip file (with documentation).
The following steps will guide you through a Windows 2000, XP, and NT OpenBSD boot floppy creation:

Download the OpenBSD 3.6 floppy images.
Format your floppy disk: My computer –> 3 1/2 floppy A: –> right click –> format.
Place the directory openbsd36_floppy_install on your c:\ drive as C:\openbsd36_floppy_install.
Open a dos prompt and type:

cd C:openbsd36_floppy_creation


Now that openbsd36_floppy_creation is your working directory type:

ntrw floppy36.fs a:



For a standard Intel architecture, you need only the first disk. If the first disk does not take you to the install screen (or you are using a laptop), you may have to make one or two more floppy boot disks. Again, format your second and third floppy disks then type the following, respectively (see Figure 1):

ntrw floppyB36.fs a:
ntrw floppyC36.fs a:




 


Figure 1. OpenBSD Floppy Creation (Win2000)


Put your newly created floppy boot installer in the a: drive of the computer on which you want to install OpenBSD. Make sure your CMOS is set up to boot from floppy first, and then boot from hard drive second.
To complete the install, you need an Ethernet card that OpenBSD supports. The networking setup procedure is quite straightforward. The following instructions explain how to set up DHCP for a DSL connection. At each listed prompt, just follow the instructions:

Would you like to (I)nstall, (U)pgrade, or (S)hell? Choose I. ENTER.
Terminal type? ENTER
Do you wish to select a keyboard-encoding table? Choose no. ENTER.
Proceed with install? Press y. ENTER.
Which one is the root disk? Choose “(or ‘done’)[wd0]“. ENTER.
Do you want to use *all* of wd0 for OpenBSD? Choose no. ENTER.
fdisk: 1>q. ENTER.
Initial label editor (Enter ‘?’ for help at this prompt.)
TYPE: “>?”. ENTER.

The tools you see are part of the OpenBSD label/partition editor. The disk label editor screen might not look pretty, but it is very powerful. The most important commands for a basic install are ‘a’ for add partition, ‘d’ for delete partition, ‘p’ for print label, and ‘q’ for quit. OpenBSD requires a manual file system setup. During this process ‘m’ is for megabytes and ‘g’ is for gigabytes. This tutorial assumes you are installing OpenBSD on a system dedicated to OpenBSD. (For dual boot issues, see the FAQ.)

         ]]>
			http://brightside.wordpress.com/2006/01/13/install-openbsd-to-secure-web-server-part-introduction/feed/
		3
	
		
			brightside
		

		

		
	
		
		
		http://brightside.wordpress.com/2006/01/12/openbsd-36-installation-guide/
		http://brightside.wordpress.com/2006/01/12/openbsd-36-installation-guide/#comments
		Thu, 12 Jan 2006 01:52:03 +0000
		brightside
				

		http://brightside.wordpress.com/2006/01/12/openbsd-36-installation-guide/
		Continue reading →]]>
			setelah booting via cd maka akan tampil pertanyaan :

 rootdev=0×1100 rrootdev=0×2f00 rawdev=0×2f02
erase ^?, werase ^W, kill ^U, intr ^C, status ^T
(I)nstall, (U)pgrade or (S)hell? i
pilihan “I” di gunakan untuk install openBSD ke system kemudian pilihan “U” untuk Upgrade system nya tanpa merubah konfigurasi terdahulu, dan kemudian pilihan “S” untuk masuk kedalam shell nya, biasanya di gunakan untuk maintenance dll.
Setelah itu akan tampil :
  Welcome to the OpenBSD/i386 3.8 install program.

This program will help you install OpenBSD in a simple and rational way. At
any prompt except password prompts you can run a shell command by typing
‘!foo’, or escape to a shell by typing ‘!’. Default answers are shown in []’s
and are selected by pressing RETURN. At any time you can exit this program by
pressing Control-C and then RETURN, but quitting during an install can leave
your system in an inconsistent state.

Specify terminal type: [vt220] Enter kbd(8) mapping? (’?’ for list) [none] Enter
kita coba instal menggunakan standar instalasi untuk pilihan terminal dan keyboard mapping-nya jadi ya tinggal tekan enter aja.
 IS YOUR DATA BACKED UP? As with anything that modifies disk contents, this
program can cause SIGNIFICANT data loss.

It is often helpful to have the installation notes handy. For complex disk
configurations, relevant disk hardware manuals and a calculator are useful.

Proceed with install? [no] y
karena kita sudah menyiapkan segalanya dan kondisi persiapan untuk instalasi sudah siap maka kita tinggal tekan “y” untuk melanjutkan proses instalasi
  Cool!  Let’s get to it…

You will now initialize the disk(s) that OpenBSD will use. To enable all
available security features you should configure the disk(s) to allow the
creation of separate filesystems for /, /tmp, /var, /usr, and /home.

Available disks are: wd0.
Which one is the root disk? (or done) [wd0] Enter
Kemudian kita masuk ke bagian tersulit dari proses instalasi ini, yaitu pembagian partisi harddrive yang akan kita gunakan. harddrive yang kebetulan di kenal adalah wd0 maka kita tinggal tekan enter untuk melanjutkan proses instalasi tersebut
  Do you want to use *all* of wd0 for OpenBSD? [no] yes
berhubung saya akan menggunakan semua partisi untuk di gunakan dengan system openBSD maka saya pilih “yes” dalam pemilihan tersebut.
  > p m
device: /dev/rwd0c
type: ESDI
disk: ESDI/IDE disk
label: ST320011A
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 39102336
free sectors: 36030960
rpm: 3600

16 partitions:
#             size        offset  fstype [fsize bsize  cpg]
a:      17593.2M       1498.7M  unused      0     0
c:      19092.9M          0.0M  unused      0     0
i:       1498.7M          0.0M  MSDOS
> d a
> a a
offset: [3069360] Enter size: [36030960] 150m
Rounding to nearest cylinder: 307440
FS type: [4.2BSD] Enter mount point: [none] /
> a b
offset: [3376800] Enter size: [35723520] 300m
Rounding to nearest cylinder: 614880
FS type: [swap] Enter > a d
offset: [3991680] Enter size: [35108640] 120m
Rounding to nearest cylinder: 245952
FS type: [4.2BSD] Enter mount point: [none] /tmp
> a e
offset: [4237632] Enter size: [34862688] 80m
Rounding to nearest cylinder: 164304
FS type: [4.2BSD] Enter mount point: [none] /var
> a g
offset: [4401936] Enter size: [34698384] 3g
Rounding to nearest cylinder: 6291936
FS type: [4.2BSD] Enter mount point: [none] /usr
> a h
offset: [10693872] Enter size: [28406448] 4g
Rounding to nearest cylinder: 8388576
FS type: [4.2BSD] Enter mount point: [none] /home
> p m
device: /dev/rwd0c
type: ESDI
disk: ESDI/IDE disk
label: ST320011A
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 39102336
free sectors: 22115520
rpm: 3600

16 partitions:
#             size        offset  fstype [fsize bsize  cpg]
a:        150.1M       1498.7M  4.2BSD   2048 16384   16 # /
b:        300.2M       1648.8M    swap
c:      19092.9M          0.0M  unused      0     0
d:        120.1M       1949.1M  4.2BSD   2048 16384   16 # /tmp
e:         80.2M       2069.2M  4.2BSD   2048 16384   16 # /var
g:       2048.0M       2149.4M  4.2BSD   2048 16384   16 # /usr
h:       4096.0M       4197.4M  4.2BSD   2048 16384   16 # /home
i:       1498.7M          0.0M   MSDOS
> q
Write new label?: [y] Enter
lanjut ke dalam penentuan partisi, yang saya pakai standar isntalasi sesuai dengan yang ada di site openBSD
  Mount point for wd0d (size=122976k)? (or ‘none’ or ‘done’) [/tmp] Enter 
  Mount point for wd0e (size=82152k)? (or ‘none’ or ‘done’) [/var] Enter 
  Mount point for wd0g (size=3145968k)? (or ‘none’ or ‘done’) [/usr] Enter 
  Mount point for wd0h (size=4194288k)? (or ‘none’ or ‘done’) [/home] Enter 
  Mount point for wd0d (size=122976k)? (or ‘none’ or ‘done’) [/tmp] done
No more disks to initialize.

OpenBSD filesystems:
wd0a /
wd0d /tmp
wd0e /var
wd0g /usr
wd0h /home

The next step *DESTROYS* all existing data on these partitions!
Are you really sure that you’re ready to proceed? [no] y
/dev/rwd0a:     307440 sectors in 305 cylinders of 16 tracks, 63 sectors 
                     150.1MB in 1 cyl groups (306 c/g, 150.61MB/g, 19328 i/g)
/dev/rwd0d:     245952 sectors in 244 cylinders of 16 tracks, 63 sectors 
                   120.1MB in 1 cyl groups (244 c/g, 120.09MB/g, 15360 i/g)
/dev/rwd0e:     164304 sectors in 163 cylinders of 16 tracks, 63 sectors 
                     80.2MB in 1 cyl groups (164 c/g, 80.72MB/g, 10368 i/g)
/dev/rwd0g:     6291936 sectors in 6242 cylinders of 16 tracks, 63 sectors 
                     3072.2MB in 20 cyl groups (328 c/g, 161.44MB/g, 20608 i/g)
/dev/rwd0h:     8388576 sectors in 8322 cylinders of 16 tracks, 63 sectors 
                    4096.0MB in 26 cyl groups (328 c/g, 161.44MB/g, 20608 i/g)
/dev/wd0a on /mnt type ffs (rw, asynchronous, local, ctime=Thu Oct 20 00:03:14 20
  05)
/dev/wd0h on /mnt/home type ffs (rw, asynchronous, local, nodev, nosuid, ctime=T
  hu Oct 20 00:03:14 2005)
/dev/wd0d on /mnt/tmp type ffs (rw, asynchronous, local, nodev, nosuid, ctime=Th
  u Oct 20 00:03:15 2005)
/dev/wd0g on /mnt/usr type ffs (rw, asynchronous, local, nodev, ctime=Thu Oct 20 
  00:03:15 2005)
/dev/wd0e on /mnt/var type ffs (rw, asynchronous, local, nodev, nosuid, ctime=Th
  u Oct 20 00:03:15 2005)
dan lanjut ke proses format atau menentukan mount point yang akan di gunakan setelah pengalokasian partisi tersebut. Setelah proses tersebut selesai maka akan berlanjut ke penentuan hostname yang akan digunakan oleh komputer tersebut.
  Enter system hostname (short form, e.g. ‘foo’): idonBSD
lalu berlanjut ke seting up network yang akan di gunakan, seperti tampilan di bawah ini :
Configure the network? [yes] Enter 
  Available interfaces are: fxp0. 
  Which one do you wish to initialize? (or ‘done’) [fxp0] Enter 
  Symbolic (host) name for fxp0? [idonBSD] Enter 
  The default media for fxp0 is 
               media: Ethernet autoselect (100baseTX full-duplex) 
  Do you want to change the default media? [no] Enter 
  IP address for fxp0? (or ‘dhcp’) 192.168.0.251 
  Netmask? [255.255.255.0] Enter 
  IPv6 address for fxp0? (or ‘rtsol’ or ‘none’) [none] 
  No more interfaces to initialize. 
  DNS domain name? (e.g. ‘bar.com’) [my.domain] idonBSD.com 
  DNS nameserver? (IP address or ‘none’) [none] 202.134.0.155 
  Use the nameserver now? [yes] Enter 
  Default route? (IP address, ‘dhcp’ or ‘none’) 192.168.0.101 
  add net default: gateway 192.168.0.101 Edit hosts with ed? [no] Enter 
  Do you want to do any manual network configuration? [no] Enter
dan berlanjut ke proses menge-set password root di komputer tersebut.
Password for root account? (will not echo) pAssWOrd 
 Password for root account? (again) pAssWOrd
berlanjut ke pemilihan media instalasi, berhubung kita memiliki CD openBSD maka kita akan melanjutkan proses instalasi tersebut dengan pilihan media instalasinya adalah cdrom
  Let’s install the sets!
Location of sets? (cd disk ftp http or ‘done’) [cd] Enter Available CD-ROMs are: cd0.
  Available CD-ROMs are: cd0.
Which one contains the install media? (or ‘done’) [cd0] Enter 
   Pathname to the sets?  (or ‘done’) [3.8/i386] Enter
dan berlanjut ke pemilihan file-set yang akan di install kedalam system tersebut, di dalam proses ini saya akan install semua file-set yang tersedia.
  The following sets are available. Enter a filename, ‘all’ to select
all the sets, or ‘done’. You may de-select a set by prepending a ‘-’
to its name.

[X] bsd
[X] bsd.rd
[ ] bsd.mp
[X] base38.tgz
[X] etc38.tgz
[X] misc38.tgz
[X] comp38.tgz
[X] man38.tgz
[X] game38.tgz
[ ] xbase38.tgz
[ ] xetc38.tgz
[ ] xshare38.tgz
[ ] xfont38.tgz
[ ] xserv38.tgz

File Name? (or ‘done’) [bsd.mp] all

The following sets are available. Enter a filename, ‘all’ to select
all the sets, or ‘done’. You may de-select a set by prepending a ‘-’
to its name.

[X] bsd
[X] bsd.rd
[X] bsd.mp
[X] base38.tgz
[X] etc38.tgz
[X] misc38.tgz
[X] comp38.tgz
[X] man38.tgz
[X] game38.tgz
[X] xbase38.tgz
[X] xetc38.tgz
[X] xshare38.tgz
[X] xfont38.tgz
[X] xserv38.tgz
dan setelah itu akan tampil proses instalasi seperti di bawah ini.
  File Name? (or ‘done’) [done] Enter 
  Ready to install sets? [yes] Enter 
  Getting bsd … 
  100% |**************************************************|  5157 KB    00:08 
  Getting bsd.rd … 
  100% |**************************************************|  4549 KB    00:02 
  Getting bsd.mp … 
  100% |**************************************************|  5202 KB    00:03 
  Getting base38.tgz … 
  100% |**************************************************| 35928 KB    00:25 
  Getting etc38.tgz … 
  100% |**************************************************|  1123 KB    00:01 
  Getting misc38.tgz … 
  100% |**************************************************|  2222 KB    00:01 
  Getting comp38.tgz … 
  100% |**************************************************| 20522 KB    00:17 
  Getting man38.tgz … 
  100% |**************************************************|  7234 KB    00:05 
  Getting game38.tgz … 
  100% |**************************************************|  2538 KB    00:01 
  Getting xbase38.tgz … 
  100% |**************************************************| 10225 KB    00:07 
  Getting xetc38.tgz … 
  100% |**************************************************| 93384       00:00 
  Getting xshare38.tgz … 
  100% |**************************************************|  1986 KB    00:02 
  Getting xfont38.tgz … 
  100% |**************************************************| 32438 KB    00:23 
  Getting xserv38.tgz … 
  100% |**************************************************| 18172 KB    00:14 
  Location of sets? (cd disk ftp http or ‘done’) [done] Enter
kemudian lanjut ke proses finishing dari instalasi tersebut :
  Start sshd(8) by default? [yes] y
  Start ntpd(8) by default? [no] y
  Do you expect to run the X Window System? [yes] y
  Change the default console to com0? [no] Enter
    Saving configuration files……done.
Generating initial host.random file ……done.
What timezone are you in? (’?’ for list) [Canada/Mountain] ?
Africa/      Chile/       GB-Eire      Israel       NZ-CHAT      Turkey
America/     Cuba         GMT          Jamaica      Navajo       UCT
Antarctica/  EET          GMT+0        Japan        PRC          US/
Arctic/      EST          GMT-0        Kwajalein    PST8PDT      UTC
Asia/        EST5EDT      GMT0         Libya        Pacific/     Universal
Atlantic/    Egypt        Greenwich    MET          Poland       W-SU
Australia/   Eire         HST          MST          Portugal     WET
Brazil/      Etc/         Hongkong     MST7MDT      ROC          Zulu
CET          Europe/      Iceland      Mexico/      ROK          posix/
CST6CDT      Factory      Indian/      Mideast/     Singapore    posixrules
Canada/      GB           Iran         NZ           SystemV/     right/
What timezone are you in? (’?’ for list) [Canada/Mountain] Asia/Jakarta 
  Setting local timezone to ‘Asia/Jakarta’…done.
  Making all device nodes…done.
Installing boot block…
boot: /mnt/boot
proto: /usr/mdec/biosboot
device: /dev/rwd0c
/usr/mdec/biosboot: entry point 0
proto bootblock size 512
/mnt/boot is 3 blocks x 16384 bytes
fs block shift 2; part offset 3069360; inode block 152, offset 4136
using MBR partition 1: type 166 (0xa6) offset 3069360 (0×2ed5b0)
done.

CONGRATULATIONS! Your OpenBSD install has been successfully completed!
To boot the new system, enter halt at the command prompt. Once the
system has halted, reset the machine and boot from the disk.
# halt
syncing disks… done

The operating system has halted.
Please press any key to reboot. 
selesai sudah standar instalasi untuk openBSD.
Taken From : http://tridianto.wordpress.com/2005/11/29/belajar-install-openbsd/

         ]]>
			http://brightside.wordpress.com/2006/01/12/openbsd-36-installation-guide/feed/
		1
	
		
			brightside