08-05-2004
Oh. im in mac OSX
no cua0 files in my /dev directorey.
lots of others though. any idea?
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
mac_prepare_process_label
MAC_PREPARE(3) BSD Library Functions Manual MAC_PREPARE(3)
NAME
mac_prepare, mac_prepare_type, mac_prepare_file_label, mac_prepare_ifnet_label, mac_prepare_process_label -- allocate appropriate storage for
mac_t
SYNOPSIS
#include <sys/mac.h>
int
mac_prepare(mac_t *mac, const char *elements);
int
mac_prepare_type(mac_t *mac, const char *name);
int
mac_prepare_file_label(mac_t *mac);
int
mac_prepare_ifnet_label(mac_t *mac);
int
mac_prepare_process_label(mac_t *mac);
DESCRIPTION
The mac_prepare family of functions allocates the appropriate amount of storage and initializes *mac for use by mac_get(3). When the result-
ing label is passed into the mac_get(3) functions, the kernel will attempt to fill in the label elements specified when the label was pre-
pared. Elements are specified in a nul-terminated string, using commas to delimit fields. Element names may be prefixed with the '?' char-
acter to indicate that a failure by the kernel to retrieve that element should not be considered fatal.
The mac_prepare() function accepts a list of policy names as a parameter, and allocates the storage to fit those label elements accordingly.
The remaining functions in the family make use of system defaults defined in mac.conf(5) instead of an explicit elements argument, deriving
the default from the specified object type.
mac_prepare_type() allocates the storage to fit an object label of the type specified by the name argument. The mac_prepare_file_label(),
mac_prepare_ifnet_label(), and mac_prepare_process_label() functions are equivalent to invocations of mac_prepare_type() with arguments of
"file", "ifnet", and "process" respectively.
RETURN VALUES
Upon successful completion, the value 0 is returned; otherwise the value -1 is returned and the global variable errno is set to indicate the
error.
SEE ALSO
mac(3), mac_free(3), mac_get(3), mac_is_present(3), mac_set(3), mac(4), mac.conf(5), maclabel(7)
STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion of the draft continues on the cross-platform POSIX.1e implementation mailing
list. To join this list, see the FreeBSD POSIX.1e implementation page for more information.
HISTORY
Support for Mandatory Access Control was introduced in FreeBSD 5.0 as part of the TrustedBSD Project. Support for generic object types first
appeared in FreeBSD 5.2.
BSD
August 22, 2003 BSD