Sponsored Content
Top Forums UNIX for Beginners Questions & Answers SCO OpenServer 5 Will Not Boot Post 303026802 by spock9458 on Monday 3rd of December 2018 01:24:17 PM
Old 12-03-2018
The contents of /etc/conf/cf.d/mscsi changes whenever I go into "mkdev cdrom" to make changes. I have tried to remove the cdrom drive and start fresh twice, and I need to have a couple of things clarified, I think: #1 - is the "mkdev cdrom" the right command to start with? #2 - what is the difference between adding a driver or adding a device? If I start with trying to add the CD Rom device, it says that I first need to install a driver. So I proceed to install a CD Rom driver using my IDE info (which I think is Secondary Master), rebuild kernel, etc. and reboot. Then when I go and try to add the CD Rom device, it tells me there is already a device configured with that IDE info. At no time, however, have I been able to do a successful mounting of the CD using:
Code:
mount /dev/cd0 /mnt

So I know I'm doing something wrong, but I don't know what to do differently.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Help For SCO OpenServer

I've just installed Unix SCO OpenServer System v in an Intel PC and Everithing ok, except just one thing, in the begining of the installation the wizard asked me about the mouse , i have a generic 3 buttons mouse and i took a logitech and did not work i need to change the mouse configuration, ... (2 Replies)
Discussion started by: jimmyvaldes
2 Replies

2. UNIX for Dummies Questions & Answers

sco openserver 5.5

hello! when i try to make my system dual boot with both win98 & sco open server 5.5 it doesn't work at all.neither win98 take start nor sco open server boots.what should i do ? kindly help me thanks (1 Reply)
Discussion started by: buntty
1 Replies

3. UNIX for Advanced & Expert Users

SCO 5.0.2 openserver

I am doing some work for a customer that is running SCO 5.0.2 openserver and they have lost their cd. Is there anyplace I can download it? I have a replacement being shipped but it will not be here for two days and they are down. Any ideals? (3 Replies)
Discussion started by: SCOoT
3 Replies

4. UNIX for Dummies Questions & Answers

boot failure SCO 5.0.6 OpenServer

hello guys. I just installed SCO 5.0.6 OpenServer it went all the way to the end of the installation and the first boot try it gave me this message. not a directory boot not found cannot open stage 1 boot failure: error loading hd (40)/boot (2 Replies)
Discussion started by: josramon
2 Replies

5. SCO

Ethereal for SCO OpenServer 5.0.7???

Which version of Ethereal can I use for SCO OpenServer 5.0.7??? (0 Replies)
Discussion started by: bean2
0 Replies

6. UNIX for Dummies Questions & Answers

SCO Openserver 6.0

Hi there guys. I just got this new SCO version and i'm having some problem printing from shell, This is what i'm typing at the # sign : lp -dHP /etc/hosts and it prints no problem but when i use any other user at the $ sign it gives me this error. /dev/fd/7: /usr/lib/lp/sysv/7: not found. ... (1 Reply)
Discussion started by: josramon
1 Replies

7. UNIX for Dummies Questions & Answers

SCO Openserver 6.0

Hi guys, I just got this new 6.0 version and i'm trying to setup a remote office to telnet to this server running sco 6.0, in previous version all i have to do is add this file under /etc/rc2.d call S99route and put the gate in that file and that was it, for some reason in 6.0 it does not... (1 Reply)
Discussion started by: josramon
1 Replies

8. SCO

sco openserver 5.0.7

Dear members when i installed dual processor patch in openserver 5.0.7 in hp ML370 G4 server it hangs in sco at G_hd_config. i tried MP4, EFS 5.64,5.70A but not solved the problem.. (0 Replies)
Discussion started by: M_farooqui
0 Replies

9. SCO

sco openserver 5.0.0 boot / root disk

Hi, I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone. I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies

10. SCO

I need SCO Openserver 4.2!!!!

I need SCO Openserver 4.2. Please, give me distributive of that version SCO:eek: (0 Replies)
Discussion started by: caine
0 Replies
EJECT(1)							   User Commands							  EJECT(1)

NAME
eject - eject removable media SYNOPSIS
eject -h eject [-vnrsfqp] [<name>] eject [-vn] -d eject [-vn] -a on|off|1|0 [<name>] eject [-vn] -c slot [<name>] eject [-vn] -t [<name>] eject [-vn] -x <speed> [<name>] eject -V DESCRIPTION
Eject allows removable media (typically a CD-ROM, floppy disk, tape, or JAZ or ZIP disk) to be ejected under software control. The command can also control some multi-disc CD-ROM changers, the auto-eject feature supported by some devices, and close the disc tray of some CD-ROM drives. The device corresponding to <name> is ejected. The name can be a device file or mount point, either a full path or with the leading "/dev" or "/mnt" omitted. If no name is specified, the default name "cdrom" is used. There are four different methods of ejecting, depending on whether the device is a CD-ROM, SCSI device, removable floppy, or tape. By default eject tries all four methods in order until it succeeds. If the device is currently mounted, it is unmounted before ejecting. COMMAND-LINE OPTIONS -h This option causes eject to display a brief description of the command options. -v This makes eject run in verbose mode; more information is displayed about what the command is doing. -d If invoked with this option, eject lists the default device name. -a on|1|off|0 This option controls the auto-eject mode, supported by some devices. When enabled, the drive automatically ejects when the device is closed. -c <slot> With this option a CD slot can be selected from an ATAPI/IDE CD-ROM changer. Linux 2.0 or higher is required to use this feature. The CD-ROM drive can not be in use (mounted data CD or playing a music CD) for a change request to work. Please also note that the first slot of the changer is referred to as 0, not 1. -t With this option the drive is given a CD-ROM tray close command. Not all devices support this command. -x <speed> With this option the drive is given a CD-ROM select speed command. The speed argument is a number indicating the desired speed (e.g. 8 for 8X speed), or 0 for maximum data rate. Not all devices support this command and you can only specify speeds that the drive is capable of. Every time the media is changed this option is cleared. This option can be used alone, or with the -t and -c options. -n With this option the selected device is displayed but no action is performed. -r This option specifies that the drive should be ejected using a CDROM eject command. -s This option specifies that the drive should be ejected using SCSI commands. -f This option specifies that the drive should be ejected using a removable floppy disk eject command. -q This option specifies that the drive should be ejected using a tape drive offline command. -p This option allow you to use /proc/mounts instead /etc/mtab. It also passes the -n option to umount(1). -V This option causes eject to display the program version and exit. LONG OPTIONS
All options have corresponding long names, as listed below. The long names can be abbreviated as long as they are unique. -h --help -v --verbose -d --default -a --auto -c --changerslot -t --trayclose -x --cdspeed -n --noop -r --cdrom -s --scsi -f --floppy -q --tape -V --version -p --proc EXAMPLES
Eject the default device: eject Eject a device or mount point named cdrom: eject cdrom Eject using device name: eject /dev/cdrom Eject using mount point: eject /mnt/cdrom/ Eject 4th IDE device: eject hdd Eject first SCSI device: eject sda Eject using SCSI partition name (e.g. a ZIP drive): eject sda4 Select 5th disc on mult-disc changer: eject -v -c5 /dev/cdrom Turn on auto-eject on a SoundBlaster CD-ROM drive: eject -a on /dev/sbpcd EXIT STATUS
Returns 0 if operation was successful, 1 if operation failed or command syntax was not valid. NOTES
Eject only works with devices that support one or more of the four methods of ejecting. This includes most CD-ROM drives (IDE, SCSI, and proprietary), some SCSI tape drives, JAZ drives, ZIP drives (parallel port, SCSI, and IDE versions), and LS120 removable floppies. Users have also reported success with floppy drives on Sun SPARC and Apple Macintosh systems. If eject does not work, it is most likely a limita- tion of the kernel driver for the device and not the eject program itself. The -r, -s, -f, and -q options allow controlling which methods are used to eject. More than one method can be specified. If none of these options are specified, it tries all four (this works fine in most cases). Eject may not always be able to determine if the device is mounted (e.g. if it has several names). If the device name is a symbolic link, eject will follow the link and use the device that it points to. If eject determines that the device can have multiple partitions, it will attempt to unmount all mounted partitions of the device before ejecting. If an unmount fails, the program will not attempt to eject the media. You can eject an audio CD. Some CD-ROM drives will refuse to open the tray if the drive is empty. Some devices do not support the tray close command. If the auto-eject feature is enabled, then the drive will always be ejected after running this command. Not all Linux kernel CD-ROM drivers support the auto-eject mode. There is no way to find out the state of the auto-eject mode. You need appropriate privileges to access the device files. Running as root or setuid root is required to eject some devices (e.g. SCSI devices). The heuristic used to find a device, given a name, is as follows. If the name ends in a trailing slash, it is removed (this is to support filenames generated using shell file name completion). If the name starts with '.' or '/', it tries to open it as a device file or mount point. If that fails, it tries prepending '/dev/', '/mnt/', '/dev/cdroms', '/dev/rdsk/', '/dev/dsk/', and finally './' to the name, until a device file or mount point is found that can be opened. The program checks /etc/mtab for mounted devices. If that fails, it also checks /etc/fstab for mount points of currently unmounted devices. Creating symbolic links such as /dev/cdrom or /dev/zip is recommended so that eject can determine the appropriate devices using easily remembered names. To save typing you can create a shell alias for the eject options that work for your particular setup. AUTHOR
Eject was written by Jeff Tranter (tranter@pobox.com) and is released under the conditions of the GNU General Public License. See the file COPYING and notes in the source code for details. The -x option was added by Nobuyuki Tsuchimura (tutimura@nn.iij4u.or.jp), with thanks to Roland Krivanek (krivanek@fmph.uniba.sk) and his cdrom_speed command. SEE ALSO
mount(2), umount(2), mount(8), umount(8) /usr/src/linux/Documentation/cdrom/ Linux 18 May 2001 EJECT(1)
All times are GMT -4. The time now is 10:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy