Sponsored Content
Operating Systems SCO Trouble with sysv floppy images created under Linux Post 302979665 by jgt on Wednesday 17th of August 2016 12:59:34 PM
Old 08-17-2016
I am cleaning out my library. I found most of the Xenix manuals, along with Lyrix, Foxbase+ and Professional.
If you want them, I will ship via UPS ground collect.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Reading SCO floppy on Linux

Is there any way I can read a floppy written on SCO Unix 3 on a Redhat Linux 6.0 machine?? If so, how? Thanks in advance, Leo :confused: (4 Replies)
Discussion started by: Leo Gessford Jr
4 Replies

2. UNIX for Dummies Questions & Answers

red hat linux installation boot floppy disk

Hi, My dear friends, I am trying to install red hat linux. I have downloaded its disc1. On the instructions page, the next stage is to make the boot disk, so that I can boot from the floppy. However, I am unable to locate the boot image iso file. I tried on google, but I got a few files which... (3 Replies)
Discussion started by: linuxpenguin
3 Replies

3. Programming

mutexing with sysv calls

My question is: what's the best way to implement mutual exclusion for a shared memory segment. I want to ensure that while updating a shared memory segment that another process will not get read part of the segment before and the other part after the update. (I also want to ensure that the update... (3 Replies)
Discussion started by: otheus
3 Replies

4. Linux

How to install linux in a system without cdrom, usb boot, floppy, other OS?

Hello to everyone, I am new to linux and I want to move to this system after bad experiences with windows. I have also a particular problem. An old laptop is probably able to handle just linux at this point of its life. The cdrom is gone, the bios doesn't have usb boot support, there is no... (6 Replies)
Discussion started by: highkftj
6 Replies

5. Homework & Coursework Questions

trouble shooting linux

hello this is laya. I need some help regarding linx installation and also trouble shooting. i installed linux mandriva 2009 in my school months ago and now it says password expired and doesnt start up. So i was wondering if there could be any default password for linux versions??? and next is that... (1 Reply)
Discussion started by: laya
1 Replies

6. Homework & Coursework Questions

trouble shooting linux

hello this is laya. I need some help regarding linx installation and also trouble shooting. i installed linux mandriva 2009 in my school months ago and now it says password expired and doesnt start up. So i was wondering if there could be any default password for linux versions??? and next is... (2 Replies)
Discussion started by: laya
2 Replies

7. Solaris

SysV package creation, how to predefine DESTDIR

Hi Solaris experts How to predefine the DESTDIR in a Solaris package? Thanks (1 Reply)
Discussion started by: ./hari.sh
1 Replies

8. Shell Programming and Scripting

Bash Script to find/sort/move images/duplicate images from USB drive

Ultimately, I'm looking to create a script that allows me to plug in a usb drive with lots of jpegs on it & copy them over to a folder on my hard drive. So in the process of copying I am looking to hash check them, record dupes to a file, copy only 1 of the identical files (if it doesn't exsist... (1 Reply)
Discussion started by: JonaQuinn
1 Replies
UPS.CONF(5)						      Network UPS Tools (NUT)						       UPS.CONF(5)

NAME
ups.conf - UPS definitions for Network UPS Tools DESCRIPTION
This file is read by the driver controller upsdrvctl, the UPS drivers that use the common core (see nutupsdrv(8)) and upsd(8). Each UPS gets its own section, and that section contains a number of directives that set parameters for that UPS. The section begins with the name of the ups in brackets, and continues until the next UPS name in brackets or until EOF. The name "default" is used internally in upsd, so you can't use it in this file. You must define the "driver" and "port" elements for each entry. Anything after that in a section is optional. A simple example might look like this: [myups] driver = fentonups port = /dev/ttyS0 A slightly more complicated version includes some extras for the hardware-specific part of the driver: [bigups] driver = apcsmart port = /dev/cua00 cable = 940-0095B sdtype = 2 In this case, the apcsmart(8) driver will receive variables called "cable" and "sdtype" which have special meanings. See the man pages of your driver(s) to learn which variables are supported and what they do. FIELDS
driver Required. This specifies which program will be monitoring this UPS. You need to specify the one that is compatible with your hard- ware. See nutupsdrv(8) for more information on drivers in general and pointers to the man pages of specific drivers. port Required. This is the serial port where the UPS is connected. On a Linux system, the first serial port usually is /dev/ttyS0. On FreeBSD and similar systems, it probably will be /dev/cuaa0. sdorder Optional. When you have multiple UPSes on your system, you usually need to turn them off in a certain order. upsdrvctl shuts down all the 0s, then the 1s, 2s, and so on. To exclude a UPS from the shutdown sequence, set this to -1. The default value for this parameter is 0. nolock Optional. When you specify this, the driver skips the port locking routines every time it starts. This may allow other processes to seize the port if you start more than one accidentally. You should only use this if your system won't work without it. This may be needed on Mac OS X systems. maxstartdelay Optional. This can be set as a global variable above your first UPS definition and it can also be set in a UPS section. This value controls how long upsdrvctl will wait for the driver to finish starting. This keeps your system from getting stuck due to a broken driver or UPS. The default is 45 seconds. All other fields are passed through to the hardware-specific part of the driver. See those manuals for the list of what is allowed. INTEGRATION
upsdrvctl(8) uses this file to start and stop the drivers. The drivers themselves also obtain configuration data from this file. Each driver looks up its section and uses that to configure itself. upsd(8) learns about which UPSes are installed on this system by reading this file. If this system is called "doghouse" and you have defined a UPS in your ups.conf called "snoopy", then you can monitor it from upsc(8) or similar as "snoopy@doghouse". Additionally, the first UPS in this file is the default ups in upsd. If you tell one of the clients to monitor a UPS by the hostname alone ("doghouse", without any @ or ups name), it uses the default UPS. If you have multiple UPSes or if you just want to avoid ambiguities, always specify the upsname and hostname with the client software. SEE ALSO
upsd(8), nutupsdrv(8), upsdrvctl(8) Internet resources: The NUT (Network UPS Tools) home page: http://www.exploits.org/nut/ NUT mailing list archives and information: http://lists.exploits.org/ Wed Oct 16 2002 UPS.CONF(5)
All times are GMT -4. The time now is 01:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy