ubuntu user

ພະຍາຍາມສະຫມັກມາດົນແຕ່ຫາກໍ່ໄດ້ເຊັງຢູ່ຫນ້ອຍຫນື່ງ

talk ສຳຫລັບສົນທະນາຜ່ານ terminal

talk
ຄຳສັງທີ່ໃຊ້ລົກັນລະວ່າງຜູ້ໃຊ້ນຳກັນເທິງລະບົບ ເຊິງຜູ້ໃຊ້ທັງສອງຝ່າຍຈະຕ້ອງພິມຄຳສັ່ງ talk ເຖິງກັນກ່ອນຈື່ງຈະເລີ່ມສົນທະນາໄດ້

ຮູບແບບຂອງຄຳສັ່ງ talk user[@host] [tty]

ກໍລະນີບໍ່ລະບຸ host ໂປຣແກຣມຈະຖືວ່າຫມາຍເຖິງເຄື່ອງປະຈຸບັນ(ນອກຈາກນີ້ຢັງມີຄຳສັ່ງ ytalk ເຊິ່ງສາມາດລົມກັນໄດ້ຫລາຍກ່ອນສອງຄົນ)
ເຊິງບາງກໍລະນີອາດຕ້ອງໄດ້ລະບຸ tty ຫາກວ່າມີຜູ້ລ໋ອກອິນເຂົ້າລະບົບດ້ວຍຊື່ດຽວກັນຫລາຍກ່ອນຫນື່ງຈໍ
ຕົວຢ່າງ talk outhai@laozaa

ຖ້າລະບົບຢັງບໍ່ມີກໍ່

apt-get install talk

Conexant chipset modems

Conexant chipset modems section
--------------------------------

Vendors 14f1 is Conexant, inheritor of the former vendor 127a Rockwell modem
technology. There are also Conexant chipsets in some modems from vendors:
158b Allied Data Tech.,
1024 Zenith
141a Apache Micro
148d Digicom Systems.

Linux drivers for Conexant chipset modems are provided ONLY through
http://www.linuxant.com/drivers. The HCF chipset modems have a dsp
(digital signal processing) chip, while the HSF lack a dsp and
this function is performed by the CPU under software direction.
For 2.4.n kernels, installation may require a patch variable: cnxinstall --patch

For a crash issue with the 2.6.16 kernel, please make sure that your
kernel was not compiled with the CONFIG_4KSTACKS option is not set as
the HSF modem driver is known to requires more than 4K of stacks in a
few cases. The are several alternate kernels supporting hsfmodem
available at http://www.linuxant.com. Look for their Link/URL on the
page with your needed hsfmodem package.

To get software, go to http://www.linuxant.com/drivers
-Find the HCF or HSF menu in the left part of the screen.
-Read README.
-Read INSTALLATION.
-Click DOWNLOAD.
-Accept conditions.
-Find text: "You can download HCF (or HSF) modem packages from the driver
download page." and click there.
-Look for your distribution, your processor, and your kernel.
-Download the matching file.
-Read again and, if you do this under Windows, print the installation
instructions matching the kind of driver file which you downloaded.
-Now just follow these instructions.

http://www.linuxant.com/drivers/hsf/downloads-patches.php has patches
that may be necessary for recent kernels.

A detailed software installation example is provided at:
http://linmodems.technion.ac.il/archive-fourth/msg00350.html

After loading of HSF drivers, there will be selective displayed by command:
# /sbin/lsmod | grep hsf
with an output like:
-----------
Module Size Used by Tainted: P
hsfich 119116 0 (autoclean)
hsfserial 26388 0 (autoclean)
hsfengine 1126348 0 (autoclean) [hsfserial]
hsfosspec 35328 0 (autoclean) [hsfich hsfserial hsfengine]
---------
plus many others not modem related.
While drivers are pre-compiled for some Linux distributions,
the installation of the HCF/HSF packages DOES in general require kernel-source/
preparation, as described in Modem/DriverCompiling.txt.

There is good support from Linuxant.com, but first gather data.
In a terminal
# su - root or prefix commands with sudo for Ubuntu related distributions.
hsfconfig --dumpdiag
If this command crashes your machine, please try instead:
hsfconfig --dumpdiag --noprobe
Send the hsfdiag.txt located in the folder /tmp/
to MODEM.SUPPORT@linuxant.com

There is a conflict between modules snd-intel8x0m and hsfmc97ich.
The snd-intel8x0m Must be loaded first or the system may hang upon hsfmc97ich insertion.
http://linmodems.technion.ac.il/archive-fourth/msg03027.html

Rafael Espindola has ported old version
5.03.27 driver code to 2.6.12. This is an Experts ONLY resource with current
information at http://www.ubuntuforums.org/showthread.php?t=180632

From http://www.linuxant.com/drivers,
get package(s) with 2.4.21_47.EL.cern included in the filename.
If such a package cannot be found, get the generic package,
for which compiling drivers will be necessary.

Copy the package to your Linux partition. Unpack with:
unzip *.zip
Under root/admin permission, install with package with
your distributions installation tools.
Should the modem hardware not be a Conexant type,
the installation will ABORT with an informative message.

Continue with any output instructions. Following a successfull installation,
The modem should be detected during the root/admin command:
wvdialconf wvtest
Edit your personal information in with:
$ gedit wvtest
See details on dialout usage in Testing.txt

====== end Conexant section section =======

wvdial

