01-02-2002
Connectivity B/w Unix & windows
i want to install ScO UNIX 5.1 in a windows 98 system.
i want it as a DUAL BOOT system. can i doit? If yes How.
and also i want to network unix with my clients. is it poosible to network both unix & windows thru a single network card.
if yes how?
also i wanted to know that thru a switch can i connect a network or configure it or also i want to know that if i have to use hub to do that? please write to me in detail about all this.
my mail-id is ::email removed::
Last edited by oombera; 02-20-2004 at 01:00 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
thanks for your help, i didnt realise you could download the operating system from sun.com:D
Ive just had a new hard drive installed 20 GIG for unix and x windows. How can i connect this hard drive for unix and x windows only? and are there any helpful tutorials for starters??
Many thanks (4 Replies)
Discussion started by: jeffersno1
4 Replies
2. IP Networking
Hello,
Can someone please tell me if it is possible to install a Unix Os on a system that already has a Windows XP? If so, how do i go about it doing it?: (6 Replies)
Discussion started by: Ike
6 Replies
3. UNIX for Dummies Questions & Answers
I used the following commands to store the discription of "sed" into a unix file:
man sed > sed.txt
But, after I download the file "sed.txt" to a Windows XP system, the file can not be displayed correctly. How to change the format of a Unix file to a Windows one? (5 Replies)
Discussion started by: endeavour1985
5 Replies
4. UNIX for Dummies Questions & Answers
I have very basic question:
I have 2 windows sytem & 1 Unix system & wanted to put all three system into one network to each other.
what kind of other hardware I need? like cable , router?
can anybody tell me the configuration? like how to connect to external hardware to put into network?
... (9 Replies)
Discussion started by: kar1
9 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I am a new member here. I am in my final year of engineering in Computer & Information Systems. Wanted to know, how file management is done in both windows and unix. Kindly, tell me anyone who knows it in detail, or has any links regarding it.
Thanks (1 Reply)
Discussion started by: farazcis
1 Replies
6. IP Networking
I have a client who is operating a SCO UNIX 4.3 server with Informix 4.12. My problem is that I need to get hold of the data using a Windows PC.
Where the hell do I start? :confused:
Thanks
Richard.
rgray@euriskotechnology.com (3 Replies)
Discussion started by: euriskotech
3 Replies
7. Shell Programming and Scripting
Hi
Even though this is unix forum, iam posting this thread as iam not sure of which forum should i post this too.
I understand perl can be used in unix environment and i have used the same for automation of my processes.
Eg:
Open a file
search the text string
replace the text string
close... (9 Replies)
Discussion started by: kenkanya
9 Replies
8. AIX
Guys,
sftp between Unix & Windows
I'd like to get good software or a way to how to configure sftp between ( windows to Unix ) and ( Unix to windows ) to be automatic login between the different operating systems without asking password ..
Pls assist in this regard … (3 Replies)
Discussion started by: Mr.AIX
3 Replies
9. Solaris
Pl. let me know whether Sun Solaris Server (Unix OS) is compatible with Windows Server or Vise Versa. Can i update the data first in Windows Server and then copied it to Sun Solaris Server or Vise Versa. (1 Reply)
Discussion started by: seemaitri
1 Replies
10. Windows & DOS: Issues & Discussions
Hi
Can we pass the parameter from the excel in windows and invoke the unix shell script from excel VBA by passing this parameter and get the results of shell script to the excel sheet?
We tried to get the things in unix independently but we still strucked in connecting the excel to... (5 Replies)
Discussion started by: bikky6
5 Replies
LEARN ABOUT NETBSD
rump_sp
RUMP_SP(7) BSD Miscellaneous Information Manual RUMP_SP(7)
NAME
rump_sp -- rump remote system call support
DESCRIPTION
The rump_sp facility allows clients to attach to a rump kernel server over a socket and perform system calls. While making a local rump sys-
tem call is faster than calling the host kernel, a remote system call over a socket is slower. This facility is therefore meant mostly for
operations which are not performance critical, such as configuration of a rump kernel server.
Clients
The NetBSD base system comes with multiple preinstalled clients which can be used to configure a rump kernel and request diagnostic informa-
tion. These clients run as hybrids partially in the host system and partially against the rump kernel. For example, network-related clients
will typically avoid making any file system related system calls against the rump kernel, since it is not guaranteed that a rump network
server has file system support. Another example is DNS: since a rump server very rarely has a DNS service configured, host networking is
used to do DNS lookups.
Some examples of clients include rump.ifconfig which configures interfaces, rump.sysctl which is used to access the sysctl(7) namespace and
rump.traceroute which is used to display a network trace starting from the rump kernel.
Also, almost any unmodified dynamically linked application (for example telnet(1) or ls(1)) can be used as a rump kernel client with the help
of system call hijacking. See rumphijack(3) for more information.
Connecting to the server
A remote rump server is specified using an URL. Currently two types of URLs are supported: TCP and local domain sockets. The TCP URL is of
the format tcp://ip.address:port/ and the local domain URL is unix://path. The latter can accept relative or absolute paths. Note that
absolute paths require three leading slashes.
To preserve the standard usage of the rump clients' counterparts the environment variable RUMP_SERVER is used to specify the server URL. To
keep track of which rump kernel the current shell is using, modifying the shell prompt is recommended -- this is analoguous to the visual
clue you have when you login from one machine to another.
Client credentials and access control
The current scheme gives all connecting clients root credentials. It is recommended to take precautions which prevent unauthorized access.
For a unix domain socket it is enough to prevent access to the socket using file system permissions. For TCP/IP sockets the only available
means is to prevent network access to the socket with the use of firewalls. More fine-grained access control based on cryptographic creden-
tials may be implemented at a future date.
EXAMPLES
Get a list of file systems supported by a rump kernel server (in case that particular server does not support file systems, an error will be
returned):
$ env RUMP_SERVER=unix://sock rump.sysctl vfs.generic.fstypes
SEE ALSO
rump_server(1), rump(3), rumpclient(3), rumphijack(3)
HISTORY
rump_sp first appeared in NetBSD 6.0.
BSD
February 7, 2011 BSD