09-14-2012
From my experience of SCO, /stand holds the currently booted kernel files, is indeed a separate filesystem written by the installer. Without /stand the system won't boot. The files in /stand are not significant in size. /stand is mounted at boot time and remains mounted continuously.
For any files to exist under the mount point, /stand would have had to have been deliberately and manually dismounted (can be done) and files put into that directory. Unless done deliberately nothing will exist in that folder.
I'm only saying this because I believe all subscribers to this thread are on the wrong track (pursuing /stand) as to the answer to the OP's question.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have to do a lot of reporting for the company that I work for and was wondering if anyone had suggestions for a way to create professional looking reports. I currently use Filepro so much that I rarely see the shell. Any help is appreciated. (3 Replies)
Discussion started by: Mike11
3 Replies
2. UNIX for Dummies Questions & Answers
Hi everyone, I'm completely new to the board and to UNIX and I have the following question regarding a script I am building.
I am trying to copy an entire directory into a new directory and I was wondering if there is any way of printing on screen a progress report, for example a percentage. It... (9 Replies)
Discussion started by: Ypnos
9 Replies
3. SCO
hi,
i m having a sco unix system...i want to store the output of dfspace command ie %free space of each partition to different variable so that i can use it for further processing.......can anybody pls help me out
thx
girish (1 Reply)
Discussion started by: girish_shukla
1 Replies
4. Shell Programming and Scripting
Hi:-
I am working on an audit report that produces a monthly summary of account activity on a particular AIX host. I am struggling with su activity and failed logins as these tend to come back with more then a month's data.
Is there a easy way that these files can be rotated/cleaned out on a... (1 Reply)
Discussion started by: janet
1 Replies
5. UNIX for Dummies Questions & Answers
I am very new to unix/linux and am unsure how to do the following tasks within my script
1) append a log file and add a timestamped echo "Error occured" to it, if posibble to print it to file and on screen at the same time would be even better.
2) As my main script will be calling on a couple... (1 Reply)
Discussion started by: shamwick
1 Replies
6. Filesystems, Disks and Memory
Hi.
How do you guys, monitor/report your Storage environment? I have people (don't we all? ) that like to have monthly reports on space (raw/assigned/available), ports available/used, switches and the such.
Do you use anything special? Or are you like me, a nice big Excel spreadsheet? How... (1 Reply)
Discussion started by: Stephan
1 Replies
7. Shell Programming and Scripting
I need to accomplish the following task -
I have a number of accounts for a number of applications that i deploy on a unix server. There are a number of directories for each account in /prod/apps directory. eg. For an account Application1 I have /prod/apps/Application1_1 /prod/apps/Application1_2... (4 Replies)
Discussion started by: niranjandighe
4 Replies
8. Solaris
Hi,
I am hunting for a low cost Monitoring & Reporting Tool for the SUN Environment.
I have all and all SUN Environment with LDOMs, Zones.
The monitoring Tool
1. Hardware failure.
2. Disk space and failure.
3. LDOMS,Zones.
4. CPU,Memory Utilization.
5. ping,URL Monitors
6. Send... (4 Replies)
Discussion started by: menonk
4 Replies
9. Shell Programming and Scripting
Below is a typical report
each of the lines represent the fields in the report
component1
component2
<pattern>
..
..
n lines ...
..
VIOL = 2
the command should display
component1
component2
VIOL = 2
only if pattern field of the report is "good"
component1 and... (8 Replies)
Discussion started by: dll_fpga
8 Replies
LEARN ABOUT CENTOS
mkbootdisk
MKBOOTDISK(8) System Manager's Manual MKBOOTDISK(8)
NAME
mkbootdisk - creates a stand-alone boot floppy for the running system
SYNOPSIS
mkbootdisk [--version] [--noprompt] [--verbose]
[--device devicefile] [--size size]
[--kernelargs <args>] [--iso] kernel
DESCRIPTION
mkbootdisk creates a boot floppy appropriate for the running system. The boot disk is entirely self-contained, and includes an initial
ramdisk image which loads any necessary SCSI modules for the system. The created boot disk looks for the root filesystem on the device sug-
gested by /etc/fstab. The only required argument is the kernel version to put onto the boot floppy.
OPTIONS
--device devicefile
The boot image is created on devicefile. If --device is not specified, /dev/fd0 is used. If devicefile does not exist mkinitrd cre-
ates a 1.44Mb floppy image using devicefile as the filename.
--noprompt
Normally, mkbootdisk instructs the user to insert a floppy and waits for confirmation before continuing. If --noprompt is specified,
no prompt is displayed.
--verbose
Instructs mkbootdisk to talk about what it's doing as it's doing it. Normally, there is no output from mkbootdisk.
--iso Instructs mkbootdisk to make a bootable ISO image as devicefile.
--version
Displays the version of mkbootdisk and exits.
--kernelargs args
Adds args to the arguments appended on the kernel command line. If this is not specified mkbootdisk uses grubby to parse the argu-
ments for the default kernel from grub.conf, if possible.
--size size
Uses size (in kilobytes) as the size of the image to use for the boot disk. If this is not specified, mkbootdisk will assume a
standard 1.44Mb floppy device.
SEE ALSO
grubby(8) dracut(8)
AUTHOR
Erik Troan <ewt@redhat.com>
4th Berkeley Distribution Tue Mar 31 1998 MKBOOTDISK(8)