Modem usage is accomplished through drivers, sometimes some helper software,
and the core communication work horse "pppd". Usually it will be found at
/usr/sbin/pppd with permissions shown on my Ubuntu system by:
$ ls -l /usr/sbin/pppd
-rwsr-xr-- 1 root dip 257720 2006-07-05 08:58 /usr/sbin/pppd
The s means "sticky" meaning only one person can use pppd at a time.
As installed, it requires Root/Adm permissions to use pppd, directly or
through front end dialer tools. This is a security precaution common to
all COMM channels. But if you want to enable a simple User to dialout,
as is basically OK for a single user PC, do:
$ su - root
# chmod a+x /usr/sbin/pppd
or for Ubuntu:
$ chmod a+x /usr/sbin/pppd
after which there will be seen:
$ ls -l /usr/sbin/pppd
-rwsr-xr-x 1 root dip 257720 2006-07-05 08:58 /usr/sbin/pppd
with the last x meaning any one can execute pppd, either directly or
much more commonly through a front end dialer such as wvdial of KPPP.

Configuration file for wvdial
-------------------------------
There is a very smart dialer utility "wvdial"
which can be used once basic modem setup is accomplished. A configuration file
is needed, which begins below with [Dialer defaults]. This file can be accessed
any where by:
$ wvdial --config Path_to/configuration_file
Most commonly the configuration file is saved as:
/etc/wvdial.conf
whereat it will serve all Users of the computer. If saved as:
/home/LoginName/.wvdial.rc
it will be found and used before /etc/wvdial.conf. Note that "." beginning
a file name means "do not show it", excess through usage of:
$ ls -a
Many local configuration files are thus "hidden" in your /home/LoginName/ folder

Some Linux installations have dialup tools like Kinternet, GnomePPP, and the
Redhat/Fedora Internet Connection Wizard which are front ends for wvdial and
will write /etc/wvdial.conf files. For this reason, it is advisable to test
your configuration file first, before copying it to /etc/wvdial.conf. Typically
a first test is run with:
$ wvdialconf wvtest
WvModem<*1>: Cannot get information for serial port.
ttySL0<*1>: ATQ0 V1 E1 -- OK
ttySL0<*1>: ATQ0 V1 E1 Z -- OK
ttySL0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttySL0<*1>: Modem Identifier: ATI -- SmartLink Soft Modem
ttySL0<*1>: Speed 4800: AT -- OK
ttySL0<*1>: Speed 9600: AT -- OK
ttySL0<*1>: Speed 19200: AT -- OK
ttySL0<*1>: Speed 38400: AT -- OK
ttySL0<*1>: Speed 57600: AT -- OK
ttySL0<*1>: Speed 115200: AT -- OK
ttySL0<*1>: Speed 230400: AT -- OK
ttySL0<*1>: Speed 460800: AT -- OK
ttySL0<*1>: Max speed is 460800; that should be safe.
ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

Found a modem on /dev/ttySL0.
Modem configuration written to wvtest.
ttySL0: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
------
will be included in a successful run, where in this case /dev/ttySL0
is the responding device port. The generated wvtest file is:
[Dialer Defaults]
Modem = /dev/ttySL0
Baud = 460800
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
; Phone =
; Username =
; Password =

which at a minimim must be edited to a form like:
[Dialer Defaults]
Modem = /dev/ttySL0
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
Phone = 3334445555
Username = Your_Login_Name
Password = Your_Password

Additional if your modem port is of the type /dev/pts/N , with N a number,
then there MUST be added a line:
Carrier Check = no
This requirement currently applies to dialups using the helper utility: slmodemd
together with slamr, slusb or ALSA modem drivers, OR the " " : martian_helper
used with the martian_drv for Lucent/Agere modems with DSP chipsets.

Then a test dialput can be done with:
$ wvdial --config wvtest

There are some Systems for which the wvdialcon test will stall at rfcomm ports.
This is a wvdialconf bug and can be bypassed by just using wvdial with a trial
wvtest, but you need to specify the port appropriate to your modem.

If the configuration file below, lines beginning with # are comments.
Removing a # will activate a line with wvdial instructions appropriate to
special circumstances.


[Dialer defaults]
# Lines begining with # are comments.
# wvdial will look for this file at /etc/wvdial.conf or /home/LoginName/.wvdial.rc

# Redhat/Fedora have an Internet Connection Wizard in the popup menus
# ICW will write a two part /etc/wvdial.conf supporting multiple modem usage.

Modem = /dev/ttySL0
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
# Lack of dialtone acquisition can be due to low line voltage,
# a common problem in Italy.
# Try inserting a "dial without waiting": X3
# Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0
# In case of connection instabilities, specify a lower frequency:
# Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=34
# a MS=90 option is sometimes necessary for Internet Providers with buggy V92 protocols:
# Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
ISDN = 0
Modem Type = Analog Modem
Phone = Dialout_phone_number
# if going through a switch board, a perhaps necessary pause can produced with a comma:
# Phone = 1,Dialout_phone_number
Username = LoginName
# if Internet Provider is MSN.net, use under Linux: MSN/LoginName
Password = YourPassWord

# the following lines is NEEDED only for usage with slmodemd or martian_helper
Carrier check = no
# Kinternet appears to add it automatically.

## If CONNECT is achieved but browsing fails, try activating the following line
# Auto DNS = yes
## To make a logfile wvdial.out
# wvdial 2>&1 | tee wvdial.out
# # For some Internet providers, the following line is necessary
# Stupid Mode = yes
## for other wvdial options, do "man wvdial" or see the documentation in
## /usr/share/doc/wvdial/

# to dial an alternate provide use "wvdial 2nd" which will preferentially read:
[Dialer 2nd]
Phone = 2nd_phone_number
Username = 2nd_LoginName
Password = 2nd_PassWord

## End wvdial config file