05-24-2012
The 6.0 install follows the Unixware install instructions, not Openserver. In order to retain the 5.0.7 system calls with the 6.0 install, you may have to select eafs or htfs file systems and not vxfs as it is not supported by 507. There is also an "Openserver compatibilty mode" kernel setting which might need to be turned on for your system calls. If you have Xenix compatible system calls, you may also need to install MP4 for 6.0.0
10 More Discussions You Might Find Interesting
1. SCO
I've installed a CD-RW rom using SCO OSR 5.0.7, but I cannot open the dev to perform backup (6 Replies)
Discussion started by: tsc_hk
6 Replies
2. Programming
I am trying to access DG-100 gps logger on Mac OS X with POSIX API. The device uses a Prolific usb-serial controller, and connect to the usb port on my mac.
After I install the Prolific driver, it shows up as /dev/tty.usbserial and /dev/cu.usbserial. The vendor has published the data format. So... (1 Reply)
Discussion started by: monkeybiz
1 Replies
3. Solaris
Hi,
I attached the CDROM device in sun 2500 system , Now i want to mount this device.
From where i can find the CDROM device.
Thnx.. (2 Replies)
Discussion started by: Aamir Sahil
2 Replies
4. SCO
Looking for specifically naming convention for a tape device for SCO Unix
What full system backup command should I use for SCO UNIX (1 Reply)
Discussion started by: jedimaster
1 Replies
5. Solaris
Hi,
I've seen similar posts on this board about ejecting CDROMs but I've tried the solutions people suggested but still cannot eject the CD. It's stuck in a production box so I can't reboot it...
bash-3.00# eject -f cdrom
/vol/dev/dsk/c0t0d0/sol_10_106_sparc/s0: Device busy
bash-3.00#... (14 Replies)
Discussion started by: jimmy54321
14 Replies
6. SCO
I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd.
I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies
7. SCO
This is my first load of SCO OpenServer v5.0.7 on a HP ProLiant ML350 G6. When it asks me to identify the source media it can't find it no matter how I respond. The SCO compatible page says it used the on board SATA DVD-ROM on Port 2 of the embedded SATA controller with "Legacy IDE emulation (as... (8 Replies)
Discussion started by: farmboy
8 Replies
8. SCO
So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller.
First, I downloaded the megasas driver from SCO and installed it on the old system.
Then I created a new Microlite Edge emergency boot cd with the new driver on it.
I... (2 Replies)
Discussion started by: jgt
2 Replies
9. HP-UX
Hello,
I am following the HPUX 11.31 install/update guide and I am trying to install "Update-UX" from the installation media. I put the CD into the drive, and I am trying to mount the device. The instructions state:Find the DVD-ROM device file name:
ioscan -C disk -f -n -k | more
A typical... (5 Replies)
Discussion started by: bstring
5 Replies
10. 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
LEARN ABOUT MINIX
kernel-install
KERNEL-INSTALL(8) kernel-install KERNEL-INSTALL(8)
NAME
kernel-install - Add and remove kernel and initramfs images to and from /boot
SYNOPSIS
kernel-install COMMAND KERNEL-VERSION [KERNEL-IMAGE]
DESCRIPTION
kernel-install is used to install and remove kernel and initramfs images to and from /boot.
kernel-install will execute the files located in the directory /usr/lib/kernel/install.d/ and the local administration directory
/etc/kernel/install.d/. All files are collectively sorted and executed in lexical order, regardless of the directory in which they live.
However, files with identical filenames replace each other. Files in /etc/kernel/install.d/ take precedence over files with the same name
in /usr/lib/kernel/install.d/. This can be used to override a system-supplied executables with a local file if needed; a symbolic link in
/etc/kernel/install.d/ with the same name as an executable in /usr/lib/kernel/install.d/, pointing to /dev/null, disables the executable
entirely. Executables must have the extension ".install"; other extensions are ignored.
An executable should return 0 on success. It may also return 77 to cause the whole operation to terminate (executables later in lexical
order will be skipped).
COMMANDS
The following commands are understood:
add KERNEL-VERSION KERNEL-IMAGE
kernel-install creates the directory /boot/MACHINE-ID/KERNEL-VERSION/ and calls executables from /usr/lib/kernel/install.d/*.install
and /etc/kernel/install.d/*.install with the arguments
add KERNEL-VERSION
/boot/MACHINE-ID/KERNEL-VERSION/ KERNEL-IMAGE
The kernel-install plugin 50-depmod.install runs depmod for the KERNEL-VERSION.
The kernel-install plugin 90-loaderentry.install copies KERNEL-IMAGE to /boot/MACHINE-ID/KERNEL-VERSION/linux. It also creates a boot
loader entry according to the boot loader specification in /boot/loader/entries/MACHINE-ID-KERNEL-VERSION.conf. The title of the entry
is the PRETTY_NAME parameter specified in /etc/os-release or /usr/lib/os-release (if the former is missing), or "Linux KERNEL-VERSION",
if unset. If the file initrd is found next to the linux file, the initrd will be added to the configuration.
remove KERNEL-VERSION
Calls executables from /usr/lib/kernel/install.d/*.install and /etc/kernel/install.d/*.install with the arguments
remove KERNEL-VERSION /boot/MACHINE-ID/KERNEL-VERSION/
kernel-install removes the entire directory /boot/MACHINE-ID/KERNEL-VERSION/ afterwards.
The kernel-install plugin 90-loaderentry.install removes the file /boot/loader/entries/MACHINE-ID-KERNEL-VERSION.conf.
EXIT STATUS
If every executable returns 0 or 77, 0 is returned, and a non-zero failure code otherwise.
FILES
/usr/lib/kernel/install.d/*.install /etc/kernel/install.d/*.install
Drop-in files which are executed by kernel-install.
/etc/kernel/cmdline /proc/cmdline
The content of the file /etc/kernel/cmdline specifies the kernel command line to use. If that file does not exist, /proc/cmdline is
used.
/etc/machine-id
The content of the file specifies the machine identification MACHINE-ID.
/etc/os-release /usr/lib/os-release
The content of the file specifies the operating system title PRETTY_NAME.
SEE ALSO
machine-id(5), os-release(5), Boot loader specification[1]
NOTES
1. Boot loader specification
https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec
systemd 237 KERNEL-INSTALL(8)