Sponsored Content
Full Discussion: SCO system V documentation
Operating Systems SCO SCO system V documentation Post 302357031 by methyl on Monday 28th of September 2009 12:55:07 PM
Old 09-28-2009
Yup it was a good metre of shelf space. Now consigned to the loft. You didn't mention the OEM. Was it ITL by any chance?
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Sco Unix Online Documentation

help would be appreciated, thanks. (1 Reply)
Discussion started by: BAM
1 Replies

2. Filesystems, Disks and Memory

SCO TCP/IP runtime System for SCO Unix

Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
Discussion started by: Cerberus
0 Replies

3. SCO

system log of SCO

Hi, I did shutdown and restart SCO server, now wanna find log to know exactly when system was effected. I took a look at /var/adm/ but seem there are no logs for my required information. it seems diff from Sun or HP UNIX... appreciate all your help. Thanks (2 Replies)
Discussion started by: milo
2 Replies

4. SCO

where can get iso of sco system v 5.05

hi all please someone tell me where can get iso of sco System V vs 5.05 regards (1 Reply)
Discussion started by: weramirez
1 Replies

5. Solaris

Comprehensive system documentation by button click

Guys There's a new WebPage where you can generate a comprehensive detailed system documentation by button click. Look at the example at https://sdoctool.sun.com/data/doc.php?ID=sdoctool&N=2 ;) Interested, go to Cheers (0 Replies)
Discussion started by: lebch
0 Replies

6. SCO

Help on System Freeze in SCO

Hi, My SCO server freezes suddenly. I just want to know if there any tools / commands availble that can find which is causing the freeze? Any help on this would be greatly appreciated. Regards, Ravikumar R (4 Replies)
Discussion started by: rrb2009
4 Replies

7. SCO

SCO UNIXware 7.1.4 system backups

Hi, I wonder if someone can help me, I want to backup my sco unix system, I dont have an external/internal tape drive. How can I make a system backup? I do have a CD-RW on the server. I am new to sco unix. Please can anyone advise on what methods I can use, I have looked a cpio. I tried... (1 Reply)
Discussion started by: kpnuts
1 Replies

8. SCO

SCO Development System for System V 3.2 R4.2

Hi Guys, Some time ago I get a disk for my SCO System V 3.2 R4.2 tcp 1.2.1 distribution. Now 4 Year later I am serarching the development system due to the fact that System V did not come with the C compiler. There is any change to get it ? my intention is academyc only. or anyone... (3 Replies)
Discussion started by: locovich
3 Replies
vblade-persist(8)					      System Manager's Manual						 vblade-persist(8)

NAME
vblade-persist - manage persistent exported ATA-over-Ethernet devices SYNOPSIS
vblade-persist ls [--no-header] vblade-persist setup shelf slot netif blockdev vblade-persist destroy shelf slot vblade-persist { start | stop | restart | auto | noauto } shelf slot vblade-persist { start | stop | restart | auto | noauto } all vblade-persist mac shelf slot { ls | clear } vblade-persist mac shelf slot { add | del } [ addr ... ] DESCRIPTION
The vblade-persist script is used to show and manipulate persistently-exported ATA-over-Ethernet devices. It has a simple subcommand syn- tax. Persistent AoE device exports can be configured to come up at boot time. For each running persistent AoE export, a symlink pointing to the backing device is created in /dev/etherd/, mirroring the devices seen by clients of the AoE device. MANAGEMENT SUBCOMMANDS
ls [--noheader] vblade-persist ls shows all existing persistent AoE exports. The columns of the output are, in order: AoE Shelf, AoE Slot, Network Inter- face, Backing Device, AutoStart, Status. AutoStart is either "auto" (start automatically at boot), or "noauto" (don't start automatically at boot). Status should be either "run" (running) or "down" (not running). The optional --no-header argument suppresses the header line. This may be convenient for machine-parseable output. setup shelf slot netif source vblade-persist setup creates a new persistent exported AoE block device. You must supply all four additional arguments. These are the same arguments supplied to vblade(8). You should specify source using an absolute path. New devices set up this way are noauto (not brought up automatically at boot) and down (not exported immediately). destroy shelf slot vblade-persist destroy halts any running exported AoE block device managed by vblade-persist and removes the service directory used to man- age it. start shelf slot stop shelf slot restart shelf slot These commands control a specific exported AoE device. Instead of specifying shelf and slot , you can also provide the special keyword all which will act on every exported AoE device. auto shelf slot noauto shelf slot These commands control whether a specific exported AoE device should be started automatically ( auto ) or not ( noauto ) at system boot time. Instead of specifying shelf and slot , you can also provide the special keyword all which will act on every exported AoE device. MAC-ADDRESS FILTERING You can use vblade-persist to restrict access to specific exports by MAC address, using the mac subcommand. mac shelf slot ls List all MAC addresses allowed to access the specified device, one per line. If the list is empty, no MAC address limits are imposed on this device. mac shelf slot clear Remove all MAC address filtering from the specified device. No MAC address limits will be imposed on this device. mac shelf slot add [ addr ... ] Add a MAC address (or more than one) to the list of allowed addresses for the specified device. Note that if there were no MAC addresses listed previously, this will enable MAC address filtering for the device. mac shelf slot del [ addr ... ] Remove a MAC address (or more than one) from the list of allowed addresses for the specific device. Note that if you remove all the MAC addresses from the list, this will disable MAC address filtering for the device. EXAMPLES
Set up /dev/sda2 as shelf 2, slot 3 on the network served by interface eth0. Make sure it starts automatically at boot, and start it up now: vblade-persist setup 2 3 eth0 /dev/sda2 vblade-persist auto 2 3 vblade-persist start 2 3 Limit that same export to MAC addresses aa:bb:cc:dd:ee:ff and 11:22:33:44:55:66: vblade-persist mac 2 3 add aa:bb:cc:dd:ee:ff 11:22:33:44:55:66 Remove all MAC address restrictions on the same export: vblade-persist mac 2 3 clear BUGS
You can't currently use the vblade-persist framework to export a device (or two) with the same shelf/slot identifier on two different net- work interfaces. DEPENDENCIES
The exports themselves are handled by vblade(8). Supervision of the exports and convenient management is enabled by runsv(8), from the runit suite. SEE ALSO
vblade(8), runsv(8) AUTHOR
Daniel Kahn Gillmor <dkg@fifthhorseman.net> vblade-persist 2007-11-11 vblade-persist(8)
All times are GMT -4. The time now is 07:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy