10 More Discussions You Might Find Interesting
1. SCO
Hi all,
A client has an SCO OpenServer Server 6.0, that is running on an HP ProLiant Box and they lost the root password.
Its equipped with a Doal-Core Intel Pentium Processor. They don't have any media or emergency disk anymore.
I tried to boot with the CD Rom, then "Tools", then exit to... (7 Replies)
Discussion started by: thm2222
7 Replies
2. SCO
SCO unix 5.0.5 - Suddently network lost & has to be reboot. I try to stop TCP & start TCP. but no connection. Any idea about that.
thanks (8 Replies)
Discussion started by: ajantha
8 Replies
3. SCO
Dear Team ,
how i can configure raid 1 (mirroring) using ide hdd in sco open unix 5
i have two 80gb identical hdd (same make/model)
thanx (0 Replies)
Discussion started by: sudhir69
0 Replies
4. SCO
I am facing a problem to install sco 5.0.6 in Dell Power Edge SC1420 which raid controller is ultra 320 scsi raid controller .
how/from where to download the ultra 320 scsi raid controller driver for sco 5.0.6.
Plz help with any idea
karzon (1 Reply)
Discussion started by: karzon
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I've got a really old system we use for call logging. The OS is SCO 3.2
uname -a output
SCO_SV bts7053 3.2 2 i386
the problem we are having is that its no longer doing its backups. The original problem was the tape drive, which has been replaced twice now. Because the company are... (1 Reply)
Discussion started by: johno12345
1 Replies
6. SCO
I have several printers setup but nothing prints.
I get the following error email
Subject: Status of lp request aclj3-2297
Your request aclj3-2297 destined for aclj3
encountered an error while printing on printer aclj3.
Reason for failure:
cat: cannot open 0: No such file or... (1 Reply)
Discussion started by: Jessie Nand
1 Replies
7. UNIX for Dummies Questions & Answers
Hello there .
I have a unix box 5.0.06 , this is the error (Telnetd: All networks ports in use .
Can anyone tellme how to resolve this problem.
Thanks a lot . (2 Replies)
Discussion started by: josramon
2 Replies
8. SCO
Happy new year guys.
I have a inspiron 5100 laptop "Dell"
When i'm trying to install SCO openserver 5.0.7 i get this error right after it goes thru the hardware bootup stage.
The error is (PANIC: wdsetparam: no device info for ctlr 1 drive 0
is ctlr 0 , drive 0 not... (0 Replies)
Discussion started by: josramon
0 Replies
9. Filesystems, Disks and Memory
Help, if possible.
In SCO Open Server with installation of two-channel RAID controller the following happens: on the channel 0 disk array is seen by an operational system, and on the channel 1 array is not seen (simultaneously). That is the operational system can not simultaneously use more than... (1 Reply)
Discussion started by: pko60
1 Replies
10. UNIX for Dummies Questions & Answers
I get the following when printing from a SCO Unix application
{ Who are you ?}
The user is printing to a printer on a network print sharing device
HP 500x.
I think this printer is shared via the Unix machine. How does
one set up printer sharing on Unix and access permissions
for them?
... (2 Replies)
Discussion started by: JoseHose
2 Replies
U9FS(4) Kernel Interfaces Manual U9FS(4)
NAME
u9fs - serve 9P from Unix
SYNOPSIS
u9fs [ directory ]
DESCRIPTION
U9fs is not a Plan 9 program. Instead it is a program that serves Unix files to Plan 9 machines using the 9P protocol (see intro(5)). It
is to be invoked on a Unix machine by inetd with its standard input, output, and error connected to a network connection, typically TCP on
an Ethernet. It runs as user root and multiplexes access to multiple Plan 9 clients over the single wire. It simulates Unix permissions
itself by assuming Plan 9 uids match Unix login names.
If a directory is specified u9fs first does a Unix chroot system call to that directory.
Plan 9 calls this service 9fs with TCP service number 564 on the Ethernet. Set up this way on a machine called, say, kremvax, u9fs may be
connected to the name space of a Plan 9 process by
9fs kremvax
Due to a bug in some versions of the IP software, some systems will not accept the service name 9fs, thinking it a service number because
of the initial digit. If so, run the service as u9fs or 564 and do the srv and mount by hand:
srv tcp!kremvax!u9fs
mount -c /srv/tcp!kremvax!u9fs /n/kremvax
For more information on this procedure, see srv(4) and bind(1).
U9fs serves the entire file system of the Unix machine. It forbids access to devices because the program is single-threaded and may block
unpredictably. Using the attach specifier device connects to a file system identical to the usual system except it permits device access
(and may block unpredictably):
srv tcp!kremvax!9fs
mount -c /srv/tcp!kremvax!9fs /n/kremvax device
(The 9fs command does not accept an attach specifier.) Even so, device access may produce unpredictable results if the block size of the
device is greater than 8192, the maximum data size of a 9P message.
The source to u9fs is in the Plan 9 directory /sys/src/cmd/unix/u9fs. To install u9fs on a Unix system, copy the source to a directory on
that system. Edit the makefile to set LOG to a proper place for a log file and to set the compile-time configuration correctly. Then com-
pile with an ANSI C compiler and install in /usr/etc/u9fs. Install this line in inetd.conf:
9fs stream tcp nowait root /usr/etc/u9fs u9fs
and this in services:
9fs 564/tcp 9fs # Plan 9 fs
SOURCE
/sys/src/cmd/unix/u9fs
DIAGNOSTICS
Problems are reported to /tmp/u9fs.log. A compile-time flag enables chatty debugging.
SEE ALSO
bind(1), srv(4), ip(3), nfsserver(8)
BUGS
The implementation of devices is unsatisfactory.
U9FS(4)
