|
|
Sponsored Content
Operating Systems
SCO
SCO OpenServer 5.0.5 Problem
Post 302412705 by jgt on Tuesday 13th of April 2010 09:38:01 AM
04-13-2010
|
|
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hello all,
I'm trying to install SCO openserver 5 on a 2.5 Gig hard drive, and I tried fdisk and a low-level format of the drive. When I insert the boot diskette all seems fine, and it asks me to set the cd-rom and it sees it and reads from it. Well, I'm thinking all is well until right after I... (1 Reply)
Discussion started by: immulett
1 Replies
2. UNIX for Dummies Questions & Answers
My company has a Compaq NeoServer running SCO OpenServer Release 5 (vintage late 1998) that we inherited from another small company. This has been a very reliable file server for our small company. We recently installed a new Linux server and would like to convert the NeoServer to other functions... (1 Reply)
Discussion started by: Jeff Boyce
1 Replies
3. UNIX for Dummies Questions & Answers
I am running the beta version of Openserver by SCO and the
Graphical login only gives me the option of logging into the
system v xwindows and I know that this build included KDE 3.3
I have tried the kde kdm command at shell prompt: command not
found. Any ideas anyone? (0 Replies)
Discussion started by: coreykirk
0 Replies
4. UNIX for Dummies Questions & Answers
Hi guys
I installed this new server with 5.0.7 openserver and i'm getting a lot of this process, if a stop and restart the printer spooler they go away but after a few minutes they appear again.This is how it looks like.
root 372 615 0 - - 00:00:00 <defunct>
root ... (0 Replies)
Discussion started by: josramon
0 Replies
5. SCO
Hi everyone,
We r installing sco openserver 5.07 on dell poweredge 2800 but we are facing problem when installing SCSI-raid drivers. Dell provide Perc4 raid card and we dont found raid drivers for this specific raid card. So we r stuck up on primary stage and we also dont know the... (2 Replies)
Discussion started by: mineshkoli
2 Replies
6. SCO
we are installing Openserver 5.0.7, system have SAS controller (Hard Disk Attached) as well as Adaptec ultra 320 controller (Tape Drive Attached).
At the time of installation we link both driver BTLD
Boot: Defbootstr link=accraid ad320
Aftes succesfully installation of accraid btld... (6 Replies)
Discussion started by: hafizurr
6 Replies
7. SCO
I need SCO Openserver 4.2. Please, give me distributive of that version SCO:eek: (0 Replies)
Discussion started by: caine
0 Replies
8. SCO
can not for the life of me workout which BTLD to load allways shows no HDD available can any one give me a clue
tried
hpsas
aacraid
lsil
a160
a320
server is a ML310 G4 ?????:confused::confused: (7 Replies)
Discussion started by: wildginger
7 Replies
9. SCO
Hi
I m trying to install SCo 5.0.5 on my laptop but it fails, I was able to install it on another computer and it did work, but with this IBM LENOVO R61 Laptop, it is giving me the message Memory error loading kernel, I searched the net concerning this issue and found that i have to write this... (1 Reply)
Discussion started by: bashar_smeirat
1 Replies
10. SCO
I am trying to upgrade our SCO Openserver 6 box to some newer HW. I can get everything working correctly except for the console display. The boot command shows up correctly, as does the SCO Openserver 6 splash screen. Right as the SCO legal ease is displaying the screen suddenly jumps to only... (4 Replies)
Discussion started by: Jim546
4 Replies
LEARN ABOUT MINIX
reboot
REBOOT(8) System Manager's Manual REBOOT(8) NAME
reboot - reboot the system immediately SYNOPSIS
reboot [-f] DESCRIPTION
Reboot can be used to reboot the system after installing a new kernel. It does not inform the users, but does log it's actions in /usr/adm/wtmp and /usr/adm/authlog. The system is then rebooted with the reboot(2) systemcall. If the -f flag is not given then all processes are sent terminate signals to give them a chance to die peacefully before the reboot() call. If the wtmp file exists, reboot logs itself as if it were a shutdown. This is done to prevent last(1) from talking about system-crashes. Reboot is registered as is in the authlog file. Reboot can only be executed by the super-user. Any other caller will be refused, either by reboot(8) or by reboot(2). SEE ALSO
reboot(2), shutdown(8), halt(8), boot(8). BUGS
The error message's given by reboot are not always useful. There are several routines that can fail, but which are not fatal for the pro- gram. AUTHOR
Edvard Tuinder (v892231@si.hhs.NL) REBOOT(8)