08-05-2004
Do an ls /dev/cua*, I think it will be called cuaa or something on BSD.
10 More Discussions You Might Find Interesting
1. Linux
Hey!
I'm trying to figure out a sollution for a problem I have at my company with an Iomega MiniMax 500 GB USB disk.
If i run cat /proc/bus/usb/devices
I get this information:
T: Bus=01 Lev=02 Prnt=04 Port=00 Cnt=01 Dev#= 5 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00... (2 Replies)
Discussion started by: noratx
2 Replies
2. Ubuntu
Hello!
I am working on an application which reads environmental instruments which have serial ports. The application requires a serial port to be present to talk to the device (i.e. /dev/ttyS0 ). In some instances the environmental devices will be 100's of yards away from the computer, so a... (5 Replies)
Discussion started by: mvona
5 Replies
3. Shell Programming and Scripting
Hi,
I have a external board connected to my serial port. I need to execute "shutdown -r now" command when system boot up. When system boots up it requires a username ans password. Then I need to run my command. I can use rc script but that is rebooting system before it asks for username and... (0 Replies)
Discussion started by: charlie.arya
0 Replies
4. Solaris
Hi Everyone,
In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies
5. Solaris
Any help much appreciated. I am a Java developer, not a Solaris adept. I'm having an issue reopening serial port with the Java app I am developing.
I develop in Windows and deploy the app on Solaris 10 (Sunfire X4170 with Xeon.) On the target machine my app uses the two serial ports... (11 Replies)
Discussion started by: Jim Ryan
11 Replies
6. SCO
I am trying to change one of my serial printers from /dev/ttyr002 to /dev/ttyr014:
lpstat -s
device for check3: /dev/ttyr002
device for check4: /dev/ttyr002
I changed the tty setting for check3 in:
/etc/printcap
/var/spool/lp/admins/lp/printers/check3
to /dev/ttyr014
Then I get:... (4 Replies)
Discussion started by: herot
4 Replies
7. Red Hat
Hi,
I have a server program that reads data coming in on USB ports. Device paths are in the format: /dev/ttyUSB0
Now, I would like to log data from another device coming in over Ethernet. My first step is trying to track down what the correct device path is which I am unsure of.
Anyone... (9 Replies)
Discussion started by: fedora18
9 Replies
8. Solaris
Hello,
I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build.
The first part is what confuses me -the cabling.
I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 Replies
9. Shell Programming and Scripting
I'm new to Linux (Ubuntu 16.04), and very new to BASH scripting. I have a Numato 8-channel USB GPIO device, which is a DAQ that appears in the system as a serial port. In Linux it appears as ttyACM0. I can easily manipulate a GPO with, for example:
echo "gpio set 7" > /dev/ttyACM0
...followed... (12 Replies)
Discussion started by: Chalk-X
12 Replies
10. UNIX for Advanced & Expert Users
Currently I am using this laborious command
lvdisplay | awk '/LV Path/ {p=$3} /LV Name/ {n=$3} /VG Name/ {v=$3} /Block device/ {d=$3; sub(".*:", "/dev/dm-", d); printf "%s\t%s\t%s\n", p, "/dev/mapper/"v"-"n, d}'
Would like to know if there is any shorter method to get this mapping of... (2 Replies)
Discussion started by: royalibrahim
2 Replies
LEARN ABOUT FREEBSD
uhsoctl
UHSOCTL(1) BSD General Commands Manual UHSOCTL(1)
NAME
uhsoctl -- connection utility for Option based devices
SYNOPSIS
uhsoctl [-a apn] [-c cid] [-p pin] [-u username] [-k password] [-r path] [-f path] [-b | -n] interface
uhsoctl -d interface
uhsoctl -h
DESCRIPTION
uhsoctl is a small connection utility for Option N.V. devices that are based on Options packet interface and uses proprietary AT_* calls to
establish connections. The utility (tries to) configure both default route and name servers (/etc/resolv.conf).
By default uhsoctl detaches from the terminal upon on a successful connection, a few command-line options exists that allows this behavior to
be changed.
uhsoctl attempts to find a usable controlling serial port based on the provided network interface. If this fails you might specify a serial
port manually.
OPTIONS
-a apn
Specify APN to connect to.
-c cid
Specify CID (Context ID) to use, by default CID 1 is used. If an APN has been configured once, it's enough to specify the CID used for
further accesses.
-p pin
Specify SIM PIN.
-u username
Specify username.
-k password
Specify username.
-r path
Path to resolv.conf, default /etc/resolv.conf. Use /dev/null to disable updating of name servers.
-f path
Explicitly set the serial port to use as controlling terminal. Might be needed if the automatic detection fails.
-b Fork into background directly, before a connection has been established.
-n Never fork into background, run entirely in foreground.
EXAMPLES
Connect to ``apn.example.com'' on interface ``uhso0'' and use PIN ``1234'' to enable the SIM card.
uhsoctl -a apn.example.com -p 1234 uhso0
Disconnect from a previously established connection.
uhsoctl -d uhso0
SEE ALSO
uhso(4)
BSD
Aug 12, 2009 BSD