07-07-2015
Knowing it runs UNIX doesn't tell us anything useful. You can't login to something which has no network connections and no terminal.
The manual says the USB port is for firmware upgrades. If you're lucky, it may actually be a terminal. Try connecting to that serial port with a program like PUTTY. Again, we have no way of knowing what baud or anything. You'll have to experiment.
This User Gave Thanks to Corona688 For This Post:
9 More Discussions You Might Find Interesting
1. Linux
Hi,
I was wondering if any of you guys know of way to make applications that use sound device on linux to access it in a "non-exclusive manner", the aim is to be able to use more than one application that requires the sound device.
Thanks (0 Replies)
Discussion started by: andryk
0 Replies
2. Linux
Hi,
we have running 8 box sles 9 cluster and on an nfs filesystem we have the problem which is grepped from /var/log/messages.
Jun 8 13:40:46 qnclpx02 kernel: attempt to access beyond end of device
Jun 8 13:40:46 qnclpx02 kernel: sdat: rw=0, want=8894615912, limit=314572800
Is there... (1 Reply)
Discussion started by: ortsvorsteher
1 Replies
3. UNIX for Dummies Questions & Answers
Hello everyone,
I write a program (Linux & Solaris) that will run as non-root user, but the program must have rw access to a device /dev/ipmi (on linux) or /dev/bmc (on solaris).
What is the standard way of granting such access?
Linux:
chmod on /dev/ipmi ?
suid root my program?
Solaris:... (1 Reply)
Discussion started by: Pavel.Bures
1 Replies
4. Homework & Coursework Questions
Problem statement.
In this part of the assignment, delegates will create a pseudo-device and write a device driver for it. The pseudo-device provides a “backdoor” for gaining root access for a particular user. Instead of compiling the device driver into the kernel, delegate will create a module.... (1 Reply)
Discussion started by: nyjilgeorge1
1 Replies
5. OS X (Apple)
hi, i am on a quest to access and even mount if possible a drive on os x. there is no driver for the device, but it lists fine in the system profiler. can i access its location from the terminal? how? here is what i get on the system profiler:
Speed: Up to 480 Mb/sec
Manufacturer: SAMSUNG
... (3 Replies)
Discussion started by: sontarieh
3 Replies
6. UNIX for Advanced & Expert Users
I am trying to load into the kernel a system-call dynamically (without restarting the kernel and compailing it) in an attempt to (once in kernel mode) write to user process's memory.
(I know there is a way to do this with the ptrace interface but it is not an option.)
I know the only way to... (1 Reply)
Discussion started by: hopelessProgram
1 Replies
7. UNIX for Advanced & Expert Users
I backed up my 320GB hard drive to a file with dd:
dd if=/dev/sda of=dev_sda.17-Mar-2012 bs=1048576The main idea was to be able to be able to completely replace my hard drive from this backup if necessary, but I'd also like to be able to restore individual files. I realize I could use this dd... (20 Replies)
Discussion started by: Matt Miller
20 Replies
8. Ubuntu
I cannot access or boot from my C drive. I'm running Zorin 9 and the drive is a Samsung SSD. The disk was encrypted on install, and that has not given me any problems before.
When I start the system it gets to the memory test page, and does not then load the password prompt, which it used to.... (1 Reply)
Discussion started by: David4321
1 Replies
9. UNIX for Dummies Questions & Answers
How to provide a client exclusive access to the NTP device or NTP server.
Example:
1. Configured md5 authentication for a subnet added below restriction line to the subnet as below in ntp.conf file. Also configured the keys and md5 authentication working .
restrict 192.168.1.0 mask... (1 Reply)
Discussion started by: iqtan
1 Replies
RLOGIND(8) System Manager's Manual RLOGIND(8)
NAME
rlogind - remote login server
SYNOPSIS
rlogind [ -aln ]
DESCRIPTION
Rlogind is the server for the rlogin(1) program. The server provides a remote login facility with authentication based on privileged port
numbers from trusted hosts.
Rlogind listens for service requests at the port indicated in the ``login'' service specification; see services(5). When a service request
is received the following protocol is initiated:
1) The server checks the client's source port. If the port is not in the range 512-1023, the server aborts the connection.
2) The server checks the client's source address and requests the corresponding host name (see IR gethostbyaddr (3), hosts(5) and
named(8)). If the hostname cannot be determined, the dot-notation representation of the host address is used. If the hostname is
in the same domain as the server (according to the last two components of the domain name), or if the -a option is given, the
addresses for the hostname are requested, verifying that the name and address correspond. Normal authentication is bypassed if the
address verification fails.
Once the source port and address have been checked, rlogind proceeds with the authentication process described in rshd(8). It then allo-
cates a pseudo terminal (see pty(4)), and manipulates file descriptors so that the slave half of the pseudo terminal becomes the stdin ,
stdout , and stderr for a login process. The login process is an instance of the login(1) program, invoked with the -f option if authenti-
cation has succeeded. If automatic authentication fails, the user is prompted to log in as if on a standard terminal line. The -l option
prevents any authentication based on the user's ``.rhosts'' file, unless the user is logging in as the superuser.
The parent of the login process manipulates the master side of the pseudo terminal, operating as an intermediary between the login process
and the client instance of the rlogin program. In normal operation, the packet protocol described in pty(4) is invoked to provide ^S/^Q
type facilities and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and
terminal type, as found in the environment variable, ``TERM''; see environ(7). The screen or window size of the terminal is requested from
the client, and window size changes from the client are propagated to the pseudo terminal.
Transport-level keepalive messages are enabled unless the -n option is present. The use of keepalive messages allows sessions to be timed
out if the client crashes or becomes unreachable.
DIAGNOSTICS
All initial diagnostic messages are indicated by a leading byte with a value of 1, after which any network connections are closed. If
there are no errors before login is invoked, a null byte is returned as in indication of success.
``Try again.''
A fork by the server failed.
SEE ALSO
login(1), ruserok(3), rshd(8)
BUGS
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but is
useful in an ``open'' environment.
A facility to allow all data exchanges to be encrypted should be present.
A more extensible protocol should be used.
4.2 Berkeley Distribution September 11, 1989 RLOGIND(8)