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
mosquitto_pub(1)														  mosquitto_pub(1)

NAME
mosquitto_pub - an mqtt version 3.1 client for publishing simple messages SYNOPSIS
mosquitto_pub [-d] [-h hostname] [-i client_id] [-I client id prefix] [-p port number] [-q message QoS] [--quiet] [-r] { -f file | -l | -m message | -n | -s} [ -u username [-P password] ] [ --will-topic topic [--will-payload payload] [--will-qos qos] [--will- retain] ] -t message-topic DESCRIPTION
mosquitto_pub is a simple mqtt version 3.1 client that will publish a single message on a topic and exit. OPTIONS
-d, --debug Enable debug messages. -f, --file Send the contents of a file as the message. -h, --host Specify the host to connect to. Defaults to localhost. -i, --id The id to use for this client. If not given, defaults to mosquitto_pub_ appended with the process id of the client. Cannot be used at the same time as the --id-prefix argument. -I, --id-prefix Provide a prefix that the client id will be built from by appending the process id of the client. This is useful where the broker is using the clientid_prefixes option. Cannot be used at the same time as the --id argument. -l, --stdin-line Send messages read from stdin, splitting separate lines into separate messages. Note that blank lines won't be sent. -m, --message Send a single message from the command line. -n, --null-message Send a null (zero length) message. -p, --port Connect to the port specified instead of the default 1883. -P, --pw Provide a password to be used for authenticating with the broker. Using this argument without also specifying a username is invalid. This requires a broker that supports MQTT v3.1. See also the --username option. -q, --qos Specify the quality of service to use for the message, from 0, 1 and 2. Defaults to 0. --quiet If this argument is given, no runtime errors will be printed. This excludes any error messages given in case of invalid user input (e.g. using --port without a port). -r, --retain If retain is given, the message will be retained as a "last know good" value on the broker. See mqtt(7) for more information. -s, --stdin-file Send a message read from stdin, sending the entire content as a single message. -t, --topic The mqtt topic on which to publish the message. See mqtt(7) for more information on mqtt topics. -u, --username Provide a username to be used for authenticating with the broker. This requires a broker that supports MQTT v3.1. See also the --pw argument. --will-payload Specify a message that will be stored by the broker and sent out if this client disconnects unexpectedly. This must be used in con- junction with --will-topic. --will-qos The QoS to use for the Will. Defaults to 0. This must be used in conjunction with --will-topic. --will-retain If given, if the client disconnects unexpectedly the message sent out will be treated as a retained message. This must be used in conjunction with --will-topic. --will-topic The topic on which to send a Will, in the event that the client disconnects unexpectedly. WILLS
mosquitto_sub can register a message with the broker that will be sent out if it disconnects unexpectedly. See mqtt(7) for more informa- tion. The minimum requirement for this is to use --will-topic to specify which topic the will should be sent out on. This will result in a non- retained, zero length message with QoS 0. Use the --will-retain, --will-payload and --will-qos arguments to modify the other will parameters. EXAMPLES
Publish temperature information to localhost with QoS 1: o mosquitto_pub -t sensors/temperature -m 32 -q 1 Publish timestamp and temperature information to a remote host on a non-standard port and QoS 0: o mosquitto_pub -h 192.168.1.1 -p 1885 -t sensors/temperature -m "1266193804 32" Publish light switch status. Message is set to retained because there may be a long period of time between light switch events: o mosquitto_pub -r -t switches/kitchen_lights/status -m "on" Send the contents of a file in two ways: o mosquitto_pub -t my/topic -f ./data o mosquitto_pub -t my/topic -s < ./data Send parsed electricity usage data from a Current Cost meter, reading from stdin with one line/reading as one message: o read_cc128.pl | mosquitto_pub -t sensors/cc128 -l BUGS
mosquitto_pub bug information can be found at http://launchpad.net/mosquitto SEE ALSO
mqtt(7) mosquitto_sub(1) mosquitto(8) libmosquitto(3) AUTHOR
Roger Light <roger@atchoo.org> 5 February 2012 mosquitto_pub(1)
All times are GMT -4. The time now is 11:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy