Sponsored Content
Operating Systems SCO Need emergency boot CD UNIXware 7.1.1 (or 7.1..4) Post 302948238 by bakunin on Saturday 27th of June 2015 09:27:23 AM
Old 06-27-2015
Quote:
Originally Posted by BernP
Hence I ask whether anyone has access to an Emergency Boot CD iso?
Two things:

First, we do not distribute software - at least, we do not distribute software in any other way than to write some source code in articles (which you are free to copy and use yourself). This is just not the scope of our board and i ask you to respect that.

Second: we try to help everybody as best as we can. This will not guarantee help from us (sometimes we simply can't) but as long as we are able to we will. Therefore opening more than one thread on the same topic will just waste everybodies time because we will read the same topic again - and still not be able to do anything about it, the same as the first time.

I will close this thread now and try to answer your other one.

bakunin
This User Gave Thanks to bakunin For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

emergency help ! about unixware backup

MY question is : First I create emergency_disk successful ,and then I create emergency_rec with command " /sbin/emergency_rec ctape1 " (in single user mode) it prompt me as : "/tmp is busy " and "/usr/tmp/hwrdmon open failed errno 0X2 adapter enquiry failed for 1... (1 Reply)
Discussion started by: luckylwf
1 Replies

2. SCO

Emergency boot

I need to boot an OpenServer 5.0.5 server but I don't have emergency boot disks for it. There are some boot disks of other servers. Can I use these disks, changing defbootstr ?. How ?. The fact is that administrator can't login as root and it seems to be a corrupted auth system issue. Other... (2 Replies)
Discussion started by: dags
2 Replies

3. SCO

Performance issue from Unixware 2.1 to Unixware 7

Hello, I am having performance problem when , i ported a c code from Unixware 2.1 to Unixware 7.0.0. My program establishes a synchornous connection with the client in a windows OS and then sends and receives messsages using the recv and send calls. What i hyave noticed is that after a... (0 Replies)
Discussion started by: Amith
0 Replies

4. SCO

steps to boot SCO server off emergency tape

I know how to create the bootable tape image by using emergency_rec, but I could not find any document to instruct me on how to boot off the tape, and detail steps I should go through, for instance, at what point the booting sequency would prompt me to enter bootable path, and what the path is...... (0 Replies)
Discussion started by: vkky2k
0 Replies

5. SCO

unixware 7.1.0 boot floppy #2 needed if someone has one.

Hi all, I'm reinstalling unixware 7.1.0 on another machine for a customer that will replace the existing machine that is now in use. When i go to start the install the second floppy is not recognized. These are the original sco floppies. I have recreated the boot floppies from the... (3 Replies)
Discussion started by: RDP
3 Replies

6. Shell Programming and Scripting

Need Emergency help with script!

I'm trying to write a script to push out to all our servers some Veritas add-ons. I want the script to push to all servers and if there server hardware matches the uname -i statement, it will install a additional add-on.. The script keeps giving me a error on line 29. Here is the script.... (3 Replies)
Discussion started by: soupbone38
3 Replies

7. Solaris

Emergency !!!Help Please--- NFS

Hi Guru's, I am unable to mount NFS share on unix system (DG/UX) which is nfs client. Error: mount: /nfsshare: Invalid argument mount: giving up on: /mountpoint i tried following commands mount -t nfs remotehost:/nfsshare /mountpoint Error: mount: /nfsshare: Invalid... (1 Reply)
Discussion started by: Justin John
1 Replies

8. SCO

Need emergency boot floopy or 5.0.5 .iso file

We have old SCO Openserver 5.0.5. and its was running out of disk space on root disk - error 142 /2. I tried to move some files to another partition with space, but I ran into issue as I moved /opt/K and /opt/P. Now when the servers boots it fails and goes into debug mode. I don't have a... (4 Replies)
Discussion started by: grips03
4 Replies

9. SCO

Emergency boot floppy - second hard disk not seen

OS = Openserver 5.0.5 Ran 'mkdev fd' and made emergency boot floppy (boot and root). Choose custom kernel, not generic. However kernel on the 1.44 floppy did not see both hard disks, it only saw the first one (SCSI id 0), and not SCSI id 1 (second disk) Q. Is this a limitation of emergency... (5 Replies)
Discussion started by: grips03
5 Replies
BOOTCTL(1)							      bootctl								BOOTCTL(1)

NAME
bootctl - Control the firmware and boot manager settings SYNOPSIS
bootctl [OPTIONS...] status bootctl [OPTIONS...] list bootctl [OPTIONS...] update bootctl [OPTIONS...] install bootctl [OPTIONS...] remove DESCRIPTION
bootctl checks, updates, installs or removes the boot loader from the current system. bootctl status checks and prints the currently installed versions of the boot loader binaries and all current EFI boot variables. bootctl list displays all configured boot loader entries. bootctl update updates all installed versions of systemd-boot, if the current version is newer than the version installed in the EFI system partition. This also includes the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created if there is no current entry. The created entry will be added to the end of the boot order list. bootctl install installs systemd-boot into the EFI system partition. A copy of systemd-boot will be stored as the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created and added to the top of the boot order list. bootctl remove removes all installed versions of systemd-boot from the EFI system partition, and removes systemd-boot from the EFI boot variables. If no command is passed, status is implied. OPTIONS
The following options are understood: -h, --help Print a short help text and exit. --version Print a short version string and exit. --path= Path to the EFI System Partition (ESP). If not specified, /efi, /boot, and /boot/efi are checked in turn. It is recommended to mount the ESP to /boot, if possible. -p, --print-path This option modifies the behaviour of status. Just print the path to the EFI System Partition (ESP) to standard output and exit. --no-variables Do not touch the EFI boot variables. EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. SEE ALSO
Boot loader specification[1] systemd boot loader interface[2] NOTES
1. Boot loader specification https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec 2. systemd boot loader interface https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface systemd 237 BOOTCTL(1)
All times are GMT -4. The time now is 05:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy