Sponsored Content
Operating Systems SCO Noob needs help with Sco Unixware 7.1 Post 302453503 by ccd1977 on Wednesday 15th of September 2010 01:27:04 PM
Old 09-15-2010
OK...

Attachment 1631We already had a copy of Microlite on the server too. It was version 2.0 though. it made four boot disks. We installed the tape to the destination machine and booted off the discs. We used an optiplex 320L with 1 GB RAm but it kept crashing. We booted it up to 2GB and it got to the 2nd disk and did like a BSOD but UNIX version.

Is the microlite 2.0 version too old to do this? Could it also be that this PC is all USB for keyboard and mouse or am I just way off base.

Here is a PIC.

Last edited by ccd1977; 09-15-2010 at 03:08 PM..
 

8 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

SCO Unixware 2.1

I am using SCO Unixware 2.1 & some PC clients are connected, suddenly one message appearslike : UX:strintercept error: dropping message this message starts coming repeatedly & agtre some time system hangs.I had to reset the system & now the problem is not there.Please suggest, why this is... (0 Replies)
Discussion started by: paprch
0 Replies

2. UNIX for Dummies Questions & Answers

SCO Unixware 7 download

According to this thread: https://www.unix.com/showthread.php?t=1 one guy says However, I cannot find any sco unixware7 iso download link in their download section (http://wdb1.sco.com/clbk_web/owa/dwn_customer), is it really for free, and if that is true, where can I download it? Thanks, (2 Replies)
Discussion started by: phalcos
2 Replies

3. SCO

Samba 3.0.24 in SCO UnixWare 7.1.4

Please help me in troubleshooting my problem in Samba? I tried to instal Samba 3.0.24 in our SCO UnixWare 7.1.4 but after installing the nmbd daemon is not running. When i check the syslog from /var/adm, the following error appears: Sep 30 13:04:22 unixeei nmbd: bind failed on port 137... (0 Replies)
Discussion started by: eric_hing
0 Replies

4. SCO

sco unixware + oracle 8.0.5

hi, anybody can give procedure for how to install oracle 8.0.5 in sco unixware 7.1.4. (0 Replies)
Discussion started by: prakrithi
0 Replies

5. SCO

SCO noob please help

hello, sco openserver R5 the following error and it fails to load. init: Command is respawning too rapidily id: vm "/home/bin/stvm.sh" init: Comand..etc id: c02"/etc/start/autostart" its trying to mount car diagnostic program in vmware, the program location is in "start" i think? i... (1 Reply)
Discussion started by: hgibbs8129
1 Replies

6. SCO

SCO Unixware 7.1.1 Install - Need help

(sorry my English, is really poor). I have a SCO Unixware 7.1.1 and I need install in ML350 G3. Reading in google and HP web, make a floppy disks for install, but the options that I have is for network or floppy disk. How install from CD with patch for HP smart array 532 ?? or How... (5 Replies)
Discussion started by: xplertor
5 Replies

7. SCO

My UnixWare SCO Server

Hi, I'm new to this Unix world and have taken over looking after the I.T side of things at work, which includes the internal ERP system which runs on a UNIX SCO platform. My initial worry is what state this is in as its been on site over 20 years. What would be the first things to check on... (13 Replies)
Discussion started by: Mick_Dundee
13 Replies

8. SCO

Need Help with installtion of SCO UNIXware 7.0.1

Hi, I need help to install SCO Unixware 7.0.1. Can any one help with any documentation or installation notes for SCO Unixware 7.0.1. Thank you (1 Reply)
Discussion started by: farhandalvi
1 Replies
SYSTEMD-MACHINE-ID-SETUP(1)                                  systemd-machine-id-setup                                  SYSTEMD-MACHINE-ID-SETUP(1)

NAME
systemd-machine-id-setup - Initialize the machine ID in /etc/machine-id SYNOPSIS
systemd-machine-id-setup DESCRIPTION
systemd-machine-id-setup may be used by system installer tools to initialize the machine ID stored in /etc/machine-id at install time, with a provisioned or randomly generated ID. See machine-id(5) for more information about this file. If the tool is invoked without the --commit switch, /etc/machine-id is initialized with a valid, new machined ID if it is missing or empty. The new machine ID will be acquired in the following fashion: 1. If a valid D-Bus machine ID is already configured for the system, the D-Bus machine ID is copied and used to initialize the machine ID in /etc/machine-id. 2. If run inside a KVM virtual machine and a UUID is configured (via the -uuid option), this UUID is used to initialize the machine ID. The caller must ensure that the UUID passed is sufficiently unique and is different for every booted instance of the VM. 3. Similarly, if run inside a Linux container environment and a UUID is configured for the container, this is used to initialize the machine ID. For details, see the documentation of the Container Interface[1]. 4. Otherwise, a new ID is randomly generated. The --commit switch may be used to commit a transient machined ID to disk, making it persistent. For details, see below. Use systemd-firstboot(1) to initialize the machine ID on mounted (but not booted) system images. OPTIONS
The following options are understood: --root=root Takes a directory path as argument. All paths operated will be prefixed with the given alternate root path, including the path for /etc/machine-id itself. --commit Commit a transient machine ID to disk. This command may be used to convert a transient machine ID into a persistent one. A transient machine ID file is one that was bind mounted from a memory file system (usually "tmpfs") to /etc/machine-id during the early phase of the boot process. This may happen because /etc is initially read-only and was missing a valid machine ID file at that point. This command will execute no operation if /etc/machine-id is not mounted from a memory file system, or if /etc is read-only. The command will write the current transient machine ID to disk and unmount the /etc/machine-id mount point in a race-free manner to ensure that this file is always valid and accessible for other processes. This command is primarily used by the systemd-machine-id-commit.service(8) early boot service. --print Print the machine ID generated or committed after the operation is complete. -h, --help Print a short help text and exit. --version Print a short version string and exit. EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. SEE ALSO
systemd(1), machine-id(5), systemd-machine-id-commit.service(8), dbus-uuidgen(1), systemd-firstboot(1) NOTES
1. Container Interface https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface systemd 237 SYSTEMD-MACHINE-ID-SETUP(1)
All times are GMT -4. The time now is 06:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy